locked
SCCM Replace method migration for XP-to-W7 without creating computer associations? RRS feed

  • Question

  • Hi all

    We want to use the Replace Method for our XP-W7 migration but do we have to create a computer association between the old and new machine name for every machine to be migrated (2500+)? If so, this does not appear to be practical because we don’t know what the new machine name will be for every old machine to be migrated until we image machines with Windows 7, which is likely to be on the same day.


    So, how can we use the Replace Method without creating computer associations please?

    Best regards
    Scott

    Monday, January 13, 2014 11:48 AM

Answers

  • That's good to know, thanks Jason. We're hoping to keep the solution as simple as possible and also looking at using UDI during the replace scenario...
    • Marked as answer by Joyce L Tuesday, January 21, 2014 10:05 AM
    Monday, January 13, 2014 7:27 PM

All replies

  • take a look at the OSD HTA Bitlocker HTA. It allows you to backup/restore using an HTA - http://www.windows-noob.com/forums/index.php?/topic/7294-the-cm12-bitlocker-frontend-hta/

    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund | Mastering ConfigMgr 2012 The Fundamentals

    • Proposed as answer by DanielRatliff Tuesday, January 14, 2014 4:43 PM
    Monday, January 13, 2014 12:17 PM
  • Thanks Kent. This HTA seems to be a very advanced solution, especially as we are new to SCCM. Is it supported by Microsoft if we need help or is it "use at your own risk"

    Kind regards
    Scott

    Monday, January 13, 2014 1:53 PM
  • I'ts not directly supported by Microsoft no; however, it's not doing anything unsupported. It merely sets a series of task variables and/or extends functionality per the SDK. It's like writing a script to automate anything: the script itself isn't explicitly support but everything it does is.

    Jason | http://blog.configmgrftw.com

    Monday, January 13, 2014 3:31 PM
  • That's good to know, thanks Jason. We're hoping to keep the solution as simple as possible and also looking at using UDI during the replace scenario...
    • Marked as answer by Joyce L Tuesday, January 21, 2014 10:05 AM
    Monday, January 13, 2014 7:27 PM
  • MDT 2012 SP1 is integrated with ConfigMgr 2012.
    We are testing a UDI solution, however, when we click “Preview” on the Refresh stage group we get the error “Unable to launch wizard in preview mode – OSDSetupWizard.exe was not found in the expected path”.  This is preventing us from checking that the changes we have made to the capture/restore settings will work or not. This error does not occur when we "Preview" the NewComputer stage group and we have checked OSDSetupWizard.exe does exist in \\<server>\MDT Toolkit\Tools\x64 and \\<server>\MDT Toolkit\Tools\x86.

    1. How do we overcome this error to allow us to preview the Refresh stage group please?

    2. Do we need to specify the DEPLOYMENTTYPE variable in the customsettings.ini and if so, do we need 3 different customsettings.ini files for each scenario (DEPLOYMENTTYPE=NewComputer, DEPLOYMENTTYPE=Refresh and DEPLOYMENTTYPE=Replace)?

    Kind regards
    Scott


    • Edited by mr5h Friday, January 17, 2014 12:58 AM
    Friday, January 17, 2014 12:33 AM
  • Check if you have the same config file opened for editing on another computer.

    Regards.

    Yuriy

     
    Friday, March 20, 2015 10:19 PM