In Article 7 we used Nlite to build a clean, lean machine. After the machine is built we deploy it to a VMware image. That image is captured and then we can deploy that image by using HII tools.
In Altiris Deployment Console there is also a way to build a clean, lean machine. The difference between the method in Article 7 and this method is that in this method we always build our new machines scripted where the previous method is only used once and then it is imaged.
In the Altiris deployment Console we are also able to build jobs for most operating systems that will enable us to do unattended installations. After building an unattened script we can build more jobs to configure options or to configure our clients. Also there we can build in jobs that will install most of our necessary software. As always a job contains one or more tasks. We can build on jobs with all the tasks, or we can build several jobs and deploy them after each other to a machine. It's just what you like to use.
The scripted install in Altiris Deployment Solution is a way to do the job, but it will not enable you to build very small images.
In this article I will explain how to build a scripted install. It will be one job with a couple of tasks that will deploy our XP software and it will configure the client after it is rolled out.
Start Your Altiris Deployment Console, and create a new task.
Give the job a name.
Then double click on the job to start the task wizard.
Give the job a description and click on Add. There we select the wizard for Scripted OS Install.
Now we select Windows because we are going to build a Windows image.
Click Next to continue.
Now we select the operating system version we like. In this case Windows XP Professional. Then we select the Language. There are four options. English, French, German and multilingual. If your language is not listed, then select the Multilingual.
We use the Default Automation as the Pre Boot environment.
Click Next to continue.
Now we have to select the installation files. If they are not listed, then you may select: Add New. This will bring up another wizard.
Give the image an unique description. Then select the installation disk where the files are. You have to select the directory where winnt.exe is located. Mostly that will be in the I386 directory.
Click OK to go back to the previous screen. You will see that the Deployment Server is copying all the files into the eXpress share.
Do the same for the service pack that you wish to include. I selected Windows XP Service Pack 3. Again it takes some time to get the files in the correct location to use it with Altiris Deployment Solution.
Click OK to go to the previous screen, and then select Next to continue.
Now we have to make a decision. We can select the default DOS image that is included with your Deployment Server install, but the disk will only be formatted in Fat 16 or Fat 32. This is not exactly what we want. If you need a Fat 32 partition, then you can use this option.
I select Continue with distributing the DOS image. In the configuration later you can choose convert to make the disk NTFS.
Click on advanced to select the size of the partitions. You can choose a size in GB, or you can use a percentage of the disk to use.
Click Next to continue.
In the next screen you can select an already built unattend script. Because this is our first time there will be none. Click Next to continue.
Now we are going to build our unattended script with or without our options.
Follow all the tabs to change the settings for your wishes. Please read them all carefully so you select the correct settings you want. Below is the complete list for you.
Unattended:
- OEMSkipEula
- UnattendMode
- KeyboardLayout
- UnattendSwitch
- FileSystem
- OemPreinstall
- TargetPath
- OemPnpDriversPath
- Win9xUpgrade
- DriverSigningPolicy
- NtUpgrade
- ExtendOemPartition
GUIUnattended:
- AdminPassword
- OEMSkipWelcome
- OEMSkipRegional
- Timezone
- Autologon
- AutoLogonCount
GUIRUNOnce:
UserData:
- FullName
- OrgName
- ComputerName
- ProductID
Regionalsettings:
Display:
- BitsPerPel
- XResolution
- YResolution
- VRefresh
Networking:
Identification
- JoinWorkGroup
- DomainAdmin
- DomainAdminPassword
- DomainOU
- JoinDomain
As you see, there are not as many options as in the previous article where we used Nlite. But in every section you can add additional tasks, and you can even build your own sections.
When you have selected everything you need, and added all the values you need in your image, then you can click next to continue.
In the Switches screen you see the switches that are used, and in the additional commands you see all the commands.
Click Next to continue.
In the following screen you will see the settings for the A-Client that will be installed automatically. You can change settings as you wish. The settings are the same as you used in the previous article where we deployed the A-Client to our clients.
Click Next to continue.
Now you see the summary of what we did. Click Next to continue.
Now you can also choose your own custom codes. Click Next when you are finished.
Our scripted OS Install is now ready.
Now we have to build a task to configure the machine. Select Add, and then modify Configuration.
Click on Microsoft Networking
Give in the domain name you like. You may also alter other settings here. Just click on all the icons in the left to see what you can do here.
Click Next to continue. And then click Finish.
Now our image will be deployed fully scripted and then it will become a member of the domain.
Our scripted install is now ready. Try it out on one of your clients or on a VMware machine.
The installation will be fully unattended.
Deploying XP with a Unattended script is a cool way to deploy XP to all your clients, but the installation is very large. All the drivers, also the unnecessary drivers are installed. This installation is over 1 GB. And almost half of it will not be used. You also see that you are not able to take out software like games, messenger and more. That is why I preferred the Nlite method. That is much more capable to take out almost everything you don't want.
In our job as a system administrator we want to build the best clients that will help us do our job with as little effort as possible. Nlite is much better for doing this because of the various ways to take things out. Next to Nlite we also can use Vlite. This will do the same as Nlite, but for Vista.
In the Next article we are going to build our a HII job to build Vista images hardware independent. This will help us in deploying more and more Vista clients that are all identical.
Deployment Console, Part 7: Building a Clean, Lean Windows XP Machine and Deploy it with Altiris Deployment Solution
Deployment Console, Part 9: The Ultimate DS 6.9 HII .bin