Altiris has built in support for Sysprep when creating or distributing images.
The documentation doesn’t mention some things that are worth knowing so I will try to address them in this post.
Sysprep support can be added to Altiris during the install where it will ask you for the Sysprep install files (deploy.cab) per selected OS.
If you didn’t add Sysprep during install you can copy deploy.cab to one of subfolders in the Sysprep folder. Eg for 32 bit Windows 2003 deploy.cab goes to Sysprep\DotNet\x86:
As I wrote earlier in this post it’s very important to use the correct Sysprep version as each OS has it’s own version.
As a general rule you should grab the deploy.cab from the install media (in the Support folder).
When creating Images you can activate Sysprep support by setting the “Prepare using Sysprep” checkbox:
If you do not need to perform special configuration for you mass storage (eg add drivers) you can select “Disable mass storage device support” under Advanced Settings.
This will make the initial Sysprep run a little faster:
Optionally you can select an Automation environment, I like the LinuxPE option since it’s boots fast like the DOS option but still as fast imaging like Windows PE.
- A few earlier post regarding PXE Boot that may be useful:
- STOP: 0x0000005D when booting Windows PE
- Compiling Drivers for Altiris Linux PXE Image Part 1
- Compiling Drivers for Altiris Linux PXE Image Part 2
When you schedule a Create Image task with Sysprep activated, Altiris will copy the files in the deploy.cab to C:\Sysprep on the target computer and run Sysprep.
It will also copy a default sysprep.inf file that is used to restore the target computer after imaging. But where does this sysprep.inf file come from?
The Sysprep folder is populated with some default answer files, named standard<os version>.inf:
So I assumed it would select the answer file based on the selected OS version. I selected Windows 2003 in my Job:
So I assumed it would copy standard2003.inf but instead it always seems to copy standardxp.inf.
If you cannot use this file, eg because you have differing files per OS you can copy a sysprep anwer file after the create image job.
If you want to do this using Linux a sample command would be:
/mnt/ds/RDeploy/Linux/firm copy /mnt/ds/Sysprep/standard2003.inf PROD:/Sysprep
In the Deploy Images task you can enable Sysprep support in the same manner:
But this time the Advanced Settings buttons allows us to select a custom Sysprep Answer file:
In the Answer file we can use both Default and Custom tokens, Altiris will replace them to the actual values before injecting it.
An example of using the Tokens is using the name in the Altiris Console as the new Computer Name:
Another place where this feature comes in handy is the AdminPassword key in the GuiUnattended section:
%ADMIN_PASSWORD% is not a default token so you must enter the password in the user_tokens table:
The password is stored securely because a regular user shouldn’t be able to access the eXpress database directly.
Note that I also tried to use an encrypted password in the answer file (setupmgr.exe allows you to do so) but this results in an error message during Sysprep which will halt the process until you click OK.
This behavior is documented here.
Note: if you use the HP branded version of Altiris a simple User Tokens Editor is included in the Tools | HP Tools menu.
By default Altiris will only create or deploy an image of the first disk. If you want to create or deploy images for multiple disks you can create a second task and use the –d<number> parameter.
The “Do not boot to Production” option will ensure that the second image is created directly after the first disk image:
When restoring multiple disks, the easiest way is to restore the extra disk(s) first by using the –d<number> parameter again.
Deselect “Automatically perform configuration task after completing this imaging task”:
The system disk image must be the last one restored and there you enable both configuration options:
(Don’t forget to select the Sysprep Answer file using the Advanced Settings option)
Was once an enthusiastic PepperByte employee but is now working elsewhere. His blogs are still valuable to us and we hope to you too.