Howto MDT uses WDS generated computernames? RRS feed

  • Question

  • Dear all

    We need a fully automated deployment, no user input shall be necessary, *absolutely* no user input.

    In our WDS only solution we used an unattend.xml with the entry (in the specialize phase, Windows-Shell-Setup):


    This lets WDS generate the computername (from Active Directory) according to the rule set in the Properties of the WDS server, tab "AD DS". The rule there is "P02%1#". This generates P001, P002, P003, .... for the computername or the already existing name (if the computer is redeployed).

    This does not work with MDT.

    We automated using bootstrap.ini, customsettings.ini, tasksequence (ts.xml), unattend.xml.

    We read about various solutions (scripts, web service etc.) that have the common disadvantage that they don't read/store the computername in AD.

    How to get back the WDS generated computernames?

    Thank you for any help.


    Zürich, Switzerland.

    Monday, August 21, 2017 4:07 PM

All replies

  • One customer of mine ended up using following solution which might work for you as well:

    - a web service to determine next free computer name in AD which adheres to your naming convention
    - tattoo computer name into the BIOS using vendor specific tools so that it can be used during redeployments.
    - a user exit script which determines if the computer name value is stored in the Asstet Tag BIOS property during the MDT initialization.
    Friday, August 25, 2017 10:53 AM
  • I am aware of two methods, one is to set OSDComptuerName = * 

    THe star '*' tells windows to auto-generate a random computername

    Otherwise there is this method:

    Keith Garner - Principal Consultant [owner] -

    Tuesday, September 5, 2017 5:22 AM