https://owa.elyriaschools.org/Microsoft-Server-ActiveSync
[cid:image001.jpg@01D2F020.EA377B50]
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Michael B. Smith
Sent: Wednesday, June 28, 2017 2:56 PM
To: exchange@lists.myitforum.com
Subject:
2016 should automatically proxy to 2010. The endpoint from the perspective of
the device is the 2016 server, so that should indeed be what is reflected in
the device configuration.
I would wonder about how you have the EAS vDirs configured, both for URLs and
authentication.
From:
I should add, a mailbox on the 2016 server with the temp.domain.com set up
works just fine.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Kennedy, Jim
Sent: Wednesday, June 28, 2017 2:20 PM
To: exchange@lists.myitforum.com
Subject: [Exchange]
Pre upgrade environment.
1 2010 CAScas.domain.com
2 2010 MBX
Current environment.
1 2010 CAS
2 2010 MBX
1 2016 Exch box temp.domain.com
So, the next step is to get the 2016 box to act as the CAS for the mailboxes on
the 2 2010 MBX boxes for OWA and ActiveSync. Got OWA no problem.
In O365, we have multiple accepted domains. Is it possible to report on the
volume of mail addressed to one of these domains?
Joe Heaton
Information Technology Operations Branch
Data and Technology Division
CA Department of Fish and Wildlife
1700 9th Street, 3rd Floor
Sacramento, CA 95811
Released yesterday:
https://blogs.technet.microsoft.com/exchange/2017/06/27/released-june-2017-quarterly-exchange-updates/
The blog article and the KB articles do a poor job of explaining everything
that has changed. 2016 CU6 includes a fix for the annoying Set-Mailbox bug
present in CU5.
