Have you heard about Virtual SMP? SCCM/ConfigMgr 2012 SMP helps to store and restore the user state data. Users state data is very critical during Operating System migrations. When you’ve loads of branch or agency offices with very slow WAN link then OS migrations are always a challenge. Copying gigs of user data over WAN not a feasible solution. We can also have offline capture and use USB drives etc. More administration is required for these kind of solutions.
Adaptiva Onesite Virtual State Migration Point (Virtual SMP) resolves most of your concerns/worries about user state data during Operating System migrations. Onesite virtual SMP configurations can be done via Task Sequence editor once you’ve integrated SCCM /ConfigMgr 2012 with Onesite. Virtual SMP uses unallocated space to user state data during the OS migrations. More details about Adaptiva Helps Enterprises Streamline Operating System Migration From XP With OneSite Rapid OSD here.
Following are the options within Adaptiva OneSite Virtual SMP
Create State Store
Pin State Store
Replicate State Store
Trim State Store
Find State Store
Delete State Store
Is Machine A Host
Wait Until Not A Host
SCCM / ConfigMgr 2012 SMP has some limitations:- If you’re NOT yet upgraded to R2. All site system roles at a secondary site must be located on the site server computer except DP. So we can’t install SMP on a remote site system computer via secondary site. If you’are already upgraded to SCCM / ConfigMgr 2012 R2 then Secondary sites support installing State Migration point (SMP) on the secondary site server, on remote site System computer and also it can co-located with DP.
How does a client select SMP ? Random selection if you’ve more than one SMP in your boundary group. When a client looks for SMP, it create a location request similar to that of a DP location request (boundary based). Once the client gets the list of SMPs, it will “randomly” pick one from the list. So it won’t follow the selection criteria of DP.