Changing a Outlook Client Access Server without a profile rebuild
I have a client that had a botched exchange migration. They were attempting a Migration from 2003 to 2010. At the point that I took over they had introduced two Exchange 2010 Client Access Servers and information spread between 2003 and both 2010 CAS(s). The fact the client did not implement a CAS Array meant that already deployed outlook profiles would never automatically move to the 2nd CAS.
A case was opened up with Microsoft and after going through several engineer escalations they stated there was no way we could accomplish getting all users pointed to the newly built CAS array without rebuilding all of the outlook profiles.
I just could not accept that. I spent a little time researching exactly how Outlook knows where its CAS is. Once I identified this I wrote a script that allows you to change the Outlook CAS while leaving all other settings alone.
I wrote an elaborate version of the script that backs things up and has complete logging and error checking. For the point of this post I will release a simple version of my much more complex script.