Unable to deploy a Windows 8.1 image using WDS name and approve!

Question

Hello,
Hopefully some of you residing Windows 8.1/2012R2 WDS experts are able to answer this question that has been tormenting me for 3 weeks now!
I have been trying to deploy a custom Windows 8.1 image to a test VM using an answer file and WDS for a mostly unattended process (outside of selecting the image to apply).
The image and installation process actually works flawlessly if I let WDS handle all known and unknown clients.  The problem comes when I try to "name and approve" the stations.  All I do is enter the name and leave everything else blank
and/or at their default settings but it always fails no matter the tweaks I've been trying to apply to the answer file, UnsecureJoin true or false with the credentials and whatnot does not matter.  For the sake of simplicity, I'll post the "specialize"
portion of my answer file which worked using UnsecureJoin without name and approve here:
<settings pass="specialize">
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Identification>
<UnsecureJoin>true</UnsecureJoin>
</Identification>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>%MACHINENAME%</ComputerName>
<RegisteredOrganization>Organization</RegisteredOrganization>
<RegisteredOwner>Utilisateur</RegisteredOwner>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>1009:00001009</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>fr-FR</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
The error I retrieved from C:\Windows\panther\setuperr.log is: "[DJOIN.EXE] Unattended Join: At least one of JoinWorkgroup/JoinDomain must be specified: 0x57".  Thus, I retry with name and approve but by specifying the JoinDomain with the
%MACHINEDOMAIN% value as such:
<Identification>
<UnsecureJoin>true</UnsecureJoin>
<JoinDomain>%MACHINEDOMAIN%</JoinDomain>
</Identification>
This seems weird since WDS should already have this information which is specified in the WDS server properties.  Still, I add the requested information and try again which then gives me the following error fetched from C:\Windows\debug\NetSetup.log:
"NetpGetDomainData: Failed to find the domain data: 0x6e"
Anybody else ran into this and know the fix for it?
Also, as an additional note, not sure if it is relevant, but doing only "Approve" will not work at all either as it gives me the following error when I attempt to do so: "The name provided is not a properly formed account name." despite
the fact that I've formatted it to use "CVL%MAC" which should pass by fine.

Answer 1

Hi,
Firstly, I need to confirm how the name setting got passed? Because according to my test, if the device named uncorrectly, it would prompt the error and couldn't go to next step:
As far as I know, the naming standard is different between Device Identity and ADDS server naming policy, the second naming policy should be like: %61username%#
Therefore, please check your PC device name if there is any problem with it. You can also refer to the contents of the link below for more details about Naming Standard:
http://programming4.us/desktop/21662.aspx
Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
For another problem, Unsecure join, according to the contents of the link below. since Vista, shared computer password is a dynamically generated, no need to assign the password manually.
http://technet.microsoft.com/en-us/library/cc730845(v=ws.10).aspx
Roger Lu
TechNet Community Support