morbius007
asked on
I have a situation where a consulting company has created a situation I have to fix, here it is.
I have a separate Domain that carries the same name as my primary domain, the primary domain is much larger, and to add to my troubles, I have the secondary domain setup as the same internal IP address range as my primary.
My question, is there a simple way to rename an existing Domain, and How easy is it to reconfigure the IP address range the domain is setting on.
Server is a 2008R2 Standard Edition and is running Exchange 2010 Standard as well, I know its a mess!
Thanks in advance for your suggestions.
My gut tells me I am going to have to wipe the PDC and start over...am I wrong?
My question, is there a simple way to rename an existing Domain, and How easy is it to reconfigure the IP address range the domain is setting on.
Server is a 2008R2 Standard Edition and is running Exchange 2010 Standard as well, I know its a mess!
Thanks in advance for your suggestions.
My gut tells me I am going to have to wipe the PDC and start over...am I wrong?
Delphineous Silverwing
You can run RENDOM.EXE (In your system32 folder) to rename the domain. The next biggest issue you will have is that the clients will be unable to logon until the computers are joined to the new domain name. Make sure you know the local admin password on all of the workstations.
you can't have 2 identical domains? DNS will be impossible.
you have domain1.local/AD/EXCH/DNS (a) and domain1.local/AD/EXCHANGE/
changing the ip range is not a big problem. They can't be the same domain? or make one a subdomain of the second one.
you have domain1.local/AD/EXCH/DNS (a) and domain1.local/AD/EXCHANGE/
changing the ip range is not a big problem. They can't be the same domain? or make one a subdomain of the second one.
Although I can't help you on this question allow me to suggest that you re-post this question and offer 500 points for a solution. This is not going to be easy and will require lots of back and forth and you will get more help if you offer more points. As an aside the more points you offer also shows just how important and or critical it is to you so keep that in mind.
hmmm...it sounds like you are talking about two separate forests, is that correct?
IP addresses when using DDNS are not a huge deal but workstations will need to refresh themselves or log back onto the network. Also, consider lowering the lease time on your DHCP server.
The previous post is correct. The biggest headache will be reattaching the workstations back to the new domain unless you use a tool like ADMT to migrate them across.
There might be much more to consider as well like file access, etc., once users have moved over. A little more detail about the environment and your goals might help.
HTH
IP addresses when using DDNS are not a huge deal but workstations will need to refresh themselves or log back onto the network. Also, consider lowering the lease time on your DHCP server.
The previous post is correct. The biggest headache will be reattaching the workstations back to the new domain unless you use a tool like ADMT to migrate them across.
There might be much more to consider as well like file access, etc., once users have moved over. A little more detail about the environment and your goals might help.
HTH
ASKER
While the RENDOM.exe will allow me to rename the domain, what effect will that have on both DNS and The MS-Exchange system services, email addresses will have to be reconfigured, or is that part of hte RENDOM.exe utilities process?
Please clarify.
Please clarify.
No. You will have to take both of those into consideration.
Look at this post and the link it provides at the bottom: http://it.toolbox.com/blogs/techscrawl/server-2008-domain-rename-28069
CHanging the domain name will mean reconfiguring DNS. As far as Exchange is concerned as long as you are not changing your public addresses (going from @contoso.com to @fabrikam.com, for example) your recipiet policies will remain the same.
WARNING: what you are about to do is fairly complicated, has many things to consider, and will have a wide range affect.
Which domain are you wanting to rename by the way? Also, are they separate forestsw or different domains within the same forest. What resources reside in the secondary domain? Users? FIle servers?
I really need more information in order to provide even a basic roadmap.
Also, if you want the domains tor eside on separate networks (different IP address space) then you must have a way to segment the network you are currently on.
Look at this post and the link it provides at the bottom: http://it.toolbox.com/blogs/techscrawl/server-2008-domain-rename-28069
CHanging the domain name will mean reconfiguring DNS. As far as Exchange is concerned as long as you are not changing your public addresses (going from @contoso.com to @fabrikam.com, for example) your recipiet policies will remain the same.
WARNING: what you are about to do is fairly complicated, has many things to consider, and will have a wide range affect.
Which domain are you wanting to rename by the way? Also, are they separate forestsw or different domains within the same forest. What resources reside in the secondary domain? Users? FIle servers?
I really need more information in order to provide even a basic roadmap.
Also, if you want the domains tor eside on separate networks (different IP address space) then you must have a way to segment the network you are currently on.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, I suspected as much but I wanted to make sure, I knew that exchange 2010 would alter the possibility of changing the domain name and that it would affect DNS negatively due to the fact that I also had to change the base IP range of the domain.
My fall back was either re installation or replacement.
Looks like that is where I am going.
Thanks again,
My fall back was either re installation or replacement.
Looks like that is where I am going.
Thanks again,