Sysprep joins domain with wrong workstation name
- Using sysprep with an answer file. After running sysprep, the Windows Welcome appears asking for the machine name (which is what I want it to do) followed by automatically joining the domain. The only thing is, when you try to log into the Vista workstation an error is displayed "the trust relation ship between this workstation and the primary domain failed". In ADUC (W2k3 with SP2) the workstation name does not match the name given to the workstation earlier. The name is completely random. The correct workstation name is displayed in DNS and DHCP, so why did it join the domain with a random name and the name given to it is not correctly displayed in ADUC?
My Sysprep.xml
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<AutoLogon>
<Enabled>false</Enabled>
</AutoLogon>
<ProductKey>MYPRODUCTKEY</ProductKey>
<TimeZone>Eastern Standard Time</TimeZone>
<RegisteredOwner>ME</RegisteredOwner>
<RegisteredOrganization>MYORGANIZATION</RegisteredOrganization>
</component>
<component name="Microsoft-Windows-Security-Licensing-SLC-UX" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipAutoActivation>true</SkipAutoActivation>
</component>
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" 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>
<Credentials>
<Domain>MYDOMAIN.COM</Domain>
<Password>MYPassword</Password>
<Username>ADDWORKSTATION</Username>
</Credentials>
<JoinDomain>MYDOMAIN.COM</JoinDomain>
</Identification>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
<SkipUserOOBE>false</SkipUserOOBE>
</OOBE>
<RegisteredOwner></RegisteredOwner>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Name>ADMIN2</Name>
<Group>Administrators;PowerUsers</Group>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<RegisteredOrganization />
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="x86" 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>en-us</InputLocale>
<SystemLocale>en-us</SystemLocale>
<UILanguage>en-us</UILanguage>
<UILanguageFallback>en-us</UILanguageFallback>
<UserLocale>en-us</UserLocale>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:d:/myimage.wim#Vista Install" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
Answers
known issue. See some of the other threads. Some users have convoluted work arounds or have made home made scripts to fix this. Bottom line is, it is a bug and MS is (hopefully) working on a fix.
Probably the easiest thing to do is use an asterisk * as the computer name in your .xml file, then when the install finishes, login with a domain account that can change the computer name, and change the computer name to the correct name.
MS must have know about this... why they let this out is puzzling to say the least.
All Replies
known issue. See some of the other threads. Some users have convoluted work arounds or have made home made scripts to fix this. Bottom line is, it is a bug and MS is (hopefully) working on a fix.
Probably the easiest thing to do is use an asterisk * as the computer name in your .xml file, then when the install finishes, login with a domain account that can change the computer name, and change the computer name to the correct name.
MS must have know about this... why they let this out is puzzling to say the least.- The worst part is that MS states that the homemade scripts are unsupported by them. I am not sure if MS knows if this problem exists, but for anyone who has premium phone support with them, please hammer them with this issue. This is really stopping us from deplying vista. It is in MS best interest to fix this.
