SysPrep Help?

It looks like it is still having the same thing. It's not running the scrip to join it to the domain. When we run it ourselves it works. But sysprep is having issues.

<?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="Error" 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="Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
</OOBE>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>TgB5AHMAVABlAGMAaAAxACEAUABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</PlainText>
</Password>
<Description>Local Administrator</Description>
<DisplayName>XXXXXXXXX</DisplayName>
<Group>administrators</Group>
<Name>XXXXXXXX</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="Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ProductKey>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</ProductKey>
<CopyProfile>true</CopyProfile>
</component>
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Identification>
<JoinDomain>school.com</JoinDomain>
</Identification>
</component>
</settings>
<cpifflineImage cpi:source="wim:c:/windows%20sysprep%20thing%2064bit/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

cluberti said:

If you're in a domain environment, and you're imaging corporate-use machines, you might want to consider you're doing it the hard way and then consider using tools designed to do this sort of thing for you, like MDT :).

Without the panther and unattend logs from a machine that didn't work, it's hard to say why your installation didn't totally work. However, I'd strongly recommend doing it the easy way and using MDT, which automates most of this for you and provides a good environment for adding drivers, installing apps, joining domains and naming PCs, and good monitoring and logging functionality built-in as well.

True but if the wheel is already made no need to remake it. Meaning this is what my company wants me to work with I can't do anything else wise then to use it. But any 411 on the issue would be helpfully tho. :)

So run this while the Sysprep is working? Other then join domain issue everything is functioning fine.

As I stated above, I can't buy that car. Thus no point in trying to get off topic. Thanks