Scripting : New image don`t work in K2000

New image don`t work in K2000

Hi!

Have fixed a new custom Windows 7 image. This is what I have done:

Step 1: Have take a Dell OEM dvd with Windows 7, and install it on a PC

Step 2: When the installation was done, I pressed ctrl-shif-f3 and enter the sysprep mode

Step 3: Installed all windows updates and added a couple of apps

Step 4: Then I run sysprep again, Enter OOBE, checked Generalize, and shutdown the computer.

Step 5: Captured the wim-file with imageX

Step 6: Extracted Dell OEM dvd with Windows 7. So I can reach the installations files.

Step 7: Replaced install.wim with that I have created in step 5.

Step 8: Created a ISO-file with imgburn. Done!

Step 9: Have installed the ISO on a VirtualBox, and it works just fine. All the app and updates are there.

Have upload it to K2000, and I use my old unattend.xml that I have used to my old scripted installation. Pre-installations task : create singel partition and format c: works fine, but after that installation is failed.

What could be wrong, maybe is the xml?

7 Comments [ + ] Show comments

Where does it fail? Does the image apply but it bluescreens? Are you receiving a specific error, maybe during sysprep? - nheyne 9 years ago
- No bluescreens. It fails at the step 4: Install OS
  See : http://www.ladda-upp.se/bilder/ickkwtswtxugvq/ - Swede 9 years ago
I don't believe using OEM media is recommended but I think that normally results in licensing problems, not imaging. How did you upload it to the K2000? - chucksteel 9 years ago
- We have always use the OEM media, I uploaded with Media Manager. - Swede 9 years ago
check to see if a pid.txt exists in the wim file you created. If it does delete it. - SMal.tmcc 9 years ago
Have created a new unattend through K2000, and now the installation goes to 100%, but after that it fails with new error. So I think the problem is in the XML. See link:
http://www.ladda-upp.se/bilder/lqgmzxxxzoaib/ - Swede 9 years ago
- The problem is definitely your unattend file. - nheyne 9 years ago
can you share your xml file. that is usually due do the language you are calling in the xml does not have the pack available to install it. - SMal.tmcc 9 years ago
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<UseConfigurationSet>true</UseConfigurationSet>
<UserData>
<AcceptEula>true</AcceptEula>
<FullName>user</FullName>
<Organization>atoy</Organization>
<ProductKey>
<Key>FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4</Key>
<WillShowUI>OnError</WillShowUI>
</ProductKey>
</UserData>
<ImageInstall>
<OSImage>
<InstallToAvailablePartition>true</InstallToAvailablePartition>
</OSImage>
</ImageInstall>
</component>
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<UILanguage>en-US</UILanguage>
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>sv-se</InputLocale>
<SystemLocale>sv-se</SystemLocale>
<UserLocale>sv-se</UserLocale>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<RegisteredOwner>user</RegisteredOwner>
<RegisteredOrganization>atoy</RegisteredOrganization>
<ProductKey>FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4</ProductKey>
<TimeZone>Pacific Standard Time</TimeZone>
<AutoLogon>
<Enabled>true</Enabled>
<Username>admin</Username>
<Password>
<PlainText>true</PlainText>
<Value>password123</Value>
</Password>
<LogonCount>4</LogonCount>
</AutoLogon>
<ComputerName>*</ComputerName>
</component>
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<Identification>
<JoinWorkgroup>WORKGROUP</JoinWorkgroup>
</Identification>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Path>reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\FirstNetwork" /v Category /t REG_DWORD /d 00000000 /f</Path>
<Description>Setting Network Location</Description>
<Order>1</Order>
<WillReboot>OnRequest</WillReboot>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<SkipMachineOOBE>false</SkipMachineOOBE>
<SkipUserOOBE>false</SkipUserOOBE>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Name>admin</Name>
<Group>Administrators</Group>
<Password>
<Value>password123</Value>
<PlainText>true</PlainText>
</Password>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<InputLocale>sv-se</InputLocale>
<SystemLocale>sv-se</SystemLocale>
<UILanguage>sv-se</UILanguage>
<UserLocale>sv-se</UserLocale>
</component>
</settings>
</unattend> - Swede 9 years ago
If your OEM CD wasn’t multilanguage than you would have problems with:
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<UILanguage>en-US</UILanguage>
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>sv-se</InputLocale>
<SystemLocale>sv-se</SystemLocale>
<UserLocale>sv-se</UserLocale>
</component>

You should set the winpe locales to be all en-US I would guess. - cserrins 9 years ago

Answers (1)

Posted by: rjobe 9 years ago

A lot of complicated steps to get an image when KACE will do it for you.

1. Load your OS up to K2 using Media Mgr.

2. Create a Scripted Install for the OS & use the basic sysprep provided by K2.

3. Perform a scripted install onto the computer you want.

4. Update the computer with all updates from MS, install any other programs, etc...

5. Capture an image (NO SYSPREP) of machine up to K2. This image can be used on the same model PC for updating/testing/etc. & just in case the image you are working on get's messed up.

6. After the Image has been captured - create a sysprep file by using the ITNinja Sysprep Creator tool (very easy).

7. Sysprep the machine and shutdown.

8. Capture an image of the syspreped machine to the K2.

9. After it's done - startup the syspreped machine and see if it completes all the way. If it does - that's a Good first step.

10. Deploy the captured image BACK to the machine and test again to see if sysprep works and it starts.

Check out the Building a Generic Image and Windows 7 Golden image creation doc's.

Russ

Comments:

If you do not sysprep the machine you can get problems with WSUS and Domain related items. You need to sysprep if you plan on joining the machine to a domain or using WSUS - SMal.tmcc 9 years ago

Answer this question

Posted by:

View more:

Scripting Questions

question