I'm building some new Exchange 2019 servers in my environment and do not want clients to immediately use their AutoDiscover service connection points (SCP) that get created in Active Directory during installation. We should be able to update the default InternalUrl/ExternalUrl values and test before these become active. What is the best way to hide, block, or disable the default SCP until I am ready to use them?
Our options appear to be:
- Update the URL values as quickly as possible after the installation completes.
Or run a looping script that looks for the creation of the SCP during installation, and performs an action immediately, such as:
- Remove "Domain Users" read permissions when it is found (or add a 'deny', but 'deny' ACEs...).
- Set the
AutoDiscoverSiteScope
attribute to a non-existent AD site as quickly as possible after the installation completes so the new one is not considered authoritative for an AD site. - Set the
IsOutOfService
attribute to $true.
Or something else to make them start out in a 'disabled' or 'out of service' state?