• 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.

Help with new server, win 2k3

A

aimjay2

n00b
Joined
Jan 17, 2008
Messages
9
Hey i need some help with this.
Where i work we have an old p4 pc with w2k3 standart edition, with more o less 55 pcs in the domain. The server is having the role of domain and file server, DHCP, DNS, WINS , etc.
We bought a new Dell server with win 2k3 also. And i think that the easiest way of migrating it, is somehow passing the config and files to the new one. But i dont know how to do it.
Any ideas?

Sory for my english, im from Spain.


Thanks a lot to everyone :)
 
i know of no way to automate dhcp. as far as i know, you have to reconfigure and activate dhcp on the new server. again, i know of no way to pass the config files.

when you dcpromo the new server (i am assuming you will do this), dns will be pretty straight foward.

i don't know about wins, sorry.

here is one nice thing that i have tested and works perfectly. you can export a registry key that has all share permissions and then import that key into to the new server. it will save you a lot of time.

http://support.microsoft.com/kb/125996
 
you can backup and restore a DHCP database to a new server. I have done this successfully twice now. If you only have a couple scopes I would just rebuild it on the new server since it will take less time than backing up and restoring. I can't remember what the backup utility is called, I think its called JetPack or JetSomething....


I would just join the new server to the domain, dcpromo it, move the schema, RID, PDC over to it, etc. Then setup DHCP, WINS, DNS, etc. Then run dcpromo on your old server to demote it from being a domain controller, then uninstall DNS, WINS, etc to make sure AD is cleaned up and you don't have old server left overs laying around. Then you'll need to re-create shares, copy data from old server to new server, edit login scripts to point to new server, etc. If you have roaming profiles or folder redirection setup then you'll need to point that to the new server.

Good luck! :D
 
Thanks for the responses!
The thing i am a little scared of touching all without knowing...
For example, if i pass the data from the old server to the new one... i will not have problems with the permissions and security issues?
I´ve been looking in support.microsoft and other places for a more o less built guide o help with this but i didnt found one?
Basically what i want to do is replace the old server with a new one, and if it is possible mantaining the same config.... both with w2k3 standart edition.

Thanks :)
 
I understand the posters who said (basically) "Call in a pro"... Someone who know's what they're doing probably will save you a lot of headache... However, I'll try to draw up a simplified outline for what you're trying to do:

Start up the new server...
Install DNS, DHCP, and WINS... But don't configure them. (Do you still really need WINS, I mean REALLY? Think about it.)

DCPROMO the new server and join it to the current domain to get AD installed. This will get all the AD data to replicate to the new server. During this phase, tell dcpromo to also configure DNS on the server.

With one server and only 55 clients, your DHCP is likely quite simple. I'd say just reconfigure it from scratch, that way you can configure your new DNS options (and WINS IP address, if you still really need it) at the same time... If you've got a lot of reservations, you can use NETSH to move them... Basically backup and restore your DHCP config... (google for netsh backup dhcp)...

As another poster mentioned, you can export the reg keys that contain your share configs (done this a number of times myself)... Then import them into the new server, tweaking paths as necessary...

Then use an app like ROBOCOPY to copy all the files from the shares of the old server to the new server, making sure to use the options to also copy the file and directory permissions...

Hopefully, that'll give you some info to get started, or to refine your google searching... Have fun.
 
I agree, who uses WINS these days ?

DHCP is the only thing that cannot be easily threw accross to another server, but for a small environment , who cares it dont take very long to just recreate the scope (and maybe recreate reservations if u need them for for certain devices)
 
for dhcp migration just use netsh dhcp server export [path to export to] on the old server then netsh dhcp server import [path to config that was exported] on the new one
make sure the new dhcp server is authorized in ad, and you will have to deactivate the scopes on the original dhcp server when everything is migrated

to migrate the file shares just use the Microsoft File Server Migration Toolkit

for WINS setup replication partners then replicate the database

and someone else already covered promoting the new server to be a dc then waiting for replication to occur (for both ad and dns) then you demote the original server from being a dc (make sure the fsmo roles migrate when you demote the original server)

and everything should work... I dont think its that big of a job, I would say one day to migrate all the stuff keep both servers up for a day to make sure all the replication works and then start pulling down the original server little by little on the third day

and if all else fails search microsoft technet
 
You must log in or register to reply here.
Back
Top