Testing this in a lab to fill in a knowledge gap just incase it ever comes up as a requirement in the future (I like to learn and test stuff in the lab when I have spare time at work). It would be used if the company changed namespace, for example, or was bought out.
If you have 2010 set up as webmail.domain.com and wanted to drop the webmail part and move to mail.domain.com (or even if the domain changed to webmail.newdomain.com) is this easy enough to accomplish? Internal and external DNS are the same (ie webmail.domain.com is used internally and externally).
OWA, Activesync and ECP, etc run off the webmail.domain.com link so the virtual directories would need to be changed which is easy enough. Where else would the change need to be applied as a lot of the settings configured are not in the console, but powershell only.
The list I can think of is:
1.OWA (2010 console under server config)
2.ECP (2010 console under server config)
3.Activesync (2010 console under server config)
4.OAB (2010 console under server config)
5. EWS (Powershell only)
6.Autodiscoverserviceinternaluri is Autodiscover.domain.com so no need to change
7.Outlook CAS array is Outlook.domain.com so no change required
8.DAG is on DAG01.domain.com so no need to change
Is the above list the only parts that would need changing, or are there more hidden settings somewhere?