1 of 1 people found this helpful
1. Your issue is probably a driver. Check what drivers are loaded vs which ones were loaded on your previous image.
2. Don't put the LANDesk agent on your image. LANDesk automatically installs the agent in conjunction with Sysprep.
The agent should not be installed on the image because of 2 reasons:
1. It causes disappearing devices in the database due to all machines having the same device id
2. The agent is constantly updated and change. Software that changes often is best left off the image.
I've experienced a similar issue, but in a different spot during Sysprep. After getting the image all squared away with extra storage drivers for each of our platforms, Syspreping, capturing etc., when we deploy our XP SP2 image it starts the Sysprep process, appears to find the right drivers, but hangs on "Registering Components". I've let it sit over night to see if there was a timeout or something but it never does. Just sits there at "Registering Components" forever. I can't seem to find any articles stating what this portion of Sysprep is doing in detail and what I might try to fix it.
Any tips would be greatly appreciated. This has been a bit of a showstopper. Everything else about the image seemed to be working fine.
There is a known issue with SYSPREP and Windows Media Player (WMP) where the newly patched version of WMP attempts to verify the serial number of the windows install before the PC has a chance to run the rest of the SYSPREP setup.
There is a hotfix available from Microsoft that installs a new version of SYSPREP.
We like to use the old SYSPREP and instead simply uninstall WMP and also don't patch WMP. I'm not a big fan of WMP anyway becuase it installs the "Windows Media Player Network Sharing" service by defualt. And it also rips music to the person's roaming profile by default as well.
Hope this helps!
Had this issue at a client and it turned out to be the video driver install during minisetup. There is a Microsoft patch for this issue. More information can be found here:
I have experienced the same problem and found the issue to be with the driver for the NSC TPM Chip that is a component of certain IBM models (T42, T43 & M52). I found details of the problem in the following link:
To get around the issue I ensure the driver is pathed but not available during sysprep (renamed .sys files) and use a GUIRunOnce command to correct the renamed driver files. You may be prompted for a missing driver but these can be ignored. Come the next reboot the driver is installed.
Hope this helps