Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hi All
We currently have a File Server that just so happens to be a Child Domain controller.
The hardware platform that this resides on is old an out of date, and we wish to move this Domain Controller to another peice of hardware.
We have been exploring different ways we can do this, but it seems that there are many things to consider and we want to draw upon some of your guys' experience.
We have thought of using 3rd pary sychronization software to synchronize the file data, but most of them out there do not replciate shared folder info, and some ACL stuff. Also, are not sure about all of the DC stuff (SYSVOL etc.).
We have thought about ghosting the OS to the other server, but the differences in hardware would most likely leave us in a world of hurt.
If anyone can offer suggestions or share their experiences, it would be greatly appreciated.
TY

"We have thought about ghosting the OS to the other server, but the differences in hardware would most likely leave us in a world of hurt."
You are right with that remark, but I have found when moving a DC to new hardware you have 3 options.
1. fresh install of OS, full rebuild of AD, install apps, copy all data.
2. Install the new SCSI/ATA/IDE controler driver on the old system. Clone the drive. Install the drive in the new rig. pray.... pray.... take 8 hours to get it back up and running properly by replacing drivers, repairing the OS, reinstaling service packs.
(if your systems are close... IE. Intel to Intel, same chip set mfg on mobo etc.. the 2nd option usually works well.)
3 Microshaft says its not recommended for DC's, but I have seen it work on them.
http://support.microsoft.com/?id=249694

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |