DS7.1 How do I apply a new build of an Automation Folder?

book

Article ID: 152729

calendar_today

Updated On:

Products

Deployment Solution

Issue/Introduction

In DS 7.1 there are two pre-installed Automation Folder builds, one WinPE and one Linux (called PEInstall and LinInstall, respectively).  In addition to the two pre-installed builds, there is the option on the 'Preboot Configurations' page to create new Automation Folder configuration as well as PXE configurations.  How do I apply one of these other Automation Folders to the environment?

Resolution

NOTE: There is a possible procedure to apply additional Automation Folders below, but first consider the following: is a new configuration needed?  The only difference between a new Automation Folder and the pre-built Automation Folder is the drivers existing in the Boot Disk Creator database when the Folder installer is built.  If the new build is to add drivers to the automation environment, then adding the drivers through the Boot Disk Creator and then selecting 'Recreate Preboot Environment' on the 'Preboot Configurations' page.  When the policy is picked up by the SBS Server's Agent, then the automation installer should regenerate to include the new drivers.

Generate the configuration and Package:

  1. From the Preboot Configurations Page, Add a new Preboot configuration and select 'Automation Folder'.  Save Changes.
  2. Once the new configuration is received by the Deployment Server, the 'Bootwiz.exe' process will run.  When it is done running, the automation folder installer has been built.
    **NOTE: Configurations are picked up by the Agent on a schedule.  To accelerate this process, open the Agent Settings on the Server and click the 'Update' button.
  3. Browse to <Program Files>\Altiris\Notification Server\NSCap\bin\Win32\X86\Deployment\Automation.  Note the existence of  the "PEInstall_x86" folder.  This is the default installation package for your automation folders.  There should also be another folder with the name of the new configuration you just generated.
  4. Verify that the package was also created in the console: it should be found at Manage>>All Resources, Organizational Views>>Default>>All Resources>>Package.

Install the Automation Folder Package:

  1. Create a new Client Job under Manage>>Jobs And Tasks.
  2. Create a task to copy and install the package. 
    1. In the job, create a new 'Copy File' task
    2. Under the 'Source' drop-down menu, select 'Upload from Local System'
    3. Under 'Location', use the 'Browse...' button to browse to and select the executable in the folder where the new automation build was placed
    4. Enter credentials under which there will be permission to copy files to the target systems.
    5. Under 'Destination', enter a folder to which the file will be copied on the target system.  This can be a temporary folder that we can delete later.
    6. Under 'Command Line', enter "<destination path>\<configuration name>_x86.exe" -s -h
    7. Enter credentials under which there will be permission to run/install files to the target systems.
    8. Enter an appropriate/descriptive name for the task.
    9. Click 'OK'.
  3. *Optional: Create a cleanup task to remove temporary file/folder
    1. In the job, create a new 'Run script' task
    2. The text of the script should be as follows:
      del "<destination path>\<configuration name>_x86.exe"
      rmdir "<destination path>"
      *Note: The <destination path> should be the path to which the file was copied, and <configuration name> is the name of the new Automation Folder
    3. Click 'OK'.
  4. Click 'Save Changes' (in the Job)
  5. This job can now be sent to the appropriate machines via either 'Quick Run' or creating a schedule.