upgrade SBS2011 to 2012 Essentials . keeping existing domain

[horsie]

Hi Guys
My apologise if the topic has been covered. I did a search and didn't find anything.

I have a physical SBS2011 box with exchange disabled. (already migrated to 365)
I am building a physical 2012 Essentials box. I want to migrate the new box to be the domain controller of the existing domain so all workstations can remain the same.
there seems to be a wizard during the setup of 2012 Essentials. Has anyone done this ? Can you offer any tips or a procedure
Thanks
Horsie

 

[FremontPC]

Until the server guys get to this thread (I'm not one of them), shoot us some info on what kind of environment you're working on, like how many accounts on the old server, how many workstations and what are they running, number of printers, etc.

You might have a look at this too, as a basic guide:

https://technet.microsoft.com/en-us/library/dn408633.aspx

Likely others will pop in to give you some tips and shortcuts, best luck!

 

[CompConfig]

How many workstations is an important question. Without migrating exchange the process is easier. Are you going to retire the sbs server or are you looking to demote it? It is possible to demote an sbs server but they have a history of not taking demotion too kindly.

 

[YeOldeStonecat]

I've done many SBS (various versions) to Server 2012 migrations, including to Essentials.

Many guides out there, from Microsoft own guides
https://www.google.com/webhp?source...migrate sbs 2011 to server 2012 r2 essentials

http://technet.microsoft.com/en-au/library/dn408633.aspx

https://blogs.technet.microsoft.com...2012-r2-essentials-migration-keys-to-success/

https://blogs.technet.microsoft.com...-in-an-existing-active-directory-environment/

Mariette Knap has a couple of good guides on the migration, as well as removing Exchange 2010.
http://www.server-essentials.com/support/cid/28?category=windows-server-2012-r2-essentials

I recommend you join her forums as a member, and check out her articles.

As you'll notice coming across various articles on migration of existing AD to Server 12 Essentials...that "Essentials Wizard" will pop up on each reboot, since it's basically a DCPROMO by itself, obviously you cannot let it complete running until you have joined the existing AD and swung roles over to it. Simply cancel it on each reboot.

Proper removal of Exchange from AD is important.
Grooming your existing OUs and flushing out old GPOs is important
Catching up on all the Microsoft updates on the Essentials server before you run the promo wizard and do the CONNECT setup client on the workstations is important, one of the updates fixes the error you'd get that the workstation already has a computer account on the domain. (you can also fix that with a registry edit on the workstations before running the Connect wizard, but...why not do it right? Just run all the updates on the server. You do need to run the Connect wizard on all the workstations so they'll show up in the dashboard and certain functions will run (remote connect, backup, etc).

 

[horsie]

Hi Team. thanks for your replies
I mean to retire the SBS server .
I have around 10 workstations running Win7 pro. As i mentioned Exchange is not running on the SBS neither is sharepoint
I just want to migrate AD

 

[horsie]

@YeOldeStonecat
Thanks very much for taking the time to give me those links.
I found the Mariette Knap guide very comprehensive . i have just one question.
I don't really understand what ' FSMO roles ' are. Do i need to migrate them. I always struggle with powershell tutes
Horsie

 

[YeOldeStonecat]

There are 5x important roles in active directory that a domain controller(s) has. As well as making sure the new DC is also a catalog holder.

Those roles are listed here..as well as the ways to transfer them using a GUI method, or done via command line inside of NDTSUtil
https://www.petri.com/transferring_fsmo_roles

Either method (mouse-GUI or command line)...gets the job done fine, use whichever you prefer. It's a job that literally takes just a few minutes.

Side note...SBS gets cranky when it is no longer "top dog". Meaning, holding all those roles and top DC. If it's SBS03...it will start rebooting hourly after...I think a 7 day grace period. SBS08 gave you like two weeks before it starts flipping out. I forget if SBS11 starts doing that. I had a "trick" I'd use to keep SBS03 running forever (do a search for sbs2003 and sbcore if you come across an SBS2003 migration). But basically..just plan your migration so that when you shift these roles, you will complete the migration within a few more days. You can join the new server to the domain and run DCPROMO on it and start shifting over DHCP and DNS duties to it, moving over data/programs/printers, etc. Modifying GPOs. But once you transfer the FSMOs and catalog, that countdown will begin to get everything else off of the old SBS before it starts bouncing hourly. Don't forget to properly remove Exchange from AD, and properly DCPROMO down the old server before putting it in the dumpster.

Another side note, when migrating Server Essentials into an existing domain, once you get the migration done...one of the last steps is letting that Essentials dashboard setup complete. And configuring it..setitng up remote portal, etc. Once the dashboard install completes, the next time you reboot it will likely fail to start. The manual install and migration process messes up the normal setup routine, and you have to go manually change some "log in as" permissions... Simple and quick..just annoying.
https://support.microsoft.com/en-us/kb/2914651

Also, don't forget, early on, when you DCPROMO the Essentials server...once it has the DNS role installed and it's a domain controller, change DHCP so that it hands out the IP of the Essentials server for DNS, instead of the IP of the SBS box. And change static objects on the network too, to point to it (printers, MFPs, etc).

 

[CompConfig]

What Ye Old just wrote is certainly 100% correct and the only way to go if you have 30+ computers, printers, users. I find it faster and easier with only 10 computers doing the new server from scratch setting up everything myself using the same settings as the old server. Then copy the data, kill the old machine put the new one in, restart the workstations and don't look back. I do this especially if we didn't setup the old server and we are replacing another company the client considered to be dropping the ball. You never know how that old company did things and you would hate to have old bad habits copied over to the new machine.

Just another way to go but everything you were told is correct and you do whatever you prefer

 

[YeOldeStonecat]

I have had a couple of messy ones where I opted to create all new from scratch. Even on small ones though, if I can...I prefer to migrate. This allows me to control the pace, and I can spread it out over a couple of evenings, transparent to end users. Move data at night modify login scripts...bounce workstations so end users log in in the morning and nothing changed from their perspective. No interruption.

Doing a whole rip 'n replace...you're stuck onsite til it's all done. Often an overnight haul, onsite. And then deal with users "where's my wallpaper of my grandaughter or dog?" or some funky oddball thing that didn't come over with a profile copy.

 

[horsie]

Thanks CompConfig
One of the reasons i wanted to try the migration method is to practice for a bigger job i have looming
Also i figured it would be much easier to get the permissions for the different file shares correct if we use the existing domain
I have a day to decide as the new server is delivered tonight

 

[YeOldeStonecat]

Built an Essentials server today to deliver Friday....
man...those Microsoft updates just never end on Essentials.....usually a pretty big first round, reboot, then a single large update, reboot...and the a couple of hundred more updates...but often takes two sniffs to catch this 3rd large round.

Client I'm building it for is a design fabrication shop, so they run Solidworks. Been just a workgroup environment, on a Synology NAS..and been on O365 E3 plan for a while.

 

[knc]

I'm really shocked why no one writes an application to do these migrations. Apparently because it must not be possible, but they can put a man on the moon! ha..

 

[YeOldeStonecat]

Too many variables and things you need to control uniquely, per case.
There are a few "swing it" migration kits you can dig up out there.

 

[marley1]

At ten computers I'd just start fresh.

 

[RoadRunner]

I have the do a SBS 2011 to 2012 essentials as well. Will just create a new domain and use migrationwiz (EDIT: Profile Wizard ) to keep profile and join to new domain. This keeps user profiles and only takes a minute per machine. Client has around 10 workstations. Will do PST export and import to O365. Their mailboxes are not large.

 

[marley1]

Remember to run the connect wizard

 

[RoadRunner]

Can you still run that after you joined the domain through migrationwiz (EDIT): ProfileWizard)

 

[marley1]

Migration wiz is for mail migration when you do a domain migration to essential the computers will not show up in the management console.

Just run the connect wizard on the machines and log in with the domain admin

But honestly for 10 machines I'd rebuild the domain

I'd also not use the wizards essentials

 

[RoadRunner]

Sorry meant ProfileWizard from Forensit.