asked on Rename a forest and a domain prior to a migration
I am in the process of setting up exchange 2013 SP1 and migrating a network to a virtualized environment. Hyper-V will be the virtualized environment. The operating system will be server 2012 r2. There will be an instance running hyper-v only on the server and then two virtual servers - one for users /profiles, AD DS,DNS,DHCP, Remote Access etc. and one for exchange 2013 sp1. It is a small network with less than 20 users
My challenge is the internal domain name being used is a .com, but is not owned or registered to the company. It has never been an issue before because nothing went beyond the forest perimeter.
Is there a method to change the forest and internal domain names that will ensure all of the trusts for the network users is protected? Or would it be better to rebuild the entire system from scratch and choose appropriate internal domain and forest names?
My challenge is the internal domain name being used is a .com, but is not owned or registered to the company. It has never been an issue before because nothing went beyond the forest perimeter.
Is there a method to change the forest and internal domain names that will ensure all of the trusts for the network users is protected? Or would it be better to rebuild the entire system from scratch and choose appropriate internal domain and forest names?
Hyper-VWindows Server 2012Exchange
Last Comment
Ibrahim Benna
Are you referring to the active directory domain namespace OR the SMTP domain namespace here? Was this domain used previously? Am I correct in understanding that this is going to be a net-new environment and not a migration/upgrade? Where is the domain name currently being used?
ASKER
This is an AD domain namespace. The task is to create a server with AD DS, DNS, DHCP etc as well as exchange 2013 on a separate virtualized server.
The internal domain name being used is mycompany.com, but mycompany.com is not a registered domain name and is not available. It has just been used on a limited server installation in the past.
The options are going forward and in effect creating a new server installation are:
change the internal active directory domain name to something like local.mycompany.com without losing the functionality of the network and user trusts, or back everything up, and rebuild the server from scratch with an internal domain name that will not create issues moving forward.
Any comments are appreciated
The internal domain name being used is mycompany.com, but mycompany.com is not a registered domain name and is not available. It has just been used on a limited server installation in the past.
The options are going forward and in effect creating a new server installation are:
change the internal active directory domain name to something like local.mycompany.com without losing the functionality of the network and user trusts, or back everything up, and rebuild the server from scratch with an internal domain name that will not create issues moving forward.
Any comments are appreciated
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.