I am considering removing the CAS from the old server which may force outlook to find it’s new server but am unsure whether this will work or not, and I think I should migrate all the mailboxes into the new DB before I do this. How do I get the outlook clients to automatically pick up the casarray servername once their mailboxes have been migrated?.What is the correct powershell command I can run on the exchange server to ensure that all my outlook clients are connected to the new exchange server for all connection types (or identify those which are connected against the old server)?.Now that you have all that background info my question is two parts: Seem to pick up the new settings, both the old server and new server functions as a multi-role exchange having the Hub, CAS and MBX roles. Mailflow is now going to the new exchange server from the gateway over port 25, the autodiscover record in the internal DNS is now also pointing to the new exchange server, outlook clients and users computers have been completely restarted but still don’t When I look at the connection status of my outlook it shows that it is connected to casarray for directory, but the old server for mail. If I run the above command against the old server my name shows on that list as well. Get-LogonStatistics -Server "new-exch2010" | where | ft username,servername,clientname When I run the following command, it shows my mailbox is indeed connected to the new exchange server, but this is not true in outlook The outlook client is 2007 in both situations. But at home on my personal laptop non-domain joined, it has appeared to reflect the Shows it is connected to (under the account settings when you go to change the settings for the account), this is on a domain joined internal desktop. I have created a brand new mailbox for a new user and the user's outlook shows it is connected to, I have migrated my own mailbox but internally my outlook So I have built the new Exchange 2010 server, configured a new DB and CASArray. On the of things the existing server lacks is a CAS array configured,
I am performing a server migration from Exchange 2010 to Exchange 2010 (the previous installation was installed by an outsourced provider and is rubbish so I'm configuring it properly).