barnesm6
asked on
Migrate AD to new server
I need to replace a clients server - too be honest it's a desktop PC with SBS2003. They've had nothing but trouble with it and we're now going to replace it with a HP Proliant ML310. This is going to be totally different hardware so it's a completely new install. I would like to try and set the new server up keeping the existing user and computer accounts as I would rather not have to go around each PC to rejoin the domain.
I'm sure I can find this out from Microsoft's site but I'd like some real life experiences of what to look out for and how best to migrate AD to the new server.
Some users and using offline folders and others have folder redirection etc and I'm hoping to retain all this by migrating AD.
Cheers
Mike
I'm sure I can find this out from Microsoft's site but I'd like some real life experiences of what to look out for and how best to migrate AD to the new server.
Some users and using offline folders and others have folder redirection etc and I'm hoping to retain all this by migrating AD.
Cheers
Mike
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No, don't do what "someone" has suggested... a bad idea because the workstations will never be correctly part of your "SBS" network. Remember, SBS has a lot of useful tools that will only work if you configure your network properly.
In most cases, unjoining the workstations and then rejoining them would allow you to still use the user's profile as long as you use the same usernames. But just in case, there is a plan B... so when you are ready to switch over, here are the steps:
1. Use the Files and Settings Transfer Wizard to back up the user's profile. The backup can just be done to the C: drive of that workstation.
2. Unjoin the workstations from the current domain
3. Delete the C:\Program Files\Micrososft Small Business Server\Clients folder
4. Make sure that DHCP is enabled (Get IP Address Automatically)
5. Reboot
6. Log in with the workstation's BUILTIN administrator account
7. Use the http://servername/connectcomputer wizard to rejoin the network.
8. Select the correct user to assign to the computer and have connectcomputer migrate the profile.
9. If you aren't given the option to migrate the profile, select NONE and then restore it with the Files and Settings Transfer Wizard.
That should be all you need!
Jeff
TechSoEasy
In most cases, unjoining the workstations and then rejoining them would allow you to still use the user's profile as long as you use the same usernames. But just in case, there is a plan B... so when you are ready to switch over, here are the steps:
1. Use the Files and Settings Transfer Wizard to back up the user's profile. The backup can just be done to the C: drive of that workstation.
2. Unjoin the workstations from the current domain
3. Delete the C:\Program Files\Micrososft Small Business Server\Clients folder
4. Make sure that DHCP is enabled (Get IP Address Automatically)
5. Reboot
6. Log in with the workstation's BUILTIN administrator account
7. Use the http://servername/connectcomputer wizard to rejoin the network.
8. Select the correct user to assign to the computer and have connectcomputer migrate the profile.
9. If you aren't given the option to migrate the profile, select NONE and then restore it with the Files and Settings Transfer Wizard.
That should be all you need!
Jeff
TechSoEasy
ASKER
Thanks for the speedy response Jeff. Nice step by step guide and all sounds so obvious when it's presented like that.
Anyway, replacing the server tomorrow so I'll let you know how it goes.
Anyway, replacing the server tomorrow so I'll let you know how it goes.
ASKER
I've been reading up on the FSTW and from what I can see it will backup outlook express settings but I see no mention of outlook settings or mail store (my clients are using local pop3 accounts in Outlook). However, I see that you can select additional folders to back up which means I could backup the pst file but it still doesn't help with having to recreate the users account in outlook later.
I have also been looking at the User state migration tool and this migrates outlook and oe settings and mail stores. Would you agree that I would be better off using this tool instead?
I have also been looking at the User state migration tool and this migrates outlook and oe settings and mail stores. Would you agree that I would be better off using this tool instead?
You don't need to worry about Outlook settings... because you don't want to restore those. You want your NEW SBS to handle the Outlook configuration... and move them off of individual POP3 accounts to having the SBS's Exchange POP3 Connector download their mail. Using the POP3 Connector will allow users to access their email remotely via Outlook Web Access and it will allow you to back it up centrally on the server as well as provide virus protection at the server level.
USMT is not necessary here because again... you want SBS to do it's stuff. If you had individual POP3 accounts before, you didn't have a very well deployed network... spend more of your time reading up on SBS Best Practices and you'll be much happier with this. :-)
A good source: http://sbsurl.com/techguide
And good books: http://sbsurl.com/best http://sbsurl.com/unleashed
Jeff
TechSoEasy
USMT is not necessary here because again... you want SBS to do it's stuff. If you had individual POP3 accounts before, you didn't have a very well deployed network... spend more of your time reading up on SBS Best Practices and you'll be much happier with this. :-)
A good source: http://sbsurl.com/techguide
And good books: http://sbsurl.com/best http://sbsurl.com/unleashed
Jeff
TechSoEasy
ASKER
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