Download and own this SCCM Installation Guide in a single PDF file.

The PDF file is a 162 pages document that contains all informations to install and configure SCCM Current Branch. Use our products page or use the button below to download it .


Icon Info

This blog post has been updated. Please refer to the new SCCM Current Branch Installation Guide.

In this part of SCCM 2012 and SCCM 1511 blog series, we will describe how to install SCCM 2012 R2 or SCCM 1511 State Migration Point (SMP).

Role Description

The State Migration Point stores user state data when a computer is migrated to a new operating system.

This is not a mandatory Site System but you need a State Migration Point if you plan to use the User State steps in your Task Sequence. These steps integrates with User State Migration Tools (USMT) to backup your user data before applying a new operating system to a computer.

sccm 2012 state migration pointsccm 2012 state migration point

Site System Role Placement in Hierarchy

The State Migration Point is a site-wide option. It’s supported to install this role on a child Primary Site, stand-alone Primary Site or Seconday Site. It’s not supported to install it on a Central Administration site.

Beginning with SCCM 2012 R2, the State Migration Point can be installed on the site server computer or on a remote computer. It can be co-located on a server that have the distribution point role.

SCCM 2012 State Migration Point Installation

  • Open the SCCM console
  • Navigate to Administration / Site Configuration / Servers and Site System Roles
  • Right click your Site System and click Add Site System Roles
  • On the General tab, click Next

sccm 2012 install fallback status point

  • On the Proxy tab, click Next

sccm 2012 install fallback status point

  • On the Site System Role tab, select State Migration Point, click Next

sccm 2012 state migration point

  • On the State Migration Point tab
    • Click the star icon, specify the folder where you want the data to be stored and how much space must be reserved on the drive
    • Specify the Deletion Policy. This is the delay to keep the data after a successful restore.
    • Enable Restore-Only mode if needed. Use this setting if you want your SMP to be in read-only mode. This is useful if you replace or decommission an existing SMP

sccm 2012 state migration point sccm 2012 state migration point

  • On the Boundary Groups tab, add the boundary group that can access the State migration Point. If you add the role on a site system that already has the Distribution Point role, the boundary group of this DP will already be listed

sccm 2012 state migration point

  • On the Summary tab, review your settings, click Next and complete the wizard

sccm 2012 state migration point

Verification and Logs files

You can verify the installation in the following logs:

  • ConfigMgrInstallationPath\Logs\Smssmpsetup.log – Detailed State Migration Point Installation status
  • ConfigMgrInstallationPath\Logs\Smpmsi.log – Provides information about the State Migration Point

If you have any error in the installation process refer to this post that explains the permission needed for the SMP to install correctly.

Create the USMT Package

To store the user state data on a State Migration Point, you must create a package that contains the USMT source files. This package is specified when you add the Capture User State step to your task sequence.

sccm 2012 state migration point

  • On your SCCM Server where you installed Windows Deployment Toolkit, browse to : C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\User State Migration Tool
    • If you don’t have this folder, it’s because you haven’t installed the USMT (included in Windows ADK) during your SCCM Installation
  • Copy the folder content in your Content Library (In my example D:\Sources\OSD\USMT)

sccm 2012 state migration point

  • Open the SCCM Console
  • Go to Software Library / Application Management / Packages
  • Right-click Packages and select Create a new package
  • Enter the Name, Manufacturer, Language
  • Check the This package contains source files check-box and specify your source folder (D:\Sources\OSD\USMT)
  • Click Next

sccm 2012 state migration point

  • On the Program Type tab, select Do not create a program and click Next

sccm 2012 state migration point

  • Complete the Create Package wizard

The State Migration Point and the USMT package are now ready for use in an OSD Task Sequence using the Capture User State and Restore User State steps.

Comments (11)


03.19.2018 AT 07:57 AM
How do I specify a large SCCM 2012 R2 environment to use only one SMP? Can I add just the SMP without having to create a DP, or can I add the existing group boundaries to the SMP without affecting how updates, and software pushes are delivered to the clients?

Kurt Johnson

02.06.2018 AT 08:23 AM
I am performing a migration of SCCM 1607 from one domain to another. The migration is going well. One of the last things I am doing is creating a USMT SMP from scratch (nothing to migrate from old environment, really). I have the SMP installed successfully but am not able to capture profiles, nor even scan the current state of the store at \\\. Question: I pre-installed IIS pre-requisites and notice that in your instructions above, you did not. I am now getting website\IIS errors. SMP uses IIS, obviously, but should I have left IIS configuration up to the installer? Any help you might have would be great... thanks.

Thomas Christian

08.11.2017 AT 08:53 AM
Hi Benoit, I Have two SMP and two site. In SCCM I create 2 boundaries, 1 for each site. I create 2 boundaries groups 1 for each site and I configure each SMP to use a boundary of each site. I have one DP who have role SMP to. When I try to use SMP on the second site. This is SMP who on my First site who save my profil(s). Sorry for my English. Thank you Christian


03.27.2017 AT 03:24 AM
how to use usmt to scane and restore the other partitions (d, e, f,.....)


03.27.2017 AT 03:22 AM
How to use usmt to scan the d, f, g partitions

Amador Gomez

01.26.2017 AT 11:36 AM
How does the task know which DP to use to upload the capture to? I try a test and the package was capture on the local c: drive and not on the DP assigned to the site.


11.05.2016 AT 06:44 AM
why we need to create USTM package although it is already in the sccm 2012 r2 cu3 package list??

Benoit Lecours

11.08.2016 AT 05:01 PM
No need to create it if it's already there.


02.02.2016 AT 12:24 AM
But aren't we using the MIGuser and the Migapp xml files when we are only to use one? My scan states are taking forever and I cannot find any info on this.