Best way to Migrate: NT4.0 Server to SBS 2003 2

[dcsnetwiz]

OKAY..really quick... I have my plan down about how I want to migrate a client of mine from NT 4.0 server to SBS 2003. However the more research I do, I find different opinions. In short whats the best way to perform this migration. LAYOUT: Brand new server from Dell, SBS 2003 standard. NT server is basically a file/print server with not a lot of data. MY PLAN.... After hours migration, copy the data to another machine, take NT 4.0 offline, impliment SBS 2003, copy data, configure network, users accounts, AD, etc.... sounds good? Any advice/input is much appreciated!

TIA

A

 

[markdmac]

You don't mention if this NT4 machine is a PDC?

How many users (obviously less than 75 since you are going to SBS)

Have you looked at ADMT? This is probably your best tool for an NT4 migration. With it you can get your SBS setup going independant of the NT4 setup. Then migrate your user accounts and machine accounts with ADMT while preserving all the SIDS for file ownership.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[dcsnetwiz]

Thanks for responding...
This NT server is a PDC with about 15-20 user accounts. My thoughts on the user accounts were to rebuild them in SBS2003 and not really worry about the old accounts. Since SBS only allows one DC I thought it might cause issues having them online at the same time. I have not come across anything about ADMT. I'll assume is the Active Directory Migration Tool...? Where do I get this tool? As far as the SIDS are concerned, is a simple file transfer not sufficient? If I rebuild the new user accounts in SBS2003, will the users no longer be able to access the files from the data transfer?

TIA

A

 

[markdmac]

You can find a copy of the ADMT tool on the Server CD, an upgraded version of it is also available for download on the web Microsoft site.

If you just do a file transfer, file ownership will get screwed up. If security in this small environment is lax then no big deal. If however you are locking things down then it could be a bigger deal. This doesn't present any large roadblocks if you can't or even don't want to use it, you just need to be prepared to reset the file permissions for each of those users. With so few users that may be acceptable. If you are doing this on a fixed price then I'd be looking for ways to reduce your time and ADMT will do that for you.

I'll now give you the flip side. SBS is really heavily reliant on Wizards and you will get the most rock solid install using those wizards including the user creation wizard.

Also, there is no problem having the two servers on at the same time. You should be able to attach to the old server and pull the data right over. You will find this easiest if you synchronize your admin ID and Passwords on both servers.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[dcsnetwiz]

ADMT...got it. That tools seems like a lot of steps for very little user accounts. It also talked about local computer accounts.... From past experience local accounts change no matter what when domains are changed. Correct me if I'm wrong but for only 15 users backing up the data (which equals less than 6GB) rebuilding all user accounts and then copy the data back is more efficient. Then re-add the client machine to the domain. Does anyone see any issues with that route?

A

 

[markdmac]

For that little data I agree with you.

Just for the record, ADMT can move the computer accounts over so the SIDS on them can stay the same too. Also, the new ADMT is totally point and click so it is really easy to use.

Still I agree that it is not worth it for this situation.

Make sure you use the web page from SBS2003 to join the computers to the domain.

http://server/connectcomputer

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[dcsnetwiz]

I guess I'm still use to 2000 server where most of the client addition was manual. In my test lab I saw the webpage option to join the client machine to the domain. I tested adding the machine to the domain from the client machine. Is the web GUI the same?

A

 

[dkediger]

I just did this 4 months ago and pretty much went by the process you outlined of manually creating new user accounts and then copying data from the old server to a temporary machine and then up to the new server.

If you can swing it, get a small switch to keep a vestige of the old server/network alive and then physically move the patch cables of the workstations to the new network as you connect them to the new server.

If something doesn't go well, you can very easily get back to your original network while you troubleshoot the glitch.

 

[dcsnetwiz]

THANK YOU ALL FOR REPLYING.... it really helps having feedback such as this. I now have a good idea for this migration and another one that involves more data and more users. Thanks

A