Every time I think I figure something out something new pops up and I end up wondering where it fits. Hopefully this will be the final time that I have to ask for help on this and thanks for all those who did help in the past.
in.acme.com= internal domain
acme.com= external domain
inmail.in.acme.com = FQDN internal exchange server
2 external owa servers in dmz
outmail1.acme.com = FQDN 1st owa server
outmail2.acme.com = FQDN 2nd owa server
mail.in.acme.com = FQDN of 1st 2010 exchange server
owa.acme.com = internet facing name of 1st 2010 exchange server
Will have second cas server, will be using cas array.
Migrating from 2003 to 2010. Not all mailboxes are going to be migrated at once so i will need 2003 running at the same time that 2010 is running. Existing legacy OWA/active sync will be running until all mailboxes have been migrated unless there's a way for 2010 OWA/active sync to take over with mailboxes still in 2003.
Setup will be 2 exchange 2010 servers running cas/hub/mailbox roles in a DAG. The cas array IP will point to the DAG IP. This setup will giving us no load balancing but will give us HA for both the Cas and the Mailbox DB. No DNS round robin.
Should the cas array name on the SAN be the internal FQDN that I have in our internal DNS server, such as: clients.in.acme.com
Since we need 2003, we'll need Legacy.domain.com. Should it be: Legacy.acme.com
on the SAN
Should autodiscover.com be: autodiscover.in.acme.com
According to MS here: http://technet.microsoft.com/en-us/exdeploy2010/default.aspx#DeploymentCheckList/ee721975/2003
the root domain should be included in the SAN. Is this necessary? If it is which root domain? my internal FQDN in.acme.com
or the external: acme.com