OK they've only got 6-7 users so I think it might be simpler just to recreate the accounts and start again. My only concern is reconnecting the computers/users to the new server.
I've set the new server up with the same domain, name etc. When I remove the old server and connect this one how would you suggest connecting the clients to the new server? I've previously come a cropper when disjoining a computer from the domain and then rejoining - disjoining removed the users profile from the client pc along with all of their data.
Someone has suggested that simply removing the .local from the end of the domain when connecting the old fashioned way will work but I attempted this on a test system and it didn't work for me.
Cheers
Mike
Main Topics
Browse All Topics





by: TechSoEasyPosted on 2006-09-12 at 17:18:58ID: 17508056
You have four options:
). This will require that you create a new domain name as part of the transition.
), and files can be moved using a USB Hard drive, or just copy the files to a drive on one of the workstations so you can copy them back to the new server.
m/pdf/rg/ a tis9.1_rg. en.pdf#sea rch=%22par agon%20dri ve%20backu p%20restor e%20to%20d ifferent%2 0hardware% 22
are
1. Use Microsoft's migration method (http://sbsurl.com/migrate
2. Migrate Manually. ie, set up the new server and re-add all of the users manually. If there are less than 10 users or so, this isn't a bad idea... especially if there are wrong configurations to begin with. You would use EXMerge to migrate the mailboxes (http://sbsurl.com/exmerge
3. Backup with Acronis True Image Server 9.0 with Universal Restore and then restore to your new server.
http://download.acronis.co
A pricey option, but it works beautifully.
4. www.sbsmigration.com The SBS Professional's Community choice for this type of migration. (my choice as well) The benefits of the Swing Migration method that SBSMigration will provide the documentation for are tremendous... you can perform the migration at your own pace. There is now downtime on the network, no late nights thrying to make sure things are working before everyone gets in at 8:00am, complete roll-back, wrap-around documentation that will be able to stay with the network, etc, etc.
I've used all four options and really like the Swing Migration the best. The only time I don't do this is for situations as stated in Option #2.
Jeff
TechSoEasy
***UPDATED 11/16/2007 by TechSoEasy -- EE's Microsoft Zone Advisor***
There is a newly published document for migrating SBS 2003 to new hardware: http://sbsurl.com/newhardw
Be aware though, that if your original SBS is an OEM license you need to buy a new license for the new machine.