Images captured without the Symantec Management Agent are difficult to use in the DS 7.1 process because any tasks following the reboot of the image into production do not run until the agent is installed. Older images - that is, those captured in an earlier version of Deployment Solution, are the most common "cause" of this limitation.
The recommended resolution to this issue is to deploy the image, install the agent, and re-capture the image per supported methodologies.
However, DS support engineers have created a process that installs the Symantec Management Agent after the image is deployed. This process could then be used as a part of Initial Deployment, which is described later in the document.
Perquisites for the article:
There are two methods documented below:
This is the simplified process that uses SMB with the "Copy File" task to copy the SMP Agent Installer down.
More details is needed for this method, and it will function a little more slowly. However, the essential method here is as follows:
This is the more complex process created for those who must NOT USE SMB in their environment.
Part One: Add an OEM extension to Boot Disk Creator
Note: Perform the steps below on the Notification Server. Once the steps are complete, create a package of the OEM folder and use package servers to update the OEM folder structure on others site servers.
By default, the WinPE WIM file created by DS 7.1 contains three optional components: WinPE-Scripting Package, WinPE-WMI-Package, and a WinPE- XML Package. These three packages provide support for the majority of tasks customers need to perform in automation. Unfortunately, they do not provide the support needed to run the advanced VBscript written by the backline team. The VBscript used in this solution needs functions provided by the ‘WinPE-MDAC-Package’(ADO). To add this package to the PXE automation environment, a new OEM extension needs to be created.
Part 1: To add a new OEM extension, follow the steps below:
The Deployment Solution will be reconfigured with two OEM extensions.
Part Two: Create a new preboot configuration that uses the ‘ADO’ extension.
Part Three: Create a new job that includes three tasks to install the Altiris Agent
Part Four: Setup Initial Deployment
Part Five: Boot system
Take brand new system and boot to PXE. Initial Deployment will trigger and job will be ran.