Current Config is Exchange 2010 SP3 RU18 on Windows 2008 R2. While we await a decision on future state (2016/2019 vs O365), we have a sideways migation being set up for Exchange 2010 SP3 RU30 on Windows 2012 R2. Both environments are in the same data center.
We have internal DNS zones configured for ThisIsOurCompany.com (internal and external) and Company.local (internal). We have been told that for an SSO project, we will be losing split DNS as our internal DNS zone for ThisIsOurCompany.com will be removed.
We have 2 different CAS pools set up on our F5 - one is for our current CAS, other is the new CAS. Our new CAS are configured with an outlook.company.local certificate issued by our internal CA, and virtual directories reference outlook.company.local in the
URLs. All internal clients trust this CA. We do not have Outlook clients connecting over the Internet. External clients are either OWA or EAS.
Our current mailboxes are still on the old mailbox servers, using outlook.ThisIsOurCompany.com as the CAS Array with cached mode configured to use that name as the RPC Proxy in GPO (Only connect if Proxy Server certificate has this principal name,RPC Proxy
Server Name). We're planning to remove these settings from the current GPO, since the proxy name is going to change. Next, we'll rename the CAS Array to the new name and set the RPCClientAccessServer to the new name on the databases (old and new).
Aside from moving mailboxes, is there any way to speed up Outlook clients to use the new name? We are definitely moving the mailboxes, but the number of databases involved will take time to empty and we have pressure to move this along as quickly as we can.
Would replacing outlook.ThisIsOurCompany.com with a CNAME record that resolves to outlook.company.local help with any mailboxes still on the old environment? Any other suggestions to allow us to move off of the old name beyond moving all mailboxes?
Any other concerns we need to worry about with making the change to outlook.company.local?
