Exchange 2010: If I build a new CAS server with a different name, is it difficult to move the services over and decommission the old one? Our current CAS server works but is slow...
I know there SSL to worry about, and the rpcclientaccessserver property, what else? I am used to SMB single-box Exchange setups and have inherited a single-CAS/dual Mailbox setup. What was suggested to me by the team here was build a new CAS server and just move things over to the new CAS. What I did was build a new CAS server (by this I mean a server with Exchange 2010 and HT/CAS roles installed and our wildcard cert installed, but I did nothing else to our environment) but what I didn't realize is that apparently some clients are connecting with the new CAS server as they're getting a security message that's effectively "NWECAS.OCHIN.ORG name does not match the security certificate". I also didn't know if it made more sense to implement a CAS array instead to give more options going forward. Thoughts? Dave
