Unattend.xml and Windows 10

Question

_{Friday, October 2, 2015 4:18 PM | 1 vote}

In previous versions of Windows you could leave the computername attribute blank when using an unattend.xml file with sysprep and setup would prompt for a computer name.  This isn't the case with Win10.  When I deploy images each requires a specific name so I relied on setup to prompt and then setup would autologin once, automatically join the domain via script, and reboot.  I'm trying to achieve this same goal with Win10, but am having no luck.  I've tried a PowerShell script that prompts to rename the PC prior to joining the domain, but that requires a restart to take effect.  Any suggestions on how I can achieve this?

All replies (5)

_{Monday, October 5, 2015 10:00 AM ✅Answered | 1 vote}

This may not be that useful, but here's what we do to solve this. Either;

• Have a customised PE boot that prompts for the computername (and possibly other information) before building the unattend.xml on the fly. With this approach you typically need a standard unattend.xml that can be used as a template. Or;
• Always use "*" to generate a randomised name, autologin locally after the specialize pass, and have your scripting prompt for the name, rename the computer prior to domain joining and continuing with your existing process. It sounds like you're already trying this one - bear in mind that the autologin provided by the specialize pass is a one-shot (I think), but your script can set auto-login registry keys and you can then restart as many times as needed. Note that the autologin keys need to be correct for the computername the computer will have on next boot.

There are variations on this - e.g. auto-logging on after the specialize pass in order to read information (e.g. Asset number) from the BIOS that would allow a name to be calculated. This can allow the whole naming process to run through unattended. Similarly, reading stuff from the BIOS to calculate a name whilst still in PE can allow the correct name to be specified in the unattend in the first place without prompting.

_{Saturday, October 3, 2015 12:29 AM | 1 vote}

Hi, you should trysetting up yourimage withMDT2013Update 1,and work withthe updatedversionofWindowsADK, thus addingthe image ofWindows 10RTM.

Download the Windows ADK for Windows 10 -> http://go.microsoft.com/fwlink/p/?LinkId=526740

Download MDT 2013 Update 1 -> https://www.microsoft.com/en-us/download/details.aspx?id=48595

Regards! 

Jesús Enrique Gonzales Azcarate [Colaborador de Comunidades Microsoft]

_{Monday, October 5, 2015 7:12 AM | 1 vote}

Hi DaveS75,

I hope the following link will be useful.

Create a Windows 10 reference image

https://technet.microsoft.com/en-us/library/mt297533(v=vs.85).aspx

Best regards

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

_{Monday, October 5, 2015 5:30 PM}

Jesus, I'm already using the latest version of the tools, but as I stated, leaving the computerName field blank as in previous versions doesn't cause setup to prompt for a computer name to be entered during OOBE.

_{Monday, October 5, 2015 5:32 PM}

Thanks, this was the next best thing I could come up with, too.  I appreciate the nudge in the right direction.