Sysprep - Windows 7 - unable to sysprep image that joins domain

[irishredbloke]

Good morning all:

Below is my unattend.xml. I am using the sysprep + win7 for creating virtual machines in Red Hat Enterprise Virtualization 3.0 but having difficulty getting them to auto-join the domain. My sysprep progression proceeds normally and completes. The initial boot of the image pauses for a computername, then after completion will allow login. The newly created win7 machine/image will not allow either administrator login or domain login. I suspect my order of operations may be incorrect in the unattend.xml file.

Thanks for any help you guys can provide. I'll be happy to quickly answer any questions you have.

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<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>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-US</UserLocale>
</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">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password> <Value>aABlAGwAcAB1ADgAMQAyAFAAYQBzAHMAdwBvAHIAZAA=</Value>
<PlainText>false</PlainText>
</Password>
<Description>First Admin User</Description>
<DisplayName>administrator</DisplayName>
<Group>administrators</Group>
<Name>administrator</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<TimeZone>Eastern Standard Time</TimeZone>
</component>
</settings>
<settings pass="specialize">
<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">
<ProductKey>XXXXX-XXXX-XXXXX-XXXXX-XXXXX</ProductKey>
</component>
<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>
<Credentials>
<Domain>OurDomain</Domain>
<Password>password</Password>
<Username>user</Username>
</Credentials>
<JoinDomain>OurDomain</JoinDomain>
<MachineObjectOU>ou=pcs,dc=ourdomain,dc=org</MachineObjectOU>
</Identification>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:d:/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

 

[Brynster]

the solution may lay in your sysprep rather than your unattend.xml file (which looks correct to me)

I think in sysprep you may have the generalize flag set which means its creating a generic image rather than a specific image.

I would suggest manually running sysprep after the install rather than from a script. ensuring the generalize checkbox is not ticked.

 

[irishredbloke]

Thanks for the reply Brynster. I'll investigate the Generalize flag by doing a new installation, Ctrl+Shift+f3 at the username prompt, then ensuring the checkbox for Generalize is not checked.

 

[irishredbloke]

actually since I started to run through the installation process and got to the Generalize part, I recall that I cancel that Sys Prep Tool window bc I'm following this guide:

Sysprep a Windows 7 Machine

The guide will tell you to cancel it and move your configured unattend.xml file in place and run a command to kick off sysprep.

 

[irishredbloke]

Still faced with the original issue.

 

[irishredbloke]

I tried removing the OU line and then running sysprep. Same result. Our windows xp sysprep looks like the following:

;SetupMgrTag
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\sysprep\i386
TargetPath=\WINDOWS

[GuiUnattended]
AdminPassword="********"
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=35
OemSkipWelcome=1

[UserData]
ProductKey=*****-*****-*****-*****-*****
FullName="Information Technology"
OrgName="Our Company Name"
ComputerName=$ComputerName$

[Display]
BitsPerPel=32
Xresolution=1024
YResolution=768

[TapiLocation]
CountryCode=1
Dialing=Tone
AreaCode=302
LongDistanceAccess="1"

[Identification]
JoinDomain=OurDomain
DomainAdmin=OurDomain\domainaccount
DomainAdminPassword=********

[Networking]
InstallDefaultComponents=Yes

[Branding]
BrandIEUsingUnattended=Yes

[Proxy]
Proxy_Enable=0
Use_Same_Proxy=0

 

[Brynster]

Very odd,
Let me whip up a test image and see what comes of it. Win 7 or Win XP you mention both?

 

[irishredbloke]

thanks so much for trying. windows 7 is the answer. maybe we can see if the unattend.xml even works...

 

[irishredbloke]

I did notice that in the article I was using it did include generalize....

sysprep /generalize /oobe /shutdown /unattend:unattend.xml

 

[Amapola]

irishredbloke I know it is off topic, but there is no way to PM in this forum, so I am leaving information here. I have some compatibility settings issue with my XFX 750i and q9550. You have somewhat similar system is I do. I kindly ask you to have a look at my thread http://www.sevenforums.com/hardware...d-core-absolute-instability-lockups-help.html and advise me if it is not hard for you. First of all, how ,on earth, did you make it work XFX 750i with "q" Quad Core series CPU?

 

[ZMan]

Any way on how this work out? I'm having the same issue and look use that article.