Microsoft 2008 R2 AD Domain Name Change (Rename)
Hello Experts,
I'm here because I'm yielding to those who have much more experience of which what is probably a simple process. In the end I'm hoping for somewhat of a step by step process. I'm a novice at AD and while I'm sure I could patch this project together, I was hoping to do something "the right way" for once.
Background:
I'm currently at a small school district which has recently gone through a name change. The network consists of 4 sites with a single MS 2008 DC at each location. The system is running well, but the name of the domain is inconsistant with the rest of the organization.
I'm sure the system would operate just fine if I left it alone, but I guess I'm a glutton for punishment because I'd like the naming to be congruent with one another.
Through research I've found that there are basically three options for my scenario:
1.) Complete rebuild of a new domain and then migration.
2.) Rename current domain
3.) Create a two domain structure with trusts.
I would prefer to do a complete rebuild as I feel I'll have a better understanding of the layout instead of any underlying configs from the previous administrator.
My problem is that I do not have funding for additional boxes to facilitate a proper test lab. I need to somehow utilize the current boxes while allowing the current domain to remain operational until I migrate the users and machines to the new domain. I do have solid backups of the current structure to fall back on.
Current Assets:
Approx 400 end user devices (mostly xp sp2)
Approx 15 production server (2003 & 2008)
AD is relatively straight forward, nothing complicated just users, computers, and security groups
CA is not involved
MS Exchange is not involved
Questions:
Can I utilize the current DCs to bring a new domain?
Will it be completely independant?
Will I need to touch every asset in order to join it to the new domain?
Is what I'm about to do stupid?
I'm open to any and all opinions
Thanks in advance.
M
I'm here because I'm yielding to those who have much more experience of which what is probably a simple process. In the end I'm hoping for somewhat of a step by step process. I'm a novice at AD and while I'm sure I could patch this project together, I was hoping to do something "the right way" for once.
Background:
I'm currently at a small school district which has recently gone through a name change. The network consists of 4 sites with a single MS 2008 DC at each location. The system is running well, but the name of the domain is inconsistant with the rest of the organization.
I'm sure the system would operate just fine if I left it alone, but I guess I'm a glutton for punishment because I'd like the naming to be congruent with one another.
Through research I've found that there are basically three options for my scenario:
1.) Complete rebuild of a new domain and then migration.
2.) Rename current domain
3.) Create a two domain structure with trusts.
I would prefer to do a complete rebuild as I feel I'll have a better understanding of the layout instead of any underlying configs from the previous administrator.
My problem is that I do not have funding for additional boxes to facilitate a proper test lab. I need to somehow utilize the current boxes while allowing the current domain to remain operational until I migrate the users and machines to the new domain. I do have solid backups of the current structure to fall back on.
Current Assets:
Approx 400 end user devices (mostly xp sp2)
Approx 15 production server (2003 & 2008)
AD is relatively straight forward, nothing complicated just users, computers, and security groups
CA is not involved
MS Exchange is not involved
Questions:
Can I utilize the current DCs to bring a new domain?
Will it be completely independant?
Will I need to touch every asset in order to join it to the new domain?
Is what I'm about to do stupid?
I'm open to any and all opinions
Thanks in advance.
M
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
see this article
https://www.experts-exchange.com/questions/25664044/Domain-rename-under-Windows-Server-2008-R2.html
all the best
https://www.experts-exchange.com/questions/25664044/Domain-rename-under-Windows-Server-2008-R2.html
all the best
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the insight into the naming reasoning.
In the end (in lue of the above information) I will stay with the current convention. It's working fine and until I muster up the confidence to wipe and redu I'llbe sticking with what I have.
Thanks for the attention to the question.
In the end (in lue of the above information) I will stay with the current convention. It's working fine and until I muster up the confidence to wipe and redu I'llbe sticking with what I have.
Thanks for the attention to the question.
1. You can't utilize the current DCs for the new domain. You could demote two of them then wipe and rebuild and make those two the new domain.
2. Yes the new domain would be a new forest/independent
3. Don't need to touch every machine using ADMT or another migration tool.
Not stupid but does require a lot of planning and testing. (regardless of method used.
Thanks
Mike