• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Copying a windows server 2003 configuration?

S

Stupid2

Gawd
Joined
Sep 8, 2001
Messages
553
I have a windows 2k3 server and I'd like to copy the configuration, e.g., the active directory users, dns server setup, pdc setup, etc., etc., to another installation of windows 2k3. Now I understand that if the hardware were the same, I could use ASR, however, this I'm trying to do this from one server to a differently configured server and I really just want the configuration of the install, not an actual back up of the whole machine.

I've got to imagine that there is a way to do this (if not, then that is just retarded) but I can't seem to find any info on google (at least with my searches). Anyone have any insight here?
thanks!
 
Unless you are replacing the machine, then you are going to need to accomplish this semi-manually. Many server services have replication capabilities in them. For AD, just promote the new machine as a DC and move the master roles. For DNS, convert your DNS zone to an AD integrated zone if it's not already and install DNS on the new server.

What services does this machine run?
 
hey thanks much, and forgive any misunderstanding on my part, I'm definitely not a sysadmin and never billed myself as such but someone has got to do it or it just won't get done. Currently the machine is running as a pdc, dns server (which in reality shouldn't be an issue as it's an isolated network), and well, that's about it really (it's running a file server and print server as well but i'm not terribly worried about having to set those up again).

Is there any chance you might care to elaborate a bit more on the active directory bit?

much obliged, thanks
 
write down IP config of current DC
build said new machine
once built, run dcpromo from a command line and go through the steps
Add DNS to new machine (confused as to why you said you didnt need DNS)
move over DHCP scopes but dont activate yet
move over FSMO roles
add printers to share (make sure they are the same share name as the old server so people wont have to remap)
let it sit for a few days
check logs
at some point after this you will have to move all the files from the current file server to the new one and recreate all the shares of course while no one is around using the files
activate new DHCP scope
dcpromo the old one back to a member server
check logs
disjoin old server from the domain, delete computer object, rename new DC to old dc's name and IP.

That should give you enough info to get started, I take no responsibility if your network completely stops working and all your hair falls out or anything else bad. There is also some other details and such that I just cant type out. Good luck and im sure someone will come in and reccommend a different way but atleast I got the ball rolling for ya
 
Jon,
thanks much obliged for the info. What i've ended up doing so far is I setup the new server on the network while the original domain controller was in place. I set the new server up as an additional domain controller and transferred over all files, dns settings, and printers. To test this, I just shutdown the original domain controller. Everything works fine except, it seems that at some point some setting to synchronize files between the desktop's and the server was turned on, so whenever a user logs on or off, their workstation tries to synchronize their files with the server. This seems to be stuck trying to acces the old domain controller rather then the new one.

(I went this route as I did not need to maintain name or ip integrity with the old domain controller).

any suggestions?
Thanks again!
 
Make sure you demote the old server as a domain controller. You do this by running the DCPROMO command. It will walk you through the demotion process.
 
MorfiusX said:
Make sure you demote the old server as a domain controller. You do this by running the DCPROMO command. It will walk you through the demotion process.
Click to expand...

Yes. This is important.

But you can just add the new server as an additional DC, and transfer the Operational Master Roles to it, and the FSMO roles of your choice as well. If this is a semi-large network, multiple AD servers are a good idea.

Basically in the end, just have the old server as a backup and AD replicator.
 
Dan_D said:
Basically in the end, just have the old server as a backup and AD replicator.
Click to expand...
You could leave it an additional DC. Depends on his reasons for moving to a new server.

You should not leave a DC shutdown/not replicating for more the 30 days. This cause replication problems when you try to bring it back up. If a DC will be down for more than 30 days, MS reccomends to demote it as a DC. Just an FYI seeing that it has been shut down.
 
MorfiusX said:
You could leave it an additional DC. Depends on his reasons for moving to a new server.

You should not leave a DC shutdown/not replicating for more the 30 days. This cause replication problems when you try to bring it back up. If a DC will be down for more than 30 days, MS reccomends to demote it as a DC. Just an FYI seeing that it has been shut down.
Click to expand...

They recommend that because a lot of changes can occur to an Active Directory in 30 days. :D

Due to the way DC's communicate I can see it being a problem if they are left un-synchronized for too long.
 
You must log in or register to reply here.
Back
Top