"Set Task Sequence Variable" task in OSD: Can this be used to prompt for computer name?


  • Can you prompt the user for a computer named using the OSDcomputerName variable in a task sequence using the "Set Task Sequence Variable" step? The technet article here ( indicates you can:

    "Alternatively, you can use the Set Task Sequence Variable action or the TSEnvironment COM object to set the variables at runtime."

    When I add this step and set the variable to "OSDcomputerName" during my OSD task sequence it just skips the step. If this is not possible, what is this step for?

    Also, some background on why I am interested in this. We want users when PXE booting and running non-required OS deployments to always be prompted for a name, in case the machine is repurposed. I added the collection variable OSDcomputerName to both Unknown Computers as well as All Desktop and Servers collections, but it pops up even when running a required OSD. I was under the impression it should not appear when the OSD is mandatory but I did not find that to be the case.
    • Edited by BryanCP Thursday, April 26, 2012 7:17 PM
    Thursday, April 26, 2012 7:00 PM


All replies

  • The Set Task Sequence Variable task provides no UI or interactivity, it just sets the variable's value.

    A very simple technique is built in though: (although for 2007, this is applicable to 2012).

    If you want something more full featured, you can use an HTA or this:

    UDI and MDT both have built-in functionality for this also when extending OSD.

    Jason | | Twitter @JasonSandys

    Thursday, April 26, 2012 8:21 PM
  • Thanks for the info.

    Am I correct that if you set the variable on the collection and make the OSD required, it should not prompt for the name during the imaging process?

    • Edited by BryanCP Friday, April 27, 2012 11:33 AM
    Friday, April 27, 2012 11:32 AM
  • And one more: I am going to use OSD++. We are outputting two task sequence variables (OSDComputerName and OSDDomainOUName). Do these overwrite or take precedence over provided answer files in the TS?
    Friday, April 27, 2012 12:39 PM
  • Honestly, not sure -- I never use required TS adverts -- too much risk of wiping out things. Should be easy to test though.

    Jason | | Twitter @JasonSandys

    Friday, April 27, 2012 3:10 PM
  • Correct. (In general) Anything set during the running of the TS (run-time configuration) trumps anything set during the build process (design-time configuration) because it comes after the design.

    Jason | | Twitter @JasonSandys

    Friday, April 27, 2012 3:12 PM
  • Thanks Jason.

    OSD++ is working great for the computer name but I am having issues with passing the OSDDomainOUName variable when created by it. I'll be testing that some more to see if it works. Even though I am using it to specify the OU, it's still using the data in the Answer file.


    • Edited by BryanCP Friday, April 27, 2012 7:18 PM
    Friday, April 27, 2012 7:16 PM
  • Another way to do this, that I find easier than Jason's linked solutions, is to set a Collection Variable to the collection the target computer is in. In my case, the Unknown Computer collection. This solution also applies to both 2007 and 2012.

    The dots are created even though when I created a variable, I left the field blank.

    Monday, April 30, 2012 12:25 PM
  • The unknown collection variable did not work for us because we want all "on demand" deployments via manual PXE boot to prompt for a password. This would be for machines that are known as well an unknown in case they are repurposed. Thanks for sharing that though.

    I am now knee deep in using MDT 2012 and a User Driven install via PXE. This seems like the best solution and exactly what we need.

    • Edited by BryanCP Monday, April 30, 2012 7:03 PM calrification
    Monday, April 30, 2012 7:02 PM
  • it is the same resolution proposed by Jason :)

    Monday, May 29, 2017 7:53 AM