DS7.1 How to install the Symantec Management Agent using VBScript from Initial Deployment

Article:HOWTO36080  |  Created: 2010-11-17  |  Updated: 2012-07-23  |  Article URL http://www.symantec.com/docs/HOWTO36080
Article Type
How To



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:

  1. Implementing %ComputerID% token-  https://www-secure.symantec.com/connect/articles/how-use-computerid-token-notification-server-7
  2. Import images into NS using the ‘ResourceImportTool.exe’  KB

There are two methods documented below:

  1. Simplified version: uses the Copy File task to copy down the SMP Agent installer (uses SMB)
  2. Complex version: uses HTTP only to copy the SMP Agent installer (avoids SMB) but also requires you modify the automation folders.


     

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:

  1. After deploying the image, use a copy file task to copy the Agent Installer into the image.  This executable is called "AeXNSCInstSvc"
  2. Edit the production registry key to execute this file in the "RunOnce' key so it will fire on reboot.
  3. Be sure that the next task in the job has a sufficient ammount of time before task expiration to allow for the agent to install.

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:

  1. Using Windows Explorer,  browse to ‘<install drive>:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task Handler\bootwiz\oem’ on the Notification Server
  2. Create a directory called ‘ADO’ and populate it with the following folders.  Note:  the file structure is also found under the ‘oem\DS’ folder.
    x64
            base
                  tools
       x86
            base
                   tools
  3. Browse to the ‘<install drive>\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task Handler\ghost’ directory.
    Copy ‘ghconfig32.exe’ to the ‘ ..\x86\base\tools’ directory and rename the file ‘ghconfig.exe’
  4. Browse to the ‘<install drive>\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task Handler\ghost\x64’ directory.
    Copy ‘ghconfig64.exe’ to the ‘ ..\x64\base\tools’ directory and rename the file ‘ghconfig.exe’
  5.  Browse to the ‘<install drive>\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task Handler\bootwiz\oem\ado ’ directory.
    Create a file called ‘default.bdc’.  Populate it with the following information:
     [PACKAGES]
    ADO=True

    [Application]
    Compress=True
    OEMRequired=DS

    Note:  This file instructs Boot Disk creator to add the ‘WinPE-MDAC-Package(ADO)’ to the preboot
  6. 6)         Browse to the ‘ <install drive>\Program Files\Altiris\Deployment\Config’ directory and locate the file named ‘Altiris.Deployment.config.
    Open the file with Notepad and search for the text  ‘Adding OEM extension’. 
    Copy out the following section of text to a new instance of Notepad:

    <!--Adding OEM Extension-->
        <items>
          <item guid="CBB5C0E6-AEDE-4905-8D58-41F762E3DB0A" classGuid="BEB44BED-F526-4c4b-A97B-0E4D9F788F6B">
            <name>OEM Extension Item</name>
            <description>Class for adding OEM Extension</description>
            <itemAttributes>Hidden</itemAttributes>
            <OEMExtension>
              <OEMExtensionName>DS Agent</OEMExtensionName>
              <OEMExtensionLocation>ds</OEMExtensionLocation>
              <OEMIsDefault>1</OEMIsDefault>
            </OEMExtension>
          </item>
        </items>

     Change the text as follows (changes marked in bold):

     <!--Adding OEM Extension-->
        <items>
          <item guid="CBB5C0E6-AEDE-4905-8D58-41F762E3DB0B" classGuid="BEB44BED-F526-4c4b-A97B-0E4D9F788F6B">
            <name>OEM Extension Item</name>
            <description>Class for adding OEM Extension</description>
            <itemAttributes>Hidden</itemAttributes>
            <OEMExtension>
              <OEMExtensionName>ADO</OEMExtensionName>
              <OEMExtensionLocation>ado</OEMExtensionLocation>
              <OEMIsDefault>0</OEMIsDefault>
            </OEMExtension>
          </item>
        </items>

    Copy the updated text back into the file so that the resulting section of the file looks as follows:

     <!--Adding OEM Extension-->
        <items>
          <item guid="CBB5C0E6-AEDE-4905-8D58-41F762E3DB0A" classGuid="BEB44BED-F526-4c4b-A97B-0E4D9F788F6B">
            <name>OEM Extension Item</name>
            <description>Class for adding OEM Extension</description>
            <itemAttributes>Hidden</itemAttributes>
            <OEMExtension>
              <OEMExtensionName>DS Agent</OEMExtensionName>
              <OEMExtensionLocation>ds</OEMExtensionLocation>
              <OEMIsDefault>1</OEMIsDefault>
            </OEMExtension>
          </item>
        <item guid="CBB5C0E6-AEDE-4905-8D58-41F762E3DB0B" classGuid="BEB44BED-F526-4c4b-A97B-0E4D9F788F6B">
            <name>OEM Extension Item</name>
            <description>Class for adding OEM Extension</description>
            <itemAttributes>Hidden</itemAttributes>
            <OEMExtension>
              <OEMExtensionName>ADO</OEMExtensionName>
              <OEMExtensionLocation>ado</OEMExtensionLocation>
              <OEMIsDefault>0</OEMIsDefault>
            </OEMExtension>
          </item>
        </items>

    Save the file.  This file instructs Boot Disk Creator to create two OEM extensions: DS Agent and ADO.  When a preboot configuration is made using the ADO OEM extension, all of the DS Agent setting along with the ADO setting will be included in the
    configuration
  7. From a command prompt browse to the ‘ <install drive>\Program Files\Altiris\Notification Server\Bin’ directory and type the following:
     ‘aexconfig /configure “c:\program files\altiris\deployment\config\altiris.deployment.config”’

 The Deployment Solution will be reconfigured with two OEM extensions.

