Changing a DC/File Server

[CrazyJoeDavola]

Hi Guys,

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
CJD

 

[mobyduck]

Why not just build the new hardware into the child domain as a DC then move data, shares and mappings at your leisure and while the ADC gets itself sorted out and you can resolve stuff like DNS errors (you will get them...)and DHCP ranges.

Run both for a week just in case, then simply promote the new hardware to PDC and remove the old hardware. It reduces your users downtime as well...

MD

 

[ntinlin]

SecureCopy from Smallwonders will do the share / file sync very well with a nice GUI but is extortionately expensive.

If you don't have too many shares then I'd just set them up manually. Use Robocopy to transition the files and update ACL's etc.

There is a way to export the shares of one server to another after you have created the folder structure from a registry key, but it is an all or nothing affair. You can't pick and choose which share details you want to bring across and drive letters all have to be the same as well.

Neill

 

[markdmac]

CrazyJoe,

I think MobyDuck misread your typing ACL for ADC, but beyond that I think that the advice given from both MobyDuck and ntinlin should get you going.

Create a new DC in the domain. Allow time for AD to replicate. That will satisfy half of your needs. I like RoboCopy a lot especially since it can copy the security flags too for you.

I would add that you should also run XCACLs to generate a report on all folder permissions. That way in the future if you need to reference this information you will still have it and can adjust any settings as necessary on the new server.

As ntinlin has suggested I would agree to just manually create the shares or to script their creation if there is a large number of them.

I hope you find this post helpful.

Regards,

Mark

 

[CrazyJoeDavola]

Thanks for all the ideas.

I'm going to try 2 methods.

#1 is a hardware "trick" I've done before by adding a scsi disk/controller and ghosting the image over to the scsi disk, then adding the scsi disk and controller over to the new server. If this does'nt work, I'll do method #2. Use Robocopy or other synchronization/replciation software to the new server, and try restoring the shares by using the registry keys fropm the old server:

http://support.microsoft.com/default.aspx?scid=kb;en-us;141589

I'm curious if anyone here has ever tried using the above method for restoring shares.

Thanks everyone for the help.
CJD