Jump to content

Search the Community

Showing results for tags 'State Migration Point'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 3 results

  1. Greetings, Wonderfully helpful forum, I'm learning a ton reading through all the post, thank you for creating this site! I'm having a problem with a site server starting the State Migration Point component. I have a primary site server and 2 site servers that should be configured exactly the same. One site server doesn't have any problems with the SMP component starting but the other one does. In the SMPMGR.log file I see; HandleSMPRegistryChanges failed. error (0x80070002). $$<SMS_STATE_MIGRATION_POINT><05-08-2013 10:24:30.338+300><thread=1484 (0x5CC)> SMPManager failed to start, Error = (0x80070002). $$<SMS_STATE_MIGRATION_POINT><05-08-2013 10:24:30.338+300><thread=1484 (0x5CC)> I've searched for those two error messages but haven't been able to find anything related to my problem. TIA!
  2. I'm trying to capture data from one PC and run a new TS to build Win7 with SOE and then restore the USMT.mig from the SMP to the new PC. I have successfully completed USMT by hardlinks and that works great, but I just can't seem to get USMT via SMP to work. I am using the MigDocs.xml, MigApp.xml, and MigUser.xml files to specify the capture data and it captures successfully on the SMP. I then have a separate TS to build a new OS, install apps, and then the last step to Request State Store, Restore User State, then Release User State. The TS completed but the User Sate hasn't been restored. It's not a permissions issue as I have created a test custom.xml capture file to only capture a single directory and it restores fine (Capture C:\Test\*.* and that directory restores fine). But when trying to restore a full user state capture (~30Gb) it won't restore. I don't want local profiles to restore so I haven't specified this in my TS. I have attached the loadstate.log for more information. loadstate.log
  3. I am trying to change the location of where the user data gets stored on the server. The SCCM server does not have enough space to handle all the computers that we will be upgrading. Currently we have the SMP pointed to a local hard drive in the SCCM server and would like to point it to a USB drive that is plugged into the server. The issue we are having is that we had originally pointed the storage location to a mounted folder (mounted by mslink) on a different server. It would not work doing it this way so we are going to just use a USB drive. When I change the location to point to the USB drive it doesn't store anything there. It will try and store it on the mounted folder even though it is no longer mounted. It ends up creating a local folder and pointing there. Nowhere in the ConfigMgr state migration point do we have it pointing to the old location....only the new USB HDD location. How do we get the server to "forget" the old location and only store on the USB HDD? A side note....The server will actually create a SMPSTORE%_%%%% folder on the USB HDD, but still won't push any data there. Making changes here...SCCM > Site Database > Site Management > [site] > Site Settings > Site Systems > [site Server] > and right click on ConfigMgr State Migration Point
  • Create New...