Installing and Uninstalling Automation Folder on Client Computers
An automation folder stores the preboot operating system on the client computers. The client computers use this functionality to boot in the preboot environment whenever required using the preboot OS that is installed locally on the client computer. The preboot operating systems for Windows and Linux operating systems are, WinPE, and LinuxPE respectively. For the Mac computers, a NetBoot environment is contained in the automation folder that is installed on the client computer.
As of 8.6 RU1, Mac is not supported. Linux x64 Preboot is supported starting from 8.6 RU3.
In Deployment Solution the Deployment Automation folder -Install policy installs the Automation folder on the client computer and the Deployment Automation folder-Uninstall policy uninstalls the automation folder from the client computers. When you enable the policy, a green
On
symbol shows on the top right corner of the policy page.For Linux and Mac client computers, to install the automation folder, if the package server is configured on HTTPS, and the SSL certificate is not installed on the client computers then you must manually download and install the SSL certificate on the client computers
The advantages of using Automation Folder over PXE services of NBS are as follows:
- Lets you boot client computers faster than booting using PXE service of the NBS setup.
- The automation folder function is not affected or restricted by firewalls.
- The automation folder can boot the client computers that have static IP address.
The default location and size of the automation folder that is created on the client computer are as follows:
Operating system | Architecture | Default folder location | Approximate folder size |
|---|---|---|---|
Windows | x86 | C:\Boot | 214 MB |
Windows | x64 | C:\Boot | 214 MB |
Linux x64 | /boot/altiris | 300 MB | |
Linux x86 | /boot/altiris | 300 MB | |
Mac | - | /Volumes/DSAutomation In case a partition is already present with the name DSAutomation then a new folder is created with DSAutomationA name. | 15 GB |
For Mac, the
Deployment Automation folder for Mac - Install
policy creates a DSAutomation
volume on the disk volume where Symantec Management Agent (SMA) is installed. The automation volume uses only the available space on the volume that is installed with SMA and does not use any free space available on other volumes. Ensure that there is sufficient space on the volume on which you have installed the SMA. If a volume is already present with the name, DSAutomation
then a new volume of name DSAutomationA
is created. You can also uninstall the automation volume with the uninstall policy for Mac automation folder. After you enable the
Deployment Automation folder for Mac - Uninstall
policy you must manually delete the DSAutomation partition that is present in the unmounted and unallocated state. If you do not want to run the uninstall policy to uninstall the automation folder from the client computer, then you must manually erase the disk and the volume from the client computer. If, you manually remove partition and the volume of the client computer, then ensure that you clean the Non-volatile random-access memory (NVRAM) of the client computer.To clean the NVRAM of a client computer, refer to http://support.apple.com/kb/HT1533 article.
- To install or uninstall an automation folder, follow these steps:
- In the Symantec Management Console, on theSettingsmenu, clickAgent/Plug-ins > All Agents/Plug-ins.
- In the left pane, expand theAgents/Plug-ins > Deploymentfolders.
- Expand the Windows, Linux, or Mac folder and then do one of the following:To install an automation folder.Select one the following Deployment Automation folder - Install policies:
- Deployment Automation Folder for Linux x64 - Install
- Deployment Automation Folder for Linux x86 - Install
- Deployment Automation Folder for Mac - Install
- Deployment Automation Folder for Windows (x64) - InstallYou can enable theDeployment Automation Folder for Windows(x64)-Installpolicy when you install and import the Windows Assessment and Deployment Kit (ADK) for Windows 8 and the PEInstall package is created on Notification Server. After the PEInstall package is created on Notification Server, the PEInstall is available and enabled on thePreboot Configurationdialog box.
- Deployment Automation Folder for Windows (x86)-InstallYou can enable theDeployment Automation Folder for Windows(x86)-Installpolicy when you install and import the Windows Assessment and Deployment Kit (ADK) for Windows 8 and the PEInstall package is created on Notification Server. After the PEInstall package is created on Notification Server, the PEInstall is available and enabled on thePreboot Configurationdialog box.
To uninstall an automation folder.Select one the following Deployment Automation folder - Uninstall policies:- Deployment Automation Folder for Linux x64 - Uninstall
- Deployment Automation Folder for Linux x86 - Uninstall
- Deployment Automation Folder for Mac - Uninstall
- Deployment Automation Folder for Windows (x64) - Uninstall
- Deployment Automation Folder for Windows (x86) - Uninstall
- On the right-side pane, you can view the details of the selected policy.Symantec recommends that you do not modify the default settings of the policy. If you want to modify the settings, first clone the policy and then modify the cloned policy.The details of the fields are as follows:Program NameDisplays the name of the program that is applicable.Enable Verbose Reporting of Status EventsThis option sends the package status events to Notification Server. TheNotification Server Event Capturesettings in theGlobal Symantec Management Agent Settingspolicy take precedence to theEnable Verbose Reportingsetting here. Events are sent only if they are enabled in theGlobal Symantec Management Agent Settingspolicy.Applied toDisplays the list of computers to which the policy applies. By default, Deployment Solution lists the targets in the textbox, as per the predefined filter that is set for the SMP. A target is a group of computers that are created as per the set filter.Package MulticastThis option disables the package download through multicast. Multicast slows down the rollout of a package, so you can turn it off for an urgent patch. Additionally, in some environments multicast does not work. For example, multicast has to be disabled for routers and switches. ThePackage Multicastsettings in theGlobal Symantec Management Agent Settingspolicy take precedence to the settings here.ScheduleThe policy schedule is displayed. By default, the options that are configured in theExtra Schedule Optionsfield are applicable. Symantec recommends maintaining these settings. By default, theRun once ASAPand theUser can runoptions are selected.Extra Schedule OptionsTheExtra Schedule Optionsthat are selected by default are as follows:
- Run once ASAP
- User can run
- ClickSave changesto save the configuration settings of the policy.