Transferring a Domain Controller The Easy Way

[BaccyNet]

Hi all!

I'm looking for a bit of advice on this one, I've built many a server from scratch but this is the first time I've needed to move a primary domain controller/file server/print server onto a new system.

Basically I have the following: An upgraded Windows 2003 server (upgraded from Windows 2000) that is currently running the sites DHCP, DNS, Printers, antivirus administrator, CD shares, two public data shares (very large!), a few other assorted services and is the main domain controller. Unfortunatly it has been in place a long time and the server is really starting to struggle with the demand being placed on it. Because of this, the network manager has aquired money to replace it and I currently have a very high spec'd HP Proliant DL580 sitting in the office.
Here's what I need help with...

I need to transfer ALL the current servers operations onto this new HP. At the same time I need to be able to bring the server online in a very short space of time (thats not building it, I mean from finalized config to replacement of current server) and it must match the previous server exactly (even the naming must be the same due to some old and odd software that we run)
Obviously I have full backups of the server every night as the two data shares are used a lot during the day but I have a small window at night where no-one is using the server (no-one has remote access to the server, yet!)
Finally as this server is the sites DHCP server, it controls the running of the Mitel IP Phone system that we also run here, another reason for my unwillingness to transfer without advice.

I looked around to see what software I could use and have stumbled accross a HP Migration tool, but I'm looking to do this at no additional purchases if possible as it was hard enough getting funding for the server in the first place.

Anything else you need to know I'll try and get back to you as soon as possible. I'll be glad for anyone opinions/articles/free software tools that can help me out with this.

Thanks in advance
Steve

 

[Roadki11]

I think i would do this over a period of time instead of trying to get it all done in one night or over a weekend. I would bring up the new server and add it as a domain controller in the domain. Then i would transfer all FSMO roles and CG to the new server. Then i would move each service one at a time over to the new server as time permits and work out the glitches with each service. Start with the easy stuff first, dns, dhcp, and printers addressing the dhcp and phone issues and printer mappings and so on and so on. once everything is moved over and working then i would dcpromo the old server out of the domain.

Just my 2 cents,

RoadKi11

 

[reynolwi]

I would agree with roadkill 100%. If you go and move everything at once and something happens along the way your downtime increases. Your only downfall is going to be the server naming issue you mentioned with your "old and odd" software.

Is there not a way to change information in the software to reflect the new server?

Wm. Reynolds
RRWDS | TxPSS

http://www.rrwds.com

http://www.txpubsafety.com

- - - - - - - - - - - - -
Network Error:
Hit any user to continue

 

[NickFerrar]

I know you don't want to spend more money but the only way I can see you doing this successfully in a short period of time is by using imaging software. We use

http://www.partition-manager.com/

(you'll need the Enterprise option), just plug in a USB hard drive with enough space for the data, boot the source server from the Paragon CD, back it up to the USB hard drive (can take several hours if there's a lot of data), plug USB drive into destination server, boot destination server from Paragon CD and restore.

We've used it a few times so far and it's worked perfectly, trying to create an image of a server without using imaging software is a nightmare and likely to fail. Better still once you've bought the software you can use it as many times as you want (we primarily use it for repartitioning C: volumes on servers).

 

[BaccyNet]

Thanks for the replies guys!

The only reason I am interested in getting the switch over done as soon as possible is due to management having invested a large sum of money in the new server and the want to see results quickly (typical!)

NickFerrar: We do currently run Symantec Ghost on site for imaging desktops and laptops, would this be alright for the server? Obviously I would have to find space somewhere for the images but that can be arranged.

I understand that time is going to be key to this and if it's the only way to go then so be it, just thought I'd explore all other avenues first just in case

Thanks
Steve

 

[faisalt]

I recently did somewhat similar task with the exception of using same name. Overall it was very smooth process. I did exactly what roadki11 has prescribed. I waited two weeks before the final decomission of old DC. The next day users complained they couldnt access their network share. They were getting Access Denied error. We are not using group policy to map network drive, so I knew the problem is not with replication. I had the feeling that something happened to share permissions at decomissioning stage. Users were getting louder so I end up calling Microsoft and he looked at the shares and told that it was not configured correctly. Everyone group should be given full control to share permission and restrict folder under security. So I did that and so far no problem. Just a word of advise, keep Microsoft number handy, just in case
Good luck!