USMT

State Migration Point

Leon Chung

• 2 min read
State Migration Point

Hello! It's been awhile. Doing many things at work now-a-days. Here's something I've been working on in SCCM. We are migrating folks from Windows 7 to Windows 10 (it works with 8 and 8.1 as well), but we have to switch folks to UEFI & Secure Boot & enable TPM for BitLocker encryption. The newer SCCM CB has a tool that allows you to do this without reformatting the drive to UEFI/GPT but we are just going to refresh their install instead since we've been doing this for awhile now.

We are using a State Migration Point (SMP) per site to store user profiles. The User State Migration Tool makes this easy. The hardest part is figuring out how to configure USMT which we won't be covering today. We are going to configure the server you're going to use for storing the user profiles.

These are the guides I used:
https://technet.microsoft.com/en-us/library/bb693655.aspx
https://www.systemcenterdudes.com/how-to-install-sccm-2012-state-migration-point/

  • After a new server is brought online, make sure SCCM Client is installed (and restart when it's done if you manually install it); have your SCCM client grab all available software updates if this is your Windows Update of choice (this will take a while)

  • In Server Management, add Roles & Features:

    • IIS Role in addition to the defaults:
      • Web Server > Security > Windows Authentication
      • Web Server > Application Development > ISAPI Extensions
      • Management Tools > IIS Management Scripts and Tools
      • Management Tools > IIS 6 Management Compatibility > IIS 6 Metabase Compatibility & IIS 6 WMI Compatibility
    • Remote Differential Compression

  • Restart the server

  • Create an empty file called NO_SMS_ON_DRIVE.SMS on the root of the C: drive to prevent SCCM from filling up the OS drive

  • Create a folder on the data drive (Assuming you have 2 drives!) called UserState, I do this so the root of my data drive is a bit more organize. Some of my sites are small enough that my SMP is the same as my Distribution Point.

  • Add new SMP server to Console:

    • Administration > Site Config > Servers and Site System Roles > Create Site System Server
    • Enter the FQDN of your SMP & Site Code, use either your Site Server's computer account or your SCCM service account, either will work.
    • Proxy depends on your infrastructure. Most likely No Proxy needed.
    • Check State Migration Point > Next
    • Click on the "Starburst" icon to configure where the User Profiles should be stored on the server. (i.e.: D:\UserState)
      100MB Reserve and Max client of 50 (or however many connections your server can handle) > OK
    • Depending on the project; Delete After should be configured with a couple days for testing and at least 1 day if the migration fail for any reason. > Next
    • Add Boundary Group (pre-existing ones)

  • Check logs to verify your work: SMSSMPSetup.log and SMPmsi.log on SMP (InstallationDrive\SMS\Logs)

  • Check for a new folder inside UserState that ends in a $

  • Start testing!