Jump to content


Sign in to follow this  
Steve G.

How Does Large-Scale Data Migration Work with SCCM 2012?

Recommended Posts

Here's what the scenario:

  • Potentially hundreds of computers to replace.
  • A couple dozen PC technicians.
  • One (1) SCCM administrator.
  • Management insists that data be backed up prior to OS deployment in the event of catastrophic failure during occurring during said deployment.

In Config Manager 2007, this was simple enough to handle. We had a handy-dandy task sequence that mapped a drive to a network share, and then ran the backup to that location, with a little variable that named the file after the source computer. If anyone ever needed data restored, they could just fire up Windows Easy Transfer and look for that file. Sure, we did hard-linking and in-place backups and restores, but it was definitely helpful to simply have the data sitting on mass storage and accessible to people who weren't SCCM admins.

 

In Config Manager 2012, however, a USMT task sequence fails with an error that indicates it doesn't allow backups to mapped drives.

 

Now, everything I've read about state migration points seems to rely creating manual one-to-one relationships between the source and destination computers, which doesn't seem practical with large scale deployments. It also seems to necessitate using SCCM to perform all restores, so a PC technician can't just snag the backup and restore it.

 

Has anyone had to face such a scenario? Are there any good guides for USMT to facilitate an en-masse PC-replacement?

Share this post


Link to post
Share on other sites


the task sequence below backs up data just fine to mapped shares

 

Share this post


Link to post
Share on other sites

Thanks for the response. It's interesting that there's no error capturing a user state directly to network storage, since both USMT 4 and 5 have not been able to do so in our environment. When we opened a ticket with MS, they said this was intended behavior.

Share this post


Link to post
Share on other sites

I attempted to import the task sequence, however even with ignoring the dependency, the import failed with an error:

 

Error: Imported Task Sequence Package (1):

Ignore Dependency CM12 UEFI BitLocker HTA

Not found

instance of __ExtendedStatus{ Description = "Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence."; Operation = "ExecMethod"; ParameterInfo = "SMS_TaskSequence"; ProviderName = "WinMgmt"; StatusCode = 2147749890;

Share this post


Link to post
Share on other sites

do you have mdt 2013 integrated ?

Share this post


Link to post
Share on other sites

I don't have MDT, MBAM, or the Maik Kosters web service.



I can go install all the stuff, but can you help me appreciate how MDT will address what seems to be a USMT limitation?



The TS is pretty simple. It doesn't boot to any kind of PE. One task creates a TS variable OSDStateStorePath, and has a value that points to the mapped drive. The Capture User State task that follows it is perfectly vanilla.

Share this post


Link to post
Share on other sites

from your error message "Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence.":

 

that's complaining about the lack of MDT Integration. This integration gives a lot more abilities that you think and it all collectively helps the task sequence mentioned above into a reality, (via the scripts etc), try it and see.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...