My Documents) is not migrated via the wizard although it tries. If your users expect that the server is 'just there', you may need to do some hand holding to get everything working after the first login. Some of your apps will migrate but not all. When you migrate clients, you are creating brand-new domain accounts (your users were probably using machine accounts before).Good time to write a CMD file to automate this! You will need to copy each shared folder individually. In my tests, robocopy was faster than copying from a USB 2 external drive (which was my original plan for migration). This gives you a way to migrate data - doĪ Robocopy from old to new through the first client you connect. You will lose access to the dashboard but you still have access to shared folders via the UNC. Before you connect PCs to the new server you have to uninstalkl the old Client Connector software.You will need to set up folders for things like MUSIC, PHOTOS, etc. The shared folders you're used to are not set up by default.My kids had presentations to finish for school. Ouch! Recoverable, but I would have hated to have this happen when my wife was working on her business and After a mandatory restart my WSE box no longer boots - bad partition table. In particular, the add-ins seem to be kind of glitchy still.įor example, I just installed the cloud storage add-in. You will want to get your WSE stable before starting a migration of real users.

There are still a few glitches in the wizards and installation software. Some things that you should put in your plan: I'm in the middle of a fairly sunstantial WHS2011->WSE2012 migration (4 users, 2.5 TB of data) right now.

Windows home server 2011 product key