OSDComputerName not working RRS feed

  • Question

  • I have set a variable OSDComputerName for Unknown computers. After F12 and loading WinPE I am promted for puting in a computername

    When I choose something like this; PC1234

    and after completing the task the computernumber is "minint-xxx"

    I have 3 operating systems in 3 TS, and have the same issue on all of them

    • Moved by TorstenMMVP Tuesday, February 26, 2013 9:03 AM moved to OSD
    Monday, February 25, 2013 8:16 PM


  • rebuilded everything, images and task sequense. Working fine now..even XP

    (maybe some corrupted items??)

    • Marked as answer by J.Louwerse Tuesday, March 5, 2013 2:33 PM
    Tuesday, March 5, 2013 2:33 PM

All replies

  • Are you positive that the task sequence isn't erroring out?


    Are there any other steps that might be trying to set the OSDComputerName variable after the start of the task sequence?



    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    <-- If this post was helpful, please click "Vote as Helpful".

    • Edited by NPherson Monday, February 25, 2013 8:32 PM
    Monday, February 25, 2013 8:32 PM
  • How are you setting OSDComputerName? Using a blank task sequence variable set on a collection and then the default UI at the beginning of the TS?

    Jason |

    Monday, February 25, 2013 8:37 PM
  • task sequences are working well, no errors...
    no other steps in the TS

    Is OSDComputerName a MDT value?

    I created the TS with the "Create Task Sequence" in SCCM and not with the button MDT Task Sequence.

    Pretty new with SCCM and I think I am missing something....

    I want to use this method for unknown pc's, and dont want to use the import function in the management console...

    Monday, February 25, 2013 8:45 PM
  • OSDComputerName is set blank on the collection Unknown Computers

    What do you mean with? then the default UI at the beginning of the TS

    Monday, February 25, 2013 8:48 PM
  • The prompt isn't anything you added, correct? It looks like the one in the blog post at , correct?

    Jason |

    Monday, February 25, 2013 9:03 PM
  • the prompt is shown because it's set on the collection...and I added nothing to the TS.

    Also need to set a Task Sequence Variable: OSDComputerName with an empty value?

    Monday, February 25, 2013 9:34 PM
  • Right, I'm just verifying what you did because I can't "see" what you did and there are other possibilities. The screenshot I'm specifically talking about is at

    Are you sure you typed in OSDComputerName for the TS variable?

    Are you PXE booting or using boot media?

    Jason |

    Monday, February 25, 2013 9:49 PM
  • Using PXE. 

    Using pxe. (But created the referce Vista image with boot media)

    Before I posted my problem to technet, the only thing I added was the above variable on the unknown computer collection.

    Now I have set (as in your example) a task variable in the TS with no value. So far so good?

    • Edited by J.Louwerse Tuesday, February 26, 2013 8:28 AM
    Tuesday, February 26, 2013 7:49 AM
  • After F12 I choose the task install vista sp2 and I need to fill in this value. 

    Tuesday, February 26, 2013 8:14 AM
  • Run an other test: even when I use the import computer function in the management console and the computer is no longer unknown the computername is changed to when the TS is ended.
    Tuesday, February 26, 2013 11:29 AM
  • There's your problem.

    You do not need the Set Task Sequence variable task in the task sequence. The
    Set Task Sequence Variable task you've added is setting the value of the
    variable to blank and is not needed at all. You simply need to define the blank
    variable on the collection, and the task sequence engine will prompt the
    interactive user to supply a value. That's it, nothing more is needed. This is
    depicted in the blog post I first referenced above:

    Once set, the value of this task sequence variable is used by the Apply
    Windows Settings task to populate the unattend.xml file which is then used by
    Windows setup (which occurs during the Setup Windows and ConfigMgr task).

    Jason |

    Tuesday, February 26, 2013 6:58 PM
  • Hi Jason, I really think there is a bigger problem.

    This one, just a test...before this forum thread the only place where I have set the OSDComputerName was on the Unknown Computer collection. I will remove it from the Task Sequence.

    But when I use the import wizard in the management console


    The computername is changed to minint-xxx when the task sequense is ready

    So lets forget the OSDComputerName, it's not working at all

    Is the problem in WinPE? Or somewhere else?

    Tuesday, February 26, 2013 7:26 PM
  • Rebuilt all, boot images and TS. Now it's working like it should!

    In a few days I will test an untend XP installation.
    What must be the value ComputerName= in my own unattend.txt?
    Is the value replaced automaticly by SCCM with the OSDComputername?

    Friday, March 1, 2013 7:40 AM
  • rebuilded everything, images and task sequense. Working fine now..even XP

    (maybe some corrupted items??)

    • Marked as answer by J.Louwerse Tuesday, March 5, 2013 2:33 PM
    Tuesday, March 5, 2013 2:33 PM