I am getting ready to add CAS/HUB servers to an existing Exchange 2010 CAS Array / DAG environment. These servers are being setup in a alternate location and I want to be able to control when clients connect to them just in case the network connectivity to them is poor or if they have any initial configuration issues. Network connectivity is being load balanced via hardware based equipment and I will not be adding these new CAS servers to the mix right away. My concern is the SCP records that are published automatically, are these only for Autodiscover? I know how to remove/change those, but are there any others for any of the other services? Hub transport I'm not as concerned with as I should be able to just disable the transport service if I run into issues there. Along the same lines, is there anyway to stop clients from automatically attempting to connect to a CAS server via SCP records as soon as the server is setup? If you don't have a good certificate ready wouldn't clients start to get cert. errors on the self signed certificate? Appreciate any input, I've setup only a few Exchange environments and have run into this both times...Jason Meyer

After installation, if you dont want users connecting the new CAS, set the AutoDiscoverServiceInternalUri for that CAS to $null or to another CAS or to the load balanced URI you have already defined.

OK, great, is that the only SCP record that gets published automatically by server name or are there any others? Thanks for the input.Jason Meyer

OK, great, is that the only SCP record that gets published automatically by server name or are there any others? Thanks for the input. Jason Meyer There is only one SCP created for each CAS, yes. So all you need to do is change that if desired.

Awesome, thanks Andy.Jason Meyer