Windows 7 Windows 7 Sysprep

[FKALurch]

I am having problems with running sysprep on some new Windows 7 64-bit machines that we just got in.

Here is what I have: Dell Optiplex 780, Windows 7 64-bit operating system. We do not have a volume license; we just use the product key that is on the machine.

Here is what I want to do after running sysprep: Want to be able to enter a computer name, product key, and join the domain by adding my user name and password (I can not add this to the answer file since my password changes.)

We have different image for every type of machine that we have here. We are using Norton Ghost version 8. I run the command sysprep /oobe /shutdown /unattend:sysprep.xml. Do not use /generalize since I have an image for every different machine type.

I have included a copy of me answer file.
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="generalize">
<component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="Link Removed due to 404 Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipRearm>8</SkipRearm>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="Link Removed due to 404 Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>net user administrator /active:yes</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="Link Removed due to 404 Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipAutoActivation>true</SkipAutoActivation>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="Link Removed due to 404 Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ShowWindowsLive>false</ShowWindowsLive>
<TimeZone>Central Standard Time</TimeZone>
<CopyProfile>true</CopyProfile>
</component>
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="Link Removed due to 404 Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Identification>
<JoinDomain>Acklie.com</JoinDomain>
</Identification>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="Link Removed due to 404 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="Link Removed due to 404 Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<UserAccounts>
<AdministratorPassword>
<Value>aAB1AHMAawBlAHIAcwAxACEAQQBkAG0AaQBuAGkAcwB0AHIAYQB0AG8AcgBQAGEAcwBzAHcAbwByAGQA</Value>
<PlainText>false</PlainText>
</AdministratorPassword>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>aAB1AHMAawBlAHIAcwAxACEAUABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</PlainText>
</Password>
<Description>Local Administrator</Description>
<DisplayName>Administrator</DisplayName>
<Group>Administrators</Group>
<Name>Administrator</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<VisualEffects>
<FontSmoothing>ClearType</FontSmoothing>
</VisualEffects>
<RegisteredOrganization>Crete Carrier Corporation</RegisteredOrganization>
<RegisteredOwner>CCC</RegisteredOwner>
</component>
</settings>
<cpifflineImage cpi:source="wim:d:/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

 

[ChatGPT]

It seems like you are encountering issues with running Sysprep on some new Windows 7 64-bit machines. I'll provide some insights into the information you've shared:

Problem Description:​

• Machines: Dell Optiplex 780 with Windows 7 64-bit OS.
• License: Using the product key on the machine without a volume license.
• Objective: Customize the machines post-Sysprep by entering computer name, product key, and joining a domain without adding sensitive information like passwords to the answer file.
• Image Management: Using different images for each machine type, not utilizing the /generalize switch in Sysprep command.
• Procedure: Running Sysprep command: sysprep /oobe /shutdown /unattend:sysprep.xml.

Recommendations:​

1. Check Licensing: Ensure that using individual product keys without a volume license is compliant with Microsoft's licensing policies.
2. Password Management: Since passwords change and can't be stored in the answer file, consider using a prompt or script to input passwords during or post-deployment.
3. Sysprep Configuration:
   • Review the Sysprep XML configuration shared to ensure it aligns with your requirements.
   • Confirm that the paths specified in the XML file for components are correct and accessible.
   []Troubleshooting:
   • Check the event logs and any error messages generated post-Sysprep for more specific details on the failures.
   • Verify that the Sysprep process is completing without errors and that the XML file is being read correctly.
   []Considerations:
   • Make sure the answer file is structured correctly, adhering to Windows' requirements.
   • Validate that the settings in the XML file match your intended configuration post-Sysprep.

Feel free to share any specific error messages or logs if available for a more detailed diagnosis of the issue you are facing!