We are currently in the process of migrating exchange 2003 to 2010 and we have everything in a co-existence which is working well. All external OWA users are redirected to legacy (if mailbox is still on 2003) and the outlook anywhere clients are pointing to the 2010 CAS array. All users still on 2003 can still access outlook anywhere with no issues or prompts.
We have a 100mbit link to a data center and we have deployed 1 x Exchange 2010 MBOX server and 2 x CAS/HT servers using WNLB and a CAS array. We also have a DC/GC in the Data Centre. We want to move our whole Exchange infrastructure to the DC rather than our in-house comms room.
We have 2 sites "HQ" which is for our local office and "DataCentre" which is for the DC.
The issue we have is that when we do a local mailbox move the outlook 2010 clients profile (all clients are outlook 2010) do not automatically update and switch to the new 2010 CAS array and thus outlook is disconnected.
If however we "Repair" the outlook 2010 profile (both internal and outlook anywhere) or simply update the server name to "cas.exchange2010.local" it updates successfully and the user can carry on using outlook as before with no issues what so ever.
also i can confirm that autodiscover is working file internally and externally and that if we manually create the same users (who we just move to exch 2010) in outlook it will auto config their profile and connect to the cas.exchange2010.local cas array.
Please can you advise what we need to do to enable instant auto update of the outlook 2010 profile to point to the exchange 2010 CAS array server rather than having to explain to the user?
best,
Mike