Searching...
Filters
SmallMediumLarge
Home Print Show Topic URL Previous Next
IT Management Suite
Client Management Suite
Server Management Suite
Deployment Solution
Asset Management Suite
ServiceDesk

Components of Deployment Solution

Deployment Solution

When you install Deployment Solution on Symantec Management Platform, the Deployment Solution components get integrated with Symantec Management Platform. The Deployment Solution leverages the platform capabilities to execute and schedule tasks, jobs, and policies, and set up site servers, use filters, and generate reports. The components of Deployment Solution help you manage the client computers in your environment.

Table: Deployment Solution components

Component

Description

Deployment Plug-in

The Deployment Plug-in is installed on the client computers on which you want to execute deployment tasks. This plug-in lets you create and deploy disk images, perform remote operating system (OS) installation, change system settings, and migrate the personality settings.

You can enable the Symantec firewall on the client computer and enable the Windows firewall on the Notification Server. However, to install the Deployment Plug-in by pushing it to computers, you need to disable one of these firewalls.

See Installing and uninstalling Deployment Plug-in on client computers

Deployment site server component

The Deployment Site Server Component was packaged with previous versions of Deployment Solution and was installed on the site servers. From the Deployment Solution 7.5 release onwards, installation of this component is deprecated, whereas, you can use the Upgrade policy to upgrade the older versions of this component.

Automation folder

The automation folder is installed on a client computer and stores the preboot environment of a specific operating system. The preboot environment that is setup by the automation folder is also known as the automation environment.

The automation folder can be installed on the client computers of Windows, Linux, and Mac operating systems. The automation folder uses the WinPE files of Windows OS and LinuxPE files of Linux OS to create the automation environment for the specific OS. For Mac, the folder uses the DSAutomation partition to boot the Mac client computers into the automation environment. The main advantage of the automation folder is that client computers can boot to the automation environment independent of the connection that is established with the Network Boot Service (NBS) setup on a site server.

See About PXE configuration using Network Boot Service

Ensure that the Deployment plug-in of the specific operating system is installed on the client computer on which the automation folder is created.

See Installing and uninstalling Automation Folder on client computers

To boot the client computers to an automation environment, DNS must be configured on the network. All computers in the network must also be able to perform a Name Server Lookup. The installation, uninstallation, and upgrade of the automation folder is triggered and rolled out as a policy for all the operating systems. You can configure the policy through the Settings > Agent/Plug-ins > Deployment and Migration menu of the console.

Network Boot Service server

The Network Boot Service (NBS) is installed on a site server and comprises of the following two services:

  • PXE service and Boot Service Discovery Protocol (BSDP) service

    SymantecNetworkBootService(PXE and BSDP)

  • TFTP service

    SymantecNetworkBootServiceTftp

The PXE service of NBS boots the client computers in the preboot environment using the PXE image whereas the BSDP is required to create the Netboot image for the Mac computers. The PXE image is used for the Windows and Linux client computers. The BSDP must be enabled in the NBS configuration settings dialog box.

The NBS also provides configuration of the TFTP service, logging levels for PXE image deployment, and configuration of the network settings.

See About Network Boot Service

Imaging tools

The Ghost disk imaging tool runs on the Windows (x86, x64), Linux (x86, x64) operating systems. The Ghost tool can also be used for creating backup disk images and images of disk partitions.

These tools support NTFS, FAT (16,32), EXT2/3, RAW file system,and HTTP and multicast imaging options. Ghost supports Windows only hardware-independent disk imaging which can be deployed to diverse client computers by using drivers from a centrally managed driver database. Backup images are not hardware-independent and are intended to be deployed on the same client computer.

For Mac operating system disk imaging, the symDeploMac imaging tool is used. Symantec recommends that you use the combo update to make the images hardware-independent. Backup imaging is not supported for Mac.

Boot Disk Creator

Boot Disk Creator (BDC) creates a boot disk using the Windows or Linux preboot operating systems. Boot Disk Creator is run on the client computers to boot the computers in WinPE or LinuxPE. BDC can also create a bootable CD or USB.

Resource Import Tool

The Resource Import tool is used for importing the existing Windows and Linux images. The tool is also used for adding Windows-scripted OS installation files.

See Importing images using Resource Import tool

Driver Manager

Driver Manager provides the interface to perform driver operations such as adding and deleting data from the DeployAnywhere driver database and the Preboot driver database.

DeployAnywhere

DeployAnywhere lets you deploy the Windows operating system image to dissimilar hardware. DeployAnywhere also lets you perform a Windows-scripted installation on bare metal computer.

See Deploying a Windows image

Deployment Task Server Component

The Deployment Task Server Component of Deployment Solution is deployed on a site server on which the Task Service executes. The Task Server Component is installed on the site server, which is assigned to perform tasks specific to Deployment Solution. This component can be installed on the Windows x86 or Windows x64 site servers only.

The Deployment Task Server Component installation or uninstallation is triggered as a policy of Deployment Solution. By default, this policy is turned on. This policy can be set through the Settings > Agent/Plug-ins > Deployment and Migration > Windows folder of the console.

Deployment Package Server Component

The Deployment Package Server Component of Deployment Solution is deployed on a site server on which the Package Service executes. This component is installed on the site server, which is assigned to Deployment Solution to store the product-specific packages or files. This component can be installed on the Windows x86 or Windows x64 site servers only.

The Deployment Package Server Component installation or uninstallation is triggered as a policy of Deployment Solution. By default, this policy is turned on. This policy can be set through the Settings > Agent/Plug-ins > Deployment and Migration folder of the console.