Part Two:  Create a new preboot configuration that uses the ‘ADO’ extension.

  1. From within the Symantec Management Console select the ‘Settings’  icon across the top of the page and select ‘All Settings’.  Click the ‘+’ next to ‘Deployment and Migration’ and ‘Symantec  Boot Services’.  Select the  Preboot Configurations’ icon.
  2. Click on the ‘Add’ button.  Enter a name for the configuration.  E.g  ‘PXE with ADO’.  From the drop down list next to the ‘OEM extensions’ text box select ‘ADO’ .
  3. Click ‘OK’ and then ‘Save Changes’
  4. Allow time for the Symantec Management Agent(s) on the task servers to request a new policy file.  When the new xml file is delivered, BootWiz will launch and a new configuration will be created.

Part Three:  Create a new job that includes three tasks to install the Altiris Agent

  1. From within the Symantec Management Console select the ‘Manage’ icon across the top of the page and select ‘Jobs and Tasks’.
  2. Right Click on the ‘Jobs and Tasks’ folder and select ‘New > Client Job’.
  3. Right Click on the new job and select ‘Rename’.  Name the job ‘Agent Offline Install’
  4. Task One
    1. Under Jobs/Task click on ‘New’ and select new ‘Task’
    2. Select ‘Deploy Image’ from the list.  Name the job uniquely to fit your situation.  E.g. ‘Deploy Windows 7’
    3. Select the appropriate image and correct product key.
    4. Uncheck ‘Include DeployAnywhere for hardware independent imaging’
    5. Supply credentials if system needs to join a domain.
    6. Click on ‘OK’
  5. Task Two
    1. Under Jobs/Task click on ‘New’ and select new ‘Task’
    2. Select ‘Run Script’ from the list.  Rename the script to ‘Agent VBscript’
    3. From the ‘Script type’ dropdown box select ‘VBScript’
    4. Copy the contents of the VBscript attached to this KB into the window.
    5. Select ‘OK’.
  6. ask Three
    1. nder Jobs/Task click on ‘New’ and select new ‘Task’
    2. Select ‘Reboot to’ from the list.  Change the name to ‘Reboot to Production’
    3. Select the ‘Production’ radio button and click on ‘OK’ and then ‘Save changes’
  7. The job will now have the three tasks.

Part Four:  Setup Initial Deployment

  1. Click on ‘Settings > All Settings’ and expand the plus side next to the ‘Deployment and Migration’.  Select the ‘Initial Deployment’ icon.
  2. Click on the ‘Add’ button and select the ‘Agent Offline Install’ job.  Click on ‘Save Changes’.  The job is now assigned to the initial deployment menu.
  3. Click on the ‘PXE Server Configuration’ hyperlink
  4. Select the ‘Respond to unknown computers’ checkbox and select ‘PXE with ADO’ for the PXE boot image from the drop down box.  Select ‘x86’ in the other box
  5. Click on ‘Save Changes’

Part Five:  Boot system

Take brand new system and boot to PXE.  Initial Deployment will trigger and job will be ran.


Attachments

InstSMA.vbs (14 kBytes)

Article URL http://www.symantec.com/docs/HOWTO36080


Terms of use for this information are found in Legal Notices