[REQUEST] Migration steps of 2011 SBS to 2016 essentials

urcomputech

Active Member
Reaction score
71
Location
Los Angeles, CA, USA
renderTimingPixel.png

Anyone have a link or advice on how to migrate profiles to a new server. The office in question has 15 users, each assigned a dedicated machine (no roaming). The single server acts as a DC, and serves files, QuickBooks, and ftp for scanning. My main concern is maintaining profiles. That is, user has the same desktop and shortcuts etc after the migration. I've setup new servers from scratch, but have never migrated. Any helpful advice or links would be really appreciated.
 
If the prior server has no folder redirection...when you do a domain "migration" all profiles remain as they were.
If you do have folder redirection, you need to plan your cutover time to move over the folder redirection. Depending on the amount of users, how much data they have in their redirected folders, performance of the old server, performance of the new server. When you edit/update that GPO for telling folder redirection where to go, that first login when the GPO applies will be SLOOOOWWWWW...as the folders are MOVED from old server to new server. Another option is kill the prior GPO for folder redirection...have users reboot workstations a few times to pull them back in to just all local profiles...and then when you start the migration to the new server the new folder redirection applies and folders just get pushed up.
 
Going solely on what you've said here
- ensure that the existing AD is working properly
- add the new server to the existing domain
- transfer the services - DHCP, DNS, printing etc.
- migrate file shares
- transfer QB and other programs.
- transfer FSMO roles
- switch off old server (but leave in situ)

At this point, if anything isn't working switching back on the old server should bring it back up temporarily while you figure out what you forgot. The joy of this method is that it can done without any downtime, if implemented correctly. Well, perhaps a little planned downtime for apps being transferred

An hour spent drawing up a step-by-step detailed checklist will safe you a lot of time during the migration.
 
Going solely on what you've said here
- ensure that the existing AD is working properly
- add the new server to the existing domain
- transfer the services - DHCP, DNS, printing etc.
- migrate file shares
- transfer QB and other programs.
- transfer FSMO roles
- switch off old server (but leave in situ)

At this point, if anything isn't working switching back on the old server should bring it back up temporarily while you figure out what you forgot. The joy of this method is that it can done without any downtime, if implemented correctly. Well, perhaps a little planned downtime for apps being transferred

An hour spent drawing up a step-by-step detailed checklist will safe you a lot of time during the migration.
Thank you for this. The way you explained it seems easily doable ... but alas, the devil is in the details :)
 
If the prior server has no folder redirection...when you do a domain "migration" all profiles remain as they were.
If you do have folder redirection, you need to plan your cutover time to move over the folder redirection. Depending on the amount of users, how much data they have in their redirected folders, performance of the old server, performance of the new server. When you edit/update that GPO for telling folder redirection where to go, that first login when the GPO applies will be SLOOOOWWWWW...as the folders are MOVED from old server to new server. Another option is kill the prior GPO for folder redirection...have users reboot workstations a few times to pull them back in to just all local profiles...and then when you start the migration to the new server the new folder redirection applies and folders just get pushed up.
Thank you for your advice ... no folder redirection or roaming. Each machine is being continuously backed-up via Backblaze.
 
OK so you just have all local profiles....so no biggie here if you do a migration, profiles remain intact.

Now moving onto a different topic, ALL THOSE OTHER STEPS of doing a migration from SBS to 2016 Essen.
SBS has a TON of stuff in there that, "to do a migration right"...needs to be cleaned up
A unique OU structure, and defaults for new computers and new users
A ton of SBS specific GPOs
Lots of SBS-centric DNS entries
And often the prior IT place did a messy upgrade to SBS...so you can have a list of lingering issues in AD to clean up from sloppy prior migrations
Often MS Exchange is still left in active directory....it was not properly uninstalled and removed.

Sometimes, especially if their setup is simple like this one sounds, and not a lot of users, I sometimes just bring in a brand new server with all new active directory and just pull workstation from old domain and put on new domain. Easy enough to move over documents, desktop, pictures, faves, all that easy peasy stuff in user libraries. Since you have O365 email is all easy. Printers..can just deploy via GPO from new server

Moving user profiles...just get the data...cherry pick what's needed. Yeah some users may lose a desktop wallpaper..they can make a new one. Business data is important, person settings..nice if you can get it, but if not..ah well...it wasn't business related in the first place.

There are profile movers like that ForensiIT thing...all that does is repoint the new profile in the registry to the old profile. I've had too many quirks from using that that have bitten me in the arse...so I'll never use those profile movers again. Should have always stuck to my believe of "only move what you need to get". Better off starting with a fresh clean profile, and not bringing over junk and glitches from the old profile.
 
Back
Top