Symantec ALTIRIS DEPLOYMENT SOLUTION 7.1 - V1, DEPLOYMENT SOLUTION 7.1, ALTIRIS DEPLOYMENT SOLUTION 7.1 User Manual
Altiris™ Deployment Solution
from Symantec User Guide
Version 7.1
Altiris™ Deployment Solution for Clients from Symantec
User Guide
The softwaredescribed inthis bookis furnishedunder alicense agreementand maybe used
only in accordance with the terms of the agreement.
Documentation version 7.1
Legal Notice
Copyright © 2009-2010 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo are trademarks or registered trademarks of Symantec
Corporation or its affiliates in the U.S.and other countries. Other namesmay betrademarks
of their respective owners.
The product described in this document is distributed under licenses restricting its use,
copying, distribution, and decompilation/reverse engineering. No part of this document
may be reproduced in any form by any means without prior written authorization of
Symantec Corporation and its licensors, if any.
THE DOCUMENTATIONISPROVIDED "ASIS" AND ALLEXPRESS OR IMPLIEDCONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO
BE LEGALLYINVALID.SYMANTEC CORPORATIONSHALLNOT BELIABLEFOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,
PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED
IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The LicensedSoftware andDocumentation aredeemed to be commercial computer software
as definedin FAR 12.212 and subject to restricted rights as defined in FAR Section52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, and any successor regulations. Any use, modification, reproduction release,
performance, displayor disclosure of the Licensed Software and Documentation by the U.S.
Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation
20330 Stevens Creek Blvd.
Cupertino, CA 95014
http://www.symantec.com
Technical Support
Symantec Technical Support maintains support centers globally. Technical
Support’s primary role is to respond to specific queries about product features
and functionality.The Technical Support group also creates content forour online
Knowledge Base. The Technical Support group works collaboratively with the
other functional areas within Symantec to answer your questions in a timely
fashion. Forexample, theTechnical Supportgroup works with Product Engineering
and SymantecSecurity Response to provide alerting services andvirus definition
updates.
Symantec’s maintenance offerings include the following:
■ A range of support options that give you the flexibility to select the right
amount of service for any size organization
■ Telephone and Web-based support that provides rapid response and
up-to-the-minute information
■ Upgrade assurance that delivers automatic software upgrade protection
■ Global support that is available 24 hours a day, 7 days a week
■ Advanced features, including Account Management Services
For information about Symantec’s Maintenance Programs, you can visit our Web
site at the following URL:
www.symantec.com/techsupp/
Contacting Technical Support
Customers with a current maintenance agreement may access Technical Support
information at the following URL:
www.symantec.com/techsupp/
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be
at the computer on which the problem occurred, in caseit isnecessary to replicate
the problem.
When you contact Technical Support, please have the following information
available:
■ Product release level
■ Hardware information
■ Available memory, disk space, and NIC information
■ Operating system
■ Version and patch level
■ Network topology
■ Router, gateway, and IP address information
■ Problem description:
■ Error messages and log files
■ Troubleshooting that was performed before contacting Symantec
■ Recent software configuration changes and network changes
Licensing and registration
If yourSymantec product requires registration or a license key, accessour technical
support Web page at the following URL:
www.symantec.com/techsupp/
Customer service
Customer service information is available at the following URL:
www.symantec.com/techsupp/
Customer Service is available to assist with the following types of issues:
■ Questions regarding product licensing or serialization
■ Product registration updates, such as address or name changes
■ General product information (features, language availability, local dealers)
■ Latest information about product updates and upgrades
■ Information about upgrade assurance and maintenance contracts
■ Information about the Symantec Buying Programs
■ Advice about Symantec's technical support options
■ Nontechnical presales questions
■ Issues that are related to CD-ROMs or manuals
Maintenance agreement resources
If you want to contact Symantec regarding an existing maintenance agreement,
please contact the maintenance agreement administration team for your region
as follows:
contractsadmin@symantec.comAsia-Pacific and Japan
semea@symantec.comEurope, Middle-East, and Africa
supportsolutions@symantec.comNorth America and Latin America
Additional enterprise services
Symantec offers a comprehensive set of services that allow you to maximize your
investment in Symantec products and to develop your knowledge, expertise, and
global insight, which enable you to manage your business risks proactively.
Enterprise services that are available include the following:
These solutions provide early warning of cyber attacks, comprehensive threat
analysis, and countermeasures to prevent attacks before they occur.
Symantec EarlyWarning Solutions
These servicesremove theburden ofmanaging andmonitoring securitydevices
and events, ensuring rapid response to real threats.
Managed Security Services
Symantec Consulting Services provide on-site technical expertise from
Symantec andits trustedpartners. SymantecConsulting Servicesoffer avariety
of prepackaged and customizable options that include assessment, design,
implementation, monitoring,and management capabilities. Each is focused on
establishing andmaintaining the integrity and availability of your IT resources.
Consulting Services
Educational Services provide a full array of technical training, security
education, security certification, and awareness communication programs.
Educational Services
To access more information about Enterprise services, please visit our Web site
at the following URL:
www.symantec.com
Select your country or language from the site index.
Technical Support . ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .. 4
Chapter 1 Introducing Deployment Solution .... ......... ..... ..... ..... ..... ... 11
About Deployment Solution . ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... 11
Components of Deployment Solution ... ..... ..... ..... ..... ......... ..... ..... ..... 12
Chapter 2 Getting started with Deployment Solution . ..... ..... ..... .... 13
Using Deployment Solution .... ..... ..... ......... ..... ..... ..... ..... ......... ..... .. 13
About the Deployment Portal .. ......... ..... ..... ..... ..... ......... ..... ..... ..... .. 16
Using Deployment Solution for the first time ... ......... ..... ..... ..... ..... .... 18
Installing the Deployment plug-in ....... ..... ..... ..... ..... ......... ..... ..... ..... 19
About Deployment Solution policies . ..... ..... ......... ..... ..... ..... ..... ........ 20
Uninstalling the Deployment plug-in ... ..... ..... ..... ..... ......... ..... ..... ..... 22
Upgrading the Deployment plug-in ..... ..... ..... ..... ......... ..... ..... ..... ..... 23
About Deployment site server components .. ..... ..... ..... .... ..... ..... ..... ... 24
About PXE .. ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ... 24
Installing Deployment site server components .... ..... ..... ......... ..... ..... . 25
Chapter 3 Configuring Deployment Solution settings ......... ..... ..... . 29
Configuring deployment and migration settings ........ ..... ..... ..... ..... .... 29
About Sysprep imaging ...... ..... ..... ..... ..... ......... ..... ..... ..... ......... ..... . 32
Adding an OS license ... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... .. 33
Creating a PXE preboot image .... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... 33
Adding a driver for a preboot configuration .... ..... ..... .... ..... ..... ..... ..... 34
About automation folders .... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... 35
About configuring a PXE server ... ..... ..... ..... .... ..... ..... ..... ..... ......... ... 36
About initial deployment ... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... .. 36
Configuring the initial deployment settings ... ..... ..... ..... ......... ..... ..... . 36
Chapter 4 Running tasks and jobs . ..... ..... ..... ..... ......... ..... ..... ..... ..... .... 39
About deployment tasks and jobs . ..... ..... ......... ..... ..... ..... ..... ......... ... 39
Creating a deployment task . ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... . 42
Changing network settings .... ..... ......... ..... ..... ..... ..... ......... ..... ..... ... 43
Combining tasks into a job ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ... 44
Contents
Scheduling a deployment task .. ..... ..... ..... ......... ..... ..... ..... ..... ......... . 44
Checking the state of a task . ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... . 45
Starting computers in different modes ... ..... ......... ..... ..... ..... ..... ........ 46
Assigning jobs to an unmanaged computer ........ ..... ..... ..... ..... ......... .. 46
Copy File options .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... . 47
About wiping a disk . ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ...... 48
Partition Disk options ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... 49
About iLO power management ..... ..... ..... ......... ..... ..... ..... ..... ......... ... 50
Chapter 5 Imaging computers ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ... 51
About images .. ..... ..... ......... ..... ..... ..... ......... ..... ..... ..... ..... ......... .... 52
Deployment image types ... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... .. 52
About image resources ... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... 53
About disk image packages .... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ... 53
Deleting an image package ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ... 54
Deleting an image resource or personality resource .. ..... ......... ..... ..... .. 55
Creating and deploying an image ......... ..... ..... ..... ..... ......... ..... ..... .... 55
About preparing to capture a disk image .. ..... ..... ......... ..... ..... ..... ..... . 57
Prepare for Image Capture options ..... ..... ..... ..... ......... ..... ..... ..... ..... . 57
About deploying images to multiple computers .. ..... ..... ..... ......... ..... .. 58
About creating an image ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... . 59
Create Image options ..... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... 59
Advanced Create Image options ..... ..... ..... .... ..... ..... ..... ..... ......... ..... . 60
About deploying an image . ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... .. 61
Deploy Image options .... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... 62
Advanced Deploy Image options .... ..... .... ..... ..... ..... ..... ......... ..... ..... . 63
Restoring a backup image .... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... 63
Deploying new computers .... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... 64
Adding new system configuration settings . ..... .... ..... ..... ..... ..... ......... . 65
System configuration editor settings ... ..... ..... ......... ..... ..... ..... ..... .... . 66
Error 10010 ........ ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... .... 67
Chapter 6 Performing scripted OS installations .... ..... ..... ..... ..... .... .. 69
About scripted OS installations ..... ......... ..... ..... ..... ..... ......... ..... ..... .. 69
OS Files options .... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ... 70
Sample scripted OS job . ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ... 70
About Windows scripted OS installations ......... ..... ..... ..... ..... ......... ... 71
Install Windows OS options .... ..... ..... ......... ..... ..... ..... ..... ......... ..... .. 71
Contents8
Chapter 7 Migrating personality settings . ......... ..... ..... ..... ..... ......... .. 73
About PC Transplant .... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... . 73
About personality templates ... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... .. 74
About migration settings ... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... .. 76
Capturing user settings ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... .. 76
Capture options ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... .. 77
Distributing user settings . ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ... 78
Deploy options ... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... 79
Appendix A Example log files ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... .. 81
rd2D7C26.txt .... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ... 81
ClientImaging_Task.txt .. ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... . 82
Index .... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ......... ..... . 85
9Contents
Contents10
Introducing Deployment
Solution
This chapter includes the following topics:
■ About Deployment Solution
■ Components of Deployment Solution
About Deployment Solution
Deployment Solution lets you integrate standard deployment features with the
Symantec Management Platform. It lets you capture and deploy disk images,
migrate dataand systemconfigurations, andchange Windows and Linux operating
system settings.Because DeploymentSolution workswith SymantecManagement
Platform, you can now use Deployment Solution servers to share jobs and tasks,
images, and security roles. You can also take advantage of the Symantec
Management Platform features of hierarchy and replication in your Deployment
Solution environment.
Deployment Solution lets you perform the following tasks:
■ Capture and restore disk images.
■ Create and deploy Sysprep-enabled standard images.
■ Migrate user data and application settings.
■ Change network operating system settings.
■ Perform scripted OS installations.
See “Using Deployment Solution” on page 13.
See “Creating and deploying an image” on page 55.
1
Chapter
Deployment Solutionintegrates with the Task Server component of the Symantec
Management Platform. Task Server integration lets you combine deployment
tasks with inventory, software management, and many other tasks. This process
automates the management of the computers that are in your environment.
Components of Deployment Solution
Deployment Solution includes many of the tools that you might have used in the
traditional Deployment Solution product.
See “Using Deployment Solution” on page 13.
The main Deployment Solution tools are installed in the following default
installation locations on the Windows platform:
■ PC Transplant Editor
C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task
Handler\PCT\PCTEdit.exe
■ PC Transplant Wizard
C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task
Handler\PCT\PCTWiz.exe
■ Boot Disk Creator
C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task
Handler\bootwiz.exe
■ RapiDeploy ImageExplorer
C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task
Handler\rdeploy\imgexpl.exe
■ Ghost Image Explorer
C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task
Handler\ghost\Ghostexp.exe
■ Image Importer
C:\Program Files\Altiris\Altiris Agent\Agnets\Deployment\Task
Handler\Tools\ResourceImporterTool.exe
Introducing Deployment Solution
Components of Deployment Solution
12
Getting started with
Deployment Solution
This chapter includes the following topics:
■ Using Deployment Solution
■ About the Deployment Portal
■ Using Deployment Solution for the first time
■ Installing the Deployment plug-in
■ About Deployment Solution policies
■ Uninstalling the Deployment plug-in
■ Upgrading the Deployment plug-in
■ About Deployment site server components
■ About PXE
■ Installing Deployment site server components
Using Deployment Solution
You can use Deployment Solution to handle all of your deployment needs.
When you use Deployment Solution for the first time, you can access the First
Time Setup page to simplify the process. This page provides links to other pages
that letyou perform the initial steps that youneed to complete to use deployment
and migration.
See “Using Deployment Solution for the first time” on page 18.
2
Chapter
Table 2-1
Process for using Deployment Solution
DescriptionActionStep
You can see a summary of your environment
from the Deployment Solution portal page.
You can also use the slide-out panel to quickly
access the pages for discovering computers,
installing Deployment Solution, changing
common settings, running reports, and more.
See “Aboutthe DeploymentPortal” on page 16.
(Optional) Complete
common processes and
view asummary of your
environment from the
Deployment Portal.
Step 1
You can enable a policy that installs the
Deployment plug-into thecomputers thatyou
select.
See “Installing the Deployment plug-in”
on page 19.
Install the Deployment
plug-in.
Step 2
You can choose a default task to run after the
new computer starts. You can also add any
tasks that you want in the initial deployment
menu of the new computer.
You can also change many other deployment
settings.
See “Configuring deployment and migration
settings” on page 29.
Configure the
deployment settings.
Step 3
Getting started with Deployment Solution
Using Deployment Solution
14
Table 2-1
Process for using Deployment Solution (continued)
DescriptionActionStep
You can choose from several task types to
create deploymenttasks. Forexample, youcan
create a task that captures or deploys a disk
image.
See “About deployment tasks and jobs”
on page 39.
See “Creating a deployment task” on page 42.
You cancombine several tasks or jobs into one
job to run sequentially. You can also specify
condition statements for your job. Your tasks
execute only if they meet the conditions that
you specify.
See “Combining tasks into a job” on page 44.
You can schedule a task to run immediately or
at a later time that you specify. You can also
choose the computers that the task runs on.
See “Scheduling a deployment task”
on page 44.
You can check the status of your deployment
tasks by running a report.
See “Checking the state of a task” on page 45.
Create, schedule, and
run deployment tasks.
Step 4
You can create disk images to deploy to
multiple computers. You can also create
backup images that copy the contents of a
single computer.
See “About images” on page 52.
Image computers.Step 5
You can create a package that contains the
source files you specify for a scripted OS
installation.
See “About scripted OS installations”
on page 69.
Perform scripted OS
installations.
Step 6
You can migrate a computer’s settings and
user preferences to another computer using
personalities.
See “About PC Transplant” on page 73.
Create and distribute
personalities.
Step 7
15Getting started with Deployment Solution
Using Deployment Solution
Table 2-1
Process for using Deployment Solution (continued)
DescriptionActionStep
Deployment Solution provides the following
reports that you can access from the Reports
> All Reports > Deployment and Migration
menu:
■ Computers with Deployment Plug-in
Installed - A list of all of the managed
computers that have the Deployment
plug-in installed on them.
■ Computers with Deployment Tasks
Execution Status - A list of details about
all of the Deployment tasks that executed
so far.
View Deployment
reports.
Step 8
You can use integrated Lights-Out features to
remotely turn off and turn on HP servers.
See “About iLO power management”
on page 50.
(Optional) Remotely
manage HP servers.
Step 9
You canuse manyof thetools thatare included
in the traditional Deployment Solution
product.
See “Components of Deployment Solution”
on page 12.
(Optional) Use
additional deployment
tools.
Step 10
About the Deployment Portal
The Deployment Portal is the home page for Deployment Solution. It contains
several smallerwindows thatprovide asummary ofyour deployment environment.
You canfind the portal under the Home menu in the console.You can also change
the size of and collapse the details for some of the windows on the portal.
The portalalso provides a way to access the most commonDeployment pages and
processes through the slide-out panel. You can access the slide-out panel by
mousing over the > icon at the far left of the portal page. You can get to the same
pages that you can access from the Deployment Portal in other ways. However,
the portal provides a faster and more convenient way to access those pages from
one place.
See “Using Deployment Solution” on page 13.
Getting started with Deployment Solution
About the Deployment Portal
16
When you use Deployment Solution for the first time, you can access the First
Time Setup page. This page provides links to other pages that let you perform
the initial steps that you need to complete to use deployment and migration.
See “Using Deployment Solution for the first time” on page 18.
You can schedule a job or task from the Deployment Portal. You can either drag
the job or task to a computer or drag the computer to a job or task. You can also
assign jobs and tasks to an unmanaged computer.
See “Assigning jobs to an unmanaged computer” on page 46.
You can drag an organizational view (from the Computers pane) to a job or task.
Or, you can drag a job or task to an organizational view. You can also add a
computer to an organizational view by dragging it.
Table 2-2
Deployment Portal windows
DescriptionWindows
Displays a tree view of the managed computers that are in your
environment.
Computers
Displays a list of the managed computers that are in your
environment.
You can filter the computers that are listed by entering text in
the Search Computers box.
Computer View
Displays the current statistics for the computer that you select
in theComputerView pane. For example,the domain,IP address,
and operating system.
You can also perform several actions byclicking the appropriate
action link, such as restarting, scheduling a task, or configuring
the computer.
Details View
Displays a tree view of the jobs and tasks that are available.
See “Creating a deployment task” on page 42.
Jobs/Tasks
Displays the details of the currently selected job or task.
You can filter the jobs and tasks that are listed by entering text
in the Search Computers box.
Job/Task View
17Getting started with Deployment Solution
About the Deployment Portal
Table 2-2
Deployment Portal windows (continued)
DescriptionWindows
Displays a list of links to the common Getting Started, Settings,
and Reports options. These links open a new details window in
the Deployment Portal to help you perform processes such as
discovering and installing. You can also configure common
settings and run common reports from the panel.
For example, you can perform the following processes from the
panel:
■ Add OS licenses
■ Configure Sysprep imaging
■ Install an automation folder
■ Create preboot configurations
■ Configure a PXE server
■ Perform initial deployment
■ Install the Deployment plug-in
See “Configuringdeployment andmigration settings”on page29.
You canaccess thispanel bydragging your mouse over the arrow
at the left of the Development Portal.
Slide-out panel
For more information, search for topics on portal pages in the Symantec
Management Platform Help.
Using Deployment Solution for the first time
When you use Deployment Solution for the first time, you can access the First
Time Setup page. This page provides links to other pages that let you perform
the initial steps that you need to complete to use deployment and migration.
You can get to the same tasks that are listed on this page in other ways. However,
this list of links is a faster way to access all of the tasks.
See “Using Deployment Solution” on page 13.
See “About the Deployment Portal” on page 16.
To use Deployment Solution for the first time
1
In theSymantec ManagementConsole, on the Home menu, click Notification
Server Management > First Time Setup.
2
Under Deployment and Migration, click any of the items in the list to get
started.
Getting started with Deployment Solution
Using Deployment Solution for the first time
18
■ Add OS Licenses
See “Adding an OS license” on page 33.
■ Sysprep Imaging Configuration
See “Configuring deployment and migration settings” on page 29.
■ Configure Deployment Settings
See “Adding new system configuration settings” on page 65.
■ Preboot Configurations
See “Creating a PXE preboot image” on page 33.
■ PXE Server Configuration
See “About configuring a PXE server” on page 36.
■ Initial Deployment task setup
The primary NotificationServer hasall of the necessary components that
are required for full functionality. This taskcompletes all of the stepsthat
are necessary for a single computer to get set up and working.
See “Configuring the initial deployment settings” on page 36.
If you need the Automation Directory install, PXE, or have remote site
servers, access these policies directly.
See “About Deployment Solution policies” on page 20.
■ Install Deployment Plug-in
See “Installing the Deployment plug-in” on page 19.
You can expand each link for a description of that task.
3
After you complete each task, click the green circle in front of that task to
add a checkmark.
Installing the Deployment plug-in
The Deployment plug-in lets you capture and deploy disk images, migrate the
data settings and the personality settings, and change your system settings. This
environment is used to manage the computers that are outside of the operating
system.
The Deployment plug-in replaces the former Deployment Solution agents, such
as AClient, DAgent, or ADLAgent. If you need them, AClient and DAgent can
coexist with the Deployment plug-in.
You can enable the Symantec firewall on the client computer and enable the
Windows firewall on Notification Server. However, to install the Deployment
plug-in by pushing it to computers, you need to disable one of these firewalls.
19Getting started with Deployment Solution
Installing the Deployment plug-in
Default policies to install, upgrade, and uninstall the Deployment plug-in are
provided with Deployment Solution. It provides installation policies for 32-bit
clients only. You can create your own 64-bit automation packages and policies
using the preboot configuration options. You can then install the policy on your
target computer.
See “About Deployment Solution policies” on page 20.
See “About automation folders” on page 35.
See “Using Deployment Solution” on page 13.
To install the Deployment plug-in
1
In the Symantec Management Console, on the Settings menu, click
Agent/Plug-ins > All Agents/Plug-ins.
2
In the left pane, expand the Agents/Plug-ins > Deployment and Migration
folders.
3
Choose eithera Linux or Windows installation and expand the corresponding
folder.
4
Click the install policy that you want to use.
5
In the right pane, in the Program name box, ensure that the correct policy
is selected.
6
Under Applied to, select the computers that you want to install the plug-in
on.
7
Under Schedule, select when you want to install the plug-in.
8
(Optional) ClickAdvanced to check if the computers you selected areavailable
at the exact time that you scheduled.
You can also select start and end dates on this page.
9
Under Extra schedule options, select the options that you want.
10
Ensure that the policy is enabled.
A green On symbol shows in the top right corner.
11
Click Save changes.
About Deployment Solution policies
Deployment Solution provides several predefined policies. These policies let you
install the Deployment plug-in and other software on the managed computers in
your environment.
Getting started with Deployment Solution
About Deployment Solution policies
20
Each policy uses a filter that specifies the computers that it affects. Also, policies
update theirtargeted computers after those computers request any policy updates.
You can access each policy by clicking the Settings menu and then expanding the
Agents/Plug-ins and Deployment and Migration folders. We provide predefined
policies for the Windows and Linux platforms.
See “Using Deployment Solution” on page 13.
Deployment Solution provides the following policies:
Table 2-3
Deployment Solution predefined policies
DescriptionPolicy name
Installs theautomation WIMin theboot
directory on the targeted client
computers. The automation WIM lets
you quickly reboot to the WinPE
environment.
See “About automation folders”
on page 35.
Deployment Automation Folder - Install
Uninstalls the automation WIM that
was previously installed.
Deployment Automation Folder - Uninstall
Installs and registers the plug-in that
the task agent uses when a
Deployment-specific task is defined.
See “Installingthe Deploymentplug-in”
on page 19.
Deployment Plug-in - Install
Uninstalls theDeployment Plug-inthat
was previously installed.
See “Uninstalling the Deployment
plug-in” on page 22.
Deployment Plug-in - Uninstall
Downloads an upgraded plug-in to the
computers thatdon’t havethe specified
version.
See “Upgrading the Deployment
plug-in” on page 23.
Deployment Plug-in - Upgrade
21Getting started with Deployment Solution
About Deployment Solution policies
Table 2-3
Deployment Solution predefined policies (continued)
DescriptionPolicy name
Installs thesite servercomponents that
can offload most of thetraffic and data
from the primary Notification Server.
When a managed computer is assigned
a deployment task, these components
instruct a task handler to load and
perform the task.
See “Installing Deployment site server
components” on page 25.
Deployment Site Server Components - Install
Uninstalls the site server components
that were previously installed.
DeploymentSite Server Components - Uninstall
Downloads the upgraded site server
components to the computers that
don’t have the specified version.
Deployment Site Server Components - Upgrade
Uninstalling the Deployment plug-in
You can uninstall the Deployment plug-in by using the plug-in uninstall policy.
This policy is turned off by default.
To use this policy, turn off the install policy. Otherwise, the plug-in can be
reinstalled as soon as it is uninstalled.
See “Installing the Deployment plug-in” on page 19.
After the policy is turned on, the plug-in is uninstalled from all computers that
meet the criteria of the filter. If you change the Applied to option to Computers,
you can select individual computers.
See “About Deployment Solution policies” on page 20.
To uninstall the Deployment plug-in
1
In the Symantec Management Console, on the Settings menu, click
Agent/Plug-ins > All Agents/Plug-ins.
2
In the left pane, expand the Agents/Plug-ins > Deployment and Migration
folders.
3
Expand the folder for your operating system.
4
Click the uninstall policy.
Getting started with Deployment Solution
Uninstalling the Deployment plug-in
22
5
In the right pane, in the Program name box, ensure that the correct policy
is selected.
6
Under Appliedto, select the computers thatyou want to uninstall the plug-in
from.
7
Under Schedule, select when you want to uninstall the plug-in.
8
(Optional) ClickAdvanced to check if the computers you selected areavailable
at the exact time that you scheduled.
9
Under Extra schedule options, select the options that you want.
10
Ensure that the policy is enabled.
A green On symbol shows in the top right corner.
11
Click Save changes.
Upgrading the Deployment plug-in
You can upgrade the Deployment plug-in by using the upgrade policy. This policy
is turned off by default.
The upgrade policy uses filters to determine if an upgrade is necessary. You can
access the filters that are used from the Manage > Filters > Software Filters >
Agent and Plug-in Filters menu.
See “About Deployment Solution policies” on page 20.
To upgrade the Deployment plug-in
1
In the Symantec Management Console, on the Settings menu, click
Agent/Plug-ins > All Agents/Plug-ins.
2
In the left pane, expand the Agents/Plug-ins > Deployment and Migration
folders.
3
Click the Deployment Plug-In - Upgrade policy.
4
In the right pane, in the Program name box, ensure that the correct policy
is selected.
5
Under Appliedto, select the computers that you want to upgrade the plug-in
on.
6
Under Schedule, select when you want to upgrade the plug-in.
7
(Optional) ClickAdvanced to check if the computers you selected areavailable
at the exact time that you scheduled.
8
Under Extra schedule options, select the options that you want.
23Getting started with Deployment Solution
Upgrading the Deployment plug-in
9
Ensure that the policy is enabled.
A green On symbol shows in the top right corner.
10
Click Save changes.
About Deployment site server components
The site server components in Deployment Solution let you offload some of the
traffic and workload from your primary Notification Server. You can set up
multiple site servers, task servers, and Deployment site servers to handle your
jobs andtasks. SymantecManagement Agentthen uses their assigned Deployment
site server for all deployment processes. These processes include imaging, disk
partitioning, and tasks that are associated with Personality Packages.
See “Installing Deployment site server components” on page 25.
The Deployment site server components can be installed on the site servers that
are configured with both Package Services and Task Services. For more
information, search for task server topics in the Symantec Management Platform
Help.
The components include the task handlers that are added to the Task Service.
The handlers let the Site Service forward deployment tasks to an assigned
computer. The components also include all of the tools that Deployment Solution
needs. These tools include RapidDeploy, Ghost, and Boot Disk Creator.
See “Components of Deployment Solution” on page 12.
The Deployment site server that is assigned to each computer also includes a
Deployment share.Any files that need to be downloaded or written by Deployment
Solution processes are stored in that Deployment share. Deployment Solution
never tries to read or write a file on any other Notification Server or site server.
If thefile to be downloaded does not exist,the Deployment task fails. If you attempt
to write a file that cannot be created on the share, that task also fails.
The site server components also include the PXE service.
See “About PXE” on page 24.
About PXE
Pre-boot eXecutionEnvironment (PXE) is an environment that you can useto boot
computers using a network interface. This process is independent of your hard
disks or installed operating systems.
Deployment site server components include PXE. You cannot uninstall PXE from
a computer without uninstalling all of the deployment components.
Getting started with Deployment Solution
About Deployment site server components
24
See “About Deployment site server components” on page 24.
You can configure PXE by using the PXE server configuration policy. However,
changing this policy automatically affects PXE on all Deployment site servers in
your environment.
See “About configuring a PXE server” on page 36.
The preboot configuration policy also affects all Deployment site servers. After
each Deployment site server processes this policy, PXE offers the same bootstrap
menu andimages to clients that boot to PXE. EachDeployment site server receives
this policyfrom Notification Server and implements the policy settings ina preboot
image. The site server creates new preboot images each time it receives new
preboot policy configurations. If you remove configurations from the preboot
policy, the site server removes the corresponding preboot images.
See “Creating a PXE preboot image” on page 33.
Do not try to clone the PXE policies. If you make changes to a cloned policy copy,
unknown consequences might occur. You cannot determine what version of the
policy Deployment Solution implemented.
You can manually add drivers for a preboot image.
See “Adding a driver for a preboot configuration” on page 34.
You can have more than one Deployment site server on a broadcast domain.
However, all Deployment site servers on this kind of domain should be assigned
to the same Symantec Management Platform site.
For example, if a client on this domain sends a PXE request, you cannot tell which
Deployment site server might respond. If the responding server doesn’t know
that a PXE reboot task exists, the server instructs the client to boot from the next
available device. Usually that device is the hard drive. All client computers with
a PXE reboot task must receive a PXE reboot image, no matter which site server
responds. All Deployment site servers that are assigned to the same Symantec
Management Platform site receive instructions to supply the corresponding
preboot image.
Installing Deployment site server components
You caninstall Deployment site server components to create taskserver handlers.
These components are installed on Symantec Management Platform site servers.
The components let the site servers manage the deployment-related tasks. The
tasks canbe scheduled to run immediately or at a later specified time. This process
improves scalability.
See “About Deployment site server components” on page 24.
25Getting started with Deployment Solution
Installing Deployment site server components
See “About Deployment Solution policies” on page 20.
Note: Before installing the Deployment components on a site server, you should
install the Package Service and Task Service on that site server. The Package
Service runs on many different operating systems. However, the Task Service is
supported only on Windows XP SP3 and Windows Server 2003 SP2.
All Deployment computer images and Personality Packages are created on the
task server that each managed computer works with. To deploy an image that
was created on a different task server, you must replicate that image to your task
server. You can replicate the image using the basic package replication that is
contained in Symantec Management Platform. You can also configure specific
replication rules for disk image packages.
You must install the site server components before you can replicate packages,
including driver packages. After the components are installed, your packages
become valid and can then be replicated.
You canuninstall and upgrade the components by choosing the appropriate policy
and following those steps.
For moreinformation, search for site server and taskserver topics in the Symantec
Management Platform Help.
To install Deployment site server components
1
In the Symantec Management Console, on the Settings menu, click
Agent/Plug-ins > All Agents/Plug-ins.
2
In the left pane, expand the Agents/Plug-ins > Deployment and Migration
> Windows folders.
3
Click the Deployment Site Server Components - Install policy.
4
In the right pane, in the Program name box, ensure that the correct policy
is selected.
5
Under Applied to, select the computers that you want to install the
components on.
6
Under Schedule, select when you want to install the components.
7
(Optional) ClickAdvanced to check if the computers you selected areavailable
at the exact time that you scheduled.
8
Under Extra schedule options, select the options that you want.
Getting started with Deployment Solution
Installing Deployment site server components
26
9
Ensure that the policy is enabled.
A green On symbol shows in the top right corner.
10
Click Save changes.
27Getting started with Deployment Solution
Installing Deployment site server components
Getting started with Deployment Solution
Installing Deployment site server components
28
Configuring Deployment
Solution settings
This chapter includes the following topics:
■ Configuring deployment and migration settings
■ About Sysprep imaging
■ Adding an OS license
■ Creating a PXE preboot image
■ Adding a driver for a preboot configuration
■ About automation folders
■ About configuring a PXE server
■ About initial deployment
■ Configuring the initial deployment settings
Configuring deployment and migration settings
Using the Settings > Deployment and Migration menu, an administrator can
perform several tasks. These tasks include managing packages, configuring
deployment-specific settings, and managing OS licenses.
The tasksin the following table are listed in the suggested order that you complete
them the first time you use Deployment Solution. However,you can also complete
these tasks in the order that you need them.
See “Configuring the initial deployment settings” on page 36.
3
Chapter
Table 3-1
Deployment and migration settings options
DescriptionActionStep
You can browse to and
upload the Deploy.cab
file.
See “About Sysprep
imaging” on page 32.
Configure yourSysprep optionsusing the Sysprep
Imaging Configuration option.
Step 1
You can track all of
your licenses for all of
your operating
systems. You can also
add licenses on this
page.
See “Adding an OS
license” on page 33.
Add a license using the OS Licenses option.Step 2
You can create your
PXE preboot
configuration settings.
From your
configuration settings,
a PXE image is also
created through a
task-based policy at a
site server level. You
can also set up a PXE
image for an
unmanaged computer.
See “Creating a PXE
preboot image”
on page 33.
You canconfigure your
PXE server in another
step.
See “Aboutconfiguring
a PXE server”
on page 36.
Create your PXE configuration using the
Symantec Boot Services (PXE) > Preboot
Configurations option.
Step 3
Configuring Deployment Solution settings
Configuring deployment and migration settings
30
Table 3-1
Deployment and migration settings options (continued)
DescriptionActionStep
You can install an
automation folder
using a policy.
See “Aboutautomation
folders” on page 35.
(Optional) Install automation folders.Step 4
You canconfigure your
PXE server and select
which PXE boot image
to use. You can also
limit the bandwidth
that is used and how
many computers
receive theautomation
at one time.
See “Aboutconfiguring
a PXE server”
on page 36.
Configure your PXE server using the Symantec
BootServices(PXE)> PXE Server Configuration
option.
Step 5
You cansee thedrivers
that are in your
deployment
environment. You can
manage the drivers
database package that
DeployAnywhere uses.
By default,the package
replicates to all of the
site servers in your
environment.
See “Adding a driver
for a preboot
configuration”
on page 34.
Add drivers to the Drivers list.Step 6
31Configuring Deployment Solution settings
Configuring deployment and migration settings
Table 3-1
Deployment and migration settings options (continued)
DescriptionActionStep
You can set the task
list fora newcomputer
that boots to the
network.
See “Configuring the
initial deployment
settings” on page 36.
See “About initial
deployment”
on page 36.
Determine what Deployment jobs or tasks run
when anunknown computer performs a PXE boot
using the Initial Deployment option.
Step 7
About Sysprep imaging
Sysprep isthe Microsoftutility that prepares computers for Windows deployments.
All Windowsplatforms after Windows XP include Sysprep files as part of the basic
OS installation.
When you use the Prepare for Image capture task, Deployment Solution
automatically uses the Sysprep files. However, for that task to work on Windows
XP, you must upload its deploy.cab file into Deployment Solution using the
Sysprep Imaging Configuration option.
When you work with Microsoft domains, each computer must use a unique
Windows SID. SIDs are security IDs that are used with Windows NT and later
operating systems. Before you deploy Windows images, you should remove the
existing SID from a computer to avoid causing network problems. The Prepare
for Image capture task automatically strips the SIDs from each computer using
Sysprep.
You canthen create an image using the Create image task and deploy the resulting
image to multiple computers.
Sysprep also disables the built-in administrator account and clears the
administrator passwordwhen it prepares a computer for imaging. You might need
to change thepassword onthe clientcomputer beforelogging on for the first time
after deploying an image.
See “Configuring deployment and migration settings” on page 29.
Configuring Deployment Solution settings
About Sysprep imaging
32
Adding an OS license
Before you use Sysprep with a Deployment job or task, you need to select the OS
and thecorresponding OS license for the job. This informationmust be configured
before the job is created.
See “About Sysprep imaging” on page 32.
The OS Licenses list stores the Volume License Keys (VLKs) that deploy the
Sysprep-enabled images.
See “Configuring deployment and migration settings” on page 29.
See “Using Deployment Solution” on page 13.
To add an operating system license
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, expand the Settings > Deployment and Migration folders.
3
Click OS Licenses.
4
In the right pane, click Add.
5
Choose the operating system.
6
Type the product key.
7
(Optional) Type a description for the license.
8
Click OK.
Your new license displays in the OS Licenses list.
Creating a PXE preboot image
The Preboot Configuration page lets you add a new policy for a preboot
configuration. Afteryou have a configuration, you can useit to create a PXE image.
Tasks canthen access and use that specific preboot configuration-based image.The
preboot configuration can also be used to create preboot installation files.
See “About PXE” on page 24.
This process also creates a resource that can be used to reboot to a task. You can
also use the resource to reboot to any job that requires you to reboot to PXE.
If the preboot policy is enabled, the server starts building the PXE image after the
server requests an updated configuration.
See “Configuring deployment and migration settings” on page 29.
33Configuring Deployment Solution settings
Adding an OS license
To create a PXE preboot image
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In theleft pane,expand the Settings > Deployment andMigration > Symantec
Boot Services (PXE) folders.
3
Click Preboot Configurations.
4
In the right pane, click Add.
5
On the Add Preboot Configuration page, enter a name and description for
your preboot configuration.
6
Select either the WinPE or Linux operating system.
7
For Windows, select the x86 or x64 architecture.
For Linux, only the x86 architecture is supported.
8
Select the OEM extension to use.
9
Select the preboot environment to build.
■ PXE -This preboot configuration can be accessed only from the PXEserver.
Only the client computers that are configured to boot to and from their
network card can access the configuration.
■ Automation folder - This preboot configuration can be installed on the
client computer by using policies.
■ Both PXE and Automation folder - This option builds both types of
configurations.
10
Click OK.
11
Ensure that the policy is enabled.
A green On symbol shows in the top right corner.
12
Click Save changes.
Adding a driver for a preboot configuration
You can use Boot Disk Creator to add the drivers that your preboot PXE
configurations need.
See “About PXE” on page 24.
If you want to install otherdrivers, create a sharedfolder that holds thosedrivers.
Then, add the path of your driver folder to a custom answer file. Make sure that
you include any credentials that are needed.
Configuring Deployment Solution settings
Adding a driver for a preboot configuration
34
BootWiz.exe is stored in the \Program Files\Altiris\Altiris
Agent\Agents\Deployment\Task Handler\bootwiz directory.
See “Configuring deployment and migration settings” on page 29.
To add a driver for a preboot configuration
1
Run BootWiz.exe.
2
In Boot Disk Creator, choose the option to create a new configuration.
3
On Step 1, enter a name for the configuration.
4
Select the type of preboot operation system that you want to add a driver to.
5
Click Next.
6
On Step 2, click the Have Disk or Internet option, and select the new driver
to add.
The driver is added.
7
On Step 2 of 4, click Cancel.
The new driver is used when you create a new configuration.
If a preboot configuration that you already created needs your new driver, you
must regenerate that driver. You can regenerate the driver by selecting the
configuration from the Preboot Configuration view and clicking the Recreate
Preboot Environment link in its menu.
About automation folders
Automation folders store preboot operating systems. Some deployment tasks
require that a client computer first boot to a preboot operating system. You can
get a preboot operating system from a PXE server or from an automation folder
that is installed on the client computer.
You can install an automation folder using a predefined Deployment policy.
See “About Deployment Solution policies” on page 20.
The automation folder stores WinPE and most of the information it needs to
perform an imaging task in a Boot.wim file.
For automation to work, your network must include DHCP and DNS. Also, all
computers in your network must be able to perform a Name Server Lookup.
WinPE 2.1 and Linux arethe only automation operating systems thatDeployment
Solution supports. Both systems are installed with Deployment Solution.
See “Configuring deployment and migration settings” on page 29.
35Configuring Deployment Solution settings
About automation folders
About configuring a PXE server
You can configure the PXE server that was automatically installed when you
installed Deployment Solution.
See “About PXE” on page 24.
You can install multiple PXE servers by installing and configuring the site server
components on a computer that is running Site Services. For more information,
search for site server topics in the Symantec Management Platform Help.
You can select the PXE boot image to use and choose to respond to unknown
computers while configuring your PXE server. You can set the threshold on the
number of computers that receive the automation simultaneously bymarking the
Limit client connections option. You can also set the amount of bandwidth to use
during the PXE process by marking the Limit bandwidth option.
See “Configuring deployment and migration settings” on page 29.
About initial deployment
Initial deploymentspecifies what jobs or tasks run when an unmanagedcomputer
performs a PXE boot.
See “Configuring the initial deployment settings” on page 36.
The unmanaged computer boots from a network card and asks for a PXE server.
The PXE server hears this request and compares the computer against its list of
known computers. After the server determines that the computer is unknown it
sends a preboot operating system to the computer. This operating system is the
same system that you configured in the PXE Server Configuration option.
After the unknown computer receives the preboot PXE image, the preboot
PECTAgent runs and requests a task server. Because the computer is unknown,
it receives an initial deployment menu that contains a preconfigured job or task.
According to the set schedule, this job or task then runs.
See “Configuring deployment and migration settings” on page 29.
Configuring the initial deployment settings
You can create an ISO image that contains the initial deployment settings that
you specify. Your ISO image can then be used to start new computers. The boot
image contains the tasks that you want in the initial deployment menu of the new
computer. It also specifies how long those tasks display on the new computer.
See “About initial deployment” on page 36.
Configuring Deployment Solution settings
About configuring a PXE server
36
See “Configuring deployment and migration settings” on page 29.
See “Using Deployment Solution” on page 13.
To configure the initial deployment settings
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, expand the Settings > Deployment and Migration folders.
3
Click Initial Deployment Settings.
4
Select howlong to display the task menu before the default task is performed.
5
Select whetherto run a default task orto turn off the computer after it initially
starts.
6
Add any tasks that you want displayed in the Initial Deployment menu.
7
(Optional) Select the default task.
8
Click Save changes.
37Configuring Deployment Solution settings
Configuring the initial deployment settings
Configuring Deployment Solution settings
Configuring the initial deployment settings
38
Running tasks and jobs
This chapter includes the following topics:
■ About deployment tasks and jobs
■ Creating a deployment task
■ Changing network settings
■ Combining tasks into a job
■ Scheduling a deployment task
■ Checking the state of a task
■ Starting computers in different modes
■ Assigning jobs to an unmanaged computer
■ Copy File options
■ About wiping a disk
■ Partition Disk options
■ About iLO power management
About deployment tasks and jobs
Deployment Solutionmanages computersusing tasksand jobs.Tasks are individual
processes, such as creating an image or capturing a computer’s personality. Each
task can be scheduled and run.
Jobs are a combination of tasks. Each task can be assigned to specific computers,
and each task specifies the order in which each task runs.
4
Chapter
You must create each task before it appears in your Manage > Jobs and Tasks >
System Jobs and Tasks > Deployment and Migration list.
See “Creating a deployment task” on page 42.
See “Combining tasks into a job” on page 44.
See “Scheduling a deployment task” on page 44.
See “Checking the state of a task” on page 45.
If a computer does not yet have the Symantec Management Agent or the
Deployment plug-in installed, you can import a predefined computer. Predefined
computers let you assign jobs to unmanaged computers.
See “Assigning jobs to an unmanaged computer” on page 46.
You can create Client Jobs and Server Jobs in Symantec Management Platform.
These two job types are identical with one exception. Server Jobs guarantee that
the exact same task sequence and execution path is followed for all nodes. For
example, the logic for a job specifies that the job stops if one of the tasks fails.
When that task fails out or times in one node, that job stops for all of the nodes.
Deployment Solution provides the following predefined tasks.
Table 4-1
Predefined deployment tasks
DescriptionTask
Applies the new configurations to a computer.
See “Adding new system configuration settings”
on page 65.
Apply System Configuration
Uses PCTransplant tocapture acomputer’s settings
and files (personality).
See “Capturing user settings” on page 76.
Capture Personality
Copies thespecified files and folders to a destination
computer.
See “Copy File options” on page 47.
Copy File
Creates disk images and backup images.
See “About creating an image” on page 59.
Create Image
Deploys the backup image files (not backup image
files).
See “About deploying an image” on page 61.
Deploy Image
Running tasks and jobs
About deployment tasks and jobs
40
Table 4-1
Predefined deployment tasks (continued)
DescriptionTask
Installs apreviously capturedcomputer personality.
See “Distributing user settings” on page 78.
Distribute Personality
Cleans a disk. You can configure this task to meet
DoD standards.
See “About wiping a disk” on page 48.
Erase Disk
Performs a scripted OS install of Linux.
See “About scripted OS installations” on page 69.
Install Linux OS
Performs a scripted OS install of Windows.
See “About scripted OS installations” on page 69.
Install Windows OS
Creates the disk partitions on a hard drive.
See “Partition Disk options” on page 49.
Partition Disk
Runs Microsoft Sysprep.
See “About Sysprep imaging” on page 32.
See “About preparing to capture a disk image”
on page 57.
Prepare for Image capture
Instructs a computer to boot to the production OS,
PXE, or automation folder.
See “Starting computers in different modes”
on page 46.
Reboot To
Deploys thebackup imagefiles (notdisk imagefiles).
See “Restoring a backup image” on page 63.
Restore BackUp Image
You canalso create many other types of tasks that workwith Deployment Solution
to add more functionality. For example, you can create the following types of
tasks:
■ A RunScript task that lets you use a scripting language such asPerl or Python.
The RunScript task supports manyscripting languagesand predefined tokens.
For more information, search for run script task topics in the Symantec
Management Platform Help.
■ An inventory task that gathers much more information than the Deployment
Solution reports provide. The inventory tasks are listed in the Symantec
41Running tasks and jobs
About deployment tasks and jobs
Management Console on the Create New Task page under Discovery and
Inventory.
■ A PowerControl task that provides many ofthe capabilities that were included
in previousversions ofthe Deployment Solution product. For more information,
search for power control task topics in the Symantec Management Platform
Help.
■ A PowerManagement task that integrates out-of-bounds (OOB) management
capabilities withtraditional Deployment Solution tasks. For more information,
search for power management topics in the Real-Time Console Infrastructure
Help.
Creating a deployment task
You can create many kinds of deployment tasks, such as changing the Windows
system settings or applying a predefined system configuration setting. You can
also capture or deploy a disk image or personality and create or restore a backup
image.
See “About deployment tasks and jobs” on page 39.
After a deployment task is created, it is listed under the Jobs and Tasks >
Deployment and Migration folder. Click any task to view the properties of that
task. You can drag and drop tasks to other folders and manually create folders.
Any folders that you create do not display until you create a task or job in that
folder. Several tasks can also be combined into one job.
See “Combining tasks into a job” on page 44.
A task cannot be deleted if it is currently in use by a job or policy. You can use the
Jobs and Tasks view to see what jobs and policies use each task.
Tasks can be renamed, deleted, cloned, moved, and scheduled by right-clicking
the task and selecting the corresponding option.
See “Changing network settings” on page 43.
See “Using Deployment Solution” on page 13.
You can use the Deployment Portal to search for your jobs and tasks.
See “About the Deployment Portal” on page 16.
To create a deployment task
1
In the Symantec Management Console, on the Manage menu, click Jobs and
Tasks.
2
In the right pane, click Create a new job or task.
Running tasks and jobs
Creating a deployment task
42
3
On the Create New Task page, in the left page, expand the Deployment and
Migration folder.
4
Click one of the task types.
5
Add any necessary information, and choose the options you want.
Make sure that you give your task a unique and meaningful name.
6
Click OK.
7
Schedule the task.
See “Scheduling a deployment task” on page 44.
Changing network settings
You can apply a system configuration to a computer. You can update a computer
name, join a domain, or change network settings.
See “Creating a deployment task” on page 42.
To change network settings
1
In the Symantec Management Console, on the Manage menu, click Jobs and
Tasks.
2
In the right pane, click Create a new job or task.
3
On the Create New Task page, in the left pane, expand the Deployment and
Migration folder.
4
Click Apply System Configuration.
5
(Optional) In the right pane, select a predefined configuration.
You can click Edit configuration to edit an existing configuration.
See “System configuration editor settings” on page 66.
You canalso choose to restore the system configuration by using the inventory
data.
6
If the target computer is in a Domain, select the corresponding check box.
Enter the credentials for the Domain.
7
Click OK.
8
Schedule the task.
See “Scheduling a deployment task” on page 44.
43Running tasks and jobs
Changing network settings
Combining tasks into a job
You canuse jobs to group several tasks together, so that they all run consecutively.
You can combine deployment-specific tasks with other tasks in a single job.
Jobs also have the condition statements that you can specify. Your tasks are then
executed only if they meet the conditions that you specify.
Jobs can be renamed, deleted, cloned, moved, and scheduled by right-clicking the
job and selecting the corresponding option.
You can drag and drop jobs to other folders and manually create folders. Any
folders that you create do not display until you create a task or job in that folder.
You can use the Deployment Portal to search for your jobs and tasks.
See “About the Deployment Portal” on page 16.
For more information, search for topics on creating a job in the Symantec
Management Platform Help.
See “Using Deployment Solution” on page 13.
To combine tasks into a job
1
In the Symantec Management Console, on the Manage menu, click Jobs and
Tasks.
2
In the left pane, right-click the folder where you want the job to be stored in,
and then click New Client Job or New Server Job.
3
In the right pane, create or add the tasks you want.
You can click New to add new jobs or tasks to your job. You can also click Add
Existing to add existing jobs or tasks to your job.
You can use the arrows to order the tasks.
See “Creating a deployment task” on page 42.
4
Select whether the job should fail if any task fails.
5
Click OK.
You can edit, order, and add or delete the tasks in a job. Right-clicking selects the
job that you want to change, and then you can use the options in the right pane.
Scheduling a deployment task
You can schedule a task to run immediately or at a time that you specify. You can
also choose the computers that the task runs on.
Running tasks and jobs
Combining tasks into a job
44
You can schedule a job or task from the Deployment Portal. You can either drag
the job or task to a computer or drag the computer to a job or task.
See “About the Deployment Portal” on page 16.
See “Using Deployment Solution” on page 13.
To schedule a task
1
In the Symantec Management Console, on the Manage menu, click Jobs and
Tasks.
2
In the left pane, expand the Jobs and Tasks > System Jobs and Tasks >
Deployment and Migration folders.
3
Click the job that you want to schedule.
4
(Optional) If you want the task to run immediately, in the right pane, click
Quick Run. Select the name of the computer that you want the task to run
on, and then click Run.
You can schedule the task to run on only one computer using the Quick Run
option.
5
If you want to schedule the task to run at a later time or you want to schedule
multiple computers, click New Schedule.
6
Choose the date and time that you want the task to run.
You can also select the task to run at specific intervals.
7
Select the Run Options that you want.
8
Select the computers that you want the task to run on.
9
Click Schedule.
Checking the state of a task
You can check the state of any tasks that previously ran.
See “About deployment tasks and jobs” on page 39.
See “Using Deployment Solution” on page 13.
You can choose different options for your report, and then click Refresh to see
the updated results.
To check the state of a task
1
In the Symantec Management Console, on the Reports menu, click All
Reports.
2
In the right pane, expand the Reports > Deployment and Migration folders.
45Running tasks and jobs
Checking the state of a task
3
Click Computers with Deployment Tasks Execution Status.
4
Select the name of the tasks that you want to check the status of.
5
Select a status.
6
Select an image name.
7
Select a timeframe.
The report runs, and the right pane is updated with the information that you
requested.
Starting computers in different modes
You can start computers in automation mode to run tasks, such as scripts. You
can choose to reboot to a PXE preboot environment or a production mode.
Do not mix PXE with automation partitions or folders on a client. You can use
PXE or automation partitions or folders but not both environments together.
Assign this task only if you want to perform a custom automation task.
See “About deployment tasks and jobs” on page 39.
To start computers in different modes
1
In the Symantec Management Console, on the Manage menu, click Jobs and
Tasks.
2
In the right pane, click Create a new job or task.
3
On theCreateNew Task page, under Deployment and Migration, clickReboot
to.
4
Click the mode that you want.
5
Click OK.
6
Schedule the task.
See “Scheduling a deployment task” on page 44.
Assigning jobs to an unmanaged computer
You can import a predefined computer to assign jobs to unmanaged computers.
An unmanaged computer does not yet have the Symantec Management Agent or
the Deployment plug-in installed on it.
See “About deployment tasks and jobs” on page 39.
Running tasks and jobs
Starting computers in different modes
46
When a computer performs a PXE Boot , the PXE process reports the new
computer’s MAC address, serial number, or BIOS UUID. From this information,
Notification Server can identify the computer and run any tasks or jobs that are
assigned to that computer.
You can also perform the same task by using the Settings menu and clicking All
Settings > Deployment and Migration.
See “About the Deployment Portal” on page 16.
To assign jobs to an unmanaged computer
1
In theSymantec ManagementConsole, onthe Home menu, click Deployment
Portal.
2
Click the slide-out panel.
3
Under Settings, select Predefined Computers.
4
In the right pane, click the Import Computers icon, and then navigate to a
.txt or a.cvs file that contains the information about thecomputer toimport.
You can copy a sample Pre-DefinedComputers.csv file from the \Program
Files\Altiris\Notification
Server\NSCap\bin\Win32\X86\Deployment\Sample\PreDefinedComputers
folder.
Copy File options
You can use the Copy File task to install files and applications. You can copy the
installation .msi or .exe file by running this task. Then, you can install the
application by using command-line switches.
See “About deployment tasks and jobs” on page 39.
You must create a deployment task before you can run it.
See “Creating a deployment task” on page 42.
You can configure the following options while creating this task.
Table 4-2
Copy File options
DescriptionOption
The item that is copied. You can include subfolders.Copy file and Copy folder
47Running tasks and jobs
Copy File options
Table 4-2
Copy File options (continued)
DescriptionOption
The source of the file to copy. You can provide a local
path or select an existing file from the Deployment
share.
If you want to copy a file that is not on Notification
Server, make sure that you provide the credentials for
the file. For the UNC option to work, you must provide
the domain (or machine name) with the user name in
the domain\username format.
Any changes you make to a local file are not
automatically updated in the Copy File task. For
example, you copy a local file using this task and then
make changes to that file. If you rerun the task, the
same file that you previously copied is used. You must
modify yourtask first and select the same file to ensure
that your changes are correctly copied.
Source
The location to the files to upload or the location of
files that are already uploaded.
Location
The credentialsthat you need to obtain the source files.Source credentials
The location where the files are copied to.Destination
The optional command-line instructions.Command Line
The credentials that are needed to execute the
command-line instructions.
Credentials
About wiping a disk
You can use the Erase Disk task to wipe a disk clean. When you reallocate
hardware, youcan use this task to ensure thatnone of the old data can beretrieved.
See “About deployment tasks and jobs” on page 39.
You can choose to erase only the system disk. Or, you can configure the task to
erase all of the disks, including any attached USB/FW drives.
You must mark the Secure erase (DOD Compliant option) check box to perform
a Department ofDefense (DoD)compliant wipe.If youchoose thisoption, thetask
wipes data according to the U.S. Department of Defense 5220.22-M standard.
According to the DoD standard, the following group of operations is performed
on the hard drive six times:
Running tasks and jobs
About wiping a disk
48
■ All addressable locations are overwritten with 0x35.
■ All addressable locations are overwritten with 0xCA.
■ All addressable locations are overwritten with a pseudo-random character.
■ All addressable locations are verified in hardware using the Verify Sectors
command to the disk.
If you do not select the DoD option, these operations are performed only once.
Note: Using the Secureerase option, this task has a 36-hour timeout value on the
task server. If this task runs on a client that has a hard disk larger than 375 GB,
the task reports as failed on the task server. However, the task continues to run
on the client until it completes.
You must create a deployment task before you can run it.
See “Creating a deployment task” on page 42.
Partition Disk options
You can run the Partition Disk task to create partitions on a disk drive.
See “About deployment tasks and jobs” on page 39.
Before you perform a scripted OS installation, your drive must have partitions.
See “About scripted OS installations” on page 69.
The drive that you want to partition must not contain any previous partitions on
it. If the drive was previously used and contains partitions, you can use the Erase
Disk task to delete those partitions.
See “About wiping a disk” on page 48.
You must create a deployment task before you can run it.
See “Creating a deployment task” on page 42.
You can configure the following options while creating this task.
Table 4-3
Partition Disk options
DescriptionOption
The drive that the partition is created on.Disk Number
The format of the partition: Fat32, NTFS, and EXT.Format
49Running tasks and jobs
Partition Disk options
Table 4-3
Partition Disk options (continued)
DescriptionOption
The type of partition to create: Extended, Logical,
Primary. By default, Primary partitions are created.
Partition
The partition is active. This option is selected
automatically for Primary partitions.
Mark Partition as Active
The size of the partition as a percentage of the total
drive.
Size - Percent
The size of the partition as a specific size.Size - Fixed Size
About iLO power management
Integrated Lights-Out (iLO) power management lets you remotely manage HP
servers. You can use iLO power management to effectively unplug and plug in a
computer.
iLO power management works only when the correct version of the sm2user.dll
file is installed. HP installs this DLL, and it must be version 8.11.00.0 or later to
enable iLO functionality in Symantec Management Platform.
You can see the iLO capabilities of a specific server by using the Manage >
Computers menu. Then, right-click a server name in your list and click the iLO
Power Management option. From the resulting menu, you can turn on and turn
off that computer. You can also click Interfaces to view the remote Web console
interface for that computer.
For more information about iLO, see the HP Web site.
See “Using Deployment Solution” on page 13.
Running tasks and jobs
About iLO power management
50
Imaging computers
This chapter includes the following topics:
■ About images
■ Deployment image types
■ About image resources
■ About disk image packages
■ Deleting an image package
■ Deleting an image resource or personality resource
■ Creating and deploying an image
■ About preparing to capture a disk image
■ Prepare for Image Capture options
■ About deploying images to multiple computers
■ About creating an image
■ Create Image options
■ Advanced Create Image options
■ About deploying an image
■ Deploy Image options
■ Advanced Deploy Image options
■ Restoring a backup image
■ Deploying new computers
5
Chapter
■ Adding new system configuration settings
■ System configuration editor settings
■ Error 10010
About images
Computer images contain the entire contents of a computer’s hard drive. These
contents include the operating system, applications, and user data. For Windows,
you can create images using either Ghost or RapiDeploy. Both are included in
Deployment Solution. Only RapiDeploy is supported for Linux. Images that are
created using Ghost cannot be deployed using multicasting.
See “About deploying images to multiple computers” on page 58.
You can create disk images or backup images.
See “Deployment image types” on page 52.
When you run a task to create an image, the following steps occur:
■ An image file is created
■ A Notification Server package is created (for disk images only)
See “About disk image packages” on page 53.
■ A resource for the image is added to the CMDB
See “About image resources” on page 53.
A new folder and image file is created each time that you run a task to capture an
image. Ifyou run the same task on the same computer three times, you have three
different folders and image files for that computer.
You can do one of the following things to avoid the duplication problem:
■ Edit the disk creation task to use a unique image name.
■ Create a new task that you configure to use a different image name.
Images are created on the task server that the source computer is configured to
work with.
Deployment image types
Deployment Solution lets you create two types of computer images.
See “About images” on page 52.
See “Creating and deploying an image” on page 55.
Imaging computers
About images
52
Table 5-1
Deployment image types
DescriptionImage
Can bedeployed tomultiple computers(provisioning). These images
are saved in a Notification Server package and can be distributed
to other package servers.
You should run the Prepare for Image capture task on the source
computer to ensure that a unique SID is created.
See “About Sysprep imaging” on page 32.
Disk image
Backs up a single computer. These images should be deployed only
to the same computer they were created from. They should not be
deployed to multiple computers.
These images are not saved in a package and cannot be distributed
to other package servers through the replication process.
Backup image
About image resources
When an image is created, a Notification Server resource for that image is also
created. The image resource is used when you build tasks to deploy your images.
See “About images” on page 52.
The SymantecManagement Console uses the resource list to display what images
can be deployed. However, the console does not verify if the image file already
exists. If your image file is deleted from the server, it is still possible to create a
task to deploy the deleted image. In this case, the task fails.
You can view a list of your image resources from the Manage > All Resources >
Default > All Resources > Software Component > Image Resource menu. You
can also right-click a resource to access the Resource Manager.
If you delete the image resource name using the Resource Manager, it does not
delete the physical imagefile from theserver. After youdelete the imageresource
name, you must remove the image file from the server.
See “Deleting an image package” on page 54.
See “Deleting an image resource or personality resource” on page 55.
About disk image packages
A NotificationServer package is created for alldisk images when you run theDisk
Image task. You can then use this package to distributethe image to other package
servers.
53Imaging computers
About image resources
See “About images” on page 52.
Disk images are stored on the Deployment share of the Deployment site server.
Each image is stored in a separate folder that is specified by a GUID. Information
about the image is also stored in the CMDB as an image resource.
See “About Deployment site server components” on page 24.
You can view your disk image packages from the Deployment Portal or from the
Manage > All Resources > Default > All Resources > Package menu. You can also
view them from the Settings > All Settings > Deployment and Migration > Disk
Images menu.
You can configure how the image package is distributed to additional package
servers using the Settings > All Settings menu. After you select the package you
want, you can then select what servers get the image from the Package Servers
tab.
You can choose from the following package distribution options:
■ All package servers
■ Individual package servers
■ Package servers by site
■ Package servers automatically with manual prestaging
You can also delete packages.
See “Deleting an image package” on page 54.
Deleting an image package
Image packages are created when you create a disk image. Both an image package
and an image resource are created in addition to the actual image file.
See “About disk image packages” on page 53.
To deleteall image references from the database, youalso need to delete the image
resource or personality resource.
See “Deleting an image resource or personality resource” on page 55.
To delete an image package
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, expand the Settings and the Deployment and Migration
folders.
3
Click Disk Image Packages.
Imaging computers
Deleting an image package
54
4
Right-click the image package that you want to delete.
5
Click Delete.
The package is deleted.
Deleting an image resource or personality resource
You must remove the image resourceor personality resource tocompletely delete
an imagereference. These steps also apply to backup images and PCT personalities.
To delete all image references from the database, you need to delete the image
package first.
See “Deleting an image package” on page 54.
To delete an image resource or personality resource
1
In theSymantec ManagementConsole, on the Manage menu, click Resource.
2
From the Group drop-down menu, select Image Resource.
3
On the Select Resource page, click the image that you want to delete.
4
Click OK.
The Resource Manager displays some of the details of the image that you
selected. The path to the image file is not listed.
5
In the left pane, click Delete.
The resource link is deleted from the database, but the actual image file is
not deleted from disk. You need to delete the image file manually.
Creating and deploying an image
For Windows, the images that are deployed to multiple computers are prepared
using Microsoft Sysprep to remove drivers, the security ID (SID), and other
computer-specific settings.Sysprep alsodisables the built-in administrator account
and clears the administrator password. You can also use the Prepare for Image
Capture task on Linux to remove all configuration-specific settings.
See “About Sysprep imaging” on page 32.
Before you perform this process, you must prepare the reference computer that
you want to image.
See “About images” on page 52.
See “About deployment tasks and jobs” on page 39.
55Imaging computers
Deleting an image resource or personality resource
You can also use multicasting to simultaneously deploy an image to multiple
computers.
See “About deploying images to multiple computers” on page 58.
Table 5-2
Process for creating and deploying an image
DescriptionActionStep
The reference computer contains the core
software andsettings thatyou wantto useon each
computer.
See “About preparing to capture a disk image”
on page 57.
Prepare a reference
computer for imaging.
Step 1
You need to copy the
support\tools\deploy.cab file from your
Windows XP installation disk or service pack to
the c:\sysprep\deploy.cabfile on the source
computer.
See “About Sysprep imaging” on page 32.
Sysprep files are included with Vista.
(XP and Windows 2003
only) Install Sysprep
files on the reference
computer.
Step 2
The operating system license isused to re-license
your reference computer after Sysprep runs.
See “Adding an OS license” on page 33.
For Linux, this step is optional.
Add an operating
system license.
Step 3
You can create disk images and backup images.
See “About creating an image” on page 59.
Create an image.Step 4
You can deploy an image that you previously
created.
See “About deploying an image” on page 61.
Deploy an imageStep 5
You can restore the exact state that a computer
was in when it was imaged.
See “Restoring a backup image” on page 63.
(Optional) Restore the
backup image that you
previously created.
Step 6
You can use Initial Deployment to image the new
computers in your environment.
See “Deploying new computers” on page 64.
Deploy images to new
computers.
Step 7
Imaging computers
Creating and deploying an image
56
About preparing to capture a disk image
You can run the Prepare for Image Capture task to get ready to deploy a disk
image to multiple computers.
See “About deployment tasks and jobs” on page 39.
See “Creating and deploying an image” on page 55.
For Windows, this task uses Sysprep to remove the computer name (SID), the
operating system license, and some hardware-dependent drivers. You should
always runthis 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.
See “About Sysprep imaging” on page 32.
You can choose several options while creating this task.
See “Prepare for Image Capture options” on page 57.
You must create a deployment task before you can run it.
See “Creating a deployment task” on page 42.
Prepare for Image Capture options
You can configure the following options while creating the Prepare for Image
Capture task.
See “About preparing to capture a disk image” on page 57.
Table 5-3
Prepare for Image Capture options
DescriptionOption
The name of the task. The name field is not
labeled.
Name
The typeof operating system the taskis runon.OS type
An operating system license that can be used
to restorethe computer back to its original state
after the task runs. If the license has not been
added to Deployment Solution, youcan add one
by clicking New.
Product key
A description of the license. You must create
the description when you add the license.
Description
57Imaging computers
About preparing to capture a disk image
Table 5-3
Prepare for Image Capture options (continued)
DescriptionOption
The targetmachine belongs to a domain. When
the task runs, it removes the computer from
any domains. This option rejoins the computer
back to its original domain after the task runs.
Target Machine is in Domain (not in
workgroup)
The credentials that the computerneeds to join
the domain again.
Enter credentials to rejoin a domain
after capture is complete
The preboot type to use to start the image
creation process.
Reboot to
About deploying images to multiple computers
You canuse multicastingto simultaneously deploy images to a group of computers.
You use the options on the Image Multicasting page to specify the IP range, port
range, and other settings to use with multicasting.
See “About images” on page 52.
See “Creating and deploying an image” on page 55.
Deployment Solutionuses the multicasting abilities of the RapiDeploy application.
RapiDeploy is more efficient when it writes directly to the IP address. You can
enter a range of IP addresses when using themulticasting feature for faster image
deployment. Because some network cards do not handle multiple multicast
addresses, you can also identify a range of ports to identify the computers.
Table 5-4
Image Multicasting options
DescriptionOption
The range of IP addresses to use for image deployment.IP range
The range of port numbers to use for image deployment.Port range
The minimum number of clientsthat need to be partof the group
before multicasting is used.
Threshold
The maximum speed to use when multicasting to avoid flooding
the network with too much traffic. As this number increases,
there is a greater chance for dropped packets and slower speeds
to occur.
Speed
Imaging computers
About deploying images to multiple computers
58
Table 5-4
Image Multicasting options (continued)
DescriptionOption
The maximum number of seconds to wait for the specified
number of clients to join the group. If this number is reached,
your images are deployed separately.
Timeout
About creating an image
You can create disk images and backup images with the Create Image task.
See “Deployment image types” on page 52.
See “About deployment tasks and jobs” on page 39.
You must create a deployment task before you can run it.
See “Creating a deployment task” on page 42.
You can deploy disk images to multiple computers. This process removes all of
the Windowsoperating systemsettings from any captured images. Your computer
restarts multiple times during this process.
See “Creating and deploying an image” on page 55.
Backup images retain the data and software of a specific computer. A backup
image contains a snapshot of the hard disk of a computer. A backup image can be
restored only to the computer that it was captured from. The image has the same
name as the computer from which it was captured.
By default,the first disk in the system is imaged using Ghost inoptimize for speed
mode. Other imaging tools are also available.
You can choose several options while creating this task.
See “Create Image options” on page 59.
You can also choose advanced imaging options for this task.
See “Advanced Create Image options” on page 60.
Create Image options
You can configure the following options while creating the Create Image task.
See “About creating an image” on page 59.
You can also set up advanced imaging options for this task.
See “Advanced Create Image options” on page 60.
59Imaging computers
About creating an image
Table 5-5
Create Image options
DescriptionOption
The name of the task. This field is not labeled.Name
The name of the image file to create. Each time this task
runs, anew image file is created. Enter aunique nameevery
time you run this task.
Image Name
A description of the image to create.Description
The name of the imaging tool you want to use. The tool is
either Ghost or RapiDeploy.
Imaging tool
The type of image you want to create. The type is either a
disk image or a backup image.
See “Deployment image types” on page 52.
Imaging type
Advanced Create Image options
The Advanced option on the Create Image task lets you configure additional
options.
See “About creating an image” on page 59.
You can choose several other options while creating this task.
See “Create Image options” on page 59.
Table 5-6
Advanced Create Image options
DescriptionOption
Determines atwhat pointan imagefile issplit into multiple
files. Themaximum sizedepends onthe imagingtool (Ghost
or RapiDeploy).
Media
Lets you add command-line options for the imaging tool.Command-line
Lets you create an image using an http:// Web address.
You need to set up the Internet Information Services (IIS)
Manager to get HTTP imaging to work. Otherwise, if you
try to use HTTP with the Create Image task, the job fails
and returns a message that the file could not be created.
HTTP
Imaging computers
Advanced Create Image options
60
About deploying an image
You can restore a computer and deploy a standard, Sysprep-enabled disk image
with theDeploy Image task. All ofthe existing data and applications on theclient
are lost, and the computer is restored to the state of the standard image.
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 plaintext password. You canthen use the answer
file while you deploy your images on remote computers.
See “About Sysprep imaging” on page 32.
See “Deployment image types” on page 52.
See “About deployment tasks and jobs” on page 39.
If thecomputer has the Deployment plug-in installed, the computerconfiguration
is saved and restored after the image is applied. The computer configuration
contains the computer name, network settings, and domain.
See “Creating and deploying an image” on page 55.
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.
See “Deploying new computers” on page 64.
If the computer is a member of a domain, supply the appropriate credentials to
rejoin the domain.
You can create an image that retains its data and software by creating a backup
image.
See “About creating an image” on page 59.
You must create a deployment task before you can run it.
See “Creating a deployment task” on page 42.
For Linux operating systems, deploying disk images and backup images does not
fully support the reiser file system. Image deployment supports only the SUSE
Ext3 filesystem. If you have a reiser partition, you must use the -raw switch when
you image the partition to preserve its structure.
You can choose several options while creating this task.
See “Deploy Image options” on page 62.
You can also set up advanced imaging options for this task.
61Imaging computers
About deploying an image
See “Advanced Deploy Image options” on page 63.
Deploy Image options
You can configure the following options while creating the Deploy Image task
See “About deploying an image” on page 61.
For Linux, only the Name and Image Name fields are necessary. All of the other
fields are optional.
You can also set up advanced imaging options for this task.
See “Advanced Deploy Image options” on page 63.
Table 5-7
Deploy Image options
DescriptionOption
The name of the task. This field is not labeled.Name
The name of the image file to deploy.Image Name
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 andlater versionsof theWindows operatingsystem.
Product Key
An option that runs DeployAnywhere after the image is
deployed. DeployAnywhere runs while the computer is
still running the WinPE preboot operating system. This
option discovers what type of hardware is on the
destination computer and creates a new HAL. The HAL
and the required drivers that Sysprep removed are then
deployed to help the computer boot successfully.
DeployAnywhere worksonly from within a WinPE preboot
operating system.
DeployAnywhere
■ Generate Sysprep configuration file using inventory
data
The required information is obtained from the CMDB.
■ Custom Sysprep configuration file
The required information is obtained from a custom
Sysprep file that you created.
Sysprep
Imaging computers
Deploy Image options
62
Table 5-7
Deploy Image options (continued)
DescriptionOption
The credentials that are needed to join the computer to a
domain.
Credentials
Advanced Deploy Image options
The Advanced option on the Deploy Image task lets you configure additional
options.
See “About deploying an image” on page 61.
You can also set up other imaging options for this task.
See “Deploy Image options” on page 62.
Table 5-8
Advanced Deploy Image options
DescriptionOption
Determines what partitions are deployed. You can change
the destination partition size by clicking the partition
number.
Partition
Lets you add command-line options for the imaging tool.Command-line
Lets youconfigure thenumber ofcomputers to run the task
before the image is multicast. You can change the default
settings.
If the threshold count is 2, there must be at least two client
computers and one master computer before multicasting is
used in this session.
Multicasting issupported onlywith theRapiDeploy imaging
tool.
Multicasting
Adds the credentials that are needed to deploy an image
that was obtained from an HTTP site.
HTTP
Restoring a backup image
The computers that you image are restored to the exact state they were in when
the image was created. A backup disk image can be restored only to the computer
from which it was captured.
63Imaging computers
Advanced Deploy Image options
Deployment Solution uses %computername% as the default name of the backup
image.
You can use the Advanced settings to preserve any files that are on the disk.
See “Creating and deploying an image” on page 55.
See “About deployment tasks and jobs” on page 39.
To restore a backup image:
1
In the Symantec Management Console, on the Manage menu, click Jobs and
Tasks.
2
In the right pane, click Create a new job or task.
3
On the Create New Task page, click Restore Backup Image.
4
Select the image name to restore.
5
(Optional) Click Advanced to specify additional parameters.
The additional parameters include the following options:
■ Partition resizing settings
■ Command-line switches for the imaging engine (Ghost or RapiDeploy)
■ Files and folders to preserve in the target computer during an image
restore
Click OK to save your options.
6
Click OK.
7
Schedule the task.
See “Scheduling a deployment task” on page 44.
Deploying new computers
You can set up new computers using a standard image. You can then start those
computers withan automation disk that loads the software to executea predefined
task server task. The predefined task can deploy a disk image and install software.
Imaging computers
Deploying new computers
64
Table 5-9
Process for deploying new computers
DescriptionActionStep
For Windows, you can use Microsoft
Sysprep to prepare images. Sysprep
removes drivers,the security ID (SID), and
other computer-specific settings.
See “Creating and deploying an image”
on page 55.
Capture a Sysprep-enabled
image for distribution to
multiple computers.
Step 1
You canspecify theSysprep-enabled image
that you captured and the system
configuration that you want to apply to
new computers.
See “About deploying an image”
on page 61.
See “Adding new system configuration
settings” on page 65.
Create a Deploy Image task.Step 2
You can add tasks to the start menu of a
new computer.
Add the Deploy Image task to
your initial deployment menu.
Step 3
You can boot computers with PXE using a
network interface. This process is
independent ofyour harddisks orinstalled
operating systems.
See “About PXE” on page 24.
Reboot the client using PXE.Step 4
A new computer is defined as a computer
that is not known to the database. An
Initial Deployment task can be used only
on new computers.
Start the new computer using
the automationdisk, andselect
the task that you created from
the Initial Deployment menu.
Step 5
Adding new system configuration settings
The systemconfiguration settings contain the network, domain, and other settings
that are applied to computers after they are imaged.
When you distribute a generic Sysprep-enabled image, the system configuration
settings are applied to the computer for the initial setup. The same configuration
settings can be applied to multiple computers using the name range feature.
You cancreate a backup image or distribute a Sysprep-enabled image to computers
that have the Deployment plug-in installed on them. In this case, you can choose
65Imaging computers
Adding new system configuration settings
to retain and restore all existing configuration settings. You can also choose to
reconfigure these settings.
See “Configuring deployment and migration settings” on page 29.
See “About deployment tasks and jobs” on page 39.
See “Using Deployment Solution” on page 13.
To add a new system configuration
1
In the Symantec Management Console, on the Settings menu, click All
Settings.
2
In the left pane, expand the Settings > Deployment and Migration folders.
3
Click System Configurations.
4
In the right pane, click New system configuration.
5
On the Create System Configuration page, type a name and description for
the new configuration settings.
6
On the Computer Name tab, enter a computer name or choose a name range.
You can also specify a Workgroup, Domain, or Organizational unit.
See “System configuration editor settings” on page 66.
7
To change the configuration for a domain, enter the administrative domain
credentials at the bottom of the page.
8
On theNetwork Adapters tab, choose a domain suffix, the number ofnetwork
adapters, and other IP address settings.
9
Click OK.
System configuration editor settings
You can create or update system configuration settings with the configuration
editor. These settings are applied to computers after you deploy a disk image or
apply a system configuration using a task server.
The credentials are either a local administrator account or a domain account (if
you join the computer to a domain).
See “Adding new system configuration settings” on page 65.
Imaging computers
System configuration editor settings
66
Table 5-10
System configuration editor settings
DescriptionSettingTab
You can select Leave existing for a
computer that is not stored in the
database. In this instance, the default
name that the Windows installation
generates is used.
Computer NameComputer Name
This option lets you use the same
configuration for multiple computers.
Computers are named using a fixed
string and a value. Additionally, if you
use a name range with a static IP
address on the Network tab, the IP
address you specify is incremented as
well.
The fixed text appears before the
number range. If the append option is
selected, the text appears after the
number range.
The range is the number that you want
to start with. This stringincrements by
1 for each computer that receives the
configuration.
Name RangeComputer Name
This tab lets you specify network
settings and provide a starting IP
address if using the Name Range
feature.
If youchange an IP address from DHCP
to static, you need to supply the subnet
mask and gateway. Even if they are the
same as they were when you used
DHCP, you need to supply these
numbers. These values are not stored
when you use DHCP.
IP address optionsNetwork Adapters
Error 10010
If you try to deployan image before thatimage is properlyreplicated to additional
site servers, youmight seeerror 10010.This errorcan alsooccur whendisk image
packages are not properly replicated before tasks are scheduled against them. In
either case, the failure is expected.
67Imaging computers
Error 10010
On the client computer, Ghost reports an error message similar to the following
statement:
Error 10010: Cannot open image file \\SITHSITESVR2\DEPLOYMENT\TASK
HANDLER\IMAGE\58A46937-EE86-40A3-B288-16FDB5DE9018\XPT EST.GHO
[WIN32 error:(0x00000003) The system cannot find the path specified.]
The client computer usually only reports that the Failed Deploy Disk
Image_DeployImage task failed.
RapidDeploy uses logs (rather than the onscreen errors that Ghost reports). If an
image does not exist on the site server that it is registered with, you might see
error logs.
See “rd2D7C26.txt” on page 81.
See “ClientImaging_Task.txt” on page 82.
Error 10010 could occur if the following conditions were met:
■ A Symantec Management Console server exists in your environment that has
multiple site servers.
■ The source of a successful CaptureDisk Image job ofComputer 1to siteserver
1 is set at \\SiteServer1\Images\GUID.
■ The administratorcreates aDeploy Image job to Computer 2, which is registered
with site server 2.
■ The task is scheduled before you use the All Settings option in the Symantec
Management Console and before you choose to replicate the disk image.
In this case, the client computer cannot execute the command because the image
is not yet on site server 2. It exists only on site server 1 until it has properly
replicated throughout each site.
You might also see this error if the task started before the image was replicated
from the parent site to the child site. In this case, you might see this error at a
child site in a hierarchy.
Imaging computers
Error 10010
68
Performing scripted OS
installations
This chapter includes the following topics:
■ About scripted OS installations
■ OS Files options
■ Sample scripted OS job
■ About Windows scripted OS installations
■ Install Windows OS options
About scripted OS installations
You can create an operating system package and decide what source files are
included in that package. The source files include all of the files that are needed
for a scripted install. You can use the Install Windows OS or Install Linux OS
tasks to perform a scripted install for Windows or Linux.
See “About Windows scripted OS installations” on page 71.
You can add filesto yourpackage usingthe OS Files link in the Deployment Portal
and by clicking Add Files.
See “About the Deployment Portal” on page 16.
You can provide a name, provide a description, and choose the platform for your
package.
See “OS Files options” on page 70.
6
Chapter
You can also delete files from your package. Only the package that is in the
database is deleted. If your physical files exist in other places, the files are not
deleted from those locations.
See “About deployment tasks and jobs” on page 39.
See “Sample scripted OS job” on page 70.
OS Files options
You can add files to your package in the Deployment Portal. Under Settings in
the slide-out panel, you can use the OS Files link to configure the import
parameters for your package. You must have JRE 1.5 or later installed to add files
to your package.
See “About the Deployment Portal” on page 16.
You can browse to the location of your source files that you want to add. Source
files are located in the Program Files\Altiris\Altiris
Agent\Agents\Deployment\Task Handler\SOI directory.
See “About scripted OS installations” on page 69.
Table 6-1
OS Files options
DescriptionOption
The name that you want assigned to your file package.Name
A description for your OS package.Description
The platform for the operating system.Platform
Sample scripted OS job
A scripted OS installation job can contain other tasks.
See “About scripted OS installations” on page 69.
The following sample task list assumes that the disk contained data previously
and that it is known in the CMDB:
■ Reboot to PXE
Loads a preboot operating system so that other tasks can run.
■ Erase Disk
Wipes the disk clean, ensuring that all data and all partitions are erased.
■ Partition Disk
Performing scripted OS installations
OS Files options
70
Configures the clean drive with a partition.
■ Install Windows OS
Runs the scripted install for the Windows operating system.
■ Reboot to Production
Reboots the computer to the final production operating system.
This task is not required for Windows Vista and later operating systems.
About Windows scripted OS installations
You canrun the Install Windows OS task toinstall the Windows operating system.
See “About scripted OS installations” on page 69.
See “About deployment tasks and jobs” on page 39.
Before you run this task, your hard drive must have the proper partitions. You
might need to run the Partition Disk task first to create partitions on your hard
drive.
See “Partition Disk options” on page 49.
You must create a deployment task before you can run it.
See “Creating a deployment task” on page 42.
This task downloads a program that installs the Symantec Management Agent.
After the agent is installed, the install policy installs the Deployment plug-in if
the policy is on.
You can choose from several options while creating this task.
See “Install Windows OS options” on page 71.
Install Windows OS options
You can configure the following options while creating this task.
See “About Windows scripted OS installations” on page 71.
Table 6-2
Install Windows OS options
DescriptionOption
The source of your operating system. You can use the
drop-down list to select a previously installed operating
system. Youcan alsoadd operatingsystems byclicking Add.
OS source
71Performing scripted OS installations
About Windows scripted OS installations
Table 6-2
Install Windows OS options (continued)
DescriptionOption
The license for the operating system. You can use the
drop-down list to select a previously added license. You can
also add licenses by clicking Add.
Product Key
The configuration options.
■ Use Inventory data to reconfigure computer
Uses the information that is stored in the CMDB to
rename and configure the computer.
■ Use default configuration settings
Uses the default settings.
■ Configuration file
Uses a custom answer file.
Configuration
The advancedoptions. Theseoptions includea specificdrive
to install the operating system on. You can also set the
region for the language and keyboard and the type of video
settings to use.
Advanced
Performing scripted OS installations
Install Windows OS options
72
Migrating personality
settings
This chapter includes the following topics:
■ About PC Transplant
■ About personality templates
■ About migration settings
■ Capturing user settings
■ Capture options
■ Distributing user settings
■ Deploy options
About PC Transplant
PC Transplant is included with Deployment Solution. PC Transplant uses a
wizard-driven interface to help you capture and distribute a computer’s
personality. Personalities are the files that contain the user data and application
settings. Personalities contain the documents, the registry settings, and the
configuration files that are associated with applications. They also contain many
other windows settings. Personalitiesare usuallycaptured aspart ofan operating
system migration or as a backup.
You can choose what settings to transplant.
See “About migration settings” on page 76.
PC Transplant does not support server operating systems, such as Windows 2003
server, Windows 2008 server, etc.
7
Chapter
PC Transplant also does not support 64-bit operating systems, so you cannot
create or distribute personalities for 64-bit systems.
See “Capturing user settings” on page 76.
See “Distributing user settings” on page 78.
You can distribute a personality through a self-extracting executable file that is
called a Personality Package. PC Transplant lets you create the Personality
Packages that can be used for multiple purposes.
Packages can include the desktop, printer, network, application settings (such as
favorites and contacts), and entire directory structures for your computers. You
can create packages that contain the most used directories, documents, and
settings for a group of computers. You can also create packages for individual
users on a shared computer. A user can then install the Personality Package on a
computer. After completing their work, each user can then uninstall the package
so the computer is ready for another user.
You can also perform a real-time migration from one computer to another. In
real-time migrations,you can map users and their properties, create useraccounts,
and install applications.
Personality Packages are based on the templates that you can run from
command-line instructions to automate operating system migrations. You can
build and edit your own templates to define the settings, file, and options that
you want for your Personality Packages.
See “About personality templates” on page 74.
Note: In a hierarchy, the Deployment Solution license must be installed on each
Notification Server to use PC Transplant and manage personalities. Licenses for
PC Transplant are not replicated to child Notification Servers.
For more information about PC Transplant, in your browser, go to
http://kb.altiris.com and search for topics on PC Transplant and personalities in
the Altiris Knowledgebase.
About personality templates
Before you create a Personality Package, you must tell PC Transplant what type
of informationto migrate. You can provide this type of informationin a personality
template file.
See “About PC Transplant” on page 73.
Migrating personality settings
About personality templates
74
A template file contains information about the settings and files that you want
to migrate. Using a template reduces errors and allows deployment jobs to
automatically create packages.
See “About migration settings” on page 76.
When you create a job to capture personalities, you must use a template. If you
haven’t created a template yet, you can use one of the default templates that are
included with Deployment Solution.
You can use one of the following files to create a template:
■ Template.exe, located in the PCT subfolder of the Deployment share.
■ PCTEdit.exe, locatedin the PCT subfolder of the Deployment share. Selecting
the Tools > Template Builder option from the editor’s menu lets you edit an
existing template or create a new one.
The first template option is to select the type of users to migrate.
You can specify either local or domain users.
■ Capture Local Users
Migrates the settings for local users. By adding the domain to the Redirect to
domain field, you can also migrate users to pre-existing domain accounts.
■ Capture Domain Users
You can migrate all of the users in a domain by selecting the Capture domain
users option. You can also choose to migrate specific users by adding the user
in the source and destination fields.
You canuse your templates as a separate utility or aspart of a Deployment Solution
job.
See “About deployment tasks and jobs” on page 39.
A deployment job might automatically modify the following template settings:
■ -qm switch
The quiet minimized switch is used unless a token is specified for the name
of the package.
■ Advanced users
The users that are specified in the job’s Advanced option and the template’s
users are both used.
■ Package path
The path in the deployment job is used for the package instead of the path in
the template.
75Migrating personality settings
About personality templates
About migration settings
You can choose what settings to migrate.
You can choose to migrate settings from the following categories:
■ Computer desktop settings
These settings includeControl Panelsettings, desktopcolors, andbackground
information.
■ Individual files and folders
■ Specific file types
■ Network settings
These settings include the computer and domain name, folder and drive share
assignments, and drive mappings for Windows.
■ Application settings
These settingsinclude the unique menu bar options for a particularapplication.
However, PC Transplant is not designed to migrate applications. A2i text files
determine the application settings that can be migrated and include the
Word.a2i, MS Outlook.a2i, andWinZip.a2i files. Over 65 A2i files are included
with Deployment Solution. You can also create custom A2i files using the A2i
Builder utility.
Personality templates determine the individual files and folders to migrate. The
computer that you use to build the Personality Package registers the file types
that you can choose to migrate.
See “About personality templates” on page 74.
You determine what desktop and network settings to migrate based on the text
files that are called Settings Files. These files are included with Deployment
Solution and PC Transplant and include the Dsktop*.ini and Ntwrk*.ini files.
See “About PC Transplant” on page 73.
Capturing user settings
You can capture a computer’s personality with the Capture Personality task.
Deployment Solution uses PC Transplant to capture and distribute personalities.
You can also choose how much data to capture, whether the files are compressed
in your package, and where to store your package.
See “About PC Transplant” on page 73.
See “Distributing user settings” on page 78.
Migrating personality settings
About migration settings
76
Personality Packages are stored in the Program Files\Altiris\Altiris
Agent\Agents\Deployment\Task Handler\PCTPackages directory. This directory
contains severalfolders that are named with GUIDs. After you createa personality,
the package is located in one of these folders.
Deployment Solution includes templates for many common applications. It also
provides tools to help you create templates for new and custom applications.
See “About deployment tasks and jobs” on page 39.
To capture user settings
1
In the Symantec Management Console, on the Actions menu, click
Deployment > Capture Personality.
2
On the Capture Personality page, type a unique name and a description.
If you capture multiple personalities, you can use the %COMPNAME% token as
the personality name.This tokencreates aunique namefor eachpersonality.
You can also select a template for your personality.
See “About personality templates” on page 74.
3
Select the other options that you want.
See “Capture options” on page 77.
4
Click OK.
5
Schedule the task.
See “Scheduling a deployment task” on page 44.
Capture options
The captureoptions inPC Transplant let you specify where the Personality Package
is created. You can also specify other options such as how much data to capture
in each file and whether to compress the files in the package.
See “Capturing user settings” on page 76.
Table 7-1
Capture options
DescriptionOption
Specifies where to store the package and the name of the
package. By default, this option uses the MI_PERSONAL
and MI_COMPUTERNAME variables.
Location
77Migrating personality settings
Capture options
Table 7-1
Capture options (continued)
DescriptionOption
Specifies that the Personality Package can be stored in
several files.You canuse this option if your package might
exceed the maximum size of a file (2 GB). This option is
also useful if your package exceeds the specific storage
media that you want to use. This option lets you use
different typesof mediafor a single package. For example,
CD-ROM, JAZ, or zip drives .
Span Package
Controls the compression of the files that are stored in
your package.
Use file compression
Distributing user settings
You can restore or distribute a personality that you previously captured by using
the Distribute Personality task. Deployment Solution uses PC Transplant to
capture and distribute personalities.
See “About PC Transplant” on page 73.
See “Capturing user settings” on page 76.
Personality Packages are stored in the Program Files\Altiris\Altiris
Agent\Agents\Deployment\Task Handler\PCTPackages directory. This directory
contains severalfolders that are named with GUIDs. After you createa personality,
the package is located in one of these folders.
See “About deployment tasks and jobs” on page 39.
To restore user settings
1
In the Symantec Management Console, on the Actions menu, click
Deployment > Distribute Personality.
2
On the Distribute Personality page, type the name of the personality that
you want to use.
If you distribute multiple personalities, you can use the %COMPNAME% token as
the personality name.This tokencreates aunique namefor eachpersonality.
You can also browse to the personality file that you want to use.
3
Choose the users to distribute the personality to.
4
Select any other options that you want to use.
See “Deploy options” on page 79.
Migrating personality settings
Distributing user settings
78
5
Click OK.
6
Schedule the task.
See “Scheduling a deployment task” on page 44.
Deploy options
The deploy options in PC Transplant include how to deal with existing files on
the destination computer and whether to restart the computer.
See “Distributing user settings” on page 78.
Table 7-2
Deploy options
DescriptionOption
Configures what the user sees on the screen while the
Personality Package is running. You can click the
Display Options box to enable this option.
Package Display
Runs thepackage onthe destinationcomputer without
any user intervention. If this option is the only option
that you choose, the user sees the package being
installed.
RunPersonality Package in quiet
mode
Determines what action occurs when a file already
exists on the destination computer.
Replace Files
Restarts the destination computer after the package
deploys.
Restart Destination Computer
79Migrating personality settings
Deploy options
Migrating personality settings
Deploy options
80
Example log files
This appendix includes the following topics:
■ rd2D7C26.txt
■ ClientImaging_Task.txt
rd2D7C26.txt
Error description:
The file could not be opened.
(Note: The file does not exist.)
(Filename: \\SITESERVER1\deployment\task handler\image\
879de9c6-78a2-41ba-a282-833c6b2946e9\XP2.img)
Possible causes:
A file that was expected to exist does not exist.
You do not have permission for this operation on the file or directory.
Possible resolutions:
Make sure the file exists and is accessible.
If the missing file is part of this program, reinstall the program.
Fix the permissions on the file or directory.
==================== Technical details ====================
Logfile = created Tue Jan 06 09:25:27 2009
Build = rdeployt.exe 6.9 (8853)
Cmdline = \\SITESERVER1\deployment\task handler\rdeploy\rdeployt.exe -noprompt -md
-f\\SITESERVER1\deployment\task handler\image\879de9c6-78a2-41ba-a282-833c6b2946e9\
XP2.img -p1 -sz1:100p
A
Appendix
Status = 41 (0x29)
Source file = imglib\fio\osfile.cpp
Line number = 287 (0x11f)
Stack trace = 0x44f090 0x44ee28 0x450fed 0x404554 0x40407f 0x402f98 0x4119f4
0x401d9c 0x40dc9d &Known=0x433490
File name = \\SITESERVER1\deployment\task handler\image\
879de9c6-78a2-41ba-a282-833c6b2946e9\XP2.img
Note = The file does not exist.
Imaging library revision = 8853 (win32-x86-release build, Fri Feb 22 19:30:12 2008)
ClientImaging_Task.txt
[2009/01/06 09:25:25.250 1636:1916 2] Log File Created. Version 7.00.369
[2009/01/06 09:25:26.265 1636:1916 2] ClientImaging_Task.cpp@65::Run()
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@49::Run()
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@63 <image><imaging><isDiskImage>
False</isDiskImage><imageType>@imageType</imageType><imageLocation>\\@SSName
\deployment\task handler\image\879de9c6-78a2-41ba-a282-833c6b2946e9\XP2.img
</imageLocation><imageName>XP2.img</imageName><imagingCommandLine> -noprompt
-md -f@fullImagePath -p1 -sz1:100p </imagingCommandLine></imaging></image>
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@115 Process imaging XML
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@208::Imaging()
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@245 <imageType>=@imageType
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@257 Input @imageType=rdeploy
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@267 Output @imageType=rdeploy
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@276<imageLocation>=\\@SSName
\deployment\task handler\image\879de9c6-78a2-41ba-a282-833c6b2946e9\XP2.img
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@302 <imageName>=XP2.img
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@304 Output @imageName=XP2.img
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@324 <imagingCommandLine>=
-noprompt -md -f@fullImagePath -p1 -sz1:100p
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@373 Input @serverName=SITESERVER1
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@387 Input @authenticationPoint=
\deployment
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@395 Server and share=\\SITESERVER1
\deployment
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@404 Input @imageToolPath=\task
handler\rdeploy\rdeployt.exe
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@424 Error getting=@NUKEGuid
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@435 Input @fullImagePath=\\@SSName
\deployment\task handler\image\879de9c6-78a2-41ba-a282-833c6b2946e9\XP2.img
Example log files
ClientImaging_Task.txt
82
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@437 Output @imagePath=\\@SSName
\deployment\task handler\image\879de9c6-78a2-41ba-a282-833c6b2946e9\XP2.img
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@443 Found @ServerName - value =
SITESERVER1
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@450 Replaced @SSName, new
fullImagePath = "\\SITESERVER1\deployment\task handler\image\
879de9c6-78a2-41ba-a282-833c6b2946e9\XP2.img"
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@581 Call CreateAProccess
(\\SITESERVER1\deployment, \task handler\rdeploy\rdeployt.exe, -noprompt -md
-f"\\SITESERVER1\deployment\task handler\image
\879de9c6-78a2-41ba-a282-833c6b2946e9\XP2.img" -p1 -sz1:100p)
[2009/01/06 09:25:26.265 1636:1916 2] Imaging.cpp@940 WNetCancelConnection2
(\\SITESERVER1\deployment)
[2009/01/06 09:25:26.890 1636:1916 2] Imaging.cpp@974 CreateProcess
(’\\SITESERVER1\deployment\task handler\rdeploy\rdeployt.exe’, ’ -noprompt -md
-f"\\SITESERVER1\deployment\task handler\image\
879de9c6-78a2-41ba-a282-833c6b2946e9\XP2.img" -p1 -sz1:100p’)
[2009/01/06 09:25:27.890 1636:1916 2] Imaging.cpp@1003 Child Process returned
error=41
[2009/01/06 09:25:27.890 1636:1916 0] Imaging.cpp@130 Create Process failed
value=41, error=183
[2009/01/06 09:25:27.890 1636:1916 2] Imaging.cpp@737::CopyIniFileToProduction()
[2009/01/06 09:25:27.890 1636:1916 2] Imaging.cpp@751 Input @exe=firm.exe
[2009/01/06 09:25:27.906 1636:1916 2] Imaging.cpp@765 Input @serverName=SITESERVER1
[2009/01/06 09:25:27.906 1636:1916 2] Imaging.cpp@779 Input @authenticationPoint=
\deployment
[2009/01/06 09:25:27.906 1636:1916 2] Imaging.cpp@795 Input @path=\Task Handler
[2009/01/06 09:25:27.906 1636:1916 2] Imaging.cpp@811 Call CreateAProccess
(\\SITESERVER1\deployment, \Task Handler\firm.exe, copy
"X:\Program Files\Altiris\Altiris Agent\PECTAgent.ini"
"PROD:\boot\altiris\iso\@inject@\Program Files\Altiris\Altiris Agent\PECTAgent.ini")
[2009/01/06 09:25:27.906 1636:1916 2] Imaging.cpp@940 WNetCancelConnection2
(\\SITESERVER1\deployment)
[2009/01/06 09:25:27.906 1636:1916 2] Imaging.cpp@974 CreateProcess
(’\\SITESERVER1\deployment\Task Handler\firm.exe’, ’
copy "X:\Program Files\Altiris\Altiris Agent\PECTAgent.ini" "PROD:
\boot\altiris\iso\@inject@\Program Files\Altiris\Altiris Agent\PECTAgent.ini")
[2009/01/06 09:25:29.609 1636:1916 2] Imaging.cpp@1007 CreateAProcess returned 0’
[2009/01/06 09:25:29.609 1636:1916 2] Imaging.cpp@1063 Output @errorMessage=Create
Process failed value=41, error=183
[2009/01/06 09:25:29.609 1636:1916 2] Imaging.cpp@1072 Imaging completed.
Failure return!!
83Example log files
ClientImaging_Task.txt
Example log files
ClientImaging_Task.txt
84
Symbols
10010
error 67
A
about
automation folder 35
capture options 77
capture personality settings 77
deploy options 79
deploy personality settings 79
deployment tasks and jobs 39
distributing personality settings 79
image resources 53
initial deployment 36
migration personality settings 76
personality migration settings 76
personality templates 74
PXE 24
add
drivers for preboot configuration 34
adding
licenses 33
system configuration 65
advanced deploy options 63
advanced image options 60
advanced task options
Create Image 60
Deploy Image 63
assign jobs and tasks
predefined computer 46
unmanaged computer 46
automation folder
about 35
using Deployment policies to install, uninstall,
and upgrade 20
automation mode
starting a computer in 46
B
backup image
creating a 59
for a single computer 59, 63
restoring a 63
Boot Disk Creator 12
adding drivers 34
C
capture
disk image 59
personality 76
preparing a disk image 57
user settings 76
capture options
about 77
clean
disk 48
DoD compliant disk 48
combining
task into job 44
command-line
advanced deploy options 63
advanced image options 60
computer
deploying new 64
configuration
Sysprep image 32
configuration driver
adding 34
configure
PXE server 36
copy
files 47
Copy File
task 47
create
backup image 59
Create Image
advanced task options 60
task options 59
Index
Create sysprep image
about 32
creating
deployment task 42
OEM extension 33
PXE preboot image 33
creating package
for scripted OS install 69
D
delete
disk image 54
image package 54
resource 55
deploy
computers 64
disk image 61
new computers 64
Deploy Image
advanced task options 63
task options 62, 71
deploy image
about 52
process for 55
deploy options
about 79
DeployAnywhere driver
settings 34
deployment
error 10010 67
settings 29
troubleshooting 67
deployment handler
about 24
deployment handlers
installing 25
Deployment plug-in
uninstalling 22
upgrading 23
Deployment settings
configuring 36
Deployment Solution
about 11
about PXE 24
about site server components 24
about task server handler 24
getting started with 13
installing automation folder 20
installing plug-in 19–20, 25
Deployment Solution (continued)
policy for installing site server 25
policy for uninstalling plug-in 22
policy for upgrading plug-in 23
portal page 16
process for 13
reports 16
settings 29
setup for first time 18
slide-out panel 18
tools 12
uninstalling automation folder 20
uninstalling plug-in 20, 22
upgrading automation folder 20
upgrading plug-in 20, 23
deployment task
creating 42
disk
clean 48
DoD compliant wipe 48
erasing 48
partitioning 49
wiping 48
disk image
capturing 59
deleting 54
deploying 61
preparing to capture 57
DoD
compliant wipe 48
drive
partitioning 49
driver
adding with Boot Disk Creator 34
settings 34
E
erase
disk 48
Erase Disk
task 48
error 10010
resolving 67
F
files
copying 47
Index86
G
Ghost
capturing image 59
H
hard drive
partition 49
HP server
iLO
turning on or off 50
HTTP
advanced deploy options 63
HTTP connection
imaging 60
I
iLO
power management 50
image
about deployment 52
capturing 59
create 55
deploy multicasting 58
deploying a disk image 61
for multiple computers 61
preparing to capture 57
Image Explorer 12
image package
deleting 54
Image preparation
about 32
image resource
about 53
deleting 55
imaging
HTTP connection 60
Import OS files
creating a package 69
initial deployment
about 36
settings 36
Initial Deployment menu
adding tasks to 36
install
software 47
Windows scripted OS 71
installation
Deployment plug-in 19
installation (continued)
Windows scripted OS 71
J
job
creating 44
L
license
adding 33
settings 33
M
migration
settings 29
migration settings
about personality 76
multicast
image deployment 58
multicasting
advanced deploy options 63
multiple computers
deploying disk image 61
N
network
changing settings for 43
O
OEM extension
creating PXE preboot image with 33
Operating system license
adding 33
options
about capture 77
about deploy 79
advanced Create Image task 60
advanced Deploy Image task 63
Create Image task 59
Deploy Image task 62, 71
Prepare for Image Capture task 57
OS files
creating a package 69
OS install
creating a package for scripted 69
OS license
adding 33
87Index
P
partition
advanced deploy options 63
disk drive 49
Partition Disk
task 49
PC Transplant 12
personality
capturing a 76
restoring a 78
personality resource
deleting 55
personality settings
about 76
personality template
about 74
policy
Deployment Solution
uninstalling 22
upgrading plug-in 23
Deployment Solution, about 20
for installing Deployment plug-in 25
for upgrading Deployment plug-in 23
portal page
for Deployment Solution 16
power management
iLO 50
preboot configuration
creating PXE preboot image 33
preboot configuration driver
adding 34
preboot mode
starting a computer in 46
predefined computer
assigning jobs and tasks 46
prepare
capturing a disk image 57
Prepare for image
about 32
Prepare for Image Capture
task options 57
process
for Deployment Solution 13
getting started with Deployment Solution 13
production mode
starting a computer in 46
PXE
about 24
PXE boot service
settings 33
PXE preboot
creating 33
PXE server
configuring 36
R
RapidDeploy
capturing image 59
image deployment 58
remote management
iLO 50
Remove SID
about 32
report
Computers with Deployment Plug-in
Installed 16
Computers with Deployment Tasks Execution
Status 16
Deployment Solution 16
resource
about image 53
deleting 55
restore
backup image 63
personality 78
user settings 78
S
sample
scripted OS job 70
schedule
a task 44
scripted OS
installation 71
scripted OS install
creating a package 69
scripted OS installation
sample 70
server
HP
turning on or off 50
settings
about personality capture 77
about personality deploy 79
about personality distribution 79
about personality migration 76
Index88
settings (continued)
changing 43
DeployAnywhere driver 34
drivers 34
for deployment and migration 29
initial deployment 36
licenses 33
OS licenses 33
PXE boot services 33
Sysprep imaging 32
system configuration 66
task list 36
setup
Deployment Solution for first time 18
SID
about 32
site server
about managing deployment tasks 24
about task server handler 24
site server component
about 24
site servers
installing task server handlers 25
managing deployment tasks 25
using Deployment policies to install, uninstall,
and upgrade 20
slide-out panel
for Deployment Solution 18
start
automation mode 46
preboot mode 46
production mode 46
state
checking a task 45
Sysprep image
about 32
configuration 32
settings 32
System configuration
adding 65
settings 65
system configuration
changing settings for 43
editor 66
settings 66
T
task
advanced Create Image options 60
task (continued)
advanced Deploy Image options 63
checking the state of a 45
combining jobs into 44
Copy File 47
Create Image options 59
creating a deployment 42
Deploy Image options 62, 71
Erase Disk 48
Partition Disk 49
Prepare for Image Capture options 57
scheduling a 44
task list
settings 36
task options
advanced Create Image 60
advanced Deploy Image 63
Create Image 59
Deploy Image 62, 71
Prepare for Image Capture 57
task server
about managing deployment tasks 24
about site server components 24
task server handler
about 24
task server handlers
installing 25
tasks and jobs
about deployment 39
template
about personality 74
tools 12
troubleshoot
error 10010 67
image deployment 67
U
uinstallation
Deployment plug-in 22
unmanaged computer
assigning jobs and tasks 46
user settings
capturing a 76
restoring a 78
V
Volume License Keys
adding 33
89Index
W
Windows
scripted OS installation 71
Windows OS
scripted installation 71
wipe
disk 48
DoD compliant 48
Index90
Loading...