Prompt for location - Task Sequence Variable RRS feed

  • Question

  • I am wondering if it is possible to have a task sequence pop up asking for user input on their current location.

    I am trying to create a task sequence that will prompt the user where the computer is going to be deployed to, so it will put the computer in the correct OU and such by using seperate Network Settings based on the users input. I would like it to have a list of options the user can choose from.

    I am not running MDT.

    • Edited by CamecoKev Wednesday, June 4, 2014 2:14 PM
    Wednesday, June 4, 2014 2:06 PM


All replies

  • Why not using MDT? Why do you want to re-invent the wheel?

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, June 4, 2014 2:32 PM
  • I am just checking to see if there is a way to do it out of the box, I have never used MDT and there is quite a bit of a learning curve surrounding it. I also don't know if MDT will do what I am looking to do either.

    I can use wmi query to use Subnets to sort out which network settings to use, but that is also quite a bit of work.

    Wednesday, June 4, 2014 2:36 PM
  • Certainly there are other ways to do what you want.

    You would need to do the following:

    • Create a HTA in Powersshell or VB that prompts the user for a location
    • The HTA will include code that will "translate" the users input into a Task Sequence variable (OSDDomainOUName)
    • You then leave the domain OU field blank in the Apply Network Settings step in your Task Sequence and it will get the value from the OSDDomainOUName (User input)

    You need to create the HTA and logic yourself so it might be easier using MDT but it really depends.

    Wednesday, June 4, 2014 3:03 PM
  • A very simply, out of the box way is to use blank task sequence variables: http://blog.configmgrftw.com/blank-task-sequence-variables/

    Jason | http://blog.configmgrftw.com

    Wednesday, June 4, 2014 3:21 PM
  • I've not used UDI that much myself, but why not take a look at it. It's really worth while to start learning MDT, it will only benefit you in the long run, trust me!

    But creating your own PowerShell front end isn't really that hard (assuming you've worked a little bit with PowerShell before).

    Here's a great guide on UDI:



    Nickolaj Andersen | www.scconfigmgr.com | @Nickolaja

    Wednesday, June 4, 2014 3:25 PM
  • I have an empty variable for OSDComputerName and it works well.

    But for this I would like to have a list presented to the user where they can select between preset values.

    Wednesday, June 4, 2014 3:33 PM
  • I have started a Change ticket to get MDT installed on my MP
    Wednesday, June 4, 2014 3:33 PM
  • If you contact me through an email or twitter, I can code it together for you if you'd like.


    Nickolaj Andersen | www.scconfigmgr.com | @Nickolaja

    Wednesday, June 4, 2014 3:44 PM
  • Then you'll have to use MDT, UDI, or something custom. You can also use OSD++: http://blog.configmgrftw.com/osd/

    Jason | http://blog.configmgrftw.com

    Wednesday, June 4, 2014 4:02 PM
  • MDT has nothing to do with your MP. You need to integrate MDT with your site which typically involves installing it on your site server *and* on any consoles where you are creating MDT integrated task sequences.

    Jason | http://blog.configmgrftw.com

    Wednesday, June 4, 2014 4:03 PM
  • I've now emailed CamoKev the script that I put together with a few modifications to the one that I posted here:


    Thought that someone else also wanted to know how I did it, sharing is caring :)


    Nickolaj Andersen | www.scconfigmgr.com | @Nickolaja

    Friday, June 6, 2014 5:20 PM