none
How Can You Select and Run a Task Sequences from a non SCCM Win PE Boot Disk?

    Pregunta

  • We have a corporate boot disk which our technicians use for things like secure wipe, debugging, problem solving etc, ghost, creating WIMs etc.

    We also have the SCCM "bootable media", which is completely seperate.

    How can we add everything that is required from the SCCM "bootable media" so that after starting from the current corporate boot disk we can simply run an executable to search for and kick off an SCCM task sequence [it would be TS's for unknown devices obviously]?

    I have seen a post somewhere (cant find it unfortunately) explaining how from within Windows you can put in the optical boot media (or bootable USB drive), run a reg key to alter some SCCM stuff (ccmexec version) and then just run an exe from the boot media which fires up the usual task sequence UI allowing you to choose which TS to run if available.

    Any idea how this could be achieved?

    viernes, 15 de junio de 2012 11:23

Respuestas

  • Hi, maybe you mean this blog post by Michael Petersen?
    http://blog.coretech.dk/mip/start-task-sequence-from-cd-on-configmgr-enabled-pc/

    You can use a similar approach to grab the autorun elements and ts boot media shell etc. the rest is just winpe.
    or you could migrate your current/legacy boot disk toolset so its based on top of cm ts boot media.

    dig around in the osd forum for more tips.


    Don

    viernes, 15 de junio de 2012 12:53
  • (its been quite a while...scratches head...)

    TS boot process will stage the boot WIM into a temp folder something like _SMSTS on the first plain/active partition on the first HDD (?)

    from memory what comes next depends on the steps within the TS chosen, e.g. if there are any FullOS steps before switch into WinPE steps and then back into FullOS steps (for a typical "Deploy" TS)

    we do have the TS boot media bits sitting on a server share, so that XP clients without CM agent can "migrate" to Win7 that way (sort of in-band) or they can PXE as an unknown computer to go to Win7.

    this works fine and the needed logic to persist boot images across restarts just works.


    Don

    sábado, 16 de junio de 2012 0:09
  • Hi, maybe you mean this blog post by Michael Petersen?
    http://blog.coretech.dk/mip/start-task-sequence-from-cd-on-configmgr-enabled-pc/

    You can use a similar approach to grab the autorun elements and ts boot media shell etc. the rest is just winpe.
    or you could migrate your current/legacy boot disk toolset so its based on top of cm ts boot media.

    dig around in the osd forum for more tips.


    Don

    That was the post!  Thanks for that Don.

    My concern at the moment is how/where the UI copies the boot WIM to, in order to start from it next boot.  If it copies it to the RAM disk, then i dont think this will be very useful.

    If you edit the default WIMs on the ConfigMgr Site server and insert your toolkits, you'll be able to get them from pretty much anywhere, PXE or when creating new CD\USB boot media. The F8 prompt in WINPE (debugging mode) will let you launch your tools, you cuold even engineer out this manual step and use the pre-execution hook to get in early and run stuff.

    http://technet.microsoft.com/en-us/library/bb694075.aspx

    sábado, 16 de junio de 2012 12:24

Todas las respuestas

  • Hi, maybe you mean this blog post by Michael Petersen?
    http://blog.coretech.dk/mip/start-task-sequence-from-cd-on-configmgr-enabled-pc/

    You can use a similar approach to grab the autorun elements and ts boot media shell etc. the rest is just winpe.
    or you could migrate your current/legacy boot disk toolset so its based on top of cm ts boot media.

    dig around in the osd forum for more tips.


    Don

    viernes, 15 de junio de 2012 12:53
  • Hi, maybe you mean this blog post by Michael Petersen?
    http://blog.coretech.dk/mip/start-task-sequence-from-cd-on-configmgr-enabled-pc/

    You can use a similar approach to grab the autorun elements and ts boot media shell etc. the rest is just winpe.
    or you could migrate your current/legacy boot disk toolset so its based on top of cm ts boot media.

    dig around in the osd forum for more tips.


    Don

    That was the post!  Thanks for that Don.

    My concern at the moment is how/where the UI copies the boot WIM to, in order to start from it next boot.  If it copies it to the RAM disk, then i dont think this will be very useful.

    viernes, 15 de junio de 2012 13:14
  • (its been quite a while...scratches head...)

    TS boot process will stage the boot WIM into a temp folder something like _SMSTS on the first plain/active partition on the first HDD (?)

    from memory what comes next depends on the steps within the TS chosen, e.g. if there are any FullOS steps before switch into WinPE steps and then back into FullOS steps (for a typical "Deploy" TS)

    we do have the TS boot media bits sitting on a server share, so that XP clients without CM agent can "migrate" to Win7 that way (sort of in-band) or they can PXE as an unknown computer to go to Win7.

    this works fine and the needed logic to persist boot images across restarts just works.


    Don

    sábado, 16 de junio de 2012 0:09
  • Hi, maybe you mean this blog post by Michael Petersen?
    http://blog.coretech.dk/mip/start-task-sequence-from-cd-on-configmgr-enabled-pc/

    You can use a similar approach to grab the autorun elements and ts boot media shell etc. the rest is just winpe.
    or you could migrate your current/legacy boot disk toolset so its based on top of cm ts boot media.

    dig around in the osd forum for more tips.


    Don

    That was the post!  Thanks for that Don.

    My concern at the moment is how/where the UI copies the boot WIM to, in order to start from it next boot.  If it copies it to the RAM disk, then i dont think this will be very useful.

    If you edit the default WIMs on the ConfigMgr Site server and insert your toolkits, you'll be able to get them from pretty much anywhere, PXE or when creating new CD\USB boot media. The F8 prompt in WINPE (debugging mode) will let you launch your tools, you cuold even engineer out this manual step and use the pre-execution hook to get in early and run stuff.

    http://technet.microsoft.com/en-us/library/bb694075.aspx

    sábado, 16 de junio de 2012 12:24