locked
Is it possible to capture a .MIG file locally with SCCM (not talking hard-links)? RRS feed

  • Question

  • Hey guys,

    I've got about 400 new machines I need to deploy to multiple offices across the country. These machines will replace existing hardware. What we'd like to do is use SCCM to silently run USMT on the older machines we plan to replace and we want this to run prior to our site visit. Once its complete we can show up at the site, copy the .MIG file to the replacement computer, restore it there (using an HTA I wrote that runs LoadState.exe) and collect the old hardware for recycling.

    Most of the SCCM-based USMT guides I've seen online focus on either hard-link migrations (where you are also deploying a new image to the device in question) or capturing the .MIG file to a network share. We need to .MIG file captured to the locak C:\ drive of the target machine and that's it (no OS upgrade needed). Is this possible with SCCM and (if so) is anyone aware of a guide or can offer tips on how to do this?

    Thursday, January 26, 2017 5:19 PM

Answers

  • Yes. It's really no different than using a UNC. You just specify a local location for the OSDStateStorePath task sequence variable. For reference, see https://technet.microsoft.com/en-us/library/hh273365.aspx.

    There are caveats here if using a refresh task sequence but it doesn't look like that's what you're doing so I won't mention them.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by ZeusABJ Thursday, January 26, 2017 7:37 PM
    Thursday, January 26, 2017 6:23 PM

All replies

  • Yes. It's really no different than using a UNC. You just specify a local location for the OSDStateStorePath task sequence variable. For reference, see https://technet.microsoft.com/en-us/library/hh273365.aspx.

    There are caveats here if using a refresh task sequence but it doesn't look like that's what you're doing so I won't mention them.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by ZeusABJ Thursday, January 26, 2017 7:37 PM
    Thursday, January 26, 2017 6:23 PM
  • Yes. It's really no different than using a UNC. You just specify a local location for the OSDStateStorePath task sequence variable. For reference, see https://technet.microsoft.com/en-us/library/hh273365.aspx.

    There are caveats here if using a refresh task sequence but it doesn't look like that's what you're doing so I won't mention them.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    I am not in this case. Thank you Jason. 
    Thursday, January 26, 2017 7:37 PM
  • Hey Sorry one more question, can I do something like:

    OSDStateStorePath = %SYSTEMDRIVE%\%COMPUTERNAME%

    And will it be "intelligent"enough to create the structure for me or should I precede it with a "MKDIR" command? Also are the following items "enough" for this to work or do I need more stuff in my task sequence?


    Thursday, January 26, 2017 7:46 PM
  • The TS is sufficient, yes.

    Not sure on the value of the variable though. I would hope using environment variables works but I don't know off hand. Should be easy enough to test though.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, January 26, 2017 7:49 PM
  • Yeah that's just semantics. I was just hoping you might already know the answer. If its one thing I've learned about SCCM its "test, test, test" until you figure it out.

    Thanks Jason!


    • Edited by ZeusABJ Thursday, January 26, 2017 9:44 PM
    Thursday, January 26, 2017 9:44 PM
  • Just a follow-up, thanks again Jason. I was able to get this working.

    Thumbs up!

    Thursday, February 2, 2017 2:58 PM