Deployment Solution lets you deploy a standard disk image on client computers using the Deploy Image task. After you deploy a new image, all the existing data and applications of the client computer are lost and the computer is restored to the state of the image that you deploy.
On Windows Server 2008, you might need to change the password on the client computer before logging on for the first time after this task runs. Sysprep clears the administrator password when it prepares a computer for imaging. You can avoid having to manually change the password by creating a custom answer file. The answer file should include a plain text password. You can then use the answer file while you deploy your images on remote computers.
Before you perform the Deploy Image task, you must know the following:
If the computer has the Deployment plug-in installed, the computer configuration is saved and restored after the image is applied. The computer configuration contains the computer name, network settings, and domain.
If Initial Deployment is used, you select the configuration settings to apply to the computer after it is imaged. To deploy a new computer that does not have an operating system, use Initial Deployment.
If the computer is a member of a domain, supply the appropriate credentials to rejoin the domain.
Ensure that you deploy a BIOS-based image on a BIOS-based computer and an EFI-based computer image on an EFI-based computer. If you deploy a BIOS-based image on an EFI-based computer, the EFI-based computer does not boot to automation environment from production environment.
Ensure that you run the x:/bcdedit.exe after deploying a UEFI enabled image on the virtual machine that has ESX 5.0 and then boot the virtual machine into the production environment
To create a deploy image task
In the Symantec Management Console, navigate to the Manage menu and select Jobs and tasks.
On the right pane, right-click Jobs and tasks and select New > Task.
On the Create new task page, select Deploy Image.
The Create or Deploy image task can only be executed in the Automation environment.
Specify a name for the task on the first field.
Enter the following of the Imaging section:
Enter the name of the image file to deploy.
For Linux, only the Name and Image Name fields are necessary. All of the other fields are optional.
Select an operating system license that can be used to boot the computer back to a working state after the task runs. If the license has not been added to Deployment Solution, you can add one by clicking New.
The Current Key option is available only for Windows Vista and later versions of the Windows operating system.
In the DeployAnywhere section, check Include DeployAnywhere for hardware independent imaging to deploy the drivers that you added to the DeployAnywhere database.
The DeployAnywhere database works only for the WinPE preboot operating system. After you select the option, the DeployAnywhere database executes once you deploy the image. The database runs even when the computer is running the WinPE preboot operating system. This option discovers what type of hardware is on the destination client computer and creates a new HAL. The HAL and the required drivers that Sysprep removed are then deployed to help the computer boot successfully.
You can skip validation of missing critical drivers that are added in DeployAnywhere database by checking Skip missing critical drivers option. Check this option if you do not want the drivers that you add to pass through the validation that is performed by Deployment Solution. The system file and the .inf file validations are bypassed for the drivers that you add if you select this option.
After you check this option, select either of the options from the Bypass Driver Validation drop-down list:
By default, this value is selected, which means that for no drivers the validation is bypassed.
You can select if you want to bypass validation for all the drivers.
If a driver does not pass the validation checks and if you did not check the Bypass Driver Validation option, then the driver will not be installed on the computer after you execute the Install Windows OS task.
In the DeployAnywhere section, select the debug log level in Debug Log Level for the installation of the drivers.
The debug log levels are as follows:
This log level captures the logs of all the failures of a task.
The log level is 5 and it retrieves log information about the drivers that match.
The log level is 10 and the log is created when a function is entered.
The log level is 11 and the log is created when the function exits.
The log level is 20 and it prints information about the devices.
The log level is 30 and it logs information about inf parsing.
No matching Device for inf
The log level is 40 and it logs information about infs if they do not match with devices of the client computer.
The log level is 255 and it logs information on all the points that are listed for this field.
Select one of the following options from the Sysprep Configuration section:
Generate Sysprep configuration file using inventory data
The required information is obtained from the CMDB.
Custom Sysprep configuration file
Click Browse to select the custom Sysprep file that you created.
Enter the credentials in the Credentials section that are needed to join the client computer to a domain.
If the client computer was not in the domain before the image was deployed, you can add the computer to the domain even after the image is deployed
Lets you decide the partitions on which you deploy the image. You can change the destination partition size by clicking the partition number.
Partition or System reserve partition deployment do not use DeployAnywhere.
For Linux, only Data Partition
deployment is supported.
To deploy Windows 7 with system reserved partition, create a job to run deploy system reserved partition and system partition in the same preboot environment.
In case of Mac Deploy image task, if empty disk space is present on the client computer then it is merged with the last partition of the client computer
For Mac Deploy image task ensure that the client computer partition capacity is more than the partition capacity of the image source computer.
Lets you add command-line options for the imaging tool.
For Ghost partition deployment, following command lines must not be used:
MODE,Size,SRC and DST values should not be used for command line.
If you want to deploy an image of a Windows 2012 computer of BIOS type which does not have a system reserve partition on a UEFI computer, then you must use the following Ghost switch
Ensure that you do not specify the switch -SZEE and select the Resize
partition option simultaneously for the deploy image task.
Lets you configure the number of computers on which you want to multicast the image. You can override the default multicast settings that were set in Settings > Deployment > Image Multicasting
There must be at least one computer over the threshold value that you specify for multicasting. For example, if the threshold count is 2, there must be at least two client computers and one master computer, which is 3 in total, before multicasting is used in the session
Deployment Solution does not support Multicast and Unicast options simultaneously if you use the Ghost imaging tool.
Lets you specify the files and folders that you want to preserve when the image is restored.
This option is not supported if the client computer is installed with Linux operating system.
Lets you add the credentials that are required to deploy an image, which was obtained from an HTTP site.
If you are reading this procedure as a part of a process, return to the process by clicking on the following link: