Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 279
  • Last Modified:

Migrating a windows 2003 DC

We have a windows 2003 domain controller that is on a homemade box that we went to transfer to a new IBM blade server. We want to maintain the name and share for the controller as if it was the same box. I am trying to find knowedge base atricles on how this should be done. we have two trains of thought

1. Pormote the IBM to a secondary DC than sieze the roles from the promary making it the primary DC. copy all files and folders ( any ideas of how to do this and maintain the shares and permissions). demote the old primary DC to a member server and remove it from the domain.

        How could we keep the name of the server

0
arahming
Asked:
arahming
  • 2
  • 2
1 Solution
 
SembeeCommented:
You can't keep the name of the server while it is a domain controller. If you only have one domain controller then you should build a temporary one somewhere else.
Transfer all the roles (don't seize them as both severs are live).
Once the roles have been transferred out, dcpromo the machine out as a domain controller, then drop in to a workgroup. You can then shutdown the old machine.
Build the new machine with the old name and then dcpromo the machine in.

Simon.
0
 
arahmingAuthor Commented:
what about all the AD object usernames and pass on the Domain this is the PDC that we are trying to migrate
0
 
SembeeCommented:
As long as you have another domain controller and you allow enough time for the replication to take place (at least an hour) then you will not loose anything. I switch around domain controllers all the time without any issues. As long as you don't try to bypass anything or take shortcuts it will be fine.

There is no need to do disaster recovery techniques if you don't have to.

Simon.
0
 
Kini pradeepIT Technology Senior ConsultantCommented:
you could stick to your current paln.

1. promote the new server as a Dc, transfer all the FSMO roles onto this box and then demote it gracefully.
make sure you have a valid system state and a complete backup to rollback.

or
http://support.microsoft.com/?kbid=249694 use this, take a backup from the current server and then restore it onto this new server, but due to driver problems you might or might not get a bluescreen. I would rathar recommend sticking to the original.
0
 
arahmingAuthor Commented:
Sembee at this point I am going to have to say that  am thinking that your way s the correct way restore from a system state to a different system makes no sense to me. do you have any document from MS that would discribe this process

Thanks
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now