Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Altiris 6.9 deploy image - using unknown Unattend file?

Created: 14 Feb 2013 | 3 comments

In our environment, we have two Altiris 6.9 servers.

I created a Windows 7 image and am able to deploy it with success, in that, all of the drivers load accordingly from the unattend file.  I can verify that the correct unattend file was used by navigating to C:\Windows\Panther on the freshly-imaged machine.

On the second server, however... if I use the same image and job, the deployment is fine, but no drivers are loaded.  On this machine, if I navigate to C:\Windows\Panther, it appears to be using a completely different unattend file.

Can anyone explain how this may be possible, and how I may resolve it?

Thanks!!!

Comments 3 CommentsJump to latest comment

BBC's picture

I don't know the details of the job you execute, but have you confirmed that the unattend file is also in place on the second DS or is this included in the build?

A few more details could help to troubleshoot the issue...

-BBC

boonet's picture

BBC,

The unattend is included in the build.  Here is how it is setup:

Copied unattend to C:\Windows\Panther and C:\Windows\System32\Sysprep

Remove computer from domain, reboot, run the following command:

sysprep.exe /oobe /generalize /shutdown /unattend:C:\Windows\system32\unattend.xml

When the computer has shut down, I turn it on and boot into our WinPE environment, where I then run the Capture Image task.

BBC's picture

I wonder if it would be better and simpler to run a task after the image deployment, which injects the file? With this you can at least exclude the possibility that this is related to the image, server or process.