For Windows, the Prepare for Capture Image task uses Sysprep utility to remove the computer name, Security Identifier (SID), the operating system license, GUID of the agent, and some hardware-dependent drivers. You must always run this task before creating a disk image. Sysprep also disables the built-in administrator account and clears the admin password.
For Linux, this task runs a preimage script to remove the configuration-related settings and prepare the computer for imaging.
You can choose several options while creating this task. You must create a deployment task before you run it.
To prepare for image capture
In the Symantec Management Console, select Manage > Jobs and Tasks.
In the left pane, do either of the following:
Right-click System Jobs and Tasks folder and select New > Task.
Expand the System Jobs and Tasks folder and right-click Deployment and Migration folder to select New > Task.
In the Create new task dialog box, under the Deployment and Migration folder select the Prepare for Image Capture task.
Under the Pre-Imaging section, select either Windows (using sysprep) or Linux operating system.
The fields and their descriptions are as follows:
Task name icon
Displays the default task name as Prepare for Image capture. You can edit the default task name to specify a relevant task name. For example, Prepare for image capture_Linux.
Lets you select the operating system for which you want to create a Prepare for image capture task.
For Windows, you can select from the following:
Select the version of Windows operating system.
Select an operating system license that you use to restore the computer back to its original state after the task runs. For Windows Vista and higher versions, you can select the Current Key option that is displayed in the list. If you select the Current Key option, then the product key is retained with the image. When you select the Current Key option in the Deploy image task, then the key that is captured is used on deploying the Windows image on the client computer.
If the license is not added to Deployment Solution, you can add one by clicking New. In the Add OS License Key dialog box, add the product key for the operating system that you select.
Enter credentials to rejoin a domain after capture is complete
Lets you join back the client computer to the domain after the task executes.
Specify the credentials to join the domain in the User name , Password, and the Confirm password fields.
This option is applicable for the Windows operating system only.
Lets you select the environment to which you want to boot the client computer before you start the image creation process.
In case of Linux, only x86 architecture type is supported.
You can either select from either of the following options:
Select this option to boot the client computer in the Automation environment. Automation environment is created on the client computers on which the automation folder is installed. Automation folders are specific to operating systems.
Select this option if you want to boot the client computer in the preboot environment.
For the PXE image, select any of the following architectures from the drop-down list:
Select this option if you want to boot the client computer based on the computer's processor architecture. For example, if you have a client computer whose processor type is x64 but the installed operating system is x86 of Windows 7, then the Auto option boots the computer in x64 architecture mode and not in x86 mode.
The Auto option can be useful if you have created a common PXE image for both x86 and x64 architectures or want to boot a computer as per the processor architecture irrespective of the OS architecture. You create PXE images through the Create Preboot Configuration dialog box of the console.
Select this option if the PXE image that you have created is for the x86 architecture of the operating system.
Select this option if the PXE image that you have created is for the x64 architecture of the operating system.
The registration time period is the time period during which the client computer is un-enrolled from the Notification Server's registration policy. This happens only when the client computer tries to boot from one environment to another. Within the specified registration time, the client computer must again register back to the registration policy, failing which, the computer must be registered manually.
The default registration time that is displayed is the registration time that is set in the Global Settings page.