bhupalk
asked on
windows server 2003 AD controller server hardware replacement
Hi there,
I got someone just setup windows server 2003 AD domain controller temporarily in a desktop PC. However, now I am about to order proper IBM server and would like to know what the best way would be to move AD and all other configurations to this new box. Do I use ghost or install windows server 2003 on the new hardware from scratch and move AD and anything else across to the new box? I am sure people do replace AD domain controller's hardware with a different hardware all the time. Please let me know. I also need to replace an existing windows 2003 terminal server with a new hardware. Would this procedure be the same?
thanks,
Bhupal
I got someone just setup windows server 2003 AD domain controller temporarily in a desktop PC. However, now I am about to order proper IBM server and would like to know what the best way would be to move AD and all other configurations to this new box. Do I use ghost or install windows server 2003 on the new hardware from scratch and move AD and anything else across to the new box? I am sure people do replace AD domain controller's hardware with a different hardware all the time. Please let me know. I also need to replace an existing windows 2003 terminal server with a new hardware. Would this procedure be the same?
thanks,
Bhupal
A 2003 TS should be very similar, just build the box, add it to the domain and configure the apps in the same way.
You will probably already have a Windows TS license server and the new box should start using it automatically.
Depends whether is anything on the machine that could complicate matters - custom applications, data etc.
With the DC, the process above is good - the key thing to remember is don't just turn the machine off and wipe it. You must DCPROMO it out of the network and preferably put it in to a workgroup (so it is dropped from the domain) before wiping so that it properly flushed out of the domain.
As long as you make the new machine a global catalog at least an hour before starting the DCPROMO out process on the old machine, all FSMO roles will transfer as part of the DCPROMO process.
Simon.
You will probably already have a Windows TS license server and the new box should start using it automatically.
Depends whether is anything on the machine that could complicate matters - custom applications, data etc.
With the DC, the process above is good - the key thing to remember is don't just turn the machine off and wipe it. You must DCPROMO it out of the network and preferably put it in to a workgroup (so it is dropped from the domain) before wiping so that it properly flushed out of the domain.
As long as you make the new machine a global catalog at least an hour before starting the DCPROMO out process on the old machine, all FSMO roles will transfer as part of the DCPROMO process.
Simon.
bhupalk
TS Licensing service runs on a DC - so make sure you transfer it to the new DC :)
Everything else Sembee says looks kosher to me :) - although personally I would transfer the FSMOs off by hand in case the DCPROMO to remove the existing DC fails to complete for some reason. This is not about best practice, more my own recent and rather painful experience recovering a downed AD for an EE client.
Cheers
JamesDS
TS Licensing service runs on a DC - so make sure you transfer it to the new DC :)
Everything else Sembee says looks kosher to me :) - although personally I would transfer the FSMOs off by hand in case the DCPROMO to remove the existing DC fails to complete for some reason. This is not about best practice, more my own recent and rather painful experience recovering a downed AD for an EE client.
Cheers
JamesDS
ASKER
Hi JamesDS,
Thank you very much for your very helpful and quick response. I am new to AD as I am a novell person. The procedure sounds OK to follow. Except I want to keep the same computer name and the IP address as the current DC. Do I rename the computer name and change the IP address after demoting the old DC? Any issues with that? Also what's the procedure to move FSMOs and DNS service etc. if you don't mind or I will do some search.
Hi Sembee,
Thanks for your help. regarding TS, I have new setup for testing in my company with one DC and one TS. The applications are pretty standard and I will be OK with the install. The TS licensing service runs on this TS server. I also want to purchase more windows CALs and TS CALs. can you please advise where I should install windows CALs and TS CALs on the DC or TS server? I think I can use the TS server for TS CALS but windows CALs I am not sure. As majority of our users will use TS via RDP, do I install both windows CALS and TS CALs on the TS server or TS CALs on TS and windows CALs on the DC? Also I want to keep the same computer name and IP as the current TS server. I will build the server using temporary computer name and IP. Can I change the computer name and IP after I remove the previous TS server from the domain?
Thanks,
Bhupal
Thank you very much for your very helpful and quick response. I am new to AD as I am a novell person. The procedure sounds OK to follow. Except I want to keep the same computer name and the IP address as the current DC. Do I rename the computer name and change the IP address after demoting the old DC? Any issues with that? Also what's the procedure to move FSMOs and DNS service etc. if you don't mind or I will do some search.
Hi Sembee,
Thanks for your help. regarding TS, I have new setup for testing in my company with one DC and one TS. The applications are pretty standard and I will be OK with the install. The TS licensing service runs on this TS server. I also want to purchase more windows CALs and TS CALs. can you please advise where I should install windows CALs and TS CALs on the DC or TS server? I think I can use the TS server for TS CALS but windows CALs I am not sure. As majority of our users will use TS via RDP, do I install both windows CALS and TS CALs on the TS server or TS CALs on TS and windows CALs on the DC? Also I want to keep the same computer name and IP as the current TS server. I will build the server using temporary computer name and IP. Can I change the computer name and IP after I remove the previous TS server from the domain?
Thanks,
Bhupal
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Regarding the CALs - Windows CALs don't need any installing. While you can put them in to the Licensing Service (not terminal services licensing) this service is generally acknowledged by the community as being a waste of time. As long as you have the licenses you are fine.
Terminal Services licensing server should really be on a domain controller. You will have to call the Microsoft licensing centre to get the licenses reissued so it would be a good time to move it. TS servers in a domain will look to a DC for licenses first. If you get additional TS servers then you do not have to worry about license duplication because they are centrally managed.
I am not a great lover of trying to keep existing machine names and IP addresses for domain controllers - it can cause a lot of complication and actually increase the downtime window as you have to remove the machine from the domain and wait for the domain to fully flush it out before you can build the new one.
If the network has been setup correctly then changing the name, IP and anything else on the network shouldn't be an issue.
Simon.
Terminal Services licensing server should really be on a domain controller. You will have to call the Microsoft licensing centre to get the licenses reissued so it would be a good time to move it. TS servers in a domain will look to a DC for licenses first. If you get additional TS servers then you do not have to worry about license duplication because they are centrally managed.
I am not a great lover of trying to keep existing machine names and IP addresses for domain controllers - it can cause a lot of complication and actually increase the downtime window as you have to remove the machine from the domain and wait for the domain to fully flush it out before you can build the new one.
If the network has been setup correctly then changing the name, IP and anything else on the network shouldn't be an issue.
Simon.
ASKER
Thank you both. Your help is much appreciated. You guys are great. You have given me enough to think about and plan the move.
cheers,
Bhupal
cheers,
Bhupal
bhupalk
Welcome, glad to help
Cheers
JamesDS
Welcome, glad to help
Cheers
JamesDS
To transfer AD to a new DC
Build your new server with Windows 2003
Use DCPromo to promote it to a domain controller
Transfer the FSMO roles and any other services (like DNS) from the old DC
Check replication using REPLMON (Windows Support tools from CD)
Demote the old DC
Procedure for replacing A terminal Server would be different - i'll let another expert pick that one up :)
Cheers
JamesDS