In this third article of the Deployment Solution series we are going to configure our PXE environment. Also we are going to build several tasks, and make sure our server is completely ready for the tasks it is build for.
First of all we have to make sure we have enough licenses. If you have not implemented enough license, you can start the license configurator. Go to start Programs Altiris Deployment Solution and select Product Licensing Utility.
Select an Activation Key File Information file.
In the screen that appears it will show you the license information in the file with an expiration date.
Click Next to continue.
Now you see all the keys that you have added. You can here remove them, replace them or add them.
Next step is to define how we are going to add our clients into the network.
First method is the easiest, but also the most dangerous way. We could configure PXE to get all the clients in the database. After that we still have to install the agent on them.
The best way is to get most of your clients configured with the agent.
To do this we are going to start the console for the first or second time, and we are going to Tools and select remote Agent Installer.
I select the second option, use this username and password for all clients. This will prevent me from giving a username for every client. With 5 clients that can be done, but if you have 500! That will be difficult.
In the next screen we are giving the default path where to install the client. Now we are going to configure the option for the default client. To do this, click on Change settings.
In our main office we configure the clients to connect directly to our head office server. We give in the IP address, and the default port that is used is 402.
Now we click on the second tab Access:
In this tab we can select the remote control settings. In my configuration I select: Allow this computer to be remote controlled. I also notify my user when is do a shutdown or a restart. If he does not respond in the given time, 10 seconds, I perform the task.
On the bottom you can define when the client denies access to the client agent.
In the security tab we can select the option to make sure that the session data is encrypted. It will slow down the communication between the agent and the server, but it will enhance the security. I do not use it.
I give in a password to prevent user shutting down the agent.
Also I hide the client tray icon.
This will prevent the user from seeing that I have a Altiris DS agent on my machines.
The tabs Logfile and Proxy are not used. Go to the last tab. Change the default bootdrive if you have a client that boots from another drive then C: and click OK.
Click Next in the screen below.
Now you can add clients automatically to the default group or create a specific group.
Click Next to continue.
Now you can add new computers. When you click on Add, network neighborhood is shown, and you can add all computers you want by clicking on them and adding them. Also clients that already have the agent can be added to make sure they get the new configured options.
Click on Finish to get the agent installed.
All agents are successfully installed.
If you get a error on a pc, then you can add the pc manually by going to the pc and start \\deploymentserver\express\agents\aclient
That will manually install the client. Make sure you configure all the settings correctly just like we did before.
After the installation all clients will appear in your deployment console.
Next step we have to do is to configure PXE.
Go to Tools and select PXE configuration.
First we are going to build our default Boot set. Click on New to start the wizard.
Give it a name, and define the site were it belongs is used it in the name.
That makes it easier later, and select the options you need. In this case I use WinPE. Click on Create boot image.
Now we are going to configure twelve steps that will help us to build the Pre boot environment.
Step 1: Customize your pre boot with an optional description.
Click Next to start the Boot disk driver locator.
Most of the drivers are already inside the WinPE image. If you'd like to add more, click on Have disk or internet.
Click Next to continue.
Here you may provide a static IP address. This will also disable you from doing more machines at once. Best practice is to use the DHCP option.
Click next to continue.
Now you have to be careful. Because we have several PXE servers we do not give the address of the static server, but we use the Multicast option. Check it and leave all settings as default.
Give the domain and the username password that is used to connect.
Best practice is to not use the administrator but an account that has administrator rights.
Leave everything as it is, and click Next to continue.
Click Next to continue, and again Next to continue in the resume screen.
Click Next to continue.
Click Next to continue.
Now the pre boot environment is being built. This takes a short while, so be patient.
Now you will notice that the OK button is enabled. Click on it.
Click OK again, and save the settings.
Best task now is to test it with a client that boots into the PXE image.
If everything works, you have to do the same task on the other deployment servers also. The PXE boot environment contains a mapping to the software and images location, and this makes it difficult to use only one.
Next step is to create a few tasks. We are going to install SVS on all clients.
There is already a default job there for us.
Let's edit it, and make it ready to install SVS.
Right click on the job, and alter the name as you like. I use a real SVS key, so I removed the 120 day trial rule.
Select the task, and select modify.
First you have to browse to where the package is located. Almost make sure that the folder with your software packages is in the eXpress share. I always create a folder software with a folder that gives the brand and the software in it. In my case it looks like .\Software\SVS\Software_Virtualization_Agent.msi
Add a valid key so the command line looks like PRODUCT_KEY=1234-1234-1234
Click Next and then Finish.
Now you have to move the job to an easy location.
In the left of the deployment console you can create a new folder. In this folder you can place your configured jobs.
Copy the standard jobs you need to this folder. It will become your personal Deployment library.
The final step in our process is to synchronize all the data to all the other servers. There are several ways to do this. The easiest way is to create a script inside the Deployment Server that copies the data.
In the next article we are going to do it with Microsoft DFS.
Deployment Console, Part 2: Installing Deployment Solution 6.9 on Our Home Site and on Other Sites.
Deployment Console, Part 4: Configuring Microsoft DFS for Deployment Server File Synchronisation