none
Setting OSDComputerName using a UserExit script

    Question

  • I have written a user exit script to set OSDComputerName from a text file using the MAC of the computer.  The relevant files are here https://onedrive.live.com/redir?resid=C4BC55BF27E7E399!4420&authkey=!ADh-gRfiBmNjHEM&ithint=folder%2c

    If I pxe boot to the deployment wizard the "Computer Details" page shows OSDComputerName would be "PC-<MACADDRESS001>".  If I continue imaging anyway, after the machine boots into Windows, I can simulate the gather process using the process outlined here http://deploymentresearch.com/Research/Post/293/Save-time-and-avoid-pain-Create-a-MDT-test-environment and the resultant log shows me that OSDComputerName would be set as expected (the MAC is found in macfile.txt).  If I then reboot and pxe boot back to the deployment wizard, now the "Computer Details" page shows the correct name from macfile.txt.  It's almost as if OSDComputerName is being read from somewhere else.

    Can anyone explain this?

    Is there a better way to name machines using a text file in the form of <MAC> = ComputerName?  This is something we've been doing since XP using vbs scripts that I've written, I'd like to begin leveraging MDT for naming but I need to keep this name file and its layout.


    • Edited by J. Wall Monday, June 06, 2016 9:10 PM
    Monday, June 06, 2016 9:05 PM

Answers

  • I've been able to get the user exit script working, it now pulls the computer name from a text file in the form of <MACAddress001> = <ComputerName>.  There are some enterprise specific comments in there but if anyone wants the script let me know and I'll clean it up and post it.
    • Marked as answer by J. Wall Tuesday, June 14, 2016 7:54 PM
    • Edited by J. Wall Tuesday, June 14, 2016 7:54 PM
    Monday, June 13, 2016 4:34 PM

All replies