Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

namespace migration concerns

$
0
0

I am about to migrate a Windows Server 2003r2 Active Directory that has an Exchange 2003 server. This domain started as an NT4 domain and has been upgraded to its current level and is working well.

I plan to migrate to Server 2012R2 and Exchange 2013.

The domain is relatively small. I can migrate (I think, with an intermediary ‘08R2 server), or I can start a fresh ‘12R2 Forest/Domain and fresh Exchange.

I would prefer to migrate, but I am worried about namespace issues.

Current namespace is      internaldomain.loc    and machines are  servername.internaldomain.loc   .

NetBIOS domain name is        internaldomain    

Users are identified as   internaldomain\username   or    internaldomain.loc\username

The Active Directory DNS server is set with forwards to our ISPs DNS servers.

We have real world      externaldomain.com   MX record forwarded through our firewall to port 25 on our Exchange server.

Is it still a supported practice in Server 2012R2 to keep internal DNS  internaldomain.loc    and the external reference  externaldomain.com    ?

One of my SSL SAN certificate vendors mentioned something about  .loc   and   .local   suffixes being disallowed on new certificates. We do not use any web interfaces to Exchange internally, and if we did for any reason, I do not mind the warning message about the certificate not being trusted (internally).

All our internal access to the Exchange server 2013 will be from Outlook 2010 or Outlook 2013.

I think all the external services such as Active Sync, Outlook Anywhere, or Outlook Web Access, or the AutoDiscover service can be referenced to the  externaldomain.com     name and internally to the Exchange Server’s external facing interface just like I do in Windows Server 2008R2 and Exchange 2010, but I am not completely sure.

I have done a certain amount of research and think I can just migrate with my current namespace, but I would like to make sure I don’t create issues.

Can I migrate with my current namespace?

I think this is straightforward, but I would like some expert opinions and advice please.

I will post this in the Windows Server and Exchange server forums.

Thank you.


Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>