You are on page 1of 472

ALTIRIS

DEPLOYMENT SOLUTION
6.5
REFERENCE GUIDE

Notice
Copyright 1996 - 2005 Altiris Inc. All rights reserved.
Product Version: 6.5
Document Date: September 8, 2005
Protected by one or more of the following U.S. Patents: 5764593, 6144992, 5978805, 5778395, 5907672, 4701745, 5016009,
5126739, 5146221, 5414425, 5463390, 5506580. Other patents pending.
Due to the inherently complex nature of computer software, Altiris does not warrant that the Altiris software is error-free, will
operate without interruption, is compatible with all equipment and software configurations, or will otherwise meet your needs.
The content of this documentation is furnished for informational use only, is subject to change without notice, and should not be
construed as a commitment by Altiris. Altiris, Inc. assumes no responsibility or liability for any errors or inaccuracies that may
appear in this documentation. For the latest documentation, visit our Web site at www.altiris.com.
Altiris, the Altiris logo, BootWorks, Eality, ImageBlaster, Inventory Solution, PC Transplant, RapiDeploy, RapidInstall, and Vision
are registered trademarks of Altiris, Inc. in the United States. Altiris, the Altiris Logo, and ManageFusion are registered trademarks
of Altiris, Inc. in other countries.
Altiris Connector, Altiris eXpress, Altiris Protect, Application Management Solution, Application Metering Solution,
Asset Control Solution, Asset Management Suite, Carbon Copy Solution, Client Management Suite, Compliance Toolkit,
Connector Solution, Contract Management Solution, Deployment Server, Deployment Solution, Energy Saver Toolkit,
Education Management Suite, Handheld Management Suite, Helpdesk Solution, Lab Management Suite, ManageFusion,
Migration Toolkit, Mobile Client for SMS, Monitor Solution, Network Discovery, Notification Server, Package Importer,
Patch Management Solution, Problem Management Suite, Recovery Solution, Security Solution, Server Management Suite,
Site Monitor Solution, Software Delivery Solution, SNMP Management, Software Delivery Suite, TCO Management Solution,
UNIX Client for SMS, Web Administrator, Web Reports, and other product names are trademarks of Altiris, Inc. in the United States
and other countries.
Audit on Connecct, Audit on Detect, AuditExpress, Scan on Detect, and SecurityExpressions are a trademarks of Pedestal Software
Inc. in the United States.
WebLens and Guaranteeing Your Net Works is a registered trademarks of Tonic Software Inc. in the United States.
WebInsight and RUM are a trademarks of Tonic Software Inc. in the United States.
Microsoft, Windows, and the Windows logo are trademarks, or registered trademarks of Microsoft Corporation in the United States
and/or other countries.
HP and Compaq are registered trademarks of the Hewlett-Packard Corporation.
Dell is a registered trademark of Dell Inc.
Macintosh is a registered trademark of the Apple Computer Corporation.
Palm OS is a registered trademark of Palm Computing, Inc.
BlackBerry is a service mark and a trademark of Research In Motion Limited Corporation.
RIM is a service mark and trademark of Research In Motion (RIM).
All other brand names are trademarks or registered trademarks of their respective companies.
PostgreSQL is released under the BSD licence.
PostgreSQL Database Management System (formerly known as Postgres, then as Postgres95)
Portions Copyright 1996-2004, The PostgreSQL Global Development Group
Portions Copyright 1994, The Regents of the University of California
Altiris Deployment Solution Reference Guide

Notice
Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a
written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs
appear in all copies.
IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE
OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE.
THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
THE SOFTWARE PROVIDED HEREUNDER IS ON AN AS IS BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS
NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
DHCP Copyright
Following is the copyright on the ISC DHCP Server:
Copyright 2004 Internet Systems Consorium, Inc. (ISC)
Copyright 1995-2003 Internet Software Consortium.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the distribution.
* Neither the name of ISC, ISC DHCP, nor the names of its contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY INTERNET SYSTEMS CONSORTIUM AND CONTRIBUTORS AS IS AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL ISC
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions. License shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1
through 9 of this document.
Licensor shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
Legal Entity shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition, control means (i) the power, direct or indirect, to cause the direction
or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding
shares, or (iii) beneficial ownership of such entity.
You (or Your) shall mean an individual or Legal Entity exercising permissions granted by this License.
Source form shall mean the preferred form for making modifications, including but not limited to software source code,
documentation source, and configuration files.
Object form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not
limited to compiled object code, generated documentation, and conversions to other media types.
Work shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work.
Derivative Works shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for
which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship.
For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by
name) to the interfaces of, the Work and Derivative Works thereof.
Contribution shall mean any work of authorship, including the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright
owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition,
Altiris Deployment Solution Reference Guide

Notice
submitted means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including
but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are
managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that
is conspicuously marked or otherwise designated in writing by the copyright owner as Not a Contribution.
Contributor shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by
Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a
perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works
of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by
such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the
Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or
counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory
patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such
litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You meet the following conditions:
(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution
notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
(d) If the Work includes a NOTICE text file as part of its distribution, then any Derivative Works that You distribute must include
a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part
of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative
Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by
the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for
informational purposes only and do not modify the License.
You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the
NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You
may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the
Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have
executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the
Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of
the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT,
MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this
License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as
a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work
stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been
advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to
offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with
this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not
on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END
OF TERMS AND CONDITIONS
Sun's Java Runtime

Altiris Deployment Solution Reference Guide

Notice
Copyright 1994-2004 Sun Microsystems, Inc. All Rights Reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
* Redistribution of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistribution in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the distribution.
Neither the name of Sun Microsystems, Inc. or the names of contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
This software is provided AS IS, without a warranty of any kind. ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED. SUN
MICROSYSTEMS, INC. (SUN) AND ITS LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY
LICENSEE AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THIS SOFTWARE OR ITS DERIVATIVES. IN NO
EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT,
INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND
REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO USE THIS
SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
You acknowledge that this software is not designed, licensed or intended for use in the design, construction, operation or
maintenance of any nuclear facility.
OpenSSL License
Copyright 1998-2003 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment:
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)
4. The names OpenSSL Toolkit and OpenSSL Project must not be used to endorse or promote products derived from this
software without prior written permission. For written permission, please contact openssl-core@openssl.org.
5. Products derived from this software may not be called OpenSSL nor may OpenSSL appear in their names without prior
written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

Altiris Deployment Solution Reference Guide

Contents
Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Chapter 1: Introduction to Deployment Solution
Features of Deployment Solution

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 1: New Features of Deployment Solution 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Planning and Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36


Chapter 2: Installing Deployment Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Deployment Server Components
.....................................................
Deployment Console
...........................................................
Deployment Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deployment Database
..........................................................
Deployment Share
.............................................................
PXE Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deployment Web Console
.......................................................
Deployment Server System Requirements

37
38
38
38
39
40
41

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Simple Install for Deployment Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Custom Install for Deployment Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Component Install for Deployment Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Installing Deployment Solution Agents


.................................................
Client Connectivity and Network Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Deployment Agent on Windows
........................................
Remote Agent Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enter administrator account information
.........................................
Specify install directory
......................................................
Automatically Add to a Group
.................................................
Select Computers on the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Download Altiris SIDgen and/or Microsoft Sysprep
................................
Change Settings
...........................................................
Get Server Security Key
.....................................................
Installing Deployment Agent for Windows
...........................................
Automating the Installation of Deployment Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing the Sample.inp file
....................................................
Creating a Template File using Remote Agent Installer
.............................
Using the Template File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Deployment Agent on Linux
..............................................
Installing the Automation Agent
...................................................
Installing Deployment Agent for PocketPC
..........................................
Altiris Deployment Solution Reference Guide

47
47
48
49
49
49
49
49
50
50
50
51
51
51
51
52
52
53
54
6

Contents

Managing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the License Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install a Regular License for Altiris Products
......................................
HP client computers and licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install Multiple Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a License from the Deployment Console
......................................
RDP Licensing
................................................................
Finding the Number of Licenses Used
..............................................
Computers Not Using a Regular License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Detecting an Expired License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Expired Licenses
..............................................................

57
58
59
59
60
60
60
61
61
61
62

DS Installation Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install Configuration
............................................................
Installing Deployment Server
.....................................................
Installing Deployment Server using Component Install
.................................
Deployment Server Install
.......................................................
Pre-boot Operating System (Simple)
..............................................
Pre-boot Operating System (Custom)
.............................................
Deployment Database Install
.....................................................
PXE Server Install
.............................................................
Client Connection to Server
......................................................
Deployment Web Console Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sysprep
.....................................................................
Installing Components
..........................................................
Simple and Custom Installation Summary
...........................................
Add Components Summary
......................................................
Deployment Database Authentication
..............................................
Add Components
..............................................................
Console Install
................................................................

62
62
63
64
64
64
65
65
66
66
67
67
67
67
68
68
68
68

Chapter 3: Installing Deployment Solution from the Altiris Console . . . . . . . . . . . . . . . . . . . . . . . . 69


Deployment from the Altiris Console
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Installing Notification Server and Enabling Deployment Solution . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Step One: Verify Installation Requirements
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
System Requirements
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Step Two: Install Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running InstallHelper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Notification Server with the Install Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrading from Previous Versions of NS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Deployment Solution from the Altiris Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Discovering Computers on the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Discovering Client Computers within a Workgroup
....................................

73
73
74
77
77
78
79

Step Three: Deploying the Altiris Agent


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Deploying the Altiris Agent from a Web Page
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Step Four: Verify Server-to-Client Communication

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Step Five: Install Deployment Servers


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Remotely Install Deployment Server (Push Silent Install)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Adding Deployment Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Step Six: Synchronize the NS and DS Databases
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Set Altiris Agent Configuration for Notification Server
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Set Polling Intervals for Deployment Solution (Deployment view on Notification Server)
. . . . . . . 87

Altiris Deployment Solution Reference Guide

Contents

Using Deployment Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88


Chapter 4: Managing from the Deployment Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Deployment Console Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Computers pane
..............................................................
Jobs pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Details pane
..................................................................
Shortcuts and Resources View
...................................................
Toolbars and Utilities
...........................................................
Deployment Solution Utility Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extending the Tools Menu on the DS Console

89
90
90
91
91
92
92

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Computer Filters and Job Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94


Creating Conditions to Assign Jobs
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Creating a Computer Group Filter
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console options
..............................................................
Global options
................................................................
Sysprep Settings
...........................................................
Task Password options
.........................................................
Domain Accounts options
.......................................................
RapiDeploy options
............................................................
Agent Settings options
..........................................................
Custom Data Sources options
....................................................
Allowed Stored Procedure List
................................................
Virtual Centers
................................................................

96
96
96
97
98
98
98
98
99
99
99

Security in Deployment Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99


Best Practices for Deployment Solution Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Enabling Security
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Groups
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Rights
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Setting Permissions
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Connecting to Another Deployment Server
Rejected Computers in Deployment Solution
Refresh Deployment Solution

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 5: Managing Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106


Viewing Computer Details

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Adding New Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108


Creating a New Computer Account
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Importing New Computers from a Text File
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Computer Configuration Properties
..................................................
General Configuration Settings
..................................................
Microsoft Networking Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TCP/IP Configuration Settings
...................................................
TCP/IP Advanced Options - IP interfaces
.......................................
TCP/IP Advanced Options - Gateway
..........................................
TCP/IP Advanced Options - DNS
.............................................
TCP/IP Advanced Options - WINS
............................................
TCP/IP Advanced Options - Static Routes
....................................
NetWare Client Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS Licensing Configuration Settings
..............................................

Altiris Deployment Solution Reference Guide

111
112
112
114
115
116
116
116
117
117
118

Contents

User Account Configuration Settings

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Deployment Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deployment Agent Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Production Agent Settings
......................................................
Changing Deployment Agent Properties from a Client Computer
........................
Changing Deployment Agent Properties from the Deployment Console
...................
Server Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Access
..................................................................
Security
.................................................................
Log File
.................................................................
Proxy
...................................................................
Startup/Shutdown
.........................................................
Deployment Agent on Linux
.....................................................
Automation Agent Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Drive Mappings
...........................................................
Authentication
............................................................
Network
.................................................................
.Deployment Agents for Pocket PC
...............................................
Connections to the Handheld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pocket PC Agent
..........................................................
Pocket PC Client
..........................................................
Deployment Agent on CE .NET
..................................................
Managing Client Connections

118
119
120
121
121
122
122
123
123
124
124
125
125
126
126
126
127
128
128
129
129

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Computer Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware
...................................................................
Drives
......................................................................
Network Configuration
.........................................................
TCP/IP
.....................................................................
Applications
.................................................................
Services
....................................................................
Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location
....................................................................
Bay
.......................................................................
Lights-Out
..................................................................

131
132
132
132
132
132
133
133
133
133
133
134

Remote Operations Using Deployment Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Restoring a Computer from its Deployment History
..................................
Configuring Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Quick Disk Image
.............................................................
Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Control
..............................................................
Send Files during Remote Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Control Properties
..................................................
Set Remote Control Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Start Multiple Sessions
.....................................................
Execute
....................................................................
User Account
.............................................................
Chat
.......................................................................
Prompt User for Properties
.....................................................
Installing Automation Partitions
..................................................
Change Agent Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

134
136
137
137
137
138
139
140
140
140
141
141
141
142
142
143

Deploying and Managing Servers

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Altiris Deployment Solution Reference Guide

Contents

Server Management Features


...................................................
Server Deployment Options
.....................................................
Managing Server Blades
....................................................
Managing New Server Blades
................................................
Virtual Bays
..............................................................
Hewlett-Packard Server Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dell Server Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fujitsu-Siemens Server Blades
...............................................
IBM Server Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Find a Computer in the Database
Using Lab Builder

144
145
146
146
146
147
147
148
148

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Chapter 6: Building and Scheduling Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154


Viewing Job Details

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

New Job Wizard


.................................................................
Migrating Computers
..........................................................
Selecting Computers in the New Job Wizard
.......................................
Apply Computers to a Job
......................................................
Associating Destination Computers
...............................................
Setting up Conditions in the New Job Wizard
.......................................
Install Software Packages
......................................................
Summary of Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Building New Jobs

155
156
157
157
157
158
158
158

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Job Scheduling Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159


Select Job(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Select Computer(s) or Computer Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Setting Conditions for Task Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Order Condition Sets
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Scheduling Jobs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Deployment Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Disk Image
.........................................................
SysPrep Settings
..........................................................
Create Disk Image Advanced
................................................
Distributing a Disk Image
.......................................................
Distribute Disk Image-Resizing
...............................................
Distribute Disk Image-Additional Options
.......................................
Scripted OS Install
............................................................
Scripted Install for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Select OS Version and Language
.............................................
Installation Source Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating System-Source Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Partition and Format Disk
...................................................
Import an Answer File
......................................................
Answer File Setup
.........................................................
Add a New Variable Value or Section
..........................................
Add a New Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command-line Switches for Scripted Install
.....................................
Deployment Agent Settings for Scripted Install
...................................
Scripted Install Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scripted Install for Linux
.......................................................
Scripted Install Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Altiris Deployment Solution Reference Guide

162
163
164
164
165
166
166
167
167
168
169
169
170
170
170
171
171
171
172
172
172
172

10

Contents

Distributing Software
..........................................................
Distribute Software Advanced
................................................
Capturing Personality Settings
..................................................
Capture Personality Advanced
...............................................
Distributing Personality Settings
.................................................
Distribute Personality Advanced
..............................................
Modifying Configuration
........................................................
Backing up and Restoring Registry Files
...........................................
Get Inventory
................................................................
Run Script
..................................................................
Script Information
.........................................................
Using LogEvent and WLogEvent in Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Copy File to
.................................................................
Copy File to Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Control
...............................................................

172
174
174
175
175
176
176
177
177
177
178
180
180
181
182

Modifying Tasks in a Deployment Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182


Modifying Multiple Change Configuration Tasks
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Creating New Script Files

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Copy and Paste Jobs and Job Folders


Importing and Exporting Jobs
Setting Up Return Codes

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Sample Jobs in Deployment Solution

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Chapter 7: Managing Deployment Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189


Deploying and Managing Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Server Management Features
...................................................
Server Deployment Options
.....................................................
Managing Server Blades
....................................................
Managing New Server Blades
................................................
Hewlett-Packard Server Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Virtual Bays
.............................................................
Dell Server Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fujitsu-Siemens Server Blades
...............................................
IBM Server Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Find a Computer in the Database
Using Lab Builder

189
189
190
191
191
192
192
193
193
193

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Chapter 8: Sample Jobs for Deployment Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196


Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Create Disk Image
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Distribute Disk Image
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Simple Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DIR Command at DOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DIR Command at Windows
.....................................................
Distribute RapidInstall Package
..................................................

197
197
197
198

Migrations
......................................................................
Capture User Application Settings
................................................
Capture User Desktop Settings
..................................................
Capture User Microsoft Office Settings
............................................
Capture User Printer Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

198
198
198
199
199

Misc Jobs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Altiris Deployment Solution Reference Guide

11

Contents

Install Office XP from Mapped Drive


..............................................
Install Office XP from UNC Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SQL 2000 Unattended Install
....................................................
SQL 2000 Unattended Install Using a RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Copy WLogevent to Client
......................................................
Install MSI 2.0 Runtime
........................................................
Repair Office XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restart Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Shutdown Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Start SQL Server Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stop SQL Server Service
.......................................................
Uninstall Office XP
............................................................
Wake up Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

200
200
200
201
201
201
202
202
202
202
202
203
203

Pocket PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Distribute Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Install Altiris Pocket PC Agent
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Scripted OS Installs
..............................................................
Create W2K Install Disk Image (Target HD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
W2K Scripted Install (Target HD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create RH7 Install Disk Image (Network) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create RH7 Install Disk Image (Target HD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RH7 Scripted Install (Network) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RH7 Scripted Install (Target HD)
.................................................
Create RH8 Install Disk Image (Network) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RH8 Scripted Install (Network) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

204
204
205
206
206
207
208
208
209

Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Send Email if Disk Space Low (Linux)
.............................................
Logevent Script (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restart HTTPD Service (Linux)
..................................................
Move Computer to Default Container (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Move Computer to Specific OU (Windows)
.........................................
Send Error Email (Windows)
....................................................
Server-side Embedded VBScript (Windows)
........................................
WLogevent CMD Script (Windows)
...............................................
WLogevent VB Script (Windows)
.................................................

209
210
210
210
210
211
211
211
211
212

XP Embedded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disable Enhanced Write Filter
...................................................
Enable Enhanced Write Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Distribute RapidInstall Package
..................................................

212
212
212
212

Chapter 9: Managing Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


LAN Switch Support List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Deployment Solution Switch Add-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Switch Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Discovering a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing and Setting Device Properties
.........................................
Setting the VLAN for a Switch Port
............................................
Assigning Connectivity to a Switch Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command-line Parameters
..................................................
GUI Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deployment Solution Switch Add-On (Command Line Options)
.........................

213
214
215
215
216
216
216
216
217
217
217
218

Altiris Deployment Solution Reference Guide

12

Contents

Chapter 10: Deployment Server Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220


Logon Account

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

General Option

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Drive Mappings Option


Transport Option

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Disk Imaging Option

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Authentication Option

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Connections Option
Debug Option

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Pre-boot Execution and Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227


Automation Pre-boot Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Which pre-boot operating system should I use? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DOS
.......................................................................
Windows PE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fedora Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

228
229
229
229

Which Automation Boot Method Works Best for My Environment?


..........................
PXE
.......................................................................
Automation Partitions
..........................................................
Boot Media (CD, USB Device, Floppy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

230
230
231
231

Configuring Automation Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Installing Windows PE, Linux, or DOS
.............................................
To install:
................................................................
Adding Additional Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Mass Storage Drivers for Windows PE
...................................

231
232
232
233
233

Configuring Automation Boot Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Configuring PXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Automation Partitions
................................................
Configuring Boot Media (CD, USB device, Floppy)
...................................

233
234
234
234

Deploying Automation to Managed Computers


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Using Automation Partitions or Boot Media
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Using PXE
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Automation Agents

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Chapter 12: Boot Disk Creator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237


Toolbar Description

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

New Configuration Wizard


.........................................................
Configuration Name
...........................................................
File Server Type (DOS)
........................................................
Network Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Have Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-Network Adapter Configurations
..........................................
TCP/IP Protocol Settings
.......................................................
Altiris Deployment Server Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Drive Mappings and Mount Points
.........................................
Configuration Summary
........................................................
Edit Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Altiris Deployment Solution Reference Guide

239
239
240
240
240
241
241
241
242
242
243
243
244
244
13

Contents

Additional Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245


Create PXE Boot Image Files (PXE)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
PXE Boot Image Creation Complete
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Automation Partitions, Network and Automation Boot Disks
...............................
Create Boot Disk
.............................................................
Create an Automation Install Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Automation Boot Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Network Boot Disk
......................................................
Remove Automation Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Import Configuration Files

246
246
247
247
248
248

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Install Pre-boot Operating System Files


..............................................
DOS
.......................................................................
FreeDOS
................................................................
MS-DOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows PE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

249
250
250
250
251
251

PXE Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252


PXE in Deployment Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PXE Services and Architecture
..................................................
Boot Images vs. RapiDeploy Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How PXE Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Part 1: DHCP Request and PXE Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Part 2: PXE Bootstrap
......................................................

252
253
254
254
255
255

Planning and Installing PXE


........................................................
Enabling PXE on Managed Computers
............................................
Installing and Configuring DHCP
.................................................
Determining How Many PXE Servers You Need
.....................................
Number of Client Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Speed
...........................................................
Physical Layout of your Network
..............................................
PXE Request Routing
......................................................
Installing PXE Servers
.........................................................

256
256
257
257
257
257
257
257
258

Configuring PXE Settings


..........................................................
PXE Settings
................................................................
Shared vs. Local
..........................................................
Session Timeout
..........................................................
DHCP Server Options
......................................................
Boot Integrity Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Boot Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Shared vs. Local
..........................................................
Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

258
258
258
258
259
259
259
259
259

Chapter 14: PXE Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261


Boot Menu Tab
..................................................................
New Shared Menu Option
......................................................
Edit Shared Menu Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Redirect Shared Boot Menu Option
...............................................
Import Boot Menu Options
......................................................

262
264
265
265
265

Install Pre-boot Operating System Files


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
DOS
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Altiris Deployment Solution Reference Guide

14

Contents

Windows PE

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

New Configuration Wizard


.........................................................
Configuration Name
...........................................................
File Server Type (DOS)
........................................................
Network Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Have Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-Network Adapter Configurations
..........................................
TCP/IP Protocol Settings
.......................................................
Altiris Deployment Server Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Configuration
.........................................................
Network Drive Mappings and Mount Points
.........................................
Configuration Summary
........................................................
Edit Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create PXE Boot Image Files (PXE)
..............................................
PXE Boot Image Creation Complete
..............................................
PXE Server Tab
DS Tab

268
268
268
268
269
269
269
270
270
270
271
272
272
273
273
274
274

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

MAC Filter Tab


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Define MAC Addresses
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Multicast Tab
BIS Tab

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Data Logs Tab

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Remote PXE Installation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Chapter 15: RapiDeploy Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281


How Imaging Works
..............................................................
How RapiDeploy Reads Hard Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Partitions Are Handled
.....................................................
Spanning Media
..............................................................
Saving Image Files on a File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Computer Settings Configuration
.................................................
Multicasting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

281
281
282
282
283
283
283

Preparing Computers for Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Task Overview
...............................................................
Prepare a Baseline System
.....................................................
Create Boot Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install the Deployment Agent For Windows for Post Image Configuration . . . . . . . . . . . . . . . . . .
Name Computers for Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

283
284
284
284
286
287

HTTP Imaging

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Creating, Uploading, and Sending Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Task Overview
...............................................................
Creating an Image File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create an Image File While Sending It to Client PCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Send Image of Master PC to Client PCs
...........................................

288
288
288
290
291

Restoring, Downloading, and Receiving Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Task Overview
...............................................................
Restoring an Image to a Master PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restoring (Download) Image to Master PC While Sending It to Client PCs . . . . . . . . . . . . . . . . .

292
293
293
294

Altiris Deployment Solution Reference Guide

15

Contents

Configuring Computers with Post-Imaging Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296


Settings Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Making Self-Extracting Image Files
Managing Images

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

Chapter 16: RapiDeploy Technical Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298


RapiDeploy Executable Files

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Running RapiDeploy from the Command-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299


RapiDeploy Command-line Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Using Command-line Switches with Executable Images
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Using SIDgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How SIDgen Works
...........................................................
Load SIDgen on your Computers (Optional)
........................................
SIDgen Memory Requirements
..................................................
Using SIDgen
................................................................
Scenarios for Generating SIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scenario 1: Non-Domain NT Servers or Workstations
.............................
Scenario 2: One PDC and Multiple Domain Members (No BDCs)
....................
Scenario 3: Synchronizing Multiple PDCs and/or BDCs
............................

308
308
308
309
309
310
310
310
311

Using File System Independent Resource Management (FIRM)


............................
How FIRM Works
.............................................................
Running FIRM
...............................................................
Using FIRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

311
312
312
313

Troubleshooting RapiDeploy

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Chapter 17: Altiris ImageExplorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318


Using ImageExplorer
.............................................................
View Properties
..............................................................
General Properties for an Image File
..........................................
General Properties for a Volume
.............................................
General Properties for a Folder
..............................................
General Properties for Files
.................................................
Description Properties for an Image
...........................................
Disk Partition Properties
....................................................
Open a File
.................................................................
Opening Split Image Files
...................................................
Find Missing Split Image Files
...............................................
Add New Files
...............................................................
Convert an Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create an Image Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extract a Folder
..............................................................
Find Files
...................................................................
Filter Results
.............................................................
Make Self-Extracting Images
....................................................
Not Enough Free Space
....................................................
Print Folder Contents
..........................................................
Print Preview
.............................................................
Print a File
..................................................................
Setting a Password on an Image File
.............................................
Settings
....................................................................
Split Image
..................................................................
Command Line Switches

321
321
321
322
322
322
322
322
322
322
322
323
323
324
324
325
325
325
326
326
327
327
327
328
329

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Altiris Deployment Solution Reference Guide

16

Contents

Deployment Web Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332


Chapter 18: Managing from the Deployment Web Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Deployment Web Console Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Computers pane
.............................................................
Jobs pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Details pane
.................................................................
Deployment Web Console Options
...............................................

334
335
335
336
336

Basic Tasks from the Deployment Web Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Remote Computer Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reject Client Computer Connections
..............................................
Assigning and Scheduling Jobs
..................................................
Finding and Filtering Computers and Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduling Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

336
337
337
337
338
338

Deployment Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Global . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SysPrep Settings
..........................................................
Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Agent Settings
...............................................................
Production Agent Settings
...................................................
Automation Agent Settings
..................................................
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logon
......................................................................

338
338
339
339
340
340
343
344
344
345
346
348

Automated Deployment Services (ADS)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

Deployment from the Altiris Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Adding Deployment Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Task Password options
........................................................
Configuring the Deployment Server Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generating Deployment Reports from the Altiris Console
..............................
Altiris Console Collections
......................................................

348
349
349
350
350
351

Using Package Servers to Replicate Deployment Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Overview of Package Servers
...................................................
Setting Up a Central Deployment Server Library
.....................................
Setting Up Package Servers
....................................................
Modify the DS Library Package
...............................................
Exporting and Importing Deployment Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

351
351
352
352
353
353

Setting Polling Intervals in Deployment Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355


Setting the DS Agent Polling Interval
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Setting the Altiris Agent Configuration Request
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Chapter 19: Managing Computers from the Deployment Web Console . . . . . . . . . . . . . . . . . . . . . 358
Managing Multiple Deployment Server Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Deployment Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing Task User Password options
............................................
Scheduling Jobs from Other Deployment Server Systems
.............................
Viewing Computer Details

359
359
359
360

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

Adding New Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361


Creating a New Computer Account
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Importing New Computers from a Text File
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Altiris Deployment Solution Reference Guide

17

Contents

Computer Configuration Properties


..................................................
Networking Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TCP/IP Settings
..............................................................
NetWare Client Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS Licensing Settings
.........................................................
User Account Settings
.........................................................
Deployment Agents

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Managing Agent Connections

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Computer Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General
.................................................................
Network
.................................................................
TCP/IP
..................................................................
Location
.................................................................
Bay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Lights-Out
...............................................................
Hardware
................................................................
Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Applications
..............................................................
Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Devices
.................................................................
Remote Operations

363
364
365
366
366
366

368
368
368
369
369
369
369
370
370
370
370
370

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

Find a Computer in the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371


Creating a Computer Group Filter
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Chapter 20: Scheduling Jobs from the Deployment Web Console . . . . . . . . . . . . . . . . . . . . . . . . . 373
Viewing Job Details

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

Building New Jobs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

Job Scheduling Wizard


Scheduling Jobs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Deployment Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Disk Image
.........................................................
Create Disk Image Advanced
................................................
Distributing Disk Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Distribute Disk Image- Resizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Distribute Disk Image-Additional Options
.......................................
Distributing Software
..........................................................
Distribute Software-Advanced
................................................
Capturing Personality Settings
..................................................
Capture Personality-Advanced
...............................................
Distributing Personality Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Distribute Personality Advanced
..............................................
Modifying Configuration
........................................................
Backing up and Restoring Registry Files
...........................................
Get Inventory
................................................................
Run Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Advanced Run Script Options
................................................
Copy File
...................................................................
Copy File Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Copy Jobs and Job Folders
Importing and Exporting Jobs

376
377
378
379
380
380
381
382
383
383
384
384
385
385
385
385
386
387
388
388

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389

Altiris Deployment Solution Reference Guide

18

Contents

Setting Up Return Codes

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Initial Deployment
................................................................
Configurations
...............................................................
Jobs
.......................................................................
Options
....................................................................

391
392
392
393

Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Chapter 21: Deployment Solution Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Deployment Server Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
How Deployment Server Components Work Together
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Deployment from Notification Server Architecture

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398

Chapter 22: Planning Deployment Solution Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401


Hierarchy of Altiris Servers

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

Design Scenarios
................................................................
Two-tier Distributed Model
......................................................
Three-tier Reporting Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Variables
..........................................................

403
403
405
407

General Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408


Database Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Scaling Deployment Solution
.......................................................
Design Strategies for Deployment Solution
.........................................
About Deployment Solution Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Branch Design for Deployment Solution
........................................
Enterprise Design for Deployment Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

411
411
412
414
415
416

Linux and Unix Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417


ADLAgent
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Installing and Configuring ADLAgent
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Distributing Software

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

Imaging Linux and Unix Filesystems


Linux Bootloaders

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

Chapter 24: Deploying Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419


Writing a Script
..................................................................
Server Scripting Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Retrieving Database Values Using Tokens
.........................................
Running Scripts on the Server
...................................................

420
420
421
421

Reporting Errors
.................................................................
DOS/CMD Error Handling
......................................................
Visual Basic Error Handling
.....................................................
Linux Shell ErSror Handling
.....................................................

422
422
423
423

Chapter 25: Managing Thin Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425


Supported Thin Client Manufacturers

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

Thin Client Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Windows XP Embedded (XPe) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Enhanced Write Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Enhanced Write Filter Utility
.......................................

Altiris Deployment Solution Reference Guide

426
426
426
427

19

Contents

Windows CE .NET
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Licensing Thin Clients

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

Chapter 26: Tokens and Import Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429


Computer Import File
System Tokens

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

Finding the Right Token Value

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432

Creating Unique Files Using Tokens


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Tokens
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Token Replacement Template Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
The Token Replacement Process
Custom Tokens

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434

Chapter 27: Command-Line Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436


Job Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Job Export Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Job Import Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Job Utility
.............................................................
Schedule Job Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Import Computer Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
axengine.exe

436
436
437
438
439
440

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440

Deployment Agent for Windows


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Aclient.exe Command-line Switches
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Aclient.inp Parameters
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Deployment Agent for DOS Command-line Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bootwork.exe
................................................................
Deployment Agent for DOS Install (Bwinst.exe) Switches
..............................
Keyboard and Screen Lock Utility (Kbdsclk) Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

444
444
446
447

Deployment Server Install Switches


..................................................
Silent Install Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simple Install Entries
.......................................................
Custom Install Entries
......................................................
Add Component Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

449
450
450
451
453

Client BIOS Settings for Wake-On LAN and PXE

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454

Command-line Switches for the Pocket PC Agent

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454

Chapter 28: Error Messages in Deployment Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456


General Error Messages
Client Error Messages

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

Communication Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459


Critical Error Messages
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Memory Error Messages

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460

Partition Error Messages

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461

Installer Return Codes

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

Altiris Deployment Solution Reference Guide

20

Chapter 1:

Introduction to Deployment Solution


Take control of all your computer resources across your organization using Deployment Solution
deployment and management tools. Take a seat at any Deployment console to remotely manage all
types of devices handhelds, notebooks, desktops, switches and servers through all phases of
computer deployment and lifecycle management. Schedule remote system upgrades, distribute
patches and drivers, re-image computer hard drives, or migrate large groups of users to new
computers without missing a single custom setting or installed program. Use Deployment Solution
to handle daily tasks and depend on it for occasional big jobs, like disaster recovery or large-scale
software updates. And do it all remotely from any Deployment console on any device with a
connection to your WAN or LAN.
That is the attitude behind Altiris Deployment Solution: Increase access and productivity while
decreasing costs and IT response time. You will appreciate the simple, easy-to-use graphical
consoles to organize computer groups, schedule deployment jobs, and distribute disk image and
update packages. Its easy. Its powerful. It conforms and scales to your infrastructure. Go ahead
take some time and learn to take control.
Integrated Deployment and Management System
Altiris Deployment Solution integrates Windows-based Deployment Server systems with the webbased Altiris solutions and services. A Deployment Server system for a specific site or defined
subnet includes Windows applications, tools, and utilities for daily management of computer
resources at the local level, and furnishes you with a Deployment Web Console for management
from the web browser.

To scale upwards and manage multiple Deployment Server systems across your organization,
Deployment from the Altiris Console (on Notification Server) centralizes reporting and management
and allows you to integrate additional Altiris web solutions to unify IT operations from a single
console.
What Can I Do with Deployment Solution?
Deploy. Manage. Migrate. Regardless of your organizations size or special IT requirements,
Deployment Solution provides a complete system to cut costs and improve response times for both
big and small jobs.

Altiris Deployment Solution Reference Guide

21

Chapter 1: Introduction to Deployment Solution

Features of Deployment Solution

Manage from a remote console. Deploy, control, and manage all types of computers across your

organization from a remote Deployment console. Use the feature-rich Deployment Server Console
for real-time management of computers, or access the Deployment Web Console from a web
browser on your preferred OS. Use Deployment from the Altiris Console to integrate reporting and
management across multiple network segments and to provide scalability and integration with other
web management solutions. See Managing from the Deployment Console on page 89.

Migrate data, applications, and personal settings. Through easy-to-use wizards, migrate data and

settings from a retiring computer to a new computer by capturing desktop, network, and application
settings. Redeploy these personal settings remotely from a Deployment console. See New Job
Wizard on page 155.

Upgrade and install software. Manage system software on a day-to-day basis for desktops, servers,
notebooks, and handhelds to upgrade applications, install service packs, set up printer drivers, and
modify systems as needed. Deployment Solution provides upgrade capabilities for all mobile
computers by deploying to remote sites as needed by traveling personnel. See Distributing
Software on page 172.
Deploy computers in large groups. Easily deploy and configure large numbers of computers
across an organization. Install hard disk images to groups of new or existing computer types using
multicasting features. Install software and personality settings with common applications, data and
drivers. Run post-configuration jobs or automated scripts to assign unique security IDs, configure
user names, and set IP addresses using deployment jobs. See Managing Computers on page 106.
Deploy and manage servers. Administrate all types of web and network servers, including ultra

high-density server board inserts. Automatically redeploy servers based on deployment history and
saved server images, or use automated scripted installs with easy-to-create answer files. Operating
systems can be installed as image files or run as scripted installsor as a combination strategy
(especially nice for managing ultra-dense server farms). See the Deployment Solution Reference.

Respond to common help desk requests. Remotely browse, diagnose, and repair problems on
systems without ever leaving a Deployment console. Detailed hardware and software inventories,
along with remote control and chat features, help simplify remote diagnosis of common problems.
See Remote Operations Using Deployment Solution on page 134.
Recover from disaster. Ease the pain of accidents by automatically backing up and restoring

configurations, personalities, registries, partitions, and drives remotely from a Deployment console.
Using the saved history of all deployment jobs assigned to a computer makes it easy to restore a
system to a previous working state. See Restoring a Computer from its Deployment History on
page 136.

Features of Deployment Solution


Deployment Solution can be installed and implemented locally as an independent Deployment
Server system on a single LAN segment or site, or scaled across the enterprise using Deployment
from the Altiris Console to consolidate all deployment and IT management efforts.

Each Deployment Server system includes services, applications, and utilities for high-bandwidth,
real-time deployment, and includes a web console to perform IT duties from a web browser.
Deployment from the Altiris Console integrates multiple Deployment Server systems for generating
deployment reports across the enterprise and adds other web IT solutions, such as the Inventory,
Application Metering, Carbon Copy and other solutions of the Client Management Suite.

Altiris Deployment Solution Reference Guide

22

Chapter 1: Introduction to Deployment Solution

Features of Deployment Solution

Deployment Server system


For local sites and network segments, the Deployment Server system provides both Windows and
web consoles and utilities. The Deployment Console is the Windows user interface that provides full
features to deploy computers, image hard disks, migrate user settings and programs, run scripted
installs, remotely control computers, and perform other deployment tasks for all of your computer
resources. Daily IT requests and jobs formerly completed by visiting each desktop, server or portable
computer in the organization can now be completed from your Deployment Server Console. In
addition, the Deployment Web Console provides most of these deployment features from a web
browser.
Components of the Deployment Server system can be installed on a single computer (a Simple
install) or distributed across several local computers (a Custom install). A Custom installation allows
you to install Microsoft SQL Server and access the Deployment Database from a separate computer.
The Deployment Share, Deployment Server, PXE Server, and Deployment consoles can also be
distributed to separate computers. The Deployment Web Console provides real-time management
from a web browser and, like the Deployment Server Console, displays data directly from the
Deployment database.
Deployment from the Altiris Console
For large organizations, multiple Deployment Server systems can be scaled to be administered from
a central Notification Server system. This integrated system provides regional reporting for all
computer resources and deployment activities. Deployment from the Altiris Console is a wide-area
network system that integrates computer deployment and management functionality into the Altiris
Notification Server infrastructure, furnishing enterprise-wide reporting and package distribution
across HTTP connections.
Deployment from the Altiris Console organizes Deployment Server systems from each network
segment or site and consolidates operations from a web console. To extend management capabilities,
you can combine additional web solutions from the Altiris Client Management SuiteInventory,
Application Management, Carbon Copy, Software Delivery and other solutionsto meet your
unique needs. Deployment from the Altiris Console extends scalability for large enterprises and
integrates additional web solutions across the organization.

Managing from the Deployment Console


Deployment Solution includes several types of user interface consoles for different types of
computer management tasks and access requirements. The Deployment Server Console (a
Windows console) is included with the Deployment Server system and provides complete
deployment and management features. The Deployment Web Console provides web browser
access to individual Deployment Server sites. Deployment from the Altiris Console integrates the
view of multiple Deployment Server sites and integrates with additional web solutions.
All Deployment consoles are divided into several operational panes:

The Computers pane displays all computer resources managed by a Deployment Server system.
It includes features to right-click and remotely execute operations on managed computers. From
this pane you can drag computer icons to job icons to schedule deployment and management
tasks.

The Jobs pane executes and schedules deployment tasks for selected computers. Using one or
more sequenced jobs, you can image, configure computer settings, distribute packages, and run
scripts by dragging Job icons to individual computers or computer groups and scheduling an
advantageous time to execute. It lets you schedule deployment jobs by dragging computer icons
to job icons, or vice versa.

The Details pane provides information and features to filter computers by type and build
deployment tasks. It extends the user interface features when working in the Computers and Jobs
panes.

From the Deployment Server Console (the Windows console), a Shortcut and Resources pane
organizes and provides easy access to MSI files, RIPs, image files (.img), Personality Packages
(.exe), and other file types. It functions as a library for packages used when building jobs in the
console.

Altiris Deployment Solution Reference Guide

23

Chapter 1: Introduction to Deployment Solution

Managing Computers

In addition, the Deployment Server Console furnishes your IT team with easy-to-use wizards to
simplify and expedite common deployment tasks. See also Managing from the Deployment
Console on page 89.

Managing Computers
From the Deployment Console you can directly manage all types of computers to perform immediate
deployment and management operations. From the Computers pane of the console, computer
resources can be grouped by location, department, type (portables, desktops or servers) and
organized to reflect your environment. You can run on-the-fly operations or quickly schedule
deployment jobs, or access each computer or computer group to change network settings, run a quick
disk image, or perform other immediate management tasks.
The console identifies each computer and computer groups with a unique icon. To access a
computer, simply click its computer icon to view configuration settings or run specific deployment
and management operations. Computer icons can be dragged to job icons to schedule and run preconfigured deployment tasks from the Windows console. In the Deployment web console, you can
manage computers using drop-down lists, secondary dialog boxes, and other familiar web features.
See also Managing Computers on page 106.
Managing with Computer Icons
Icons displayed in the Computers pane of the console help in identifying the computer types and
deployment status. Group icons can be expanded to view the member computers, and computer
types can be identified by specific icons: handhelds, desktops and notebooks, servers, computer
groups, and Linux computers. Computer icons can also identify the state of the managed computer
a logged in user, a computer waiting for further instructions, a user not logged in and other states of
deploymentwhen performing operations or executing deployment tasks on a selected computer.
See also Viewing Computer Details on page 107.
This icon identifies a managed desktop or notebook computer that
is active and has a user logged on.
This icon identifies a managed Windows network or web server
that is active and has a user logged on.

This icon identifies a Linux computer.


This icon identifies a handheld computer.
This icon identifies a pre-configured computer account with user
account settings that are not associated with a new computer.
Additional icons represent deployment status, inactive computers, computers running a deployment
job, and new computers. See also Viewing Computer Details on page 107.
Immediate Management Access from the Console
From a Deployment console you can select a computer and actuate various computer configuration
and management operations for a specific computer in your system. You can create new deployment
tasks, reboot, restore the hard drive, view deployment history, and perform other advanced tasks
using the commands on this menu. Some operations such as changing configuration settings,
copying files, and creating quick disk images create job files automatically. See also Remote
Operations Using Deployment Solution on page 134. For complete information about Deployment
consoles, see Managing from the Deployment Console on page 23.

Altiris Deployment Solution Reference Guide

24

Chapter 1: Introduction to Deployment Solution

Building and Scheduling Deployment Jobs

Building and Scheduling Deployment Jobs


Jobs are designed as objects with defined deployment tasks. Jobs can be built, organized, and
scheduled to run on selected computers or computer groups from a Deployment console. Jobs
automate both simple and complex IT administrative duties from complete deployment and
migration tasks to simple DOS commands and modification of configuration settings. You can build
and schedule jobs from any of the Deployment consoles.
Deployment jobs give you the ability to organize, store and assign administration tasks for each
computer or computer group. You can create and deploy images, back up registry files, run scripted
installs, or make post-imaging changes such as adding printers and applications. You can deploy and
run packagesRIPs, images, personality packages, MIS programs, and othersto migrate
applications, configure computer settings, deploy complete hard disk images, and much more. You
can also assign jobs with conditions to run only on defined computer types. See also Building and
Scheduling Jobs on page 154.
Jobs are built in the Deployment Server Console by creating a job name (identified by a job icon in
the console) and adding predefined deployment tasks. Tasks such as Distribute Software, Run Script,
or Create Disk Image are added and executed sequentially when scheduled to run on computers or
computer groups. And even within computer groups, different jobs can be assigned to different
computer types based on OS, hardware, or other specified condition. See also Deployment Tasks
on page 162.
When a job is built, it can be scheduled to run immediately, at desired intervals, or at any other
advantageous time when traffic is low. In addition, you can use bandwidth throttling features to
schedule and run deployment tasks to large groups without affecting network traffic. See also
Scheduling Jobs on page 160.
From the Deployment Server Console, you have several options when creating deployment jobs:

Create common deployment tasks quickly and easily using the New Event Wizard.

Import jobs from other Deployment Solution systems.

Manually create deployment tasks from the console.

Copy and paste deployment tasks from within the console.

See also Building New Jobs on page 158.


In the Jobs pane you can create and organize deployment jobs. You can then assign jobs by dragging
icons to the desired computer or computer group.
Building Jobs
Building jobs includes creating a new job and then adding tasks to the job to run in sequence when
scheduled on selected computers. You can build jobs by adding tasks manually or you can step
through the New Job Wizard to create common jobs and schedule them quickly and easily. Sample
tasks are also included with Deployment Solution to use as installed or to easily customize and run.
See also New Job Wizard on page 155.
After creating and building a job, you can then assign it to a computer and schedule it to run at any
timeimmediately, after a specified time, or on a daily, weekly, or monthly schedule. The
deployment status of each job will be reflected in the console.
Assigning Deployment Jobs with Icons
Like computer icons used to identify types of computers in the console, job icons identify the status
and success of each scheduled deployment job. After scheduling jobs, you can then monitor the
progress as the job icons update at each step of execution.

Altiris Deployment Solution Reference Guide

25

Chapter 1: Introduction to Deployment Solution

Imaging

This job is assigned to a computer but not scheduled to run. Until


scheduled, this job icon will remain unchanged.
This job is assigned to the computer and scheduled to run either
immediately or in the future.
This job is currently processing.

This job has completed successfully.

See also Viewing Job Details on page 154.


Scheduling Jobs
From the Schedule Job dialog box you can run jobs immediately or schedule the job to run in batches
at defined intervals. You can also assign the job to repeat every hour, day, or week. Scheduling jobs
can be as simple as clicking OK to run immediately or as sophisticated as required to meet your
deployment needs.
For complete information about building and scheduling deployment jobs, see Building and
Scheduling Jobs on page 154.

Imaging
A primary task of Deployment Solution is to capture an image (clone of the hard drive) from a
reference computer and distribute the image to set up new computers or reinstall computers to their
basic configuration. You can create a library of image files on the Deployment Share (file server
storage) and schedule image jobs to different computer types as required.
Deployment Server allows you to push down a boot image remotely and execute the image either
DOS, Linux, Windows PE, or a PXE Server, eliminating the need to physically attend and boot each
managed computer. See also Creating a Disk Image on page 163, Distributing a Disk Image on
page 165, and New Job Wizard on page 155
Imaging from Deployment Server
Deployment Server includes multiple features to capture an image and lay it down to a new or
existing computer. You can use the Deployment Server Console to create and distribute disk images
using deployment tasks, such as the Quick Disk Image wizard shown below:
Pre-boot environments allows you to boot to automation to create and deploy images, back up and
restore a computers Registry file, or run other automation tasks. You can also boot to a Network
Server and run imaging files and other commands. See Boot Disk Creator Help, and PXE
Configuration Utility Help.

Migrating Computers
Deployment Solution provides various options to migrate operating systems, computer
personalities, software, or complete hard disk images. You can accomplish migration tasks
individually or as a single job.

Altiris Deployment Solution Reference Guide

26

Chapter 1: Introduction to Deployment Solution

Deploying and Managing Servers

The New Job Wizard steps you through each migration option, allowing you to capture a complete
hard disk image (to upgrade to a new computer), migrate a user to another operating system with the
same personality settings and applications, or to simply move personality settings from one
computer to the another. Using the New Job Wizard is one of the easiest ways to build deployment
tasks to migrate user data and settings.
Deployment Solution allows you to build sophisticated deployment jobs that automatically migrate
personalities, including deployment tasks to capture the users personality, migrate OS and software,
and then reconfigure the computer with the users original personality settings. You can also edit
Personality Packages or Rapid Install Packages (RIPs) on-the-fly using the PC Transplant Editor and
the Wise MSI Editor tools from the Deployment Server Console.

Deploying and Managing Servers


Deployment Solution includes features designed specifically for deploying and managing network
or web servers. Server-specific features include scripted installs for initial installation, and support
for remote management cards, multiple network adapters, history transfers to support rip and
replace redeployment, and additional functionality required for automating server management.
Deployment Solution also integrates with other hardware vendors to provide systems and tools to
manage large server installations and support automatic deployment strategies. These unified
systems simplify and automate server configurations and large-scale migrations, and support
emerging hardware for ultra high-density server systems.
From a Deployment console you can build deployment jobs to run scripted installs for Windows and
Linux servers. These unattended installs can be run directly over the network for individual web
or network servers. Answer files can be created and edited from a Deployment console for each
scripted install.
You can also execute server-specific scripts and redeployment tasks. Enhanced task logging and
history tracking features let you recall deployment actions to quickly redeploy mission-critical
servers.

Lets Get Started


Deployment Solution is a full-featured remote deployment system designed to manage computer
devices across all types and sizes of small to medium organizations and large enterprises. It includes
Windows and web components to design and scale a system for your specific IT needs and
challenges. Deployment Solution provides a wide array of tools, utilities and applications to design
a system for your specific needs. Deployment Solution is easy-to-use and adaptable to your
environment.
You can design and install a Deployment Server system specific to your hardware, organizational
structure, network architecture, and other environmental variables. The installation and
configuration process allows you to install Deployment system components (database, services,
network share, user interface console) to a single computer or distribute components to separate role
servers.

Altiris Deployment Solution Reference Guide

27

Chapter 1:

New Features of Deployment Solution 6.5


Silent support of all install options
Deployment Solution provides a silent.ini builder utility that lets you create the silent.ini file for
Simple Install, Custom Install, Add Component, or a Hot Fix without manually typing in the
contents of silent.ini.
Support changing database name on install
Deployment Solution provides an option to specify a custom database name during Custom Install
procedure. You can specify any database name other than the default name. See Deployment
Database Install on page 65.
Encrypted communication between DataManager and Engine
The communication between the DataManager and Engine is encrypted using Open Secure Socket
Layer (SSL). The earlier communication used to be in plain text format. Now, the DataManager uses
the same mechanism as that of the Deployment Agent for Windows.
Multiple PXE support
Deployment Solution supports Multiple PXE boot Images. This helps you choose different PXE
boot images depending on the task level. This option also enables you to boot to multiple pre-boot
environments during the course of a job.
Multiple PXE boot images option is available for Run Script task, Create Disk Image task, Distribute
Disk Image, Backup Registry, and Restore Registry tasks. Refer to the Automation- PXE or
BootWorks environment option for the above mentioned tasks.
Get Inventory task
While the Get Inventory function is not a new capability of Deployment Solution, it is however, a
new task that can be added to any Deployment job. From both the Deployment and Web Consoles,
the Get Inventory task is available on the task list when creating or modifying Deployment jobs. See
Get Inventory on page 385.
Centrally managed task password
Deployment Server administrators can now add or change user passwords for the tasks: Copy File
to, Distribute Software, Run Script, Distribute Personality, and Capture Personality. Deployment
Solution 6.5 allows administrators the same functionality; however, new credentials were entered
for each of the tasks listed above, and for every user that wants to add these tasks to deployment jobs.
This enhanced feature gives administrators the ability to centrally manage passwords for jobs and
tasks, while saving time and effort when adding or changing user password information. See
Changing Task User Password options on page 359.
New UI for Distribute Disk Image - Additional Options
This feature provides a new user interface to specify additional options for Distribute Disk Image
task.
In the 6.1 version of Deployment Solution, Deployment Console provides two options Remove
BootWorks Partition and Remove Compaq System Partition on the Additional options tab of the
Distribute Disk Image Advanced dialog box. These two options allowed the user to change the

Altiris Deployment Solution Reference Guide

28

Chapter 1: New Features of Deployment Solution 6.5

behavior of the RapiDeploy program that runs the imaging tasks. But instead of removing the
partitions from the client computer, selecting these options forced RapiDeploy to replace the
partitions on the client computer with those in the image.
The new UI provides several new options to mange the additional options. See Distribute Disk
Image-Additional Options on page 380.
Importing and exporting jobs
The Deployment Web Console is now capable of importing and exporting job folders.
Administrators and users, who have been granted the privileges to perform this function, can use this
feature to remotely restore and backup job folders without having to go to the Deployment Console.
See Importing and Exporting Jobs on page 389.
Importing Virtual Computers
This feature is already available through the Deployment Console, but it is new to the Deployment
Web Console. You can import computer configuration data files to set up computer accounts in the
Deployment database, from any computer that has the Deployment Web Console installed. See
Importing New Computers from a Text File on page 363.
Rejecting connections
The Deployment Web Console introduces the capability of rejecting computer connections to the
Deployment Server. The Reject Connection is a new Computer Action that will remove the client
computer's name and all of its information from the Deployment database. The client computer will
not be manageable until it associates with another Deployment Server. See Reject Client Computer
Connections on page 337.
Using Deployment Solution, you can also allow the rejected computer to connect to the Deployment
server and manage.
Distributing Notification Server software
The Deployment Web Console lets you distribute Notification Server software packages, such as
Agents, Pocket PC Client, PCT, and more, to client computers using the Distribute Software task in
deployment jobs. You can achieve this by using the Distributing Software task.
Use of Tokens
The Deployment Web Console allows the use of different Deployment Solution tokens while
specifying the computer name during configuration. This option is available only for multiple
computers. Refer to Define name range in Networking Settings.
Enhanced Role Based Security
The enhanced Role Based Security provides a robust environment for the Deployment Web
Console. Enhanced Role Based Security provides the administrators with rights to deny or allow
users to schedule jobs and permission to move a computer, job, group, or folder to another group or
folders.
A new security permission, Schedule this job is available in the Object Security dialog box for the
selected job. A user who has been denied this right for the job cannot schedule the job regardless of
other privileges.
A new security permission, Move Object is also available in the Object Security dialog box for the
selected computer, folder, job, or group. A user who has been denied this right cannot move a
computer, folder, job, or a group. See Enabling Security on page 344.
Active Directory support
Deployment Solution 6.5 supports adding groups from the Active Directory, and reading and using
Active Directory syntax for user identifications, example: email@domain.com. This support is valid
for all the instances where user names and domains are required.
Deployment Solution passes existing user credentials, that is, the credentials used by the users to
authenticate to NT to the Deployment Web Console, and does not require re-authentication to the
SQL database on startup.

Altiris Deployment Solution Reference Guide

29

Chapter 1: New Features of Deployment Solution 6.5

Deployment Solution also authenticates users based on their group membership. Deployment
Solution provides the ability to set security assignments, such that any user who belongs to that
Active Directory group has the assigned rights in Deployment Solution. See Importing groups from
the Active Directory on page 102.
Reboot option
Deployment Solution ensures that if Reboot option is not specified, then the client computer will not
restart after the configuration has changed. Previously, the client computer had to restart after any
configuration changes were applied, and there was no way to control the restarting of the computer.
Deployment Solution 6.5 introduces Reboot after configuration option for configuration tasks. You
can find this option in the Networking tab of the Computer configuration page.
Deployment Server options
Deployment Solution 6.5 enables you to set all the options related to Deployment Server in one page
using the Deployment Web Console. The options that you can set are Role-based Security, Global,
Agent Settings, Speed of replication, and Deployment Server name and port information.
Previously, this feature was available only through the Deployment Console. See Deployment
Server Configuration on page 338.
Microsoft Sysprep
Deployment Solution provides you native support for Sysprep. It allows you to use Sysprep while
creating a disk image or distributing a disk image. This facilitates in building hardware generic
images while ensuring that they are in compliance with the MS support agreement.
You can modify the Sysprep settings and include a customizable answer file as well. A new option
is introduced for Create Disk Image and Distribute Disk Image tasks. You can
enter global values for Sysprep settings using Global tab of the Deployment Server Options feature.

Prepare using sysprep

End Result Return Codes


Deployment Solution supports defining and displaying the meaning of end-result of user-defined
return codes. This presents a clear picture of the status of individual tasks for an assigned job. See
Setting Up Return Codes on page 185.
RDeployT Options
Deployment Solution facilitates the imaging of thin client computers. This feature introduces
RdeployT as the imaging executable for Create Disk Image and Distribute Disk Image tasks. See
Create Disk Image Advanced on page 164 and Distribute Disk Image-Additional Options on
page 166.
Static Routing configuration
The Advanced option in the Computer Configuration Properties page allows the administrator to set
up static routing information. It also allows you to specify the DNS Suffix Search order and turning
the NetBIOS on or off. See TCP/IP Advanced Options - Static Routes on page 117.
Log history for all cancelled events
Deployment Solution logs history for scheduled events, which are aborted through user prompts.
You can view this information when you check the history of events for a specific computer. You
can then choose to save the history in a text file or delete it. See Viewing a Computers History on
page 136.
Force Default Agent Settings
Deployment Solution forces the Default Client Settings to a new client computer when the computer
connects to the server first time. This setting is valid for Automation as well as Production agents.
See Agent Settings on page 340.
Enhanced security for Deployment Agent
Deployment Solution 6.5 uses key pairs to validate that the Deployment Server that Deployment
Agent is connecting to is authentic. This feature helps in determining the authenticity of the
Deployment Server. See Server Connection on page 122.

Altiris Deployment Solution Reference Guide

30

Chapter 1: New Features of Deployment Solution 6.5

Sleep settings for the Deployment Agent for Windows


Deployment Solution provides a UI configuration parameter that indicates the predetermined
amount of time the Deployment Agent for Windows sleeps after the operating system starts. A new
option Delay starting jobs after system startup can be found on the Deployment Web Console by
accessing the Startup/Shutdown tab of the Production Agent Settings. See Startup/Shutdown on
page 343.
Maintaining order of jobs
Deployment Solution facilitates scheduling of jobs in the order they are selected. When a job folder
is selected from the Jobs pane, folders and jobs are displayed in the Details pane of the Deployment
Console. The job folders, jobs within the folders, and individual jobs are scheduled in the order they
are selected. This feature is introduced for Deployment Console as well as Deployment Web
Console.
Delete History
Delete history feature lets an administrator, or a user with administrator rights, or users with allow
permission for Delete History, to view, save, and delete the history of any computer. On the
Deployment Web Console, you can select a computer whose history you want to delete, and select
History from the drop-down box in the Computers pane. The history of the computer, if available,
appears on the Details pane. Click the Delete icon to delete the history of the selected computer.
Filters
Deployment Solution version 6.5 adds three new default filter criteria for Deployment Console and
two new default criteria, and Advanced Find functionality for Deployment Web Console. The new
criteria's are Active Computers, Inactive Computers, and Advanced Find. To know more about
Filters, see Creating a Computer Group Filter on page 372.
Remove inactive computers
Deployment Solution lets you manage inactive client computers by automatically removing
computers that have not communicated with the Deployment Server after a selected period of time.
This feature can be set from the Deployment Web Console by using the Deployment Server Options
page. Refer to the Remove inactive computers after __ days option available in Maintenance on
page 339.
Enhanced Status Display
Deployment Solution 6.5 provides users with more detailed information. The Jobs Details page
displays the elapsed time for scheduled jobs and the status field displays errors incurred when the
job runs, but only if error conditions are used, and the tasks within the job that completed
successfully. You can view these changes in the Details pane of Deployment Console.
Copy jobs and jobs folder
The Deployment Web Console allows user's, who have administrator privileges or have been
granted permissions to create jobs, or create job folders, to copy jobs and job folders to any other
root level job folder in the tree view of the Jobs pane. You can have up to 30 subfolders below the
root level folder, but you cannot copy a job folder to a child level folder.
Extended Run Script capabilities
Deployment Solution 6.5 extends the Run Script capability to support additional command line
parameters for UNIX and Linux systems as well as Windows systems. See Advanced Run Script
Options on page 386.
Find next for Find Computer
You can find computers in the Deployment database by entering the search criteria in the Find
Computer in Database dialog. The search starts at the beginning of the computer list in the
Computers pane of the Deployment Console and highlights the computer name when a match is
found. See Find a Computer in the Database on page 148.
New with this release, you can now press F3 to find the next computer that matches the search
criteria until there are no more results, or the end of the computer list has been reached.

Altiris Deployment Solution Reference Guide

31

Chapter 1: New Features of Deployment Solution 6.5

Tab control on the Schedule Job dialog box


This feature introduces tab control on the Schedule Job dialog box. The three tabs are Job Schedule,
Selected Computer(s), and Selected Job(s). The Selected Computer(s) tab displays information about
the computers on which jobs are scheduled, the group to which they belong, and the IP addresses.
The Selected Job(s) tab displays the scheduled jobs and the folder to which the jobs belong. There
are two buttons for changing the order of the jobs also.
Installation prompt for Sysprep
During the installation of the Deployment Solution, a prompt appears to insert the appropriate
Microsoft Windows CD, and copy the files from the CD to the appropriate area to be used by
Deployment Solution.
Copy tasks
This feature lets you copy and paste single or multiple tasks from one job to another, or within the
same job. After tasks are pasted into the destination job, you can modify the tasks, if needed. The
ability to copy and paste tasks saves time and effort when creating or modifying jobs. You can copy
tasks using CTRL+C and CTRL+ V also. See To copy and paste a task on page 182.
Installing correct database
Deployment Solution installation allows you to choose which language database you want to install.
You can choose from English, French, German, Spanish, Japanese, and Simplified Chinese.
Adding new tasks to the existing task lists after cursor position
The Deployment Console introduces a new feature that lets you insert a task after any cursor position
within the task list of a Deployment job. You can achieve this without having to use the Up or Down
buttons to set the order of the task.
Resizable task list pane
The Deployment Console's task pane can be increased or decreased in size by dragging the bottom
pane (horizontal bar) that separates the task list and the scheduled computer list. This feature lets you
view a greater number of tasks in a deployment job without using the scroll bar to navigate up and
down.
Localized strings
In Deployment Console, the system folder names appear as per the System locales.
User-defined Ports
Deployment Solution allows an administrator to specify the ports (up to two) that will be used when
running remote control from the Deployment Console. Refer to the options provided for Primary and
Secondary ports on the Global options of Program Options. See Global options on page 96.
Support Windows Pre-installation Environment (Windows PE)
Deployment Server supports Windows PE 2005, which requires files from Windows Server 2003
SP1 installation CD as a pre-boot environment. Using Windows PE as a pre-boot environment, you
can do the following:

Create bootable CDs

Create PXE boot configurations

Capture and deploy images

Install Windows PE automation partitions

Support Linux Pre-boot Environment


Deployment Server supports Linux, but only the Red Hat Fedora version. BDCgpl.frm contains the
files needed to install Linux as a pre-boot operating system. This file is available for download from
the Altiris Solution Center.
Using Linux as a pre-boot environment, you can do the following:

Altiris Deployment Solution Reference Guide

32

Chapter 1: New Features of Deployment Solution 6.5

Create boot disks

Create boot configurations

Capture and deploy images

Install Linux automation partitions

Automation partition compatibility with other products


Deployment Solution now supports an embedded automation partition that can co-exist with the
embedded partition from Altiris Recovery Solution on the same computer. However, you must have
Deployment Solution 6.5 or later and Recovery Solution 6.1 or later to be completely compatible.
Create boot CD
Boot Disk Creator lets you create ISO images for DOS, Linux, and Windows PE pre-boot operating
systems configurations that can be burned to a CD. However, you must provide your own third party
CD burning software. The bootable CD can then be used to manually boot client computers to
automation.
PXE Configuration Utility
This utility is newly-designed and provides greater flexibility to do the following tasks:

Centrally manage all PXE Servers across the network. The boot menu options can be either
Shared or Local. By default, PXE Configuration opens in the Shared Configuration mode and
any new boot menu options or property settings you change, will affect all PXE Servers on the
network.

Create boot menu options using Boot Disk Creator from within PXE Configuration. You can also
import configurations Direct from floppy, or select User supplied to add your own files to the
MenuOption<number> folder.

Install DOS, Linux, or Windows PE pre-boot operating system files any time you want.
However, you must install at least 1 pre-boot operating system before you can create boot menu
options with Boot Disk Creator.

Set the order of boot menu options. When client computers PXE boot, the menu list displays the
boot menu options you created in the order you set.

Select which Shared boot menu option you want to be used as the default boot option on client
computers.

Enable and configure the level of logging for various PXE server functions and communications.

PXE Manager
When you do a Deployment Server Simple or Custom install, if you select Install PXE Server, the
PXE Manager Service will always install to the same computer as the Deployment Server. PXE
Manager synchronizes Local and Shared boot menu options with all PXE Servers on the network,
and communicates with the Deployment Server and the Deployment database. It stores all PXE boot
images and sends boot images to PXE servers that require them or need to be updated. It also keeps
track of the PXE Configuration Utility properties settings for each PXE Server you have on the
network and applies the modifications to each PXE server if there is a change.
PXE BIS integration
Boot Integrity Services (BIS) is easier to implement and manage. BIS is now centrally managed by
PXE Manager, which manages certificates through a cetral interface. Enable BIS from the PXE
Configuration Utility, provide a certificate password, and then install BIS Certificates to any
computer or group of computers from the Deployment Console.
Assign PXE boot menu options to automation tasks in a Deployment job
You can create 1 Deployment job with 2 tasks, and assign a different boot menu option to each of
the tasks. Example: assign a DOS boot menu option to a Run script task to update the client
computer's BIOS, and then assign a Windows PE boot option to a Create disk image task for
imaging.
Only Shared boot menu options can be assigned to the following automation tasks:

Altiris Deployment Solution Reference Guide

33

Chapter 1: New Features of Deployment Solution 6.5

Run script

Create disk Image

Distribute disk image

Scripted OS install

Backup registry

Restore registry

RapiDeploy performance
You can select which performance option you want to use when imaging client computers. By
default, the Performance field has change from Balanced for size and speed to Optimize for speed.
This new option makes it so there is less data compression, which increases the size of image files.
However, it will take less time to decompress an image file when it is restored to a client computer.
Enhanced status display from RapiDeploy to Deployment Server
This feature lets you view the imaging status for client computers from the Deployment Console
when an imaging job runs. The client computer is passed the parameter, -dsstatus, which returns the
imaging status to the Deployment Console.
Example: When the imaging job begins to run on the client computer, the Deployment Console will
display the status in the following format.
Client computer images
Uploading disk image (as master); Time Remaining:13:29(4% complete)
Multicasting images
Downloading disk image (as client); Time Remaining:6:54(32% complete)
Downloading disk image (as master); Time Remaining:6:54(32% complete)
The percentage displayed on the Deployment Console updates when the monitor refreshes. The
minimum refresh rate is 30. You must also select the display status option in the Deployment
Console, because this feature is not set as a default option. Do the following:
1

From the Deployment Console, select Tools > Option.

Click the Global tab.

Select Display imaging status on console.

HTTP image access


When you create a Deployment job with the tasks, Create Image or Distribute Image, you must enter
the path and file name to where the physical image files are located. RapiDeploy will now accept an
HTTP path to save or restore images.
Example: The file format is http://<IP address>/images/<filename.img>. There is no naming
resolution for DOS pre-boot environments, so you must always enter a specific IP address. The
images directory is the physical location where images will be stored.
You can create an images virtual directory in IIS, or any physical directory location that users have
will have access. The virtual directory properties must have Read and Write selected on the Virtual
Directory tab. Select Basic authentication (password is sent in clear text) on the Directory Security
tab. If you create an images directory in any other location, make sure the security properties for the
directory has Read and Write selected for users.
The HTTP protocol for imaging is not necessarily faster than TCP/IP, but it increases the options for
how you want client computers to connect to a directory for imaging.

Altiris Deployment Solution Reference Guide

34

Chapter 1: New Features of Deployment Solution 6.5

DoD wipe program


The -dod parameter has been added to the Wipe disk utility. Previously, when you ran the Wipe disk,
it would wipe data from the hard disk using 1 number and 1 pass. The -dod parameter lets you enter
a number, which is use as a pattern for the first pass of the wipe. The second pass of the wipe is the
complement, or opposite bit pattern of the number used for the first pass. The third pass of the wipe
is a random pattern for every other bit through out the entire hard disk. Using this parameter to wipe
a disk protects unclassified data layers from being restored.
Divide images into smaller files
Image Explorer lets you split a single image file into smaller segments of some other size, and then
store the smaller files on CDs. However, you must provide your own third party CD burning
software.
When you split an image, a new image file of the split size is created from the original image, without
causing damage to the source. You can also convert an existing image file of any split size into
another image file of any split size. This enhancement will not work on version 4.5 or older image
files, but you can split image files that were created using the newer 5.6 version.
Image Explorer enhancements
There are new enhancements to Image Explorer, which provides you the ability to access these
features without having to run RapiDeploy. You can now do the following:

Add file to an image file using command line options

Extract a file from an image file using command line options

Create .IMX image index file

Convert old 4.5 format image file to new 5.6/6.0 format image file

Convert image file to self-extracting image

Exclude volumes

Altiris Deployment Solution Reference Guide

35

Planning and Installing


Deployment Solution is a highly flexible and scalable system. It is designed to meet deployment,
management, and migration needs for small, medium and large organizations with diverse
topologies and varying computer management requirements. This section provides steps for
installing Deployment Solution components, but also includes system architecture details and
discusses planning strategies to install and optimize your Deployment Solution system.
Quick Links
Planning Deployment Solution
Installations on page 401

Design a system for small or large environments


with varying needs. Understand basic scalability
and optimization principles to set up your system.

Deployment Solution
Architecture on page 395

View a basic diagram and overview of the


components that make up Deployment Solution.

Installing Deployment Server


on page 37

Install the Windows components of Deployment


Solution.

Installing Deployment Solution Install Deployment Solution by first installing


Notification Server and then pushing down an
from the Altiris Console on
installation of Deployment Server. You can then
page 69
install Deployment Server systems to specific sites
or network segments. A system of Package
Servers can also be implemented.

Altiris Deployment Solution Reference Guide

36

Chapter 2:

Installing Deployment Server


Deployment Server is a flexible, scalable computer deployment and management system that can be
installed and configured quickly on a single computer, or installed across several computers to
distribute processing for large enterprise environments. You can run a Simple install to position all
Deployment Server Components on a single computer (most frequently used), or plan and perform
a Custom install to distribute installation of components across separate computers in the site. The
Deployment Web Console can be installed as part of the Deployment Server installation on any
computer running Microsoft IIS.
After installing Deployment Server components, you can remotely install Deployment Agents on all
types of computer resources across your organization: laptops and handhelds, LAN and web servers,
network switches, and so on. Windows computers, Linux computers, and handhelds can be managed
as a unified environment, with each client communicating through its own Deployment agent to
update inventory data and react to Deployment Server commands and deployment tasks.
Select one of the following methods for installing a Deployment Server system:

Simple Install for Deployment Server (page 42)

Custom Install for Deployment Server (page 44)

Component Install for Deployment Server (page 46)

To install Deployment Agents on the client computer, see Installing Deployment Solution Agents
on page 47
Note: You can also install the Deployment Server components remotely from the Altiris Console.

Deployment Server Components


The Deployment Server system includes the following components:

Deployment Console (page 38)

Deployment Server (page 38)

Deployment Database (page 38)

Deployment Share (page 39)

PXE Server (page 40)

DHCP Server (not an Altiris product)

Deployment Web Console (page 41)

Installing Deployment Solution Agents (page 47)

Sysprep (page 67)

All of these components can be installed on the same computer or distributed across multiple
computers as needed for your environment.

Altiris Deployment Solution Reference Guide

37

Chapter 2: Installing Deployment Server

Deployment Server Components

Deployment Console
The Deployment Console is the Win32 user interface for Deployment Solution. You can install this
Windows console on computers across the network to view and manage resources from different
locations. In addition, from this console, you can access the Deployment Database on other
Deployment Server systems to manage sites across the enterprise. See Connecting to Another
Deployment Server on page 104.
Deployment Console communicates with the Deployment Database and Deployment Server
services. In a Simple Install for Deployment Server, the Deployment Console is installed on the
same computer as all of the other components. In a Custom Install for Deployment Server, you need
to make sure that a connection is available to these computers and security rights are set. You will
need to have administrative rights on any computer running the Deployment Console.
See also Deployment Web Console on page 41, Managing from the Deployment Console on
page 89, and Deployment Server Components on page 37.

Deployment Server
Altiris Deployment Server controls the flow of the work and information between the managed
computers and the other Deployment Server components (Deployment Console, Deployment
Database, and the Deployment Share). Managed computers connect and communicate with the
Deployment Server to register inventory and configuration information and to run deployment and
management tasks. Computer and deployment data for each managed computer is then stored in the
Deployment Database.
Note: To view, start, or stop Deployment Server, go to the Altiris Server services in your Windows

Manager.

Managed computers require access to the Deployment Server at all times, requiring that you have
administrative rights on the computer running the Deployment Server.

Setting Rights to install Deployment Server

Create a user account to run the Deployment Server. The service runs
as a logged in user, not as a system account. You must create this
account on all Deployment Server computers. The account must have
full rights to the Deployment Share. The account must have a nonexpiring password.
Assign a static IP address to the Deployment Server computer. Other
components will not be able to connect to the Deployment Server if you
use DHCP and dynamically change the IP address.
To install the Deployment Server on a remote computer, the default
NT/2000 administration shares must be present. Restore any shares
that have been removed before you install the Deployment Server.
Hint: Creating an administrative account using the same name and password on each computer will

be easier to remember than using the names and passwords of existing accounts.

Most packages (RIP, Personality Packages, and MSI files) are passed through the Deployment
Server. Therefore storing these files on the same computer as the Deployment Server can speed up
the deployment of these packages. Image files, however, are sent directly from the Deployment
Share to the client computer when executing an imaging task.
See also Deployment Server Components on page 37.

Deployment Database
The Deployment Database can be installed on Microsoft SQL Server 2000 or Microsoft Desktop
Engine (MSDE) 2000. See Deployment Server System Requirements on page 41.

Altiris Deployment Solution Reference Guide

38

Chapter 2: Installing Deployment Server

Deployment Server Components

Note: In Deployment Solution 6.0 and later, if you have multiple instances of the Microsoft SQL
Server already set up, you can identify a specific instance using this format: <database
instance>\express. Example: if you have a clustered Microsoft SQL Server named

SQLClusterSvr to manage multiple Deployment Solution systems on different network segments,


you can enter the name SQLClusterSvr\salesSegment or

SQLClusterSvr\marketingSegment during the Deployment Server setup


depending on the previously established database instance. This feature is supported in the silent

install INI file and the GUI install executable.

The database maintains all of the information about the managed computers, such as:
Hardware.

RAM, Asset tag, and Serial numbers

General Information.
Configuration.

Computer name and MAC address

TCP/IP, Microsoft Networking, and User information

Applications. The applications installed and information about these applications, such as the name
of the application, Publisher, and Product ID
Services.
Devices.

Windows services installed

Windows devices installed such as network adapter, keyboard, and monitors

Location information.

Contact name, phone, E-mail, Department, Mail Stop, and Site

The Deployment Server Database also contains jobs and other data used to manage your computers.
Note: You can install a single Deployment Database per Deployment Server system--you cannot

have two databases storing data for a single computer. If the computer you are installing the database
to has an existing Microsoft SQL Server, then the Deployment Database will simply be added to
that instance of the database engine.

Support for Multiple Database Instances


In Deployment Solution 6.0 and later, you can identify a named instance of the Microsoft SQL
Server when installing Deployment Solution. You can now identify other named instances of
Microsoft SQL Servers rather than accessing only the default instance. This feature lets you identify
and run multiple databases from one clustered Microsoft SQL Server to manage multiple sites or
network segments. This feature is supported in the silent install INI file and the GUI install
executable. See Custom Install for Deployment Server on page 44. The 6.5 release of Deployment
Solution also supports providing a different name for the Deployment database other than the default
eXpress.
See also Deployment Server Components on page 37.

Deployment Share
Deployment Share is a file server or shared directory where Altiris program files and packages are
stored. The Deployment Share can be a shared directory (default Simple install in Program Files\
Altiris\eXpress\Deployment Server) or another file server (in the Custom install you can
assign a Microsoft Windows or Novell NetWare file server).
Deployment Share is where you store image files, registry files, MSI packages, Personality
Packages, script files, and more. When a computer is being deployed or managed, Deployment
Server will store and retrieve these packages from the Deployment Share as needed.

Altiris Deployment Solution Reference Guide

39

Chapter 2: Installing Deployment Server

Deployment Server Components

If you are installing Deployment Solution on a remote file server (not


the computer where you are running the install program), create a
share (or give Read/Write rights for NetWare) on the file server
where Deployment Server will be installed. The share must allow
access to all of the other components, including managed computers
and the user account that runs the Deployment Server.
This share must be created before you begin installing. If you are
not installing to a remote computer, you can select the option to
create the share during install.
Note: You can install only one Deployment Share per Deployment Server system. However, if the

Deployment Share's hard drive gets full, other computers can be used as additional, backup storage
points. In some cases, other systems emulating a Microsoft or NetWare environment can be used as
the Deployment Share.

Note for NetWare users: If you have trouble using the Novell NetWare server as a Deployment

Share, install the Novell Client rather than the Microsoft NetWare Client.
See also Deployment Server Components on page 37.

PXE Server
The Altiris PXE Server provides client computers on a subnet the ability to boot into an automation
operating system.. When the Deployment Server sends a deployment job, the client computer
receives a request to boot reboot. PXE-enabled computers will connect to the first PXE Server they
discover and then load the PXE boot image which contains the automation operating system along
with an automation agent. The client's automation agent will then communicate with the
Deployment Server and receive the job that was scheduled for that computer.
You can install PXE Server on a Microsoft Server 2003, Windows 2000 Server and Advanced
Server. The PXE Server also functions on the same protocols as a standard DHCP Server so you can
place the PXE Server on any Windows server that you would place a DHCP server. You can also
install as many PXE Servers as required in your system, but you must also have a DHCP Server
servicing addresses to PXE-enabled clients in their scope.
The PXE Server sends a boot menu option list to the client when the computer performs a PXE boot.
The deployment job, which contains at least 1 automation task, will either use the default automation
environment, or one that is specified by a user who has permissions to create a deployment job.
When a boot menu options is selected the client will then request the PXE boot files from the PXE
MTFTP Server. These are then downloaded from the PXE MTFTP Server to the client computer's
RAM storage. The client computer will always boot according to the request and reply
communications taking place between the Deployment and PXE Servers. S
Altiris supports DOS, Linux, and Windows Pre-Installation Environment (Windows PE) as pre-boot
environments. These options let you create a single job that contains multiple automation tasks, each
of which can use their own pre-boot environment. The default automation environment (the first preboot operating system files installed during the Deployment Solution installation) will be used for
Initial Deployment, unless you specify otherwise.
See also Pre-boot Operating System (Simple) (page 64) , Installing Automation Partitions (page
142) , and PXE Configuration Utility Help.
DHCP Server
The DHCP (Dynamic Host Configuration Protocol) server is a server set up to assign TCP/IP
address to the client computers. This server is not an Altiris product, but it is required if you intend
to use PXE Server.
We suggest that you use DHCP to manage the TCP/IP address in your network regardless of whether
you use PXE or not. This will greatly reduce the amount of time it takes to set up and manage your
computers.
See also Deployment Server Components on page 37.

Altiris Deployment Solution Reference Guide

40

Chapter 2: Installing Deployment Server

Deployment Server System Requirements

Deployment Web Console


The Deployment Web Console remotely administrates a Deployment Server installation from a web
browser. It deploys and manages Windows and Linux computers (both client and server editions) in
real-time with many of the features present in the Deployment Console.
The Deployment Web Console can be installed on any computer running the Microsoft IIS Server,
including a computer running Deployment Server, Notification Server, or a remote computer
running only Microsoft IIS.
Note: If Microsoft IIS is running, the Deployment Web Console will be installed automatically

during the Windows installation.

Important: The DS Installer does not detect the version of MDAC that is installed. The Deployment

Web Console requires MDAC version 2.71 or later to install. If the version of MDAC is earlier than
2.71, the web console will display a target of invocation error.

See also Deployment Console on page 38 and Deployment Server Components on page 37.

Deployment Server System Requirements


The following lists the system requirements for Deployment Server components and the network
environment.
Network

TCP/IP is used for communication between all Deployment Server components. If you have a
NetWare file server for your Deployment Share, IPX can also be used to communicate with this
component.

For Windows 2000 systems, you must set up Active Directory with the Permissions compatible
with pre-Windows 2000 option. If you choose the option Permissions compatible only with
Windows 2000 servers, the Deployment Server cannot manage domain accounts for you.

If you are using Windows 2000 only permissions, change them to the pre-2000 option from the
Windows Start menu. Open a DOS prompt to add the group Everyone by typing the following:
net localgroup Pre-Windows 2000 Compatible Access Everyone /add

Then restart all domain controllers for the change to take effect.

Deployment Server

256 MB of RAM

200 MB of available disk space

Deployment Server Components

Component

Hardware

Software

All components require Pentium III processors


Deployment Server RAM: 256 MB
Disk Space: 200 MB required

Windows 2000 Server and Advanced


Server
Windows Server 2003

Deployment
Console

RAM: 128 MB
Disk Space: 3.5 MB

Windows 2000 Professional, Server and


Advanced Server
Windows XP Professional
Windows Server 2003

PXE Server

Memory: 128 MB
Disk Space: 25 MB (for boot

DHCP server (must be on the network, but


does not have to be on the same computer
as PXE server)
Windows 2000 Server or Advanced Server
Windows Server 2003

files)

Altiris Deployment Solution Reference Guide

41

Chapter 2: Installing Deployment Server

Simple Install for Deployment Server

Deployment Server Components

Component

Hardware

Software

Deployment
Database

Memory: 128 MB
(Microsoft SQL ServerTM 2000 (SP3) or
Disk Space: 55 MB (for program MSDE 2000 (SP3)

files), plus space for data.

Deployment Share Memory: 128 MB


(File server for
Disk Space: 100 MB for
storage)
Deployment Server program
files plus space for storing files
(image, boot, RIP, etc.)

Windows NT (SP6)
Windows 2000 Server or Advanced Server
Windows Server 2003
NetWare (file server only. Cannot use for
any other components).

Deployment Web
Console

Windows 2000 Professional, Server or


Advanced Server
Windows XP Professional
Windows Server 2003
MS IIS 5.5
MDAC 2.71 or later.

Memory: 128 MB

Deployment Agents
Minimum client requirements:

Pentium processor
Operating Systems:

Windows 95 or later
Linux: Red Hat 7.2, 7.3, 8.0, 9.0 and Advanced Server 2.1, 3.0
Linux: SuSE 8.0, 8.1 and Enterprise Server 8
Linux: United Linux 1.0

5 MB contiguous disk space

See the following sections for additional information:

Installing the Deployment Agent on Windows (page 48)

Installing Deployment Agent on Linux (page 52)

Installing the Automation Agent (page 53)

Installing Deployment Agent for PocketPC (page 54)

Simple Install for Deployment Server


The Simple Install places all Deployment Server Components Deployment Server, Deployment
Console, Deployment Share, and Deployment Databaseon the same computer. You can install the
Deployment Server with a Microsoft Desktop Engine (MSDE) from the Simple Install. The
Deployment Web Console will install automatically during a Simple Install (and during a silent
install) if the Microsoft IIS services are currently running on the selected computer.
Downloads for the Altiris Deployment Solution are available either on the Altiris product CD or can
be downloaded from www.altiris.com.

AltirisDeploymentSolutionWin_6_5 installs all of the Windows


components of Deployment Solution. Using the Simple Install option, you
can install MSDE 2000 on a local computer if a database is not already
installed.
Note: Simple installation works only with a default MSSQL 2000 or MSDE install. Customized

installation of MSSQL, will not work with the simple installation of Deployment Solution.

Altiris Deployment Solution Reference Guide

42

Chapter 2: Installing Deployment Server

Simple Install for Deployment Server

To run a simple install


1

Start the server and log on using the administrator account that you created for the Deployment
Server. See Deployment Server System Requirements on page 41.

Launch the appropriate Altiris Deployment Server installation file and follow the setup steps.
The Deployment Server self-extracting install dialog box opens.

Click the Use current temp folder option to use the current temporary folder to download
installation files or Extract to a specific folder option to set a path to an existing folder to download
installation files. Click Extract and Execute App option to extract and execute the application
immediately.

Click Simple Install.

Select Include PXE Server. This option will install the Altiris PXE Server. See PXE Server on
page 40. This is optional.

Click Install. Click Yes to the Software License Agreement.

Enter the following information in the Install Information screen:


a

In File Server path, enter the drive letter and the path where you want to install the
Deployment Server program files.
(The default path is C:\Program Files\Altiris\eXpress\Deployment Server.)

Select Create eXpress share to create a Deployment Share on the computer. The Deployment
Share lets you store files on the computer and run Deployment Server system applications.
See Deployment Share on page 39.

Click License File and browse to locate a license file (.lic file). This is the activation key you
received when you registered your Altiris software. Click Upgrade using existing license to
upgrade the installation using an existing license. If you do not have a license file, click Free
7 day license. The installation will continue and allow you to use a free evaluation license file.
See the Altiris Getting Started Guide for further licensing information.
Note: You do not need to apply a license key to activate the HP Thin Client t5000 Series.

This managed client computer will automatically receive a non-expiring license when
connected to the console.

Enter an administrator user name and password for the Deployment Server system. This
account must already exist. By default, the name you are currently logged on as will display.
If you use a domain account, enter the domain and the user name (Example:
Domain1\administrator).

Click Next. The Installation Information dialog box is displayed that lists the selected
Deployment Server components to be installed.
Note: If you are upgrading your installation, a message box will open asking: Do you want to
replace the share? Click Yes and continue. If you click No, then a secondary message box will

open, stating that the share is already in use and you need to manually set the share to point
to the correct directory. Click OK to this message. This features indicates that you may be
creating a new share (specifically when you changed the path in the previous screen) and that
you need to manually point to the new share after installation.

Click Install to install the components listed on the summary screen, or Back to modify settings
before starting the installation. The installation process begins and might take several minutes to
complete.

The Installation Information dialog box is displayed stating if you want to install clients.
Enable Sysprep Support. Select this option to enable Sysprep support. Provide the location of the
Microsoft Sysprep files.
Remote Install Clients. Select this option if you want to push the Deployment Agent to computers
running the Windows NT, 2000, XP, and Windows Server 2003 operating systems.
Download Adobe Acrobat. Select this option if you want to download the Adobe Acrobat Reader

to read documentation in PDF format.

10

After the installation is complete, click Finish.

Altiris Deployment Solution Reference Guide

43

Chapter 2: Installing Deployment Server

Custom Install for Deployment Server

You have successfully completed a Simple install for a Deployment Server system. Click the
Deployment Console icon on your desktop to view all computer resources running Deployment
Agents configured for your Deployment Server.
See Custom Install for Deployment Server on page 44.

Custom Install for Deployment Server


The Custom Install lets you distribute all Deployment Server ComponentsDeployment Server,
Deployment Console, the Deployment Share, and the Deployment Databaseon different
computers. You can install Deployment Server with Microsoft Data Engine (MSDE) or install it to
an existing SQL Server.
Downloads for the Altiris Deployment Solution are available either on the Altiris product CD or can
be downloaded from www.altiris.com.

AltirisDeploymentSolutionWin_6_5 installs all of the Windows


components of Deployment Solution. Select the Custom install
option to add new components or to install Deployment Solution to
an existing database.

To run a custom install


1

Start the server and log on as the administrator account that you created to run Deployment
Server. See Deployment Server System Requirements on page 41.

Launch the appropriate Altiris Deployment Server installation file and follow the setup steps.
The Deployment Server self-extracting install dialog box is displayed.

Click the Use current temp folder option to use the current temporary folder to download
installation files, or click the Extract to a specific folder option to set a path to an existing folder
to download installation files. Click Extract and Execute App option to extract and execute the
application immediately.

Click the Custom Install option if any of the following conditions exist:

You are using the NetWare file server as a Deployment Share.

You are managing many computers and require a distributed architecture to meet bandwidth
restrictions and other design requirements.

Click the Install button. Click Yes to the Software License Agreement.

Install the Deployment Share and enter the license file location:

In File Server path, enter the drive letter and the path where you want to install the
Deployment Server program files. The default path is C:\Program
Files\Altiris\eXpress\Deployment Server.

Select Create Deployment Share to create a Deployment Share in the system. The Deployment
Share lets you store files on the computer and run Deployment Server system applications.
The Deployment Share can be on a Microsoft Windows server or Novell NetWare server.
(You can only create the share if it is on a Microsoft Windows Server; the Novell share
should already be set up.) See Deployment Share on page 39.

Click License File and browse to locate a license file (.lic file). This is the activation key you
received when you registered your Altiris software. Click Upgrade using existing license to
upgrade the installation using an existing license. If you do not have a license file, click Free
7 day license. The installation will continue and allow you to use a free evaluation license file.
See the Altiris Getting Started Guide for further licensing information. Click Next.
Note: You do not need to apply a license key to activate the HP Thin Client t5000 Series.

This managed client computer will automatically receive a non-expiring license when
connected to the console.

Altiris Deployment Solution Reference Guide

44

Chapter 2: Installing Deployment Server

Custom Install for Deployment Server

Enter Deployment Server information. Select the computer to install Deployment Server, the
services that controls the flow of the work and information between the managed computers and
Deployment Server components. Install the Deployment Server on this computer or on a remote
computer.

Enter a static IP address for the Deployment Server computer to ensure that the IP address
remains constant. Type the port information in the Port: text box.

Enter the path where the Deployment Server should be installed.

Provide account information that already exists on the Deployment Share and the
Deployment Server. Click Next. See Deployment Server on page 38.

Enter Deployment Database information. Identify where you want to install the database, or select
an existing Microsoft SQL Server from the list of computers. See Deployment Database on
page 38.
Note: If you have multiple instances of the Microsoft SQL Server already set up, you can identify
a specific database instance in this field using the format: <SQL Server Name>\<database
instance>.

Depending upon the selection of SQL Server instance, the default port at which the selected
instance is listening will be displayed in the SQL Port Number text box. You can edit the port
number if you have manually entered the SQL Server name or if the port number does not get
filled automatically due to some fire wall restriction.
You can choose to use a different name other than eXpress for your Deployment Database. Type
the alternate name in the Database Name: field and click Next.
Note: The name of the Deployment Share, however, will still remain eXpress.
9

Identify the type of Deployment Database authentication to be used. Enter the user name and
password if SQL Server authentication is used. Click Next.
If a previous installation of the Deployment Database is detected, a message appears stating
whether you want to preserve or overwrite the existing database.

10

Enter the Pre-boot Operating Systems information required for Boot Disk Creator. Select any
one of the four options from FreeDos, MS-DOS, Linux, and Windows PE. Click Browse to select
the FIRM file (for FreeDos and Linux OS) or enter the path for the location of operating system
files (for MS-DOS and Windows PE).

11

Enter PXE Server information. Click Next. See PXE Server on page 40.

Select the pre-boot operating system to use as the default PXE boot menu item. You can
select DOS, Linux, or Windows PE.

12

Enter information on how you want to connect your managed computer to connect to the
Deployment Server. Click Connect directly to Deployment Server and provide the DS IP address
and Port or click Discover Deployment Server using TCP/IP multicast and provide a Server name. If
the Server name box is left blank then it finds the first Deployment Server that responds.

13

Enter Deployment Console information. Select if you want to install on the computer you are
currently installing from or on a remote computer.

14

Provide information for installing the Deployment Web Console on the computer you are
currently installing from. This computer must be running Microsoft IIS. You are required to
provide information about the path where you want to install the Deployment Web Console, and
also valid user credentials. Click Next. See Deployment Web Console Information on page 67.
Note: This option will be disabled if Microsoft IIS is not detected.

15

The Installation Information dialog box will open to display the selected Deployment Server
components to be installed.
Note: If you are upgrading your installation, a message box will display stating: Do you want to

replace the share? Click Yes and continue. If you click No, then a secondary message box will
display stating that the share is already in use and you will need to manually set the share to point
to the correct directory. Click OK. This features tells you that you may be creating a new share
(in rare occurrences where you changed the path in the previous screen) and you may have to
manually point to the new share after installation.

16

Click Install to install the components listed on the summary screen, or choose Back to modify
settings before starting the installation. The installation process will begin, and might take
several minutes.

Altiris Deployment Solution Reference Guide

45

Chapter 2: Installing Deployment Server

17

Component Install for Deployment Server

Install Deployment Agent to client computers. The Installation Information dialog box will open
asking if you want to install clients.
Enable Sysprep Support. Select this option to enable Sysprep support. Provide the location of the

Microsoft Sysprep files.

Remote Install Deployment Agent. Select this option if you want to push the Deployment Agent to
computers running the Windows NT, 2000, XP, and Windows Server 2003 operating systems.
Download Adobe Acrobat Reader.

Select this option if you want to download the Adobe Acrobat


Reader to read documentation in PDF format.

18

After the installation is complete, click Finish.

You have successfully completed a Custom install for a Deployment Server system. Click the
Deployment Console icon on your desktop to view all the computer resources running Deployment
Agents configured for your Deployment Server.
See Simple Install for Deployment Server on page 42.

Component Install for Deployment Server


The Component installation option lets you add selected Deployment Server Components
Deployment Console, Deployment Web Console, Altiris PXE Server, and Deployment Agents to the
existing Deployment Share. Additionally, you can also add Microsoft Sysprep files.
To install components
1

Start the server and log on with the administrator account that you created to run Deployment
Server. See Deployment Server System Requirements on page 41.

Launch the appropriate Altiris Deployment Server installation file and follow the setup steps.
The Deployment Server self-extracting install dialog box will open.

Click Extract and Execute App.

Click Add Component.

Click Install. Click Yes to the Software License Agreement.

Enter a path for the Deployment Share. Click Next.

Select the Components to install.

Install an additional Deployment Console.

Install an additional Deployment Web Console. Click this option to install an additional
Deployment Web Console on the local computer. The web console will install on the local
computer if it is running Microsoft IIS. See Deployment Web Console Information on
page 67.
Install an additional Altiris PXE Server. Use this option to add additional PXE Servers across a
network segment to handle boot requests for large environments.
For all of the available options for installing Altiris PXE Server, see PXE Server Install on
page 66.

Click this option to install another Deployment


Console (a Windows executable) on another computer. You can add as many Deployment
Consoles as required to manage from multiple consoles across your system, but you can only
install one at a time.

Install additional Deployment Agents. Click this option to install additional Deployment
Agents on client computers, setting up managed computers in the Deployment Server
system.

Add Microsoft Sysprep files. Click this option to install the Microsoft Sysprep files, if you did
not install them earlier. See Sysprep on page 67.

Select Download Adobe Acrobat (for documentation) if you want to install Adobe Acrobat to read
the product documentation.

Altiris Deployment Solution Reference Guide

46

Chapter 2: Installing Deployment Server

Installing Deployment Solution Agents

Installing Deployment Solution Agents


Each client computer requires the Deployment Agent to run as the Production Agent on a local hard
disk, which communicates with the Deployment Server and registers in the Deployment Database.
For Windows and Linux client computers, Deployment Solution lets you push agent software to
a client computer from a Deployment console, or you can pull the Deployment agent from the
client computer from the Deployment Web Console (or just pull it from the Deployment Share).
You can install an embedded (recommended) or hidden automation partition, which contains an
Automation Agent that establishes communications with the Deployment Server to run the
deployment jobs that have been assigned to the client computer. See Installing Automation
Partitions (page 142) . The Deployment agents for handhelds are also easily installed from the
console using prebuilt jobs.

Deployment Agent. Install a Production Agent to a Windows desktop, notebook, or server,


computer. You can also install this agent to any supported Linux workstation or server. See
Installing the Deployment Agent on Windows on page 48.

Deployment Agent on Linux. Install on any supported Linux workstation or server. See

Automation Agent. Install on any Windows desktop, notebook, or server computer. See
Installing the Automation Agent on page 53.

Installing Deployment Agent for Pocket PC. Install on handheld computers running the Pocket
PC operating system. See Installing Deployment Agent for PocketPC on page 54.

Installing Deployment Agent on Linux on page 52.

Client Connectivity and Network Adapters


Altiris supports all standard network adapter cards and includes many drivers with the installation
of Deployment Solution. However, sometimes outdated drivers (including default drivers that come
with the hardware) cause problems when clients are in automation mode. To avoid these problems,
you should check the manufacturers web site for your network adapter to make sure you use their
latest driver in your pre-boot operating system configuration file.
Some common client problems that can be solved by updating drivers are:

Locking when loading drivers or failing to connect to the server

Locking when imaging (downloading, uploading, or multicasting)

Microsoft Client Drivers


Boot Disk Creator is set up to work with drivers that follow a certain standard. Since not all NIC
drivers follow that standard, files may need to be moved to a different location. The following 3 files
must be in the same directory:

The DOS driver for your card (drivername.dos)


The sample protocol.ini that comes with your driver (protocol.ini)
The OEM setup file that specifies the DOS driver (oemsetup.inf)

Example: the OEM setup file will contain lines similar to the following:
[netcard]
NGRPCI=NETGEAR FA310TX Fast Ethernet PCI
Adapter,0,ndis,ethernet,real,NGRPCI,NGRPCI_NIF
[NGRPCI] (This header must be the sixth item listed in the line above)
Device=NGRPCI.DOS (If this line is missing, add it. The syntax is
device=drivername.)

If there is no protocol.ini file, create a text file that contains the following command:
DriverName=drivername

Altiris Deployment Solution Reference Guide

47

Chapter 2: Installing Deployment Server

Installing Deployment Solution Agents

Novell Client Drivers


The Boot Disk Creator does the following:

Searches all subdirectories for a directory that contains *.ins, *.com, and net.cfg files. (They
must be in the same directory.) The .ins file is then opened to get information about the network
card.

The program searches the file for a line starting with a carat (^). This line must have at least two
values listed, separated by a comma. The two values needed are the description of the card
(value1), and the .com driver file name (value2).

The following are requirements to install Deployment Agents to set up managed computers for each
Deployment Server system.

Installing the Deployment Agent on Windows


For client computers running a Windows operating system, Deployment Solution lets you install the
Deployment Agent software using Remote Agent Installer to push the agent to client computers
from the Deployment console. Or, you can pull the Deployment Agent at the client computer by
accessing the Deployment Share or downloading the install package from the Deployment Web
Console. You must have administrative rights to the client computers and File and Print Sharing
must be enabled to install the agent software.

Click the Remote Agent Installer button on the Deployment Console toolbar, or click
to open the utility program. You can also download
aclient.exe from the network share or the Deployment Web Console to install a
Deployment agent. See Remote Agent Installer (page 49)
Tool > Remote Agent Installer

Windows 9x. For Windows 95/98/Me clients, you must install the agent software locally. There are

several ways to do this: You can add commands to the client login script to map to the Deployment
Agent on your file server and run the executable, or you can e-mail the executable or a shortcut to
users and run the install program from the client computer. For Windows 95, you must add Microsoft
updates for COM support for the Deployment Agent to run on the client computer.

Windows XP. The Deployment Agent will not install to Windows XP if the Use simple file sharing

(recommended) option is enabled on Windows XP. To ensure that this option is cleared, open My
and click Tools > Options. Select the View tab and ensure that the Use simple file sharing
check box is cleared.
Computer

When remotely installing the Deployment Agent on a Windows XP computer, each user must have
an account password. Remote Agent Installer will return an error message if it is unable to get to the
Administrative share on the remote XP computer for each user. Windows XP will not allow access
to any Administrative shares if the user on that computer does not have an assigned password
(including the guest account). When all users have passwords and the Network Setup Wizard has
run, you can successfully install the Deployment Agent using the Remote Agent Installer.
Note: Before installing the Deployment Agent on computers running Windows XP, disable the

simple file sharing option.


.

Deployment Agent

Processors

Pentium

Disk space

5 MB contiguous

Altiris Deployment Solution Reference Guide

48

Chapter 2: Installing Deployment Server

Installing Deployment Solution Agents

Deployment Agent

Operating systems: Windows 95, 98, ME


Windows NT 4.0 (Service Pack 4 or later)
Windows 2000
Windows XP
Windows Server 2003
RAM

32 Mb

Remote Agent Installer


You can use the Remote Agent Installer utility program to install the Deployment Agent on
Windows 2003/XP/2000/NT operating systems. For Windows 95/98/ME computers, you will have
to install manually by running aclient.exe downloaded from the network share or from the
Deployment Web Console. After downloading the install executable, run it on the local computer to
install.

Enter administrator account information


Enter common administrator credentials for all client computers, or keep default to be prompted for
login credentials for each client computer.
Let me specify a user name and password for each computer as its installed. Prompts for an
administrative user name password for each computer in the remote install list. This is the default
option.
Use this username and password for all clients. Enter credentials for an administrator account that has
rights to all client computers added to the remote install list.

Click Next.

Specify install directory


Enter a location to install the Deployment Agent.
Install directory. Enter the path where the Deployment Agent will be installed on the client computer.
Enable this agent to use SIDgen and/or Microsoft Sysprep. Select if you are going to set NT security on

the client computer. If you enable this option, you will be required to locate and download program
install files.
View agent settings in the summary box.
Click Change Settings to set Production Agent Settings on page 120 for the Deployment Agent.

Automatically Add to a Group


You can add new computers to the All Computers group automatically, or specify another computer
group.
Add clients to default group.

Adds new computers to the All Computers group.

Add clients to a specific group.

separate subgroups.

Specify another group to add new computers. Use back slashes to

Select Computers on the Network


Identify client computers on the network and add them to a list of computers to remotely install the
Deployment Agent.
Add.

Select the computers by name in the list, or enter a computer name or IP address.

Altiris Deployment Solution Reference Guide

49

Chapter 2: Installing Deployment Server

Computer Name.

Installing Deployment Solution Agents

Enter the name of a computer on the network or its IP address.

Properties.

Select a computer and view agent install settings. You can also change SID and Agent
settings from this Agent Properties dialog box.

Import. Find an RCI file and import new computers from a file previously created file in a DOS text

file.

This file has the following parameters: -c:[computer] u:[username] p:[password]


i:[input file]. The parameters must be entered in this order. The password parameter is not

required if the administrator account does not have one assigned. If you are using the default settings,
you do not need to specify an input filename. Each computer entry must be on a separate line.

Export. You can export the computers listed into an export file for future use. The default extension
is *.RCI. Remote Agent Installer first looks for an RCI file extension, but any DOS text file can be
used.

When the computers appear in the installer list and the properties have been set, click Finish. The
status of the agent install is shown on screen.
After the Deployment Agent is installed, it will connect to Deployment Server automatically and
appear in the Computers pane of the Deployment console.

Download Altiris SIDgen and/or Microsoft Sysprep


If you selected Enable this agent to use SIDgen and/or Microsoft Sysprep on the previous dialog box,
the Remote Agent Installer dialog box will assist in finding required install files for specific versions
of the hard disk configuration utilities from Altiris and Microsoft.
Select to download and install the Altiris SIDgen executable or the Microsoft
Sysprep files. The Microsoft Sysprep files are specific to the NT operating system.
You can select to install one or both utilities.
Update file system permissions when changing SIDs. Click to automatically update file system
permissions to maintain the individual file permissions that may have been set. This also includes
the individual network shares that may exist on this client (in NT you can set permissions on folders,
shares, and individual files.) Checking this option also includes those individual permissions. This
will take a long time to convert the SIDs. To make the SID utility run faster, do not mark this option.

The installation program for installing Altiris SIDgen is located in the Deployment
Share (in Program Files > Altiris > eXpress > Deployment Server
> sidgen.exe by default).
To install Microsoft Sysprep, you need to download the install files required for
the Windows NT operating systems running on the client computer.
Windows NT 4 (nt4prep.exe)
Windows 2000/XP/2003 (deploy.cab)

You can install these files from the Microsoft Resource Kit Microsoft Resource
Kit CDs for each Operating system.
Click Next.

Change Settings
Click the Change Settings button to modify access, security and other settings on the Deployment
Agent to be installed. See Production Agent Settings on page 120.

Get Server Security Key


This page appears only if you enabled the Enable key-based authentication to Deployment Server
option in the Change Agent Settings.

Altiris Deployment Solution Reference Guide

50

Chapter 2: Installing Deployment Server

Installing Deployment Solution Agents

Enter the security key file path for the Deployment Server or browse and select a file containing the
security key file path.

Installing Deployment Agent for Windows


Run AClient.exe from the Deployment Share (shared folder) or download the install file from the
Deployment Web Console.
1

At the Altiris Client Service dialog box, enter a location to install the Deployment agent. Select
one of these options, if required:

Secure modification of server properties.

Enable changing of Security ID. Select when managing security IDs to run a SID utility as part

Advanced. Click to open the Computer Configuration Properties dialog box and enter settings
for the Deployment agent you are installing.

settings.

This prohibits users from changing any agent

of an imaging job.

Click Next.
If you chose to enable security IDs, you will see a screen listing options you can use for managing
SIDs. Select the utilities that you want to use and enter the path where the utilities are stored.

Click Next to install the Deployment Agent. Select a group in Deployment Console to add the
client to. This is optional.You can also leave it at the default group.

After the Deployment agent is installed, it will connect to Deployment Server automatically and
appear in the Computers pane of the Deployment console.
See also Installing Deployment Solution Agents on page 47.

Automating the Installation of Deployment Agent


If you choose not to use Remote Agent Installer to install Deployment Agent, perform the
installation using log-on scripts or batch flies. However, this requires that you manually complete
the installation at each client computer. Instead, you can use a template file to set applicable options
and properties.
The template file is a text file that can be used to automate configuration of the properties when
installing Deployment Agent from a batch file, login script, or manually from a client computer. The
template file can be created using two methods: editing the sample.inp file or using Remote Agent
Installer.

Editing the Sample.inp file


Deployment Solution ships with a sample template file named sample.inp, which contains the
commands to configure installation options and properties. This file is located in Program
Files\Altiris\eXpress\Deployment Server.
Most of the parameters have been disabled in this file. To enable an option, remove the semicolon.
Example: to specify a specific IP address and port number for the client to use to locate the
Deployment Server, remove the semicolon from the TcpAddr and TcpPort lines and then change the
address and port number to the correct values.

Creating a Template File using Remote Agent Installer


A template file can be created when running Remote Agent Installer. After modifying agent
properties and adding computers to the Selecting Clients window, use the Export button to create the
template file. Clicking the Export button creates a file to import computers (*.rci) as well as the
template file (*.inp).
Example: if you had computers named PC-1 and PC-2 listed in the Selecting Clients window and then
exported these computers using the file name Export.rci, these two template files would be created:

Altiris Deployment Solution Reference Guide

51

Chapter 2: Installing Deployment Server

Installing Deployment Solution Agents

Export_PC-1.inp
Export_PC-2.inp

Using the Template File


To use the template file you created, run the AClient.exe installation program specifying the
template file and using the -install switch. Example:
\\FX1\eXpress\AClient.exe aclient.inp -install
The following command-line switches are available:
Switch

Definition

-install

AClient.exe runs and installs the Deployment Agent on the computer as


opposed to just running it in memory.

-remove

Permanently removes Deployment Agent from the computer where it was


installed.

-silent

Lets you use the switches without being prompted for further input.

-stop

Stops the Deployment Agent from running, but does not remove it. The next
time the computer is booted, the Deployment Agent will run in production
mode.

-start

Starts the Deployment Agent. This switch will only work when Deployment
Agent is installed on the computer.

Installing Deployment Agent on Linux


You can install the Deployment Agent to any supported Linux workstation or server by downloading
and running the Deployment Agent for Linux installation file (a bin file) on the client computer. The
Deployment Agent is updated automatically on Linux computers when upgrading to a new version
of Deployment Solution. The creation date of the Deployment Agent is checked and updated when
a new agent is available.
System Requirements

Processors

Pentium

Disk space

5 MB contiguous

Operating systems: RedHat 7.2, 7.3, 8.0, 8.1


RedHat Advanced Server 2.1
United Linux 1.0
RAM

32 MB

Installing the Deployment Agent for Linux


1

After downloading the BIN file to a local directory, you can install from the command-line.

To install from the command line, drive to the directory where you saved the BIN file, switch
to the root user (su) and change the directory to the location of the bin file by typing
(cd < directory>)

after changing the directory, you need to have the permission to execute the bin file, to obtain
the permission, type
chmod 544 <filename>

and then type: ./<file name>

The Deployment Agent for Linux will be installed in the /opt/altiris/deployment/


adlagent directory.

Altiris Deployment Solution Reference Guide

52

Chapter 2: Installing Deployment Server

Installing Deployment Solution Agents

After installing the Deployment Console, you can change settings in the configuration file by
making direct edit changes to the adlagent.conf file, or running a script from the /opt/
altiris/deployment/adlagent/conf directory where the adlagent.conf file is
located.

To run the script to change settings for the adlagent configuration file, drive to the /opt/
altiris/deployment/adlagent/conf directory from the shell and type the following:
./configure

You will then be prompted to select Multicast options to identify a Deployment Server to
manage the current client computer, or you can select a specific Deployment Server by
setting the Multicast option to false and adding the IP address of the desired Deployment
Server.

To edit the configure file directly, open the adlagent.conf file located in the
/opt/altiris/deployment/adlagent/conf

directory and make setting changes to the configuration document.

In many cases, you may want to edit the configuration file to change functionality or
properties. Example: you can open the adlagent.conf file in an editor and scroll to the
[Transport] section and the UseMcast line. Change UseMcast=true to
UseMcast=false. Then type the IP address of the specific Deployment Server you want to
manage the client computer into the TCPAddr=<IP address> line. Additional
configuration settings can also be identified and edited in the configuration file.
3

After making edits to the configuration file, restart the Deployment Agent for Linux.
To start and stop the Deployment Agent for Linux, you must enter the full path name or drive to
the /etc/rc.d/init.d directory (with administrator/root rights) and use the
adlagent stop and adlagent start commands, or the adlagent restart command.
You can also use the Package Manager installed with Linux to restart the Deployment Agent for
Linux.
By stopping and starting the Deployment Agent for Linux, the service will update the changes
made in the adlagent configuration file.

You can now view the Linux managed computer from a Deployment console.
See Installing Deployment Solution Agents on page 47.

Installing the Automation Agent


After Deployment Server has detected a managed computer through the Deployment Agent in a
production environment, you can install an Automation Partition from the Computers pane. You can
use this feature on Windows 2003/XP/2000/NT.
Note: For Windows NT, embedded automation partitions will not boot if the partition starts at a size

larger than 2 GB. In most cases you will not want to use a hidden automation partition with Windows
NT. PXE Servers or the embedded automation partition is preferable for Windows NT.

System Requirements

Processors

Pentium

Disk space

5 MB contiguous

Operating systems: MS DOS and Linux


RAM

32 MB

Here are some other ways to create and install an Automation Agent, which resides in an embedded
(recommended) or hidden partition on the client computers hard disk.

For Windows 95, 98, or ME computers, create boot disks to install locally.

For Deployment Solution systems running PXE Server, create boot menu options from the PXE
Configuration Utility, using on of the following methods: Boot Disk Creator, Direct from floppy, or
User Specified. See PXE Configuration Utility Help.

Altiris Deployment Solution Reference Guide

53

Chapter 2: Installing Deployment Server

Installing Deployment Solution Agents

To install an Automation Partition on Windows 2003/XP/2000/NT computers, you can create a


Microsoft Install Package (MSI) and deploy it using a job from the console. See Distributing
Software (page 172) . You can also create floppy disks, a bootable CDs with an ISO image, or
bootable USB devices. See Boot Disk Creator Help

To install an Automation Partition


See Installing Automation Partitions (page 142) .

Installing Deployment Agent for PocketPC


The Deployment Agent for Pocket PC lets you manage and deploy handheld computers running the
Pocket PC operating system, including:

HP iPAQ Pocket PC

HP Jornada Pocket PC

Casio Cassiopeia Pocket PC

You can manage handhelds through a cradle attached to a host computer, or through direct
connection to the network using a LAN or wireless network adapter. When connected through the
cradle, the Pocket PC Agent software will reside on the host computer and the Pocket PC Client
software will reside on the handheld computer. This configuration allows Deployment Server to
recognize and update the handheld each time it returns to the cradle and synchronize with the host
computer using Microsoft ActiveSync. Handheld computers connected directly to the network
install only the PPC Client software and are managed like any other computer in your Deployment
Server system.
System Requirements

Processors

ARM
MIP
SH3

Disk space

5 Mb contiguous

Operating systems: Pocket PC


RAM

16 Mb

Install from a cradle or cable. See Install a Pocket PC Agent from the Deployment Console on

page 55 to install to a handheld computer in the cradle attached to a host computer.

Download CAB files with ActiveSync. See Install Pocket PC Agent from the Host Computer on

page 56 to install the handheld by running or copying the Deployment agent install file or the
Deployment Client CAB files over the network.

Install directly to the handheld. See Install Pocket PC Client on the Handheld on page 56 to
install only the Deployment Client from CAB files on the handheld computer.

Altiris Deployment Solution Reference Guide

54

Chapter 2: Installing Deployment Server

Installing Deployment Solution Agents

The Deployment Agent for Pocket PC (PA) runs on the host computer, which itself is a managed
computer running the Deployment Agent (DS). The Deployment Agent for Pocket PC automatically
installs the Deployment Client for Pocket PC (PC). You can also install the Deployment Client for
Pocket PC directly to the handheld by installing the required CAB files.

Install a Pocket PC Agent from the Deployment Console


When installing a handheld running the Pocket PC operating system, you can attach to a host
computer and run Microsoft ActiveSync software to synchronize data between the host computer
and the handheld. Deployment Solution lets you install Deployment Agents on both the host
computer and the handheld to communicate with Deployment Server as a managed computer.
The Altiris Pocket PC Agent is software that runs on the host computer. This agent communicates
through the handhelds cradle to the Pocket PC Client running on the handheld. The Pocket PC Agent
also automatically installs Pocket PC Client on the handheld. The Pocket PC Agent provides
communication between the Pocket PC Client on the handheld and the Deployment Server.
ActiveSync is required for the Pocket PC Agent because it provides the IP stack the Pocket PC Agent
uses to communicate with the handheld.
The Pocket PC Agent monitors the connect and disconnect jobs sent to the handheld. If the Pocket
PC Client on the handheld is present but not started, then the agent will start it. The Pocket PC Agent
also acts as a relay agent to transfer data from the Pocket PC Client on the handheld to the
Deployment Server.
From a Deployment console, you can schedule and run a Sample job to install the Pocket PC Agent
on a host computer. Make sure that the handheld is connected to the host computer and seated in the
cradle. You must also download Microsoft ActiveSync and install it (this is free software
available on the Microsoft web site) on the host computer. Then synchronize the host computer with
the handheld.
To install from a Deployment console
Use Deployment Solution to find computers with ActiveSync and run deployment jobs to
automatically copy the necessary files and install the Deployment PPC Agent and PPC Client.
1

From a Deployment console, in the Jobs pane open the Samples > Pocket PC folder.

Click the Install Altiris Pocket PC job and then select the Active Sync computer condition in the
Condition box in the Details pane.

Drag the Install Altiris Pocket PC job to the host computer. If you are using a Web console, then
assign using web features.

Schedule the job.


After the Pocket PC Agent has installed, the Altiris Pocket PC Agent icon will appear in the
system tray of the host computer.
When the Deployment Agent is initialized, it will connect to the handheld. The agent will check
if the Altiris Pocket PC Client is installed on the handheld. If not, the agent will automatically
install it.
When the Pocket PC Client is installed on the handheld, the Deployment Client icon will appear
in the system tray of the handheld and the client details screen will display.
Note: For ease of use, the Pocket PC Client will first try to connect to a Pocket PC Agent. If it

fails, the Pocket PC Client will try to connect directly to the Deployment Server.

Click OK.
The handheld will appear in the Deployment Console as a unique computer displaying the
handhelds name.

See Installing Deployment Agent for PocketPC on page 54.

Altiris Deployment Solution Reference Guide

55

Chapter 2: Installing Deployment Server

Installing Deployment Solution Agents

Install Pocket PC Agent from the Host Computer


From the host computer, you can install the Pocket PC Agent by running the ppcagent.exe
installation file on the host computer. After installing the Pocket PC Agent, it will automatically
install the Pocket PC Client when the computers synchronize. This is the fastest and easiest way to
install both agents on the host and handheld computers.
Note: After you have installed the Altiris Pocket PC Agent on a host computer, the PPCAgent.exe

file can be executed from the C:\Altiris\PPCAgent directory (or the directory where you installed
Pocket PC Agent if you chose a directory different from the default). This lets you access the features
of this program even though the icon has been hidden.
In addition, if you are using ActiveSync 3.5 or a later version, you can also log on to the Deployment
Share in the Deployment Server > Pocket PC Client folder and copy the correct CAB file
for the handheld (based on type of processor) to the host computer. You can then copy the CAB files
directly to the handheld using the Explore feature in ActiveSync.

To install Pocket PC Client directly with ActiveSync


1

Copy the CAB file to the host computer with ActiveSync (or to a share where you can copy the
file from).

Connect your device to your desktop computer using a cradle or cable.

In ActiveSync, click Explore. Windows Explorer will open the Mobile Device window for your
device.

In Windows Explorer, browse to the CAB file that you want to copy.

Right-click the file and click Copy.

Place the cursor in the desired folder for your device, right-click, and click Paste.

From the device, tap Start > Programs > File Explorer.

Browse for the CAB file and tap the file to execute it. When the Pocket PC Client is installed on the
handheld, the Deployment Agent icon appears in the handhelds system tray.
Note: If using ActiveSync 3.5, the Pocket PC Agent is not required after the Pocket PC Client is

installed. However, the Pocket PC Agent can still be useful for installing the Pocket PC Client onto
the handheld, loading the client, and managing client settings.
See Installing Deployment Agent for PocketPC on page 54.

Install Pocket PC Client on the Handheld


You can install the Pocket PC Client directly to the handheld computer if your handheld has a
network adapter (LAN or wireless), allowing you to download the correct CAB file and install the
Pocket PC Client to communicate with the Deployment Server.
The following CAB files are provided based on processor type. Copy the CAB files from the
Deployment Share in the Deployment Server\PocketPCClient folder: ppccInt.Arm.CAB,
ppccInt.MIP.CAB, ppccInt.SH3.CAB.
To install Pocket PC Client using CAB files
1

Copy the CAB file to the host computer with ActiveSync (or to a share where you can copy the
file from).

Connect your device to your desktop computer.

In ActiveSync, click Explore. Windows Explorer will open the Mobile Device window for your
device.

In Windows Explorer, browse to the CAB file that you want to copy.

Right-click the file and click Copy.

Place the cursor in the desired folder for your device, right-click, and click Paste.

From the device, tap Start > Programs > File Explorer.

Altiris Deployment Solution Reference Guide

56

Chapter 2: Installing Deployment Server

Managing Licenses

Browse for the CAB file and tap the file to execute it. When the Pocket PC Client is installed on the
handheld, the Deployment Agent icon appears in the handhelds system tray.
See Installing Deployment Agent for PocketPC on page 54.

Uninstall the Pocket PC Agent


1

Open the Pocket PC Agent status sheet by double-clicking Altiris Pocket PC Agent icon.

Click Options > Uninstall.

You can also uninstall the agent by running the ppcagent -remove switch from the command line.
Note: There is no uninstall program for the PPC Client. To remove the Pocket PC Client, you must
remove the client file from the My Device\Windows\ppccInt.exe file on the handheld.

Command Line Switches for the Pocket PC Agent


You can also manage the Pocket PC Agent through command-line switches. The Pocket PC Agent
is started using the C:\Program Files\Altiris\PPCAgent\PPCAgent.exe program file. If you need to
perform some function with a command-line switch, run the program file followed by the applicable
switch.
To restart the agent, you would run:
C:\Program Files\Altiris\PPCAgent\PPCAgent.exe -restart
The following is a list of the supported switches:

-stop

Stops the agent.

-start

Starts the agent after it has been stopped.

-restart

Stops and restarts the agent.

-silent

Installs the agent without the installation dialog screens.

-remove

Stops and uninstalls the agent.

Managing Licenses
From the Deployment Console you can find the number of licenses used, detect an expired license,
or apply a license to a client computer. You can install multiple Deployment Servers, but licensing
is based on the number of managed client computers.
The Deployment Server system also provides the license utility to install or update regular licenses,
or add licenses to computers installed with Deployment Solution. This utility lets you display license
status, install a newer license, and add additional licenses.

Altiris Deployment Solution Reference Guide

57

Chapter 2: Installing Deployment Server

Managing Licenses

Licensing Terms
Term

Description

AUP - Annual Upgrade


Protection

Altiris Annual Upgrade Protection or AUP allows registered


Altiris software users to upgrade to any version of the
registered product that is released during the coverage period
without paying an upgrade charge. Regular production licenses
will never have a license expiration date, but will always have
an AUP date. As long as this date is not expired you can use that
license to register any version of Deployment Server.

Licensed Nodes

The total number of client and server computers that a


Deployment Server is licensed for. Each client computer that
has an agent and that communicates actively with the
Deployment Server uses a single license node.
You can view this information on the About Deployment
Console box. This detail is also displayed in the License Details
when you apply a license with the Product Licensing Utility,
and select a license file.

DS and PCT

These are common abbreviations for Deployment Server and


PC Transplant. Both of these products are licensed with the
same licensing model, and very often a single license applies to
both products at once, although some licenses will only apply
to PC Transplant.

Expired License

All regular licenses (that are purchased) never expire.


Evaluation licenses however do have an expiration date. After
the expiry date those trial or evaluation licenses will no longer
function, and will need to be replaced with a regular license.

See also: Using the License Utility (page 58) , Adding a License from the Deployment Console
(page 60) , RDP Licensing (page 60) , Finding the Number of Licenses Used (page 61) , Computers
Not Using a Regular License (page 61) , Detecting an Expired License (page 61) , and Expired
Licenses (page 62) .

Using the License Utility


The Deployment Server system provides a license utility to update or add licenses to installed sites,
which lets you apply the license activation key file (.lic file) after Altiris products are installed. This
utility is installed to the Deployment Share during the Deployment Server installation.
When you open the License Utility, the Altiris Activation Key Wizard displays. On the Select Altiris
Program Files to Activate page, you can select the Replace all existing license Activation Keys with this
new Activation Key checkbox, which will overwrite the current Activation Key with the one you are
installing.

The License Utility lets you display license status, install a specific product, install new or updated
licenses for installed software, and additional licenses for installed software.
To open the Altiris License Utility
Option 1:
Click Start > Programs > Altiris > Deployment Solution > Product
Licensing Utility.

Option 2:
Browse to the location where you installed the Deployment Share.

Run license.exe.

Altiris Deployment Solution Reference Guide

58

Chapter 2: Installing Deployment Server

Managing Licenses

To display license status


1

Open the License Utility.

Enter the directory path to the new lic file.

Click Next.
A summary screen displays the activation key information.

Click Cancel.

Install a Regular License for Altiris Products


When a product is installed from the Altiris CD or the Altiris web site, a 7-day trial license is
automatically applied. However, you can apply a 30-day evaluation license or a purchased regular
license to installed products that use a license activation key file (LIC).
Important: Save the license activation key file as you will need it when future product updates are

released. After you receive the key, store it in a safe place (such as a floppy disk) for future reference.
Multiple license activation key files can be stored in individual folders on a single disk. You can also
store multiple license activation key files in the same folder, as long as the file names are different.

To apply a regular license file


1

Open the License Utility.

Enter the directory path to the new lic file and click Next.
The Altiris Activation Key Wizard displays activation key information.

Click Next.
A list displays the Altiris products that are installed on the Deployment Server. Each program
file uses license activation key files.

Select one of the following:


Option 1:
a

Select the product you want to license. Use the Shift key to select multiple products.

Click Finish to apply the license to the selected products.

Option 2:
a

Click Add to browse to the location of an Altiris product folder.

Select the program filename and click Open. The product will be added to the license list.

Select the products to license and click Finish.

Option 3:
a

Select the products you do not want to apply a license to.

Click Remove.

Select the products to license and click Finish.

See Installing Deployment Solution Agents on page 47.

HP client computers and licensing


HP client computers automatically connect to the Deployment Server with a 30 trial license. In the
Deployment Console, HP client computers display a clock icon to indicate that the trial license is
limited, and has an expiration date. You can upgrade the trial license by doing the following:
1

From the Deployment Console, right-click on the HP client computer and select Properties.

Click the Apply regular license checkbox.

Click OK. The license is automatically upgraded to a purchased license.

Altiris Deployment Solution Reference Guide

59

Chapter 2: Installing Deployment Server

Managing Licenses

Note: You do not need to apply a license key to activate the HP Thin Client t5000 Series. This
managed client computer automatically receives a non-expiring license when connected to the
console.

Install Multiple Licenses


Some Altiris utilities can combine multiple licenses together for the total number of nodes. Example:
two 50-node licenses can be combined to a single 100-node license. This option lets you apply an
add-on license to the Altiris products you have installed on the Deployment Server.
1

Open the License Utility.

Enter the directory path to the new lic file and click Next.
The Altiris Activation Key Wizard displays activation key information.

Click Next.
A list displays the Altiris products that you have licensed.

Click Finish.

See also: Managing Licenses (page 57) , Adding a License from the Deployment Console (page 60)

, RDP Licensing (page 60) , Finding the Number of Licenses Used (page 61) , Computers Not Using
a Regular License (page 61) , Detecting an Expired License (page 61) , and Expired Licenses (page
62) .

Adding a License from the Deployment Console


Use this option to install a license to a computer from the Deployment Console after the free trial
has expired. You must apply a regular (permanent) license to continue managing client computers.
You cannot install a license directly to a client ccomputer. However, you must install a regular
license on the Deployment Server before you can install and manage licenses for client computers
from the Deployment Console.
To install a regular license to a single computer
1

From the Deployment Console, right-click on the computer that you want to apply the license.

Select Properties.

Select Apply regular license.

Click OK.

To install a regular license to multiple computers


1

From the Deployment Console, right-click on the computer group that you want to apply the
license.

Select Advanced.

Select Apply Regular License.

See also: Managing Licenses (page 57) , Using the License Utility (page 58) , RDP Licensing (page

60) , Finding the Number of Licenses Used (page 61) , Computers Not Using a Regular License
(page 61) , Detecting an Expired License (page 61) , and Expired Licenses (page 62) .

RDP Licensing
RDP (Rapid Deployment Pack) is a version of Deployment Server released to HP customers. It
functions and behaves almost in a similar manner in regards to licensing. The only major difference
is that due to HP policy, AUP for their customers is much longer than normal. Deployment Server
will not apply licenses correctly if they have AUP longer than 3 years. Because of this, if you have
licenses for RDP, and you download Deployment Server from the Altiris.com website, you will not
be able to apply the licenses.

Altiris Deployment Solution Reference Guide

60

Chapter 2: Installing Deployment Server

Managing Licenses

The easiest way to resolve this issue is to use the install files from the HP site. Those installation
files will use a slightly different version of the Product Licensing Utility, and they will allow licenses
with long AUP dates.
See also: Managing Licenses (page 57) , Using the License Utility (page 58) , Adding a License

from the Deployment Console (page 60) , Finding the Number of Licenses Used (page 61) ,
Computers Not Using a Regular License (page 61) , Detecting an Expired License (page 61) , and
Expired Licenses (page 62) .

Finding the Number of Licenses Used


Open the Deployment console and select Help > About from the main menu bar. You will now be
able to see the total number of licenses that you have purchased, the total licenses that you have used,
and the total licenses available.
You can also tell which computers have not had a regular license applied to them by looking at the
computer in the Computers pane. If the icon has a clock in the lower left-hand corner, this computer
is still using the free license.
See also: Managing Licenses (page 57) , Using the License Utility (page 58) , Adding a License

from the Deployment Console (page 60) , RDP Licensing (page 60) , Computers Not Using a
Regular License (page 61) , Detecting an Expired License (page 61) , and Expired Licenses (page
62) .

Computers Not Using a Regular License


From the Deployment Console, you can tell which computers do not have a regular license. If the
icon has a clock in the lower left-hand corner of the Computers pane, then this is an HP computer
that is still using the free 30 license.
See also: Managing Licenses (page 57) , Using the License Utility (page 58) , Adding a License

from the Deployment Console (page 60) , RDP Licensing (page 60) , Finding the Number of
Licenses Used (page 61) , Detecting an Expired License (page 61) , and Expired Licenses (page 62) .

Detecting an Expired License


A computer listed in the Computers pane of the Deployment console will be gray instead of blue if
the license has expired. However, this may not always mean the license has expired so check the
other options listed below.
1

A computer with an expired license will state Client license expired - see computer properties when
selected.

If you try to display the properties of a computer with an expired license, the following error
message displays:
Error: You have chosen a computer that has expired. Clients that are expired cannot be managed

until a license is purchased for them and they have been flagged in the Computer Properties
dialog box to accept a regular license.

Note: If you place a job on a computer with an expired license, the same error message is
displayed.

Directing client computers to the correct Deployment Server


If you review the client computer list from the Deployment Console, and notice some computers are
not available when you click on them, it could be that the computer was moved from one
Deployment Server to the other, and the former server had an expired licence. To verify that a client
computer is associated with the Deployment Server you want, do the following:
1

Double-click on the Deployment Agent icon at the client computer.

Select Properties.

Altiris Deployment Solution Reference Guide

61

Chapter 2: Installing Deployment Server

DS Installation Help

Enter the IP address of the correct Deployment Server in the Address/Hostname field.

Click OK.

See also: Managing Licenses (page 57) , Using the License Utility (page 58) , Adding a License

from the Deployment Console (page 60) , RDP Licensing (page 60) , Finding the Number of
Licenses Used (page 61) , Computers Not Using a Regular License (page 61) , and Expired Licenses
(page 62) .

Expired Licenses
Regular Deployment Server licenses do not expire, however the 7 day trial license, or the 30 day
evaluation licenses do expire, and can cause some problems if not replaced properly after adding
regular licenses. Computers with expired licenses become dead nodes and can no longer be managed
by the DS console.
When a license is first installed on the Deployment Server, each computer in the database takes a
license node. If this node is a temporary license, then that computer has a tag in the database that
says it is a trial node. If that license is not replaced before the time limit then that computer will stop
accepting jobs or any type of remote management.
When the Deployment Server receives new regular licenses, it does not by default release the trial
license nodes that it was using before. This can cause problems if the trial licenses are still being
used and they expire even after you apply a regular license. There are 2 ways to deal with this
lingering expired license issue.
First you can set up a global option that will automatically replace any trial license with a regular
license as soon as they become available. This is a long term and preventative solution to expired
license issues.
1

In the Deployment Console, go to Tools > Options

Click Global tab.

Select the Automatically replace expired trial licenses with available regular licenses box. This
solves the computer node licenses expiry issue.

The second way you can deal with expired licenses is reapply all of the regular licenses to the
computer nodes. This is good if you want to see an immediate resolution to a license issue.
1

In the Deployment Console, right-clicking on the All Computers computer group (or any other
computer group you need to do this to).

Select Advanced > Apply Regular License. This will make all computer nodes in that group release
whatever license node they were using, and then take a regular license node.

See also: Managing Licenses (page 57) , Using the License Utility (page 58) , Adding a License

from the Deployment Console (page 60) , RDP Licensing (page 60) , Finding the Number of
Licenses Used (page 61) , Computers Not Using a Regular License (page 61) , and Detecting an
Expired License (page 61) .

DS Installation Help
The following are help file topics for the Deployment Server installation program accessed by
clicking the Help button or pressing the <F1> key. These topics identify and explain the screen
elements on the dialog boxes used in the installation process.

Install Configuration
The Deployment Server system supports both a Simple Install and a Custom Install option. A Simple
installation lets you install all components on a single computer. The Custom installation lets you
distribute individual components of a Deployment Server system on multiple computers. Use the
Component Install option to install additional components on your system.
Pre-Installation

Altiris Deployment Solution Reference Guide

62

Chapter 2: Installing Deployment Server

DS Installation Help

Simple Install Helper. Click this option to check for an installation of Microsoft SQL Server for a
Simple install. If Microsoft SQL Server or MSDE is located, then the installation program will
continue. If not, then the installation program will prompt you to automatically install MSDE 2000
from an Altiris download web site.

Installation Type
Simple Install. Click this option to install all Deployment Server components on a single computer.
This configuration is recommended for managing computers on a single LAN or across a site with
few subnets. See Simple Install for Deployment Server on page 42.
Include PXE Server. Select this feature to install the Altiris PXE Server when running the Simple

install option. The PXE Server requires a DHCP server also installed on your network.

Custom Install.

Click this option to install Deployment Server components on multiple computers


across your system. A Custom install lets you balance network activity for large enterprises with
multiple subnets. Example: use this option to distribute the Deployment Database on a separate
computer or assign another file server as the Deployment Share to store image and package files. See
Custom Install for Deployment Server on page 44.

Component Install.

Click this option to install additional Deployment Server components to your


system. Example: use this option if you want to add a PXE Server to your Simple or Custom
installation, or if you need multiple Deployment consoles. See Component Install for Deployment
Server on page 46.
If you have multiple network adapter cards, then a secondary dialog box appears stating to select the
IP address for the Deployment Server interface.
See also Deployment Server System Requirements on page 41.
Important: If you are running Deployment Server on a MS Windows Server 2003 Domain

Controller with SMB Signing enabled then you cannot execute any imaging and DOS jobs. When
running jobs on MS Windows Server 2003, you must change the SMB Signing Registry Key to
execute DOS-based deployment jobs.
To disable SMB signing on the Windows 2003 Server
1

Open the Default Domain Controller Security settings dialog box by clicking Start > Settings >

Locate the Microsoft network server: Digitally sign communications (always) policy setting, rightclick it and select Properties, and then select Disabled.

Disable the Microsoft network server: Digitally sign communications (if client agrees) policy setting
as well. This is Enabled by default.

Control Panel > Administrative Tools > Domain Controller Security Policy >Local Policies >Security
Options.

Installing Deployment Server


Specify the Deployment Share (shared directory) where the image files, RIPs, and other package
files will be stored. Make sure that you have a shared Windows or NetWare directory with free disk
space and appropriate security rights before installing.
File server path. Select the drive letter and directory path where Deployment Server will be installed.
The default path is the Program Files directory on the local computer.
Create Deployment Share. If
Share check box to create a

installing to a local Windows computer, select the Create Deployment


shared directory as your Deployment Share. If you are installing to a
remote file server or if you choose an invalid path, then this option is unavailable.
Note: If installing to a remote file server, create a share or grant access rights to the Deployment

Server directory on the file server before you start the installation. For Windows XP, you must
run the Network Setup Wizard accessed from My Network Places to enable sharing.

Free 7 day license.

Click to use an evaluation license for a new Deployment Server installation.

Altiris Deployment Solution Reference Guide

63

Chapter 2: Installing Deployment Server

DS Installation Help

Upgrade using existing license. Upgrade the Deployment Solution install by using an existing license

file.

License file. Type the path or browse to the license (.lic) file received when you registered on the
Altiris web site.
Service user name and Service password. If running a Simple Install, type the user name and password
of the Deployment Server service and the Deployment Share. For domain accounts include the
domain name, for example: orgDomain\admin. Make sure you create the administrator domain
account before starting the installation.

Note: During a Custom Install, the Service user name and Service password boxes are not displayed

on this screen.

See also Deployment Server Components (page 37) , and Managing Licenses (page 57) .

Installing Deployment Server using Component


Install
Specify the Deployment Share (shared directory) where image files, RIPs, and other package files
are stored. Make sure that you have a shared Windows or NetWare directory with available disk
space and security rights before installing.

Deployment Server Install


Install the Deployment Server on a computer. The service is identified in the Services section of the
Windows Computer Management as Altiris eXpress Server.
To install service on a local computer
1

Click On this computer.

Type the Deployment Server IP address and port information.

Enter the path to install the Deployment Server.

Type the user name and password of the Deployment Server. For a domain account, type the
domain and user name. Create this account before starting the installation.

To install service on a remote computer


1

Click On a remote computer.

Type the name of the computer or browse to where you want to install. The destination path and
IP address of the computer will appear automatically.

Type the user name and password of an administrator account for the Deployment Server
computer. For domain accounts include the domain name, for example: orgDomain\admin.
The user account must have rights to the Deployment Share. Create the administrator domain
account before starting the installation.

See also Deployment Server Components on page 37.

Pre-boot Operating System (Simple)


Select a default pre-boot operating system, which Deployment Server will use as the default when
creating a deployment job with an automation task. However, you can install additional pre-boot
operating system files through Boot Disk Creator later.
If you are running a PXE Server in your system environment, the first pre-boot operating system you
install becomes the default boot menu option for Initial Deployment. The menu options will display
DOS Managed, Linux Managed, or Windows Managed.

Altiris Deployment Solution Reference Guide

64

Chapter 2: Installing Deployment Server

DS Installation Help

You can assign an automation pre-boot operating system to an automation task when it is added to
a deployment job. This flexibility lets you run several automation tasks within a single job, and each
task can boot to the automation environment you want.

None. Select this option if you do not want to provide a default automation operating system. You
can also select this later through the Boot Disk Creator utility.

FreeDOS. Browse to the BDCgpl.frm file, which is located in the GPL folder on the Deployment

MS-DOS. DOS requires an original Microsoft Windows 95 or 98 installation disk, or browse to


the system formatted files.

Linux. Browse to the BDCgpl.frm file, which is located in the GPL folder on the Deployment
Server. The exact location of the folder will vary, depending on the installation path. This .frm
file is open source code and is not owned by Altiris. However, this file is available to all
customers by downloading the file from the Altiris Solutions Center.

Windows PE. Browse to the Windows PE files and the Microsoft Windows operating system path.

Server. The exact location of the folder will vary, depending on the installation path. This .frm
file is open source code and is not owned by Altiris. However, this file is available to all
customers by downloading the file from the Altiris Solutions Center.

Altiris supports Microsoft Windows PE 2005.

See Boot Disk Creator Help, and PXE Configuration Help.

Pre-boot Operating System (Custom)


Select a default pre-boot operating system, which Deployment Server will use as the default when
creating a deployment job with an automation task. However, you can install additional pre-boot
operating system files through Boot Disk Creator later.
If you are running a PXE Server in your system environment, the first pre-boot operating system you
install becomes the default boot menu option for Initial Deployment. The menu options will display
DOS Managed, Linux Managed, or Windows Managed.
You can assign an automation pre-boot operating system to an automation task when it is added to
a deployment job. This flexibility lets you run several automation tasks within a single job, and each
task can boot to the automation environment you want.

FreeDOS. Browse to the BDCgpl.frm file, which is located in the GPL folder on the Deployment

MS-DOS. DOS requires an original Microsoft Windows 95 or 98 installation disk, or browse to


the system formatted files.

Linux. Browse to the BDCgpl.frm file, which is located in the GPL folder on the Deployment
Server. The exact location of the folder will vary, depending on the installation path. This .frm
file is open source code and is not owned by Altiris. However, this file is available to all
customers by downloading the file from the Altiris Solutions Center.

Windows PE. Browse to the Windows PE files and the Microsoft Windows operating system path.

Server. The exact location of the folder will vary, depending on the installation path. This .frm
file is open source code and is not owned by Altiris. However, this file is available to all
customers by downloading the file from the Altiris Solutions Center.

Altiris supports Microsoft Windows PE 2005, and Microsoft Windows 2003 SP1.

See Boot Disk Creator Help, and PXE Configuration Help.

Deployment Database Install


Install the Deployment Database on a local or remote server with or without an existing Microsoft
Data Engine (MSDE) or Microsoft SQL Server. To install the database you must have
administration rights to the selected server.
Note: In Deployment Solution 6.0 and later, if you have multiple instances of the Microsoft SQL
Server already set up, you can identify a specific instance using this format: <SQL Server
Name>\<database instance>. The instance of the database can vary. Example: if you have a

Altiris Deployment Solution Reference Guide

65

Chapter 2: Installing Deployment Server

DS Installation Help

clustered Microsoft SQL Server to manage multiple Deployment Solution systems on different
network segments, you can enter the name salesSegment\express or
marketingSegment\express depending on the previously established database instance.
Install the Deployment Database using these options:

Select the Microsoft SQL Server instance where you want to install your Deployment database.

You can also choose to change the default SQL Port number.

To name the Deployment Database differently from the default name eXpress, you can type a
different name in the Database Name: box. However, this does not alter the Deployment Share
name.

See also Deployment Server Components on page 37.

PXE Server Install


Select options to boot locally using the Altiris Automation Partition or across the network using the
Altiris PXE Server using the Intel Pre-boot eXecution Environment (for PXE-compliant computers
only).
Note: If you have a Novell NetWare file server, you must set up the Altiris PXE Server after

installing Deployment Server. The Universal Network Device Interface (UNDI) default driver is not
supported by Novell NetWare.

Click No I will be using an Altiris automation partition on each client computer, if you do not use
PXE and prefer using embedded (preferred) or hidden partitions, or bootable media to run tasks.
Note: This option is unavailable for installing PXE Servers using Add Components.

Click Yes, I want to install PXE Server on this computer to install on the local computer.
Note: This option is selected by default for the Add Components install.

Click Yes, I want to install PXE Server on a remote computer to install the Altiris PXE Server on a
remote computer. Type the name of the computer and the path.

Type the IP address for the PXE Server and the Deployment Server.

Type the path on the computer to install the PXE Server.

Select the pre-boot operating system that will be used as the default PXE boot menu item. The
pre-boot operating system options that are enabled depends on the options selected for pre-boot
operating system in the Pre-boot Operating Systems page. For example, if you select Linux in the
Pre-boot Operating Systems page, then the Linux option will be enabled as the default PXE boot
menu item.

See also Installing the Automation Agent (page 53) , Pre-boot Operating System (Simple) (page 64)
, and PXE Configuration Utility Help.

Client Connection to Server


Select the protocol that your managed computers will use to connect to the Deployment Server.
Installs the Altiris PXE Server using the Intel Pre-boot
eXecution Environment (for PXE-compliant computers only). You can use this without PXE for
faster access, as it goes directly to the IP address without searching.

Connect directly to Deployment Server.

If managed computers are on a different segment or if you are using the Altiris PXE Server with an
UNDI driver, click Connect directly to Deployment Server and enter the IP address of the Deployment
Server that the managed computers will connect to. Do not change the port number unless the default
is already being used.
Note: If you change the port number, you will have to change the client configurations.

Altiris Deployment Solution Reference Guide

66

Chapter 2: Installing Deployment Server

DS Installation Help

Allows managed computers to connect to any


Deployment Server. To use multicasting and connect to a specific Deployment Server, enter the
name of the Deployment Server computer.

Discover Deployment Server using TCP/IP multicast.

Multicasting cannot be used with the UNDI driver. If you want to use different drivers on the PXE
Server, you can create multiple PXE boot files after installing.
See also Deployment Agents on page 118.

Deployment Web Console Information


This feature lets you remotely manage Deployment installations, deploy and manage Windows and
Linux computers (both client and server editions) in real-time, and benefit from many of the same
features available in the Deployment Console.
To Install Deployment Web Console
1

By default, DS Web Console installs to the same computer running the installer. Click On a
remote computer, and then click the Browse button to navigate to a computer where you want the
installation to occur. You can also choose to not install Deployment Web Console by clicking
the Do not install option.

If you want to change the default values, enter a Console port and Deployment Web Console path
for the installation.

The Service user name and Service password must be an existing account on the Deployment
Share and the destination computer where the Web Console will be installed.

Note: If you are installing an additional Deployment Web Console using Add Component, the Do

not Install option will be disabled.

See also Deployment Console on page 38 and Deployment Server Components on page 37.

Sysprep
Enter the location of the Microsoft Sysprep files according to operating system. Type the location or
click Browse and select the required files.

Installing Components
Click Install, or choose Back to change settings.
See also Deployment Server Components on page 37.

Simple and Custom Installation Summary


The components are installed.
You may choose to remotely install Deployment Agents, enable Sysprep support, and download
Adobe Acrobat for documentation.
Enable Microsoft Sysprep Support. Select this option to enable Sysprep support. Provide the location

of the Microsoft Sysprep files.


Remote Install Clients.

Select this option to push the Deployment Agent to computers running the
Windows NT, 2000, XP, and Windows Server 2003 operating systems.

Download Adobe Acrobat Reader.

PDF format.

Select this option to download software to read documentation in

Click Finish. See also Deployment Server Components on page 37.

Altiris Deployment Solution Reference Guide

67

Chapter 2: Installing Deployment Server

DS Installation Help

Add Components Summary


The components displayed in the list are installed.
Download Adobe Acrobat. Select this option if you want to download the Adobe Acrobat Reader to
read documentation in PDF format.

Click Finish. See also Deployment Server Components on page 37.

Deployment Database Authentication


Specify the type of authentication the Deployment Database will use. You can select Windows NT
authentication or SQL Server authentication. If you choose to use SQL authentication, enter the user
credentials with administrative rights for the SQL database.
Use Windows NT authentication.

authentication.

Click to use the Windows network or Active Directory

Use SL Server authentication. Enter the user name and password set for the Microsoft SQL Server. If
using MSDE, then the default sa user name is used with no password required.

See also Deployment Server Components on page 37.

Administrator Credentials
During a component install, you are required to provide the user name and password of an
administrator account for the Deployment Server computer. For domain accounts include the
domain name, example: orgDomain\admin. The user account must have rights to the Deployment
Share. Create the administrator domain account before starting the installation.

Add Components
If you have already installed Deployment Server, you can add components to the existing system.
Select the type of component you want to add.
See also Deployment Server Components on page 37.

Console Install
You can install the Deployment Console on either the local computer or multiple remote computers.
Installing to remote computers lets you manage computers from multiple Deployment Consoles
across the Deployment Server installation.

Click On this computer to install the Deployment Console to the local computer.

Click On a remote computer to install the Deployment Console to a remote computer. Type the
computer name or browse and select a computer.

See also Deployment Server Components on page 37.


Installer Return Codes
For a list of return codes for the installation program, see the Error Messages in Deployment
Solution chapter in the Reference Guide.

Altiris Deployment Solution Reference Guide

68

Chapter 3:

Installing Deployment Solution from the Altiris Console


Deployment Solution provides both web and Windows components that can be installed from the
Altiris Console on Notification Server. Use this guide to install all Deployment Solution
components, including Notification Server, Deployment Servers, Deployment consoles, PXE
Servers, and agent software for each managed client computer.

Deployment Solution can be installed as a stand-alone Deployment Server system for a specific site
or integrated as a component of a larger Notification Server infrastructure. As a plug-in web
solution, Deployment Solution joins with other Altiris IT management solutions such as Inventory,
Helpdesk, Application Metering, and Software Delivery solutions. It is also a mainstay of the Client
Management Suite and Server Management Suite. These complementary solutions and suites
provide remote, automated administration of desktop, notebook, servers, handheld, and network
computer devices.

Altiris Deployment Web Console Help

69

Chapter 3: Installing Deployment Solution from the Altiris Console

Deployment from the Altiris Console

Deployment from the Altiris Console


Deployment from the Altiris Console lets you access and manage multiple Deployment Server
systems from the Altiris Console, providing a comprehensive deployment system managed in the
Notification Server infrastructure.

This guide details the basic tasks required to set up Notification Server and enable the Deployment
Solution in a controlled lab environment. After an initial evacuation, you can then move your Altiris
system into a production setting. For general set up information for Altiris products, see the Altiris
6.0 Getting Started Guide. For in-depth planning concepts and rollout instructions for large or
distributed environments, see the Installation section in the Altiris Notification Server Reference
Guide.

Installing Notification Server and Enabling


Deployment Solution
To install Deployment Solution from the Altiris Console, install Notification Server and then push
down the Deployment Server to a target computer running the Altiris Agent. After installing the
Notification Server agent, you can then push down Deployment Agents for various operating
systems (Windows, Linux, DOS, PPC) from a Deployment console.
After installing the prerequisite software and services on your Windows server, you can download
the Altiris InstallHelper from the Altiris web site or product CD. The InstallHelper program will
verify setup requirements and automatically download missing software and services. InstallHelper
will automatically launch the setup program for Notification Server and allow you to install
Deployment Solution from the Altiris Console.
From the Getting Started page on the Altiris Console, you can run a network discovery to identify
computers on the network and push down the Altiris Agent to a client computer where you want to
install Deployment Server. You can then verify communication between the Notification Server and
the Altiris Agent on the managed server.
Steps for Installing Notification Server and Deployment Solution
1

Ensure that the selected target server has all installation requirements before installing
Notification Server and Deployment Solution. See Step One: Verify Installation Requirements
on page 71.

Download and install prerequisite software and services, and then install Notification Server and
Deployment Solution to a Windows server. See Step Two: Install Server Software on page 73.

Altiris Deployment Web Console Help

70

Chapter 3: Installing Deployment Solution from the Altiris Console

Step One: Verify Installation Requirements

Push down and install the Altiris Agent to each computer device. See Step Three: Deploying
the Altiris Agent on page 80.

Validate communication between Notification Server and the Altiris Agent. See Step Four:
Verify Server-to-Client Communication on page 83.

Install Deployment Servers. See Step Five: Install Deployment Servers on page 83. This will
push a silent install of all required Deployment Server components.

Synchronize the NS and DS databases. See Step Six: Synchronize the NS and DS Databases
on page 85.

What type of installation?


Set up and configuration will vary depending on what you already have installed:

start with Step One:


Verify Installation Requirements on page 71 to identify system requirements, download
required software and services, and run the Notification Server installation wizard. If you are
evaluating Deployment Solution, accept the default settings and install in a test environment with
a server and client computers.

If Notification Server 6.0 is already installed, see Installing Deployment Solution from the Altiris
Console on page 77 to add Deployment Solution from the Solution Center.

If upgrading to Notification Server 6.0 and previous versions of Deployment, see Upgrading from
Previous Versions of NS on page 77 for detailed instructions about optimizing for
Notification Server 6.0. Because Notification Server 6.0 and Deployment Solution 6.1 include
major feature upgrades, in many cases you will need to perform basic update tasks to increase
allotted disk space for the database, and perform additional design optimization tasks.

If installing Altiris Notification Server 6.0 and Deployment for the first time,

Step One: Verify Installation Requirements


Before setting up Deployment, select an appropriate Windows server to install the Notification
Server, Deployment solution, and any additional solutions. The server and clients should comply
with the System Requirements on page 72.
Deployment can be run in either a Workgroup environment or on a Domain. For evaluation
purposes, running in a Workgroup is simplest and the evaluation can be performed with a minimum
of two computers, a server computer (with minimal server requirements) and a client computer. This
lets you perform the basic installation tasks and get a feel for Deployment Solutions capabilities.
As you roll out Deployment Solution to a Domain or to a production Workgroup environment,
depending on the number of managed computers in your environment, you may want to increase
RAM, enlarge disk space for the Notification Database, or upgrade the server.

Altiris Deployment Web Console Help

71

Chapter 3: Installing Deployment Solution from the Altiris Console

Step One: Verify Installation Requirements

Updating to Deployment Solution 6.1 SP1 and Notification Server 6.0


Deployment Solution 6.1 SP1 installs to the Notification Server 6.0 infrastructure with new taskbased user interface features, updated security, localized language support, easy-to-use wizards, and
integrated IT solutions. In fact, the whole Notification Server infrastructure has been updated,
including the Deployment Solution and its complementary suite of IT solutions.
New users will enjoy the ease-of-use and intuitive features for getting up and started. Previous users
updating to the new Altiris Console will see significant updates and a new task-based user interface
with increased response and functionality.

These major updates will require the installation of Microsoft .NET services, updated MDAC
connectivity, increased database requirements, and other design considerations. See Upgrading
from Previous Versions of NS on page 77 for complete information.

System Requirements
The following are system requirements for installing Notification Server and the HP Client Manager
Software on a server and setting up the Altiris Agent on the managed client computers.
Server Requirements

Operating System

Windows Server 2003, and Windows 2000 Server, Windows 2000


Advanced Server with SP2 or later.

Processor

Pentium III 800 MHz or faster

RAM

512 MB
1 GB recommended for increased speed in large environments

Hard Drive

20 GB (recommended)
105 MB for Notification Server and components (disk space)
1 GB for SQL Server database

File system

NTFS partition

Altiris Deployment Web Console Help

72

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Two: Install Server Software

The following are system requirements for the client computer running the Altiris Agent.
Client Requirements

Operating System

Windows 95 or later

Disk space on client

5 MB disk space for Altiris Agent, plus space to install required


software.

RAM

64 MB

Browser

Microsoft Internet Explorer 4 or later

Step Two: Install Server Software


To install Notification Server, start by downloading Deployment Solution install files from the
Altiris web site or CD. The download package for Deployment will include an
NSInstallHelper.exe file that launches a prerequisite wizard to verify that all required programs
and services are present on the server. If additional software is required, InstallHelper will assist in
downloading and installing any missing components. After it verifies that all prerequisite software
is installed, InstallHelper will automatically launch the installation wizard for Notification Server.

Running InstallHelper
From the Altiris web site or a product CD, access the HP Client Manager Software solution to
download the NSInstallHelper.exe to check for the installation of required programs and
services. If missing, the following software and services will be identified by the InstallHelper and
links will be provided to download the required software.
Microsoft SQL Server vs. MSDE
During installation, Altiris Notification Server creates an Altiris database in either a full install of
Microsoft SQL Server 2000 or using Microsoft SQL Server 2000 Desktop Engine (MSDE 2000), a
limited-feature edition of SQL Server. It is recommended that you install the full version of
Microsoft SQL Server for production use, although MSDE can be downloaded and used for
evaluation of the product. For additional information about the limitations of MSDE 2000, see http:/
/www.microsoft.com/sql/msde/default.asp
Prerequisite Software

Database

Microsoft SQL Server 2000 SP3 (recommended) or Microsoft


Desktop Engine 2000 (MSDE).
Important: If you do not have an MS SQL Server database installed,
InstallHelper will assist in installing MSDE 2000 in order to evaluate
DS. You will want to install Microsoft SQL Server to manage over
100 client computers.

Microsoft IIS

Including FTP Server and IIS with Worldwide Web Server

Services

Microsoft .NET 1.1 framework (with ASP .NET), Microsoft Data


Access Control 2.7 (MDAC)

Browser

Microsoft Internet Explorer 6.0 or later

To install, click Next to download the next component in the list.

Altiris Deployment Web Console Help

73

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Two: Install Server Software

Note: You may be required to restart InstallHelper after each software installation. You will then
need to run InstallHelper again to ensure that all prerequisites are installed.

Installing Notification Server with the Install Wizard


If all required software and services are installed, then InstallHelper will automatically download
and run the Notification Server installation wizard.

Altiris Deployment Web Console Help

74

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Two: Install Server Software

Accept licensing terms and follow all prompts provided in the installation wizard to set up
Notification Server. For Setup Type, select the Complete option for evaluation or testing purposes.
For advances users, select Custom for installation across a distributed environment.
1

The User Identity Settings page will appear first. Enter credentials with administrator rights.

Important: If you are operating in a Workgroup, enter the server's computer name followed by
a user name with administrator rights, such as CanyonRim-Server2\administrator. If the server
is part of a domain, enter the Domain name followed by a user name with administrator rights,
as the graphic above illustrates. In both cases, the user name entered must authenticate as a
Windows user with local administrator rights to the NS computer to add, create, and delete files,
and query the Notification Database.
2

The E-mail Settings page lets you set up an e-mail address to send alerts to the administrator
automatically from system events generated from Notification Server.
Entering e-mail settings is optional. Notification Server generates e-mail notifications for events
generated from Notification Server. Example: through the use of Notification Servers Alert
Manager, a limited incident management program, you can automate generating an incident
when the DS system meets a specific criteria. For more advanced features in managing incidents
and assets, you can download and install the Altiris Helpdesk Solution, an ITIL compliant
product. See www.altiris.com/products/helpdesk/ for more details.
Note: The e-mail feature is not essential for standard Deployment features. If you are not going

to use the e-mail notification in Notification Server or if you are only evaluating Deployment,
click Next to skip this step.

Altiris Deployment Web Console Help

75

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Two: Install Server Software

In the E-mail address field, enter an IT e-mail address to receive messages from events generated
within the Notification Server infrastructure. In the SMTP server field, enter the name of the
Simple Mail Transfer Protocol (SMTP) server used for e-mail management for the site or subnet.
The SMTP server distributes e-mail files across the organization and is used to forward e-mail
generated from Notification Server. Enter the authentication credentials if your SMTP server is
protected.
Note: In most cases, your IT department will protect the SMTP server to avoid direct access from

unwanted e-mail. To send event e-mail messages to the provided e-mail address through
protected SMTP gateways, enter valid administrator credentials for the appropriate SMTP
server. In most cases, the authentication credentials would be your domain login name in the
form of domainName/username and the associated password. Click Send Test E-mail to verify
that Notification Server is sending e-mail messages to the correct address. Click the button and
verify that a test e-mail is sent to the e-mail inbox.

The SQL Database Settings page allows you identify and enter authentication credentials for the
Notification Database used by Notification Server to store and access Deployment data.

MSDE 2000 installations: If you are evaluating Deployment using MSDE 2000, just click Next

to accept the default values. This will identify MSDE 2000 as the local instance of SQL Server
and create an Altiris database automatically. For MSDE 2000, Notification Server will use the
application credentials (the Windows credentials) rather than the SQL login credentials, which
are used only when setting up the full installation of SQL Server.

In the Server name field, localhost will appear as a system variable name for the initial instance
of Microsoft SQL Server or MSDE 2000 that was installed as part of the software system
requirements. The actual name of the SQL Server can also be entered here (the initial instances
of SQL Server take the computer name by default).
In the Use existing database field, select the Notification Database previously created within the
selected instance of SQL Server. For new installations, enter a name in the Create new database
field. The default name is Altiris, but this database name can be changed.
Select Use application credentials to authenticate using Windows credentials with administrative
rights. Select Use SQL login to authenticate using Microsoft SQL Server credentials.
To select an appropriate Command Timeout (in seconds), enter a value between 1 second and
3600 seconds (1 hour). The database command timeout setting applies to all SQL Server
connections used by the Notification Server. If you experience timeout errors when using a
database connection due to network traffic or heavy server usage, increase the value of this
setting.
4

The Setup Wizard Completion page summarizes the settings entered in the previous pages. Click
Finish.

Altiris Deployment Web Console Help

76

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Two: Install Server Software

When complete, the Altiris Console will open to the Getting Started page. From this page you can
install Deployment from the Solutions page. If the Getting Started page closes, you can start the
Altiris Console by clicking Start > Programs > Altiris > Altiris Console from the Windows operating
system.

Upgrading from Previous Versions of NS


Deployment Solution 6.1 SP1 installs to Notification Server 6.0, a major update of the Altiris
infrastructure. Upgrading to Notification Server 6.0 lets you further optimize the design of your
system, clean up old files and database data, and expand the database to handle the added features
included with Notification Server 6.0 and Deployment Solution 6.1 SP1.
To upgrade to Notification Server 6.0, you will be required to uninstall previous versions of
Notification Server and any installed Altiris solutions from your Windows operating system,
including previous versions of Deployment Solution. It is also suggested that you back up your
database to retain inventory data, status information, custom reports, collections, and policies in your
Notification Server system. By backing up your Notification Database and later identifying it when
installing Notification Server 6.0, you can ensure that all information is retained during this upgrade
process.
Steps required for Notification Server 6.0 and Deployment Solution 6.1 SP1 upgrade
1

Open Add/Remove Programs from the Control Panel in your Windows operating system.

Remove Altiris Notification Server

Remove Altiris Deployment Solution

Remove any other Altiris solutions that are currently installed

Back up your Notification Database. If you have a version of the Notification Database previous
to the Notification Server 5.5 SP3 database, you will have to upgrade first to that version of
Notification Solution.

Run InstallHelper to identify any missing software required for Notification Solution 6.0. See
Running InstallHelper on page 73.

Install Notification Server 6.0. See Installing Notification Server with the Install Wizard on
page 74.

Enable Deployment Solution 6.1 SP1. See Installing Deployment Solution from the Altiris
Console on page 77.
Altiris Agents and Package Servers will also update automatically. All necessary logic is built
into the Notification Server install packages. You can simply enable the upgrade policies.

Verify the upgrade installation. See Step Four: Verify Server-to-Client Communication on
page 83

Installing Deployment Solution from the Altiris


Console
After installing Notification Server, click the Install Altiris Solutions from the Solution Center link on
the Getting Started tab of the Altiris Console.

Altiris Deployment Web Console Help

77

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Two: Install Server Software

The Solution Center page will open with a list of Available Solutions. Click the appropriate Solutions,
Suites, or Segments button, or sort solutions categorized by operating system (OS).
To install Deployment Solution, select Deployment Solution from the Solutions list. Click the Start
button on this page to begin the download and installation process of all selected Altiris solutions.

During the install process, a black dialog is displayed but does not appear to be doing any function,
or running any process. This dialog is normal and indicates that Deployment Solution is installing
to NS. When Deployment Solution completes its download to NS, the dialog no longer displays. You
must refresh the web browser for the Deployment tab to display in the Altiris Console.

To verify that Deployment is installed, click the Configuration tab on the Altiris Console. In the tree
view, click Upgrade/Install Additional Solutions, and then click the Currently Installed tab on the
Solution Center page. This table displays a list of the solutions installed on Notification Server.

Discovering Computers on the Network


Identify and select all the client computers on the network by entering each domain name or browse
and select from available domains using the Domain Picker. Additionally, you can discover all
computers sharing files and printers or running the messenger service, and computers that have trust
accounts in the domain.

Altiris Deployment Web Console Help

78

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Two: Install Server Software

If you are using DS in a Workgroup, you can skip this step and go directly toDiscovering Client
Computers within a Workgroup on page 79 where you can specify the inclusion of individual
computers by IP address or computer name.
Note: During an evaluation, you can skip this step and deploy the Altiris Agent without completing

a full network discovery operation. However, when deploying the Altiris Agent to several computers
in a large environment, you will want to use this automated process to discover computers on the
network.

Click Discover all computer resources on the Quickstart page. The Resource Discovery page will
open.

Enter the name of the Domain or browse to select available domains by clicking the folder icon
. Click the Add button
to include the domain in the search list.

Select Domain Browse List to discover all computers (including Windows 98 SE computers)
currently sharing files or printers or running the messenger service.

Select Domain Membership to discover all computers that have trust accounts in the domain,
including Windows NT/2000/XP/2003 computers in the domain. It will not find any Windows
98 SE computers. This method is slower than the Domain Browse List method and will not
identify the Operating System of the computer.

Click Discover Now. Computers from the entered domains will be discovered and listed. Select
the computers you want to receive the Altiris Agent and click Apply.

Discovering Client Computers within a Workgroup


You must discover client computers on the network before you deploy the Altiris Agent. If you are
installing Deployment Solution in a Workgroup environment and have not yet discovered client
computers, this process lets you enter the IP address or computer name for each client within the
Workgroup.

To Discovery Workgroup Clients


1

From the Altiris Console, click the Configuration tab.

In the tree view, click Configuration > Altiris Agent > Altiris Agent Rollout > Altiris Agent Installation.

To discover client computers within a Workgroup, enter the IP address or computer name of the
client you want to receive the Altiris Agent, and then click Add. Continue entering the IP address
or computer name for each client within the Workgroup. When have completed all client entries,
go to step 5 on page 80 to continue Step Three: Deploying the Altiris Agent.

Altiris Deployment Web Console Help

79

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Three: Deploying the Altiris Agent

Step Three: Deploying the Altiris Agent


After you discovered all client computers on the network, you can now filter and select client
computers to receive the Altiris Agent. This process lets you automatically install the Altiris Agent
on Windows 2000, 2003, and XP computers. For Windows 98 SE, see To install the Altiris Agent
from a web page on page 82.
Important: If you are running Windows XP on a computer that is not in a domain, you must go to

Windows XP Simple File Sharing on page 82 for information on how to deploy the Altiris Agent
to those types of client computers.
To Deploy the Altiris Agent

From the Altiris Console, click the Configuration tab.

In the tree view, click Configuration > Altiris Agent > Altiris Agent Rollout > Altiris Agent Installation.

On the Altiris Agent Installation


Computers page.

Click the drop-down arrow and select a collection from the list, and then click OK.

page, click the Select Computers button to open the Select

Hint: Select the Discovered computers not reporting inventory filter from the drop-down list to
view all discovered client computers that do not have an Altiris Agent already installed. You can
also add the names of known computers in the Add field.
5

The collections or computer names listed on the Altiris Agent Installation page, will receive the
Altiris Agent. If you do not want to send to one or more clients in the list, highlight the client,
and then click the Delete icon to delete the entry.

Altiris Deployment Web Console Help

80

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Three: Deploying the Altiris Agent

After reviewing the client list, you are now ready to deploy the Altiris Agent. Click the Install
button and the Altiris Agent Installation Options page displays.

Altiris Agent

Select the Show the Altiris Agent icon in the system tray option and enter any other information on
the page, and then click Proceed With Install. The Altiris Agent will be copied to the client
computers and automatically installed.
Note: You must have global Administrator rights to deploy the Altiris Agent from the

Notification Server to client computers.

There is no process indicator to monitor the installation of the Altiris Agent on the client
computers. However, click the View Installation Status Report button to display installation report
options.

Click the Run this report option to open the Altiris Agent Installation status page.

10

Enter the property value in each field if you do not want to run the report with the default settings.

Altiris Deployment Web Console Help

81

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Three: Deploying the Altiris Agent

11

Click Refresh and all clients that you are deploying to will list if the Altiris installation was
successful.

12

Close the report window to return to the Altiris Console.

Windows XP Simple File Sharing


If Windows XP simple file sharing is enabled on a client computer within a workgroup, it will not
allow non-guest access over the network and will not allow the Altiris Agent to be deployed
remotely. By default, simple file sharing is enabled on a Microsoft Windows XP-based computer if
the computer is not a member of a domain. Therefore, Windows XP client computers in a
Workgroup must have simple file sharing disabled.
To Disable Simple File Sharing
1

Click Start, and then click My Computer.

On the Tools menu, click Folder Options, and then click the View tab.

In the Advanced Settings section, clear the Use simple file sharing (Recommended) checkbox.

Click OK.

Deploying the Altiris Agent from a Web Page


To download the Altiris Agent installation package from a web browser, you must pull the agent
installation file from Notification Server. This method of installation is required to install the Altiris
Agent on Windows 98 SE operating systems.
To install the Altiris Agent from a web page
1

From the Altiris Console, click the Configuration tab view. In the tree view pane, navigate to
Configuration > Altiris Agent > Altiris Agent Rollout.

Select Altiris Agent Installation. View the URL of the download page in the field under URL of
download page for Win32 users. You can e-mail this URL to your users to assist in installing the
Altiris Agent.

Click Show me this page to view the download page that you will send to users.

Altiris Deployment Web Console Help

82

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Four: Verify Server-to-Client Communication

The URL that you will send to your users will be of the form:
http://NSName:80/Altiris/NS/Agent/AltirisAgentDownload.aspx

where NSName is the name of the Notification Server computer.


You are now ready to configure the Deployment Solution.

Step Four: Verify Server-to-Client Communication


This last step verifies the installation of Notification Server, the Altiris Agent, and Deployment
Solution. There are several ways to test that all components are installed and to verify
communication between Notification Server and the managed client computer:

From the managed client computer, you can quickly verify the installation of the Altiris Agent
by simply checking the client computer. The Altiris Agent icon will appear in the system tray of
the managed computer.
When the Deployment Solution installation completes, the Altiris Agent will display a
Deployment Server properties command from its menu.

To verify that Deployment Server is installed on the destination computer, click the Altiris Agent
in the system tray of the destination computer and select Properties. Check the install status of
the Deployment Server install package, and the Deployment Agent package.

In a larger test environment with several managed computers, you may want to run the Altiris
report to check the client to server communication.
As part of its routine, the Altiris Agent sends basic inventory to Notification Server soon after it
is installed and reports the Altiris-enabled computers recently inventoried. This report can be
found in the Altiris Console by clicking the Reports tab view, then in the tree view pane,
navigating to Reports > Notification Server Infrastructure > Agent > Altiris Agent Inventory.
Agent basic inventory (sorted by last update)

Step Five: Install Deployment Servers


This section will detail how to install Deployment Server to client computers. Select one of the
methods below for more details about installing Deployment Servers.
Remotely Install Deployment Server (Push Silent Install) on page 83
Adding Deployment Servers on page 85

Remotely Install Deployment Server (Push Silent


Install)
This type of installation lets you enter each clients information on the Notification Server, and then
remotely (push) Deployment Server to a target destination, where a silent installation will be
performed. The term push install means that a policy is sent from Notification Server to a target
destination where Deployment Server will install. After receiving the policy, the client computer
will communicate with NS and pull down the Deployment Server packaged used during the silent
installation. This method of installing Deployment Server lets you manage the entire install process
from the Notification Server.
To Remotely Install Deployment Server
1

From the Altiris Console, click the Configuration tab.

Click Configuration > Solutions Settings > Deploy and Migrate > Deployment > Full Installation /
Upgrade > Install Wizard. The Deployment Server Installation Wizard page displays.

Click Run Installation Wizard.

Altiris Deployment Web Console Help

83

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Five: Install Deployment Servers

Click the Add Server icon to enter the IP address or computer name of the computer that you want
to receive Deployment Server from the Notification Server.

The Deployment Server Installation Settings page displays. This information is used on the
target client computer when DS performs the installation.

From the Deployment Server Installation Settings page, click the drop-down arrow and select
the computer you want to remotely install. The computers listed are compiled from the NS
database and display only if the client computer has the Altiris Agent and Microsoft SQL
Server installed.

Enter the Administrator username and password. All component services will run under this
account.

By default, the Free 7 day license option is selected. Leave this setting selected if you are
evaluating this product. If you purchased Deployment Solution, select the License file option.
A text field will display for you to enter the path where the licensing file (.lic file) is located,
or you can click the Browse icon to navigate to the licensing file location.

Click Advanced to configure options for the silent install. The IP address of the Deployment
Server computer will be listed. If you have multiple network adapters, then the first IP
address will be displayed.
Click one of the Deployment Server database authentication options, select the Install PXE
checkbox to install a PXE Server on the destination server, and then select the Install the
Deployment Web Console checkbox to install a stand-alone web console. Click OK.

Altiris Deployment Web Console Help

84

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Six: Synchronize the NS and DS Databases

If you do not have DOS boot files installed on NS, then a page will open asking you to find the
required DOS files.

Click one of the options to gather the DOS files at the bottom of the page, and then click Next.
The DOS files are gathered and the silent install begins.

Important: The installation of Deployment Server will begin after the Altiris Agent

configuration update. This can take several minutes to install.

Note: The configuration request interval is set from the Altiris Console in the Configuration tab

> Altiris Agent > Altiris Agent Configuration > All Windows Servers (or another appropriate collection).
For evaluation purposes, set the Request new configuration to 1 minute and set the Basic inventory

to 15 minutes.

Now that all the information for the target computer has been created, a policy is sent from
Notification Server to the client destination. The client receiving the policy, knows to connect to
NS and receive the DS package used on the client during the DS installation.
Note: The silent install of Deployment Server will take several minutes to complete.

Adding Deployment Servers


You can manage multiple Deployment Servers from the Deployment Web Console. To consolidate
multiple Deployment Server sites, you can identify and add existing Deployment Servers to appear
in the Computers and Jobs pane from the Deployment Web Console, or the Deployment tab of the
Altiris Console.
1

Click Add Deployment Server in the Computers or Jobs action list.

In the Deployment Servers page, type the name of the existing Deployment Server. This is the
computer name of the Deployment Server, in most cases.

Click Advanced to enter credentials if Deployment Solution security is enabled for the
Deployment Server. Also, enter the Domain and connection speed.

Step Six: Synchronize the NS and DS Databases


This section will help you set the polling intervals for the NS and DS databases. It is important to
understand that specific information from the DS database is sent to the NS. For the database
information to work correctly, be sure to set the Altiris Agent Basic settings for NS, and the polling
intervals for DS.

Altiris Deployment Web Console Help

85

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Six: Synchronize the NS and DS Databases

Set Altiris Agent Configuration for Notification


Server
Set the polling interval between the Notification Server and Deployment Server so that the data from
Deployment Servers will be transferred to the Notification Server database. Set a short polling
interval such as 10 minutes, so that the reports generated on Notification Server display more
accurately, Deployment Server data.

To Set the Altiris Agent Configuration for NS


1

From the Altiris Console, click the Configuration tab.

Click Configuration > Altiris Agent > Altiris Agent Configuration > All Windows Server (excluding
Package Servers). The Altiris Agent Settings page opens with the General tab view displayed.

In the Agent Basic Setting section, the Request new configuration information every option is set to
15 minutes (testing only). Click the drop-down arrow and select a different time interval from the
list.

By default, the Send basic inventory every option is set to 1 day (Recommended). Click the dropdown arrow and select a different time interval from the list.

Click Apply.

Note: These settings can be set to any length of time you want to update the database data. If the

polling interval is set more frequently, you have access to report information on the NS without
having to wait for long periods of time. For production purposes, change the polling intervals to meet
your network demands, so that the NS database is updated frequently through out the day.

Altiris Deployment Web Console Help

86

Chapter 3: Installing Deployment Solution from the Altiris Console

Step Six: Synchronize the NS and DS Databases

Set Polling Intervals for Deployment Solution


(Deployment view on Notification Server)
You must set the polling interval for all Deployment Servers so that the data stored in the DS
database is sent to the Notification Server database.

From the Altiris Console, click the Configuration tab.

Click Configuration > Solutions Settings > Deploy and Migrate > Deployment > Deployment Server
Agent Configuration > Deployment Server Agent Configuration. The Deployment Solution Agent
Configuration page is displayed.

By default, the Deployment Server Agent Config for all Deployment Servers collections selected.

Click the drop-down arrow and select a time interval from the Computer/Job Polling Interval list.

Enter a username in the Database Login ID field.

Enter a password in the Database Login Password field.

Re-enter the password in the Confirm Password field.

If you have enabled DS role-based security on the Deployment Server, you can enter the same
username in the Role based Username field. If you have not enabled DS role-based security, leave
the Role based fields blank.

Enter a password in the Role based Password field.

10

Re-enter the password in the Confirm Password field.

11

Click Apply.

Altiris Deployment Web Console Help

87

Using Deployment Solution


This section provides feature identification and basic procedures for deploying and managing
computer resources from the Deployment Console. See Managing from the Deployment Web
Console for instructions on deploying from the Deployment Web Console.
Quick Links
Managing from the Deployment Compare Deployment consoles and refer to
Console on page 89
general Deployment Server Console features.
Managing Computers on
page 106

Create new computer accounts, remotely operate


computers, and modify computer properties.

Building and Scheduling Jobs


on page 154

Build deployment jobs by adding and modifying


deployment tasks. Schedule jobs to run at Initial
Deployment or at an optimum time.

Managing from the Deployment Deploy and manage computer devices from the
Web Console on page 333
browser.
Managing Deployment Servers Configuration and management information for
on page 189
deploying network and Web servers

Altiris Deployment Solution Reference Guide

88

Chapter 4:

Managing from the Deployment Console


Deployment Solution provides both Windows and web user interface consoles to deploy and manage
computer devices across local or wide area networks. As an IT administrator, you can manage all
computer devices from one of these Deployment consoles:
The Deployment Console is a Windows-based console with complete deployment and management
features, including remote control, security, PXE server configuration, image editing, and other
deployment utilities and features. See Deployment Console Basics on page 89.
The Deployment Web Console provides basic deployment and management functionality from a web
browser, including the ability to remotely access and manage computer devices, build and schedule
jobs, and view multiple Deployment connections.
Deployment from the Altiris Console combines management and reporting features across multiple
Deployment Server systems and lets you integrate additional web applications in the client and
server management suites, including Inventory, Software Delivery, Recovery, HelpDesk, Patch
Management and Application Metering solutions.

To launch the Deployment Console, double-click the icon on the desktop, or


click Programs > Altiris > Deployment Server > Console.

Features of the Deployment Console. The Windows console for Deployment Solution provides
standard Computers, Jobs, and Details panes to drag and drop icons, view properties, and identify
state and status of Deployment objects. In addition, the Deployment Console also includes a
Shortcuts and Resources view and provides the tools, utilities and features required for complete
computer resource management. See Deployment Console Basics on page 89.
Set Program Options. From the Tools > Options dialog box, you can set preferences for each
Deployment Server system. See General Options on page 96.
Set Security. From the Tools > Security dialog box, you can set security rights and permissions for
all Deployment consoles. See Security in Deployment Solution on page 99.
Connecting to other Deployment Server systems. Connect to other Deployment Server

connections from your current Deployment Console and manage computers beyond your current
network segment or site. See Connecting to Another Deployment Server on page 104.

Customize the Tools menu. You can add commands to the Tools menu to open commonly-used

deployment programs and utilities. See Extending the Tools Menu on the DS Console on page 93.

Deployment Console Basics


The Deployment Console is your main portal to Deployment Solution. It is a feature-rich Win 32
program with real-time access to computer resources, deployment jobs, and package files, each
represented with distinct icons to identify status and settings. From the Deployment Console you can
build simple or complex deployment jobs, assign them to a computer group, and then verify
deployment execution.

Altiris Deployment Solution Reference Guide

89

Chapter 4: Managing from the Deployment Console

Deployment Console Basics

Because the Deployment Console can reside on its own computer, you can have multiple consoles
running from different locations. The Deployment Console only needs to be running while making
assignments or viewing information about the managed computers. You can turn on the console, run
management tasks, and then turn off the console without interrupting the execution of scheduled or
running jobs.
Scheduling information is saved in the Deployment Database and tasks are executed at their
scheduled time. If an assignment to a managed computer is made from two different consoles at
approximately the same time, the computer will be assigned those tasks in the order they are
received. See Console options on page 96 to set refresh intervals for the Deployment Console.

Features of the Deployment Console


Like all Deployment consoles, the Deployment Console is divided into several panes to organize
computers, deployment jobs, and software packages and scripts. It gives you a graphical view of
your network and provides features to build jobs, drag-and-drop icons to schedule operations, store
and access jobs and packages, and report the status and state of all of your computer resources. The
Deployment Server includes three main panes, plus toolbars, wizards, shortcuts, and utility
programs.

Computers pane
Use this area to view and select managed computers for the Deployment Server system. You can
select and right-click a computer in the Computers pane to run Remote Operations Using
Deployment Solution on page 134, or view Computer Properties on page 131. You can also
create computer groups to organize collections of similar computers.

Create Computer Groups by clicking Computer Groups on the toolbar, or rightclicking in the Computer pane and selecting Groups. Click View > Show
Computers to display only computer group icons and not the individual
computers.
When a computer or group is selected, the Details pane displays a list of computers in the group and
provides basic information about each computer. The Filter detail bar displays in the Details pane
that helps to view computers by a set criteria. When a computer is selected, you can view the
computer status in the Details pane, including a list of jobs that have run or are scheduled to run on
the computer, and the status of each job.
To get more details about all of the tasks that have run on computers, click Status Detail. Status detail
displays a more detailed breakdown of all of the processes the job has executed and a status message
indicating what has been completed.
You can also import new computers from a text file or add security rights and privileges for a
specified computer or group of computers. See Managing Computers on page 106 for complete
information about setting up, importing, and managing computers from the Computer pane.

Jobs pane
Use this area to create and build jobs with specific deployment tasks. You can select and right-click
a job in the Jobs pane when Building New Jobs or running the New Job Wizard. You can also import
new jobs from a text file or add security rights and privileges for a specified job or collection of jobs.
Set up folders to organize and access jobs in a way that makes sense to you. Create a new folder by
right-clicking in the Jobs section and select the New Folder option. You can also create folders by
selecting File > New > Folder.

Altiris Deployment Solution Reference Guide

90

Chapter 4: Managing from the Deployment Console

Deployment Console Basics

Click View > Jobs View to show or hide the Jobs pane.

When a job is selected, then the Details pane displays a list of computers in the folder and gives basic
information about each job, such as its state and status. It also shows the computers or computer
groups to which the job is assigned.

The Conditions detail bar is also displayed, allowing you to assign jobs to computers. See
Setting Conditions for Task Sets on page 159.

In System Jobs, folders are created to store jobs that are created when running operations from
the console.
Drag-n-Drop Jobs. Jobs are created and automatically placed in this folder when you drag an MSI,

RIP, or other package files from the Resources view to a specific computer or group, see the
Shortcuts and Resources View on page 91.
Image Jobs.

Jobs are placed in this folder when you create a Quick Disk Image.

Restoration Jobs.

Jobs are placed in this folder when you run a Restoring a Computer from its
Deployment History job.

From the Jobs pane you can drag job icons to computer icons to execute jobs, such as creating
images, deploying computers, changing configurations, or installing software. Once a job is created,
you can change it by adding, modifying, or deleting tasks. Jobs can be run immediately, scheduled
to run a particular time, or saved for a later time. See Building and Scheduling Jobs on page 154
for complete information about setting up, importing, and managing computers from the Jobs pane.

Details pane
The Details pane
Shortcuts panes.

extends the user interface features when working in the Computers, Jobs, or

When you select a computer in the Computers pane, the Details pane changes to a Filters area (if
you click a group icon) and displays the status of all jobs assigned to the selected computer.

When you select a job icon in the Jobs pane, the Details pane displays information about the job
to set up conditions, order tasks, and add, modify, or remove tasks.

When you select a computer or computer group in the Computers pane, the Details pane displays
information about a computer, including IP address, MAC address, and status.

When you select a batch file, you can click Modify to update the file.

When you select a hard disk image file (.img), the Details pane displays a description of the
image file, plus information about the included partitions.

When you click on package files, the Details pane displays the title, description, version, creation
date, and platform of a RIP or Personality Package.

Shortcuts and Resources View


The Shortcut and Resources pane provides easy access to the computers and job objects identified in
the console and the software packages stored in the Deployment Share. In the Shortcuts view, you
can drag computers, computer groups, jobs, and job folders to organize and access commonly-used
console objects. In the Resources view, you can identify and assign package files.

Altiris Deployment Solution Reference Guide

91

Chapter 4: Managing from the Deployment Console

Deployment Console Basics

Click View > Shortcuts to open the Shortcuts and Resources pane. You can drag
the jobs and computer icons to this pane. Click Resources in the Shortcuts and
Resources view, or click View > Resources or CTRL+R to open a filtered list of
packages residing on the Deployment Share.
The Shortcuts view provides quick links to view and access computers, jobs and packages. It can act
as a palette of Deployment Solution icons to drag to other working panes in the console, or storage
to save commonly-used jobs and computer icons.
The Resources view let you see a filtered view of the package filesMSI files, RIPs, image files,
Personality Packages, and other resource packagesstored in folders in the Deployment Share.
From the Resources view, you can drag packages directly to computers in the Computers pane to
deliver software. This automatically creates jobs in the System Jobs > Drag-n-Drop Jobs folder in the
Jobs pane. The Resources view lets you identify packages assigned to each job and assign those
packages to create new jobs.
Using Resources Directly
If you do not want to create a shortcut to a resource but still want to use a resource to assign work to
a computer, you can move the resource to a designated computer. To do so:
1

Enable the Shortcut view.

Click the Resources button at the bottom of the Shortcut window.

Browse to the selected resource and drag it to the appropriate computer.

You can create a new script file from the Resources view, and use it directly to schedule it on a
computer. See Creating New Script Files on page 184.
See Console options on page 96 for options to set refresh intervals for Resources view.

Toolbars and Utilities


The toolbars and menus on the Deployment Console provides major features and utility tools to
deploy and manage computers from the console. From the Main toolbar, you can create new jobs and
computer accounts and run basic deployment tasks. On the Tools toolbar, you can launch
Deployment Solution administration tools and package editing tools. It also includes buttons to
quickly run commonly used Remote Operations Using Deployment Solution.

Deployment Solution Utility Tools


The Deployment Console lets you open utility programs from the Tools menu or from the Tools
toolbar. You can launch Deployment Solution administration tools (Boot Disk Creator, PXE
Configuration, Wise SetupCapture and Remote Agent Installer) and package editing tools (Wise
MSI Editor, PC Transplant Editor, and Image Explorer) from the toolbar.
Administration tools

Boot Disk Creator. Use this tool to create boot disk configurations, and automation and
network boot media to image client computers. The Boot Disk Creator can maintain several different
boot disk configurations for different types of network adapter cards. See Altiris Boot Disk Creator
help.

Altiris Deployment Solution Reference Guide

92

Chapter 4: Managing from the Deployment Console

Extending the Tools Menu on the DS Console

PXE Configuration. After installing the Altiris PXE Server, you can create and modify
configurations, which make up the boot menu options that display on client computers. This is
another solution to boot computers to automation. See the Altiris PXE Configuration help.

Remote Agent Installer. Remotely install the Deployment Agent on client computers from
the console. This utility lets you push the agent installation to client computers from the Deployment
Console.

Carbon Copy. Remotely control managed computers to view and troubleshoot problems
from the Deployment Console. This utility provides comprehensive remote access features beyond
the Remote Control feature accessed by right-clicking a computer or computer group from the
Deployment Console.

Package Editing Tools

PC Transplant Editor. Use this tool to edit a Personality Package to add or remove data. See
the PC Transplant help located in the Deployment Share.

Image Explorer. After a disk image is saved to the Deployment share, this tool lets you view
and manage data in the image file. You can edit and split and image, create and index, and more. See
the Altiris Image Explorer help file located in the Deployment Share.

Wise MSI Editor. Edit MSI packages generated from the Wise Setup Capture tool or other
MSI files used to distribute software and other files.

Extending the Tools Menu on the DS Console


You can add commands to the Tools menu on the Deployment Console to quickly access additional
management applications. This allows easy access to applications commonly used with Deployment
Solution.
Commands are added by modifying or adding new INI files. You can insert commands to the root

ATools.ini file for the main menu or add new INI files to create submenus. Place both types of
INI files in the same directory where the Deployment Console executable (eXpress.exe) is located
(the default location is the Program Files\Altiris\ eXpress\Deployment Server).

You can add up to eight menu items to the main menu, and eight menu items for each submenu.
These INI fields are included for each application added to the Tools > Altiris Tools menu:
[Application name or submenu declaration]
MenuText=<the application name displayed in the menu>
Description=<the name displayed when you mouse over the menu item>
WorkDir=<directory set as default when executable is run>
Executable=<path to the executable files>

Altiris Deployment Solution Reference Guide

93

Chapter 4: Managing from the Deployment Console

Computer Filters and Job Conditions

The ATools.ini file extends the main Tools menu on the console. This sample file contains one
submenu, Web Tools, and two additional menu items, Notepad, and Netmeeting. The INI files are
located in the Deployment Share.
[Submenus]
Web Tools=wtools.ini
[Notepad]
MenuText=Notepad Editor
Description=Simple Editor
WorkDir=.
Executable=C:\WINNT\notepad.exe
[NetMeeting]
MenuText=NetMeeting
Description=NetMeeting
WorkDir=.
Executable=C:\Program Files\NetMeeting\conf.exe

Another Tools INI file is named wtools.ini. It is a submenu file referenced by the main ATools.ini file.
On the main menu this is titled Web Tools (see Tools.ini) and contains two applications, Explorer
and Acrobat.
[Explorer]
MenuText=Explorer
Description=Windows Explorer
WorkDir=.
Executable=C:\Program Files\Internet Explorer\explorer.exe
[Acrobat]
MenuText=Acrobat Reader
Description=Acrobat Reader
WorkDir=.
Executable=C:\Program Files\Adobe\Acrobat\acrobat.exe

Computer Filters and Job Conditions


Use this dialog box when Creating a Computer Group Filter to filter only the specified computers in
a computer group, or when Setting Conditions for Task Sets when running a job only on the specified
computers in a group.

Creating Conditions to Assign Jobs


You can Set Conditions on a scheduled job to run only on the computer devices that match a defined
criteria. As a result, you can create a single job with tasks defined for computers with varying
properties, including OS type, network adapters, processors, free disk space, and other computer
properties. You can then create task sets for each job that will apply only to the computers matching
those conditions.

Altiris Deployment Solution Reference Guide

94

Chapter 4: Managing from the Deployment Console

Computer Filters and Job Conditions

Click a job in the Jobs pane. The Condition feature will open in the Details pane. Click
Setup to add new conditions or edit existing conditions. When you are setting conditions
to schedule a job, select from a list of predefined database fields or create custom tokens
that key on other fields in the database.
Creating Custom Tokens
You can also create custom tokens to set conditions based on the database fields not provided in the
available preset conditions. in the Conditions dialog box. For example, select User Defined Token
from the drop-down list in the Fields box. Select contains in the Operation field, and enter Milo in the
Value field. In the Token field, enter the following custom
token:%#!computer@lic_os_user%.This filters out only the jobs with the registered license user
named Milo. The job runs only on the computers that meet the specified criterion.

Default Filters
Filter Name

Description

Active Computers

Displays all the active computers.

Inactive Computers Displays all the inactive computers.


Computers With
Failed Jobs

Displays all the computers where jobs have failed to execute.

Windows 9x/ME

Displays only the computers with Windows 9x or ME operating systems.

Windows NT/2000/ Displays only the computers with Windows NT, 2000, or 2003 operating
2003
systems.
Windows XP

Displays only the computers with Windows XP operating systems.

Windows CE
(PDAs)

Displays only the computers with Windows CE operating systems.

Linux

Displays only the computers with Linux operating systems.

Windows XP
Embedded

Displays only the computers with Windows XP Embedded operating systems.

Windows CE .NET Displays only the computers with Windows CE .NET operating systems.
Pocket PC (PDAs) Displays only the Pocket PC computers.

Creating a Computer Group Filter


For Computer Filters, this dialog box lets you display and list all computers in a group according to
a specified criteria. For example, you can create a filter to view all the computers in a particular
group that have Windows 2000, 256 MB of RAM, and 20 GB hard disks only. By applying the filter,
you can then view all the computers that meet the specified criteria in the Details pane of the
Deployment Console.

Click a computer group in the Computers pane. The Filter feature is displayed in
the Details pane for the selected computer group. Click Setup to add new filters,
or modify, and delete existing computer filters.
To create or modify a computer filter
1

Click the All Computers group or any other computer group.

On the Filter bar in the Details pane, click Setup > New to create a new filter.
Or

Altiris Deployment Solution Reference Guide

95

Chapter 4: Managing from the Deployment Console

General Options

click Setup > Modify.


3

Type a name for the filter, and click Add. The Filter Definition screen will be displayed.

Define the conditions you want to filter.


Click the Field box to see a list of computer values stored in the Deployment Database. Select a
computer value and then set the appropriate operation from the Operations list. In the Value box
enter an appropriate value for the selected database field.
For example, you can choose Computer Name as the Field, Contains as the Operation, and Sales as
the Value.

Repeat to include other conditions. Click OK.

General Options
Use Program Options feature to set general options for Deployment Solution. Click Tools > Options
to view the Program Options dialog box.

Console options (page 96)

Global options (page 96)

Task Password options (page 98)

Domain Accounts options (page 98)

RapiDeploy options (page 98)

Agent Settings options (page 98)

Custom Data Sources options (page 99)

Console options
Set basic console features for miscellaneous refresh actions and warning messages.
Scan resource files for changes every ____ seconds. Specify how frequently (in seconds) the
Deployment Console updates its view of package files in the Resources view, see Shortcuts and
Resources View on page 91.
Warn user when no tasks are assigned to the 'default' condition. When a job is assigned to computers
and the Default condition has no tasks assigned, then a message box is displayed. The job has no
secondary default tasks assigned if a computer in the group does not meet the primary conditions.
See Setting Conditions for Task Sets on page 159.
Refresh displayed data every ____ seconds. Refresh the display of data accessed from the Deployment
Database. This lets you refresh console data at defined intervals rather than updating every time the
Deployment Console receives a command from the server, which can be excessive traffic in large
enterprises.

Global options
Set global options for the Deployment Server system.
Delete history entries older than _____ days. Specify the number of days an entry is kept in the history

until it is deleted. Enter any number between 1 and 10,000. If you dont select this option, log entries
will remain in the history.

Remove inactive computers after ____ days. Specify

the number of days you want to keep inactive


computers in the Deployment database before they are deleted. The default value is 30 days, but any
number between 1 and 10,000 is valid.

Altiris Deployment Solution Reference Guide

96

Chapter 4: Managing from the Deployment Console

General Options

Synchronize display names with Windows computer names. Automatically update the displayed name

of the managed computer names in the console when the client computer name changes. If this
option is not selected, changes to the computer names will not be reflected in the console.
Synchronization is off by default. The names do not have to be synchronized for the Deployment
Server to manage the computer.
Reschedule failed image deployment jobs to immediately retry.

Immediately retry a failed image


deployment job. The program continues to retry until the job succeeds or until the job is cancelled.

Client/server file transfer port: _____.

Specifies a static TCP port for file transfers to the clients. The
default value is 0 and causes the server to use a dynamic port. This setting is useful if you have a
firewall and need to use a specific port rather than a dynamically assigned port.

Automatically replace expired trial licenses with available regular licenses. Allows Deployment
Solution to automatically assign a permanent license to the computer after the trial license expires.

Be careful when using this option. Make sure that you do not give a permanent license to computers
that you do not want to manage after their trial license expires.
Display Imaging status on console. Displays the status of the imaging job on the Deployment Console.
Remote control ports. Specifies ports for using the Remote Control feature. You have the option to
enter a primary port address and a secondary port address (Optional).
Primary lookup key. Specifies the lookup key type used to associate a new computer with a managed
computer. The options are Serial Number (SMBIOS), Asset Tag (SMBIOS), UUID (SMBIOS), or MAC
Address.
Sysprep Settings.

This lets you enter global values for Sysprep. See Sysprep Settings on page 97.

Sysprep Settings
View and configure the Sysprep settings for the Deployment Server.

Computer Information tab


In Computer Information tab, you need to enter the Computer Name, Suffix, and Current
Suffix. In the Licensing Information area, specify the user and organization name. You can
provide the licensing information by selecting the number of concurrent connections per
server or per seat.
Per Server: Per Server indicates that the end user purchased client access licenses for each
server, which allows a certain number of concurrent connections to the server.

Per Seat indicates that the end user has purchased a client access license for each
computer accessing the server.

Per Seat:

OS Product Key tab


In the OS Product Key tab, select the suitable operating system from the Operating System
drop-down list. After you select the operating system, a list of all product keys for the
selected operating system is displayed. Select an operating system from the Operating System
drop-down list, and click Add to type the Product Key. You can type up to 29 characters for
the Product Key. The new product key is added to the list of Available keys of the selected
OS.
To remove a product key, select the product key to be deleted, and click Remove.
Note: If the product key is being used by another task, you are not allowed to delete the

product key. You are prompted with a message stating that the product key is being used by
another task.

Altiris Deployment Solution Reference Guide

97

Chapter 4: Managing from the Deployment Console

General Options

Task Password options


This feature lets you set or change user passwords from a central location, so they can access the
tasks: Copy File to, Distribute Software, Run Script, Distribute Personality, and Capture Personality
when creating or modifying jobs. However, this tab is only visible to administrators and select users
who have been granted the appropriate privileges.
You must enter the information for all 4 fields before you can click the Update button. After the
users password is confirmed, the Deployment database updates the users credentials across
multiple Deployment servers at the same time.
The Status field shows the results of password updates. For example: if you select 5 Deployment
servers from the Computers pane, and you performed a Change Task Password for a user or group,
then the Status field will display the message: 5 records updated.

Domain Accounts options


This single sign-on feature retrieves the administrator (or user with administration rights) name and
password for each domain, allowing you to avoid logging on for each managed computer when
completing imaging and configuration jobs.
Click Add to enter the Domain name. The Add Domain account displays. Enter the name of the
selected domain and provide the administrator credentials. Click OK. The administrator name and
domain will be listed in the Domain Accounts list box.
Note: To enter the administrator user name for a Windows XP domain, you need to add both the
domain name with the user name. For example, instead of entering just the user name jdoe, you
need to enter domainName\jdoe.

RapiDeploy options
This feature optimizes the multicasting ability of the RapiDeploy application in Deployment Server,
allowing you to deploy images to a group of computers simultaneously, download an image from a
file server, or access a local hard drive, and manage the imaging of several client computers
concurrently.
Because RapiDeploy is more efficient when writing directly to the IP address of the network adapter
driver, you can enter a range of IP addresses when using the multicasting feature to speed computer
deployment and management. Deployment Server accesses the range of computers using the defined
IP pairs and avoids retrieving the computers through the port and OS layers.
However, because some network adapter cards do not handle multiple multicast addresses, you can
also identify a range of ports to identify these computers. On the first pass Deployment Server
accesses the selected computers using the list of IP numbers. On the second pass, Deployment Server
accesses the selected computers using the port numbers or higher level operating system ID's.
Note: Multicasting images is not supported when using the UNDI driver on PXE, and will be

disabled on the client.

Click Reset to set the default values.

Agent Settings options


These are the default agent settings for new computers. Click Change Default Settings to change
Windows Agents Settings for Windows and DOS. Set Production Agent Settings for new computer
accounts or set Automation Agent Settings for new computers.
These default settings are applied only for new client computers that have never connected to the
Deployment Server, and have no information stored in the Deployment Database. These settings are
not for the existing managed computers nor are these settings applied when setting properties using
the Remote Agent Installer.

Altiris Deployment Solution Reference Guide

98

Chapter 4: Managing from the Deployment Console

Force new agents to take these default settings.

adding a new computer.

Security in Deployment Solution

Select this option to force the default settings when

When the Deployment Agent connects, Deployment Server verifies if the computer is a new or
existing computer. If the client computer is new and if the Force new agents to take these default
settings option is selected, then the Deployment Agent on the client computer receives the default
settings established in the Options > Agent Settings dialog box. If the computer is recognized as an
existing managed computer, then it uses the existing agent settings.

Custom Data Sources options


This option lets you set up credentials to authenticate to external Deployment Databases and other
Microsoft SQL Server databases to extract data using custom tokens. Click Add to enter an
administrator alias and other login information for the Microsoft SQL Server (or MSDE) hosting the
desired Deployment Database.
The information required to create a custom data source entry are listed below:
Alias.

The alias name you would like to use when referencing the external SQL database.

Server.

The name of the external SQL database server or IP address.

Database.

The name of the external database from which you want to extract data.

Use Integrated Authentication. This option tries to authenticate to the external database using the
domain account you are currently logged on as.
User name and Password. When the integrated authentication is not being used, you must provide
a user name and password to authenticate to the external database.

Click Allowed Stored Procedures to allow or deny access to stored procedures for a custom
database.

Allowed Stored Procedure List


Click Allowed Stored Procedures to explicitly allow or deny access to a stored procedure in the
selected data source. If a token calls a stored procedure not in the list, then an error will be logged.
See the Deployment Solution 6.5 Reference Guide for information about creating and using custom
variables and tokens.

Virtual Centers
You can keep a list of all VMware Virtual Center web services. The hosts and virtual computers
from each Virtual Center that have corresponding computers in the Deployment Database will be
displayed in the computer tree. These virtual computers display under Virtual computers node in the
Computer pane.
Click Add on the Virtual Center page, and enter the Server host name, display name, and user name.
You can also set up a password for the selected user.
Note: Computers used as VMware hosts must have UUIDs.

Security in Deployment Solution


Deployment Solution provides a security system based on associating job and computer objects with
user and group permissions, allowing IT personnel to be assigned to different security groups to
manage operations on specific computer groups or job folders. Each security group can then perform
only a defined scope of deployment operations on each computer group or job folder. Additionally,
each user can be assigned rights to access general console features.
Note: Security rights and permissions set in one console are enforced in all Deployment consoles.

Altiris Deployment Solution Reference Guide

99

Chapter 4: Managing from the Deployment Console

Security in Deployment Solution

To set general security rights, click Tools > Security and add a user name and
password. You can create users and groups and set scope-based rights.
To set feature-based permissions for specific computers or jobs, select the object
in the console, right-click and click Security.
See also
Best Practices for Deployment Solution Security (page 100)
Enabling Security (page 100)
Setting Permissions (page 103)
Groups (page 102)
Rights (page 102)

Best Practices for Deployment Solution Security


Deployment Solution is based on defining groups of users and groups of computers and jobs, and
then associating one with another. Altiris recommends that you first create user groups based on
administration duties or access to levels of deployment operations. Example: you will most likely
set up a group with full Administrator rights. This group will have access to run all operations on all
computers using all types of jobs. No permissions need to be set on each computer group or job
folders for the Administrator group because they have full rights to all features and resources.
However, you can also set up a Technician group that has only basic access and permissions limiting
deployment operations. This will prohibit members of the group from re-imaging the Server
computer group or scheduling Distribute Disk Image jobs. You can explicitly Allow or Deny the
group from running these operations for each computer group in the Computers pane or each job
folder in the Jobs pane.
After creating the Technician group, you can limit their rights to set General Options and then set
permissions on each computer groups and job folder for the group. You can select the computer
group, right-click it and select Permissions. Then select the group name in the left pane, and click
Allow or Deny for a list of deployment operations. Example: you can select the Deny checkbox for
Restore, Schedule Create Disk Image, and Schedule Distribute Disk Image.
Additional groups can be created with different rights and permissions depending on the needs and
responsibilities in the IT team. If users are assigned to multiple groups, the Evaluate Permission and
Evaluate Rights features will sort and display effective permissions and rights.

Enabling Security
You can enable security by first creating a group with Administrator rights, adding a user to the
Administrator group, and then selecting Enable Security.
Note: When the Administrator Right is selected, you do not need to select any other rights because

the Administrator Right implies that all other rights are selected.

Click Tools > Security.


The Security dialog box displays.

Click Manage User Groups tab and click Add. The Add User Group dialog box displays.

Select the authentication type. You can choose to add a DS group or a group from the Active
Directory. To add groups from Active Directory, see Adding groups from the Active Directory
on page 102.

Click DS Group
Note: The Browse button is disabled for Local Group.

Altiris Deployment Solution Reference Guide

100

Chapter 4: Managing from the Deployment Console

Security in Deployment Solution

Type a name and description in the Add User Group dialog box. Click OK.
The group name displays in the window.

Select the new group name and click Rights.

Select Administrator in the Rights dialog box. This assigns complete rights and permissions to
the group. Click OK, and click Close.

On the main Security dialog box, click Manage Users tab, and click Add.
The Add User Account dialog box displays.

Select the authentication type. You can choose to add a DS user or a user from the Active
Directory. To add users from Active Directory, see Adding users from the Active Directory on
page 101.

10

Click DS User in the Add User Account dialog box.


Note: The Browse button is disabled for DS User.

11

Type user name, full name, and password. Retype the password, and provide a description for
the user. Click OK.

12

Select the user name in the main Security dialog box. Click the Rights button.

13

Click the name of the new Administrator group in the Groups window. This assigns the new user
to the new group with Administrator rights. Click OK.
Note: You can assign the user Administrator rights directly, but assigning users to groups is

advised. See Best Practices for Deployment Solution Security on page 100.

14

Now that you have a user with administrator rights, select the Enable Security box.

Security is now enabled. You can now create users and groups and assign permissions to computer
groups and job folders.
Adding users from the Active Directory
You can add users from the Active Directory.
1

In the main Security dialog box, click Manage Users tab, and click Add.

Click AD User in the Add User Account dialog box.

If you know the user name, type it in the User name box, or click Browse to select user from the
Active Directory.
The password field is deactivated as the user is being added from the Active Directory.
Note: You can add only one user at a time. To import users, see Importing users from the Active

Directory on page 101.

Type a description for the user in the Description box.

Click OK.

Importing users from the Active Directory


You can also import users from the Active Directory. In the main Security dialog box, click Manage
Users tab, and click AD Import to open a standard Windows Active Directory dialog box. Add users
from Active Directory, not groups. The users are added to the Deployment Database. However, you
still need to assign the users to security groups with appropriate rights and permissions.
Note: When logging on with the imported AD account, Deployment Solution accessed the Windows

Active Directory server to validate the user password.


Evaluate Rights

Click Evaluate Rights to identify the combined rights of the selected user and its user group(s). This
feature identifies effective rights for each user by resolving any possible conflicts between multiple
group settings.

Altiris Deployment Solution Reference Guide

101

Chapter 4: Managing from the Deployment Console

Security in Deployment Solution

Groups
Assign the user to previously created groups. If you are enabling security, you can assign the user to
a group with Administration rights.
To add groups, from the Security dialog box, click the Manage User Groups tab, and click Add. Select
the authentication type, and then type the required details. You can view the members of any group
by clicking the group in the Manage User Groups dialog box and clicking View Members.
See also Best Practices for Deployment Solution Security on page 100, and Enabling Security
on page 100.
Adding groups from the Active Directory
You can add users from the Active Directory.
1

In the main Security dialog box, click Manage User Groups tab, and click Add.

Click AD Group in the Add User Group dialog box.

If you know the group name, type it in the Name box, or click Browse to select the group from
the Active Directory. A list of groups, along with their descriptions, display in a new dialog box.
Select a group from the list, and click OK.

The Name, Domain, and Description gets automatically filled. However, you can modify the
description. Click OK.

The newly added group displays in the main Security dialog box.
Importing groups from the Active Directory
You can also import users from the Active Directory. In the main Security dialog box, click Manage
User Groups tab, and click AD Import to open a standard Windows Active Directory dialog box. Add
groups from Active Directory. You can choose a domain from the Domain List, and select a group
from the displayed list. The group is added to the Deployment Database. However, you still need to
assign the users to security groups with appropriate rights and permissions.
DS Authentication
If the user is already in the DS database, and it tries to access the Deployment Console, then
Deployment Server checks the authentication with the logged on user, and upon matching does not
prompt for user credentials. Similarly, if a group has already been added in the DS database, and if
a system logged-on user, who is a part of the AD group, tries to access the Deployment Console,
then Deployment Server does not prompt for credentials.

Rights
This dialog box lets you set general rights for a user or group. To verify, add or change the rights
assigned to each console user, use the following steps:
1

From the Security screen, select a user and click Rights.

From the Set Rights For window, click the Rights tab.

Select the checkbox for each right that you want to grant.

After selecting all applicable rights, click OK to save your changes.

A brief explanation of each Deployment Server right that can be assigned is detailed below:
Administrator. Lets user access to all features available on the Deployment console. You must
have Administrator rights to enable security. See Enabling Security on page 100.
Options Console. Lets you set Console options. If this checkbox is selected, you can set the view

and set the console options.

Options Global. Lets you to set Global options. If this checkbox is selected, you can view and set

the global options.

Options Domain Accounts.

domain accounts option.

Altiris Deployment Solution Reference Guide

Lets you set Domain Accounts options. You can view and set the

102

Chapter 4: Managing from the Deployment Console

Options RapiDeploy.

options.

Security in Deployment Solution

Lets you set RapiDeploy options. You can view and set the RapiDeploy

Options Agent Settings.

settings.

Lets you set Agent Settings options. You can view and set the agent

Options Custom Data Sources. Lets you create Custom Data Sources options. You can view,
create, and set database aliases.
Manage Rejected Computers.

change status.

Lets you view Rejected Computers in Deployment Solution and

Refresh Clients. Lets you Refresh Deployment Solution clients. You can use
clients <CTRL +F5> feature to disconnect and reconnect client computers.

the View > Refresh

Allow scheduling on All Computers. Lets you schedule jobs on All Computers. If you have
administrator rights, then by default you have the rights to schedule job on all computers,
irrespective of the checkbox state. You can grant this right to a specific user or a group.
Import/Export. Lets

you import and export jobs and import computers as well. See Importing
and Exporting Jobs on page 184 and Importing New Computers from a Text File on
page 110.

Options Task Password. Lets you centrally update passwords for users and groups so they can
access the tasks: Copy File to, Distribute Software, Run Script, Distribute Personality, and Capture
Personality when creating or modifying. You must have administrative rights to access this

option. See Task Password options on page 98.

Use PXE Configuration Utility. Lets

you use the PXE Configuration Utility.

Options Virtual Centers. Lets you view and add options for Virtual Centers. See Virtual Centers

on page 99.

Setting Permissions
Set permissions for jobs, job folders, computers, and computer groups. See Best Practices for
Deployment Solution Security on page 100 for additional design tips.
1

Right-click on a computer group or job folder (or individual computers and jobs) and select
Permissions. The Object Security dialog box displays.

Click the Groups tab and select a group name. Or click the User tab and select a user name.

From the list in the right pane, select if you want to Accept or Deny permission to run the
operations on the selected computers or job objects. These permissions include access to Remote
Operations Using Deployment Solution and features for scheduling Deployment Tasks.

Select the Allow or Deny checkbox to explicitly set security permissions for these Deployment
Solution features for the selected objects.
Note: Administrators have access to all objects with unrestricted rights and permissions. You

cannot explicitly deny permissions to computer or job objects for users with administrator rights.

To assign permissions to multiple groups, click Set permissions on all child objects to assign the
values without closing the dialog box.

Click Close.

Note: You can set permissions for all jobs and computers by clicking in the Jobs pane or Computers
pane without selecting a job or computer object.

Permission Rules
Permissions received through different sources may conflict with each other. The following
permission rules determine which permissions are enforced:

Permissions cannot be used to deny the user with Administrator console rights access to use
any console objects or features.

User permissions take precedence over Group permissions.

Altiris Deployment Solution Reference Guide

103

Chapter 4: Managing from the Deployment Console

Connecting to Another Deployment Server

Deny

Permissions do not flow down an object tree. Instead, the object in question looks in the
current location, and then up the tree for the first permission it can find and uses the same.

If a console user does not have permissions to run all of the tasks the job contains, the user is
not allowed to run the job.

overrides Allow. When a user is associated with multiple groups, one group could be
allowed a permission at a particular level while the other group is denied the same
permission. In this scenario, the permission to deny the privilege is enforced.

Evaluate Permissions
Click Evaluate Permissions to identify the combined permissions of groups and containers with
contrasting permissions. This feature identifies effective permissions for each object by resolving
any possible conflicts.
If a job includes multiple tasks and one of the tasks does not have sufficiently assigned permissions,
then the whole job fails due to lack of access permissions.
Note: Permissions to schedule jobs also allows a user to delete jobs in the Details pane after a job

runs. For example, if a job contains errors and does not run, then no other jobs can be scheduled. The
user must delete the job before scheduling a new job.

Connecting to Another Deployment Server


From the Deployment Console you can connect to other Deployment Servers on your LAN and
manage computers beyond the network segment that you are currently logged on to. Opening a
connection requires that you connect to the Deployment Database of the preferred Deployment
Server connection using the ODBC Data Source Administrator.

Click File > Connect to or press CTRL+O to open the Connect to Deployment Server
dialog box. Enter requisite information to connect to the external Deployment
Server connections using an ODBC driver.
Note: Although you are accessing another connection (another Deployment Database), Windows

remembers the last place you browsed to, which would be the Deployment Share of the previous
Deployment Server connection. You need to browse to the new connections Deployment Share to
access its shared folder containing its RIPs, images, executables, and other resources.

Connecting to a new Deployment Database


1

Click New.... The Define Connection Information dialog box displays.

Enter a name for the connection to be opened.

Establish an ODBC data source.


a

Click ODBC Administrator.

Click the System DSN tab, and then click Add.

Select the SQL Server driver source and click Finish.

In the Create a New Data Source to SQL Server dialog box, enter a name and description for
the data source.

If an entry for your server already exists, select it from the menu. Otherwise, enter the name
of the server hosting your remote SQL server in this box. Click Next.

Click Next in the Create a New Data Source to SQL Server dialog box to accept the default
settings.

Select the Change the Default Database to: checkbox and then select eXpress from the menu.
Click Next.

Click Finish. The specifications for the ODBC data source displays.

Click Test Data Source... to verify that the source is reachable.

Altiris Deployment Solution Reference Guide

104

Chapter 4: Managing from the Deployment Console

Rejected Computers in Deployment Solution

Click OK. You will return to the main ODBC Data Source Administrator dialog box with
your new data source listed in the System DSN tab. Click OK.

Using the menu in the ODBC Data source name dialog box, select the new Data Source name
you just created.

In the Installation Directory path field enter the full UNC path (or path using any locally mapped
drive) to the directory of the required Deployment Server, for example:
\\SalesServer\express or H:

Click OK.

Rejected Computers in Deployment Solution


When an unwanted managed client computers attaches to your Deployment Solution system, you
can right-click the computer in the Computers pane and select Advanced > Reject Connection. You
can view these rejected computers by clicking View > Rejected Computers.
The rejected computers are prohibited from being active in the Deployment Database. They are
identified and rejected by their MAC address.
You can remove computers from the Rejected Computers list by selecting it and clicking Accept
Computer(s). This allows the computer to attach again and be managed by the Deployment Solution
system.

Refresh Deployment Solution


You can refresh the Deployment Console by clicking View > Refresh Console (or pressing <F5>) to
update data from the Deployment Database. You can also click View > Reset Client Connections (or
press Ctrl+<F5>) to disconnect and reconnect all managed computers in a Deployment Server system.
When you refresh the managed client computers, you are asked if you want to disconnect all
computers. Click Yes. This tells the Deployment Agent to shut down and restart. It also creates
additional network traffic when all computers connect and disconnect. By refreshing the managed
client computers, you ensure that you are viewing the current status and state of all computers
resources in your system.

Altiris Deployment Solution Reference Guide

105

Chapter 5:

Managing Computers
From the Computers pane of a Deployment Solution console, you can identify, deploy, and manage
all computer resources across your organization, including desktop computers, notebooks,
handhelds, network and web servers, and network switches. You can quickly modify any computers
configuration settings or view its complete management history. Or you can take on big projects,
like completely re-imaging the hard drive, restoring software and migrating personality settings for
a whole department. You now have management of all your computer resources available from a
Windows or web console from any location.
All computer resources can be accessed and managed as single computers or organized into
computer groups with similar hardware configurations or deployment requirements, allowing you to
run deployment jobs or execute operations on multiple computers simultaneously. You can use
search features to locate a specific computer in the Deployment Database, or set filters to sort
computers by type, configuration, OS, or other criteria.
Manage with Computer icons. Major computer types are identified by a computer icon in the

console, with a listing of scheduled jobs and operations associated with each computer. In the
Deployment Console, you assign and schedule deployment jobs to computers or groups by dragging
the computer icon to a job in the Jobs pane, or vice versa. See Viewing Computer Details on
page 107.

Computer icons displays in the Computer pane of the Deployment console where
they can be organized into groups. To assign and schedule a computer in the
Deployment Server Console, drag a computer icon or group icon to a job icon.
Add new computers. Deployment Solution lets you add new computer accounts and set
configuration properties for new computers before they are recognized by the Deployment Server
system. Preset computer accounts will automatically associate with new computers when they start
up, or can be associated with pre-configured computers. See Adding New Computers on page 108.

Click the New Computer button on the console to create a new computer account.
You can also click File > New > Computer or right-click in the Computers pane
and select New Computer.
When the new computer starts up you can assign it a preset account.
Click the New Group button on the console to add a new group in the Computers
pane of the Deployment console. You can also click File > New > Computer Group
or right-click in the Computers pane and select New Group.
Deploy to groups of computers. Organize computers by department, network container, hardware
configuration, software requirements, or any other structure to meet your needs. You can then
deploy and provision computers on a mass scale. To filter computers in a computer group to
schedule jobs only to the appropriate computer types, see Computer Filters and Job Conditions on
page 94.
Configure Computer Agents. See the property pages for modifying Deployment Agent settings.

See Deployment Agents on page 118.

Altiris Deployment Solution Reference Guide

106

Chapter 5: Managing Computers

Viewing Computer Details

View and configure computer properties. You can modify computer settings for each computer

from the console. See Computer Configuration Properties on page 111. Or you can view the
Computer Properties page for detailed access to a computers hardware, software, and network
property settings. See Computer Properties on page 131.

Run remote operations from the console. Perform operations quickly in real-time from a

Deployment console. Restore a computer to a previous state, configure property settings, send a file,
remote control, chat, set security, run deployment jobs or select from additional management
commands. See Remote Operations Using Deployment Solution on page 134.

Build and schedule jobs. Build deployment jobs with one or more management tasks to run on

selected computers. Create jobs and add tasks, then assign the job to computer groups. Jobs can be
organized and assigned for daily tasks or to handle major IT upgrades. See Building and Scheduling
Jobs on page 154.
Manage Handhelds. Deployment Solution manages handheld computers (PDAs). See
.Deployment Agents for Pocket PC on page 127.
Manage Servers. Deployment Solution also manages network or web servers to administrate highdensity server farms or server network resources across your organization. See the Deployment
Solution Reference.

Viewing Computer Details


In Deployment Solution, a computer resource is identified in the console with a distinctive icon to
display the computer type Windows desktop or notebook, handheld, server, or Linux OS and
its current status. These computer icons change to convey the state of the computer, such as the log
on status, server waiting status, or user with a timed license status. You can also view the status of
the jobs assigned to the selected computer in the Details pane of a Deployment console (see
Viewing Job Details on page 154).
The following is a sample list of computer icons displayed in each Deployment console, identifying
computer type and state.

Managed Computers

Computer connected to the Deployment Server with a user logged in.

Computer connected to Deployment Server but the user is not logged on.

Computer with a time-limited user license and a user logged on.

Computer not currently connected to the Deployment Server but known to the
Deployment Database.
A pre-configured with values defined in advance using the New Computer feature. As
soon as the computer connects and the Deployment Server recognizes the new
computer and changes the icon. See Adding New Computers on page 108.
A managed computer waiting for user interaction before running deployment tasks.
This icon displays if the Workstations checkbox is selected in Initial Deployment. See
Sample Jobs in Deployment Solution on page 186.
A master computer is identified as a computer used to broadcast images to other client
computers.

Altiris Deployment Solution Reference Guide

107

Chapter 5: Managing Computers

Adding New Computers

Managed Computers

A connected handheld computer.

A managed server connected to the Deployment Server with a user logged on.
Additional icons identify different states of server deployment.
A managed Linux computer connected to the Deployment Server with a user logged on.
Additional icons identify different states of Linux computer deployment.

Blade Servers - physical view

Physical view of Rack/Enclosure/Bay components for high-density server


systems. These icons display as physical representations to allow management
of different levels of the server structure. In addition, server icons identify
logical server partitions. See Bay on page 133 for properties and rules to
deploy Rack/Enclosure/Bay servers.

Computer Groups

Select the New Computers or All Computers group to run jobs or operations for these
default groups identified by an icon in the Computers pane.
Additional computer groups can be added to the Computers pane to organize similar
computer types or to list computers of similar departments or locations. Click the New
Group button or select New > Computer Group to create a new group.
See also Deployment Agents on page 118.

Adding New Computers


Computers can be added to the Deployment Database using three methods:

Install the Deployment Agent. If you install the Deployment Agent to a computer with the

operating system already installed, then the computer will be added automatically to the
Deployment Database at startup. New computers with the Deployment Agent installed will be
added to the All Computers groups (unless otherwise specified in the Deployment Agent
configuration). You can then move the computer to another group if desired.

Use Initial Deployment to configure and deploy new computers booting to automation.
Starting up a new computer with the Automation Agent lets you image the hard drive, assign IP
and network settings, distribute personal settings and software, and install the Deployment Agent
for new computers. Using Initial Deployment you can associate new computers with preconfigured computer accounts. These newly configured computers display in the New Computers
group. See Sample Jobs in Deployment Solution (page 186) .

Create or import computer accounts from the Deployment console. You can add new

computers using the New Computer feature or import computers using a delimited text file. You
can pre configure computer accounts by adding names and network settings from the console.
See Creating a New Computer Account on page 109.

Altiris Deployment Solution Reference Guide

108

Chapter 5: Managing Computers

Adding New Computers

About New Computers


When a new computer starts up, if Deployment Server recognizes the MAC address provided in a
New Computer account or import file, it will automatically associate the user account at startup with
the New Computer icon. If this value is not provided, then the computer will be displayed as a preconfigured computer account, allowing you to associate it to a new computer.

The New Computer icon displays for a new computer if the MAC Address is
provided when creating a new computer account using any import or new
computer account feature.
A pre-configured computer account icon displays if specific hardware data
(MAC Address) is not known. As soon as the computer starts up and is
associated with a pre-configured computer account, then Deployment Server
recognizes the new computer and the icon changes.
A pre-configured computer account can be associated with a new computer using the Initial
Deployment feature. You can create multiple pre-configured computer accounts and then associate
the account with a new computer when it boots to automation. At startup, the configuration settings
and jobs assigned to the pre-configured computer account can be associated with the new computer.
Pre-configured Computer Account
Deployment Solution provides features to create a pre-configured computer account to pre-define a
computers configuration settings and assign customized jobs to that computer even if you do not
know that computer's MAC address. This type of computer is known as a pre-configured computer
account.
Pre-configured computer accounts offer a great deal of power and flexibility, especially when you
need to deploy several computers to individual users with specific needs. The pre-configured
computer account saves your time because you can configure the computer before it arrives on site.
You can set up as much configuration information (computer name, workgroup name, and IP
address, for example) that you know about the computer and apply it to the new computer as it comes
online. You can also prepare jobs prior to the arrival of the new computer to deploy the computer
using customized images, MSIs and RIPs based on a user's specific needs.
Example: a user might request Windows 2000 with Office 2000 and virus scanning software
installed on the new computer. The user also might request that his or her personality (customized
user settings, address books, bookmarks, familiar desktop settings) be migrated from the old system.
You can build any job, including any of the available tasks, and assign it to a pre-configured
computer account.
When the new computer finally arrives, you will be ready to deploy it because you have done all the
work ahead of time. Boot the client computer to automation (, and the new computer will connect to
the server and become a managed computer. Then you can perform an Initial Deployment, or run a
deployment imaging job on the new computer.

Creating a New Computer Account


You can create computer accounts for individual computers or for computer groups. When creating
new accounts for computer groups, you can automatically assign new names and associate them with
existing computer groups or the New Computer group.

Click the New Computer button on the console to create a new computer account.
You can also click File > New > Computer or right-click in the Computers pane
and select New Computer.

Altiris Deployment Solution Reference Guide

109

Chapter 5: Managing Computers

Adding New Computers

To create a new computer account


1

Click Add.

Enter names and configuration settings for each new computer account using the Computer
Configuration screens. See Computer Configuration Properties on page 111 for a description
of the configuration settings.
Note: If you do not enter a MAC address, the computer you create or import will become a

virtual computer.

Click Import to add new computers from a delimited text file (see Importing New Computers
from a Text File on page 110). This is optional.

Click OK.
A pre-configured computer account icon displays in the Computers pane.

When a new computer starts up, you can assign it to this preset account.
To create and associate multiple computer accounts
You can create computer accounts and automatically assign predefined names. These computer
accounts can then be associated with computers in a selected computer group.
1

Select a computer group, including the New Computers group (empty groups cannot access
features). Right-click and select the Configure command.

Enter names and configuration settings for each new computer account using the Computer
Configuration screens. See Computer Configuration Properties on page 111.

Click the Microsoft Networking category and click the Define Range button. This is optional.
a

In Fixed Text box, type a base computer name. Example: enter Sales.

Type a numeral or letter in the Range Start box to add to the Fixed Text name. This will create
a unique name for a group of computers starting with the specified character. The range of
numerals and letters will be assigned to the computer name. Example: enter 3.

Select Append to add the range of numerals after the computer name. Clear the checkbox to
add names before the computer name.
The example computer names will begin with Sales3 and end with Sales7.

Click OK.

Click the Associate button. You can now associate computers in a group (including the New
Computers group) with the multiple computer accounts.

Click OK.

Importing New Computers from a Text File


You can import computer configuration data using delimited text files (.txt, .csv, or .imp files) to
establish multiple computer accounts in the Deployment Server database. This file contains all
configuration data for a new computer, including all settings displayed in the Computer Properties
of a selected computer.
1

Click File > Import/Export > Import Computers.


A dialog box will open allowing you to select import files. These files can have txt, csv, or imp
extensions.

Select the import file. Click Open.


If a correctly formatted computer import file is selected, then a message box displays, informing
you that the computer import is complete and identify the number of computers added. Click OK
on this message box.
New computers will display as pre-configured computer accounts in the Computers area of the
console (as single computers or in groups), and any jobs imported from the import file will be
listed in the Jobs area.

Altiris Deployment Solution Reference Guide

110

Chapter 5: Managing Computers

Computer Configuration Properties

Note: Jobs can be added to the import file. They can be created and associated with the new

computers.

If the computer import file is incorrectly formatted, a warning displays, stating that the computer
import file is incorrect.
3

Edit computer settings by selecting a computer from the list and clicking the Properties button.

The Computer Properties sheet opens to edit or add values not set in the import file, such as
computer name, TCP/ IP settings, user name, and other configuration settings.

Click OK.
The imported computers displays in the Computers pane of the Deployment console.

You can also import a computer to be placed in a sub-folder in the Computers pane and create a job
to be associated with the imported computer. See the sample import file for additional information.
Referencing the Sample Import File
When creating an import file, use either the ImportComputers55.txt file or the
ImportComputers55.xls file in the Samples folder of the Deployment Share. The
ImportComputers55.txt file provides a sample import template you can access to test the Import
feature. The ImportComputers55.xls file is a Microsoft Excel spreadsheet that lets you add
values to each identified column and then save the file as a delimited TXT file to import to the
Deployment Database. The sample import file places a computer (DB Computer 1) in a computer
group (Test Group) and adds a job (Test Job) that is associated with the imported computer.
Note: Altiris Deployment Solution 5.5 and later use the 5.5 format for importing computers.

Previous versions of Deployment Solution use the 4.0 format.


Deploying New Computers on a Mass Scale

If you need to deploy large numbers of computers (100 to 5,000), consider using a barcode scanning
system to collect user information (names, OS and application needs) and computer information
(MAC address, serial numbers, asset tags). You can save this information to a file, which can then
be imported into the New Computers List View. Depending on the number of incoming computers, the
amount of information you have about those computers, and the needs of individual users, you can
use either the pre-configured computer account method (best for smaller numbers of new computers)
or the Initial Deployment job (best when deploying generic setups by departments or groups).
If you are using an import file, make sure you know primary lookup key. This is the piece of
information that Deployment Server needs to set up a unique computer. The primary lookup key can
be Serial Number, Asset Tag, UUID, or MAC address.

Computer Configuration Properties


These computer property settings can be viewed, set, and modified when performing the following
computer management operations:

Adding New Computers (page 108) .

Modifying Configuration (page 176) . Create or edit property settings in a deployment job.

Sample Jobs in Deployment Solution (page 186) configuration settings.

Click the configuration group icons to set additional computer property values. After you edit these
computer property settings, the computer will be restarted so that the changes can take effect.

Computer Configuration Properties

General Configuration Settings

Set the most important value from this property sheet. It


includes the name of the computer in Deployment
Solution, the NetBIOS name of the computer, the MAC
address and other settings.

Microsoft Networking Configuration Set the Windows name of the computer and the
Settings
Workgroup or Domain settings.

Altiris Deployment Solution Reference Guide

111

Chapter 5: Managing Computers

Computer Configuration Properties

Computer Configuration Properties

TCP/IP Configuration Settings

Set the TCP/IP addresses for one or more network


adapters.

NetWare Client Configuration


Settings

Set Novell Directory Services client logon options.

OS Licensing Configuration Settings Set the registered user name and view the hashed
installation license key for the installed operating system.
User Account Configuration Settings Set the local Windows user account values.

General Configuration Settings


The General category provides access to important property settings that are also
listed in other configuration categories. Click other category icons to view and
set additional configuration properties.

Field

Description

Name

Provides a name that displays in the Deployment console (not the BIOS name
of the computer).
Note: The Name box will be disabled for multiple computer configuration.

MAC address

The unique identification address of the network adapter.

Serial Number

The serial number of the computers motherboard.

Asset Tag

The asset tag of the computer, if available.

Computer Name

The Windows name of the computer.

IP Address

Current IP address of the computer. Multiple IP addresses are listed in this


box.

Registered User

The name of the user who registered the operating system software

License key

The hash value rendered from the OEM key or 25-digit license key required
when installing the operating system.

User name

The user name for the local Windows user account.

Full name.

The full name for the local Windows user account.

Password

The password for the local Windows user account.


See also Computer Configuration Properties on page 111.

Microsoft Networking Configuration Settings


Enter the computer name and workgroup or domain property settings for the
managed computer. If you are using Active Directory, you can add computers to
a domain and a specified organizational unit (OU).
Use the SIDgen or SysPrep utilities to generate unique SIDs. This can be done by manually running
either or both of these utilities or selecting these features while installing the Deployment Agent.

Altiris Deployment Solution Reference Guide

112

Chapter 5: Managing Computers

Computer Configuration Properties

Field

Description

Computer Name

This is the NetBIOS name for the computer. The name must be unique in the
network and is limited to 15 characters.
Note: The Computer Name box will be disabled for multiple computer
configuration.

Define Range

Click to create a sequential range of computer names. You can identify a root
name and automatically increment its associated number. This option is
available when selecting groups of computers.
Note: When setting name ranges, do not set names using multiple Modifying
Configuration tasks and then assigning the names by Setting Conditions for
Task Sets. If you set up two separate name ranges to be assigned by separate
conditions, then the computer names will increment irrespective to the base
name.

Workgroup

Click and enter the name of the workgroup to place the managed computer.

Domain

Enter either the fully qualified domain name, the DNS domain name, or the
WINS domain name. You can enter the fully qualified domain name (for
example, mjones.yourcompany.com), and specify the organizational unit
(OU) using this format: OU/newOU/users. The complete entry to place the
computer in the users OU is the following:
mjones.yourcompany.com/OU/newOU/users
internal.myServer.org/New Corporate Computer OU/Mail Room/
Express Mail Servers

Altiris Deployment Solution Reference Guide

113

Chapter 5: Managing Computers

Computer Configuration Properties

Field

Description

Computer Name
Range

For new computers, set a range of names for multiple new computers:
Fixed text. Enter the text portion of the name which you want associated
with each computer, for example: Marketing.

Range start. Enter a whole number to add to the fixed text, for example: 1.

Append. Select this checkbox to add the range after the fixed text in the
computer name. If you clear this box then the number will be added as a
prefix to the fixed text.

Result.

Associate. Click to match new computer accounts with new computers.


After setting the fixed text and a range of numbers to automatically
generate computer names for new computer accounts, you can associate
the new computer accounts with new computers logging in to the network.
Select any Target Computer and associate it with an Available Name.
Click Auto Assign to generate all listed target computers with all available
computer names.

View an example of the selected names that will be assigned to


each computer, for example: Marketing...Marketing6.

See also Computer Configuration Properties on page 111.


Use Token for
computer name

Select the checkbox to specify the computer name using tokens. Selecting this
option enables the Select Token combo box and disables the Define Range
option.
Note: This option is applicable for multiple computers and not for single

computers.

Select Token: You can select one of the six tokens from the drop-down list.
%NAME%- Complete computer name.

%NICyMACADDR%- MAC address of the computer with NIC specific


number. Selecting this option enables the NIC Number option. You need
to specify the NIC number, which ranges from 1-8.

%SERIALNUM%- Serial number from SMBIOS.

%NODENAME%- First 8 characters of actual computer name.

The NIC Number textbox is visible for NIC number input; the default value is 1.

TCP/IP Configuration Settings


Enter TCP/IP settings for one or more network adapters. Click Advanced to view
or setup IP interfaces, DNS, WINS, and static routes. For computer groups, click
Associate to assign a range of pre-defined IP addresses.

Altiris Deployment Solution Reference Guide

114

Chapter 5: Managing Computers

Computer Configuration Properties

Field

Description

Host name

The DNS name of a device on a network. The name is used to locate a


computer on the network.

Network Adapter

A list of all network adapters installed in the selected computer.


The network adapter with the lowest bus, device, and function number will be
the first listed (NIC0 - zero based). If the bus, device, and function
information cannot be determined for a network adapter, it will be enumerated
in the order it is detected.
When configuring multiple network adapters, make sure that one network
adapter is not using an Intel Universal NIC driver (commonly called UNDI
driver) to connect to Deployment Server. If one network adapter uses the
native driver and one uses an UNDI driver, then your computer will display
twice in the console.
Add. Enter new settings for additional network adapters installed on the
client computer.
You can add virtual network adapter settings to send a job to a computer
group containing computers with varying numbers of network adapters. If
a computer in the group has only one network adapter, then it will be
configured only with the IP settings listed first. If IP settings are provided
for additional network adapters not present in the computer, then they will
be disregarded.

MAC Address. The MAC address is a unique number assigned to the


network adapter by the manufacturer. You are unable to change this
number. The MAC address displays in this box when viewing computer
configuration settings. This box is shaded when creating a Modify
Configuration task.

DNS connection Suffix.

address.

Enter this to add domain suffixes to the root

Use DHCP to obtain an IP address.

DHCP server.

Assign a static IP address.

values.

Select this to obtain an address from a

Select this to set common static IP address

See also Computer Configuration Properties on page 111.


Reboot After
Configuration

To restart the computer after modifying configuration.

TCP/IP Advanced Options - IP interfaces


(Linux and NT type only). Click Add to view or set named interfaces for this network
adapter. Use this tab to view or add TCP/IP addresses to an existing network adapter card on Linux
or an NT type operating system.

IP Interfaces

Common IP Information

Field

Description

IP Address

Add or modify an IP address common to all interfaces.

Subnet mask

Enter the appropriate subnet mask.

Altiris Deployment Solution Reference Guide

115

Chapter 5: Managing Computers

Computer Configuration Properties

Linux Specific

Field

Description

Interface Name

Establish Linux-specific IP interface settings. Make sure you use the eth
syntax when naming new interfaces, for example: eth0:1 or eth0:new
interface.

Broadcast Address Enter the Broadcast address for the specified IP interface.
Interface State

The default value of the interface state is Up, which denotes that the named
interface is operating. You can shut down the named interface by selecting
Down.
See also Computer Configuration Properties on page 111.

TCP/IP Advanced Options - Gateway


Add a Gateway address for this network adapter. If using a static IP address, select the address and
click Add or Modify. Use the Up and Down arrows to move an address to the top of the list to set the
primary address.

TCP/IP Advanced Options - DNS


Add a DNS address for this network adapter. If using a static IP address, select the address and click
Add or Modify. Use the Up and Down arrows to move an address to the top of the list to set the primary
address.
DNS Server Address:

Add additional Domain Naming Servers (DNS) for this network adapter.

Add the name of the Domain Suffix, and then use the Up and
Down arrows to set the DNS suffix search order.

Append these DNS Suffixes (in order):

TCP/IP Advanced Options - WINS


Add a WINS address for this network adapter. If using a static IP address, select the address and click
Add or Modify. Use the Up and Down arrows to move an address to the top of the list to set the primary
address.
Add additional WINS settings for this network adapter. Select Enable or Disable NetBIOS over TCP/
or Use NetBIOS settings from DHCP server for this network adapter.

IP,

Note: Windows 95/98/ME operating systems do not allow editing this information. The Deployment

Console will disable the edit feature on those types of clients.

Altiris Deployment Solution Reference Guide

116

Chapter 5: Managing Computers

Computer Configuration Properties

TCP/IP Advanced Options - Static Routes


Field

Description

Destination

Enter the IP address of the destination Deployment Server.

Netmask

Enter the subnet mask.

Gateway

Enter the additional gateways required to reach the destination server.

Interface

Enter the IP address for the interface over which the destination can be
reached.

Metric

Enter the cost associated

Flags (Linux)

Enter the flag associated with a linux specific OS. Possible flags include:
U (route is up)
H (target is a host)
G (use gateway)
R (reinstate route for dynamic routing)
D (dynamically installed by daemon or redirect)
M (modified from routing daemon or redirect)
A (installed by addrconf)
C (cache entry)
! (reject route)

Ref (Linux)

Enter the number of references to this route.

Use (Linux)

Enter the count of lookups for the route.

NetWare Client Configuration Settings


Set Novell NetWare client values for a new or existing computer. Select whether
you want to log in directly to a NetWare server or to a NetWare tree in the Novell
Directory Service (NDS). You can then specify the preferred tree, server name,
and NDS context.

Field

Description

Ignore NetWare
settings

Select to disregard all Novell NetWare client settings for this computer.

Preferred server

Click and enter the name of the NetWare server, for example: \\OneServer.
This is the primary login server for the NetWare client.

Preferred tree

Click and enter the name of the NDS tree.

NDS User name

Click and enter the name of the user object for the NetWare client.

NDS Context

Click and enter the organizational unit context for the user.

Run login scripts

Select this option to run the NetWare client login scripts.


See also Computer Configuration Properties on page 111.

Altiris Deployment Solution Reference Guide

117

Chapter 5: Managing Computers

Deployment Agents

OS Licensing Configuration Settings


Enter or view the license information for your Windows operating system
software (Windows 95, 98, NT, 2000, XP, and 2003 Servers).

Field

Description

Registered user

Enter the name of the registered user.

Organization

Enter the name of the Organization.

License key

Enter the alpha-numeric license key. This is the hash value rendered from the
OEM key or 25-digit license key required when installing the operating
system.
See also Computer Configuration Properties (page 111) .

User Account Configuration Settings


Set up local user accounts for the newly imaged computer or when running a
configuration task. Enter a user name, full name, and password, then set standard
Windows login options.

Field

Description

User name

The user name for this local Windows user account.

Full name

The full name for this local Windows user account.

Password

The password for this local Windows user account.

Confirm Password Confirm the password for the local Windows user account.
Groups

Specify the Windows groups that this user will belong to as a commadelimited list, for example: Administrators, Marketing, Management

User must change


password at next
logon

Select to force the user to change the password after setting the configuration
properties.

User cannot change Prohibit the user from changing their password at any time.
password.
Password never
expires.

Select to maintain the user password.


See also Computer Configuration Properties on page 111.

Deployment Agents
The Deployment Agent is installed as the Production Agent to each client computer in the
Deployment Server System. This lets you remotely manage computers from the Deployment
Console and perform production tasks, such as run script, distribute software, get inventory, and
more.

Altiris Deployment Solution Reference Guide

118

Chapter 5: Managing Computers

Deployment Agents

The Automation Agent is installed to client computers so you can run deployment jobs with
Automation tasks, such as run script, create disk image, scripted OS install, and more.
You can install the Deployment Agent to client computers in the production environment, running
Windows or Linux, or PPC Handhelds or Thin Client devices running CE. NET.
See also Production Agent Settings (page 120) , and Automation Agent Settings (page 125) .

To set or modify Deployment Agent settings from the Deployment Server


Console
Right-click a computer or group and select Change Agent Settings.

Click Production Agent or Automation Agent.

To set or modify agent settings for new computers


Click Tools > Options.

Click Agent Settings. For handhelds, tap the Pocket PC Client icon in the
system tray and select Properties.

See
To view or modify settings at a Windows client computer
Right-click the Deployment Agent icon in the system tray.

Click Properties.

See

Deployment Agent Descriptions


The Deployment Agents reside on client computers and communicate with the Deployment Server.
The following table lists the agents and their description.
Deployment Solution Agents

Deployment Agent on Windows Runs on Windows computers, including desktops, notebooks,


thin clients, and servers. See Production Agent Settings on
page 120.
Deployment Agent on Linux

Runs on Linux workstations and servers. See Production


Agent Settings on page 120.

Automation Agent

This agent boots computers running Windows and Linux


operating system to Automation when a deployment job is
received. See Boot Disk Creator Help and Installing
Automation Partitions (page 142) .

Deployment Agent on Pocket PC Runs on the host computer for a handheld running the Pocket
PC operating system. See .Deployment Agents for Pocket
PC on page 127.
Deployment Agent on Pocket PC Runs on the handheld computer.
Deployment Agent on CE .NET

Runs on HP T5000 and Neoware Thin Client computer devices


running the CE .NET 4.2 and 5.0 operating system. See
Deployment Agent on CE .NET on page 129.

Notification Server Client

The NS client is an Altiris Agent that runs on computers


supported by Notification Server. This agent runs on the
Deployment Server computer when running Deployment
Solution on Notification Server.

Deployment Server Agent

Runs on the Deployment Server computer when running


Deployment on Notification Server.

Altiris Deployment Solution Reference Guide

119

Chapter 5: Managing Computers

Deployment Agents

To install the Deployment Agent to a newly added computer


When a Deployment Agent is installed on a computer, it will search across the network for a
Deployment Server to attach to. When a Deployment Server is located by the Deployment Agent,
then the client computer will be added as a record to the Deployment Database.

When the Deployment Agent is running on a computer, the user will see a small icon
in the system tray. When the icon is blue, then the client computer running the
Deployment Agent is connected to the Deployment Solution system.
When the Deployment Agent icon is clear, it shows that the client computer is not
connected to the Deployment Solution system. The agent may be configured
incorrectly, the Deployment Server is down, or other network problems exist.
Automatically update to newer version of Deployment Agent
At times, Altiris may update versions of the Deployment Agent to enhance features. For best
performance, it is suggested that all managed computers run the latest version of the Deployment
Agent. When a new version of the Deployment Agent is saved to the Deployment Share file server,
the managed computers will automatically update the Deployment Agent.
1

From the computer where Deployment Server is installed, click Start > Programs > Altiris >
The Deployment Server Configuration utility will open.

Deployment Solution > Configuration.

Click Options.

Click Transport.

Select the Automatically update clients option.

Production Agent Settings


You can set the default agent settings for new client computers so that when they are added to the
network, they will automatically find the Deployment Server and become
or modify properties settings for the Production or Automation Agent by, or the Automation Agent.
To set or modify agent settings in the Deployment Server Console for Windows or
Linux clients, right-click the computer and select Change Agent Settings > Production
Agent Settings.
To set or modify agent settings for the Deployment Agent, click Tools > Options.

Click the Agent Settings tab.

Select the Force new agents to take these default settings checkbox to set the
Deployment Agent setting for all new computers.

Click each agent setting tab to set properties.

Click OK.

To view or modify settings at a Windows client computer


Right-click the Deployment Agent icon in the system tray.

Click Properties.

When the Deployment Agent in the production environment is first started, the agent establishes a
connection to the Deployment Server using the following general steps:
1

The agent service is started and initialized.

A TCP socket is created.

A connection is made to the Deployment server.

The agent is updated, if required.

A basic inventory of the client is sent to the Deployment Server.

Altiris Deployment Solution Reference Guide

120

Chapter 5: Managing Computers

Deployment Agents

After the initial connection process is complete, no additional data needs to be sent to or from the
Deployment Server for the Deployment Agent to remain connected.
Note: If no Deployment Solution traffic is sent to the Deployment Agent, the TCP/IP protocols send

an occasional watchdog packet (approximately every 24 hours) to ensure that the connection is still
valid.

Changing Deployment Agent Properties from a


Client Computer
You can change the Deplyment Agent properies settings at a client computer that is currently
running the Deployment Agent. Do the following.

Right-click the Deployment Agent icon in the system tray.

Field Definitions
View status. Bring up the Altiris Client Service page to observe the current status of the Deployment

Agent. You can also see computer name, deployment server connected to, IP address, multicast
address, and MAC address. You can also watch Deployment Agent communicate with the
Deployment Server. Clicking the Properties button will allow you to edit the Deployment Agent
properties. Passwords will protect this option.

About. Display the version and licensing statement for Deployment Agent. Passwords have no effect
on this option.
View log file. View the Deployment Agent log file, if you have chosen the option to create a log file.

Passwords have no effect on this option.

Clear log file. Clear

the log file if one has been created.

Shutdown for imaging. Make an image of a computer without using a job. This will make the required
preparatory changes to the computer before an image is made. Failure to do this will break the
reconfiguration phase when deploying the image using a job. Passwords will protect this option
Change Name in Console. Change how this computer is listed in the deployment server console. This

option does not change the NetBios name of the computer or the name of the computer in the
database, but only changes the name of the computer displayed in the Computers window.
Passwords will protect this option.

Remove.

Uninstall Deployment Agent from the computer. Passwords will protect this option.

Exit. Stops all Deployment Agent services from running but does not uninstall Deployment Agent.
Deployment Agent will load normally the next time you boot the computer. Passwords will protect
this option.
User Properties.

Quickly go to the User Properties page to view or make changes. Passwords can
protect this option.

Admin Properties. Quickly go to the Admin Properties page to view or make changes. Passwords will

protect this option.

Show Network Interfaces. View what network cards are in your computer. Passwords will protect this

option.

Changing Deployment Agent Properties from the


Deployment Console
When you change the Production Agent properties from the Deployment Console, all computers
added to the Deployment system take on the settings as their default. However, you can change
Production Agent settings for a specificate client computer from either the Deployment Conosle or
at the client computer.

Altiris Deployment Solution Reference Guide

121

Chapter 5: Managing Computers

Deployment Agents

You can change the following Production Agent settings.


Production Agent Settings

Server Connection

Log File

Access

Proxy

Security

Startup/Shutdown

Server Connection
Connect directly to this Deployment Sever. Select this option so that the client receiving the

Deployment Agent will connect to the Deployment Server you selected to configure.

Address/Hostname.
Port.

Enter the IP address or NetBIOS name of the Deployment Server computer.

Enter the port number communicating with the Deployment Server.

Enable key-based authentication to Deployment Server. Select

this option to require that the client


computers that are trying to connect to the Deployment Server. This helps keep rogue computers
from connecting to unauthorized Deployment Servers.

Discover Deployment Server using TCP/IP multicast. Managed computers can use the multicast

address if they are on the same segment as the Deployment Server or if multicast is enabled on the
network routers. Ensure that the multicast address and port match those set up on the Deployment
Server. Try using defaults on both the client and Deployment Server if you are having problems
connecting.

Managed computers should use the Deployment Server IP address if multicasting is disabled on the
network routers or if they are not on the same network segment as the Deployment Server. The port
number must match the number set on the Deployment Server. Otherwise, your clients will not be
able to connect.
Server Name.
Port.

Enter the NetBIOS name of the computer running the Deployment Server.

Enter the port number distributing the multicast address.

Multicast Address. Enter

the group multicast address.

TTL. Specifies the number of routers the multicast request is allowed to pass through.Change this
setting if you need to find a Deployment Server that is more than 32 routers away (default setting)
or if to restrict the search to a smaller number of routers, making it easier to find the closest
Deployment Server.

Refresh connection after idle. Select the Refresh Connection after idle checkbox and then set the
refresh time by seconds, minutes, hours, or days. The Deployment Server will close the connection
after the specified time and immediately try to re-open the connection. This will force clients to
realize the network is down.

The default checking is of 28800 seconds or 8 hours. It is recommend keeping this setting above
28800. Do not set this option too low--reconnecting to the Deployment Server increases bandwidth
when connecting. If this option is set too low you can run into problems where it takes longer for
your clients to connect than to refresh their connections.
Abort files transfers if the rate is slower than. Preserve bandwidth on slower connections by

selecting this option, which will save bandwidth when running deployment tasks on slower
connections.

Access
Set these commands to control how the client handles requests from the server.
Allow this computer to be remote controlled. Select to allow the administrator to remote control the
selected computer. The default setting is to NOT allow the computer to be remote controlled.

Prompt the user before performing actions.

Altiris Deployment Solution Reference Guide

122

Chapter 5: Managing Computers

Deployment Agents

Shutdown and Restart. Select for the user to be prompted before shutting down or restarting the
computer. This feature overrides the Power Control option from the Deployment Server to Force
applications to shut down without a message.
Copy file and Run command. Select for the user to be prompted before running a program or executing

file copy commands


Remote Control.

Select for the user to be prompted before running the Remote Control commands.

You can set a default time before running or aborting the commands. Select the time for the user to
respond and then either continue with the operation or abort the operation.
Time to wait for user response. If one of the Prompt the user before perform actions is selected and the
user is not at the computer to respond, you need to decide whether to continue or abort. Select the
amount of time you want to wait for a response, and then select one of the following:

Continue the operation.

Abort the operation.

Click to continue without receiving a response from the user.

Click to not continue without receiving a response from the user.

Select when the Deployment Server is denied access to the Deployment Agent. Select the days and then
set the start and end times when access to the Deployment Agent is denied.

Security
This page lets you secure data between the Deployment Server and the Deployment Agent, or to set
a password so that the user on the client computer can only view and modify the User Properties of
the Altiris Client Settings on the managed computer.
Select to ALLOW encryption from this
managed client computer to the Deployment Server. This allows encrypted data transmissions
between the Deployment Server and the Deployment Agent on the client computer. If selected, then
the client computer can connect (but is not required to connect) using encryption.
Encrypt session communication with Deployment Server.

To enable encryption protocols, you must open the Deployment Configuration tool and select the
Transport tab. Select the Allow encrypted sessions with the servers checkbox to allow Deployment
Server to transmit using encryption protocols.
Require encrypted session with any servers. Select to require encryption between the managed client

computer and the Deployment Server. If this option is selected and the option to allow encryption in
the Deployment Configuration tool is not selected, then the Deployment Server will not
communicate with the Altiris Client on the managed client computer.

Note: Selecting encryption options will slow down the communication path between the agent and

the Deployment Server.

Select to allow users on the managed computer to


access the Admin properties only if they enter the set password. If the box is selected and the user
does not know the password, then they will only have rights to open the User Properties, which
includes only the User Prompts and Remote Control tabs on the Altiris Client Settings dialog box.

Password protect Admin properties from user.

Enter the password in the Password field and reenter the password for confirmation in the
field.

Confirm Password

Hide client tray icon. Select to hide the Altiris Client icon in the system tray of the managed computer.

If you hide the icon then you will be required to run AClient.exe -admin to view and modify the
complete administration properties from the managed client computer.

Log File
The Log File property page controls how data is logged and saved in a Deployment Server system,
allowing you to save different types and levels of information to the log files. You can save a text
file with log errors, informational errors, and debugging data using this dialog box.
If the log exceeds the specified size then older data will be dropped from the files. You can maximize
the size of the log file to save all selected data.

Altiris Deployment Solution Reference Guide

123

Chapter 5: Managing Computers

Deployment Agents

Save log information to a text file.

Click to save information to a log file.

File name. Enter the name and path of the log file. The default is to save the log file to the \Program

Files\Altiris\AClient\AClient.log file.

Maximum size.

Enter the maximum number of bytes for each log file.

Log errors.

Select this option to save only the errors returned when running a job or operation
between the Deployment Server and the Deployment Agent.

Log informational messages.

computer.

Select this option to save a list of procedural steps run on the client

Log debugging information. Select this option to list comprehensive debugging information in the text

file.

Use this tab to save the Deployment Agent log file. By default, the option Save log information to a
is cleared. Select it to enter a file name for the log and the maximum size for the log file.

text file

Note: If the log exceeds the specified size then older data will be dropped from the files, so it is
recommended to provide maximum file size.

Proxy
Typically, remote networks on the other side of a router or switch cannot receive multicast or Wake
On LAN packets from the Deployment Server. Setting the managed computer as a proxy client
computer will forward or re-create the multicast packets. A managed client computer set up as a
multicast proxy will simply act as a Deployment Server and advertise the servers name and IP
address through multicasting. Or you can set the managed computer as a proxy to send Wake On
LAN packets.
Set these options to control how the managed computer will act as a proxy agent, identifying the type
of traffic this managed computer will forward from the server.
Foward Wake-On-LAN packets.

packages.

Select if you want the managed computer to forward Wake on LAN

Forward Deployment Server discovery multicast packets. Select

if you want to advertise the


Deployment Server to client computers on another LAN segment or if the client computer is on the
other side of the router.

Send multicast advertisement every. Set the time by seconds, minutes, hours, or days for managed
computers send multicast advertisement.

Startup/Shutdown
Delay starting jobs after system startup. Set the time by seconds, minutes, hours, or days for managed

computers to delay jobs until after system startup.

Specify the Windows boot drive. Specify the drive that the client computer will boot from. The default

is C:

Force all programs to close when shutting down. Select this option to shut down applications when
using Power Control features. The user will still be prompted to Abort or Continue the shutdown.
Synchronize date/time with Deployment Server. Select this option to synchronize the system clock of
managed computers with the time of the Deployment Server.
Prompt for a boot disk when performing automation jobs.

while doing any automation jobs.

Select this option to prompt for a boot disk

Advanced
Disabled direct disk access for Deployment Agent for DOS (BootWorks) communication.

option to disable the direct disk access for Automation communication.

Altiris Deployment Solution Reference Guide

Select this

124

Chapter 5: Managing Computers

Deployment Agents

Deployment Agent on Linux


The Deployment Agent that is installed on Linux workstations and server is software that established
communications between Linux computers and the Deployment Server. The agent collects and
sends data from the client computer to the Deployment Server system, executes deployment tasks
sent from the server, installs packages, and runs management processes as directed from a
Deployment console. See Installing Deployment Agent on Linux (page 52) for additional
information.
A Linux computer is identified in the Deployment Console by unique Linux icons reflecting
deployment and process status, allowing you to deploy and manage computers just like the
Deployment Agent on Windows computers, with the following exceptions:
Supported Features of Client Software for Windows and Linux
Deployment Task

Deployment Agent on
Windows computers

Deployment Agent on
Linux systems

Create Disk Image

Yes

Yes

Distribute Disk Image

Yes

Yes

Scripted OS Install

Yes

Yes

Distribute Software

Yes

Yes

Capture Personality

Yes

No

Distribute Personality

Yes

No

Change Configuration

Yes

Yes

Backup Registry Files

Yes

N/A

Restore Registry Files

Yes

N/A

Run Script

Yes

Yes

Copy File

Yes

Yes

Shutdown/Restart

Yes

Yes

Automation Agent Settings


You can configure property settings for the Automation Agent for specified computers or computer
groups. You can remotely maintain important agent settings and update settings as required from the
Deployment Console.
To set or modify agent settings for a specific computer
From the Deployment Console, right-click a computer icon and select
Change Agent Settings.

Select Automation Agent.

To set or modify agent settings for ALL computers


Click Tools > Options, then click Agent Settings.

Select Force new Automation agents to take these setting.

Click Change Default Setting.

When a new client computer connects, it will receive the default agent settings from the Deployment
Server for drive mappings, authentication, and LMHost entries. Each client computer will still have
the capability to maintain its unique settings for the Automation Agent as it is defined when you
create new configurations, using Boot Disk Creator. The Automation Agent is installed as an
embedded (recommended) or hidden partition, or booted manually using one of Boot Disk Creators
creation methods. See Boot Disk Creator Help, and Installing Automation Partitions (page 142) .
See also Drive Mappings (page 126) , Authentication (page 126) , Network (page 126) .

Altiris Deployment Solution Reference Guide

125

Chapter 5: Managing Computers

Deployment Agents

Drive Mappings
Set drive mappings used by the Automation Agent to access hard disk image files and other packages
from a specified network drive. It is required that the F Drive be mapped to the Deployment Share.
You can also map other file server directories when storing large numbers of image files or
deployment packages.
Drive Mapping: By default, the mapped drive that displays is F: \\<Deployment Share server>\eXpress.
Click Add, Edit, or Remove to modify the mapping.

Note: You must select a shared folder for this field. The browse window lets you select any type of

folder, but the Automation Agent will only map to and access files from a shared folder.

Enter the path for the Deployment Share. The path you enter will map to the drive letter you
selected in the Drive field. You can also click Browse to navigate to the Deployment Share if you are
unsure of the directory path or if the image files are store on a file server.
Path:

Example:

Windows users:

NetWare users:

Linux users:

\\server\share

server\volume:directory

//server/mount point

See also Deployment Agents (page 118) , and Automation Agent Settings (page 125) .

Authentication
Provide the login credentials that the Automation Agent requires to map network drives. The
associated credentials for each network drive must have the rights that the Automation Agent
administrative rights to access files.
Domain/Workgroup. Enter the name of the Domain or Workgroup of the user that the Deployment
Agent for DOS will use to log on as to map the network drives.
User name. Enter the user name that the Automation Agent will use to log on to the server and shared

folder you defined on the Drive Mappings page.

Password.

Enter the password.

Confirm Password.

Enter the password again for confirmation.

See also Deployment Agents (page 118) , and Automation Agent Settings (page 125) .

Network
These settings lets you match the IP address with the computer name, as maintained in the LMHosts
file in the Automation partition.
1

Click Add.

From the Add LMHosts Entry dialog, enter the Computer Name that you want to associate with and
IP address.

Enter the IP address of the computer, using one of the following options.
Option 1:

Enter the IP Address.

Option 2:

Click the Lookup IP button. The IP address field automatically populate with the IP address
of the computer name you entered in the Computer Name field.

Click OK.

See also Deployment Agents (page 118) , and Automation Agent Settings (page 125) .

Altiris Deployment Solution Reference Guide

126

Chapter 5: Managing Computers

Deployment Agents

Deployment Agents for Pocket PC

Using the Pocket PC Agent, Deployment Solution manages handheld computers running the Pocket
PC operating system 2000 or later, and ARM processors.

To set or modify agent settings for the Pocket PC Agent on the host computer (to
manage in a cradle, attached cable, or wireless NIC), double-click the Pocket PC
Agent icon in the system tray. See Pocket PC Agent on page 128.
To set or modify agent settings on the Pocket PC Client on the handheld
computer, tap the Pocket PC Agent icon in the system tray of the handheld. See
Pocket PC Client on page 129.

Managing Handhelds from a Deployment Console


When a handheld has the Pocket PC Client installed, the handheld is installed in the Deployment
Server Database and displays as a unique computer in the Deployment Server console (see Viewing
Computer Details on page 107):

A blue arrow indicates an active connection for the handheld device.


A grayed icon indicates an inactive connection for the handheld device.
Like all other managed computer in the Deployment Server system, you can perform remote
operations on the handheld from a Deployment console (see Remote Operations Using Deployment
Solution on page 134) and inventory properties.
Gather and report inventory. Gather inventory information, such as applications, services, devices,
TCP/IP, hardware, and more.
View computer properties. Gather basic properties such as installed applications, devices, device

type, and basic configuration information.

Set configuration properties. Configure TCP/IP information and computer name. Many of the

normal configuration options do not apply to the Pocket PC.

File Copy. Download files to the local device file system. If the file transfer is interrupted, it will be
able to resume the file transfer where it left off.
Software Delivery. Send EXE files or CAB files to be launched or installed on the Pocket PC.
Time Synchronization. Synchronize the handhelds date and time with the Deployment Server.
Remote Control. Perform any task on the handheld from the Deployment Server Console as if you
were physically working on the handheld. Control a single client or group.
Reboot. Reboot HP iPAQs from the Deployment Server Console. At this time, this feature is

unavailable on other handhelds.

Name/Location/Email/Phone user settings. Set the owner information. If you choose the
advanced option in the console to prompt for these items, the user on the Pocket PC will not be
prompted, but instead the items will be taken from the owner information.

Not all management tasks are available when managing handhelds. These tasks are currently NOT
available for handhelds:

Altiris Deployment Solution Reference Guide

127

Chapter 5: Managing Computers

Create Quick Disk Image

Change Client Settings

Power Control

Deployment Agents

Note: The reboot option works on HP iPAQs, but not others.

If you select an unsupported task, you will receive an error stating that the feature is not available
for handhelds.
See also Connections to the Handheld on page 128, Pocket PC Agent on page 128, and Pocket
PC Client on page 129.

Connections to the Handheld


You can connect your handheld to a host computer using the connect cable and/or the cradle shipped
with your handheld device. Or if you have a network adaptor for your handheld, you can connect
directly with the Deployment Server from the handheld computer so it will be managed like any
other client computer on the network.
When you install the Pocket PC Agent (PA) on a host computer, it will automatically install the
Deployment Client on the handheld. This lets you run jobs and update inventory data when the
handheld is docked to the host computer. The Pocket PC Agent uses Microsoft ActiveSync on the
host computer to communicate between the Pocket PC Client (PC) on the handheld and the
Deployment Server. ActiveSync provides the IP stack that the Pocket PC Agent uses to
communicate with the handheld.

Many handhelds support direct network connections through a modem or LAN adapter. Handhelds
with a direct connection to the network can then be managed by Deployment Server. The Pocket PC
Client will first try to connect to a Pocket PC Agent. If that fails, it will try to connect directly to the
Deployment Server.
Important: The Pocket PC Client on a handheld using a cradle and ActiveSync 3.1 cannot directly
communicate with the Deployment Server and must use the Pocket PC Agent. However, if using
ActiveSync 3.5, the Pocket PC Agent is not required once the Pocket PC Client is installed. The
Pocket PC Agent is still useful for installing the Pocket PC Client onto the handheld, loading the
client, and managing client settings.

See also .Deployment Agents for Pocket PC on page 127.

Pocket PC Agent
You can configure the Pocket PC Agent settings on the host computer. For a list of command-line
options when executing the PPCAgent.exe, see Command-line options for the Pocket PC Agent in
Deployment Solution Reference Guide.
To view or configure the Pocket PC Agent properties
1

Double-click the Altiris Pocket PC Agent icon in the system tray of the host computer. The status
of the connection between the handheld and the host computer will be displayed.

Click Properties.

Altiris Deployment Solution Reference Guide

128

Chapter 5: Managing Computers

Deployment Agents

Select the General tab and modify settings.


Hide Tray icon. Select to not place the Pocket PC Agent icon in the host computers system tray.
If selected, you can view the status and properties windows by launching the ppcagent.exe
program in C:\Altiris\PPCAgent\PPCAgent.exe (default location).

Select the Transport tab and modify settings.


Pocket PC Agent Properties
Agent Port.

This is the port that the Pocket PC Agent is listening on for Pocket PC connections.
The agent port is updated each time the handheld connects.
Pocket PC Client Properties

Set server IP and port equal to AClient. If you are running from a cradle or cable, select this option.
Let me specify the server IP and port.

If the handheld is connected directly to the network, enter


the IP address of Deployment Server.

Set Pocket PCs server IP and port upon cradle connection. Select this option to assign the handheld

the entered IP address and port number each time the handheld connects through the agent.

Click OK.

The host computer may require you to restart.


See also .Deployment Agents for Pocket PC on page 127.

Pocket PC Client
You can the set properties on the Pocket PC Client program running on the handheld computer by
clicking the Pocket PC Client icon in the system tray.
To view or configure the Pocket PC Client properties
1

From the handheld, tap the Altiris Pocket PC Client icon in the system tray.

Tap Properties.

Tap the General tab and select if you want to synchronize time settings with Deployment Server.

Tap the Security tab to select options to be prompted before running actions on the handheld.

Tap the Transport tab to view or change settings (see settings details below).

Click OK.

To restart the Pocket PC Client


1

Tap Start > Programs > File Explorer.

Tap My Device.

Tap Windows > StartUp > AClient.

If the handheld is attached to the cradle, you can restart the Pocket PC Client by restarting the Pocket
PC Agent or by reconnecting the handheld to the cradle.
See also Deployment Agents on page 118.

Deployment Agent on CE .NET


Deployment Solution manages Hewlett-Packard T5000 series and Neoware thin client computer
devices, running the Windows CE .NET 4.2 and 5.0 operating systems. These computer devices ship
with the Deployment Agent for CE .NET already installed and displays in the Deployment Console
as managed computers when connected to the network.
The Deployment Agent performs the following limited tasks on the Window CE .NET platform:

Modify Computer Configuration (the computer name and TCP/IP Setting only)
Distribute software (.cab and .exe files)

Altiris Deployment Solution Reference Guide

129

Chapter 5: Managing Computers

Managing Client Connections

Execute and run scripts (DOS and WIN batch files) *no VBS support
Copy files and directories
Create disk images
Distribute disk images
Remote Control clients (24 bit color depth only. No chat or send file features)
Power Control (restart/shutdown/wake up jobs)
Set computer properties
Create conditions to run jobs and filter computers
Modify client properties via Windows and Linux agent settings

Additional features included with other Deployment Agents are not supported in the Deployment
Agent on CE .NET.
To install the Deployment Agent for CE .NET if deleted
If the Deployment Agent on CE .NET is deleted on the managed computer, it can be installed from
the Deployment Server \ Agents \ CEAgent folder in the Deployment Share.
From the managed computer you can then access the Deployment Share and launch the file to install
the agent. Example: type this command from the client computer:
\\<computer name>\express\Agents\CEAgent\CEClient_6.5.xxx.exe -install

Notes for Deployment Agent on CE.NET devices


The default image on a CE .NET Thin Client with 32 MB of flash RAM leaves 4 MB free disk space.
When trying to install an embedded automation package using the Distributing Software task, you
may get the following Error 112: Not enough disk space for package.

If you select Start > Settings > Control Panel > System > Memory tab and move the slider to allow
more than half of the memory to be allocated to Storage Memory, then you will be able to execute
a job that copies an embedded automation package to the \Temp folder on the CE .NET device
and execute a Windows Run Script task containing Start \Temp\<Embedded BootWorks
Package.exe>. This will install the Automation Agent and leave 1 MB of free disk space on
the device. If the slider shows less than half the memory available allocated to Storage Memory,
then Windows CE may not restart.

Another option for freeing up additional disk space is to uninstall the pre-installed HP
applications, allowing you to free up to as much as 10 MB of disk space. This lets you install an
embedded automation package through a Distribute Software task. Again, if the slider is not
placed around the middle of the Memory tab, then an Error 112 may occur.

See also Deployment Agents (page 118) .

Managing Client Connections


The following utilities are provided for managing transmissions between the Deployment Server and
Deployment Agents running on the managed client computers.
Reset a Client Connection
Resetting the connection that a managed computer has with the Server simply disconnects and
reconnects the computer. This is useful for troubleshooting or if you suspect there is a bad
connection.
To reset a client connection, right-click a computer and click Advanced > Reset connection. When the
computer disconnects, its icon will turn gray. The computer should then reconnect and its icon color
will return to its original active status color.

Altiris Deployment Solution Reference Guide

130

Chapter 5: Managing Computers

Computer Properties

Reject or Retrieve a Rejected Computer


If a computer that you do not want to manage connects to your Deployment Server, you can reject
it. This removes the unwanted computer from the Computers pane in the console. Further attempts
by the computer to connect will be denied. Although the computer is not deleted, any history or
schedule information associated with the computer is deleted.
1

Right-click the computer you want to reject from connecting to the Deployment Server.

Click Advanced > Reject Connection.

Click OK.

Rejected computers are stored in a Rejected Computers list. Select View > Rejected Computers to
view this list.
Accept a Previously Rejected Computer
If you now want to accept a previously rejected computer, you can retrieve it and reconnect it to the
Deployment Server.
1

Click View > Rejected Computers.

From the list, select the computer you want to retrieve.

Click the Accept Computer(s) button to remove the computer from the rejected list (this doesnt
delete the computer, just removes it from the list of rejected computers).

Click Yes to confirm the action, then click Close.

This client computer may now be managed from within the Computers pane. Connection requests
from this client computer will now be allowed.
See also Deployment Agents on page 118.

Computer Properties
View and edit the computer properties for each managed computer.

View and edit computer properties by double-clicking a computer icon in the


pane, or right-clicking and selecting Properties, or clicking the icon
in the toolbar.
Computers

General

Services

Hardware

Devices

Drives

Location

Network Configuration

Bay

TCP/IP

Lights-Out

Applications

Altiris Deployment Solution Reference Guide

131

Chapter 5: Managing Computers

Computer Properties

General
View or change the name of the computer as it displays in the console. You can
view the following: logged in user names, operating system installed, name of
the Deployment Server, whether or not an automation partition is installed,
version of the Altiris Windows Client, and other client information.
See also Computer Configuration Properties on page 111.

Hardware
View processor make and type, processor count, RAM installed on the
computer, display configuration, manufacturer, model, product name, MAC
address of each network adapter installed, serial number, asset tag, UUID, and
whether or not Wake On LAN and PXE are installed and configured.
See also Computer Configuration Properties on page 111.

Drives
View information about each drive on the computer. If you have multiple drives,
you can select a drive from the list box to view its settings, such as capacity,
serial number, file system, volume label, and number of drives installed.
See also Computer Configuration Properties on page 111.

Network Configuration
View Microsoft Networking, Novell Netware settings, and user information for
the selected managed client computer.
See also Computer Configuration Properties on page 111.

TCP/IP
View TCP/IP information, including a list of all installed network adapter cards
(up to eight) for the selected computer. Click Change to open the configuration
window allowing you to modify settings (see Configuring Computers on
page 137).
See also Computer Configuration Properties on page 111.

Altiris Deployment Solution Reference Guide

132

Chapter 5: Managing Computers

Computer Properties

Applications
View the applications that are installed on the computer, including description,
publisher, version number, product ID, and systems components.

See also Computer Configuration Properties on page 111.

Services
View the services installed on the computer as well a description, start type, and
path for each service.

See also Computer Configuration Properties on page 111.

Devices
View the devices installed on the computer, including display adapters, disk
drives, ports, storage volumes, keyboards, and other system devices.

See also Computer Configuration Properties on page 111.

Location
View and edit user-specific properties such as contact name, phone number, e-mail
address, department, mail stop, and site name. As the administrator, you can enter
this information manually or you can let the user populate this screen using Prompt
User for Properties.
See also Computer Configuration Properties on page 111.

Bay
View location information and other properties for Rack / Enclosure / Bay
components for high-density and blade servers. Set rules for automatic redeployment of blade servers based on physical location changes. This
property is available only to systems using blade servers.

Altiris Deployment Solution Reference Guide

133

Chapter 5: Managing Computers

Remote Operations Using Deployment Solution

Server Deployment Rules


From the Bay property page, you can select rules to govern actions taken when a new blade server
is detected in a selected bay. These rules are described below:
Rule

Action

Re-Deploy Computer

Restore a blade server using deployment tasks and configuration settings


saved from the previous server blade in the bay. This lets you replace new
blades in the bay and automatically run deployment tasks from its deployment
history. (See Restoring a Computer from its Deployment History on
page 136.)
All deployment tasks in the bay's history will be executed starting from the last
Distributing a Disk Image task or Scripted OS Install task, or from any script
(in a Run Script task) with this command: rem deployment start.

Run Predefined Job

The server will process any specified job. Select a job to run automatically
when a new server is detected in the bay.

Ignore the Change

This option lets you move blades to different bays without automatically
running jobs. The server blade placed in the bay is not identified as a new
server and no jobs are initiated. If the server existed in a previous bay, the
history and parameters for the server are moved or associated with the new
bay. If the server blade is a new server (never before identified), then the
established process for managing new computers will be executed.

Wait for User


Interaction

(default) No job or tasks are performed (the Deployment Agent on the server
blade is instructed to wait). The icon on the console changes to reflect that the
server is waiting.

See also Computer Configuration Properties on page 111.

Lights-Out
View information about the remote management hardware installed on the
selected computer (most often a server) used to power up, power down and
restart the computer remotely, or to check server status. You can also enter the
password for the remote management hardware by clicking Password.
Note: This feature is currently only available for selected HP Integrated Lights Out (ILO) and
Remote Insight Lights-Out Edition (RILOE) features.

See also Computer Configuration Properties on page 111.

Remote Operations Using Deployment Solution


The Operations menu in the Deployment console provides a variety of commands to remotely
manage all computers in your site or network segment. Some operation commands, such as Restore,
automatically create and schedule deployment jobs and place them in the Systems Jobs folder in the
Jobs pane. Other commands, like Chat or Remote Control, open utility programs to access and
remotely manage computers.

Open the computer operations menu by right-clicking a computer icon in the


Computers pane, clicking Operations on the menu bar, or clicking the icons in the
toolbar.

Altiris Deployment Solution Reference Guide

134

Chapter 5: Managing Computers

Remote Operations Using Deployment Solution

Computer Operations
Restore

Reconfigure your computer to a former state. Select from a list of


previous deployment tasks and select to restore only the ones you want.
See Restoring a Computer from its Deployment History on page 136.

History

View, print, delete, and save to file a history of deployment tasks. See
Viewing a Computers History on page 136.

Configure

Set network and local configuration properties for each computer,


including computer name, IP address, domains, Active Directory
context. See Configuring Computers on page 137.

Quick Disk Image

Select a computer and image its hard disk. This will create and store the
image to distribute now or later. See Quick Disk Image on page 137.

Power Control

Wake up, restart, shut down, and log off remotely. See Power Control
on page 137.

Remote Control

Open a remote control window directly to a selected client computer.


Investigate problems directly from your console. See Remote Control
on page 138.

Execute

Type and run commands remotely. See Execute on page 141.

Copy File to

Copy selected files, directories, or entire directory structures and send


them to the selected computer(s). See Copy File to on page 180.

Chat

Start an individual chat session with one or more selected client


computers. Communicate actions or query for symptoms during
administration. See Chat on page 141.

ADVANCED >
Clear Status

Clear computer status as shown in the title bar of the List View.

Prompt User for


Properties

Query the user for personal information. This feature sends a form to the
user to fill out. See Prompt User for Properties on page 142.

Reset Connection

Disconnect and reset the connection between Deployment Server and


the Deployment Agent on the selected computer.

Install Automations

Embed automation partitions onto the selected computers hard disk to


enable a managed computer to run automation tasks.

Get Inventory

Update property settings for a selected computer. These inventory


settings can be viewed in Computer Properties on page 131. Select it
to ensure that you have the latest inventory of the computer.
Set the timeout value in the General tab of the Deployment Server
Configuration utility (in the Control Panel).

Reject Connection

Refuse communication with the selected computer.

Install BIS Certificate

Install a BIS certificate for the selected computer.

Remove BIS
Certificate

Remove a BIS certificate from the selected computer.

Apply Regular License

Apply a permanent license if a client computer is using a time-limited


license or requires an updated license.

New Job Wizard

Open this to schedule deployment jobs for the selected computer. See
New Job Wizard on page 155.

New Group

Click to create a new computer group in the Computers pane.

New Computer

Create a new computer account. See Adding New Computers on


page 108.

Rename

Assign the computer or group a new name in the console. Right-click a


computer or group to edit in the Computer pane.

Delete

Delete a computer, a computer group, or any combination of computers


and groups from the database.

Altiris Deployment Solution Reference Guide

135

Chapter 5: Managing Computers

Remote Operations Using Deployment Solution

Computer Operations
Change Agent
Settings

Update property settings for the Deployment Agent running on selected


computer(s). See Deployment Agents on page 118.

Security

View security settings for the selected computer(s). See Security in


Deployment Solution on page 99.

Properties

View computer configuration and network properties. See Computer


Properties on page 131.

Restoring a Computer from its Deployment History


Occasionally it is necessary to restore a computer to its original settings based on operations or
deployment jobs previously executed on the computer. A computers past deployment history is
displayed in the Restore Computer dialog box, where you can restore a computer by selecting tasks
displayed from its history file. You can then rerun the deployment tasks to restore the computer.

Restore a computer by right-clicking a computer icon in the Computers pane and


selecting Restore, clicking Operations > Restore on the menu bar, or clicking the
icon in the toolbar. You can restore a computer using Remote Operations Using
Deployment Solution or by creating and scheduling a job using the New Job
Wizard.
1

Right-click a computer and click Restore.


The Restore Computer dialog box will open with a list of previous tasks with checkboxes.

Click the Show only list box and select only the type of tasks that you want displayed. Click the
Since list box to filter tasks by date. This is optional.

Click Next to view a summary of tasks selected to reschedule.

Click Next to schedule the job (See Scheduling Jobs on page 160).

Click Finish.

When you finish this computer operation, a new job displays in the Jobs pane of the Deployment
console under the System Jobs > Restoration Jobs folder. The job name will have a generic format of
Restore: <computer name>.
Viewing a Computers History
You can view a history of deployment tasks for a specific computer. Users who do not have
administrative privileges or the permissions to delete a computers history, will not have access to
this option.
1

Right-click a computer and click History.


The History of <Computer Name> dialog box will open with a list of previous tasks, including
when the task was scheduled, its deployment status and other deployment information.

Click Save As to save the file as a TXT or LOG file. This is optional.

Click Print to print the History file. This is optional.

Click Delete to delete the History file. Click Yes to the confirmation message.

Click Close.

See also Remote Operations Using Deployment Solution on page 134.

Altiris Deployment Solution Reference Guide

136

Chapter 5: Managing Computers

Remote Operations Using Deployment Solution

Configuring Computers
From the Operations menu you can enter and modify configuration settings for computers. See
Computer Configuration Properties on page 111 for complete information about configuration
settings.
1

Right-click a computer and click Configure.


The Computer Configuration Properties dialog box will open.

Set basic configuration values in the General configuration group (default view).

Click other configuration group icons in the left pane to set additional values.

Click OK.

See also Remote Operations Using Deployment Solution on page 134.

Quick Disk Image


This computer operation creates a disk image of the selected computer. This option is a quick and
easy way to create a disk image of a selected managed computer from the Deployment console.
To run a disk image job you must have an automation partition installed on the client computer, or
it is PXE-enabled and can boot to automation by connecting to a PXE Server.
1

Right-click a computer and click Quick Disk Image.


The Schedule Computers dialog box will open. See Scheduling Jobs on page 160.

Schedule the job to run immediately or at a later time. You can also click the option to not
schedule the job (this option places the job in the working area and will not run until you
manually drag it to a selected computer and reschedule it).

Click OK.
When you finish this computer operation, a new job displays in the Jobs pane of the Deployment
console under the System Jobs > Image Jobs folder. The job name will have a generic format of
Create Image: <computer name>.

See also Remote Operations Using Deployment Solution on page 134.

Power Control
This computer operation lets you wake up a computer, restart a computer, shut down, or log off as
the current user for a selected managed computer. You can also power a computer on if Wake-OnLan is supported.

Restore a computer by right-clicking a computer icon in the Computers pane and


selecting Power Control, clicking Operations > Power Control on the menu bar, or
clicking the icon in the toolbar.
1

Right-click a computer and select Power Control.


A secondary menu will open with these options:

Altiris Deployment Solution Reference Guide

137

Chapter 5: Managing Computers

Remote Operations Using Deployment Solution

Power Control options

The Wake Up feature is hardware-dependent and is only available for inactive


computers. Select this command to start a computer that has been turned off.

Wake up

Notes:

Your operating system and network adapter must be capable of recognizing


and processing the wake-on-lan packets. Non-embedded network adapters
must be properly configured. Example: 3Com NICs have an extra header
cable that enables Wake on LAN. Check the documentation that came with
your network adapter for more information about Wake-on-LAN.
For NICs and operating systems that support Wake-on-LAN Power
Management features, you need to go to Properties of the network adapter
driver and select the Power Management tab. Click the Allow this device to bring
the computer out of standby option for this device to bring the computer out of
standby status.
Note: Some computers have to enable this feature in their BIOS.
Restart...

Click to reboot the selected managed computer. Select Force Applications to


close without a message box to restart immediately without prompting the user.

Shut down...

Click to shut down the selected managed computer. Select Force Applications
to shut down immediately without prompting
the user.
to close without a message box

Click to log off of the selected managed computer. Select Force Applications
to close without a message box to log off immediately.

Log off...

Select a Power Control option. A Confirm Operation dialog box will open. Select the Force
application to close without a message box to shut down users without a warning. If you do not
select Force application to close without a message, the user will be prompted to save any work
before the power operation is continued.

Click Yes.

See also Remote Operations Using Deployment Solution on page 134.

Remote Control
Remote Control is a computer management feature built in to the Deployment Server Console. It lets
you control all types of computers to view problems or make immediate changes as if you were
sitting at the managed computers screen and using its keyboard and mouse.

When a managed computer is being remote controlled, the Deployment Agent


icon in the managed computers system tray flashes alternate icons.
Remote Control also provides Chat, Copy File to, and CTRL+ALT+DEL features
to assist in administrating managed computers from the console.

Note: You cannot disable the flashing eye icon while the computer is being remote controlled.

Before you can remote control a managed computer:

The managed computer must have the Altiris Agent for Windows installed and properly set up.

The client must have the appropriate Proxy option checked in Altiris client properties.

The client and Deployment Server Console must be able to communicate to each other through
TCP/IP.

Altiris Deployment Solution Reference Guide

138

Chapter 5: Managing Computers

Remote Operations Using Deployment Solution

To remote control a managed computer


1

Right-click a computer and click Remote Control.


This opens the Remote Control window displaying the managed computers screen.
Note: If the selected managed computer does not allow a remote control operation, you can

change this client setting using the Remote Control options in the Change Agent Settings
command. The default setting is to not allow remote control of the managed computer. See
Deployment Agent Proxy on page 124 options.
2

From the Remote Control window you can execute the following commands:

Remote Control options

Toolbar
Chat

Click to open a chat session with the selected managed computer. This starts
a chat session between the console computer and the managed computer. The
chat session opens a chat window that lets you send messages back and forth
between the Console and the managed computer. If you are controlling
multiple computers in a single window and start a chat session, the chat
session is only between the Console and the master client.

Refresh

Click to update the screen view of the managed computer.

CTRL+ALT+DEL

Click to select restart or logon options for the managed computer.


Note: The managed computer must be running Windows NT/2000/XP/2003
and have the keyboard and mouse driver installed for this feature to be
available.

Send File

See Send Files during Remote Control on page 139.

Toggle Control

Click to change between control access of the managed computer (default) or


view access only of the managed computer.

Control menu
Disable Input from
the Client

Click to prohibit the user of the managed computer from using the keyboard
or mouse during the remote control session.

Close Window

Click to close the remote control window of the managed computer.

View menu
Refresh

Click to refresh the view of the screen.

Fit to Window

If this option is selected, the client display image becomes the same size as the
Remote Control window. If not, the image is the size of the client display.

Color Depth

See Remote Control Properties on page 140.

Properties

See Remote Control Properties on page 140.

To end a Remote Control session, click Control > Close Window in the Remote Control window.

Send Files during Remote Control


Click to send files to the managed computer being remotely controlled. Enter the name of the source
file to be copied and the destination path on the managed computer. Select required compression and
encryption options.
If you are controlling multiple clients within a single window, this dialog will send a file to the
master client only.
Source filename.

Enter the name of the file to be sent.

Destination path.

Enter the path where you want the file to reside on the managed computer.

Compress Data.
Encrypt Data.

Select to compress the file during the copy process to decrease network traffic.

Select to encrypt data package for security.

Altiris Deployment Solution Reference Guide

139

Chapter 5: Managing Computers

Remote Operations Using Deployment Solution

You can also drag entire folders from the Console computer to the remote control window, which
will copy the files to the remote client computer.

Remote Control Properties


Color Depth. Click to specify the color depth (number of colors) used by the Remote Control window.

This setting applies only to the Remote Control window at the console, not the display of the
managed computer. There is no benefit to setting a color depth on the Remote Control window
greater than that of the managed computer. The benefit of lower colors is improvement in speed.

Use specific image resolution.

client display.

Click to specify the width and height of the image that represents the

Update interval. Select to specify how often the image in the Remote Control window is updated (in
milliseconds). The more frequently the display is updated, the more bandwidth is required.
Only update foreground window.

session.

Select to refresh only the selected window in the remote control

Set Remote Control Permissions


Deployment Solution provides multiple features for ensuring privacy and security when a managed
computer is remotely controlled. Before a managed computer can be remotely controlled, the
Remote Control preferences on the Deployment Agent for Windows must be set to allow remote
control access.
You can also lock the keyboard and mouse of the managed computer or provide a message to the
user asking for permission to initiate a remote session. This provides an opportunity for the user to
allow or reject the request. In certain environments, such as a lab or classroom, using a prompt to
ask for permission might not be preferred.
To remotely set security options on each managed computer, use Change Agent Settings from the
console or open Properties on the Deployment Agent on the client computer (you must access Admin
properties).
1

After opening the Deployment Agent property page, select the Remote Control tab.

Select Allow this computer to be remote controlled to provide access from the Deployment Server
Console.

To lock the user from using the keyboard and mouse during a remote control session, select the
Enable NT keyboard and mouse driver box. This is optional.
This option works only on Windows NT/2000/XP/2003.
Important: After selecting this option (either enabling or disabling the keyboard and mouse) you

must restart the managed computer. This can be done using a Power Control operation.

If you want the user to be prompted before a remote control session begins, click the User
Prompts tab.
a

Under the Choose the commands you would like to be prompted before executing options, select
the Remote Control commands option.

Specify the number of seconds that you want the prompt to wait. Also, specify what will
happen after the prompt time is up. Click either Continue the operation or Abort the operation.

Click OK.

Start Multiple Sessions


You can manage multiple computers using the Remote Control feature. However, the more
computers you include in the session the larger the bandwidth over the network.

Open a separate Remote Control window for each managed computer. Right-click each
computer and select Remote Control. A new window will open for each selected computer.

Open a Remote Control window for a group of managed computers. Right-click a computer
group icon and select Remote Control.

Altiris Deployment Solution Reference Guide

140

Chapter 5: Managing Computers

Remote Operations Using Deployment Solution

The Remote Control Options dialog box will open with options to Control each client separately in
its own window or to Control all clients together. If you select to control clients separately, then
individual windows will open for each computer. If you select to control clients together, then
you will be asked to select a master computer.
The master computer is the computer that displays in the Remote Control window, however all
actions taken from the console will also run on the other computers in the group. All computers
in the group should be similar in configuration to work properly.
Note: If you are controlling multiple computers in a single window, you can send a file only

between the console and the master client. If you want to send a file to multiple clients at the
same time, use the Copy File to feature (see Copy File to on page 180.)

To end a Remote Control session, click Control > Close Window.

See also Remote Operations Using Deployment Solution on page 134.

Execute
Send a command from the Deployment console as if you were entering a command from the
command-line prompt on the client computer.

Execute a command to a client computer by right-clicking a computer icon in the


pane and selecting Execute, clicking Operations > Execute on the
menu bar, or clicking the icon in the toolbar.

Computers

Type a command that you would like executed on the remote computer(s) selected, or select from
a list of previously run commands. Example: type regedit to open the Registry on the
computer.

To run the command as another user on the managed computer, click the User button and enter
the user name and password.

User Account
Use this dialog to run a script using another local user account. You can log in with another user
name and password with rights to run an execute command.
Run with default security credentials.

default option.

Run with the following credentials.

This option runs with the current user credentials. This is the

Click this option to log on with another user name and password.

See also Remote Operations Using Deployment Solution on page 134.

Chat
You can communicate with managed computers using the Chat text messaging system. From the
Deployment Server Console, select an individual computer or a group of computers to open an
individual chat session with each logged-in user.

Open text messaging with a user by right-clicking his or her computer icon in
the Computers pane and selecting Chat, or clicking the icon in the Remote
Control window.
1

Open a chat session. The Chat with <computer name> window will open identifying the computer
you are sending messages to.

Type a message in the lower text box.

Altiris Deployment Solution Reference Guide

141

Chapter 5: Managing Computers

Remote Operations Using Deployment Solution

Click Send or press <Enter>.


The exchange of text messages displays in the upper text box.

See also Remote Operations Using Deployment Solution on page 134.

Prompt User for Properties


This feature allows an administrator to prompt a user for computer location and user information.
The information supplied in this form displays in the Location properties in the Computer Properties
dialog.
To prompt a user for location properties
1

In the Computers pane of the Deployment Server Console, right-click a computer and click
Advanced > Prompt User for Properties. You can also select a computer and click on the Prompt
User for Properties icon in the toolbar or click on Operations > Prompt User for Properties.
A dialog box will open in the Deployment Server Console with a list of properties.

Select the properties to prompt the user. The properties selected in this dialog box will be active
on the property form sent to the user, allowing the user to type information for the selected
properties.
Note: All properties will be selected by default; you must deselect the properties you dont want

included when the client is prompted.

Click OK.
The properties form displays for the logged-on user of the computer, asking for location
properties.

When the user enters information and selects OK, the Location properties in the computer
properties fields will be updated for the selected computer. If the user changed the computer
name, then the name in the Computers pane of the Deployment console will also change. These
settings are stored directly to the Deployment Database.
See also Chat on page 141 and Remote Operations Using Deployment Solution on page 134.

Installing Automation Partitions


When the Deployment Server sends a deployment job to client computers, tasks within the job can
be assigned the default automation pre-boot environment, or one of DOS, Linux, or Windows PE.
The embedded (recommended) or hidden automation partition you install to the client computers
hard disk contains the Automation Agent, which connects to the Deployment Server and receives
deployment jobs automatically when in the automation environment.

Altiris Deployment Solution Reference Guide

142

Chapter 5: Managing Computers

Deploying and Managing Servers

You can have multiple tasks within a deployment job, and each task can be assigned to run in a
different automation environment, depending on the task and end result you want. The following list
are automation tasks that you can add to deployment jobs.

Run script
Create disk image
Distribute disk image
Scripted OS install
Backup Registry
Restore Registry

During the Deployment Server installation, the Pre-boot Operating System page displays for you to
select a default pre-boot operating system, which is used by Boot Disk Creator to create the
configurations that boot client computers to automation. You can install additional pre-boot
operating system files through Boot Disk Creator. See Boot Disk Creator Help.
If you are running PXE Servers, you do not need to install an automation partition on each client
computers hard disk. When the Deployment Server sends a deployment job, PXE-enabled client
computers search for a PXE Server to receive the boot menu options and the boot menu files that are
required to boot to automation. See Automation Pre-boot Environment in the Deployment Server
Reference Guide.
To install an automation partition
1

Right-click a computer and click Advanced > Install Automation Partition.


Note: All pre-boot operating system types are displayed regardless of what has been loaded into
Deployment Server through the Boot Disk Creator. If a pre-boot operating system type is
selected that is not installed, the server attempts to create the install package, but then fails. The
following error is displayed: "The OS and hardware type are supported but the files have not
been gathered by the user".

Select the pre-boot operating system environment you want to install from the drop-down list.

Click OK.
The Automation Agent you selected installs as an embedded partition on the client computers
hard disk. After the installation completes, the client computer reboots automatically. You can
now run automation-specific deployment tasks this computer.

See also

Change Agent Settings


This feature lets you modify most of the agent settings for a selected computer or computer group.
You can set properties for the Production Agent (Deployment Agent), or for an Automation Agent.
To change agent settings
1

From the Computers pane, right-click a computer and select Change Agent Settings.

Select either Production Agent or Automation Agent.

Edit the properties settings.

Click OK.

Deploying and Managing Servers


Deployment Solution provides additional features to remotely install, deploy and manage network
and web servers. From the Deployment Server Console, you can configure new server hardware,
install operating systems and applications, and manage servers throughout their life cycle. And
because servers are mission-critical, you can set up a system to quickly deploy new servers or
automatically re-deploy servers that have failed. Features like rules-based deployment, support for
remote management cards, and quick server restoration from a deployment history give you new
tools to manage all servers throughout your organization.

Altiris Deployment Solution Reference Guide

143

Chapter 5: Managing Computers

Deploying and Managing Servers

Servers are identified in the Computer pane with distinctive server icons. Like all
managed computer icons, the icons change to identify the status and state of the
computer, such as user logged on or Server Waiting.
Note: Servers are recognized by their operating system (such as Windows 2000
Advanced Server, Windows Server 2003, or any Linux OS), multiple processors, and
specific vendor server models.
Manage Servers from the Console. The Deployment Server Console includes features specifically
designed for deploying and managing servers, such as enhanced task logging and history tracking
features to let you recall administrative actions and quickly redeploy mission-critical servers.
Set Server-specific options. Servers are essential to any organization and require special planning
and management strategies. Deployment Server provides server-specific features to automatically
deploy new servers and maintain existing servers. See Server Deployment Options on page 145.

Server Management Features


Deployment Server provides various features for deploying and managing servers. These features
are supported for client and handheld computers as well, but are essential in deploying servers.
Server icons. The Deployment consoles display icons to identify servers across the network. Like
other computer icons in the console, server icons can be selected to view server properties or assign
specific jobs and management tasks

Icon

Description
Indicates a server is active and a user is logged on.

Indicates a server is disconnected from the console.

Indicates a server is in a waiting state.


Run Scripted Installs. Execute scripted, unattended installs across the network for both Microsoft
Windows and Linux servers. Follow steps to create answer files and set up OS install files using a
wizard. See Scripted OS Install on page 167.
Support for multiple network adapter cards. Because servers may require more than one network

interface card, Deployment Server provides property pages to access and configure multiple network
adapters remotely from the console. See TCP/IP Configuration Settings on page 114.

Synchronized server date and time. Deployment Server automatically sets the servers date and
time after installing or imaging (as part of the configuration process). Deployment Agents include
an option to disable this feature (it is off by default).
Enhanced scripting capabilities. You can deploy multiple tasks per deployment job and boot to
DOS multiple times when configuring and deploying a clean server. Deployment Server also lets
you view and debug each step in the deployment script, and track each job to provide a history of
tasks for redeploying a server.

Altiris Deployment Solution Reference Guide

144

Chapter 5: Managing Computers

Deploying and Managing Servers

Server Deployment Options


Deployment Server includes features to automatically reconfigure and redeploy new servers. If you
are using Initial Deployment to automatically re-image new servers or run installation scripts, you
can (1) safeguard against mistaken disk overwrites, or (2) run automatically for every server not
identified as a managed computer in the database. These contrasting settings are based on polices
that you define for managing servers in your organization.
Example: if you rely on PXE to boot the new server and you want to deploy new servers
automatically without halting the process, you must change the default settings in the PXE
Configuration Utility. In contrast, if you want to ensure that the server waits before being deployed
(or waits a set time before proceeding) to avoid erroneous re-deployment, you need to set the options
in the Advanced section of Initial Deployment.
Halt the Initial Deployment of Servers
When a server boots from the PXE server or from Automation (if the option is set), Deployment
Server recognizes it as a new computer and will attempt to configure the computer with Sample Jobs
in Deployment Solution. Initial Deployment includes a feature to prohibit servers from being
deployed automatically.
1

Click Initial Deployment and select Properties.

Click the Advanced tab.

Click the Servers checkbox and click OK.

Initial Deployment will not run for any computer identified in the console as a server.
Change PXE Options for Initial Deployment
If installing a server using a PXE Server, the server will attempt to install but will not run
automatically using default settings. It will wait until a boot option is selected from the client
computer. You can change the default setting in the PXE Configuration Utility to allow Initial
Deployment to run automatically and not sit at the prompt.
1
2

Click on Start > Programs > Altiris > PXE Services > PXE Configuration Utility.
Click the DS tab.

Select a pre-boot operating system from the Initial Deploy boot option drop-down list.

Click Execute Immediately.


Initial Deployment will run automatically for every identified server.

Click Save.

Click OK.

Clear BootWorks Prompt for Remote Install


When you run a deployment job on a computer where the Deployment Agent has been remotely
installed, a message displays stating that no BootWorks partition or PXE stamp is found. The
message will stay open until the user clicks OK on the message dialog, which delays executing the
scheduled job as part of an automated redeployment process. To fix this delay:
1

Select Tools > Options.The Altiris Program Options dialog will open.

Select the Agent Settings tab.

Select the Change Default Settings button.

Select the BootWorks tab.

In the lower section, select Never prompt me from the list.

Altiris Deployment Solution Reference Guide

145

Chapter 5: Managing Computers

Deploying and Managing Servers

Click OK.

Following these steps will assure that the BootWorks message will not come up and things will move
forward when a job is scheduled.

Managing Server Blades


Deployment Solution lets you manage high-density server blades with Rack/Enclosure/Bay (R/E/B)
hardware and properties. From the Deployment Console you can deploy and manage these spaceefficient server blades using the physical view to assign jobs to the Rack, Enclosure, or Bay level of
the server cluster, or you can manage each server blade directly from the logical view. See Bay on
page 133 for properties and rules to deploy Rack/Enclosure/Bay servers.

Using Deployment Solution, you can employ rip and replace technology that lets you insert a new
server blade and automatically configure and deploy it exactly like the previously installed server
blade, allowing you to replace any downed server and get it back on line quickly. Altiris provides
fail-safe features to ensure that no server is mistakenly overwritten and ensures that all disk images,
software, data, and patches are applied to the new server from the history of jobs assigned to the
previous server blade.

Managing New Server Blades


Deployment Solution lets you automatically deploy, configure and provision new server blades
using a variety of features, including Sample Jobs in Deployment Solution, and Server Deployment
Rules.
New Server Blades in Newly Identified Bays
When new blades are identified in a Bay that has not been used previously (if it has been used
previously then the Bay object will be identified in the physical view), then both the Initial
Deployment and Virtual Bays features can be set up to automatically run configuration tasks and
deployment jobs.
To Create Virtual Bays: Set up Virtual Rack/Enclosure/Bays for Hewlett-Packard Rapid
Deployment Pack installations of Deployment Solution.
Initial Deployment set up: Clear the Servers checkbox in the Advanced dialog box.
If both new computer features are set up and a new server blade is installed in a Bay not previously
identified by the Deployment Server, then the Create Virtual Bay feature will execute and Initial
Deployment will not execute.
New Server Blades in Identified Bays
If a new HP server blade is installed in an identified Bay (one that has already had a server blade
installed and is visible from the Deployment Console), then both Sample Jobs in Deployment
Solution and Server Deployment Rules can be set up. However, when both are set up then the Server
Deployment Rules will execute and Initial Deployment will not execute.

Virtual Bays
Hewlett-Packard blade servers now have a Virtual Bay feature that lets you pre-assign deployment
jobs to the Rack, the Enclosure, or to a specific blade server in the Bay. Any HP blade server can
have predefined deployment jobs and configuration tasks associated with it to execute automatically
upon installation. (This feature requires that the Hewlett-Packard Rapid Deployment Pack is
installed.) The Virtual Rack/Enclosure/Bay icons will change from virtual icons to managed server
icons in the Deployment console as live blade servers are inserted and identified by Deployment
Solution.
Rack name.

Enter or edit the name of the Rack.

Enclosure name.

Enter or edit the name of the Enclosure.

Altiris Deployment Solution Reference Guide

146

Chapter 5: Managing Computers

Enclosure type.

Deploying and Managing Servers

Select the type of HP server blade from the list.

Initial Job. Select an existing job to run when the pre-configured computer account is associated with
a new server blade.
Server Change rule. Select the Server Deployment Rules to run on the Bay when a new server blade

is installed.

Note: If you create Virtual Bays for an enclosure (such as the BLe-class with 20 bays) and then if

another model of server blade with an enclosure containing fewer bays is connected (such as the
BLp-class with 8 bays), then the excess virtual bays will be truncated automatically. Conversely, if
you create Virtual Bays with fewer bays (8) and then install an enclosure with additional bays (20),
you will need to recreate the virtual bays in the enclosure (right-click the enclosure name in the
physical view and click New Virtual Bays).

See also Managing New Server Blades on page 146.

Hewlett-Packard Server Blades


Hewlett-Packard high-density blade servers can be deployed and managed from the Deployment
console. The following HP server blades are supported:
HP Proliant BL e-Class

HP Proliant BL p-class

Proliant BL 10e

Proliant BL 20p

Proliant BL 10e G2

Proliant BL 20p G2
Proliant BL 40p

HP blade servers allow you to employ all features provided in the Deployment Console when you
install the HP Proliant Essentials Rapid Deployment Pack (see www.hp.com/servers/rdp), including
the Virtual Blade Server feature. The name of each Rack for an HP Server is displayed along with
the assigned name for the Enclosure and Bay. These names are collected from the SMBIOS of the
server blade and displayed in both the physical and server views within the Computers pane of the
Deployment console.
For HP blade servers in the physical view the Rack name can be a custom name in the console, with
all subordinate Enclosures and Bays also identified. Example:
<rackName>
<enclosureName>
<bayNumber>

See also Server Management Features on page 144 and Server Deployment Options on
page 145.

Dell Server Blades


Dell high-density blade servers can be deployed and managed from the Deployment console. All
Dell Rack Servers are supported by Deployment Solution, but the server blades can also be managed
from the physical view in the Rack/Enclosure/Bay view. The following servers are supported:
Dell Rack Servers

Dell Server Blades

All PowerEdge rack servers

PowerEdge 1655MC

For Dell blade servers in the physical view, the Rack name will always be Dell. All subordinate
Enclosures and Bays are identified with custom names under the Dell rack name. Example:
Dell
<enclosureName>
<bayName>

Altiris Deployment Solution Reference Guide

147

Chapter 5: Managing Computers

Find a Computer in the Database

See also Server Management Features on page 144 and Server Deployment Options on
page 145.

Fujitsu-Siemens Server Blades


Fujitsu-Siemens high-density blade servers can be deployed and managed from the Deployment
console. All Fujitsu-Siemens Rack Servers are supported by Deployment Solution, but the server
blades can also be managed from the physical view in the Rack/Enclosure/Bay view. The following
servers are supported:
Fujitsu-Siemens Rack Servers

Fujitsu-Siemens Server Blades

All Primergy rack servers

Primergy BX300 blade servers

For Fujitsu-Siemens blade servers in the physical view, the Rack name will always be FujitsuSiemens. All subordinate Enclosures and Bays are identified with custom names under the FujitsuSiemens rack name. Example:
Fujitsu-Siemens
<enclosureName>
<bayName>

See also Server Management Features on page 144 and Server Deployment Options on
page 145.

IBM Server Blades


IBM high-density Blade Centers can be deployed and managed from the Deployment console. All
IBM blade servers are supported by Deployment Solution, but the server blades can also be managed
from the physical view in the Rack/Enclosure/Bay view.
For IBM blade servers in the physical view, the Rack name will always be IBM. All subordinate
Enclosures are identified with custom names under the IBM rack name and Bays are identified by
number. Example:
IBM
<enclosureName>
<baynumber>

See also Server Management Features on page 144 and Server Deployment Options on
page 145.

Find a Computer in the Database


This search filter lets you type a string and query specified database fields for specific computer
properties. You can search for user or computer names, licensing or location information, or primary
lookup keys: MAC address, serial number, asset number, or UUID. This search filter queries
property values displayed in the Computer Properties on page 131 pages.

Click <CTRL> F or click the Find Computer button on the console toolbar to
search the Deployment Database for computers by property settings.
The search begins at the top of the computer list and highlights the computer
name in the Computers pane when a match is found. Press F3 to find the next
computer that matches the search criteria until there are no more results, or the
end of the computer list is reached.
1

In the Search For box, type all or part of the computers property values that you would like to
search for. This alpha-numeric string will be compared with specified database fields.

In the In Field box, select the field that you want to search in the Deployment Database.

Altiris Deployment Solution Reference Guide

148

Chapter 5: Managing Computers

Using Lab Builder

Example: to find a computer by searching for its IP address, type the address in Search For field
and then select IP Address from the In Field drop down list.

Name

BIOS name of the computer.

Computer Name

Deployment Solution name of the computer.

MAC Address

0080C6E983E8, for example.

IP Address

192.168.1.1, for example.

ID

The computer ID. 5000001, for example.

Serial Number

Serial number installed in BIOS. A primary lookup key.

Asset Tag

Asset number in BIOS. A primary lookup key.

UUID

A primary lookup key.

Registered User

Name entered when OS was installed.

Product Key

Product Key for the operating system.

Logged On User

Name of user currently at the computer.

Physical Bay Name

The actual bay number: 7x, for example.

The computer you are looking for will be displayed and highlighted in the Computers window in the
console.
Note: This search is not case-sensitive and allows wildcard searches using the *.

See also Computer Filters and Job Conditions on page 94.

Using Lab Builder


Use the Lab Builder to set up jobs under the Lab folder in the Jobs pane to set up a classroom or lab
environment.

Click the Lab Builder button on the console toolbar or click File > New > Lab
Builder to set up jobs specifically created for managing multiple computers in a
lab environment.
You can set up jobs to:

Create Disk Image

Deploy Lab

Restore Lab

Update Configuration

Upload Registries

Each of these jobs contains a default list of tasks. Lab Builder places these five new jobs under a
folder (which you name) located under the Lab folder. All of the tasks in the jobs have been assigned
default paths and file names that allow them to use the same images and configuration information,
registry data, etc. It is suggested that you do not change the file names and paths. If you change the
default settings (example: changing the image name), you must change it in all of the jobs where the
image is used.
To use Lab Builder
1

Click the Lab Builder icon on the toolbar, or choose File > New > Lab Builder.

Enter the name of the lab setup.

Altiris Deployment Solution Reference Guide

149

Chapter 5: Managing Computers

Using Lab Builder

Note: The lab name must be unique because the program creates a default image file name based

on the name, and the image file name must be unique. The default image name is synchronized
in all of the lab jobs, so if you change the name later you must change it in all the jobs that use
the image.

Enter a lab description to help you differentiate the lab from others (optional). Click OK. This is
also optional.

Identify an image in the Create Disk Image job.

Set computer names and addresses in the Update Configuration job.

The following information describes the default jobs. To run one of these jobs, simply drag it to the
computer or computer group that you want it applied to.
Create Disk Image.

This job uploads an image of a computer to the server and an image name is
created automatically based on the lab name. However, there is no actual image in the job until you
drag the image source computer to this job.

Deploy Lab. This job has three default tasks: Deploy image, Apply configuration settings, and Back
up registry files. The image that is uploaded using the Create Disk Image job is deployed when you
use this job. The configuration settings you specify in the Update Configuration job are applied to
the computers, and then the computer registry files are uploaded to the Deployment Server.
Restore Lab. This job restores the image and registry files to a computer where a lab was previously
deployed. You can quickly get a computer running again by restoring the lab on that computer.
Update Configuration.

This job lets you set unique configuration information (such as computer
names and network addresses) for client computers. When a lab is deployed, each computer has an
identical image, but not the same configuration settings. This means you don't have to visit each
computer to reset IP addresses and other settings when you deploy an image.
Upload Registries.

This job backs up computer registry files to the Deployment Server.

Altiris Deployment Solution Reference Guide

150

Chapter 5: Managing Computers

Altiris Deployment Solution Reference Guide

Using Lab Builder

151

Chapter 5: Managing Computers

Altiris Deployment Solution Reference Guide

Using Lab Builder

152

Chapter 5: Managing Computers

Altiris Deployment Solution Reference Guide

Using Lab Builder

153

Chapter 6:

Building and Scheduling Jobs


A job represents a collection of predefined or custom deployment tasks that are scheduled and
executed remotely on selected client computers. You can build jobs with tasks to automatically
create and deploy hard disk images, back up and distribute software or personality settings, add
printers, configure computer settings, and perform all aspects of IT administration. Jobs can be run
immediately for a specific computer, or stored and scheduled for daily or long-term administrative
duties on multiple computer groups.

Job icons display in the Jobs pane of the Deployment console. To assign and
schedule a job in the Deployment Console, drag the job icon to selected computer
icons. Job status icons also display in the Details pane of the Deployment Console
to indicate various deployment states. See Viewing Job Details on page 154.
The New Job Wizard guides you through common deployment and management jobs. It is an easy
way to set up new users or migrate users to new computers, create and distribute images of
computers on the network, distribute software packages, restore computers, and more.
Jobs include one or more Deployment Tasks. You build jobs by adding tasks to a job and then
customizing the task for your specific needs. You can add tasks to capture and distribute images,
software packages, and personality settings. Or you can write and run a script task, or run scripted
installs, configure settings, copy files and back up registry settings. You can also modify existing
jobs by adding, modifying, copy and pasting, or deleting tasks to fit your needs. See Building New
Jobs on page 158.
Set conditions on jobs to run only on computers with properties that match the criteria that you
specify. You can build one job to run on different computer types for different needs, and avoid
mistakes by ensuring that the right job runs on the right managed computer. See Setting Conditions
for Task Sets on page 159.
Initial Deployment lets you run predefined jobs and configuration tasks on new computers when
they start up. You can automatically deploy new computers by imaging and configuring TCP/IP,
SIDs, and other network settings and then installing basic software packages. See Sample Jobs in
Deployment Solution on page 186.
Sample jobs are installed with Deployment Solution and display in the Samples folder of the Jobs
pane. You can run many sample jobs as they are, or you can set environmental variables. See
Sample Jobs in Deployment Solution on page 186.

Viewing Job Details


As jobs are assigned, scheduled and executed, it is helpful to know specific details about their status
and assignments. The Deployment Console provides job icons to show state and status of the job in
the Details pane:

Job status icons that update to display the state of the job in running deployment tasks. These
icons are graphical symbols in the Deployment console used to identify the status of an assigned
job.

Altiris Deployment Solution Reference Guide

154

Chapter 6: Building and Scheduling Jobs

New Job Wizard

.
Indicates that a job is scheduled to run on a computer or computer group.

Indicates that a job is in progress.

In the Details pane, indicates that a job has executed successfully.

Indicates that a job is associated with a computer or group of computers but is not
scheduled.
Indicates error conditions when individual tasks run.

A description of the job, if available. You can also use the Add or Modify buttons in the main
window to edit the description as well.

If a job defines error conditions when individual tasks run, the Status field displays any errors
incurred and the tasks that completed successfully.

Job Schedule details. This is the job's run time, beginning when the job started and ending when
it completed successfully.

The currently applied conditions displayed in a list box with a Setup button to add conditions to
different task sets for different computer properties within a job. Conditions specify
characteristics that a computer must have before the job will execute. See Setting Conditions
for Task Sets on page 159.

A list of tasks assigned to the job and task descriptions are also be displayed. Change the order
of the task execution with the arrow buttons. Tasks are executed in the order they are listed. See
Deployment Tasks on page 162.

Features to add, modify, and delete tasks for each job.

A list of assigned computers and its deployment history.

To sort jobs or computer details, just point and click on the category in the Details bar. Example:
click the Status column heading to organize and display the progress status of the job.
See also Viewing Computer Details on page 107.

New Job Wizard


The New Job Wizard provides integrated features to build, assign, and schedule common
deployment jobs. It helps you build the most common jobs, and guides you through additional steps
to assign and schedule the jobs to selected computers. It lets you quickly build image files and deploy
new computers, distribute software packages, migrate users, and more.
Note: When a software package or deployment job are scheduled to run on client computers, users

will see the Altiris Client Service Message dialog display, warning them that a job is about to
execute. If a user clicks the Abort button when the message displays, an event is logged to the client's
history so that Deployment Solution administrators know when users abort a scheduled event.

Altiris Deployment Solution Reference Guide

155

Chapter 6: Building and Scheduling Jobs

New Job Wizard

Create a new job by clicking the New Job Wizard button on the Deployment
Console, clicking File > New > Job Wizard, or right-clicking in the Jobs pane of the
Deployment Console and selecting New Job Wizard. The New Job Wizard will
open to guide you through basic deployment jobs.
1

Select a job option:


Create an image. This wizard guides you through the steps required to create an image of a
computers hard disk and schedule the job. See Creating a Disk Image on page 163.
Deploy and configure computers. This wizard guides you through the steps required to lay down
a new disk image on a selected computer and then install software and personality settings. See
Distributing a Disk Image on page 165.

This wizard guides you through steps required to install software


packages. You can set conditions, select packages, assign to computers, and schedule the job.
See Distributing Software on page 172.

Deploy software packages.

Restore a computer. This wizard guides you through the steps required to restore a computer to a

known working state by re-imaging the hard drive and reinstalling software packages,
personality settings, and defining configuration values. This option reschedules jobs saved in
each managed computers history record, which contains all deployment tasks previously
processed. See Restoring a Computer from its Deployment History on page 136.

This wizard guides you through the steps required to move a computer hard
disk image, applications, and personality settings from a source computer to a destination
computer. You can perform one or more migration operations using provided options.

Migrate computers

Give the job a unique name. You can type a name with up to 64 characters.

Follow the steps in each wizard to create a job (some New Job wizards build multiple jobs).
After creating a job, it will display in the Jobs pane of the Deployment console with deployment
tasks listed in the Tasks list for each job selected.

Note: You cannot define return codes when using the New Job Wizard. See Building New Jobs

on page 158 to build customized jobs and set up return codes.

See also Modifying Tasks in a Deployment Job on page 182.

Migrating Computers
From the New Job Wizard you can select Migrate computers to quickly distribute hard disk images,
software, and settings from a users current computer to a new computer. You can image a new
computers hard disk with a new operating system and then install software and personality settings.
Or perform different levels of migration to distribute only software or to simply capture and
distribute personality settings to the new computer.
Migrate one computer to another separate computer
Click this option to migrate a user from a source computer (old computer) to another destination
computer (new computer). Capture personality settings, distribute a new hard disk image, distribute
software and then redistribute the saved personality settings from the source computer to the new
destination computer.
Click the option alone to migrate only personality settings to one or more computers. Additionally,
select Prepare destination computer with a disk image to distribute a disk image to the new computer
and select Install software packages prior to applying the personality on the destination computer to
install software packages on the new computer.
Note: This option will create two jobs that will display in the Jobs pane: Job (Capture) and Job

(Distribute).

Job (Capture) includes a Capture Personality Settings task (see Capturing Personality Settings on
page 174) to capture the personality of the source computer and a Modify Configuration task to
rename the source computer to avoid naming conflicts (see Modifying Configuration on
page 176). The source computer will be named computerName (Old).

Altiris Deployment Solution Reference Guide

156

Chapter 6: Building and Scheduling Jobs

New Job Wizard

includes a Deploy Image task (see Distributing a Disk Image on page 165) if
selected, a Modify Configuration task to update settings to the destination computer, and one or
more Install Package tasks to update software (if selected) and migrate personality settings (see
Distributing Software on page 172).

Job (Distribute)

Migrate the same computer to another operating system


Click this option to upgrade the operating system on a computer and then reinstall personality
settings and software packages on the same computer. It will create jobs and tasks to capture the
personality settings, distribute a new disk image, distribute software packages, and then migrate the
personality settings.
Click the option alone to deploy a disk image and migrate personality settings to the computer.
Select Install software packages prior to applying the personality on the destination computer to install
software packages on the computer.
Note: This option will create two jobs that displays in the Jobs pane: Job (Capture) and Job
(Distribute).

Job (Capture) includes a Capture Personality Settings task (see Capturing Personality Settings on
page 174) to capture the personality of the source computer.
Job (Distribute) includes a Deploy Image task (see Distributing a Disk Image on page

165) and one


or more Install Package tasks to update software, if selected (see Distributing Software on
page 172).
Simply capture the personality of the computers
Click this option to capture and save, but not distribute, the personality settings of the selected
computer(s). You can choose a personality template and save Personality Packages to the
Deployment Share, allowing you to distribute these personality settings later to new computers.

Note: This option will create a single job with a Capture Personality Settings task (see Capturing

Personality Settings on page 174).

See also New Job Wizard on page 155.

Selecting Computers in the New Job Wizard


The New Job Wizard provides steps to select and assign computers to the jobs created in the wizard,
rather than requiring you to create a job and then assign it to computers when Building New Jobs.
The jobs created in the New Job Wizard display in the Jobs pane, and can be saved and assigned to
other computers at a later time. You can also schedule jobs for the specified computers in the wizard
(see Scheduling Jobs on page 160).

Apply Computers to a Job


When deploying software in the New Job Wizard, you can select computers to assign the
Distributing Software job created in the wizard. You can also select an option to simply store the job
and use it at another time without scheduling the job. Regardless of the scheduling option selected,
the job will display in the Jobs pane to use at another time.
New Computers.

the job.

Open an Adding New Computers dialog box to create new user accounts to assign

See also Scheduling Jobs on page 160.

Associating Destination Computers


Use this dialog box to associate source computers with destination computers when migrating
personality settings. Depending on the computers selected in the previous Select Computers dialog
box, you can migrate personality settings captured from the source computers to new destination
computers.

Altiris Deployment Solution Reference Guide

157

Chapter 6: Building and Scheduling Jobs

Building New Jobs

Right-click a computer in the Source column to replace it with another source computer. Right-click
a computer in the Destination column to replace it with another destination computer and assign it to
a new source computer. To automatically assign multiple computers, click Automatic to assign
source computers with destination computers using an alpha-numeric order. The associated
computers will share personality settings after running the jobs.
See also Migrating Computers on page 156.

Setting up Conditions in the New Job Wizard


The New Job Wizard also provides steps to set up conditions, a step usually performed
independently for each job during its build phase. Setting conditions lets you run selected tasks only
on computers matching defined criteria (see Setting Conditions for Task Sets on page 159).
Click Setup conditions for this set of tasks to open the Define Conditions dialog box from the New Job
Wizard.

Install Software Packages


The New Job Wizard provides steps to install software packages to the selected computer(s). You
can install any type of software to the managed client computer, including MSIs, RIPs, and
Personality Packages. If the selected package is not a RIP or Personality Package, then a message
box will open asking if you want to continue (See Distributing Software on page 172 for additional
information).

Summary of Options
After selecting options in the New Job Wizard, you can view a summary of job names, assigned
computers, conditions, and other selected choices. To change any options, click Back to return to
previous dialog boxes. Click Finish to complete the steps in the wizard.
See also New Job Wizard on page 155 and Job Scheduling Wizard on page 159.

Building New Jobs


A job can be a single task to distribute software or change computer property settings, or a job can
be a series of tasks sequenced to migrate hard disk images, set post-installation TCP/IP and SID
values, and install software packages and personality settings.

Create a new job by clicking the New Job button on the Deployment Console.
Click File > New > Job, or right-click in the Jobs pane of the Deployment Console,
and select New Job. You can modify jobs by double-clicking the job or rightclicking, and then selecting Properties. Add tasks to each job using the Setup
commands.
1

Create a new job. Enter a unique name and description for the job. You can type a name with up
to 64 characters.
A new job will be added to the Jobs pane in the Deployment console. You can group and
organize jobs, and then access and apply them to computers or computer groups from an index
of prebuilt jobs.

Set conditions to apply the job to specified computers meeting defined criteria. Order multiple
conditions to run jobs on computers that match the first applicable condition. See Setting
Conditions for Task Sets on page 159. This is optional.

Click Add to add open a list of possible deployment tasks to add to each job. See Deployment
Tasks on page 162.

Set task options using the provided wizards.

Altiris Deployment Solution Reference Guide

158

Chapter 6: Building and Scheduling Jobs

Job Scheduling Wizard

After you complete the steps to create a task, it will be added to the task list box. Click Add to
add another task. Use the arrow buttons to change the order of execution of the tasks in the Task
list box.
Tasks are executed in the order that they display in the task list. As a result, make sure you do
not run a task that will override previous tasks. Example: list Distribute Disk Image above
Distribute Software or Distribute Personality, allowing the hard disk to be imaged before installing
applications and settings.
5

Set Return Codes. The last action in each task wizard lets you set return codes for each
deployment task. See Setting Up Return Codes on page 185. This is optional.

After adding tasks, click OK.

To schedule the job, drag it to a computer or computer group. The Schedule Jobs dialog box will
open. See Scheduling Jobs on page 160.

See also Importing and Exporting Jobs on page 184.

Job Scheduling Wizard


The Job Scheduling Wizard provides features to assign jobs to selected computers and computer
groups, and to then schedule the jobs to run without using a mouse. This new feature meets Section
508 requirements to improve disability access and allows integration of voice activation software
and other user interface features.

Select Job(s)
Select the job(s) or group(s) of jobs to assign to computers or computer groups. Use the SHIFT and
CTRL keys to select multiple jobs or job folders. Click Next.

Select Computer(s) or Computer Groups


Select the computer(s) or group(s) of computers to assign the jobs selected in the previous dialog
box. Use the SHIFT and CTRL keys to select multiple computers or groups. Click Next.
New Computers.

Click this button when Adding New Computers.

Setting Conditions for Task Sets


Setting conditions on a job lets you run selected tasks only on computers that match defined criteria.
As a result, you can create a single job with tasks defined for computers with varying properties,
including OS type, network adapters, processors, free drive space and other computer properties.
You can then create task sets for each job that will apply only to the computers matching those
conditions.
Note: The default condition (named default) has no parameters or values associated with it. If this

is the only condition that a job contains, then the tasks associated with the default condition will
always work on all of the computers to which the job is assigned. Default condition is like having
no conditions.

In addition, if a task is associated with the default condition the task will always execute when a
computer does not meet any other conditions associated with this job.
1

Select a job in the Jobs pane of the Deployment Console.

Click Setup next to the Condition box. A menu will open with options to create a New condition,
Modify a condition, or Delete a condition.
To reorder conditions, click Order and reorder them using the Up or Down buttons. See Order
Condition Sets on page 160.

Click New in the menu to open the Condition Settings dialog box. Enter a name for the condition
up to 64 characters.

Altiris Deployment Solution Reference Guide

159

Chapter 6: Building and Scheduling Jobs

Scheduling Jobs

Click Add to open the Condition dialog box.


Click the Field list and select a data field heading from the list. You can define conditions based
on common client features such as operating system, software and hardware version, hard drive
space, OS language, RAM, and other characteristics.
Click Operation and select a compare statement. In the Value box, type a string to search for in
the selected database field. You can set conditions based on computer properties stored in fields
in the Deployment Database. Example: you might want to set a condition to match a particular
asset tag, Altiris agent version, or IP address. You can use wildcard characters and AND/OR
operators.

To set up custom conditions based on custom tokens, select User Defined Tokens from the Field
list.

Click OK.

The task set you create displays in the Task list for each condition. When you select a new condition,
the tasks for that condition display.
You can set Condition A to distribute the XPImage.img file to Windows XP computers using a
Deploy Image task. You can then set Condition B to distribute the W2KImage.img file to Windows
2000 computers using another Deploy Image task. When the job is applied to a computer group, the
conditions will be evaluated for each computer and the appropriate task will execute on the
appropriate computer.
Note: When using User Defined Tokens to set conditions for some client property values, you may

be required to use the decimal value rather than the hex value. Example: when setting conditions
based on the NICS table on the nic_device_id and nic_vendor_id columns, you are required to use
decimal values.
See also Deployment Tasks on page 162.

Order Condition Sets


By specifying and ordering different sets of conditions, you can determine when a task executes
based on defined computer properties. Each condition is processed in sequence until the computer
matches the condition defined within a set. If the computer does not meet any of the defined
conditions, it will run the default condition. Once a match is found, the set of tasks for this condition
set is processed.
See also Setting Conditions for Task Sets on page 159.

Scheduling Jobs
After a job has been created, and it has been assigned to multiple computers or computer groups. The
Schedule Job dialog box will open automatically, allowing you to schedule the job to run
immediately, at a scheduled interval, or assigned but not scheduled. Job and job folders selected
from the Jobs pane of the Deployment Console are scheduled in the order they were selected, even
across multiple Deployment Servers.
To schedule a job
1

Drag a job to a computer or computer group. The Schedule Job dialog box will open.

In the Schedule Job dialog box, click the Job Schedule tab. The options are as follows:

Do not schedule. This option lets you apply jobs to computers but does not run the job until
you return to the Schedule Job dialog box and set a run time.

Run this Job immediately. This

Schedule this Job. This option lets you type the date and time to run the job at a specified time
and date. To run it at regular intervals, specify a time and date to repeat.

Repeat this job every x.

week(s).

Altiris Deployment Solution Reference Guide

option lets you run the job now.

A job can be scheduled to execute by minute(s), day(s), hour(s),

160

Chapter 6: Building and Scheduling Jobs

Scheduling Jobs

Allow this job to be deferred for up to x. A job can be deferred when the server is busy executing

Schedule in batches of x computers at y minute intervals.

other jobs, setting a lower priority for particular jobs. By default all jobs are deferred up to
five minutes.
computers in batches to maximize efficiency.

This option lets you schedule

Click the Computer(s) Selected tab. This is a list of computers, their associated group, and IP
address that the job is scheduled to run.

Click the Job(s) Selected tab. This displays the job name and folder is located in the Jobs pane.
Use the UP and Down arrow to change the order of the scheduled jobs.

Click OK.

Note: The Schedule Job dialog box is the same for Rescheduling Jobs, New Job Wizard, and Job

Scheduling Wizard.

To reschedule a job
1

From either the Computers or Jobs panes in the Deployment console, select a job or computer
that has been previously scheduled.
A job icon displays in the Details pane identifying the computers assigned or the name of the job.

Select the job icon, click the scheduled computers in the Details pane, right-click and then click
Reschedule.
If you selected a computer icon, click the job icon in the Details pane, right-click and then click
The Schedule Jobs dialog box will open.

Reschedule.
3
4

To immediately start a scheduled job that has not yet run, right-click the job icon and select Start

Now.

To stop a repeating job, right-click the job in the Details pane and click Discontinue Repeat. At
this point you need to schedule a new time to run the job or click the Do not schedule option.

To remove computers from a scheduled job


You can complete this task by removing a job assigned to a computer or removing a computer
assigned to a job.
1

Click a job in the Jobs pane.

Click a computer in the Details view and press Delete or right click the job(s) and select Delete.

To remove tasks from a job


You can remove tasks assigned to a job by double-clicking the job and opening the Job properties
dialog box. (Edit features will also open in the Details view of the Deployment Console when you
select the job from the Jobs pane).
1

Select one of the assigned tasks in the Task list.

Click Delete.

To remove scheduled jobs from a computer


1

Click the computer.

Select the scheduled job in the Details window, and press Delete or right click the job(s) and
select Delete. To remove multiple jobs, hold down the SHIFT or CTRL key while you select the
job(s), then press Delete or right click the job(s) and select Delete.
The icon for a scheduled job is yellow.

To run a job immediately from the Resources view


If you have a batch file, image file, RIP, MSI, or executable file assigned to a job or stored in the
Deployment Share, then these files and packages will be displayed in the Resources view (see
Shortcuts and Resources View on page 91). You can drag these files and packages from the
Resources view to a computer or computer group to automatically create and run a job (or you can
drag computers to a file or package in the Resources view). A job will be created automatically for
each assigned package in the Systems Jobs > Drag-n-Drop folder.

Altiris Deployment Solution Reference Guide

161

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

See also Building New Jobs on page 158 and Modifying Tasks in a Deployment Job on
page 182.

Deployment Tasks
A task is an action of a job. Jobs are built with tasks. Each task is executed according to its order in
the task list contained in a job. You can resize the task pane by dragging the bottom pane (horizontal
bar) that separates the task list and the scheduled computer list of the Deployment Console. This lets
you view a greater number of tasks in a deployment job without using the scroll bar to navigate up
and down.
The Deployment Console has multiple tasks available from the Add menu, including:
Create a disk image from a reference computer and save the image file (IMG or
EXE files) for later distribution. See Creating a Disk Image on page 163.

Create Disk Image.

Distribute Disk Image. Distribute previously created disk images (IMG or EXE files) or create a disk
image from a reference computer on the network and simultaneously distribute it (IMG or EXE) to
other managed computers on the network. See Distributing a Disk Image on page 165.
Scripted OS Install. Run scripted (unattended) installs using answer files to install computers
remotely over the network. See Scripted OS Install on page 167.

Distribute RIPs, MSI files, scripts, personality settings and other package files
to computers or groups. See Distributing Software on page 172.

Distribute Software.

Capture Personality. Capture the personality settings of a selected computer on the network using the
PC Transplant software. PC Transplant ships as a part of Deployment Server. See Capturing
Personality Settings on page 174.
Distribute Personality Package. Send a Personality Package to computer or groups. It identifies valid
Altiris packages and assign passwords and command-line switches to Personality Packages. See
Distributing Personality Settings on page 175.
Modify Configuration. Modify the IP address, computer and user name, domains and Active Directory

organizational units, and other network information and computer properties. See Modifying
Configuration on page 176.

Back up Registry. Back up an individual registry file for a selected computer and save it to a selected
directory. See Backing up and Restoring Registry Files on page 177.
Restore Registry. Restore registry settings previously saved for a selected computer. This lets you
recover from a hard disk crash or other disasters. See Backing up and Restoring Registry Files on
page 177.
Get Inventory. This lets you gather inventory information from client computers to ensure that the
deployment database is up-to-date with the latest computer properties. See Get Inventory on
page 177.

Create custom commands using scripts to perform jobs outside the bounds of the pre
configured tasks. Use the Run Script dialog box to select or define a script file to run on specified
computers or groups. See Run Script on page 177.

Run Script.

Copy File to. Copy a file from the Deployment Share or another source computer to a destination
computer. See Copy File to on page 180.

Perform power control options to restart, shutdown, power off, and log off. See
Power Control on page 182.

Power Control.

Tasks are listed for each job in the task list box. Each task will execute according to its order in the
list. You can change the order using the up and down arrow keys.

Altiris Deployment Solution Reference Guide

162

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

Creating a Disk Image


This task creates an image of a computers hard disk and then saves the image as an .img or .exe file.

Create an image file using the New Job Wizard or adding the task when Building
New Jobs. You can distribute the disk image file using the Distributing a Disk
Image task. This task will run Altiris RDeploy.exe from the console to capture
and migrate hard disk images.
Note: To create an image of a computer, you must boot to DOS, Linux or Windows PE. This requires

that you set up PXE Server or Deployment Agent for DOS automation.

Enter a path and file name to store the disk image file. You can store image files to access later
when a managed computer is assigned a job that includes the image file.
The default file name extension is IMG. Saving image files with an EXE extension makes them
into self-extracting executable files (the run-time version of RapiDeploy is added in the file).

Click Local image store if you want to store the image file locally on the managed computer's hard
drive. Be sure to enter the path relative to the managed computer (Example: c:\myimage.img).
This is optional.
When you store an image locally on a managed computer instead of a file server, you save server
disk space and decrease network traffic. If you imaging multiple computers or if you image
computers frequently, there is a strong advantage in storing images locally.
Prerequisite: Make sure you have a hidden automation partition installed on the computers
hard disk with enough disk space to hold the images you want to store.
Note: When imaging computers where labs are cached, do not use the option to remove the

automation partition unless you want to clear the lab from the computer.

Select Prepare using Sysprep to use a Sysprep answer file when creating an image. Then, click
the Sysprep Settings button.
Note: You must enter global values for Sysprep before you select the Prepare using Sysprep
option. To enter global values for Sysprep, navigate to Tools > Options > Global tab > Sysprep
Settings. See SysPrep Settings on page 164.

4
5

Type a description to help identify the task.


Select the required pre-boot environment from the Automation - PXE or BootWorks environments
drop-down list to perform the Create Disk Image task in selected preboot environment. By default the DOSManaged Boot Option type will be selected.

(DOS/Windows PE/Linux)
6

Click Advanced to select Media Spanning and additional options. See Create Disk Image
Advanced on page 164. This is optional.

Select the required pre-boot environment from the Automation (Pre-boot Environment) dropdown list to perform the Create Disk Image task. The option reported by the PXE Manager is the
default pre-boot environment option.

Click OK (if you are using the New Job Wizard).


or
Click Next.

Set Return Codes. See Setting Up Return Codes on page 185. This is optional.

10

Click Finish. The task displays in the Task list for the job.

Troubleshooting Tip: If an imaging Job fails on a managed computer, the Deployment agent
configuration page displays on the client with a prompt, asking if the user wants to configure the
client or restore the original settings. Select Cancel > Restore Original Settings on the client screen.

See also Deployment Tasks on page 162.

Altiris Deployment Solution Reference Guide

163

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

SysPrep Settings
You can use an existing Sysprep answer file or create a new file by entering the information onto
the Computer Information tab. Regardless of the Sysprep file used, you must select an operating
system and enter product key information.

Answer File/OS tab


By default, Deployment Solution uses an Altiris answer file unless you select the Use following
as answer file for Sysprep checkbox. Click the Folder button and browse to an existing Sysprep
answer file. The View Answer file button lets you view the selected answer file.
Click the drop-down arrow and select an Operating System from the list. Click the Add button to
enter product key (up to 29 characters) information. Add as many product keys as needed, then
select a product key from one of the keys listed in the OS Information pane. You can also specify
additional command-line switches in the Additional command-line switches box.

Computer Information tab


Select the Use following values for this Job checkbox if you want Sysprep to use the values you
define. Otherwise, the Sysprep global values are used.
Computer name. This is a token value that is replaced with information read from the Deployment
database when the image is created. If this field is modified, the Suffix and Current Suffix fields

are reset to zero.


Suffix.

Enter up to five digits in this field.

Current Suffix.

By default, the suffix value is used. This field cannot be edited.

In the Licensing Information area, specify the user and organization name. You can provide the
licensing mode by selecting the number of concurrent connections, per server or per seat.
Per Server. Per Server indicates that the end user has purchased client access licenses for each
server, which allows a certain number of concurrent connections to the server.

Per Seat indicates that the end user has purchased a client access license for each
computer accessing the server.

Per Seat.

Create Disk Image Advanced


RDeploy Options
Change Deployment Solution to run RDeployT as the default imaging executable (instead of
RDeploy). This facilitate the imaging of thin client computers.
Graphical Mode (RDeploy). Select
Text Mode (RDeployT). Select

this checkbox to run the RDeploy in a GUI mode.

this checkbox to run the RDeploy in a text mode.

Media Spanning
Maximum file size.

The Maximum file size supported is 2 GB. To save an image larger than 2 GB,
Deployment Server will automatically break it into separate files regardless of your storage capacity.
From the Maximum file size list, select a media type.

Specify ___ MB.

If the preferred type is not on the list, enter the file size you want in the field.

Additional Options
Do not boot to Windows. Select this option to create an image of the hard disk while booted to DOS
without first booting to Windows to save network settings (TCP/IP settings, SID, computer name,
etc.). If you select this option, these network settings will not be reapplied to the computer after the
imaging task, resulting in network conflicts when the computer starts up.

Note: This checkbox should be selected when imaging Linux computers.

Altiris Deployment Solution Reference Guide

164

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

Compression.

Compressing an image is a trade-off between size and speed. Uncompressed images


are faster to create, but use more disk space.

Select Optimize for Size to compress the image to the smallest file size. Select Optimize for Speed to
create a larger compressed image file with a faster imaging time. The default setting is a balance
between Optimize for Size and Optimize for Speed.
Note: Configuration restoration after imaging a compressed drive is not supported for this release.
Additional command-line switches.

You can add command-line switches specifically for the


RapiDeploy program to execute imaging tasks. See the Altiris RapiDeploy Reference Guide located
in the Docs folder in the Deployment Share.

Distributing a Disk Image


Distribute an image (.img) or executable (.exe) file to managed computers to lay down a previously
created hard disk image.

Distribute a hard disk image using the New Job Wizard or adding the Distribute
Disk Image task when Building New Jobs. You can create the disk image file
using the Creating a Disk Image task. This task will run Altiris RDeploy.exe
from the console to capture and migrate hard disk images.
Note: If you are going to deploy Windows image over a Linux computer or Linux image over a

Windows computer, then you need to change the path of the Deployment Agent for Windows log
file accordingly.

Click Select a disk image file to select a stored image file. This lets you lay down a new image file
from a previously imaged computer. This is a common way to distribute an image file.
Note: When entering Linux mount points, you must put a single quote around folders or

filenames that contain either a period (.) or a space. These are considered special characters in
Linux and must have single quotes around the name so that the directory path can be found.
Example: //ImageServer/DS Images/mnt/z.

Select Local image store if you stored the image file on the client computers hard drive. With
local image store, the image file is stored on a partition on the computer being imaged.
Consequently, the server cannot validate the image when a local image store is used. This is
optional.

If you want to image a source computer on the network, click Select a computer on the network.
Enter the name and location of the source computer to both create an image and distribute the
newly created image file. This is optional.
This option saves an image of a selected computers hard disk in its current state each time the
job executes. You can schedule the job to image a specified computer every time it runs, allowing
the image to be updated each time.
Note: Network mapping must exist on the source computer before imaging. UNC paths are not

supported in DOS.

Select the Save the disk image as a file while distributing option to save the newly created image
file to a specified disk drive. If you use a reference computer as the image source, you can also
choose to save the image as a file for later use. Select the checkbox to save the image and type
in or browse for the location where you want to store the file.
4

Select Prepare using Sysprep to use a Sysprep answer file when distributing an image. Then, click
the Sysprep Settings button.
You can use an existing Sysprep answer file or create a new one by entering the information on
the Computer Information tab. Regardless of the Sysprep file used, you must select an operating
system and enter product key information.

Altiris Deployment Solution Reference Guide

165

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

Note: You must enter global values for Sysprep before you select the Prepare using Sysprep
option. To enter global values for Sysprep, navigate to Tools > Options > Global tab > Sysprep
Settings. See SysPrep Settings on page 164.
5

Click Automatically perform configuration tasks after completing this imaging task to boot the
computer again and push down configuration settings to the newly imaged computer. This is
optional.
Select the required pre-boot environment from the Automation - PXE or BootWorks environments
drop-down list to perform the Create Disk Image task in selected preboot environment. By default the DOSManaged Boot Option type will be selected.

(DOS/Windows PE/Linux)
7

Click Advanced to resize partitions and set additional options. See Distribute Disk ImageResizing on page 166. Click OK.

Select the required pre-boot environment from the Automation (Pre-boot Environment) dropdown list to perform the Distribute Disk Image task. The option reported by the PXE Manager
is the default pre-boot environment option.

Click OK (if you are using the New Job Wizard).


or
Click Next.

10

Set Return Codes. See Setting Up Return Codes on page 185. This is optional.

11

Click Finish.

See also Deployment Tasks on page 162.

Distribute Disk Image-Resizing


By default, whenever you deploy an image, you have the option to resize the partition to take
advantage of the available disk space. Drive Size gives you information about the size of the image,
so you can determine if you need to change partition sizes. Minimum indicates the amount of space
the image will use on the target computers. Original indicates the image source disk size.
Fixed Size.

Select this option and enter the desired partition size.

Percentage.

occupy.

Select this option and enter the percentage of free space that you want the partition to

Min.

View the minimum size of the partition.

Max.

View the maximum size of the partition.

Note: FAT16 file systems have a 2 GB limit and cannot be resized larger than that (although it can
be sized smaller than the minimum value). HP partitions remain a fixed size.

Distribute Disk Image-Additional Options


This option lets you specify operations for existing Automation Agents and OEM disk partitions.
The options are as follows: leave the partition as it is, remove, or replace the existing partitions. If
the image file does not contain any information for an automation or OEM partition, the option will
default to Leave the clients existing Automation or OEM partition as it is.
RDeploy Options:
Graphical Mode[RDeploy]. Click this option if you want to choose the imaging executable as RDeploy.
Text Mode[RDeployT]. Click this option if you want to choose the imaging executable as RDeployT.
Text Mode or RDeployT is the default choice.

Automation Partition:
Leave the client's existing BW partition as it is. If

the image file contains no automation partition


information, by default, this option is selected. The automation partition will remain unchanged
when distributing disk images.

Altiris Deployment Solution Reference Guide

166

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

Delete the client's Automation partition [-nobw]. Select

Automation partition from client computers.

this option if you want to delete the existing

Replace the client's existing BW partition from image file [-forcebw]. Select this option if you want to
replace the existing automation partition on the client computer with the automation partition from
the image file.

OEM Partition:
Leave the client's existing OEM partition as it is. If the image file contains no OEM partition
information, by default, this option is selected. The OEM partion will remain unchanged when
distributing disk images.
Delete the client's OEM partition [-nooem]. Select

partition from client computers.

this option if you want to delete the existing OEM

Replace the client's existing OEM partition from image file [-forceoem]. Select this option if you want to
replace the existing OEM partitions on the client computer with the OEM partition from the image
file.
Additional Command line switches. You can add command-line switches specifically for the
RapiDeploy program that runs imaging tasks. See the Altiris RapiDeploy Reference Guide located
in the Docs folder of the Deployment Share.

Note: The checkdisk command-line switch should not be used from a Deployment console. The
post-configuration task will fail after an image restore.

See also Deployment Tasks on page 162.

Scripted OS Install
The Scripted OS Install task performs remote, automated, and unattended operating system
installations over the network using answer files to input configuration and installation-specific
values. Scripted installs allow you to deploy server and client computers across the network from
installation files, and then perform post-installation configuration tasks. You can run scripted installs
for Windows or Linux computers.
Important: Scripted Install requires either an automation boot disk or PXE Server. Using embedded

automations will cause the selected image (DOS, Linux, Windows PE) to load and then halt. It will
not allow the scripted install to run.
When running a Scripted OS Install task, you can identify the type of OS to install for supported
languages, run the scripted install, and update with service pack installations. This task provides
easy-to-use features to create an answer file for each scripted installation.
Scripted installs are flexible in performing post-configuring tasks, but much slower and bandwidth
intensive. Complete network and web server installation and configuration tasks profit most from
scripted installs.

Windows. Use complete unattended install features to copy Windows OS source files quickly to the
Deployment Share and easily create an answer file. Configured OS install sets can then be reused to
build and run scripted install jobs as needed. See Scripted Install for Windows on page 167.
Linux. Run scripted install jobs to remotely install different versions of Linux. You can customize
sample scripted install jobs installed with the Deployment Server system and create a kickstart
answer file to remotely run a scripted install. See Scripted Install for Linux on page 172.

Scripted Install for Windows


1

After selecting Add > Scripted OS Install, click the Windows option.

Select the type of Windows operating system to install. See Select OS Version and Language
on page 168. Click Next.

Altiris Deployment Solution Reference Guide

167

Select the required pre-boot environment from the Automation - PXE or BootWorks environments
drop-down list to perform the Distribute Disk Image task in selected
pre-boot environment. The option reported by the PXE Manager is the default pre-boot
environment option.

(DOS/Windows PE/Linux)

Select source files. Click the list to select Windows OS source files already copied to your
Deployment Share. See Installation Source Files on page 169.

Click Add New from the list to set up new OS installation files. See Operating System-Source
Files on page 169.
Click OK after entering a unique name and the path to the OS installation source files. The source
files will be copied over to the Deploy folder in the Deployment Share directory. The first source
files added will be given a generic name of WinOS001, with additional OS source folders named
to WinOS002, WinOS003 and so on. Service Pack source files will also be stored as an
WinSP00x.img file.
This process could take a few minutes. Because the installation source files are copied over to
the Deployment Share, when running subsequent scripted installs you will not need to add new
source files for this version of Windows. They can be selected from the list of installation source
files. See Installation Source Files on page 169.
Note: When importing Scripted Install jobs, you must edit the job files to point to the installation

source files on the new Deployment Server system. This requires you to run the Scripted Install
for Windows wizard and modify the path and name of the folder for the Installation Source Files
for the exported jobs. This is required for both the main installation and service pack installation
files. See also Importing and Exporting Jobs on page 184.

After the source files are copied, select the newly created OS source name from the Installation
Source Files list. Click Next.

Click to distribute a DOS disk image (default), or continue without distributing a DOS image and
partition and format the hard disk of the destination computer using custom scripts or setup
utilities. Click Advanced to set partition size, delete hidden partitions or set RapiDeploy
command-line parameters. Click Next. See Operating System-Source Files on page 169.
Note: Before running a scripted install, you must install DOS. However, DOS is not required if

you are using your own scripts or utilities to partition and format the client computer.

Import an answer file to the Deployment Database. See Import an Answer File on page 170.
Click Next.

Create the Answer file. See Answer File Setup on page 170. Click Next.

10

Set command-line switches for cmdlines.txt files and for the WINNT installation program. See
Command-line Switches for Scripted Install on page 171. Click Next.

11

View and modify the Deployment Agent for Windows configuration file from the dialog box.
See Deployment Agent Settings for Scripted Install on page 172. Click Next.

12

View summary of selected options. See Scripted Install Summary on page 172. Click Next.

13

Set up return codes for the Scripted Install task. See Setting Up Return Codes on page 185.
Click Finish.

See also Scripted OS Install on page 167.

Select OS Version and Language


Identify the operating system version to run in a scripted install. The selected version and language
must correspond to your Windows installation files.
We support multiple languages for the following Deployment Solution utilities.

Altiris Deployment Solution Reference Guide

168

Chapter 6: Building and Scheduling Jobs

Boot Disk creator

Image Explorer

PXE Configuration Utility

Remote Client Installer

Control Panel Applet

DS Info

PW Util (Password utility)

Switch Management

Deployment Tasks

Select the OS version. Select the Windows operating system you want to install from the list. Click
Template if you want to install another version or language of a Windows operating system not

provided in the list.

Select the OS language. Select the language version of the

operating system to install. The language


must correspond to the OS source files. If you selected the Template option, then only the
Multilingual language option can be selected (this is a generic language option).

Automation (Pre-boot Environment). Select the required pre-boot environment from the Automation
(Pre-boot Environment) drop-down list. The option reported by the PXE Manager is the default preboot environment option.

List of supported multiple languages

German

French

Spanish

Japanese

Simplified Chinese

See also Scripted Install for Windows on page 167.

Installation Source Files


If you copied installation files to the Deployment Share for previous scripted installs, then the name
of this install source configuration displays in the list box for each OS type and language. To create
new source configuration sets for additional OS installs, select Add new source files from the list box.
Select or add new OS source files. Select the assigned name for each OS source configuration in the
list, or select Add new source files from the list to create a new install task. Previous scripted install
jobs will create a WinOS00x.img file in the Deploy directory of the Deployment Share.

The Operating System-Source Files dialog lets you identify the version of Windows install files and
enter the path to the files (on the CD or other medium).
Select or add new service pack source files. Run service pack updates immediately after installing the

operating system during the scripted install process. Previous scripted install jobs will create a

WinSP00x.img file.

See also Scripted Install for Windows on page 167.

Operating System-Source Files


Name OS source configuration, identify path and automatically copy Windows installation files to
the Deployment Share.
Enter a unique name for the OS source files.

Enter a name for the OS source configuration files to


assign an alias to associate with the install files for a specific OS version and language.

Altiris Deployment Solution Reference Guide

169

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

Enter path to OS source files.

Enter the path to the I386 folder on the CD where the Windows
installation programs and support files are stored. Example: browse to the CD drive and select
I386\WINNT.exe. Click Open.
The Windows OS identified previously in the Installation Source Files dialog box must match the
source files selected here. If the name and language of the OS does not match the installation files,
then you will receive an error.
Click OK and the files will copy from the source CD (or other volume) to the Deployment
Server\Deploy directory in the Deployment Share. This process will take a few minutes.
Enter a short description. Enter a description of the Windows OS source configuration, for example:

W2K Advanced Server SP3 English. This is optional.

See also Scripted Install for Windows on page 167.

Partition and Format Disk


Select a DOS disk image to distribute to the client computers before starting the Windows scripted
install. A DOS image is provided in the Images directory in the Deployment Share (default path in
the Name field).
Select a DOS disk image. Click this option to distribute a DOS image from the Deployment Share.
The Deployment Server system includes a DR DOS image file that is selected by default. You can
create your own MS DOS image from your 95 or 98 CD and build a job.
Advanced. Select advanced options to set the size of the partitions, or to remove hidden partitions
and add command-line switches. See Create Disk Image Advanced on page 164 and Distribute
Disk Image-Resizing on page 166.
Continue without distributing DOS image. Click this option to not install a DOS image from
Deployment Server. Skip this step if you are installing DOS using custom procedures for your
environment.

Note: While attempting to do a scripted install for Linux, make sure that you select both the options,

and Remove HP System Partition. This will remove the OEM partition
and allow the automation partition to be created as the first partition.

Remove Automation Partition

See also Scripted Install for Windows on page 167.

Import an Answer File


Reference a previously created answer file for a Windows scripted install. You can also view a
summary of the OS source configuration.
Select to import a previously created answer file to the Deployment
Database. Values for the answer file will be imported from the delimited text file and displayed in
the Answer File Setup dialog box.

Import existing unattend.txt.

You can enter a path and select an answer file with any name. The answer file will be imported to
the database, edited in the console (if required), and then distributed as an unattend.txt file to the
client computer.
See also Scripted Install for Windows on page 167.

Answer File Setup


Use these dialog boxes to enter values to create an answer file for a scripted install. These values are
stored in the Deployment Database. An answer file is then generated from the database
(unattend.txt) and distributed to each managed computer when the job executes.
In the Answer File Setup, select a value (a row) in the table. A pop-up list displays in the Values
column to change values for each entry. You can add new variables to each section by selecting the
bottom row named Add new Variable. To add a new section to the answer file, click the right arrow
button until the Add new Section tab displays (the last tab on the right).

Altiris Deployment Solution Reference Guide

170

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

Required answer file values will be selected automatically in the dialog box with a gray check (you
cannot clear these variables). Optional but selected values will have a green check. Other optional
values will be cleared. Select these optional values if you want to add them to the answer file when
it is generated.
The various tabs in the Answer File Setup dialog box correspond to general answer file sections. See
the Microsoft Windows Unattended Setup Guide for specific values for an unattended setup file.
See also Scripted Install for Windows on page 167.

Add a New Variable Value or Section


Use this dialog box to add new values to each variable or to add new variable sections to the answer
file.
Enter a name for the value or section. If you add a value, then this name displays in the pop-up list and

entered in the cell if selected. If you are adding a section, then this name displays in the new tab in
the Answer File setup dialog box.

Enter a value to be displayed instead of the real value.

tab.

Enter an alias that displays in the cell or on the

See the Microsoft Windows Unattended Setup Guide for your specific operating system values for
an unattended setup file.
See also Scripted Install for Windows on page 167.

Add a New Variable


Use this dialog box to add new variables to the answer file. This variable displays as a row in the
Answer File Setup dialog box.
Name of the variable.

Select a variable name.

Type of new variable.

Select a variable data type. The Default value and Displayed value boxes will
be activated depending on the variable type selected.

Default value of the variable.

Enter values for a list, text, password, or IP address types.

Displayed value of the variable.

variable value.

Enter an alias for list item types to be displayed instead of the real

Description. Enter comments to describe the new variable. It will be displayed in the Description
column of the Answer File Setup dialog box.

See also Scripted Install for Windows on page 167.

Command-line Switches for Scripted Install


Use this dialog box to enter Windows NT commands that are executed from the cmdlines.txt file.
You can also add WINNT scripted install command-line switches.
Switches.

install.

Add or edit switch commands to this line for the WINNT install program for the scripted

Additional commands in the cmdlines.txt file. Enter additional Windows scripted install commands in
this dialog box. The commands will execute in the order they are listed. The provided command
installs the Deployment Agent for Windows during the Install Component phase of the installation.
You can view and edit Deployment Agent settings in the next dialog box.

See also Scripted Install for Windows on page 167.

Altiris Deployment Solution Reference Guide

171

Deployment Agent Settings for Scripted Install


View or edit Deployment Agent for Windows settings in this dialog box. You can change agent
settings using this text-edit dialog box. See Production Agent Settings on page 120 for a list of the
Deployment Agent properties.
Select this option to apply these settings globally. This is to maintain
consistency in the way agent settings are applied.

Save these settings globally.

See also Scripted Install for Windows on page 167.

Scripted Install Summary


View a summary of the selected options for the scripted install. Click Back to change any of these
settings or click Finish to complete the Scripted Install task.
See also Scripted Install for Windows on page 167.

Scripted Install for Linux


The Scripted OS install for Linux provides a wizard to help set up Linux installation files and run
Sample jobs. Follow steps in the wizard to identify the type of scripted install and locate the answer
files. You can also modify and run Sample deployment jobs to remotely run a scripted install on
Linux servers and workstations. For complete information, see the Deploying Linux chapter in the
Deployment Solution Reference Guide located in the Docs folder of the Deployment Share.
Directory.

Browse to or enter the path and name of the Linux answer file (Kickstart file).

Command-line.

Enter command-line switches.

Automation - PXE or Bootworks environment (DOS/Windows PE/Linux). Select the required pre-boot

environment from the Default Automation drop-down list to perform the Backup and Restore task
in selected pre-boot environment. The option reported by the PXE Manager is the default pre-boot
environment option. By default the DOSManaged Boot Option type will be selected.
See also Scripted OS Install on page 167 and Scripted Install for Windows on page 167.

Scripted Install Summary


View a summary of the selected options for the scripted install. Click Back to change any of these
settings or click Finish to complete the Scripted Install task.
See also Scripted Install for Linux on page 172.

Distributing Software
Send MSI Packages, CAB, EXE, and other package files to selected computers or computer groups,
including EBS, and RPM files for Linux computers. This task identifies valid Altiris packages and
assigns passwords and command-line switches.

Altiris Deployment Solution Reference Guide

172

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

Distribute software packages to managed computers using the New Job Wizard
or adding the Distribute Software task when Building New Jobs.

Enter the name and location of the package to distribute in the Name field.
Note: Information about the package will be displayed in the Description area for valid packages.

If no description is displayed, then the file is not a RIP or a Personality Package.

For RIPs, if you set the password option when you created the RIP, you must enter the password
for the package to run.

Select Run in quiet mode to install the package without requiring user interaction.

Specify the users to associate with the RIP or the Personality Package.

Click Apply to all users to run the package for all users with accounts on the computer.

If sending the package to a managed computer with multiple users and if you only want it
installed for certain users with a unique password, clear the Apply to all users box.
Example: to install a RIP for a specific user accounts on a computer add values to the
Additional command-line switches field:
-cu:JDoe;TMaya;Domain\BLee
Note: The command-line switches are specific to any package you are distributing that

supports command-line options, such as MSI and Personality Packages. For a complete list
of command-line switches, see the Wise MSI Reference Guide and the Altiris PC Transplant
Pro Reference Guide.

If distributing an install package or other types of packages with associated support files, you can
click Copy all directory files to install all peer files in the directory. Click Copy subdirectories to
distribute peer files in the directory and all files in associated subdirectories.
Important: Some clients may have software installed on the client computer that, for protection
against harmful software, only allows software programs on a list of "well-known" executables
to run. Therefore, whenever the system administrator wanted to install a patch on client
computers, he or she would have to update the well-known-executable list on all the client
computers, which could be a lot of work.

To save the work of updating that list, or of manually renaming distribution packages, the
"RenameDistPkg" feature was added. Now, the system administrator may update the wellknown-executable list once with a filename of their choosing. The well-known filename may
then be entered into the Windows registry of the Deployment Server computer (the computer
running axengine.exe), as the "Value data" of a string value named "RenameDistPkg" under the
"HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Altiris eXpress\Options" key. If the
RenameDistPkg registry entry is set, then Deployment Server will rename installation files that
are copied to the client computers.
This feature only affects files that are temporarily copied to the client computer as part of a
"Distribute Software" task. The file that is to be executed only during the installation, sometimes
referred to as the "package", is the file that gets renamed, not the files that actually get installed
to various locations on the target computer.
If the Copy all directory files option is enabled task, only the main (installable) file will be
renamed.
6

Click Advanced to specify how files are distributed to the managed computer. You can copy
through Deployment Server, or copy and run directly from the Deployment Share or from
another file server. See Distribute Software Advanced on page 174. Click Next.

Provide additional command-line switches for distributing software.

Set Return Codes. See Setting Up Return Codes on page 185. This is optional.

Click Finish.

Altiris Deployment Solution Reference Guide

173

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

Notes:

When a RIP or Personality Package is executed through Deployment Server, the quiet mode
command-line switch is applied. This means the user will not be able to interact with the user
interface on the managed computer.

If the Personality Package is configured to run only if a particular user is logged in and only if
the user has an account on the managed computer, the package will run the next time that user
logs in. If the user does not have an account, the package aborts and sends an error back to the
console via the Deployment Agent. If the package is not run through Deployment Server, a
message is displayed on the managed computer and the user is prompted to abort or continue.

See also Modifying Tasks in a Deployment Job on page 182.

Distribute Software Advanced


Copy files using Deployment Server then execute. Click this option to distribute packages through
Deployment Server to the managed computer, requiring two file copy transactions if the
Deployment Share is on another file server. This option is run for Simple installs and is the default
option.
Copy directly from file source then execute. Click this option to copy packages directly from the
Deployment Share if this data store is located on another server (a Custom install). It will copy the
file and then run it, avoiding running through Deployment Server and diminishing processor output.
Execute directly from file source.

or another selected file server.

Click this option to run files remotely from the Deployment Share

File source access and credentials. Enter the user name and password for the client computer and the

Deployment Share. Both must have the same user name and password (this is not an issue if both are
on the same domain).

Note: Windows 95/98/ME computers have security limitations when copying files directly from the

source to the Deployment Agent using the UNC path name. It is suggested that you use the Copy files
for these types of computers or plan a proper security strategy for
direct copying.

using Deployment Server option

Capturing Personality Settings


The Capture Personality task lets you save personal display and user interface settings defined in the
OS for each user. You create a Personality Package that can be saved and distributed when migrating
users. This task will run Altiris PC Transplant from the console to capture and distribute settings.

Capture personality settings using the New Job Wizard or adding the Capturing
Personality task when Building New Jobs. See Distributing Personality Settings
to migrate settings to another user.
1

After creating a job, click Add > Capture Personality.

Enter the name of a personality template, or browse and select a template. A default personality
template is included in the PCT folder of the Deployment Share (DEFAULT.PBT). Enter the
name of the folder where you want to store the package.
The personality template lets you define the settings, files, and options to be captured during run
time. Click Template Builder to open a wizard to build a custom template.

In User account and folder login, enter the login credentials for the managed computer from which
the personality settings will be captured, and the file server where the Personality Package will
be stored.

In Package login, enter a password for the Personality Package. This is a run time password that
is required when the Personality Package runs on the destination computer.

Click Advanced to specify additional features.

Altiris Deployment Solution Reference Guide

174

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

Set Advanced options and click OK. Click Next.

Set Return Codes. See Setting Up Return Codes on page 185. This is optional.

Click Finish. You have now captured a personality setting and saved it as PCT file in the selected
location (most often in the PCT folder on the Deployment Server shared directory on the
Deployment Share). The Capture Personality task now displays in the Task list. See
Distributing Personality Settings on page 175.
Notes:

To capture a personality on a Windows 95, 98, or ME computer, make sure that all users have
Write access to the Deployment Server share (by default at C: Program
Files\Altiris\eXpress\Deployment Server in a Simple install). Also, make sure
that the User account and folder login boxes are blank. A user must also be logged on at the
client computer to capture the client profiles. An error will be returned if you attempt to
capture personality settings on Windows 9x computers that are not authenticated. It is
recommended that you don't capture personalities for mixed groups of Windows 9x and
Windows NT/2000/XP/2003 computers.

Set the conditions on the job for either Windows 95/98/ME or Windows NT/2000/XP/2003
computers to ensure that the appropriate Capture Personality task runs on the appropriate
computers.

Capture Personality Advanced


Domain users. Select this option to capture personality settings for all domain users on the computer.
Local Users.

Select this option to capture personality settings for all local users on the computer.

Custom. Specify users or groups to capture personality settings. Select the Custom checkbox and
enter the Users or Groups you want to capture personality settings. Also, instead of specifying
names, you can also select users that have been either created or last accessed in a specified number
of days.
Additional command-line switches.

You can add command-line switches specifically for the PC


Transplant program that migrates personality settings. See the Altiris PC Transplant Guide in the
docs folder of the Deployment Share.

Distributing Personality Settings


The Distribute Personality task allow you to save personal display and user interface settings defined
in the OS for each user. You will distribute Personality Packages to migrate personality settings.
This task will run Altiris PC Transplant from the console to capture and distribute settings.

Distribute personality settings using the New Job Wizard or adding the Distribute
Personality task when Building New Jobs. See Capturing Personality Settings to
create a Personality Package.

In the Name box, enter the file name and location of the PCT file.
Note: Information about the Personality Package will be displayed in the Description area for

valid Personality Packages (PCT files). If no description is displayed, then the file is not a valid
package.

If you use a token, such as %COMPNAME% in this field, and you proceed with the job, when
you apply the job to a Windows XP computer, the user must enter input before the job completes.
Altiris recommends you enter a valid Personality Package name and use the Additional commandline switches fields for token values. See the Altiris PC Transplant Pro Reference Guide for a
complete list of valid command-line switches.
2

In the Password box, type the password set for the PCT file when created.

Select Run in quiet mode to install the package without displaying the PC Transplant screens.

Altiris Deployment Solution Reference Guide

175

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

Specify the users to associate with the Personality Package.

Click Apply to all users to run the package for all users with accounts on the specified
computer.

If sending the package to a managed computer with multiple users and if you only want it
installed for certain users with a unique password, clear the Apply to all users box.
Example: to install a Personality Packages for a specific user accounts on a computer, add
values to the Additional command-line switches field:
-user: JDoe; TMaya; BLee
Note: The command-line switches are specifically for Personality Packages. For a complete

list of command-line switches, see the Altiris PC Transplant Pro Reference Guide.

Click Advanced to specify how Personality Packages are copied to the managed computer. You
can copy through Deployment Server, or copy and run directly from the Deployment Share or
from another file server. See Distribute Personality Advanced on page 176. This is optional.

Set Advanced options and click OK.

Click OK (if you are using the New Job Wizard).


or
Click Next.

Set Return Codes. See Setting Up Return Codes on page 185. This is optional.

Click Finish.

For more information about capturing a computer's personality settings, see the Altiris PC
Transplant Pro Reference Guide.
See also Distributing Software on page 172 and Modifying Tasks in a Deployment Job on
page 182.

Distribute Personality Advanced


Copy files using Deployment Server. Click this option to distribute software packages through
Deployment Server to the managed computer, requiring two file copy transactions if the
Deployment Share is on another file server. Use this option for Simple installs to take advantage of
security rights defined by Deployment Server. This is the default option.
Copy directly from file source.

Click this option to copy packages directly from the Deployment


Share, sending only one copy across the network. It will copy the file and then run it and avoid
running through Deployment Server and diminishing processor output. Because the Deployment
Agent doesn't recognize shared rights and is not guaranteed to have a mapped drive to the data
source, you will need to identify a user name and password for the data share computer from the
target computer. This option also requires a full UNC path name in the Source Path field in the Copy
File dialog box.
Run directly from file source.

another selected file server.

Click this option to run files remotely from the Deployment Share or

File Source Credentials. Enter the user name and password for the client computer and the
Deployment Share. Both must have the same user name and password (this is not an issue if both are
on the same domain).

Modifying Configuration
You can add a task to configure or modify the configuration of computer property settings using the
Modify Configuration dialog box. The Deployment Agent will update the property settings and then
restart the computer for changes to take effect.
1

After creating a job, double-click the job, and then click Add > Modify Configuration.

Select the Reboot after Configuration checkbox to restart client computer after the configuration
changes are complete. By Default, the checkbox for Reboot after Configuration is selected.

Altiris Deployment Solution Reference Guide

176

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

Enter or edit the property settings in the Configuration dialog box. Click the category icons in the
left pane to set additional values for each property setting group. See Computer Configuration
Properties on page 111.

Click Next.

Set Return Codes. See Setting Up Return Codes on page 185. This is optional.

Click Finish.

See also Modifying Tasks in a Deployment Job on page 182.

Backing up and Restoring Registry Files


Copy registry files of selected computers using the Back up Registry task and save the registry file
settings to a selected directory. You can also create a Restore Registry task to copy the registry
settings to a managed computer.

Copy registry settings by adding the Back up Registry task when Building New
Jobs. Restore registry settings by adding the Restore Registry task.

Enter the directory path to back up or restore registry files.

Select the required pre-boot environment from the Automation - PXE or Bootworks environment
(DOS/Windows PE/Linux) drop-down list to perform the Backup and Restore task in selected preboot environment. The option reported by the PXE Manager is the default pre-boot environment
option.

Select the required pre-boot environment from the Automation - PXE or lets you environments
(DOS/Windows PE/Linux) drop-down list to perform the Backup and Restore task in selected preboot environment. The option reported by the PXE Manager is the default pre-boot environment
option. By default the DOSManaged Boot Option type will be selected.

Click Advanced if Windows was installed on client computers in a directory other than the
default. Enter the correct path to the root of the Windows directory.

Select Include registry information for all users to back up registry keys for all user accounts.
Note: If you clear this checkbox, then only the Administrator and Guest user accounts will

be backed up or restored.

Click Next.

Set Return Codes. See Setting Up Return Codes on page 185. This is optional.

Click Finish.

See also Modifying Tasks in a Deployment Job on page 182.

Get Inventory
Use this task to gather inventory from an individual or group of client computers. This ensures that
the Deployment database is up-to-date with the latest computer properties information. You can
view the history of the Get Inventory task in the Computers History pane. See Viewing a
Computers History on page 136.

Click Add, and then select Get Inventory from the list.

Run Script
Select an existing script or write a new script file to run on selected managed client computers.

Altiris Deployment Solution Reference Guide

177

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

Run script files on client computers by adding the New Script task when Building
New Jobs. See Script Information to identify how the script displays, script
security, and an option for server-side execution of the script.
1

If you have a script file defined, click Run the script from file and then browse from the folder icon
to select the file. To read or edit the script file, click Modify.
Note: To run scripts that call an executable, use the start command.

Example: start c:\windows\notepad.exe opens the Notepad application on the client


computer.
2

To create a new script, click Run this script. Type the script in the provided text box, or click
Import and select a script file to import. When a script is imported you can modify it in the text
box.

Specify whether the script should be run from DOS, Windows, or Linux.

Click Next.

Set Script Information. See Script Information on page 178.

Click Next.

Set Return Codes. See Setting Up Return Codes on page 185. This is optional.

Click Finish.

Notes:

When a computer is in automation mode using a DOS configuration, it does not see DOS
partitions. To run a script using the DOS Automation Agent, use FIRM (File-system Independent
Resource Manager) commands. FIRM can only copy files and delete files; it cannot run code on
a drive.

Deployment Server assumes a return code of zero (0) as a successful script execution. Some
programs return a code of one (1) to denote a successful script execution. If a program returns a
one (1), you will see an error message at the Deployment console even though the script ran
correctly. To modify the return codes, you can edit the script file to return a code that the console
interprets correctly.

See also Modifying Tasks in a Deployment Job on page 182.

Script Information
Click an option to run the script on a selected managed computer or to run the script on the
Deployment Server computer.
Script Run Location
On the client computer. The option runs the script on the managed computer to which you assign the

job.

Locally on the Deployment Server. This option runs a server-side script on the Deployment Server of

the managed computer. In most cases you will want to create a server-side script task that runs in
context with other tasks. Example: you can add a task to image a computer and then add a task to
execute a server-side script to post the imaging return codes to a log file stored on the Deployment
Server computer.

Use the -id switch for running scripts on Deployment Server when using the WLogEvent and
LogEvent utilities. See Using LogEvent and WLogEvent in Scripts on page 180.
Important: Scripts requiring user intervention will not execute using this feature. The script will run

on the Deployment Server of the managed computer, but will not be visible. Example: if you run a
DOS command locally on the Deployment Server, the Command Prompt window will not open on
the Deployment Server computer when the script executes.

Altiris Deployment Solution Reference Guide

178

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

When running the script on the Deployment Server, it will execute specifically for the assigned
managed computer. Example: if you create a job with a script to run locally on the Deployment
Server and assign the job to 500 computers, then the script will run on the Deployment Server 500
times.
Client Run Environment

Select the environment for your client. You can run in either production or automation mode.
Production - Client-installed OS (Windows/Linux).

Linux production environment.


Security Context.

Click this option to run the script in a Windows or

This identifies the security options for running scripts.

Default (local system account).

managed computers.

Use the network security account established to administrate all

Specific user. If you have selected to run the task on the local Deployment Server, you are
required to enter an administrator user name and password for that Deployment Server account.
(In most cases Deployment Server does not have the Deployment Agent installed, prohibiting it
from using a network security account.)
Script Window. This determines how the Script Window displays when
Minimized, Normal, Maximized, or Hidden from the drop-down list..

the script runs. Select

Script Options - (Windows/Linux)


Additional command-line switches.

runs in Windows or Linux.

Enter in commands that you want to execute when the script

Automation - PXE or Bootworks environment (DOS/Windows PE/Linux). Click to run the script in the
automation environment. Select a pre-boot automation environment from the drop-down list.

If you select Linux as the OS type, then the Locally on the Deployment Server option will be disabled
and only the Additional command-line switches under the Production Client installed OS(Windows/
Linux) will be enabled.
If you select DOS as the OS type, then the Locally on the Deployment Server option and the Production
- Client-installed OS (Windows/Linux) option will be disabled.
Example Script
The process to convert NT4 from FAT16 to NTFS normally returns a 1 after a successful
completion. Here is an example of the file that is modified to return a code of 0 (which is the success
code recognized by the Altiris Console and utilities). You can make similar changes to your script
files as needed.
CONVERT /FS:NTFS
if ERRORLEVEL 1 goto success
goto failure
:success
set ERRORLEVEL = 0
goto end
:failure
echo Failed
set ERRORLEVEL = 1
goto end
:end

Altiris Deployment Solution Reference Guide

179

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

Using LogEvent and WLogEvent in Scripts


The logging features, LogEvent and WLogEvent, accommodates detailed logging to help debug
complex scripts. These utilities include the following features:

Logging will be stored in the database instead of a log file.

A DOS-based tool can be called from any script file to log status and error codes.

The console displays and works with the new status messages.

LogEvent posts status messages back to the Deployment Console, allowing you to view the status
of the script. It is a light-weight reporting tool that can log both status strings and status codes to the
history file and the console.
LogEvent

Use the LogEvent utility for DOS and Linux scripts.

WLogEvent

Use the WLogEvent utility for Windows scripts.

The LogEvent and WLogEvent utilities are command-line driven only there is no user interface.
Use both utilities with the following switches.
LOGEVENT -c:code -id:%ID% -l:level -ss:message
code is any number for a return code level.
id

is used for server-side scripting only. For server-side scripts you must add the -id:%ID% switch.

See the Locally on the Deployment Server option on Script Information to select a server-side script.
level is the severity level. The following levels are used:

1 = Information message
2 =Warning message
3 = Critical failure message. Only this level can be used to set up a return code. See Setting Up
Return Codes on page 185. The response will not execute for a return code unless a level 3 is
specified when using the LogEvent and WLogEvent command in a script.
message is the status string. If spaces exist in the message, then the string must be contained in

quotes. Specifying a severity level of 3 will cause the script job to fail.
Example Scripts

REM Bootwork unload


Set ImageName=F:\Images\XPIntel.img
rdeploy -mu -f%ImageName% -p1
logevent -l:1 -ss:Created %ImageName.
REM Execute WLogEvent.exe from CMD script
REM This script requires WLogevent.exe to reside on the client
REM in the temp directory
.\WLogevent.exe -c:0 -l:1 -ss:"Running Dir on %NAME%"
dir
.\WLogevent.exe -c:0 -l:1 -ss:"Finished with the DIR command on %NAME%"

Copy File to
Copy all types of files to managed computers. You can send selected files or directories to a
computer or computer group. If a full path is not provided the file copy is relative to the system folder
on the managed computer.

Altiris Deployment Solution Reference Guide

180

Chapter 6: Building and Scheduling Jobs

Deployment Tasks

Send files to client computers by adding the Copy File to task when Building New
Jobs. Use the Copy File to operation (see the Remote Operations Using
Deployment Solution menu) to copy files quickly from Computers pane in the
console.
1

Click either the Copy File or Copy Directory option. Click Copy Subdirectories to copy all
subdirectories.

Enter the directory path and name of the file or directory. The Source path defaults to the
Deployment Share, but you can type or browse to a file or directory.
To copy files or directories through Deployment Server from the Deployment Share, you can
enter a relative path in this field. To copy files or directories directly from the Deployment Share
to the managed computer, you must enter the full UNC path name (see Copy File to Advanced
on page 181 features).
Note: When entering the source path for copying files through the Deployment Server, you can

only access the shared directories through an established user account. Specifically, you can only
use UNC paths when you have sufficient authentication rights established.

Type the destination path. The Destination path field automatically enters a sample path, but you
can enter the directory path that you require. If the destination path does not exist on the
destination computer it will be created.

Click Advanced to specify additional features to copy files through Deployment Server or
directly from a file server. See Copy File to Advanced on page 181.

Click Next.

Set Return Codes. See Setting Up Return Codes on page 185 (Optional).

Click Finish.

See also Modifying Tasks in a Deployment Job on page 182.


Using Location Variables
Location variables are being added to Deployment Server for the Copy Files feature, allowing you
to enter a token variable rather than requiring a complete location path when copying files to a
managed computer (a client computer running the Deployment Agent). The current variables
include:
Temp. Enter Temp in the Destination path to set the Temp directory (identified in the system path)
for the managed computer. Example: instead of entering C:\windows\temp\setup.exe in the
Destination path, just enter temp:setup.exe.

Copy File to Advanced


Select options to copy files directly from the Deployment Share. This option is for files stored on
another network server in a distributed Deployment Server installation.
Copy files using Deployment Server. This option distributes software packages through Deployment
Server to the managed computer, requiring two file copy transactions if the Deployment Share is on
another file server. Use this option for Simple installs to take advantage of security rights defined by
Deployment Server. You can use a relative path name entered in the Source Path box in the Copy
Files dialog box. This is the default option.
Copy directly from file source.

Click this option to copy packages directly from the Deployment


Share, sending only one copy across the network. It will copy the file directly to avoid running
through Deployment Server and diminishing processor output. Because the Deployment Agent
doesn't recognize shared rights and is not guaranteed to have a mapped drive to the data source, you
will need to identify a user name and password for the data share computer from the target computer.
This option also requires a full UNC path name in the Source Path field in the Copy File dialog box.

File Source logon.

Enter the user name and password for the client computer and the Deployment
Share. Both must have the same user name and password (this is not an issue if both are on the same
domain).

Altiris Deployment Solution Reference Guide

181

Chapter 6: Building and Scheduling Jobs

Modifying Tasks in a Deployment Job

Note: Windows 95/98/ME computers have security limitations when copying files directly from the

source to the Deployment Agent using the UNC path name. It is suggested that you use the Copy files
for these types of computers or plan a proper security strategy for
direct copying.

using Deployment Server option

Power Control
Start the computer using Wake-on-LAN or run standard power control options to restart the
computer, shut down, or log off the current user.

Wake up, shut down or log off client computers by adding the Power Control task
when Building New Jobs. See the Power Control operation to send commands
quickly from the console.
1

Create a job.

Click Add > Power Control.

Select an option: Restart, Shut down (if available), Log off or Wake up (Send Wake-On-LAN).

Select Force application to close without message, if applicable.

Click Next.

Set Return Codes. See Setting Up Return Codes on page 185 (Optional).

Click Finish.

Modifying Tasks in a Deployment Job


You can build jobs by adding or modifying deployment tasks. When you modify the tasks in a job,
any computer already scheduled to run the job will run the modified job.
To add a task to a job immediately
If the task (image, batch file, executable, etc.) is saved in the product directory, it displays on your
Resources list in the Shortcuts pane. Simply drag it to an existing job and it will be added
To add a task to a job
1

Double-click the job you want to modify in the Jobs pane.

Click Add and select another task from the menu.

Follow the basic instructions on each dialog box provided for each task. Select the type of task
you want to add and follow directions.

After finishing task configuration, a new task displays in the Jobs list.

Change the order of the tasks using the Up and Down arrow buttons. The tasks will execute in
the order listed.

To copy and paste a task


Use the steps below to copy and paste tasks within the same job, or from one job to another. You can
use CTRL+C and CTRL+V to copy and paste tasks.
1

Click the job that contains the task you want to copy in the Jobs pane.

In the Details pane, right-click the task, and then select Copy Task. (To copy multiple tasks,
press the CTRL key and select the desired tasks. The tasks that are highlighted will be copied
when you select Copy Task.)

In the Jobs pane, click the destination Job where you want to paste the task.

Altiris Deployment Solution Reference Guide

182

Chapter 6: Building and Scheduling Jobs

Modifying Tasks in a Deployment Job

Right-click in the Details pane and select Paste Task. The tasks displays at the bottom of the
task list, and will use the use the condition settings of the current job.

Change the order of the task using the Up and Down arrow buttons. The tasks will execute in the
order listed.

To modify a task in a job


1

Double-click the job you want to modify in the Jobs pane.

Select the desired task from the list.

Click Modify and follow directions to make your changes. Click OK.

To remove a task from a job


1

Double-click the job you want to modify in the Jobs pane.

Select the task you want to remove from the task list.

Click Delete. Click OK.

To copy and paste tasks


Use the steps below to copy and paste tasks within the same job or from one job to another. You can
also use CTRL+C and CTRL+V to copy and paste tasks.
1

Click the job that contains the task you want to copy in the Jobs pane.

In the Details pane, right-click the task, and then select Copy. (To copy multiple tasks, press the
CTRL key and select the desired tasks. The tasks that are highlighted will be copied when you
select Copy.)

In the Jobs pane, click the destination Job where you want to paste the task.

Right-click in the Details pane and select Paste. The tasks displays at the bottom of the task list
and will use the current condition settings of the destination job.

Change the order of the task using the Up and Down arrow buttons. The tasks will execute in the
order listed.

To add a new task to an existing task list


1

Select a job from the Jobs pane.

Click on one of the tasks within the job, and then add a new task. The new task is inserted above
the task you highlighted, and all other jobs shift down one position.

Use the Up and Down buttons to change the order of the tasks within the job.

Modifying Multiple Change Configuration Tasks


If you have scheduled multiple Modifying Configuration tasks to a computer group, you can doubleclick Change Configuration in the task list of the Details pane to modify each computers
configuration settings independently.
1

Click the job in the Jobs pane with a Change Configuration task. Double-click the Change
Configuration task.
A message box will open. Click YES to modify configuration settings individually for each
scheduled computer. Click NO to modify the Change Configuration task when the job is
scheduled again (the current job will send modified configuration files already created).
If you click YES, then a Modify Job wizard will open with a list of each managed computer
scheduled to change configuration settings. Select one or more computers and click Next.

In the Computer Configuration Properties property page, modify settings. Click Next.

Set Return Codes. See Setting Up Return Codes on page 185.

Click Finish.

Altiris Deployment Solution Reference Guide

183

Chapter 6: Building and Scheduling Jobs

Creating New Script Files

Creating New Script Files


You can create script files and directly schedule the script file to run scripts on any computer or
computer groups.
To create new script files
1

Go to View > Shortcuts View.

Click Resources in the Shortcuts view to move the focus to the Resources view.

Go to File > New > Script File.


Note: The Script File option will be activated only if the focus is on the Resources view.

A script file is created by default at the root of the resources. The default file name is Batch.bat.
4

Right-click the Batch.bat file, and select Modify.


Note: You can rename the batch file, by right-clicking the file, and selecting Rename.

Type the script in the open file, and save it.

Drag the Batch.bat file to a computer or computer group where you want to schedule the job.

Specify the scheduling options, and click OK. See Scheduling Jobs on page 160.

Copy and Paste Jobs and Job Folders


Jobs or job folders (including their subfolders) can be copied to any other job folder in the treeview
of the Jobs pane of the Deployment Console. A Job folder can only be copied to a root level folder,
which has a limit of 30 subfolders, and cannot be copied to a child level folder.
If you copy a job or folder with the same name as the destination job or folder, the copied job or
folder is automatically named Copy of <job or folder name>. This feature can only be performed by
administrators or users who have been granted permissions to create jobs, or job folders.
To copy jobs and job folders
1

In the Jobs pane, right-click on a job or job folder that you want to copy, and then click Copy.

Right-click on the destination job folder in the Jobs pane, and then click Paste.

Importing and Exporting Jobs


Jobs can be exported to back up Deployment Server data or to share jobs between Deployment
Server installations.
To import jobs
1

Right-click in the Job pane, and select Import


or
Click File > Import/Export > Import Jobs.

Browse to or type the path and name of an existing import file (a BIN file).

Select Import to Job Folder to import the jobs to an existing folder in the Jobs pane. If you have
a folder already selected it displays in the edit field.

Select Overwrite existing Jobs and Folders with the same name to replace identical jobs and folders.

Select Delete existing jobs in folder to overwrite and replace all jobs in the selected Jobs folder.
Click OK to import the job(s).

To export jobs
1

Right-click the job or Jobs folder you want to export and select Export
or

Altiris Deployment Solution Reference Guide

184

Chapter 6: Building and Scheduling Jobs

Setting Up Return Codes

Click File > Import/Export > Export Jobs.


2

Select the destination folder and enter a file name.

Click the Export subfolders button to export all folders subordinate to the selected job folder.

Click OK.

Setting Up Return Codes


When you create a task in a job, you can define a response to specific return codes generated from
that task after it runs. You can determine the response if the task runs successfully or if the task fails.
You can also set up custom return codes generated from scripts or batch files that are unique to your
environment or deployment system.
Note: Return code handling cannot be set up for jobs created in the New Job Wizard.

When creating a task, the Return Codes dialog box displays so you can set a response if the task was
successful or to determine a default response if the task failed. Because Deployment Server returns
a 0 (zero) if the task runs successfully, any other return code value denotes some type of failure in
running the task. As a result, in the Success box you can select an action if the return code is 0 (zero),
or select an action in the Default box if the return code is not a 0 (zero).
Return codes are first evaluated to be successful (zero) or failed (non-zero). If the task returns as
successful, then it will run the action in the Success box. If it is not successful, then it determines if
the return code has been assigned a custom code value. If the return code is defined as a custom code,
then the selected action for that custom code is executed. If no custom code is assigned to the return
code, then the action set in the Default is executed.
Note: If Using LogEvent and WlogEvent in Scripts, you can only generate return codes when the

level 3 message is specified. Specifying a severity level 3 will cause the script job to fail and allow
you to respond using this return code feature.
Return Code Actions
For both successful tasks (in the Success box) and failed tasks (in the Default box), you can
determine these specific actions:

Stop.

This action will stop the job after the task runs. Subsequent tasks will not run.

Continue.

This action will continue with subsequent tasks in the job after the task runs.

Select a job.

This action will allow you to select existing jobs to run after the task completes.

These actions also apply to custom return codes designed specifically for your system.
Custom Return Codes
In the Other return codes area, you can view custom return codes set specifically for your system.
You can add return codes by clicking the Add button below the Other return codes area, or by clicking
the Master Return Code button.
Type a custom code in the Code box, select a response action from the Response list, select the status
from the Status list to specify the interpretation of this return code as Success or Failure, and provide
a message in the Message box. These custom codes can respond to any return codes set up in scripts
or batch files in the Run Scripts task, or these custom codes can respond to system return codes
thrown from Deployment Server or external codes generated when distributing applications,
personality settings, or disk images. Any task can have custom codes that respond to different return
code values.
Master Return Codes. This is a list of all the return codes existing in the Deployment database. You
can add, modify, and delete the codes and their values so that setting codes for other tasks is easier.

This allows you to add a new custom return code for the task. You can also choose to add the
return code to the Master Return Codes list.

Add.

Altiris Deployment Solution Reference Guide

185

Chapter 6: Building and Scheduling Jobs

Sample Jobs in Deployment Solution

Modify. This allows you to modify the return codes listed in the Other return codes area. The changes

you make do not update the Master Return Codes list.

This allows you to delete return codes listed in the Other return codes area, but not from the
Master Return Codes list.

Delete.

To set up return codes


To set up return codes, you need to determine how to respond to the Deployment Server success
return code (zero) in the Success box, how to respond to a failure return code (a non-zero) in the
Default box, and how to respond to a custom or externally generated return code defined in the Other
return codes box.
The example below describes how to set up a simple process to deal with custom and system return
codes, and how to interpret the status of user defined return codes:
1

In the Success list box, keep the default value Continue. This allows the job to continue running
additional tasks in the job after successfully completing this task.

Click Add to add custom return codes. The Add Return Code dialog box displays.

In the Code box, enter a value of 10 (ten).

Click the Response drop-down arrow and select Continue from the list.

Click the Result drop-down arrow and select Success from the list. This displays that even if the
return code was not zero, success by default, the task will be considered a success as per users
choice.

Enter a description for the return code in the Status field. This is the message that will be
displayed when the task, within a selected job, executes.

Select the Add to Master return code list checkbox to add the custom code to the master return code
list. The code is then listed in both, the Other return code and Master Return Codes list. This is
helpful if you want to use the return code again.

Click OK. The return code is added to the list of Other Return Codes.

If the code you added already exists, a message dialog box displays the return code and asks if
you want to replace it. Click Yes to replace the return code, and click No to return to the Add
Return Code dialog box.

10

Select Select a job from the Default box to select a job to be executed when a default condition is
reached. The Select a Job dialog box opens, allowing you to select an existing job that runs if the
task returns a failed system return code (non-zero) or a return code not defined as a custom return
code.

Note: The status of the tasks executed in a job is also displayed in the history of a computer.

Sample Jobs in Deployment Solution


Sample jobs are installed with each Deployment Server system, allowing you to quickly modify or
add parameters, or to run the sample jobs as they are. During installation, jobs are automatically
imported from the samples.bin file to the Deployment Server system where they can be viewed
in the Samples folder in the Jobs area of the Deployment console. Click each job and identify its
features in the Description field of the Details pane.
Jobs in each folder marked with an asterisk (*) require input parameters or other minor modifications
added before running on your system. These modifications allow you to add parameters to the job,
such as user name and password or other required data for the job to be functional. Jobs requiring
input parameters or customizing will not function properly if you do not edit the job with the
information specific to your environment.
All files without an asterisk (*) can be used to perform the identified functions without modification.
However, if the job conditions are not met or are not consistent with the computer type, then you
may get an error. Example: if the Repair Office XP job runs on a computer without MSOffice XP, then
you will get an error when running the job.
Note: When upgrading versions of Deployment Solution, it is suggested that you copy and rename

modified sample jobs to avoid overwriting with new sample jobs.

Altiris Deployment Solution Reference Guide

186

Chapter 6: Building and Scheduling Jobs

Altiris Deployment Solution Reference Guide

Sample Jobs in Deployment Solution

187

Chapter 6: Building and Scheduling Jobs

Altiris Deployment Solution Reference Guide

Sample Jobs in Deployment Solution

188

Chapter 7:

Managing Deployment Servers


This section provides basic reference information when deploying and managing Thin Client
computer, including:
Deploying and Managing Servers (page 189)
Find a Computer in the Database (page 194)
Using Lab Builder (page 195)

Deploying and Managing Servers


Deployment Solution provides additional features to remotely install, deploy and manage network
and web servers. From the Deployment Server Console, you can configure new server hardware,
install operating systems and applications, and manage servers throughout their life cycle. And
because servers are mission-critical, you can set up a system to quickly deploy new servers or
automatically re-deploy servers that have failed. Features like rules-based deployment, support for
remote management cards, and quick server restoration from a deployment history give you new
tools to manage all servers throughout your organization.

Servers are identified in the Computer pane with distinctive server icons. Like all
managed computer icons, the icons change to identify the status and state of the
computer, such as user logged on or Server Waiting.
Note: Servers are recognized by their operating system (such as Windows 2000
Advanced Server, Windows Server 2003, or any Linux OS), multiple processors, and
specific vendor server models.

Manage Servers from the Console. The Deployment Server Console includes features specifically
designed for deploying and managing servers, such as enhanced task logging and history tracking
features to let you recall administrative actions and quickly redeploy mission-critical servers. See
Server Management Features on page 189.
Set Server-specific options. Servers are essential to any organization and require special planning
and management strategies. Deployment Server provides server-specific features to automatically
deploy new servers and maintain existing servers. See Server Deployment Options on page 190.

Server Management Features


Deployment Server provides various features for deploying and managing servers. These features
are supported for client and handheld computers as well, but are essential in deploying servers.

Altiris Deployment Solution Reference Guide

189

Chapter 7: Managing Deployment Servers

Deploying and Managing Servers

Server icons. The Deployment consoles display icons to identify servers across the network. Like
other computer icons in the console, server icons can be selected to view server properties or assign
specific jobs and management tasks

Icon

Description
Indicates a server is active and a user is logged on.

Indicates a server is disconnected from the console.

Indicates a server is in a waiting state.


Run Scripted Installs. Execute scripted, unattended installs across the network for both Microsoft
Windows and Linux servers. Follow steps to create answer files and set up OS install files using a
wizard. See Scripted OS Install on page 167.
Support for multiple network adapter cards. Because servers may require more than one network

interface card, Deployment Server provides property pages to access and configure multiple network
adapters remotely from the console. See TCP/IP Configuration Settings on page 114.

Synchronized server date and time. Deployment Server automatically sets the servers date and
time after installing or imaging (as part of the configuration process). Deployment Agents include
an option to disable this feature (it is off by default).
Enhanced scripting capabilities. You can deploy multiple tasks per deployment job and boot to
DOS multiple times when configuring and deploying a clean server. Deployment Server also lets
you view and debug each step in the deployment script, and track each job to provide a history of
tasks for redeploying a server.

Server Deployment Options


Deployment Server includes features to automatically reconfigure and redeploy new servers. If you
are using Initial Deployment to automatically re-image new servers or run installation scripts, you
can (1) safeguard against mistaken disk overwrites, or (2) run automatically for every server not
identified as a managed computer in the database. These contrasting settings are based on polices
that you define for managing servers in your organization.
For example, if you rely on PXE to boot the new server and you want to deploy new servers
automatically without halting the process, you must change the default settings in the PXE
Configuration Utility. In contrast, if you want to ensure that the server waits before being deployed
(or waits a set time before proceeding) to avoid erroneous re-deployment, you need to set the options
in the Advanced section of Initial Deployment.
Halt the Initial Deployment of Servers
When a server boots from the PXE server or from BootDisk (if the option is set), Deployment Server
recognizes it as a new computer and will attempt to configure the computer with Sample Jobs in
Deployment Solution. Initial Deployment includes a feature to prohibit servers from being deployed
automatically.
1

Click Initial Deployment and select Properties.

Click the Advanced tab.

Click the Servers check box and click OK.

Initial Deployment will not run for any computer identified in the console as a server.

Altiris Deployment Solution Reference Guide

190

Chapter 7: Managing Deployment Servers

Deploying and Managing Servers

Change PXE Options for Initial Deployment


If installing a server using a PXE Server, the server will attempt to install but will not run
automatically using default settings. It will wait until a boot option is selected from the client
computer. You can change the default setting in the PXE Configuration Utility to allow Initial
Deployment to run automatically and not sit at the prompt.
1
2
3

Click on Start > Programs > Altiris > PXE Services > PXE Configuration Utility.
Click Altiris BootWorks (Initial Deployment). Click Edit.
Select Execute Immediately.
Initial Deployment will run automatically for every identified server.

Click OK.

Clear BootWorks Prompt for Remote Install


When you run a deployment job on a computer where the Deployment Agent has been remotely
installed, a message will appear stating that no BootWorks partition or PXE stamp is found. The
message will stay open until the user clicks OK on the message dialog, which delays executing the
scheduled job as part of an automated redeployment process. To fix this delay:
1

Select Tools > Options.The Altiris Program Options dialog will open.

Select the Agent Settings tab.

Select the Change Default Settings button.

Select the BootWorks tab.

In the lower section, select Never prompt me from the list.

Click OK.

Following these steps will assure that the BootWorks message will not come up and things will move
forward when a job is scheduled.

Managing Server Blades


Deployment Solution allows you to manage high-density server blades with Rack/Enclosure/Bay
(R/E/B) hardware and properties. From the Deployment Console you can deploy and manage these
space-efficient server blades using the physical view to assign jobs to the Rack, Enclosure, or Bay
level of the server cluster, or you can manage each server blade directly from the logical view. See
Bay on page 133 for properties and rules to deploy Rack/Enclosure/Bay servers.

Using Deployment Solution, you can employ rip and replace technology that allows you to insert
a new server blade and automatically configure and deploy it exactly like the previously installed
server blade, allowing you to replace any downed server and get it back on line quickly. Altiris
provides fail-safe features to ensure that no server is mistakenly overwritten and ensures that all disk
images, software, data, and patches are applied to the new server from the history of jobs assigned
to the previous server blade.

Managing New Server Blades


Deployment Solution allows you to automatically deploy, configure and provision new server blades
using a variety of features, including Sample Jobs in Deployment Solution, Virtual Bays, and Server
Deployment Rules.

Altiris Deployment Solution Reference Guide

191

Chapter 7: Managing Deployment Servers

Deploying and Managing Servers

New Server Blades in Newly Identified Bays


When new blades are identified in a Bay that has not been used previously (if it has been used
previously then the Bay object will be identified in the physical view), then both the Sample Jobs in
Deployment Solution and Virtual Bays features can be set up to automatically run configuration
tasks and deployment jobs.
To Create Virtual Bays: Set up Virtual Rack/Enclosure/Bays for Hewlett-Packard Rapid
Deployment Pack installations of Deployment Solution.
Initial Deployment set up: Clear the Servers check box in the Advanced dialog box.
If both new computer features are set up and a new server blade is installed in a Bay not previously
identified by the Deployment Server, then the Create Virtual Bay feature will execute and Initial
Deployment will not execute.
New Server Blades in Identified Bays
If a new HP server blade is installed in an identified Bay (one that has already had a server blade
installed and is visible from the Deployment Console), then both Sample Jobs in Deployment
Solution and Server Deployment Rules can be set up. However, when both are set up then the Server
Deployment Rules will execute and Initial Deployment will not execute.

Hewlett-Packard Server Blades


Hewlett-Packard high-density blade servers can be deployed and managed from the Deployment
console. The following HP server blades are supported:
HP Proliant BL e-Class

HP Proliant BL p-class

Proliant BL 10e

Proliant BL 20p

Proliant BL 10e G2

Proliant BL 20p G2
Proliant BL 40p

HP blade servers allow you to employ all features provided in the Deployment Console when you
install the HP Proliant Essentials Rapid Deployment Pack (see www.hp.com/servers/rdp), including
the Virtual Blade Server feature. The name of each Rack for an HP Server is displayed along with
the assigned name for the Enclosure and Bay. These names are collected from the SMBIOS of the
server blade and displayed in both the physical and server views within the Computers pane of the
Deployment console.
For HP blade servers in the physical view the Rack name can be a custom name in the console, with
all subordinate Enclosures and Bays also identified. For example:
<rackName>
<enclosureName>
<bayNumber>

See also Server Management Features on page 189 and Server Deployment Options on
page 190.

Virtual Bays
Blade servers now have a Virtual Bay feature that allows you to pre-assign deployment jobs to the
rack, the enclosure, or to a specific server blade in the bay. Any blade server can have predefined
deployment jobs and configuration tasks associated with it to execute automatically upon
installation. The Virtual Rack/Enclosure/Bay icons will change from virtual icons to managed server
icons in the Deployment console as live blade servers are inserted and identified by Deployment
Solution.
Rack name.

Enter or edit the name of the Rack.

Enclosure name.

Enter or edit the name of the Enclosure.

Altiris Deployment Solution Reference Guide

192

Chapter 7: Managing Deployment Servers

Enclosure type.
Initial Job.

blade.

Deploying and Managing Servers

Select the type of HP server blade from the list.

Select an existing job to run when the virtual computer is associated with a new server

Server Change rule. Select the Server Deployment Rules to run on the Bay when a new server blade

is installed.

Note: If you create Virtual Bays for an enclosure (such as the BLe-class with 20 bays) and then if

another model of server blade with an enclosure containing fewer bays is connected (such as the
BLp-class with 8 bays), then the excess virtual bays will be truncated automatically. Conversely, if
you create Virtual Bays with fewer bays (8) and then install an enclosure with additional bays (20),
you will need to recreate the virtual bays in the enclosure (right-click the enclosure name in the
physical view and click New Virtual Bays).

See also Managing New Server Blades on page 191.

Dell Server Blades


Dell high-density blade servers can be deployed and managed from the Deployment console. All
Dell Rack Servers are supported by Deployment Solution, but the server blades can also be managed
from the physical view in the Rack/Enclosure/Bay view. The following servers are supported:
Dell Rack Servers

Dell Server Blades

All PowerEdge rack servers

PowerEdge 1655MC

For Dell blade servers in the physical view, the Rack name will always be Dell. All subordinate
Enclosures and Bays are identified with custom names under the Dell rack name. For example:
Dell
<enclosureName>
<bayName>

See also Server Management Features on page 189 and Server Deployment Options on
page 190.

Fujitsu-Siemens Server Blades


Fujitsu-Siemens high-density blade servers can be deployed and managed from the Deployment
console. All Fujitsu-Siemens Rack Servers are supported by Deployment Solution, but the server
blades can also be managed from the physical view in the Rack/Enclosure/Bay view. The following
servers are supported:
Fujitsu-Siemens Rack Servers

Fujitsu-Siemens Server Blades

All Primergy rack servers

Primergy BX300 blade servers

For Fujitsu-Siemens blade servers in the physical view, the Rack name will always be FujitsuSiemens. All subordinate Enclosures and Bays are identified with custom names under the FujitsuSiemens rack name. For example:
Fujitsu-Siemens
<enclosureName>
<bayName>

See also Server Management Features on page 189 and Server Deployment Options on
page 190.

IBM Server Blades


IBM high-density Blade Centers can be deployed and managed from the Deployment console. All
IBM blade servers are supported by Deployment Solution, but the server blades can also be managed
from the physical view in the Rack/Enclosure/Bay view.

Altiris Deployment Solution Reference Guide

193

Chapter 7: Managing Deployment Servers

Find a Computer in the Database

For IBM blade servers in the physical view, the Rack name will always be IBM. All subordinate
Enclosures are identified with custom names under the IBM rack name and Bays are identified by
number. For example:
IBM
<enclosureName>
<baynumber>

See also Server Management Features on page 189 and Server Deployment Options on
page 190.

Find a Computer in the Database


This search filter allows you to type a string and query specified database fields for specific
computer properties. You can search for user or computer names, licensing or location information,
or primary lookup keys: MAC address, serial number, asset number, or UUID. This search filter
queries property values displayed in the Computer Properties on page 131 pages.

Click <CTRL> F or click the Find Computer button on the console toolbar to
search the Deployment Database for computers by property settings.
The computers that match the search will be highlighted in the Computers pane.
1

In the Search For box, type all or part of the computers property values that you would like to
search for. This alpha-numeric string will be compared with specified database fields.

In the In Field box, select the field that you want to search in the Deployment Database.
For example, to find a computer by searching for its IP address, type the address in Search For
field and then select IP Address from the In Field drop down list.

Name

BIOS name of the computer.

Computer Name

Deployment Solution name of the computer.

MAC Address

0080C6E983E8, for example.

IP Address

192.168.1.1, for example.

ID

The computer ID. 5000001, for example.

Serial Number

Serial number installed in BIOS. A primary lookup key.

Asset Tag

Asset number in BIOS. A primary lookup key.

UUID

A primary lookup key.

Registered User

Name entered when OS was installed.

Product Key

Product Key for the operating system.

Logged On User

Name of user currently at the computer.

Physical Bay Name

The actual bay number: 7x, for example.

The computer you are looking for will be displayed and highlighted in the Computers window in the
console.
Note: This search is not case-sensitive and allows wildcard searches using the *.

See also Computer Filters and Job Conditions on page 94.

Altiris Deployment Solution Reference Guide

194

Chapter 7: Managing Deployment Servers

Using Lab Builder

Using Lab Builder


Use the Lab Builder to set up jobs under the Lab folder in the Jobs pane to set up a classroom or lab
environment.

Click the Lab Builder button on the console toolbar or click File > New > Lab
Builder to set up jobs specifically created for managing multiple computers in a
lab environment.
You can set up jobs to:

Create Disk Image

Deploy Lab

Restore Lab

Update Configuration

Upload Registries

Each of these jobs contains a default list of tasks. Lab Builder places these five new jobs under a
folder (which you name) located under the Lab folder. All of the tasks in the jobs have been assigned
default paths and file names that allow them to use the same images and configuration information,
registry data, etc. It is suggested that you do not change the file names and paths. If you change the
default settings (for example, changing the image name), you must change it in all of the jobs where
the image is used.
To use Lab Builder
1

Click the Lab Builder icon on the toolbar, or choose File > New > Lab Builder.

Enter the name of the lab setup.


Note: The lab name must be unique because the program creates a default image file name based

on the name, and the image file name must be unique. The default image name is synchronized
in all of the lab jobs, so if you change the name later you must change it in all the jobs that use
the image.

Enter a lab description to help you differentiate the lab from others. This field is optional. Click
OK. This is optional.

Identify an image in the Create Disk Image job.

Set computer names and addresses in the Update Configuration job.

The following information describes the default jobs. To run one of these jobs, simply drag it to the
computer or computer group that you want it applied to.
Create Disk Image.

This job uploads an image of a computer to the server and an image name is
created automatically based on the lab name. However, there is no actual image in the job until you
drag the image source computer to this job.

Deploy Lab. This job has three default tasks: Deploy image, Apply configuration settings, and Back
up registry files. The image that is uploaded using the Create Disk Image job is deployed when you
use this job. The configuration settings you specify in the Update Configuration job are applied to
the computers, and then the computer registry files are uploaded to the Deployment Server.
Restore Lab. This job restores the image and registry files to a computer where a lab was previously
deployed. You can quickly get a computer running again by restoring the lab on that computer.
Update Configuration. This job allows you to set unique configuration information (such as computer

names and network addresses) for client computers. When a lab is deployed, each computer has an
identical image, but not the same configuration settings. This means you don't have to visit each
computer to reset IP addresses and other settings when you deploy an image.
Upload Registries.

This job backs up computer registry files to the Deployment Server.

Altiris Deployment Solution Reference Guide

195

Chapter 8:

Sample Jobs for Deployment Solution


Sample jobs are shipped and installed in the Deployment Share (<DS install
path>\Altiris\eXpress\Deployment Server\Samples) to assist in various deployment
tasks. During installation, jobs are automatically imported from the samples.bin file into

Deployment Solution where they can be viewed in the Samples folder in the Jobs area of the console.
The Samples folder contains subfolders for Imaging, Simple Tests, Migrations, Miscellaneous Jobs,
Pocket PC, Scripted OS Installs, Scripts, and XP Embedded.
Jobs in each folder marked with an asterisk (*) require input parameters or other minor modifications
added before running on your system. These modifications allow you to add parameters to the job
such as user name and password, or other required data to allow the job to be functional. These jobs
will not function properly if you do not edit the job task with the information specific to your
environment.

All files without an asterisk (*) can be used to perform the identified functions without modification.
However, if the job conditions are not met or are not consistent with the computer type then you may
get an error. For example, if the Repair Office XP job runs on a computer without MS Office XP then
you will get an error when trying to run the job.
Note It is suggested that you copy the desired sample job and change the name to avoid overwrites

if you reinstall Deployment Solution.

Sample files are provided to help create jobs and other files for use in your specific environment.
These files portray possible solutions and configurations, and can be modified and rewritten. Each
of these jobs can also be created in the Deployment Server Console and executed with the same
effectiveness to meet your specific needs. Because of continually changing market conditions and
specific requirements for your organization, Altiris cannot guarantee the effectiveness of these
sample files working in your environment.
See sample jobs in these categories:
Imaging (page 196)
Simple Tests (page 197)
Migrations (page 198)
Misc Jobs (page 199)
Pocket PC (page 203)
Scripted OS Installs (page 204)
Scripts (page 209)
XP Embedded (page 212)

Imaging
Use these sample jobs for basic imaging tasks:
Create Disk Image (page 197)

Altiris Deployment Solution Reference Guide

196

Chapter 8: Sample Jobs for Deployment Solution

Simple Tests

Distribute Disk Image (page 197)

Create Disk Image


Description Creates a disk image.
Additional files required None.
What this task does This task will create a disk image using the name of the computer as the image

filename.

Steps to use Assign the job to a computer or computer group.

Distribute Disk Image


Description Distributes a disk image.
Additional files required None.
What this task does This job will distribute the disk image using the name of the computer as the

image filename.

Steps to use Assign the job to a computer or computer group.

Simple Tests
Run simple commands and install software packages using these jobs:
DIR Command at DOS (page 197)
DIR Command at Windows (page 197)
Distribute RapidInstall Package (page 198)

DIR Command at DOS


Description Runs the DIR command in DOS
Additional files required None.
What this task does This task runs the DIR command at the DOS prompt. If the managed computer
is running in Windows, it will tell the Deployment Agent to restart the computer to automation and
the computer will reboot. When the computer starts, the BootWorks application runs and the DIR
command executes. After the DIR command runs, the computer will boot back to the production
status. This task also uses the Logevent application to send the scripting status back to the
Deployment Server.
Steps to use Assign the job to a computer or computer group.

DIR Command at Windows


Description Runs the DIR command in Windows from a command prompt
Additional files required None.
What this task does This task runs the DIR command in Windows from a command prompt.
Steps to use Assign the job to a computer or computer group.

Altiris Deployment Solution Reference Guide

197

Chapter 8: Sample Jobs for Deployment Solution

Migrations

Distribute RapidInstall Package


Description Runs the shwnm.exe RapidInstall package.
Additional files required: None.
What this task does This package includes a utility that displays the computer name in a window.
A shortcut is created in the startup group so that every time the computer is started the window will
display the computer name.
Steps to use Assign the job to a computer or computer group.

Migrations
With the aid of PC Transplant, capture various user settings using these jobs:
Capture User Application Settings (page 198)
Capture User Desktop Settings (page 198)
Capture User Microsoft Office Settings (page 199)
Capture User Printer Settings (page 199)

Capture User Application Settings


Description Collects the users application setting using PC Transplant.
Additional files required None.
What this task does This task will use PC Transplant and a supplied PCT template to gather the

application settings for all of the users that exist on the computer. The client computer will execute
the PC Transplant Wizard using the specified template and create a file (computername.exe) at
the specified location.
Steps to use
1

Edit the job.

Assign the username and password for use with Windows NT/2000/XP/2003 based systems. If
you are using this job on Windows 9x computers, then the logged-in user must have rights to the
specified location for the template and package creation.

Assign the job to a computer or computer group.

Capture User Desktop Settings


Description Collects the users desktop setting using PC Transplant
Additional files required None.
What this task does This task will use PC Transplant and a supplied PCT template to gather the

desktop settings for all of the users that exist on the computer. The client computer will execute the
PC Transplant Wizard using the specified template and create a file (computername.exe) at the
specified location.

Steps to use
1

Edit the job.

Assign the username and password for use with Windows NT/2000/XP/2003 based systems. If
you are using this job on Windows 9x computers, then the logged-in user must have rights to the
specified location for the template and package creation.

Altiris Deployment Solution Reference Guide

198

Chapter 8: Sample Jobs for Deployment Solution

Misc Jobs

Assign the job to a computer or computer group.

Capture User Microsoft Office Settings


Description Collects the users Microsoft Office setting using PC Transplant
Additional files required None.
What this task does This task will use PC Transplant and a supplied PCT template to gather the

Microsoft Office settings for all of the users that exist on the computer. The client computer will
execute the PC Transplant Wizard using the specified template and create a file
(computername.exe) at the specified location.

Steps to use
1

Edit the job.

Assign the username and password for use with Windows NT/2000/XP/2003 based systems. If
you are using this job on Windows 9x computers the logged-in user must have rights to the
specified location for the template and package creation.

Assign the job to a computer or computer group.

Capture User Printer Settings


Description Collects the users printer setting using PC Transplant
Additional files required None.
What this task does This task will use PC Transplant and a supplied PCT template to gather the

printer settings for all of the users that exist on the computer. The client computer will execute the
PC Transplant Wizard using the specified template and create a file (computername.exe) at the
specified location.
Steps to use
1

Edit the job.

Assign the username and password for use with Windows NT/2000/XP/2003 based systems. If
you are using this job on Windows 9x computers the logged-in user must have rights to the
specified location for the template and package creation. Assign the job to a computer or
computer group.

Misc Jobs
Misc jobs can be executed on computers, including installation and repair of Office XP, computer
power control, and SQL service and installation:
Install Office XP from Mapped Drive (page 200)
Install Office XP from UNC Source (page 200)
SQL 2000 Unattended Install (page 200)
SQL 2000 Unattended Install Using a RIP (page 201)
Copy WLogevent to Client (page 201)
Install MSI 2.0 Runtime (page 201)
Repair Office XP (page 202)
Restart Computer (page 202)

Altiris Deployment Solution Reference Guide

199

Chapter 8: Sample Jobs for Deployment Solution

Misc Jobs

Shutdown Computer (page 202)


Start SQL Server Service (page 202)
Stop SQL Server Service (page 202)
Uninstall Office XP (page 203)
Wake up Computer (page 203)

Install Office XP from Mapped Drive


Description Installs Microsoft Office XP.
Additional files required Microsoft Office XP setup files located on the network share that will be
used in the drive mapping.
What this task does This script maps a network drive and installs Microsoft Office XP Professional
with Front Page from it.
Steps to use
1

To customize the script, change the UNC that the drive is being mapped to, as well as the
username and password.

To change the username, go into the advanced settings of the script. Note that the client computer
must be in the domain if you are using domain authentication.

Assign the job to a computer or computer group.

Note It is strongly recommended that you follow Microsoft's guidelines for preparing Office XP to

be deployed. The setup should be customized using the proper tools, and an administrative install
should be performed to place the setup files on the network share. For more details, consult the
Office XP Resource Kit.

Install Office XP from UNC Source


Description This task will install Microsoft Office XP.
Additional files required Microsoft Office XP setup files located on the network share that will be

used in the script.

What this task does This script runs a Microsoft Office XP Professional with Front Page install

directly from a UNC.


Steps to use
1

To customize the script, change the location of the setup files, as well as the username and
password. Note that the client computer must be in the domain if you are using domain
authentication.

To change the username, go into the advanced settings of the script.

Assign the job to a computer or computer group.

Note It is strongly recommended that you follow Microsoft's guidelines for preparing Office XP to

be deployed. The setup should be customized using the proper tools, and an administrative install
should be performed to place the setup files on the network share. For more details, consult the
Office XP Resource Kit.

SQL 2000 Unattended Install


Description This script will do an unattended install of SQL Server 2000.
Additional files required The files from the SQL Server 2000 disk.

Altiris Deployment Solution Reference Guide

200

Chapter 8: Sample Jobs for Deployment Solution

Misc Jobs

What this task does This script will copy all of the files and directories from the SQL setup to the
client computer, then execute an unattended install using the specified silent install script
(sqlins.iss).
Steps to use
1

Copy the files from the SQL 2000 CD into the .\samples\misc\sql2000 directory. Edit the
sqlins.iss file located in the .\samples\misc\sql2000 directory to include your CD key.

Assign the job to a computer or computer group.

SQL 2000 Unattended Install Using a RIP


Description This script will do an unattended install of SQL Server 2000 using a RapidInstall
Package to copy the files on the computer and execute the setup using a post install script.
Additional files required The files from the SQL Server 2000 disk inserted into the
sql2000pkg.exe RapidInstall package.
What this task does This script will copy all of the files and directories from the SQL setup to the
client computer using a RapidInstall package, then execute an unattended install using the specified
silent install script (sqlins.iss) in a post install script.
Steps to use
1

Start RapidInstall Editor and open the sql2000pkg.exe located in the


.\samples\misc\sql2000 directory.

Edit the sqlins.iss file in the TempPath\SQL2000 directory in the RIP.


To edit the file, select the SQL2000 directory in the Files view and right click the file listed to
the right and choose Open With. Choose Notepad as the associated program. Replace the CDKey
entry in the file and save the file. Close Notepad. Choose OK in the Edit File dialog to reinsert the
changed file into the RIP.

Copy the files and directories from the SQL 2000 CD into the SQL2000 directory in the RIP by
dragging and dropping them onto the SQL2000 folder.

After the files have been added to the RIP, save it by choosing File>Save. Close the RapidInstall
Editor.

Assign the job to a computer or computer group.

Copy WLogevent to Client


Description Copy the wlogevent.exe to the windows client computer for use with script logging.
Additional files required None.
What this task does This job will copy the wlogevent.exe from the Deployment Server directory

to the client computer in the temp directory. This file is used for logging status in windows scripts.

Steps to use Assign the job to a computer or computer group.

Install MSI 2.0 Runtime


Description Installs the Microsoft Installer runtime files.
Additional files required None.
What this task does This task uses conditions to determine the OS of the computer and installs the
appropriate MSI 2.0 runtime files.
Steps to use Assign the job to a computer or computer group.

Altiris Deployment Solution Reference Guide

201

Chapter 8: Sample Jobs for Deployment Solution

Misc Jobs

Repair Office XP
Description This script will force Microsoft Office XP Professional with Front Page to be repaired

on the client computer.

Additional files required The source that Office XP was originally installed from must be

accessible in order for the repair to function successfully.

What this task does This script will force Microsoft Office XP Professional with Front Page to be
repaired on the client computer. You can substitute the Product ID of any MSI (Windows Installer)
installed application in this sample.
Steps to use Assign the job to a computer or computer group.

Restart Computer
Description Restarts the client.
Additional files required None.
What this task does Restarts the client if restart is supported.
Steps to use Assign the job to a computer or computer group.

Shutdown Computer
Description Shutdown the client.
Additional files required None.
What this task does Shuts down the client if shutdown is supported.
Steps to use Assign the job to a computer or computer group.

Start SQL Server Service


Description This script will start the SQL Server service.
Additional files required None.
What this task does This script will send the NET START MSSQLServer command to the

computer.

Steps to use
1

If you run the SQLServerAgent you need to remove the REM on the line that starts the agent
service.

Assign the job to a computer or computer group.

Stop SQL Server Service


Description This script will stop the SQL Server service.
Additional files required None.
What this task does This script will send the NET STOP MSSQLServer and NET STOP
SQLServerAgent command to the computer. This job will stop the agent service because the SQL

server will not stop if this is running from the command line.

Steps to use Assign the job to a computer or computer group.

Altiris Deployment Solution Reference Guide

202

Chapter 8: Sample Jobs for Deployment Solution

Pocket PC

Uninstall Office XP
Description This script will force Microsoft Office XP Professional with Front Page to be
uninstalled on the client computer.
Additional files required The source that Office XP was originally installed from must be

accessible in order for the uninstall to function successfully.

What this task does This script will force Microsoft Office XP Professional with Front Page to be
uninstalled on the client computer. You can substitute the Product ID of any MSI (Windows
Installer) installed application in this sample.
Steps to use Assign the job to a computer or computer group.

Wake up Computer
Description Wake up a computer.
Additional files required None.
What this task does Sends a Wake On LAN packet to the computer. If the client supports Wake On

LAN, then this will succeed.

Steps to use Assign the job to a computer or computer group.

Pocket PC
These jobs are used to install agents and CAB files to manage handheld devices in Deployment
Solution:
Distribute Software (page 203)
Install Altiris Pocket PC Agent (page 203)

Distribute Software
Description Installs a simple application that displays the name of the Pocket PC.
Additional files required None.
What this task does This job allows you to set a condition for a MIPS, ARM, or SH3 processor for
your handheld device. Once a condition is set then it will install the correct CAB file from the
Samples directory.
Steps to use Assign the job to the handheld device displayed in the Computers section of the
Deployment Server Console.

Install Altiris Pocket PC Agent


Description Installs Pocket PC Agent on the host computer (the computer with the handheld cradle)
for the handheld device. This job sets a condition to check if ActiveSync is installed on the host
computer. If ActiveSync is installed, the Pocket PC agent will install. If ActiveSync is not installed,
then an error will appear stating that your condition is not met on the selected computer.
Additional files required Microsoft ActiveSync on the host computer.
What this task does This job places the Pocket PC agent on the host computer to manage a

connected handheld device.

Altiris Deployment Solution Reference Guide

203

Chapter 8: Sample Jobs for Deployment Solution

Scripted OS Installs

Steps to use Assign the job to a managed computer acting as host (with Microsoft ActiveSync

installed) for a handheld device.

Scripted OS Installs
These imported jobs allow you to run scripted, unattended installs on both Windows and Linux
servers. These jobs are used for both Network installs and Hard Disk installs. To do a network
scripted install of Windows, use the Scripted OS install task type in a job:
Create W2K Install Disk Image (Target HD) (page 204)
W2K Scripted Install (Target HD) (page 205)
Create RH7 Install Disk Image (Network) (page 206)
Create RH7 Install Disk Image (Target HD) (page 206)
RH7 Scripted Install (Network) (page 207)
RH7 Scripted Install (Target HD) (page 208)
Create RH8 Install Disk Image (Network) (page 208)
RH8 Scripted Install (Network) (page 209)

Create W2K Install Disk Image (Target HD)


Description This job creates a disk image to be used for installing Windows 2000 using files from
the local hard drive. This method is not supported from the Scripted OS install task. This process can
be repeated for XP and .NET as well. This job is only used once to set up the image that will be
repeatedly called from the "W2k Scripted Install (Target HD)" job.
Additional files required

< DS install path >\IMAGES\DOS_ONLY.IMG. Image file containing a simple bootable

partition that is provided during the product install.

Windows 2000 installation files (I386 directory from the Windows CD). These files need to be
copied from the Windows CD to the OS files directory. The default directory is <DS install
path>\DEPLOY\WIN\W2K\I386 directory.

< DS install path >\Deployment Server\


\SAMPLES\SCRIPT~1\WINDOWS\W2KSETUP.BAT. DOS batch file that the job calls to copy

the Deployment Agent, other DOS utilities, and the Windows OS files needed for the target HD
install.
If you need to supply drivers that are not included with the Windows installation you will need
to create a $OEM$ directory under the i386 directory.

If you have hardware or other devices that are not supported in the OS distribution, you can add
the drivers needed in the $OEM$ directory that is supported by the unattended install process.
In our examples we have added drivers for Intel display, network and chipset. The $1 specifies
the root of the %SYSTEMDRIVE% variable. You will need to verify that the directories are included
in the OemPnpDriversPath value in the Unattended section of the unattended.txt file.
Note The Windows unattended install process requires that all drivers in $OEM$ be fully

extracted. Zip files cannot be used. See the "Microsoft Windows 2000 Guide to Unattended
Setup" for more information. This guide is named unattend.doc and is in the deploy.cab
file in the \Support\Tools folder of the Windows 2000 installation CDROM.
What this task does This job creates a hard drive image that can later be used for installing
Windows 2000 through the hard disk install method. It downloads the DOS_ONLY image to the

selected client. This creates a 2 GB, FAT16 DOS bootable partition. It reboots the client so that DOS
will recognize the newly created DOS partition. It calls the w2ksetup.bat file to copy the
Deployment Agent, and the Deployment Agent input file (aclient.inp) as well as various other

Altiris Deployment Solution Reference Guide

204

Chapter 8: Sample Jobs for Deployment Solution

Scripted OS Installs

DOS utilities to facilitate a Windows scripted install. It also copies the Windows OS files (usually
from the I386 directory) to the target's hard drive in the C:\I386 directory. It runs rdeploy.exe
to create a disk image of the now populated DOS partition.
Steps to use
1

Make a copy of the sample job.

If you want to create your own DOS_ONLY.img with MSDOS instead of using the supplied DR
DOS image, you will need to manually create the image. To create your own DOS image, use a
DOS boot floppy to run fdisk.exe to create a 2GB partition on a reference computer. Format
the partition to be a system drive. Copy the appropriate DOS files needed (e.g., himem.sys,
smartdrv, xcopy, etc.). Create an autoexec.bat file that runs smartdrv to speed the
installation and then looks for a file called install.bat. Install.bat will be used in our
examples to initiate the unattended installation.
Example Autoexec.bat file:
@echo off
smartdrv
IF NOT EXIST c:\install.bat goto no_install
call c:\install.bat
goto done
:no_install
echo No Install File
:done

Be sure to include smartdrv in the batch file. This command starts SMARTDrive, which
creates a disk cache in extended memory. A disk cache will significantly speed up the imaging
process. After the above tasks have been performed, create an image of the drive named
MS_DOS.img. Once the MS_DOS image is created, copy the i386 folder of the Windows CD
(along with the $OEM$ folder if supplemental drivers will be required) to the DOS computer.
Now create another image of the drive and name it W2K_AS.img. This image will be used for
hard drive scripted OS installs to provide the OS files needed for the Windows installation. A
total of two DOS images should be created with the second image containing Windows install
files in a C:\i386 folder. If you use the MS_DOS.img then edit the task and replace
DOS_ONLY.img with MS_DOS.img.
3

Edit the last Run Script task, Create Windows Install Disk Image, and change the SET
ImageName=F:\IMAGES\W2K_HD.IMG line to the name of the image you wish to create.

If you copied the Windows OS files to a location other than <DS install
path>\DEPLOY\WIN\W2K\I386, edit the second Run Script task, Copy Windows Files to Hard
Drive, and specify the location on the SET OSFilesPath= line.

Change the name of the job to reflect the desired purpose (optional).
Note After this job finishes, it will leave the client computer in an unmanageable state.

Assign the job to a computer or computer group.

W2K Scripted Install (Target HD)


Description Deploys the Windows 2000 operating system using the Target HD scripted install

model. This will use the image we created with the Create W2K Scripted Install (Target HD) job.

In 6.5, we recommend using FAT32.img rather than DOS_ONLY.img to perform scripted installs.
Additional files required

<install path>\IMAGES\W2K_HD.IMG. This is the image file created by the Create W2K

Install Disk Image (Target HD) job described above. You may have changed the name. This image

file contains a DOS bootable partition with the Deployement Agent and other various DOS
utilities along with the Windows OS files that are required for a Windows unattended install.

<install path>\IMAGES\Install.bat. File that executes the scripted install.

Altiris Deployment Solution Reference Guide

205

Chapter 8: Sample Jobs for Deployment Solution

Scripted OS Installs

Windows unattended answer file. A sample provided by the product installation located in the

<DS install path>\SAMPLES\SCRIPTED OS INSTALL\WINDOWS directory.

What this task does This job starts a Windows unattended OS install on a client using the hard disk
install method. It downloads the W2K_HD image (or whatever you have named it) to the selected

client. This creates a 2 GB, FAT16 DOS bootable partition with the OS files to do a Windows
unattended install. It then reboots the computer to get the new partition and format information. It
uses a script to get the unattended answer file copied to the client. It then reboots the client. Upon
reboot, the DOS partition is booted and the OS install is automatically started with the
autoexec.bat that is called in the image.
Steps to use
1

Make a copy of the sample job.

Edit the Deploy Image task and change the name of the image file to the name you created with
the Create W2K Install Disk Image (Target HD) job described above.

Edit the answer file to specify the product key and other information.

Change the name of the job to reflect the desired purpose (optional).

Assign the job to a computer or computer group.

Create RH7 Install Disk Image (Network)


Description Creates a disk image to be used for installing RedHat Linux v7.1 through the Network
install method. The Network method copies the RedHat files from an FTP server during OS
installation. See the user guide for instructions on setting up an FTP server for this purpose.
Additional files required

<DS install path>\IMAGES\DOS_ONLY.IMG. Image file containing simple bootable

partition. Provided during the product install.

<DS install path>\SAMPLES\SCRIPT~1\RedHat\RH7SETUP.BAT. DOS batch file that


the job calls to copy the basic RedHat files needed for the Kickstart install such as LOADLIN,
VMLINUZ, etc.

What this task does This job creates a hard drive image that can later be used for installing RedHat
Linux through the network install method. It downloads the DOS_ONLY image to the selected client.
This creates a 2 Gig FAT16 DOS bootable partition. Then it reboots the client so that DOS will
recognize the newly created DOS partition. It then calls RH7SETUP to copy the basic RedHat files
that facilitate a RedHat Kickstart install. It then runs RDeploy to create a disk image of the now
populated DOS partition.
Steps to use
1

Make a copy of the sample job.

Edit the last Run Script task, Create Red Hat Install Disk Image, and change the SET
ImageName=F:\IMAGES\RH71_FTP.IMG line to the name of the image you wish to create.

Change the name of the job to reflect the desired purpose (optional).

Assign the job to a computer or computer group.

Create RH7 Install Disk Image (Target HD)


Description Creates a disk image to be used for installing RedHat Linux (v7.1 or later) through the
hard disk install method (where files are installed from the local hard drive).
Additional files required

<DS install path>\IMAGES\DOS_ONLY.IMG. DOS_ONLY.IMG is an image file containing

a simple bootable partition provided during the product install.

Altiris Deployment Solution Reference Guide

206

Chapter 8: Sample Jobs for Deployment Solution

Scripted OS Installs

RedHat OS files (REDHAT and DOSUTILS directories from the RedHat CD). These files need
to be copied from the RedHat CD to the <install
path>\DEPLOY\CDS\REDHAT\RH71\REDHAT and <install
path>\DEPLOY\CDS\REDHAT\RH71\DOSUTILS directories, respectively.

<DS install path>\SAMPLES\SCRIPT~1\REDHAT\RH7SETUP.BAT. DOS batch file that

the job calls to copy the RedHat OS files needed for the target hard drive install.

What this task does: This job creates a hard drive image that can later be used for installing RedHat
Linux v7.1 through the Hard Disk install method. It downloads the DOS_ONLY image to the selected

client. This creates a 2 Gig FAT16 DOS bootable partition. It reboots the client so that DOS will
recognize the newly created DOS partition. It calls RH7SETUP.bat to copy the basic RedHat files
that facilitate a RedHat Kickstart install. It also copies the RedHat OS files to the target's hard drive
in the C:\REDHAT directory. It runs RDeploy to create a disk image of the now populated DOS
partition.
Steps to use
1

Make a copy of the sample job. Edit the last Run Script task, Create Red Hat Install Disk Image, and
change the SET ImageName=F:\IMAGES\RH71_HD.IMG line to the name of the image you
wish to create.
If you copied the RedHat OS files to a location other than <DS install
path>.\DEPLOY\CDS\REDHAT\RH71, edit the second Run Script task, Copy RedHat Files to
Hard Drive, and specify the location on the SET OSFilesPath= line.

Change the name of the job to reflect the desired purpose (optional).

Assign the job to a computer or computer group.

RH7 Scripted Install (Network)


Description This job deploys the RedHat Linux operating system using the Network scripted install
model. The network method copies the RedHat files from an FTP server during OS installation. See
the Deployment Solution User Guide for instructions on setting up an FTP server for this purpose.
Additional files required

<DS install path>\IMAGES\RH71_FTP.IMG. This is the image file created by the Create

job described above. You may have changed the name. This
image file contains a DOS bootable partition with the basic RedHat files that facilitate a RedHat
Kickstart install.

RH7 Install Disk Image (Network)

RedHat Kickstart answer file. A sample is located in the \SAMPLES\SCRIPTED OS

INSTALL\REDHAT directory.

What this task does This job starts a RedHat Kickstart OS install on a client using the Network
install method. It downloads the RH71_FTP image (or whatever you have named it) to the selected

client. This creates a 2 Gig FAT16 DOS bootable partition with files to facilitate a RedHat Kickstart
install. It reboots the client so that DOS will recognize the newly created DOS partition. It uses a
Scripted OS Install task to start the unattended install on the client. This task contains the location of
the OS install files located on the FTP server as well as the Kickstart file to be used for the OS install.
Steps to use
1

Make a copy of the sample job.

Edit the Deploy Image task and change the name of the image file to the name you created with
the Create RH7 Install Disk Image (Network) job described above.

Edit the Scripted OS Install task and change the location of the Kickstart answer file.

Change the hard drive ID in the Command Line edit box to the proper ID for the target system.
The default is ks=hd:hda1/ks.cfg where hda1 is the default hard drive ID.

Change the name of the job to reflect the desired purpose (optional).

Assign the job to a computer or computer group.

Altiris Deployment Solution Reference Guide

207

Chapter 8: Sample Jobs for Deployment Solution

Scripted OS Installs

RH7 Scripted Install (Target HD)


Description This job deploys the RedHat Linux operating system using the Hard Disk scripted
install model.
Additional files required

<DS install path> \IMAGES\RH71_HD.IMG. This is the image file created by the Create
RH7 Install Disk Image (Target HD) job described above. You may have changed the name. This
image file contains a DOS bootable partition with the RedHat OS files that are required for a
RedHat Kickstart install.

RedHat Kickstart answer file. A sample is located in the \SAMPLES\SCRIPTED OS

INSTALL\REDHAT directory.

What this task does: This job starts a RedHat Kickstart OS install on a client using the Target HD

install method. It downloads the RH71_HD image (or whatever you have named it) to the selected
client. This creates a 2 Gig FAT16 DOS bootable partition with the OS files to do a Kickstart
unattended install. It uses a Scripted OS Install task to get the Kickstart answer file copied to the
client. This task contains the location of the answer file to be used for the OS install. It reboots the
client. Upon reboot, the DOS partition is booted and the OS install is automatically started.
Steps to use
1

Make a copy of the sample job.

Edit the Deploy Image task and change the name of the image file to the name you created with
the Create RH7 Install Disk Image (Target HD) job described above.

Edit the Scripted OS Install task and point it to the desired Kickstart answer file.

Change the hard drive ID in the Command Line edit box to the proper ID for the target system.
The default is ks=hd:hda1/ks.cfg where hda1 is the default hard drive ID.

Change the name of the job to reflect the desired purpose (optional).

Assign the job to a computer or computer group.

Create RH8 Install Disk Image (Network)


Description Creates a disk image to be used for installing RedHat Linux v8.0 through the Network
install method. The Network method copies the RedHat files from an FTP, NFS, or HTTP server
during OS installation. See the RedHat User guide for instructions on setting up a source server for
this purpose.
Additional files required

<DS install path>\IMAGES\DOS_ONLY.IMG. Image file containing simple bootable

partition. Provided during the product install.

<DS install path>\SAMPLES\SCRIPT~1\RedHat\RH8SETUP.BAT. DOS batch file that


the job calls to copy the basic RedHat files needed for the Kickstart install such as LOADLIN,
VMLINUZ, etc.

What this task does This job creates a hard drive image that can later be used for installing RedHat
Linux through the Network install method. It downloads the DOS_ONLY image to the selected client.
This creates a 2 Gig FAT16 DOS bootable partition. It reboots the client so that DOS will recognize
the newly created DOS partition. It calls RH8SETUP to copy the basic RedHat files that facilitate a
RedHat Kickstart install. It runs RDeploy to create a disk image of the now populated DOS partition.
Steps to use
1

Make a copy of the sample job.

Edit the last Run Script task, Create Red Hat Install Disk Image, and change the SET
ImageName=F:\IMAGES\RH80_FTP.IMG line to the name of the image you wish to create.

Change the name of the job to reflect the desired purpose (optional).

Assign the job to a computer or computer group.

Altiris Deployment Solution Reference Guide

208

Chapter 8: Sample Jobs for Deployment Solution

Scripts

RH8 Scripted Install (Network)


Description This job deploys the RedHat Linux operating system using the Network scripted install
model. The network method copies the RedHat files from an FTP, NFS, or HTTP server during OS
installation. See the Deployment Solution User Guide for instructions on setting up an FTP server
for this purpose.
Additional files required

<DS install path>\IMAGES\RH80_FTP.IMG. This is the image file created by the Create

job described above. You may have changed the name. This
image file contains a DOS bootable partition with the basic RedHat files that facilitate a RedHat
Kickstart install.

RH8 Install Disk Image (Network)

RedHat Kickstart answer file, located in the \SAMPLES\SCRIPTED OS INSTALL\REDHAT


directory.

What this task does This job starts a RedHat Kickstart OS install on a client using the Network
install method. It downloads the RH80_FTP image (or whatever you have named it) to the selected

client. This creates a 2 Gig FAT16 DOS bootable partition with files to facilitate a RedHat Kickstart
install. It reboots the client so that DOS will recognize the newly created DOS partition. It uses a
Scripted OS Install task to start the unattended install on the client. This task contains the location of
the OS install files located on the FTP server as well as the Kickstart file to be used for the OS install.
Steps to use
1

Make a copy of the sample job.

Edit the Deploy Image task and change the name of the image file to the name you created with
the Create RH8 Install Disk Image (Network) job described above.

Edit the Scripted OS Install task and change the location of the Kickstart answer file.

Change the hard drive ID in the Command Line edit box to the proper ID for the target system.
The default is ks=hd:hda1/ks.cfg where hda1 is the default hard drive ID.

Change the name of the job to reflect the desired purpose (optional).

Assign the job to a computer or computer group.

Scripts
These jobs are provided to give some ideas of things that can be accomplished by scripting. The
scripts have been divided into scripts for Windows and scripts for Linux:
Send Email if Disk Space Low (Linux) (page 210)
Logevent Script (Linux) (page 210)
Restart HTTPD Service (Linux) (page 210)
Move Computer to Default Container (Windows) (page 210)
Move Computer to Specific OU (Windows) (page 211)
Send Error Email (Windows) (page 211)
Server-side Embedded VBScript (Windows) (page 211)
WLogevent CMD Script (Windows) (page 211)
WLogevent VB Script (Windows) (page 212)

Altiris Deployment Solution Reference Guide

209

Chapter 8: Sample Jobs for Deployment Solution

Scripts

Send Email if Disk Space Low (Linux)


Description This script will send an email specifying that the computer had less free space than
specified threshold.
Additional files required None.
What this task does This script will send an email notifying the specified user of the computer that
has less than the specified threshold of disk space free.
Steps to use
1

Edit the embedded script to specify the email username to send to and the threshold percentage.

Assign this job to a computer or computer group.

Logevent Script (Linux)


Description This script shows how to use the logevent utility to send status back to the console while
running a Linux script.
Additional files required None.
What this task does This job sends a status message to the console then executes an ls command,
then sends another message to the console.
Steps to use Assign the job to a computer or computer group.

Restart HTTPD Service (Linux)


Description This script will restart the HTTPD service.
Additional files required None.
What this task does This script will check to see if a page can be loaded from the http server. If it
cannot be loaded, then the script will restart the httpd service.
Steps to use Assign the job to a computer or computer group.

Move Computer to Default Container (Windows)


Description This script will take the specified computer and move it to the specified domain default
computer container.
Additional files required None.
What this task does This script will take the specified computer and move it to the specified domain
default computer container.
Steps to use
1

Edit the movecomp_cn.vbs to specify the domain that you want to use for the computer to be
moved in.
This script will not create the computer account in the domain. If it is not already a member of
the domain, this event will fail.

Assign the job to a computer or computer group.

Altiris Deployment Solution Reference Guide

210

Chapter 8: Sample Jobs for Deployment Solution

Scripts

Move Computer to Specific OU (Windows)


Description: This script will take the specified computer and move it to the specified domain OU.
Additional files required None.
What this task does This script will take the specified computer and move it to the specified domain

OU.

Steps to use
1

Edit the movecomputer.vbs to specify the domain and OU that you want the computer to be
moved into.
This script will not create the computer account in the domain. If it is not already a member of
the domain, this event will fail.

Assign the job to a computer or computer group.

Send Error Email (Windows)


Description This script will send an email specifying that the computer had an error.
Additional files required None.
What this task does This script will send an email using the job name and computer name to

identify the client that had an error. This script is run on the Deployment server and can be used as
a job to be run when having a specific error occurs.

Steps to use
1

Edit the sendmailscript.vbs to specify the SMTP server and the user to have the email sent
from and to.

Assign the job to a return code handler on another task. (See "Setting up Return Codes" in help
for more details).

Assign the calling job to a computer or computer group. If you have the error then this job (Send
Error Email) will be called.

Server-side Embedded VBScript (Windows)


Description This script will log an event to the event log.
Additional files required None.
What this task does This script will log an event to the application event log under the WSH

module. The text will read Deployment Server Job complete for <computername>.

Steps to use Assign the job to a computer or computer group.

WLogevent CMD Script (Windows)


Description This script shows how to use the Wlogevent utility to send status back to the console
while running a Windows CMD script.
Additional files required None.
What this task does This job will copy the WLogevent.exe to the Windows client, then sends a
status message to the console, then executes a dir command, then sends another message to the

console.

Steps to use Assign the job to a computer or computer group.

Altiris Deployment Solution Reference Guide

211

Chapter 8: Sample Jobs for Deployment Solution

XP Embedded

WLogevent VB Script (Windows)


Description This script shows how to use the Wlogevent utility to send status back to the console
while running a Windows VB script.
Additional files required None.
What this task does This job will copy the WLogevent.exe to the Windows client, then sends a
status message to the console, then executes a dir command, then sends another message to the

console.

Steps to use Assign the job to a computer or computer group.

XP Embedded
These jobs are provided to give samples when working with XP embedded that have the Enhanced
Write Filter enabled:
Disable Enhanced Write Filter (page 212)
Enable Enhanced Write Filter (page 212)
Distribute RapidInstall Package (page 212)

Disable Enhanced Write Filter


Description Disable the Enhanced Write Filter.
Additional files required None.
What this task does This job will disable the Enhanced Write Filter and reboot the client computer.
Steps to use Assign the job to a computer or computer group.

Enable Enhanced Write Filter


Description Enable the Enhanced Write Filter.
Additional files required None.
What this task does This job will enable the Enhanced Write Filter and reboot the client computer.
Steps to use Assign the job to a computer or computer group.

Distribute RapidInstall Package


Description Runs the shwnm.exe RapidInstall package after disabling the Enhanced Write Filter.
Additional files required None.
What this task does This job will disable the Enhanced Write Filter, and then install a package that

includes a utility that displays the computer name in a window. A shortcut is created in the startup
group so that every time the computer is started the window will display the computer name. After
installing the RIP, the Enhanced Write Filter will be enabled.

Steps to use Assign the job to a computer or computer group.

Altiris Deployment Solution Reference Guide

212

Chapter 9:

Managing Switches
To administer roles and configurations for network servers, it is necessary to discover and modify
the network switch settings for the connected network servers. Deployment Solution provides the
Switch Add-On program to discover and manage Virtual Local Area Networks (VLAN) settings on
a LAN switch or to run commands from the command-line. This utility allows you to directly
discover and provision the port settings of a LAN switch.

To open the Switch Management tool, click Tools > Altiris Tools > Switch
Management. This will open the Deployment Solution Switch Add-On utility tool.
Network switches will be identified in the left pane. Click the star button to Add
New Switches.
Switch Management Features
Typically, a VLAN setting is port based it is a LAN switch port that can be configured as a
member of a specific VLAN. As such, client and server computers connected to that LAN switch
port are members of the VLAN and can communicate with other member client and server
computers of that VLAN. By changing the VLAN setting of a switch port, you can move client and
server computers between logical VLAN groupings without actually changing the physical network
infrastructure.
Often, when modifying server roles or configurations, it will be necessary for you to change the
grouping or VLAN for the servers network. This can be accomplished by changing the VLAN
setting on the switch port that the server is connected to.
The Deployment Solution Switch Add-On allows you to perform the following functions:

Discover the LAN switch MIB II system information (command-line and GUI)

Discover the switch ports of a LAN switch (command line and GUI)

Discover the VLAN setting for each switch port (command line and GUI)

Modify the VLAN setting of a switch port (command line and GUI)

Assign physical connectivity of a workstation/server to a switch port (GUI)

About Switch Add-On for Deployment Solution


Switch Add-On will assume port-based VLANs (not MAC-based VLANs), managing only VLANs
for a specified port setting on the switch. For this release, it will assume only one VLAN per port.
(Switch Add-On will not perform any type of VLAN trunking management in its initial release.)
Deployment Solution Switch Add-On will only support VLAN management based on the list of
supported devices in LAN Switch Support List (page 214) .
Deployment Solution Switch Add-On will only support SNMP v1. You will need the SNMP read
community name to discover a LAN switch (along with its port/VLAN mappings) and the SNMP
write community name to manage the port/VLAN settings.
All discovered switch information will be kept in a local database file (SwitchMngtDb.txt). To
ease installation and support, this file will be text based and be located in the directory from which
the Deployment Solution Switch Add-On applications are executed.

Altiris Deployment Solution Reference Guide

213

Chapter 9: Managing Switches

Notes

If a LAN switch supports the 802.1Q VLAN standard, Deployment Solution Switch Add-On will
only provide PVID management on a port.

Since most vendors do not support VLAN Add/Edit/Delete through SNMP, Deployment
Solution Switch Add-On will not provide these features.

All devices that are to be managed must support SNMP v1.

LAN Switch Support List


Deployment Solution Switch Add-On

switches:

supports these specific vendors with the following LAN

Cisco Catalyst 1900/2820 series switches


Models: All models (OS Versions 8.XX and up - Enterprise Edition)

Cisco Catalyst 2900 series switches


Models: WS-C2900, WS-C2926 (OS versions 3.1 and later)
Models: WS-C2948G, WS-C2980G and WS-C2980GA (All OS versions)

Cisco Catalyst 2900 XL / 2900 XL LRE series switches


Models: All models (IOS versions 11.2(8) SA3 and later)

Cisco Catalyst 3500 XL series switches


Models: All models (IOS versions 12.0(5) XP and later)

Cisco Catalyst 4000 series switches


Models: WS-C4003, WS-C4006, WS-C4912G (All OS versions)

Cisco Catalyst 5000 series switches


Models: WS-C5000, WS-C5002, WS-C5500, WS-C5505, WS-C5509, WS-C5509E (OS
versions 3.1 and up)

Cisco Catalyst 6000 series switches


Models: WS-C6006, WS-C6009, WS-C6506, WS-C6509, WS-C6509NEB, WS-C6513 (All
OS/IOS versions)

HP
Models: BL eClass Interconnect Switch (802.1Q PVID management only)

Dell
Models: PowerEdge 1655MC Integrated Switch (802.1Q PVID management only)

Altiris Deployment Solution Reference Guide

214

Chapter 9: Managing Switches

Using Deployment Solution Switch Add-On


The Deployment Solution Switch Add-On program is a stand-alone application that displays a
graphical view of the all switches that have been discovered along with their respective switch ports.

The following are port attributes displayed in the Details pane of the program:
Switch
Port

The switch to which the port belongs

The name of the port (vendor-specific port names will be shown when available)

Description
VLAN

The description of the switch port

The VLAN assignment for the switch port

Connectivity

Any user assigned mapping of clients or servers to the switch port

By selecting a device in the tree view pane, the switch port display will be updated to show its
respective ports. By selecting Network in the tree view, all switch ports that have been discovered
will be shown in the switch port view. You can sort on attributes by selecting the appropriate
column.

Adding a Switch Device


To add a switch to the Deployment Database
1

Press the Add icon on the toolbar


Or, right-click Network in the tree view.

From the pop up menu that opens, click Add Device.

Altiris Deployment Solution Reference Guide

215

Chapter 9: Managing Switches

Note When the device is available and the SNMP communities are correct, the application will read

the MIB II system information from the device and add the device to the tree view. If not, an error
message be displayed.

Discovering a Device
Once a device has been added to the database, all of the properties for that device can be discovered.
By selecting the device in the tree view and right clicking, the following menu will open:

Click Discover Device to discover all the switch device properties and store these values in the
Deployment Database. Once the discovery process is complete, the switch ports for that device will
be seen in the port view.

Deleting a Device
A device can be deleted in two ways:
1

Press the Delete icon on the toolbar:


Or, right-click and select Delete.

Viewing and Setting Device Properties


Select and view Properties for a switch device by right-clicking its name in the tree view. The system
information for the selected device will display. This dialog box will allow you to make any
necessary modifications to the SNMP read and SNMP write community strings (passwords).

Setting the VLAN for a Switch Port


To set a switch port to a specific VLAN, right-click on a switch port in the switch port view and click
Click Set VLAN to display all available VLANs on the switch. Select a VLAN from the list.

The Deployment Solution Switch Add-On application will then use the supplied SNMP community
strings (passwords) and attempt to change the VLAN setting on the port. If successful, the VLAN
column will be updated.

Altiris Deployment Solution Reference Guide

216

Chapter 9: Managing Switches

Note It is possible to select more than one port in the port view and assign all selected ports to a
particular VLAN in one operation. However, due to the number of operations required to change
VLANs on some switching devices, this operation can be time consuming.

Assigning Connectivity to a Switch Port


From the switch port view, right-click any switch port and click Assign/View Connectivity to
determine what client or server computers are connected to a particular switch port. This dialog box
will open:

The Assign/View Connectivity dialog box displays all visible devices, including the MAC addresses
that are being forwarded by the switch. It also displays any previous connectivity mapping, such as
an X in the Connected column). You can add a hostname to a specific MAC address by right-clicking
the appropriate MAC address. A menu will open. Click Add/Edit Host Info to enter the hostname on
the dialog.
Note If the IP address and Hostname columns are blank for a MAC address, the application does not
have enough information about the global network to display an IP Address/Hostname binding to
that MAC address.

You can assign connectivity to a particular switch device by selecting the device (or MAC address)
in the list and clicking Assign Connectivity to Port. This will mark the MAC address as connected to
this port. You can remove connectivity by selecting the MAC address that you want to remove from
connectivity and clicking Remove Connectivity from Port. When the dialog is closed, the client and
server computers can be seen in the Connectivity column of the switch port view.

Command-line Parameters
The following command line parameters can be supplied to the Deployment Solution Switch AddOn program to launch the program with the appropriate
-d=<switch IP address>: By supplying the IP address of the switch, the Switch Add-On program will
launch and automatically select the supplied device in the tree view (thereby, showing all of its ports
in the port view).
-e=<end node MAC address>: By supplying the MAC address of a client or server computer, the
Switch Add-On program will launch and automatically select the switch and port that the client or
server computer is connected to (if the connectivity has been previously assigned).

GUI Tools
The Switch Management Console includes a Tools menu, providing a Ping IP Range command to
assist in "pinging" a specified IP range in order to generate traffic to a range of devices that might
otherwise be inactive. From this dialog box you can specify the starting and ending IP addresses to
ping. Success or failure messages will appear in the list.

Altiris Deployment Solution Reference Guide

217

Chapter 9: Managing Switches

The Ping IP Range tool can be used to lookup the MAC address of the device being pinged. To be
successful, SNMP must be enabled on the end device. The user can supply an SNMP Read
community name to perform this operation. Otherwise, the user may clear the SNMP MAC Lookup
box to ping only the end device.

If a device is inactive, the forwarding tables in the switch will not show the MAC address of
the client or server computer. The Ping IP Range tool can be used to refresh the forwarding table in
the switch.
Note

Deployment Solution Switch Add-On (Command


Line Options)
Along with the Deployment Solution Switch Add-On graphical program, a command-line interface
is provided that will support the command line arguments listed below. This program file is named
switchcfg.exe. It will be executed from the same directory that the database file
(SwitchMngtDb.txt) is located.
Command-line Interface Parameters
By executing the switchcfg.exe without any arguments, you will see displayed the usage of the
CLI application as below.
The following is a description of the available command line arguments and how they are to be used:
This indicates the mode of the operation to be performed. The two possible values are:
1) discover, and 2) set (as in set VLAN).

-m=<mode>

-d=<target ip>

This indicates the switch (by IP address) to perform the operation on.

-r=<read community>

The SNMP read community name (password) to use to discover the switch.

-w=<write community> The SNMP write community name (password) to use to perform any set
operations on the indicated device.
-p=<port name>

The name of the switch port the user is attempting to configure.

-v=<VLAN number>
-n-<VLAN name>

The VLAN number to set the switch port to (or).

The VLAN name to set the switch port to.

Altiris Deployment Solution Reference Guide

218

Chapter 9: Managing Switches

-e=<end node MAC address> The MAC address of the workstation/server that you want to be put in
a particular VLAN. In order for the utility to perform this operation correctly, the connectivity of the
MAC address must have already been assigned using the GUI application. When using this option,
the user must only supply the SNMP write community (password) and the VLAN (name or number)
to put the workstation/server in. The CLI application will use its database to lookup the appropriate
(bound) switch and switch port to provision.
-c=<SNMP retry count>
-t=<SNMP timeout>

The number of attempts that SNMP should attempt before giving up.

The SNMP timeout value in milliseconds.

Note Prior to executing any command to provision a switch, that switch MUST be discovered.

Otherwise, the program will report errors.

Command-line Examples
Discover a Switch
switchcfg.exe -m=discover -d=<target IP> -r=<SNMP read>

Set VLAN on a Switch/Port


switchcfg.exe -m=set -d=<target IP> -w=<SNMP write> -p=<port name> -n=<VLAN
name>

Set VLAN for a Workstation/Server (End Node)


switchcfg.exe -m=set -w=<SNMP write> -e=<MAC address> -n=<VLAN name>

Altiris Deployment Solution Reference Guide

219

Chapter 10:

Deployment Server Configuration Utility


The Deployment Server Configuration Utility provides general preferences for the Deployment
Server. You can use the Deployment Server Configuration Utility to:

Set up an account for Deployment Server. See Logon Account (page 221).

Stop, start, and restart Deployment Server.

View server activity and statistics.

Map drives to file servers in your Deployment Server system (if you have images stored in more
than one place). See Drive Mappings Option (page 222).

Set the communications protocol (multicast or TCP) and set the imaging multicast threshold. See
Transport Option (page 223).

Filter connections from the Deployment Server by IP addresses or network adapter interface.
Connections Option (page 225).

Set debug and log file options in the Debug Option (page 225).

Log in to the Deployment Server you want to manage. Open the Deployment Server
Configuration Utility by clicking Start > Programs > Altiris > Deployment Server >
Configuration.
From the main view of the Deployment Server Configuration Utility, you can view Deployment
Server statistics, start and stop the Deployment Server, access Deployment Server configuration
options and more.

Item

Description

Server activity
and statistics

Lists the number of Deployment Server sessions (clients) and Deployment


Server Consoles currently running on the network.

Start

Starts the Deployment Server on the local computer.

Stop

Stops the Deployment Server on the local computer.

Restart

Restarts the Deployment Server on the local computer.

Altiris Deployment Solution Reference Guide

220

Chapter 10: Deployment Server Configuration Utility

Logon Account

Account

Opens the Server Login Account dialog box, which allows you to specify the
account used by the Deployment Server service.
The LocalSystem account requires a simple install that runs Deployment
Server services on the local computer, prohibiting access to network shares or
components.
With the LocalSystem account selected, you can click the Allow service to
interact with desktop box to place an icon in your system tray. This icon allows
you to quickly shut down the Deployment Server services or to view server
statistics (just as you can do from the Manage > Services and
Applications > Services > Altiris eXpress Server service).
The default setting is to provide a user name and password during installation.
With this option you can install the service on different computers and access
components across the network.

Options

Opens the Deployment Server Options dialog, which allows you to specify
Deployment Server options.

Logon Account
This Service Logon Account dialog is used to set up the user account used by Deployment Server.

Item

Description

Use the Local System account

Specifies that the LocalSystem account should be used by the


Deployment Server service. You can use this option if your
Deployment Server directory is located on the same computer
as the Deployment Server and if you don't need to access any
other file servers.

Use the following account and


password

Specifies that a user-defined account should be used by the


Deployment Server service. If this option is selected, you must
supply the appropriate username and password. The account
must have Administrator equivalent rights on the Deployment
Server computer. You must use this option if your Deployment
Server directory is located on a different server than the
Deployment Server.

To specify or change the Deployment Server service account


1

Open the Deployment Server Configuration Utility in the Control Panel of the Deployment
Server computer.

Click Account.

Choose whether you want to use the LocalSystem account or a user-defined account. If you
choose a user-defined account, you must enter the username and password.

Click OK.

General Option
The General tab provides features to set inventory polling and the timeout value when updating
connections of managed computers.
Update Inventory.

Set the polling intervals to inventory each managed computer for basic hardware
and software properties. The default value of 24 hours will inventory each computer no more than
once a day. However, an inventory is only performed when a computer (with the Deployment Agent)
starts up. If a computer is not restarted for a number of days, no inventory will be taken even though
the Update Inventory value is set to 24 hours. When the computer resets, even though the Update
Inventory interval has passed, the inventory will automatically be taken.

Altiris Deployment Solution Reference Guide

221

Chapter 10: Deployment Server Configuration Utility

Drive Mappings Option

Set the value to 0 to turn polling off and retain only the values already in the database for each
managed computer.
An inventory is only executed when the Deployment Agent starts up on the managed computer. As
a result, if the computer is not restarted for a period of days then no inventory will be taken during
that time even though the update inventory value is set to 24 hours. When the computer is restarted
and if the Update Inventory interval has elapsed, then an inventory will be run on the managed
computer.
Ping Time-out. Set the time-out value when using the Operations > Update all agent connections
feature or when automatically updating connections (Deployment Solution will automatically
update connections to client computers after 60 minutes if no activity has occurred). The console will
send out a packet to the IP address of each managed computer and wait for a response for the length
of time entered.

Drive Mappings Option


The Drive Mappings tab is used to add, edit, and delete drive mappings used by the Deployment
Server. Any drive mappings used to reference files need to be duplicated here.
For example, if you create a job that distributes software packages from a drive on another file server
using a mapped G: drive, then you will need to create a G: drive mapping on the Deployment Server
using this dialog box.

Item

Description

Drive Letter and


UNC Path

Displays the drive mappings with the mapped drive letters and the
corresponding UNC paths.

Add

Opens the Map Drive dialog, which allows you to create a drive mapping.
Driver Letter. Drive letter to which the drive mapping is mapped.
UNC path. UNC path to which the mapped drive points.

Modify

Opens the Map Drive dialog, which allows you to edit the drive letter or UNC
path of the selected drive mapping.

Remove

Removes the selected drive mapping.

Data store path

Specifies the path to stored packages and files and other DS functions (such as
license verification). The default path is C:\Program
files\Altiris\express\Deployment Server.
Note Do not use this setting to change the path to the Deployment Share.
Modifiying this setting does not automatically allow you to use another shared
directory other than the express share. To change the Deployment Share shared
directory, run a Custom install to establish another location for the Deployment
Share.

To create a drive mapping


1

Open the Deployment Server Configuration Utility in the Control Panel of the Deployment
Server computer.

Click Options and select the Drive Mappings tab.

Click Add.

Specify the Drive Letter and UNC Path.

Click OK.Click OK.

Click Yes to restart the service.

Altiris Deployment Solution Reference Guide

222

Chapter 10: Deployment Server Configuration Utility

Transport Option

To edit a drive mapping


1

Open the Deployment Server Configuration Utility in the Control Panel of the Deployment
Server computer.

Click Options and select the Drive Mappings tab.

Select the drive mapping you want to edit and click Edit.

Modify the Drive Letter and UNC Path as desired.

Click OK.Click OK.

Click Yes to restart the service.

To remove a drive mapping


1

Open the Deployment Server Configuration Utility in the Control Panel of the Deployment
Server computer.

Click Options and select the Drive Mappings tab.

Select the drive mapping you want to remove and click Remove.

Click Yes to confirm your decision. Click OK.

Click Yes to restart the service.

Transport Option
The Transport tab allows you to specify settings for the Deployment Server transport protocols.

Item

Description

Disable multicast support


(agents must connect using
TCP)

Disables multicast support, which means clients must connect to the


Deployment Server using TCP.

Multicast Address

The multicast address. This is used only if multicast is not disabled.

Multicast Port

Port used for the multicast. This is used only if multicast is not
disabled.

Multicast TTL

Specifies the number of "hops" or hubs that the client can go through
to multicast. This is used only if multicast is enabled.

TCP Port

The TCP port. This is used whether multicast is enabled or disabled.

Automatically update
clients

Automatically updates the Altiris Client for Windows on managed


computers if there is a difference (older or newer) between the client
available in the Deployment Server directory and the managed client.

Allow Encrypted Sessions

Allows encrypted sessions between the Deployment Agent and


Deployment Server. If the Deployment Agent data encryption is
turned on, then this Deployment Server option must also be turned on
to pass encrypted data between client and server.

To specify the Deployment Server transport


1

Open the Deployment Server Configuration Utility in the Control Panel of the Deployment
Server computer.

Click Options, and select the Transport tab.

Do one of the following, depending on the transport you want to use:

If you want to use multicast, do not select the Disable multicast support checkbox.

If you want to use TCP, select Disable multicast support and supply the Multicast Address,
Multicast Port, Multicast TTL, and TCP Port.

Click OK.

Altiris Deployment Solution Reference Guide

223

Chapter 10: Deployment Server Configuration Utility

Disk Imaging Option

Disk Imaging Option


The Disk Imaging tab allows you to specify when image multicasting is used and how much
bandwidth is used during multicasting.
Note When multicasting a disk image using the PXE Server, the boot disk on the PXE Server cannot
be configured with an Intel Universal NIC driver (also known as an UNDI driver). The multicasting
feature will be disabled for multicasting because of continued data corruption problems inherent
with the Intel Universal NIC driver. This unreliability results in random files being corrupted in the
image file, a problem that may appear immediately or go undetected until accessing the files later.
As a result, if the computers being imaged are booting to PXE boot files configured with an Intel
universal driver, then multicasting is disabled and all computers will be imaged using direct
connections.

Item

Description

Use disk image multicast


threshold of n clients

Specifies the number of clients that must be involved in a job before


image multicasting is used. If the number of clients is less than or
equal to the number specified, multicasting is not used. Set this value
to 0 to disable multicasting. If this option is not selected, multicasting
will be used whenever there are two or more clients.When
multicasting is not used, all clients become Masters and will read
from the image server independently. This option might be used if
your clients can read an image file from the server faster than trying
to coordinate masters and clients.

Limit each disk image


multicast to n Mbps

Limits the bandwidth used in a multicasting session to a user-defined


number of Mbps. This option prevents the multicasting operation
from using all of the available bandwidth on a network, so other
network traffic can take place at a reasonable rate.

To set when multicasting is used


1

Open the Deployment Server Configuration Utility in the Control Panel of the Deployment
Server computer.

Click Options and select the Disk Imaging tab.

Select one of the following depending on when you want to use multicasting:

If you do not want to use multicasting, select the Use disk image multicast threshold of n clients
checkbox and set n to 0.
If you want to use multicasting whenever there is more than one client, do NOT select the
checkbox.

Use disk image multicast threshold of n clients

If you want to use multicasting only when there are more than a specific number of clients,
select the Use disk image multicast threshold of n clients checkbox and set n to the number of
clients there must be more than before multicasting is used.

4.Click OK.
To set the maximum bandwidth used during multicasting
1

Open the Deployment Server Configuration Utility in the Control Panel of the Deployment
Server computer.

Click Options and select the Disk Imaging tab.

Select the Limit each disk image multicast to n Mbps checkbox and set n to the maximum
bandwidth you want a multicasting operation to use.

Click OK.

Altiris Deployment Solution Reference Guide

224

Chapter 10: Deployment Server Configuration Utility

Authentication Option

Authentication Option
The Authentications tab allows you to authenticate to an existing SQL Server database and to the
NetWare Server as a file access point.
Database Authentication
To access and authenticate to a specified Microsoft SQL Server database:
1

Click the Use SQL Server account authentication check box.

Enter the user name for the specified database.

Enter the password.

NetWare Server Authentication


To access and authenticate to a Novell NetWare Server:
1

Enter the user name for the selected server.

Enter the password.

Connections Option
The Connections tab allows you to allow or reject connections from the Deployment Agents based
on the IP subnet, IP address, and local interfaces.
Define Subnets
Select the Allow/reject agents based on their IP subnet box and click the Define Subnets button.
Click Add or Modify to enter or edit a network IP address and the corresponding mask.
Define IP Addresses
Select the Allow/reject agents based on their IP address box and click the Define IP Addresses button.
Click either the Allow or Reject option. Click Add or Modify to enter or edit a specific a range of IP
addresses to connect to the Deployment Server.
Define Interfaces
Select the Allow/reject agents based on their IP address box and click the Define IP Addresses button.
Select from the list of network adapter cards to allow or reject when connecting to Deployment
Server.

Debug Option
The Debug tab allows you to set debug options for Deployment Server and communication between
managed computers.
Engine Debug Logging.

Select this option to set the name and location of the logging report and the
logging level for Deployment Server. The Engine Debug Log is a single report that captures debug
information for Altris support personnel.
Log File Name: Set the path and name for the log text file. The default name is axengine.log in the
Deployment Server shared directory.
Max File Size:

Set the size of the text file by entering the maximum file size allowed.

Logging Level:

Enter the logging level. This number can be from 1 to 9, with nine the deepest
logging level and one the most cursory logging level. Altiris support will instruct you on the
required logging level for your issue.

Log Agent Communication with Engine. Select the directory path and name to log error messages
between managed computers and the Deployment Server.

Altiris Deployment Solution Reference Guide

225

Chapter 10: Deployment Server Configuration Utility

Debug Option

Log Directory.

Set the path of the folder to collect the client error messages. Each managed
computer will have its own log file in this directory named <the computer ID of the managed
computer>.log.

Max File Size.

Set the size of each log file by entering the maximum file size allowed.

Altiris Deployment Solution Reference Guide

226

Pre-boot Execution and Imaging


Deployment Solution has the ability to perform work on computers before the normal operating
system loads. To do this, a managed computer is booted into an environment where it can
communicate with your Deployment Server to perform tasks.
In DS, this preboot environment is called automation. In order to perform image capture and
deployment, scripted installs, registry backups, or execute certain scripts, you must implement a way
to boot computers into this evironment.
This section provides the information you need to configure a boot method, including PXE, and
select an operating environment for automation tasks. Additional sections are included containing
details on the utilities provided by Deployment Server to manage these processes.
Quick Links
Automation Pre-boot
Environment on page 228

Learn about the available automation boot methods and


environments, and determine which best suits your deployment.

Boot Disk Creator on


page 237

Learn about using the Boot Disk Creator utility to create and install
automation configurations.

PXE Server on page 252

Learn about the features of PXE and how to deploy PXE services on
your network.

PXE Configuration Utility Learn about using the PXE Configuration utility to perform PXE
on page 261
configuration.
RapiDeploy Imaging on
page 281
RapiDeploy Technical
Reference on page 298

Learn about the RapiDeploy imaging utility.

Altiris ImageExplorer on Learn how to view and modify RapiDeploy images using the Image
page 318
Explorer utility.

Altiris Deployment Solution Reference Guide

227

Chapter 11:

Automation Pre-boot Environment


Deployment Solution uses two modes to manage computers:
Automation

A pre-boot environment used primarily for imaging. Automation


is also used for scripts which must be executed before a computer boots and for registry backups.

Production

The normal operating system of the computer. Production tasks


include software installation and personality capture.

Several of the tasks you perform to manage your network can be completed in the production
environment. However, other tasks, primarily imaging, must be performed before the operating
system boots. In DS, this pre-boot environment is called the automation environment, or booting into
automation mode.
The following table contains a list of DS tasks and the environment in which they execute:
Production Tasks

Automation Tasks

Distribute Software

Create Disk Image

Capture Personality

Distribute Disk Image

Distribute Personality

Scripted OS Install

Get Inventory

Backup Registry

Copy File to

Restore Registry

Modify Configuration

Run script

Power Control
Run script
In order to manage computers in a pre-boot state, you must select a method to boot computers to
automation, then decide which OS to use in the automation environment.
DS provides support for a broad range of boot methods and automation operating systems; this
section helps you decide which works best for your environment.
In order to set up automation, you must make the following decisions:

Which pre-boot operating system do I want to use?

Which automation boot method works best for my environment?

Which pre-boot operating system should I use?


Deployment Solution supports the following automation operating systems: Windows PE, Fedora
Linux, MS DOS, and FreeDOS. This section provides an overview of the available automation OSs
so you can find an environment (or environments) that suit your needs.

Altiris Deployment Solution Reference Guide

228

Chapter 11: Automation Pre-boot Environment

Which pre-boot operating system should I use?

An important thing to note is that the automation environment you use is not constrained by the
production OS on the computer. All of the DS automation tools support these OSs, so you can
perform DS automation tasks in any OS (Linux computers can be imaged from DOS, Windows
computers can be imaged from Linux, and so on).
You might even use two automation OSs for different tasks within the same job. For example, you
might use a vendor-supplied tool to perform a BIOS update in DOS, then boot to Windows PE or
Linux to perform an imaging task.
When you set up your test environment, you might want to run automation jobs in multiple OSs to
see if one performs better in your environment.
The following sections contain an overview of the automation operating systems:

DOS (page 229)

Windows PE (page 229)

Fedora Linux (page 229)

Although you can use these environments to perform a wide-variety of management using scripts
and other tools, support for these environments is limited to the task performed by Deployment
Solution.

DOS
DOS is still used often today as a pre-boot environment, though new technologies have emerged that
might better suit your environment, such as Windows PE.
The largest roadblocks most companies face when using DOS are access to drivers that support
modern hardware, and security concerns. DOS still performs well for several tasks though, and can
be a good choice if you have the proper driver support.
DOS typically requires only around 1 MB of space.
DOS provides an additional advantage in a PXE environment. When performing an automation task
on multiple computers, the PXE server can use multicast to boot automation, which enables large
numbers of managed computers to boot DOS simultaneously.

Windows PE
Windows PE (Windows Pre-boot Environment) is the next generation boot environment for
Windows computers. Windows PE provides several advantages over DOS, including better driver
support (Windows PE uses the same drivers used by the other modern versions of Windows),
increased speed, and generally more functionality.
Windows PE typically requires around 150 MB of space.
The biggest drawbacks are its size, which causes increased boot time, especially when booting over
the network using PXE, and its licensing requirements. Additionally, clients using Windows PE
require at least 256 MB of RAM.

Fedora Linux
Fedora Linux provides an alternate pre-boot environment to DOS or Windows PE. The Fedora
distribution used by DS includes the 2.6.11 Core 3 kernel and a number of network drivers supported
by this kernel. Additional drivers can be compiled against this kernel and added as well. Many
vendors provide gigabit and wireless drivers for Linux that are not available in DOS.
Linux typically requires around 10 MB of space.
Linux can be a good choice if you do not want to license MS DOS or Windows PE, but you need
updated driver support.

Altiris Deployment Solution Reference Guide

229

Chapter 11: Automation Pre-boot Environment

Which Automation Boot Method Works Best for My Environment?

Which Automation Boot Method Works Best for My


Environment?
After you have determined which OSs you want to use in the automation environment, you need to
determine how to boot these computers into automation. Again, DS supports a broad range of
environments: PXE, automation partitions, or boot media (CD, USB device, or floppy).
This section provides an overview of the available boot methods to help you select the method that
works best for your environment, and contains the following:

PXE (page 230)

Automation Partitions (page 231)

Boot Media (CD, USB Device, Floppy) (page 231)

PXE
Pre-boot Execution Environment (PXE) is an industry standard developed to boot computers using
a network card. PXE can boot computers regardless of the disk configuration or operating system
installed, and doesnt require any files or configuration settings on a client. After PXE boot is turned
on in the BIOS, a computer can communicate with your DS PXE server to receive automation jobs.
PXE provides a number of advantages, especially when you are using the initial deployment features
of DS, which enables you to remotely deploy an image to a computer which has no software
installed.
For example, the receiving department of your company could have PXE enabled on their subnet.
When a new computer arrives, a technician could quickly unpack and plug the computer into the
network, and possibly enable PXE boot if it was not enabled by the manufacturer.
When this unknown computer contacts the Deployment Server, it is assigned an initial deployment
job, which could image the computer with the corporate standard image, install additional packages,
then power off the computer. The computer is now ready for delivery with minimal effort.
PXE also provides an advantage if you need to use multiple automation OSs in your environment.
Since the image containing the automation OS is downloaded when a task is executed, different OS
environments can easily be assigned to different tasks.
At the same time however, this can be a disadvantage if you are using an OS with a large footprint,
such as Windows PE, since the entire image must be downloaded each time you run an automation
task. If you often run automation jobs, especially on several computers simultaneously, embedding
the automation OS on the disk is faster and significantly reduces network traffic.
It is also possible to use PXE for initial deployment, then install an automation partition as part of
the deployment. In this case, you could use the initial deployment features of PXE for arriving
computers, then install an automation partition in case you need access to automation at a later time.
This configuration does not require PXE in your general network environment, but still provides
access to the automation environment without physical access.
When using the DOS automation environment, PXE provides an additional advantage: multicast
boot. This enables your PXE server to simultaneously boot up to 100 computers in a single session
to perform automation work. PXE multicast booting is not provided by Windows PE, and is not
supported on Linux.
Images can still be deployed using multicast to all supported automation environments, but nonDOS OSs must be booted using unicast, which is considerably slower.

Altiris Deployment Solution Reference Guide

230

Chapter 11: Automation Pre-boot Environment

Configuring Automation Operating Systems

Automation Partitions
An automation partition is a sector of your hard disk drive partitioned and managed by DS. This
partition contains the automation operating system and the files needed to contact your Deployment
Server, and must be present on each managed computer.
The biggest advantage to an embedded partition is that it does not require PXE, yet it still enables
you to boot into automation remotely. The biggest disadvantages to embedded partitions is that they
consume space on the drive, they requires an existing partition on the drive, and they must be
manually installed from a disk on Linux and Unix OSs.
Another drawback, depending on your configuration, might be the fact that only one automation OS
can be installed to a managed computer that is using an automation partition. If you have tools that
are supported only in DOS, this might limit you to DOS for all automation tasks on a particular
managed computer.
Automation partitions have an additional advantage in some configurations. Optionally, you can
create a different type of automation partition, called a hidden partition, to store an image (or other
files) locally.
This provides advantages in environments where computers need to be re-imaged often, or in
environments where there is limited bandwidth or network connectivity. Since the image is stored
locally, the time needed to create and restore images is greatly reduced and network traffic is
significantly reduced as well.

Boot Media (CD, USB Device, Floppy)


Generally, the biggest drawback to boot media is that it forces you (or someone else) to physically
access the managed computer. However, if you are managing smaller numbers of computers, or do
not plan to access the automation environment often, it might be a good choice. Also, if you have
employees with the ability and access to boot their own computers using disks you provide, this
could also be a good solution.
Boot media has some configuration limitations though. DS is designed to manage computers
remotely, even in the automation mode, and several tasks and jobs require access to both the
production OS and the automation environment (for example, an imaging operation first captures
configuration details from the production OS before booting to automation to capture the image).
Because of this, it is often difficult to schedule a job, then coordinate booting the managed computer
to the right environment at the right time. If you assign a job which requires booting into automation
mode, the boot disk must be present at the right time to boot automation. If a complex job requires
access to the production environment during this time, the BIOS will most likely continue to boot to
automation until the boot media is removed. If this job, or a subsequent job, requires automation
access again, the boot media must be re-inserted.
To avoid these issues, some customers load the DS tools, the RapiDeploy imaging executable, and
the image on physical media. They then boot a computer, execute the necessary commands, then
provide the required image files. In this circumstance, the remote management capabilities of DS are
not being used, so the process is more manual, but it does not require network access.
This works especially well when managing thin clients or other computers where all necessary files
can fit on a single disk or USB device.

Configuring Automation Operating Systems


The following sections guide you through installing and configuring the automation operating
systems supported by DS:

Altiris Deployment Solution Reference Guide

231

Chapter 11: Automation Pre-boot Environment

Configuring Automation Operating Systems

Installing Windows PE, Linux, or DOS


Automation operating systems are installed using the Boot Disk Creator, which is available in the
Deployment Console by clicking Tools > Boot Disk Creator.
The following files are required to install the listed automation OS:
WindowsPE

Windows PE 2005 installation CD. Currently, Windows PE is


available to volume licensing customers through Microsoft.
See http://www.microsoft.com/licensing/programs/sa/support/
winpe.mspx for information on obtaining Windows PE.
Windows 2003 Server SP1 installation CD.

Linux

The .frm file containing Fedora Linux. This file is available for
download from the Altiris Solutions center at (URL)

MS DOS

A Windows 98 SE, Windows 98, or Windows 95 installation


CD, and the proper licensing to use this on the intended
computers. Files are copied from the win98 or win95 folder
from this installation CD.

FreeDOS

The .frm file containing FreeDOS. This file is available for


download from the Altiris Solutions center at (URL). For additional information on FreeDOS visit www.freedos.org.

To install:
1

In Deployment Console, click Tools > Boot Disk Creator.

In Boot Disk Creator, click Tools > Install Pre-Boot Operating Systems.

Click Install and complete the wizard, providing the files listed in the previous table when
prompted.

For complete details on this process see Boot Disk Creator on page 237.

Altiris Deployment Solution Reference Guide

232

Chapter 11: Automation Pre-boot Environment

Configuring Automation Boot Methods

Adding Additional Files


Occasionally, you might need to make additional files available within an automation environment,
such as utilities or mass storage drivers. These files can be added to every automation configuration
of a specific type, or to select configurations only. This is determined by the location you add the
files in Boot Disk Creator:

Files added here are included in


WinPE configuration 1 only.

Files added here are included in


every Windows PE configuration.
The following example provides an overview of this process.

Adding Mass Storage Drivers for Windows PE


1

Select either the Windows PE Additional Files folder, or a specific Boot Disk Creator
configuration.

Right-click and select add > Folder. Using this add folder command, create the following path:
i386\system32\diskdrivers

Within the diskdrivers folder, create the necessary folders to contain your drivers. The folders
you add should contain a txtsetup.oem file, and at least one *.sys file, and possibly additional
files. You must also ensure that any sub-folders specified by txtsetup.oem are included, and that
the [defaults] section references the proper device driver (some textsetup.oem files might support
multiple devices and drivers, and the proper device must be specified in the [defaults] section).

The diskdrivers path is for adding mass storage drivers. If you are adding different driver types, you
might need to modify this path.

Configuring Automation Boot Methods


When pre-boot tasks need to be performed, DS sends a message to the client computer to restart in
the automation environment. This includes a shutdown command issued from DS, and a
modification to the MBR if using an automation partition.
After the managed computer reboots, the automation environment is loaded from PXE, an
automation partition, or from boot media. The deployment agent then contacts the Deployment
Server.
After a connection is established, the Deployment Server sends the client computer its assigned jobs
and tasks. After the automation tasks run, a status message is sent to the Deployment Server
indicating that all work is complete. The Deployment Server then sends a message that the client
computer should reboot back to the Production environment (the MBR is then restored when using
automation partitions).

Altiris Deployment Solution Reference Guide

233

Chapter 11: Automation Pre-boot Environment

Configuring Automation Boot Methods

The following sections guide you through the process of setting up PXE, automation partitions, or
media to boot your computers into the automation mode:

Configuring PXE

Configuring Automation Partitions

Configuring Boot Media (CD, USB device, Floppy)

Configuring PXE
PXE is a server-based technology, and requires additional components on your DS server, and
possibly other computers. Setting up and configuring PXE is covered in detail in PXE Server on
page 252.

Configuring Automation Partitions


DS provides two types of automation partitions:
Embedded Partition

A small embedded section installed on the production partition


of a managed computer which contains the automation OS. Depending on the OS, the size varies from 5 to 200 MB (you specify the size when the partition is created based on
recommendations).

Hidden Partition

A larger partition installed on the hard drive of a managed computer to contain not only the automation OS, but to provide
room to store images and other files. This partition is not normally viewable in the production OS.

An embedded partition doesnt create an actual disk partition, it reserves space on an existing
partition by marking the sectors on the disk as unusable. The target drive must have an existing
partition before an embedded partition can be installed.
A hidden partition creates an actual disk partition, but this partition is hidden from normal view
within the production system, though it is still viewable by FDISK or by an administrator. The
partition is listed as a non-DOS partition.
When a computer using an automation partition is assigned jobs, the Master Boot Record (MBR) of
the computer is modified to boot to this hidden partition. After the work is completed, the MBR is
restored to the previous configuration.
Hidden partitions are very useful for computers which are imaged often, such as those in a test lab
or provided for general use (such as a hotel or a library). After the visiting person is done using this
computer, you may want to quickly re-image to ensure that the next visitor finds the computer in
good working order. In these circumstances, a hidden partitions enables you to quickly restore an
image without needing access to a high bandwidth network.
Automation partitions can be installed using an installation package deployed from DS (windows
only), or installed from a CD, USB device, or floppy. This is different than using boot media to
access automation, because the automation partition media is used once per computer to install, then
the partition is used to perform tasks.
Using boot media to access automation doesnt leave any files on the computer, but the media must
be used each time you want to access automation.

Configuring Boot Media (CD, USB device, Floppy)


Creating and using boot media is a straightforward process. Boot media boots a managed computer
to automation without leaving any files on the computer, and can be installed to CDs, USB devices,
or floppy disks.
Boot media is created directly from the Boot Disk Creator utility.

Altiris Deployment Solution Reference Guide

234

Chapter 11: Automation Pre-boot Environment

Deploying Automation to Managed Computers

Deploying Automation to Managed Computers


Automation partitions and boot media configurations are created using the Boot Disk Creator utility.
PXE configurations are created using the PXE configuration utility.
This difference is due to the way in which the automation OS is deployed to the managed computer.
Automation partitions and boot media use install packages or boot disks, while PXE uses a
configurable menu to provide boot options, with each option on the PXE menu linked to a specific
automation configuration.
This section contains guidelines to create PXE, automation partitions, or boot media configurations
and deploy these configurations to managed computers.

Using Automation Partitions or Boot Media


1

Install the automation OSs you want to use, as explained in Installing Windows PE, Linux, or
DOS.

In Boot Disk Creator, Create a new configuration. The wizard is accessed by clicking File > New
configuration.
This configuration contains the automation OS files, network drivers, IP address of your server,
and other settings which control how the managed computer communicates with DS.
This configuration does not specify how this automation configuration is installed. This is done
using the Create Boot Disk wizard, which is launched automatically after you create a
configuration.

The Create Boot Disk wizard provides three options:

Create an automation parti- Creates an executable, or configures a CD, USB device, or


tion install package
floppy to install the automation environment. This process
is executed once per device. After that, the computer uses
the files from the automation partition.
Select this if you are using automation partitions. For managed linux computers, you need to use a CD, USB device or
floppy because not executable is provided for this platform.
Create an automation boot Configures a CD, USB device, or floppy with the files necdisk
essary to boot a computer to automation mode. After booting, the computer executes any automation work previously
scheduled, or waits for work to be assigned.
Select this if you are using boot media to boot computers to
automation. None of these files are installed, so the media
must be used each time you need to access automation.
Create a network boot disk Configures a CD, USB device, or floppy with the files necessary to boot to a prompt.
This is useful if you have management task you need to perform that doesnt require interaction with DS, as your Deployment Server is not contacted in this scenario. None of
these files are installed to managed computer.
4

After selecting how you want to install automation, complete the wizard.
Complete details on using the Boot Disk Creator are contained in Boot Disk Creator on
page 237.

You can also uninstall an automation partition using an install package, or configure a CD, USB
device, or floppy from Boot Disk Creator.

Altiris Deployment Solution Reference Guide

235

Chapter 11: Automation Pre-boot Environment

Automation Agents

Using PXE
1

Install the automation OSs you want to use, as explained in Installing Windows PE, Linux, or
DOS.

In the PXE Configuration utility (Start > All Programs > Altiris > PXE Services > PXE
Configuration Utility), create a new menu item to correspond to the automation configuration
you want to install.

Click Create Boot Image to launch the configuration wizard. This wizard is identical to the
wizard used when creating configurations for automation Partitions or boot media.
When this options is selected from the PXE menu, the necessary files are loaded, the job is
performed, then the computer boots to the production OS. None of these files are saved on the
managed computer, they are downloaded each time the computer boots to automation.

Provide any additional configuration options, then click Save.

Automation Agents
Automation Agents are provided for each of the pre-boot operating systems supported by
Deployment Server. Automation Agents are the client software which communicates with DS to
execute jobs and tasks in the automation mode.
The following table contains the Automation and Production Agents used by each OS in each
environment:
Operating System

Automation Agent

DOS

Bootwork.exe

Windows

Production Agent
AClient.exe

Windows PE

AClient.exe

Linux

ADLagent

Altiris Deployment Solution Reference Guide

ADLagent

236

Chapter 12:

Boot Disk Creator


Altiris Boot Disk Creator (BDC) is a utility tool that comes with Deployment Solution and lets you
create configurations for pre-boot environments. You can create DOS, Linux, and Windows
Preinstallation Environment (Windows PE) configurations, which gives you greater flexibility in
managing client computers. The configurations you create can be assigned to automation tasks
within deployment jobs that will boot client computers to the automation environments. The
Deployment Solution automation tasks include the following:

Run Script

Create Disk Image

Distribute Disk Image

Scripted OS Install

Backup Registry

Restore Registry

The Deployment Server sends a message to the client computer that the type of task within a
deployment job requires an automation environment. The client computer then boots to the
automation environment you created using Boot Disk Creator and connects with the Deployment
Server to run the tasks that have been assigned by the deployment job. This feature lets you create a
single deployment job with multiple tasks that will boot to the automation environment you want
when each task runs.
The Boot Disk Creator Utility gathers data as you create new configurations. The base pre-boot
operating system files, disk drivers, files you add to the Additional Files folder (in the treeview of
Boot Disk Creator), and all the settings you selected in the New Configuration Wizard are added to the
boot image. Based on the type of pre-boot environment you are creating, the appropriate Automation
Agent is also added. Boot Disk Creator then creates the type of bootable media you want to use when
booting client computers to automation. Boot Disk Creator supports the following bootable media:

Floppy disks

Bootable CDs with an ISO image

USB flash drives

Windows installation packages

See Create Boot Disk (page 246), Automation Partitions, Network and Automation Boot Disks
(page 246).
Before creating configurations, you must first install the pre-boot operating system files for the types
of pre-boot configurations you want to create. When the Deployment Solution gets installed, you
have the option to install the pre-boot operating system files at that time. If there are no files
installed, you can use the Install Pre-boot Operating System Files feature within Boot Disk Creator
to install the necessary pre-boot operating system files.
Example: you can install DOS, Linux, or Windows PE operating system files so you can create any
type of configuration any time you want. Or, you can install only DOS and Windows PE system files
and then install Linux later. You can only create configurations for the type of pre-boot operating
system files you have installed. This feature also lets you update pre-boot operating system files
when you receive new releases of software and makes it easy to install system files any time you
want. See Install Pre-boot Operating System Files (page 249).

Altiris Deployment Solution Reference Guide

237

Chapter 12: Boot Disk Creator

The New Configuration Wizard is the main process of Boot Disk Creator. This is how you select the
type of pre-boot environment configuration you want to create, along with other settings such as, the
type of network adapter, network server information, TCP/IP information, and more.
After the wizard completes, the Create Boot Disk Wizard automatically displays. This is the
production process of Boot Disk Creator that lets you select the boot disk creation method for how
you want to implement the configuration you created. You can create floppy boot disks, which are
used for DOS configurations since Linux and Windows PE system files are too large to fit on a
floppy. Network and automation boot disks can create ISO images, which you can save to bootable
CDs using your own third party CD burning software, or you can select a flash drive from the
Bootable drive drop-down list. You can also create a Windows Installation package to run in a
Windows production environment, which will install an embedded (recommended) or hidden
automation partition on the client computers hard drive. See Automation Partitions, Network and
Automation Boot Disks (page 246).
If you create an Automation boot disk, the Automation Agent is added to the configuration so that
when you boot client computers, they will try to connect to the Deployment Server. If you select
Network boot disk, client computers will boot to the network server you specified in the New
Configuration Wizard, displaying only a users prompt. See New Configuration Wizard (page 239).
Boot Disk Creator can also be accessed from the PXE Configuration Utility, so that you can create
boot menu options using the New Configuration Wizard. You can also create boot configurations
directly from Boot Disk Creator, and then import the boot images into the PXE Configuration
Utility. The PXE Configuration Import feature lets you import images that have been created by
Boot Disk Creator or any other third party imaging software, but you cannot edit the boot images
after they have been imported. See PXE Configuration Utility Help.
To help you manage the configurations you create, Boot Disk Creator uses colors to inform you
which type of pre-boot configuration you are editing. The colors on the display change when you
select a configuration in the treeview of the utility. The colors indicate the following:

Black:

Blue:

Green:

Red:

No configuration has been selected or there are no configurations to select.

DOS configuration
Linux configuration

Windows PE configuration

See Edit Configurations (page 244).


The Boot Disk Creator Utility is easy to use because each process guides you through the settings
and options you can select to create pre-boot environment configurations to help manage automation
tasks used by the Deployment Server.

To start the Boot Disk Creator tool, open the Deployment Console and click
the button on the toolbar, or click Tools > Boot Disk Creator.

Altiris Deployment Solution Reference Guide

238

Chapter 12: Boot Disk Creator

Toolbar Description

Toolbar Description
The buttons on the toolbar help you navigate to the tasks you want to perform within Boot Disk
Creator in one click. The options are:
Toolbar Description

Buttons

Description
New Configuration Wizard (page 239): Creates new
configurations that is used when booting client computers to
automation or a network prompt.
Create an Automation Install Package (page 247): Creates
and installs an embedded automation partition to a client
computers hard disk, using an installer package.
Remove Automation Partition (page 248): Removes an
automation partition from a client computers hard disk.
Create Automation Boot Disk (page 247): Creates
automation boot disks to manually boot client computers to
automation.
Create Network Boot Disk (page 248): Creates network boot
disks to manually boot client computers to a specified
network server.

New Configuration Wizard


You can create as many configurations as needed to support varying types of computer
environments. Before you begin, you must install the pre-boot operating system files that Boot Disk
Creator uses to create new configurations. See Install Pre-boot Operating System Files (page 249).

To start the New Configuration Wizard, click the button on the toolbar of the
Boot Disk Creator tool, click Ctrl+N, or click File > New Configuration.

Configuration Name
This is the first page of the New Configuration Wizard, which is the same for DOS, Linux, or
Windows PE. You must enter a name of for the configuration to make the Pre-boot Operating System
for this Configuration fields active. The description field is optional but helps you to know what the
configuration contains, such as the file server type, NIC drivers, and any additional files you want
to add.
Field Definitions
Name: The configuration name you enter displays in the Configurations treeview after the wizard is

completed.

Enter a description for the configuration. (Example: enter the type of computer,
operating system, network adapter, and any other characteristics that will help you identify this
particular configuration.) After the Create Configuration and Create Boot Disk wizards complete, if
you select the configuration from the treeview, the description you entered for this field displays at
the top of the right pane.
Description:

Pre-boot Operating System for this Configuration: Boot Disk Creator supports DOS, Linux, and
Windows PE operating systems to create pre-boot environments. Select the pre-boot operating
system, and then click Install Pre-boot Operating System Files (page 249) to install pre-boot
operating system files.

Altiris Deployment Solution Reference Guide

239

Chapter 12: Boot Disk Creator

New Configuration Wizard

File Server Type (DOS)


The Deployment Share stores image files, packages, and data files. By default, the Deployment
Share is installed to the Deployment Server, but it can be on another server, depending on the
whether you selected a Simple or Custom Deployment Solution installation.
Field Definitions
Select this option to store images on a Microsoft server using TCP/IP network
communications (recommended). However, if you use IPX to communicate with a Microsoft server,
select the IPX checkbox at the bottom of the page.

Microsoft Windows:

Novell NetWare (VLM): Select this option to store images on a NetWare server with VLM clients, using

IPX network communications.

Novell NetWare (Client32):

Select this option to store images on a NetWare server with 32-bit clients.

Use IPX to communicate with Netware: Select


Novel NetWare (Client32) server.

this checkbox if IPX is the network protocol for the

Network Adapter
The drivers listed in the Network Adapters window vary depending on the type of configuration you
are creating. You can install pre-boot operating system files for DOS, Linux, or Windows
Preinstallation Environment (Windows PE). See Install Pre-boot Operating System Files (page 249).
Example: After installing the pre-boot operating system files for Windows PE, the Windows NIC
drivers that are available to create a Windows PE configuration display, and are automatically added
to the new configuration. If you select Auto-detect network adapter, Windows PE determines which
network adapter driver to use.
Select a driver from the network adapters driver list. You must create a new configuration for each
type of network adapter that is installed on client computers, unless you want to create a Multi-NIC
configuration. See Multi-Network Adapter Configurations (page 241). If you want to add or change
adapter settings (such as I/O Memory, IRQ, and PCMCIA for DOS configurations) click Advanced.
See Advanced (page 241).
Advanced Features
The network adapters you select must support DOS, Linux, or Windows PE so that client computers
can connect to a network or Deployment Server, depending on whether you create automation
partitions, or network or automation boot disks. The Have Disk (page 240) button lets you install
network adapter drivers from a disk, CD, or network folder. The Internet (page 241) button lets you
connects to an Altiris supported web site to download and install network adapter drivers. The
Advanced (page 241) button lets you further define network adapters and their drivers.
Field Definitions
Allow selection of multiple network adapters: Select this option to add multiple network adapter drivers

to a single PXE boot file configuration. This feature lets you build configuration files to boot
multiple computers that contain different types of network adapter cards. See Multi-Network
Adapter Configurations (page 241).

Select this to have Windows PE auto-detect the type of adapter that is


in a client computers when the boot image runs.

Auto-detect network adapter:

Have Disk
You can add network adapter drivers by using any disk media or navigating to a folder. Network
adapters can be downloaded from the manufacturers Web site and saved to a folder or a disk to be
installed later. New network adapters come with a floppy disk or CD to install the appropriate
drivers.

Altiris Deployment Solution Reference Guide

240

Chapter 12: Boot Disk Creator

New Configuration Wizard

Internet
Altiris supports many manufacturer network adapters and supports a Web site for you to download
the latest NIC drivers. From the Network Adapter page, click Internet to launch the Web browser and
connect to ftp://support.altiris.com/support/NIC_drivers/. Download the driver you want, and then
unzip the files it to a folder on the hard drive. Click Add Driver and the driver you downloaded will
be added to the Network Adapters list.

Advanced
This options lets you add or change settings for network adapter cards so they will work correctly
when using DOS configurations. If you are creating a Linux or Windows PE configuration, this
option is not available. From the Network Adapter page, click Advanced. Refer to the following
properties and values.
Microsoft clients

EMM386 Memory (config.sys):

Advanced settings (protocol.ini):

Memory (protocol.ini):

IRQ (protocol.ini): Add

config.sys file.

Append memory address information to this line in the


Add parameters to the NIC section of the protocol.ini file.

Add parameters to the network setup section of the protocol.ini file.


parameters to the network setup section of the protocol.ini file.

Novell VLM clients

Emm386 memory (config.sys): Append

config.sys file.

Advanced settings (config.sys):

memory address information to this line in the

Add parameters to the NIC section of the net.cfg file.

Novell Client 32

Emm386 Memory (config.sys):

config.sys file.

Append memory address information to this line in the

Advanced settings (driver command line):

file.

Add driver command-line entries to the landrv.bat

Multi-Network Adapter Configurations


If you are creating a DOS configuration, when you select Multi-NIC configurations, a list of supported
drivers displays. You can select Multi-NIC drivers to be included in the configuration by pressing
Shift-Click or Ctrl-Click. After a client computer boots using a multi-network adapter configuration,
Boot Disk Creator applies the driver that matches the first network adapter card that it detects.
Example: if you are going to use the multi-network adapter configuration for several different client
computers, this option can save you time and effort in booting different computers. However, if a
client computer has 2 NIC cards and you use the multi-network adapter configuration to boot the
computer, the first NIC card is detected and can potentially be the wrong network adapter required
to connect to the Deployment Server.
Multiple Network Adapters Load Order
This option is for DOS and Windows PE configurations only. This lets you specify which order the
physical network adapters will be detected when the client computer boots.
Example: If most client computers have a Broadcom Ethernet adapter, but some computers have a
3Com10/100 LAN PC Card Fast Ethernet card, you would use Up and Down to move the Broadcom
Ethernet adapter to the top of the list.

Altiris Deployment Solution Reference Guide

241

Chapter 12: Boot Disk Creator

New Configuration Wizard

TCP/IP Protocol Settings


This page lets you set up TCP/IP protocol settings for boot configurations. TCP/IP is the default
protocol when client computers boot to automation on a Windows network. If you are using the IPX
protocol, Deployment Server uses its own IP stack to work on IPX networks.
Field Definitions
Obtain an IP address from a DHCP server: Select this option if you want client computers to obtain an

IP address from a DHCP server.

Use a static IP address: Select this option if you want a client computer, using this configuration, to
be assigned a specific IP address. Enter an IP address, Subnet mask, and default gateway. You can
also enter a primary and secondary WINS address if you need to resolve IP addresses and naming
conventions. This option also requires that you create a configuration for each client computer, so
that the IP address is not the same for all computers.

Altiris Deployment Server Communication


This option lets you set communication properties for the Deployment Server. The Deployment
and Port fields are critical because they define how client computers establish
communications with the Deployment Server.

Server IP address,

You can also specify how you want to run the Automation Agent, either from the Deployment Share
or from the local hard disk. However, this feature is only for Linux and Windows PE configurations,
since DOS configurations always run the Automation Agent from the Deployment Share. See the
Automation Agent Location field definitions below.
Example: The TCP port on the Deployment Server is set to 402 and the Port field in the Boot Disk
configuration is set to 502. This would result in client computers not being able to communicate with
the Deployment Server, because the port numbers do not match. To establish communications
between client computers and the Deployment Server, change the Port field in the Boot Disk
configuration to 402.
Note: The settings on this page are only used if you create an automation boot image where the

Automation Agent needs to know how to find the Deployment Server. If you intend to create a
network boot disk, you can ignore this page by clicking Next, as none of the properties will be used
to create a network boot image.
To set the TCP port on the Deployment Server

From the Deployment Server, click Start > Control Panel > Deployment Solution Configuration

applet > Options > Transport tab.

Enter the TCP port number.

Click OK.

Use TCP/IP multicasting to find the Altiris Deployment Server: Select this option to use TCP/IP
multicasting to find the Deployment Server. When client computers boot to automation using this
configuration, a multicast packet will broadcast across the network to find where the Deployment
Server is located.

Multicast IP address:

Port: This option defines which port client computers will use to communicate with the
Deployment Server Engine, which manages the Deployment Database, sends job commands
to the Deployment Agent, and more.

Server name: When you select Use TCP/IP multicasting to find the Altiris Deployment Server, a
multicast packet will broadcast to the server you specify. If you leave this field blank, the
client computer will connect to any server responding to the multicast packet.

Enter a multicast IP address for client computers to send a broadcast


packet across the network to find the Deployment Server.

Altiris Deployment Solution Reference Guide

242

Chapter 12: Boot Disk Creator

New Configuration Wizard

Use TCP/IP to connect to the Altiris Deployment Server: Select this option to connect to a specific

Deployment Server. You must select this option if your network adapter or network does not support
multicasting. See your network adapter documentation or call the manufacturer or consult with your
IT department for information.

Server IP address: Enter the IP address of the Deployment Server to access information stored

Port: This option defines which port client computers will use to communicate with the
Deployment Server Engine, which manages the Deployment Database, sends job commands
to the Deployment Agent, and more.

in the Deployment Share. If you are using the Intel Universal NIC driver (UNDI), the IP
address is required.

Automation Agent Location


Remote: Select

this option to run the Automation Agent from the Deployment Share. This ensures
that you are running the latest version of the agent when the client computer boots to the automation
mode.

Local: Select

this option to run the Automation Agent from the local boot image, which is included
in the automation partition or in bootable media. The Automation Agent that boots the client
computer to automation mode, will always be the same version as when it was originally created. If
you want to update the Automation Agent to the latest version, you must reinstall the automation
partition or recreate all bootable media.

Network Connection
This option lets you define how client computers connect to the Deployment Share or a file server
where image files are stored.
Window
Workgroup: Enter

the workgroup for the Deployment Share or file server.

NetWare
Server name: Enter the server name for the Deployment Share or file server. Click Advanced to enter
a NetWare context for the server, and then select a Frame type if it is different than the default value

of 802.2.

User name: Enter the authorized user name that was set up when the Deployment Share directory was
created. If you did not assign a User name and Password when for the Deployment Share or file server
was created, leave this and the Password field blank.
Password:

Enter the password for the user name.

Confirm password: Enter the password for the user name as confirmation that you entered the proper
password in the Password field.

Network Drive Mappings and Mount Points


This option lets you set up drive mappings (for DOS and Windows PE) or mount points (for Linux)
so that when client computers boot to automation or a network prompt, they will connect to the
appropriate server. You can create multiple drive mappings or mount points. However, if you are
creating a DOS configuration, the first mapped drive you specify must connect to the Deployment
Share.
Field Definitions
Manually create drive mapping: Select this option if you want the drive mappings to be included in the

autoexec.bat file when client computers boot to automation.

By default, the mapped drive that displays is F: \\<Deployment Share server>\eXpress. Click
the drop-down arrow and select a different drive letter if F: is already in use.

Drive:

Altiris Deployment Solution Reference Guide

243

Chapter 12: Boot Disk Creator

New Configuration Wizard

Enter the path for the Deployment Share. The path you enter will map to the drive letter you
selected in the Drive field. You can also click Browse to navigate to the Deployment Share if you are
unsure of the directory path or if the image files are store on a file server.
Path:

Example:

Windows users:

NetWare users:

Linux users:

\\server\share

server\volume:directory

//server/mount point

Note: When entering Linux mount points, you must put a single quote around folders or filenames

that contain either a period (.) or a space. These are considered special characters in Linux and must
have single quotes around the name so that the directory path can be found. Example: //ImageServer/
DS Images/mnt/z.

Create and entry in the LMHOSTS file for the Deployment Server file store (other entries must be added
manually): Select this option if your network does not support NetBIOS name resolution for IP
addresses. Enter a Server name and IP address so that client computers can find the Deployment

Share where image files are stored.

Use NetWare login scripts to create drive mappings:

want login scripts to create the drive mappings.

Select this option if you use NetWare and you

Configuration Summary
This page lets you review all the options you selected throughout the New Configuration Wizard. If
you find a setting mis-entered or not what you want, click Back to re-select the option. When you
click Finish, the Create Boot Disk Wizard automatically displays for the next process to begin. See
Automation Partitions, Network and Automation Boot Disks (page 246) and Edit Configurations
(page 244).
If you are using Boot Disk Creator from within the PXE Configuration Utility, the Edit
Configuration page displays next. See Edit Configurations (page 244).

Edit Configurations
This is the main Boot Disk Creator page that displays when you start the utility. If you are using Boot
Disk Creator from within the PXE Configuration Utility, this page displays at the end of the New
Configuration Wizard.
This feature lets you modify configurations that have already been created. As you select files and
folders from the treeview in the left pane, the configuration information displays in the right pane.
The display color changes to help you know the type of configuration you selected to view, edit, or
delete. The colors displayed are:

Black:

Blue:

Green: The configuration you selected or created is based on the Linux pre-boot environment.

Red: The

You have not selected or created any configurations.

The configuration you selected or created is based on the DOS pre-boot environment.

configuration you selected or created is based on the Windows PE pre-boot


environment.

To change configuration settings, right-click on a configuration folder and select Edit Configuration,
and then click Back until you find the page for the options that you want to change. You can also
make text edits to files (selected from the treeview) in the right pane.
All other files within a configuration can be edited as needed. However, after you edit a
configuration, Boot Disk Creator rewrites certain files within the configuration so that drive
mappings and mount points are always updated. The following files are rewritten after editing
configurations:

DOS - mapdrv.bat, unmapdrv.bat

Altiris Deployment Solution Reference Guide

244

Chapter 12: Boot Disk Creator

New Configuration Wizard

Linux - mounts.local
WinPE - mapdrv.bat

See also: New Configuration Wizard (page 239), Install Pre-boot Operating System Files (page

249)

Additional Files
Boot Disk Creator lets you add additional files to folders that will either apply to a specific
configuration or to all configurations that are of the same type of pre-boot operating system.
However, any files you add to the global <OS> additional files folders will be written to the boot
image before the specific configuration files. If a file in the <OS> additional files folder is the same
name as a file in a specific configuration folder, it will be overwritten.
Example: if a file named 5684_Drivers resides in the DOS additional files folder, and the same file
5684_Drivers exists in a specific configuration folder, then when the files are written to a boot
image, the file in the configuration folder will overwrite the file in the DOS additional files folder.
This may cause unexpected results. If you edit text files in a <OS> additional files folder, yet the
specific configuration file is the one that is written to the boot image, the result will not be as you
expected.
Add files to all configuration
When you install a pre-boot operating system, a new folder will be added to the bottom of the
treeview on the main page of Boot Disk Creator. If you install pre-boot operating system files and
the <OS> additional files folders do not display, press F5 to refresh Boot Disk Creator. The folders
that display are as follows:

DOS additional files

Linux additional files

WinPE additional files

Boot Disk Creator will copy the files from the <OS> additional files folders to all corresponding
operating system configurations and will be added to the boot images. These folders are considered
global, since they can affect configurations of the same type.
Example: using the Windows Copy and Paste command, you can add tracert.exe to the WinPE
additional files folder. Each WinPE configuration you create will then add the files in the WinPE
additional files folder to the boot image.
Add files to a specific configuration
If you want to add files to a specific configuration only, and do not want to use the global feature of
the <OS> additional files folders, do the following:
1

Right-click a configuration in the treeview and select New > Folder. A new subfolder is created
in the treeview.

Enter a name for the folder so that you know they are added files.

To add files to the <OS> additional files folder, do one of the following methods:

Copy files from a network folder and Paste them into the configuration folder.

Right-click a configuration and select Add File. A browser dialog displays to navigate to the
file you want to add.

Right-click on a configuration and select File > Text file. A new empty text file is added to the
treeview. Enter a name for the file and write text as needed in the left pane.

Create PXE Boot Image Files (PXE)


This option is for Boot Disk Creator configurations created from within the PXE Configuration
Utility. Because PXE Servers download boot image files to client computers, after you select all the
properties for a New Configuration, Boot Disk Creator must know what type of image file to create.
Field Definitions

Altiris Deployment Solution Reference Guide

245

Chapter 12: Boot Disk Creator

Automation Partitions, Network and Automation Boot Disks

Automation PXE image: The automation agent for the type of pre-boot operating system configuration
you created will be added to the settings you selected throughout the New Configuration Wizard.
Network PXE image: The configuration you created will not contain an automation agent. When client

computers boot with this image file, they will map to a network server and be at a users prompt.

Force 2.88 MB PXE image:

Select this option to increase the size of PXE boot images.

PXE Boot Image Creation Complete


This page lets you know when the PXE boot image file is completed. Click Back to change the new
configuration settings for the boot menu option. When you click Finish, the boot menu option
displays in the Boot Menu tab.

Automation Partitions, Network and Automation Boot Disks


After you create a New Configuration, the Create Boot Disk (page 246) dialog automatically
displays. This process lets you select and create the method of booting a client computer to the
automation environment. If you install an automation partition on a client computers hard disk, then
deployment jobs can run automatically. However, you can create bootable media to manually boot
client computers to automation, and then run deployment jobs as needed. See New Configuration
Wizard (page 239).

Create Boot Disk


This dialog lets you create 3 different types of bootable media: an automation partition install
package, automation boot disks, or network boot disks. Each type of bootable media guides you
through a wizard to gather specific information required for the type of media you want to create.
The Create Boot Disk step numbers displayed at the top of the dialog page will vary depending on:

How the Create Boot Disk dialog was started

The type of media you selected to create

The pre-boot environment you specified in the configuration you created

However, based on your selections, Boot Disk Creator will display the appropriate dialog pages
when creating bootable media.
Example: If you right-click on a configuration in the treeview and select Install automation partition,
the number of dialog pages thereafter will be different than if you select the option, Create an
automation partition install package, from this page. Both options achieve the same result even though
the dialog steps may be different.
Select this option to close the Create Boot Disk dialog
without creating an automation boot disk, installer package, or network boot disk. You can select
any of these options from the Boot Disk Creator toolbar or from the File menu.

Choose this dialog and return to the editor:

Create an automation partition install package: Select this option to create an automation install
package that will install an embedded automation partition to any client computer on the network.
See Create an Automation Install Package (page 247).

Select this option to create automation boot disks so you can


manually boot a client computer to automation. See Create Automation Boot Disk (page 247).

Create an automation boot disk:

Create a network boot disk: Select this option to create network boot disks so you can manually boot

a client computer to a network server. See Create Network Boot Disk (page 248).

Altiris Deployment Solution Reference Guide

246

Chapter 12: Boot Disk Creator

Automation Partitions, Network and Automation Boot Disks

Create an Automation Install Package


This feature lets you create an automation installation setup package that will install an embedded
automation partition on a client computer when it executes. The installer package will run in a
production environment even though the New Configuration is based on the different pre-boot
operating system.
Example: You can create a DOS configuration but select to install the automation partition using an
installation setup package that runs in a Windows production environment.
Field Definitions
DOS bootable disk:

Select this option to install the automation partition using a DOS bootable disk.

Linux bootable disk: Select this option to install the automation partition using a Linux bootable disk.
Windows setup package: Select this option to install the automation partition using an installation
setup package that runs in a Windows production environment.

Select this option to install the automation partition using an


installation setup package that runs in a Windows CE .NET production environment.

Windows CE .NET setup package:

Create an embedded DOS automation partition (recommended):

embedded partition to a client computers hard disk.

Select this option to install an

Create a hidden DOS automation partition (for partitions greater than 50 MB): Select this option to install

a hidden automation partition.

Partition size in MB: The default partition size value will change, depending on the type of operating
system you selected. Example: If you are creating an automation partition for a Windows PE
configuration, then the partition size is 150-200 MB. However, the partition size for a DOS
configuration would range is only 5-50 MB.

Select this option to lock the users keyboard on the client computer when the
automation environment boots or an automation job runs.

Lock keyboard:

By default, installation packages are stored in the Deployment Share


bwpkgs folder. The name of the configuration you selected before starting the Create Boot Disk
process is the name of the setup package unless you define it otherwise. Click Browse to navigate to
the folder where you want the setup package stored.
Installer package file path:

Run silent install:

Select this option to install the automation partition without user input.

Install the Altiris Deployment Agent for Windows: Select this option to install the Deployment Agent
on client computers in the production environment after the automation partition is installed.

If you selected to install the Deployment Agent (above), click this button to set limited
properties for the Deployment Agent.

Advanced:

This is a progress page to display the automation installation


package process. The process does the following: Copying files to production area, Creating the FRM
files, Preparing install environment, Inserting into the installer package.
Creating automation partition installer:

After the automation partition installation package is created, the


Boot Disk Creation Complete page displays, and confirms where the installer package is located.

The setup package is located at:

Create Automation Boot Disk


This feature lets you create automation boot disks to manually boot a client computer to the
automation environment so deployment jobs can run. Automation boot disks give you greater
flexibility because you can physically go to any client computer on the network and boot to
automation, so long as the client computer can connect to the Deployment Server.

Altiris Deployment Solution Reference Guide

247

Chapter 12: Boot Disk Creator

Automation Partitions, Network and Automation Boot Disks

Field Definitions
Bootable ISO CD Image:

Select this option to create an ISO CD boot image.

ISO image file path: Enter the path to the folder where ISO images are stored. You must use third party
software to burn the ISO image to a CD.
Bootable disk: Select this option to create a boot disk that can be used at client computers to manually

boot to automation or manually install an automation partition. Click the drop-down arrow to select
bootable media from the list. All the drives listed will display the physical drive number instead of
the logical drive letter.

Rescan drives: If you attach a USB flash drive to the server, but it is not displayed in the Bootable
disk drop-down list, you can click this button to rescan the physical drives that are attached to the

server. A list of available drives will be updated in the drop-down list.

Show fixed drives: If you try to select a USB flash drive from the Bootable disk drop-down list, but
you cannot find it even after clicking Rescan drives, it is possible that the flash drive you are using
displays in Windows as Fixed instead of Removable. Select this option to display all drives attached
to the server.

Create Network Boot Disk


This feature lets you create a network boot disk that you can use at any client computer on the
network. The properties you defined when creating the New Configuration will map a drive to a
specified server when a client computer uses a network boot disk. You will then have access to the
network servers system to execute and manipulate files manually.
Field Definitions
Bootable ISO CD Image:

Select this option to create an ISO CD boot image.

ISO image file path: Enter the path to the folder where ISO images are stored. You must use third party
software to burn the ISO image to a CD.
Bootable disk: Select this option to create a boot disk that can be used at client computers to manually

boot to a network server. Click the drop-down arrow to select bootable media from the list. All the
drives listed will display the physical drive number instead of the logical drive letter.

Rescan drives: If you attach a USB flash drive to the server, but it is not displayed in the Bootable
disk drop-down list, you can click this button to re-scan the physical drives that are attached to the

server. A list of available drives will be updated in the drop-down list.

Show fixed drives: If you try to select a USB flash drive from the Bootable disk drop-down list, but
you cannot find it even after clicking Rescan drives, it is possible that the flash drive you are using
displays in Windows as Fixed instead of Removable. Select this option to display all drives attached
to the server.

Remove Automation Partition


This feature lets you remove an automation partition on a client computers hard disk. You can
create bootable CDs, flash drives, and floppy disks to use manually at the client computers, or you
can create a Windows uninstall package that can be distributed to a client computer through a
deployment job. You could also create a network boot disk, connect to a specific server where the
Windows uninstall package is stored, and then run the executable from the client computer.
Field Definitions
DOS bootable disk:

Select this option to remove an automation partition using a DOS bootable disk.

Linux bootable disk: Select this option to remove an automation partition using a Linux bootable disk.
Windows setup package:

Select this option to remove an automation partition using an installation


setup package that runs in a Windows production environment.

Altiris Deployment Solution Reference Guide

248

Chapter 12: Boot Disk Creator

Import Configuration Files

Windows CE .NET setup package:

Select this option to remove an automation partition using an


installation setup package that runs in a Windows CE .NET production environment.

Bootable ISO CD Image:

automation partition.

Select this option to create an ISO CD boot image that will remove an

ISO image file path: Enter the path to the folder where ISO images are stored. You must use third party
software to burn the ISO image to a CD.
Bootable disk: Select this option to create a boot disk that removes an automation partition from a
client computer. Click the drop-down arrow to select bootable media from the list. All the drives
listed will display the physical drive number instead of the logical drive letter.
Rescan drives: If you attach a USB flash drive to the server, but it is not displayed in the Bootable
disk drop-down list, you can click this button to re-scan the physical drives that are attached to the

server. A list of available drives will be updated in the drop-down list.

Show fixed drives: If you try to select a USB flash drive from the Bootable disk drop-down list, but
you cannot find it even after clicking Rescan drives, it is possible that the flash drive you are using
displays in Windows as Fixed instead of Removable. Select this option to display all drives attached
to the server.

Import Configuration Files


The configuration format has changed from all previous versions of Boot Disk Creator. This is
because of increased support and functionality that Boot Disk Creator now provides. However, you
can save previously created configurations by using the Import Previous Version Configuration
Files dialog to convert the configurations format to this release. Configuration files that are
successfully imported can be used to support automation and imaging on client computers.
Note: There may be some instances when older configuration files cannot be converted to the new
file format. Files that do not import successfully will have to be recreated configurations using the
New Configuration Wizard in this version of Boot Disk Creator.

Field Definitions
Directory:
Browse:

Enter a path to where the configuration files that you want to convert are located.

Click to navigate to the directory path where configuration files are located.

Config File Name: This is the name of the old configuration files that you have selected to convert and
import into this release of Boot Disk Creator.
Description:

This is the description for the old configuration files.

To import configuration files


1

Open the Boot Disk Creator Utility.

Click File > Import.

Install Pre-boot Operating System Files


Boot Disk Creator requires that you install the pre-boot operating system files for at least one preboot environment before you can create new configurations. Boot Disk Creator uses these files when
creating configurations and boot images. You can install all supported pre-boot operating system
files at the same time, or you can select to install only those pre-boot environments you want to use.
You can install FreeDOS and MS-DOS, but you must select which DOS version you want to run
since you cannot run both versions at the same time.
Example: you can install the DOS and Windows PE pre-boot operating system files to start creating
configurations to support your infrastructure, which currently does not have a need for Linux boot
images. After working with Deployment Server and Boot Disk Creator, you decide you want to

Altiris Deployment Solution Reference Guide

249

Chapter 12: Boot Disk Creator

Install Pre-boot Operating System Files

create Linux configurations and Linux boot images. You can open the Install Pre-boot Operating
System Files dialog at any time to install the Linux system files, or of the other pre-boot operating
system files.
When you install the pre-boot operating system files for DOS (page 250), Linux (page 251), or
Windows PE (page 251), a check mark next to the operating system name indicates that the files
have been successfully installed. The operating system version number displays (except for MSDOS), and the Install button changes to display Update.
If you acquire a newer version of DOS, Linux or Windows PE, click Update to install the new files.
However, any existing operating system files will be deleted before the newer files are installed.
Example: If you installed Windows PE, and Altiris supports a newer version that becomes available,
click Update to install the new files. All existing Windows PE files will be deleted from the hard disk
before the new files are installed. If you experience any problems with the new version of Windows
PE, you will have to install the older version to restore Boot Disk Creator functionality for Windows
PE.
To install pre-boot operating system files

Click the Install button next to the pre-boot operating system that you want to install.

DOS
You can install FreeDOS (page 250), MS-DOS (page 250) or both. However, you can only run one
version of DOS at a time. If both versions of DOS are installed, click either FreeDOS or MS-DOS to
select the version you want to run as the default for creating configurations.

FreeDOS
Deployment Solution provides FreeDOS in a file named BDCgpl.frm. The BDCgpl.frm file can be
downloaded from the Altiris Solution Center Web site and then saved to any location on the network.
When newer versions of FreeDOS become available, an updated .frm file will be available online
through Deployment Solution Hot Fixes or Service Pack releases.
Note: FreeDOS may not support newer motherboard chip-sets.

MS-DOS
Using an original Microsoft Windows 95/98 installation CD, copy the appropriate files to a system
formatted floppy disk, a folder that can be accessed from Boot Disk Creator, or use the CD directly.
Use Microsoft Windows 95/98 installation CD:

Windows 95/98 installation CD.

Select to install MS-DOS from an original Microsoft

Floppy Disk: Select to format a disk using the Format a: /s command. Copy the required files listed
below from an original Microsoft Windows 95/98 installation CD to the floppy disk. Boot disk
creator only installs DOS files from the A drive. If you select B-Floppy Drive from the drop-down list,
Boot Disk Creator will still try to read data from the A-Floppy Drive.
Folder: Select to copy the required files to a folder that can be access from within Boot Disk Creator.

Boot Disk Creator requires the following MS-DOS files.


MS-DOS files

Required

Optional

HIMEM.SYS

EDIT.COM

EMM386.EXE

MEM.EXE

SMARTDRV.EXE

ATTRIB.EXE

SYS.COM

MODE.COM

Altiris Deployment Solution Reference Guide

250

Chapter 12: Boot Disk Creator

Install Pre-boot Operating System Files

MS-DOS files

Required

Optional

XCOPY32.MOD

FORMAT.COM
FDISK.EXE

Important: The SMARTDRV.EXE file is required for all computers running a scripted install in

Windows 2003\XP.

Linux
Deployment Solution provides Linux RedHat Fedora in a file named BDCgpl.frm. The BDCgpl.frm
file can be downloaded from the Altiris Solution Center Web site and then saved to any location on
the network. When newer versions of Linux become available, an updated .frm file will be available
online through Deployment Solution Hot Fixes or Service Pack releases.

Windows PE
Altiris supports Windows PE 2005 as a pre-boot environment for Boot Disk Creator. When you
install Windows PE, you will be asked to supply 2 CDs: Windows PE 2005 and Windows Server
2003 SP1.
In most instances, the Welcome to Microsoft(R) Windows(R) Server 2003 page displays after
inserting the Windows Server 2003 CD. Click Exit to avoid installing the full version of Windows
Server.
There are two dialog pages to complete the Windows PE installation. You will first be asked to
provide the Windows PE CD, followed by the Windows CD. The text on the page lists the operating
system CD you need to enter for each of these pages.
Example: On the Windows PE CD page, the text displays Windows PE 2005 (Windows Server 2003while the Windows CD page displays Windows Server 2003-SP1 (Windows PE 2005). The first
operating system listed on each page is the CD you want to use.
SP1),

Note: To install a Windows PE automation partition, DOS also needs to be installedeither

FreeDOS or MS-DOS.

Altiris Deployment Solution Reference Guide

251

Chapter 13:

PXE Server
Pre-boot Execution Environment (PXE) is an open industry standard which enables computers to
boot remotely using a network card.
PXE uses standard network protocols to establish a communication channel between a computer and
a PXE server during the boot process. Using this channel, a PXE server sends an execution
environment to the computer so that work can be performed in a pre-boot state.
In Deployment Solution, this pre-boot state is called the automation environment, and DOS, Linux,
and Windows PE are currently supported as pre-boot operating systems. An overview of the
automation boot methods and environments is contained in Automation Pre-boot Environment on
page 228.
An advanced, tightly integrated PXE environment is provided with DS. DS leverages PXE to
provide the following advantages:

When a managed device needs to boot into automation, DS restarts the computer and notifies the
PXE server. PXE server then boots the computer into the automation environment indicated in
the DS job automatically.

PXE can perform an initial deployment of a new system by checking to see if a computer exists
in DS.

All PXE configuration is done using the PXE Configuration Utility from the DS console,
enabling you to remotely configure all PXE servers in your network.

PXE in Deployment Solution


PXE is used in DS to perform two tasks:

Boot managed computers into the automation environment

Perform initial deployment of new managed computers

How you implement PXE is partially dependent on what you plan to do with it. Many organizations
use PXE only on a subnet in a receiving department to deploy corporate images and initial
configuration of new computers. After this computer is assigned to a user, PXE is not used in the
normal production environment.
This limits the extent of the PXE environment, but prevents you from accessing the automation
environment to capture images and perform other automation-only tasks.
Other companies which often use automation select PXE because it leaves no footprint on the
managed computer, and has several other advantages such as image multicasting and tight DS
integration.
Regardless of how broadly you implement PXE, DS provides tools and services to simplify
management of PXE in your environment. This section contains the following topics providing an
overview of PXE in DS:

PXE Services and Architecture

How PXE Works

Altiris Deployment Solution Reference Guide

252

Chapter 13: PXE Server

PXE in Deployment Solution

PXE Services and Architecture


Deployment Solution 6.5 introduces a new tiered PXE architecture which enables you to provide
global settings and boot options shared across all PXE servers, then override configuration and
expand boot options on a local level.
Now boot options and PXE settings can be applied to a shared configuration. This shared
configuration is inherited by all PXE servers in your environment. Each PXE server still has its own
specific configuration, so you can override settings and add additional boot options as needed.
New services have been provided to replicate settings and data automatically, making it unnecessary
for you to individually configure each PXE server.
The following table contains an overview of the PXE services:
Service

Description

PXE Manager

Provides all boot options and configuration settings for


each PXE server in your environment.

Interfaces with the PXE Config Utility to replicate data and


apply PXE configuration.

Manages all communication between DS and your PXE


servers.

The PXE Manager Service is installed on your DS server


regardless whether or not you have also installed a PXE server.

Interfaces with PXE Manager to receive data and


configuration.

Configures, starts, and stops the additional PXE services on


the PXE server.

PXE Server

Provides the PXE listener and proxy DHCP to respond to


PXE requests and send the location of bootstrap files.

MTFTP

Sends bootstrap files to managed computers using TFTP.

PXE Config Helper

The PXE Manager service interacts with DS, PXE Helper service, and the PXE config utility to
perform centralized PXE management:

Altiris Deployment Solution Reference Guide

253

Chapter 13: PXE Server

PXE in Deployment Solution

On each individual PXE server, the PXE Server service and the MTFTP service are installed to
perform the work of a PXE server. These services are configured, started and stopped by the PXE
Config Helper service. Clients connect directly to these services during the PXE boot process:

Boot Images vs. RapiDeploy Images


When using PXE, two types of images are discussed and used in DS:
Boot Images

Contains the files necessary to PXE boot a managed computer


into an automation environment. Boot images correspond to options on the PXE menu. The PXE menu item and its corresponding image are referred to as a Boot option.
These images are never captured or modified by hand, and are
created using the Boot Disk Creator utility.

RapiDeploy Images

An image containing a snapshot of a computer, used to deploy a


standard environment to new computers, save the current state of
a computer for easy restoration, and several other management
tasks.
These are often simply referred to as images, and are captured
from your reference and other computers, and can be deployed
directly to managed computers.

In a PXE environment, a managed computer can receive a boot image from a PXE server multicast,
load the image, then receive an image through a multicast from RapiDeploy.
This can be confusing, because both PXE server and RapiDeploy send images, and both can use
multicast technology. The difference is the type of image they deploy.
A boot image contains only the files necessary to load automation, and is largely transparent. A
RapiDeploy image contains what is normally considered an image, which is a snapshot of a disk
or partition, usually containing an OS and standard applications.

How PXE Works


Before a computer can boot over a network, it needs two things: an IP address to communicate, and
the location of a PXE server to contact for boot instructions.
The following sections outline the PXE boot process:

Part 1: DHCP Request and PXE Discovery

Part 2: PXE Bootstrap

Altiris Deployment Solution Reference Guide

254

Chapter 13: PXE Server

PXE in Deployment Solution

Part 1: DHCP Request and PXE Discovery


Request and Receive an IP Address
Initially, the boot agent directs the execution of normal DHCP operations by broadcasting a
DHCPDISCOVER packet (255.255.255.255) to port 67 on its local physical subnet to discover a
DHCP server.
Any available DHCP servers respond with a broadcast DHCPOFFER packet indicating their server
IP.
When the client has chosen a target DHCP server, it broadcasts a DHCPREQUEST packet that
includes its MAC address and the IP address of the selected DHCP server. The DHCPREQUEST
also contains option 60 to identify the client as a PXE client.
PXE Option 60
DHCP allows clients to receive options from the DHCP server indicating various services that are
available on the network. A number of standard and custom options are available that can convey a
vast amount of information to DHCP clients. Option 60 deals specifically with PXE related services.
Both PXE clients and servers use option 60 to convey specific information about the PXE services
they need or are providing.
Contacting the PXE Server
All DHCP servers examine the DHCPREQUEST packet. If the request is intended for a different
server, the IP address they offered is reclaimed. The DHCP server providing the accepted offer
supplies a DHCPACK packet to the client to acknowledge the clients receipt of its IP.
During this process, the Altiris PXE server monitors the wire for DHCPREQUEST packets with an
option 60 (PXE client).
When a packet is recognized, the client MAC address is used to find any pending automation work
in DS, using the following process:
When a PXE server starts, it receives a list of all managed computers, their MAC addresses, and the
boot menu each managed computer should receive if that PXE server is contacted.
This list is updated at a regular interval, as well as each time the PXE configuration Utility is loaded.
When a client contacts this PXE server, the client MAC address is checked against this list. If found,
the associated boot menu is sent. When there is no automation work, the local boot option is set as
default with a zero second timeout, causing the managed computer to boot locally. Clients that are
not found in the MAC address table can be assigned initial deployment.
If work is found, the correct boot option is selected, and the PXE bootstrap is performed by
responding with its address using a DHCPACK with option 60.
At this point, the client has received a DHCPACK containing an IP address, and a DHCPACK with
option 60 containing a PXE server. If the PXE server is located on the same server as DHCP, both
are contained in the same DHCPACK packet.

Part 2: PXE Bootstrap


Now the client is ready to contact the PXE server for boot files. After this request, clients are
provided a boot menu containing all of the boot options the PXE server can provide. Most of the
time, the correct boot option has already been selected by DS, so this transparent to the client.
After the selection is made, the client requests the necessary boot files using MTFTP, depending on
the automation OS being loaded. For example, when loading DOS, the client requests two files: a .0
and a .1 file.
The .0 file functions as a bootstrap loader. It creates a RAM disk and manipulates the BIOS interrupt
vectors, interrupt structures and hardware information tables to make the RAM disk function exactly
like a typical floppy disk. This file then copies the .1 file byte by byte into the newly created RAM
disk.

Altiris Deployment Solution Reference Guide

255

Chapter 13: PXE Server

Planning and Installing PXE

The .1 file is an image of a boot disk floppy with modifications to the autoexec.bat and additional
files which ultimately provide the automation environment on the managed computer.
The following diagrams contain a basic outline of this process:

Planning and Installing PXE


This section contains an overview of the PXE deployment process, in the following sections:

Enabling PXE on Managed Computers

Installing and Configuring DHCP

Determining How Many PXE Servers You Need

Installing PXE Servers

Enabling PXE on Managed Computers


Each computer you plan to manage using PXE must have PXE boot enabled (sometimes called
network or NIC) and set to the correct sequence in the BIOS. It is also a good idea to apply the latest
BIOS updates, especially if your network card is integrated on the motherboard.
DS also supports Wake on Lan to power on managed computers remotely. If this is enabled, a Wake
on Lan signal is sent to the managed computer if the device is powered off (disconnected from DS)
when a job is scheduled to start.

Altiris Deployment Solution Reference Guide

256

Chapter 13: PXE Server

Planning and Installing PXE

Installing and Configuring DHCP


DHCP is an integral part of the PXE process, and must be installed and configured in order to use
PXE. A DHCP server is not provided with Deployment Solution, you must obtain, install, and
configure this component separately.
After DHCP is set up and your PXE servers are installed, you need to configure how your PXE
servers interact with the DHCP server. See PXE Server Tab on page 274.

Determining How Many PXE Servers You Need


Number of Client Connections
PXE servers do not typically require a lot of resources. By using multicast, a single PXE server can
deploy a boot image to up to 100 computers at a time, and not consume any more resources than it
would deploying a single image. Multiple multicast sessions can be executed simultaneously.
Usually a single PXE server in a specific location is enough if you use multicast to boot computers
and spread out your jobs to be in line with the capabilities of your server. Additional PXE servers
can easily be added if necessary.

Network Speed
Since the majority of the resources on a PXE server are used transferring files over the wire, the
faster the network, the more work a single PXE server can do. A single PXE server on a gigabit
network can remotely boot a larger number of computers over a period of time than even multiple
servers on a slower network.
This becomes especially important when using certain automation environments, such as Windows
PE, that can be over 100 MB and do not provide support for multicast booting. Boot files must be
delivered to each of these managed computers individually, causing a large amount of network
traffic and greatly increased boot times.
This is less of an issue when using boot images with a small footprint, such as DOS, which support
multicast booting.

Physical Layout of your Network


A PXE deployment is often set up according to the physical layout of your network. If you have three
offices in different locations, it might make sense to install a PXE server at each location to reduce
traffic and resolve routing issues (see PXE Request Routing on page 257).
In these configurations, the deployment share can be mirrored to a local server, and images are
usually taken from and restored to local file servers. See Redirection on page 259 for an example
of this type of configuration.

PXE Request Routing


PXE clients use broadcast packets to find DHCP and PXE services on a network, and multicast
packets (MTFTP) to transfer files. These packet types can present challenges when planning a PXE
deployment because most default router configurations do not forward broadcast and multicast
traffic.
To resolve this, either your routers need to be configured to forward these broadcast and multicast
packets to the correct server (or servers), or you need to install a PXE server on each subnet.
Routers generally forward broadcast traffic to specific computers. The source subnet experiences the
broadcast, but any forwarded broadcast traffic targets specific computers.
Enabling a router to support DHCP is common. If both PXE and DHCP services are located on the
same computer, and DHCP packet forwarding is enabled, you shouldnt have any problem
transferring broadcast packets.

Altiris Deployment Solution Reference Guide

257

Chapter 13: PXE Server

Configuring PXE Settings

If these services are located on different computers, additional configuration might be required.
If you are going to forward packets, make sure your router configuration allows DHCP traffic to
access the proper ports and IP addresses for both DHCP and PXE servers.
Once the broadcast issues are resolved, the routing of multicast traffic must be considered.
Multicasting leverages significant efficiencies in transferring files but also introduces challenges
similar to broadcast packet forwarding. Like the broadcasting solution, routers can be configured to
support multicast traffic between PXE Clients and PXE Servers.
Please consult the documentation provided by your router vendor for additional information on
packet forwarding.

Installing PXE Servers


After you have determined the PXE needs of your network, you must to determine where to install
these PXE servers.
A PXE server can be installed on your DS server, on your DHCP server, on another server in your
network (such as a file server), or as a standalone server. You can also use a combination of these
(for example, a PXE server on your DS server and your DHCP server).
The actual installation process is straightforward. You can install a PXE server at the same time as
you install DS, or you can install one later by running the installation program again from your DS
server and selecting the add additional components option.
After these servers are installed an running, they are configured using the PXE Configuration Utility.
See Configuring PXE Settings on page 258.

Configuring PXE Settings


All PXE configuration is done using the PXE Configuration Utility. The PXE config utility is used
to create and modify two things:

Shared and local configuration settings. These settings include timeout values, replication and
logging options, and so on.

Boot options. Each boot option corresponds to a specific configuration which includes an
operating system, network and other drivers, utilities, mapped drives, and so on.

This section contains a brief overview of selected PXE configuration and boot options. For complete
details, see PXE Configuration Utility on page 261.

PXE Settings
Shared vs. Local
DS provides a PXE settings hierarchy enabling you to provide shared and local PXE configuration
values. All PXE servers inherit the shared values unless they are overridden on the local server.

Session Timeout
The PXE configuration utility connects the PXE Manager service on DS. To make sure your changes
are not overwritten by another instance of the PXE Configuration Utility, only one instance of PXE
config is allowed to connect to PXE manager at any given time.
If you attempt to launch PXE Configuration when another instance is running, you receive an error.
To prevent you from being completely locked out for extended periods (for example, an instance is
inadvertently left open on another computer), a timeout has been added which terminates a
connection after 30 minutes of inactivity after someone else attempts to connect.

Altiris Deployment Solution Reference Guide

258

Chapter 13: PXE Server

Configuring PXE Settings

This timeout applies only if someone else is attempting to launch PXE Configuration. If no other
connections are attempted, the timeout is never enabled and your session remains active.

DHCP Server Options


This must to be configured according to the DHCP implementation in your environment. See PXE
Server Tab on page 274 for a complete explanation of available DHCP options.

Boot Integrity Services


PXE is potentially vulnerable to hackers, especially in security-conscious business and government
settings not willing to risk network boot ups unless safeguards are in place. For example, it is
important ensure that the boot image comes from a trusted source and has not been tampered with
in transit. You can also designate and enforce which boot images can be installed on selected groups
of platforms. Boot Integrity Services (BIS) addresses these security needs.
BIS enhances the network boot environment by providing mechanisms to validate the source and
integrity programs and data downloaded over the network prior to the time an operating system is
installed. Using BIS firmware built into the client computer, BIS can validate (before executing a
boot image) that the image came from a trusted source and was not tampered with en route.
Deployment Server supports the BIS technology. However, the BIS support from Altiris is only
applicable when the computers being managed also supports BIS. Even if BIS is configured from
the Deployment Server console, BIS will not work unless the physical computer supports it. At the
present time, there are very few computers that support BIS.

Boot Options
Boot options are the boot configurations provided to a client by a PXE server. Each boot option has
a corresponding automation operating system, network drivers, and other settings.

Shared vs. Local


DS provides a PXE boot option hierarchy enabling you to provide shared and local PXE boot
options. Shared boot configurations are available on all PXE servers, while local boot options are
available on a specific PXE server.

Redirection
This lets you redirect a global PXE menu option to use a local PXE menu option on a specific PXE
server.
Redirection settings are not available on the shared configuration, they are always specific to an
individual PXE server. This is due to the role redirection plays in your PXE environment.
Consider the following example:
You manage computers in three locations: Two offices in Ontario, and one office in Alberta. To limit
transfer between each site, each office has a local PXE server, and a file server with a mirror of the
deployment share. This enables clients at each location to contact the local PXE server to boot, then
use the local deployment mirror to access the network tools and to store images.
You need to create a job to capture an image of each managed computer on Friday evening, once a
month. To create this job, you add an imaging task, select a PXE boot option, then set the schedule.
Simple, right?
Hold on. If you select the same PXE boot option for each office, you are going to have problems.
The Alberta office uses a mirror of the deployment share on alb1\eXpress, and stores captured
images on alb1\images. The two Ontario offices use the ont1 and ont2 servers respectively.
You could go ahead and create three global configurations and three different jobs, but that is
confusing and could potentially cause problems if the wrong selection is made. If you took this route,
on each PXE server, two of the three global configurations could potentially cause problems (they

Altiris Deployment Solution Reference Guide

259

Chapter 13: PXE Server

Configuring PXE Settings

are mapped to drives in remote offices). Since you enjoy avoiding problems, what you really need
is a way to select a single global configuration for a job, then update it based on the location of the
PXE server.
This is exactly what redirection does. You create a global configuration named, for example,
Imaging Environment. Then, on each PXE server, you create a local configuration for each office
with the correct server mappings.
The Imaging Environment global option is then redirected to the local option. Now the imaging
job can be applied to all computers at once, simplifying the process and reducing the chance of
errors.

Altiris Deployment Solution Reference Guide

260

Chapter 14:

PXE Configuration Utility


Altiris PXE Configuration Utility integrates with Altiris Deployment Solution and lets you manage
all PXE Servers across the network. PXE Configuration has been completely rewritten to give you
more capability in working with Deployment Server, which allows administrators greater flexibility
when performing the following tasks:

Creating boot menu options

Installing BIS Certificates

Creating boot disks, and network PXE images

Assigning pre-boot environments to tasks within deployment jobs

Setting properties to customize specific PXE Server

Setting the boot menu option order for client computers

PXE Server has also been added to Role Based Security to ensure that only those users authorized
can make changes to boot menu options.
If you select Deployment Solution Simple Install and Install PXE Server, they will both install to the
same server. If you select Custom Install and Install PXE Server, you can choose to install them to
separate servers. However, regardless of the PXE install options you select, PXE Manager will
always install on the Deployment Server. See the Deployment Solution Reference Guide.
PXE Manager
PXE Manager is a service that synchronizes Deployment Server and all PXE Servers installed and
configured across the network. It keeps track of all PXE Server boot menu options, and whether they
are Shared or Local. PXE Manager also gathers data from all PXE Servers and stores the information
in the PXE Manager.ini file. Whether you are in Use Shared properties or select a server to Customize
PXE Server (Shared Configuration), the changes you make to the properties settings will be saved to
the PXE Manager.ini file when you click the Save button. Then, when you close the PXE
Configuration Utility, PXE Manager creates and distributes the appropriate PXE.ini file for each
PXE Server on the network. See PXE Manager (page 278).
Shared or Local boot menu options
When you start the PXE Configuration Utility, you can select which properties you want to set. The
Use Shared properties option lets you create Shared boot menu options that will be used by all PXE
Servers on the network. When you select a specific PXE Server from the File menu, you can select
the Customize PXE Server (Shared Configuration) option that lets you change any of the shared
properties for that specific server. By default, PXE Configuration will always start in the Use Shared
properties mode. See Boot Menu Tab (page 262).
The boot menu options you create will display as a menu list on client computers when a PXE boot
operation is performed. You can set the order of the boot menu options and select which menu option
you want as the default. Previous users of Altiris PXE Server will notice that Initial Deployment and
ManagedPC are no longer boot menu options. You can still perform an Initial Deployment, but now
you can select DOS, Linux, or Microsoft Windows Preinstallation Environment (Windows PE) as
the pre-boot automation environment. By default, the pre-boot operating system selected at install
time will be set for Initial Deployment. See DS Tab (page 275).

Altiris Deployment Solution Reference Guide

261

Chapter 14: PXE Configuration Utility

Boot Menu Tab

Boot Disk Creator and PXE Configuration


Boot Disk Creator is now integrated with the PXE Configuration Utility, so that you can keep track
of the boot menu options you create, edit, and delete. When you select a boot menu option to edit or
delete using the Boot Disk Creator method, the Summary page displays the MenuOption<number>, so
you always know which boot menu option you are working with. See Boot Menu Tab (page 262)
and Edit Shared Menu Option (page 265).
PXE Server provides 3 different methods of creating boot menu options: the New Configuration
Boot Disk Creator, importing Direct from floppy, and User supplied, which is for more
advanced users. For each boot menu option created, there is a boot image stored on the PXE Server.
A boot image consists of a file or set of files. When client computers perform a PXE boot, a menu
list displays for users to select a boot menu option. PXE Server downloads the boot image that
corresponds with the boot menu option that the user selects. See New Shared Menu Option (page
264).

Wizard from

Automation Tasks
Only Shared boot menu options can be assigned to a task in a deployment job. The tasks the can run
in automation are:

Run script

Create Disk Image

Distribute Disk Image

Scripted OS Install

Backup Registry

Restore Registry.

When a client computer performs a PXE boot, the Deployment Agent verifies if there is work to
complete. If so, the client computer boots to automation and performs the deployment jobs that have
been assigned. If there are no deployment jobs for the client computer, the Local Boot menu option
is automatically selected.
Example: If a deployment job contains the task Create Disk Image, and the Automation - PXE or
Bootworks environment (DOS/Windows PE/Linux) field is assigned to DOS - Broadcom, then when
client computer executes the task, it will use DOS - Broadband as the automation environment.

the

Additional tasks within the same job may be assigned a different boot menu option, yet each task
will execute in the automation environment you want. See the Deployment Solution Reference
Guide.
See also: Boot Menu Tab (page 262), PXE Server Tab (page 274), DS Tab (page 275), MAC Filter

Tab (page 276), Multicast Tab (page 277), BIS Tab (page 279), Data Logs Tab (page 279), Remote
PXE Installation (page 280).
To open PXE Configuration

Option 1:

From the Deployment Console, click PXE Configuration on the toolbar. You can also click Tools
> PXE Configuration.

Option 2:
1

Click Start > Programs > Altiris > PXE Services > PXE Configuration Utility.

Click each tab to set the category in the PXE Server properties.

Boot Menu Tab


This lets you create, edit, and delete boot menu options, set the boot menu order, define the prompt
for users, append the server name to the prompt, and set the users time-out response when the boot
menu list displays on client computers. PXE boot menu options can be either local or shared,
depending on whether you select Use Shared properties or Customize PXE Server.

Altiris Deployment Solution Reference Guide

262

Chapter 14: PXE Configuration Utility

Boot Menu Tab

When you manage all PXE Servers (Shared) across the network, the page displays Boot Menu Option
at the top of the page and above the list of configurations.
When you select a specific server (Local) from the File menu, the page displays Boot Menu Option for
PXE Server: (name of Server). This will help you identify which mode you are working in.

for PXE Server: (Shared Configuration)

By default, PXE Configuration Utility opens to the last saved action, which could be either Shared
Configuration or Custom PXE Server mode. The boot menu options listed are for all PXE Servers, so
the Scope will always be Shared. The OS field indicates the type of pre-boot operating system files
used to create the boot menu option. If you select a PXE Server from the File menu, the window
displays the boot menu option for the PXE Server you selected. The Scope field will display both
Shared and any new boot menu options you create will display Local. The OS field is the same as in
the Shared mode.
View Area
When you are in Shared Configuration mode, only configurations you create for all PXE Servers is
displayed in the view area. When you are in Customize PXE Server <server name> mode, both Shared
and Local configurations display. You cannot create a configuration named the same as any other
configuration in the view area, regardless of the mode you are in.
Example: if you are in Customize PXE Server <server name> mode, you can view both Shared and
Local configuration. You can create a Local configuration named DOS Clients since there are no
others with the same name. Then, you change to Shared Configuration mode and create a
configuration named DOS Clients because the Local configuration of the same name does not
display in the view area. When you change back to Customize PXE Server <server name> mode, both
DOS Clients configurations display in the view area. When client computers perform a PXE boot,
both configurations display and users will not know which boot menu option to select. See Redirect
Shared Boot Menu Option (page 265).
Boot Menu Options for PXE Server: <Shared Configuration>
Name: This is the name of the PXE item that will display on client computers after a PXE boot
operation is performed.
Scope: Shared indicates that the configuration is available on multiple PXE Servers in an
environment where they are all serviced by a single Deployment Server. Local indicates the
configuration was created for a specific PXE Server.
OS:

The operating system that the configuration will use to boot on client computers.

Up and Down: Select to order boot options. The top boot option is the default that runs automatically
if no other option is selected from the PXE Server menu. Altiris recommends that the Boot Local
menu option remain at the top of the boot menu list.
New: Click to open a dialog box to add a new boot menu option. See New Shared Menu Option (page

264).

Edit:

Click to modify properties for boot menu options. See Edit Shared Menu Option (page 265).

Delete: Select

a boot menu option from the list and click Delete. You are not allowed to delete boot
menu options if they are assigned to a task within a deployment job. Go to the Deployment Console,
open the appropriate deployment job, and delete the task or change the Automation - PXE or
Bootworks environment (DOS/Windows PE/Linux) field before you try to delete the boot menu option.

Boot Menu Properties


This is selected when you are setting the properties for a Shared
Configuration. You cannot change this selection on the other pages if you are setting properties for
the Shared Configuration.

Use Shared properties:

Customize PXE Server (Shared Configuration): This option is available when you select a specific
server from the File menu. You can keep the settings on the page or customize the properties for the

PXE Server you selected.


Prompt: This

is the user prompt for the PXE boot menu list when it displays on client computers.
You can change the text message but not the <F8> command, as it is still required to perform a PXE
boot option.

Altiris Deployment Solution Reference Guide

263

Chapter 14: PXE Configuration Utility

Boot Menu Tab

Append server name: Select this option to have the PXE Server name listed following the prompt on

client computers when the boot menu list displays. This helps users know which PXE Server is
servicing their client computer.

Time-out: This is the length of time the prompt is displayed before the boot process starts. If the user
does not press the <F8> key within the time-out period, the default boot option runs.
Save: Click to save all changes you made to the PXE Manager.ini file. When you close the PXE
Configuration Utility, PXE Manager creates and sends PXE.ini files to each PXE Server on the
network.

New Shared Menu Option


The PXE Configuration Utility lets you create up to 23 boot menu options that can be selected from
client computers. When a PXE-enabled client computer makes a request to the PXE Server, the PXE
Server will download a boot menu list for users to select a boot option.
This dialog page also integrates with Boot Disk Creator as it lets you create new automation
configurations from within the PXE Configuration Utility. However, all the configurations you
create from this dialog, are meant for PXE Servers and the client computers that use PXE as their
primary boot option.
Menu Item Properties
This is the name of the PXE configuration that will display as a boot item when the PXE
menu downloads to client computers after a PXE boot operation is performed.

Name:

Allow as default PXE boot option: Select this option to move the configuration you are creating to the

top of the boot menu, so that it becomes the default boot option on client computers. It you do not
select this option, the Up button is active to move the configuration up the menu list but becomes
inactive if you try to move the configuration to the default boot position.

This field can help you identify which PXE item you are configuring. PXE
configurations are stored in the default directory of C:\Program Files\Altiris\eXpress\Deployment
Server\PXE\Images\MenuOption<number>. The MenuOption number increments each time you
create a new configuration.
Location on PXE Server:

Operating System: Select the type of pre-boot operating system for the configuration you are
creating. If an operating system has an asterick next to it, then the pre-boot operating system files
must be installed before Boot Disk Creator starts the New Configuration Wizard. See Install Preboot Operating System Files (page 266).

Image creation method


Boot Disk Creator: This lets you start the New Configuration Wizard from Boot Disk Creator. Any
configurations you create or edit using this method will be for PXE boot menu items only. New
Configuration Wizard (page 268).
Direct from floppy: Select this option if you want the PXE Server to read a configuration file from a
floppy. See Import Boot Menu Options (page 265).
User supplied: This is for advanced users. If you select this option, you must select Other in the
Operating System area. The Location field will display the path where the new configuration is
stored. The folder MenuOption<Number> is created as a subfolder of MasterImages, but no
configuration files are stored there until advanced users add the configuration files manually. See
Import Boot Menu Options (page 265).
Create Boot Image: You must enter a descriptive name for the PXE configuration in the Name field
before this button becomes active. The New Configuration Wizard from Boot Disk Creator starts
unless you have not installed the pre-boot operating system files for the type of configuration you
want to create. The Install Pre-boot Operating System Files dialog will display before the New
Configuration Wizard starts if you need to install the pre-boot operating system files. See Install Preboot Operating System Files (page 266) and New Configuration Wizard (page 268).

Altiris Deployment Solution Reference Guide

264

Chapter 14: PXE Configuration Utility

Boot Menu Tab

Edit Shared Menu Option


When you are in Shared Configuration mode, only Shared configuration display in the view area of
on the Boot Menu tab. The Edit button is displayed when you select any of the Shared boot menu
options. However, if you are in Customize PXE Server: <server name> mode the Edit button
displays when you select any Local boot menu options, but the Redirect button displays when you
select a Shared boot menu option. See Redirect Shared Boot Menu Option (page 265).
To edit Shared or Local boot menu options
1

Select a boot menu option from the view area on the Boot Menu page, and click Edit.

If you selected Boot Disk Creator as the Image Creation Method, click Edit Boot Image. The Edit
Configuration page from the New Configuration Wizard will only display the
MenuOption<number> you selected from the Boot Menu page.

To make changes, right-click on the MenuOption<number> and select Edit Configuration, or click
Edit on the Edit Configuration page until you find the options you want to change.

See also: Edit Configurations (page 273) and Boot Menu Tab (page 262).

Redirect Shared Boot Menu Option


This option lets you select a Shared configuration from the Customize PXE Server <server name>
mode and redirect it to a Local configuration, which gives you greater flexibility in managing all
deployment jobs.
Example: Your main office is in Utah and there are 2 satellite offices, one in Los Angeles and the
other in New York, you can send a single deployment job to all client computers and have each
satellite office use its own Local configuration to boot to automation and access images.
Deployment Server lets you select the Automation - PXE or Bootworks environment (DOS/Windows PE/
Linux) configuration from the drop-down list when setting up imaging jobs. However, only Shared
configurations are displayed in the list. When the Deployment Server sends the job to client
computers, the Deployment Agent receives a message that it must boot to automation. Client
computers that are PXE-enabled will find the nearest PXE Server and receive the boot image files
needed to boot to automation.
When Redirect is used, the Shared configuration selected for the automation task within the
deployment job, can point to a Local configuration so that when client computers are booting to
automation, the Local configuration will be used to access local network servers and images.
To redirect a Shared boot menu option
1

From the PXE Configuration Utility, click File.

Select a PXE Server. (This is the Customize PXE Server <server name> mode.)

Click on a Shared configuration, and click Redirect.

Click the drop-down arrow and select a Local configuration from the list.

Click OK. The Shared configuration displays the redirected configuration in the list.

Import Boot Menu Options


This option lets you import boot menu options that were created using Third Party imaging software,
or previous versions of Altiris PXE Server.
Option 1:
1

From the New Shared Menu Option dialog, select Direct from floppy and click Import Boot Image.

Insert a floppy disk. The path and name of the new MenuOption<number> displays.

Click Next. A progress bar displays the PXE boot file image being read as it is imported.

Click Finish.

Altiris Deployment Solution Reference Guide

265

Chapter 14: PXE Configuration Utility

Install Pre-boot Operating System Files

Option 2:
1

From the New Shared Menu Option dialog, select User Supplied.

Copy the PXE files you want in the MenuOption<number> folder.

Click OK.

Install Pre-boot Operating System Files


Boot Disk Creator requires that you install the pre-boot operating system files for at least one preboot environment before you can create new configurations. Boot Disk Creator uses these files when
creating configurations and boot images. You can install all supported pre-boot operating system
files at the same time, or you can select to install only those pre-boot environments you want to use.
You can install FreeDOS and MS-DOS, but you must select which DOS version you want to run
since you cannot run both versions at the same time.
Example: you can install the DOS and Windows PE pre-boot operating system files to start creating
configurations to support your infrastructure, which currently does not have a need for Linux boot
images. After working with Deployment Server and Boot Disk Creator, you decide you want to
create Linux configurations and Linux boot images. You can open the Install Pre-boot Operating
System Files dialog at any time to install the Linux system files, or of the other pre-boot operating
system files.
When you install the pre-boot operating system files for DOS (page 266), Linux (page 267), or
Windows PE (page 267), a checkmark next to the operating system name indicates that the files have
been successfully installed. The operating system version number displays (except for MS-DOS),
and the Install button changes to display Update.
If you acquire a newer version of DOS, Linux or Windows PE, click Update to install the new files.
However, any existing operating system files will be deleted before the newer files are installed.
Example: If you installed Windows PE, and Altiris supports a newer version that becomes available,
click Update to install the new files. All existing Windows PE files will be deleted from the hard disk
before the new files are installed. If you experience any problems with the new version of Windows
PE, you will have to install the older version to restore Boot Disk Creator functionality for Windows
PE.
To install pre-boot operating system files
1

From the Boot Menu tab, click New.

Enter a name for the boot menu item in the Menu item properties field.

Click the operating system for the boot menu item. If there is an asterick next to the operating
system name, the pre-boot operating system files have not been installed.

Click the Install button next to the pre-boot operating system that you want to install.

DOS
You can install FreeDOS (page 266), MS-DOS (page 267) or both. However, you can only run one
version of DOS at a time. If both versions of DOS are installed, click either FreeDOS or MS-DOS to
select the version you want to run as the default for creating configurations.

FreeDOS
Deployment Solution provides FreeDOS in a file named BDCgpl.frm. The BDCgpl.frm file can be
downloaded from the Altiris Solution Center Web site and then saved to any location on the network.
When newer versions of FreeDOS become available, an updated .frm file will be available online
through Deployment Solution Hot Fixes or Service Pack releases.
Note: FreeDOS may not support newer motherboard chip-sets.

Altiris Deployment Solution Reference Guide

266

Chapter 14: PXE Configuration Utility

Install Pre-boot Operating System Files

MS-DOS
Using an original Microsoft Windows 95/98 installation CD, copy the appropriate files to a system
formatted floppy disk, a folder that can be accessed from Boot Disk Creator, or use the CD directly.
Use Microsoft Windows 95/98 installation CD:

Windows 95/98 installation CD.

Select to install MS-DOS from an original Microsoft

Floppy Disk: Select to format a disk using the Format a: /s command. Copy the required files listed
below from an original Microsoft Windows 95/98 installation CD to the floppy disk. Boot disk
creator only installs DOS files from the A drive. If you select B-Floppy Drive from the drop-down list,
Boot Disk Creator will still try to read data from the A-Floppy Drive.
Folder: Select to copy the required files to a folder that can be access from within Boot Disk Creator.

Boot Disk Creator requires the following MS-DOS files.


MS-DOS files

Required

Optional

HIMEM.SYS

EDIT.COM

EMM386.EXE

MEM.EXE

SMARTDRV.EXE

ATTRIB.EXE

SYS.COM

MODE.COM

XCOPY32.MOD

FORMAT.COM
FDISK.EXE

Important: The SMARTDRV.EXE file is required for all computers running a scripted install in

Windows 2003\XP.

Linux
Deployment Solution provides Linux RedHat Fedora in a file named BDCgpl.frm. The BDCgpl.frm
file can be downloaded from the Altiris Solution Center Web site and then saved to any location on
the network. When newer versions of Linux become available, an updated .frm file will be available
online through Deployment Solution Hot Fixes or Service Pack releases.

Windows PE
Altiris supports Windows PE 2005 as a pre-boot environment for Boot Disk Creator. When you
install Windows PE, you will be asked to supply 2 CDs: Windows PE 2005 and Windows Server
2003 SP1.
In most instances, the Welcome to Microsoft(R) Windows(R) Server 2003 page displays after
inserting the Windows Server 2003 CD. Click Exit to avoid installing the full version of Windows
Server.
There are two dialog pages to complete the Windows PE installation. You will first be asked to
provide the Windows PE CD, followed by the Windows CD. The text on the page lists the operating
system CD you need to enter for each of these pages.
Example: On the Windows PE CD page, the text displays Windows PE 2005 (Windows Server 2003while the Windows CD page displays Windows Server 2003-SP1 (Windows PE 2005). The first
operating system listed on each page is the CD you want to use.
SP1),

Altiris Deployment Solution Reference Guide

267

Chapter 14: PXE Configuration Utility

New Configuration Wizard

New Configuration Wizard


You can create as many configurations as needed to support varying types of computer
environments. Before you begin, you must install the pre-boot operating system files that Boot Disk
Creator uses to create new configurations. See Install Pre-boot Operating System Files (page 266).

To start the New Configuration Wizard, click the button on the toolbar of the
Boot Disk Creator tool, click Ctrl+N, or click File > New Configuration.

Configuration Name
This is the first page of the New Configuration Wizard, which is the same for DOS, Linux, or
Windows PE. You must enter a name of for the configuration to make the Pre-boot Operating System
for this Configuration fields active. The description field is optional but helps you to know what the
configuration contains, such as the file server type, NIC drivers, and any additional files you want
to add.
Field Definitions
Name: The configuration name you enter displays in the Configurations treeview after the wizard is

completed.

Enter a description for the configuration. (Example: enter the type of computer,
operating system, network adapter, and any other characteristics that will help you identify this
particular configuration.) After the Create Configuration and Create Boot Disk wizards complete, if
you select the configuration from the treeview, the description you entered for this field displays at
the top of the right pane.

Description:

Pre-boot Operating System for this Configuration: Boot Disk Creator supports DOS, Linux, and
Windows PE operating systems to create pre-boot environments. Select the pre-boot operating
system, and then click Install Pre-boot Operating System Files (page 266) to install pre-boot
operating system files.

File Server Type (DOS)


The Deployment Share stores image files, packages, and data files. By default, the Deployment
Share is installed to the Deployment Server, but it can be on another server, depending on the
whether you selected a Simple or Custom Deployment Solution installation.
Field Definitions
Select this option to store images on a Microsoft server using TCP/IP network
communications (recommended). However, if you use IPX to communicate with a Microsoft server,
select the IPX checkbox at the bottom of the page.

Microsoft Windows:

Novell NetWare (VLM): Select this option to store images on a NetWare server with VLM clients, using

IPX network communications.

Novell NetWare (Client32):

Select this option to store images on a NetWare server with 32-bit clients.

Use IPX to communicate with Netware: Select


Novel NetWare (Client32) server.

this checkbox if IPX is the network protocol for the

Network Adapter
The drivers listed in the Network Adapters window vary depending on the type of configuration you
are creating. You can install pre-boot operating system files for DOS, Linux, or Windows
Preinstallation Environment (Windows PE). See Install Pre-boot Operating System Files (page 266).

Altiris Deployment Solution Reference Guide

268

Chapter 14: PXE Configuration Utility

New Configuration Wizard

Example: After installing the pre-boot operating system files for Windows PE, the Windows NIC
drivers that are available to create a Windows PE configuration display, and are automatically added
to the new configuration. If you select Auto-detect network adapter, Windows PE determines which
network adapter driver to use.
Select a driver from the network adapters driver list. You must create a new configuration for each
type of network adapter that is installed on client computers, unless you want to create a Multi-NIC
configuration. See Multi-Network Adapter Configurations (page 270). If you want to add or change
adapter settings (such as I/O Memory, IRQ, and PCMCIA for DOS configurations) click Advanced.
See Advanced (page 269).
If the network adapter you want does not appear in the list, you can click Have Disk, Internet, or
Advanced (if they are available for the type of configuration you are creating) to add additional
drivers. See Have Disk (page 269), Internet (page 269), Advanced (page 269).
Field Definitions
Allow selection of multiple network adapters: Select this option to add multiple network adapter drivers

to a single PXE boot file configuration. This feature lets you build configuration files to boot
multiple computers that contain different types of network adapter cards. See Multi-Network
Adapter Configurations (page 270).

Select this to have Windows PE auto-detect the type of adapter that is


in a client computers when the boot image runs.

Auto-detect network adapter:

Have Disk
You can add network adapter drivers by using any disk media or navigating to a folder. Network
adapters can be downloaded from the manufacturers Web site and saved to a folder or a disk to be
installed later. New network adapters come with a floppy disk or CD to install the appropriate
drivers.

Internet
Altiris supports many manufacturer network adapters and supports a Web site for you to download
the latest NIC drivers. From the Network Adapter page, click Internet to launch the Web browser and
connect to ftp://support.altiris.com/support/NIC_drivers/. Download the driver you want, and then
unzip the files it to a folder on the hard drive. Click Add Driver and the driver you downloaded will
be added to the Network Adapters list.

Advanced
This options lets you add or change settings for network adapter cards so they will work correctly
when using DOS configurations. If you are creating a Linux or Windows PE configuration, this
option is not available. From the Network Adapter page, click Advanced. Refer to the following
properties and values.
Microsoft clients

EMM386 Memory (config.sys):

Advanced settings (protocol.ini):

Memory (protocol.ini):

IRQ (protocol.ini): Add

config.sys file.

Append memory address information to this line in the


Add parameters to the NIC section of the protocol.ini file.

Add parameters to the network setup section of the protocol.ini file.


parameters to the network setup section of the protocol.ini file.

Novell VLM clients

Emm386 memory (config.sys): Append

config.sys file.

Advanced settings (config.sys):

Altiris Deployment Solution Reference Guide

memory address information to this line in the

Add parameters to the NIC section of the net.cfg file.

269

Chapter 14: PXE Configuration Utility

New Configuration Wizard

Novell Client 32

Emm386 Memory (config.sys):

config.sys file.

Append memory address information to this line in the

Advanced settings (driver command line):

file.

Add driver command-line entries to the landrv.bat

Multi-Network Adapter Configurations


If you are creating a DOS configuration, when you select Multi-NIC configurations, a list of supported
drivers displays. You can select Multi-NIC drivers to be included in the configuration by pressing
Shift-Click or Ctrl-Click. After a client computer boots using a multi-network adapter configuration,
Boot Disk Creator applies the driver that matches the first network adapter card that it detects.
Example: if you are going to use the multi-network adapter configuration for several different client
computers, this option can save you time and effort in booting different computers. However, if a
client computer has 2 NIC cards and you use the multi-network adapter configuration to boot the
computer, the first NIC card is detected and can potentially be the wrong network adapter required
to connect to the Deployment Server.
Advanced Features
The network adapters you select must support DOS, Linux, or Windows PE so that client computers
can connect to a network or Deployment Server, depending on whether you create automation
partitions, or network or automation boot disks. The Have Disk (page 269) button lets you install
network adapter drivers from a disk, CD, or network folder. The Internet (page 269) button lets you
connects to an Altiris supported web site to download and install network adapter drivers. The
Advanced (page 269) button lets you further define network adapters and their drivers.
Multiple Network Adapters Load Order
This option is for DOS and Windows PE configurations only. This lets you specify which order the
physical network adapters will be detected when the client computer boots.
Example: If most client computers have a Broadcom Ethernet adapter, but some computers have a
3Com10/100 LAN PC Card Fast Ethernet card, you would use Up and Down to move the Broadcom
Ethernet adapter to the top of the list.

TCP/IP Protocol Settings


This page lets you set up TCP/IP protocol settings for boot configurations. TCP/IP is the default
protocol when client computers boot to automation on a Windows network. If you are using the IPX
protocol, Deployment Server uses its own IP stack to work on IPX networks.
Field Definitions
Obtain an IP address from a DHCP server: Select this option if you want client computers to obtain an

IP address from a DHCP server.

Use a static IP address: Select this option if you want a client computer, using this configuration, to
be assigned a specific IP address. Enter an IP address, Subnet mask, and default gateway. You can
also enter a primary and secondary WINS address if you need to resolve IP addresses and naming
conventions. This option also requires that you create a configuration for each client computer, so
that the IP address is not the same for all computers.

Altiris Deployment Server Communication


This option lets you set communication properties for the Deployment Server. The Deployment
and Port fields are critical because they define how client computers establish
communications with the Deployment Server.

Server IP address,

Altiris Deployment Solution Reference Guide

270

Chapter 14: PXE Configuration Utility

New Configuration Wizard

Example: The TCP port on the Deployment Server is set to 402 and the Port field in the Boot Disk
configuration is set to 502. This would result in client computers not being able to communicate with
the Deployment Server, because the port numbers do not match. To establish communications
between client computers and the Deployment Server, change the Port field in the Boot Disk
configuration to 402.
Note: The settings on this page are only used if you create an automation boot image where the

Automation Agent needs to know how to find the Deployment Server. If you intend to create a
network boot disk, you can ignore this page by clicking Next, as none of the properties will be used
to create a network boot image.
To set the TCP port on the Deployment Server

From the Deployment Server, click Start > Control Panel > Deployment Solution Configuration

applet > Options > Transport tab.

Enter the TCP port number.

Click OK.

Use TCP/IP multicasting to find the Altiris Deployment Server: Select this option to use TCP/IP
multicasting to find the Deployment Server. When client computers boot to automation using this
configuration, a multicast packet will broadcast across the network to find where the Deployment
Server is located.

Multicast IP address:

Port: This option defines which port client computers will use to communicate with the
Deployment Server Engine, which manages the Deployment Database, sends job commands
to the Deployment Agent, and more.

Server name: When you select Use TCP/IP multicasting to find the Altiris Deployment Server, a
multicast packet will broadcast to the server you specify. If you leave this field blank, the
client computer will connect to any server responding to the multicast packet.

Enter a multicast IP address for client computers to send a broadcast


packet across the network to find the Deployment Server.

Use TCP/IP to connect to the Altiris Deployment Server: Select this option to connect to a specific

Deployment Server. You must select this option if your network adapter or network does not support
multicasting. See your network adapter documentation or call the manufacturer or consult with your
IT department for information.

Server IP address: Enter the IP address of the Deployment Server to access information stored

Port: This option defines which port client computers will use to communicate with the
Deployment Server Engine, which manages the Deployment Database, sends job commands
to the Deployment Agent, and more.

in the Deployment Share. If you are using the Intel Universal NIC driver (UNDI), the IP
address is required.

Automation Agent Location


Remote: Select

this option to run the Automation Agent from the Deployment Share. This ensures
that you are running the latest version of the agent when the client computer boots to the automation
mode.

Local: Select

this option to run the Automation Agent from the local boot image, which is included
in the automation partition or in bootable media. The Automation Agent that boots the client
computer to automation mode, will always be the same version as when it was originally created. If
you want to update the Automation Agent to the latest version, you must reinstall the automation
partition or recreate all bootable media.

Network Configuration
This option lets you define how client computers connect to the Deployment Share or a file server
where image files are stored.
Window
Workgroup: Enter

the workgroup for the Deployment Share or file server.

Altiris Deployment Solution Reference Guide

271

Chapter 14: PXE Configuration Utility

New Configuration Wizard

NetWare
Server name: Enter the server name for the Deployment Share or file server. Click Advanced to enter
a NetWare context for the server, and then select a Frame type if it is different than the default value

of 802.2.

User name: Enter the authorized user name that was set up when the Deployment Share directory was
created. If you did not assign a User name and Password when for the Deployment Share or file server
was created, leave this and the Password field blank.
Password:

Enter the password for the user name.

Confirm password: Enter the password for the user name as confirmation that you entered the proper
password in the Password field.

Network Drive Mappings and Mount Points


This option lets you set up drive mappings (for DOS and Windows PE) or mount points (for Linux)
so that when client computers boot to automation or a network prompt, they will connect to the
appropriate server. You can create multiple drive mappings or mount points. However, if you are
creating a DOS configuration, the first mapped drive you specify must connect to the Deployment
Share.
Field Definitions
Manually create drive mapping: Select this option if you want the drive mappings to be included in the

autoexec.bat file when client computers boot to automation.

By default, the mapped drive that displays is F: \\<Deployment Share server>\eXpress. Click
the drop-down arrow and select a different drive letter if F: is already in use.

Drive:

Enter the path for the Deployment Share. The path you enter will map to the drive letter you
selected in the Drive field. You can also click Browse to navigate to the Deployment Share if you are
unsure of the directory path or if the image files are store on a file server.
Path:

Example:

Windows users:

NetWare users:

Linux users:

\\server\share

server\volume:directory

//server/mount point

Note: When entering Linux mount points, you must put a single quote around folders or filenames

that contain either a period (.) or a space. These are considered special characters in Linux and must
have single quotes around the name so that the directory path can be found. Example: //ImageServer/
DS Images/mnt/z.

Create and entry in the LMHOSTS file for the Deployment Server file store (other entries must be added
manually): Select this option if your network does not support NetBIOS name resolution for IP
addresses. Enter a Server name and IP address so that client computers can find the Deployment

Share where image files are stored.

Use NetWare login scripts to create drive mappings:

want login scripts to create the drive mappings.

Select this option if you use NetWare and you

Configuration Summary
This page lets you review all the options you selected throughout the New Configuration Wizard. If
you find a setting mis-entered or not what you want, click Back to re-select the option. When you
click Finish, the Create Boot Disk Wizard automatically displays for the next process to begin.
If you are using Boot Disk Creator from within the PXE Configuration Utility, the Edit
Configuration page displays next. See Edit Configurations (page 273).

Altiris Deployment Solution Reference Guide

272

Chapter 14: PXE Configuration Utility

New Configuration Wizard

Edit Configurations
This is the main Boot Disk Creator page that displays when you start the utility. If you are using Boot
Disk Creator from within the PXE Configuration Utility, this page displays at the end of the New
Configuration Wizard.
This feature lets you modify configurations that have already been created. As you select files and
folders from the treeview in the left pane, the configuration information displays in the right pane.
The display color changes to help you know the type of configuration you selected to view, edit, or
delete. The colors displayed are:

Blue:

Green: The configuration you selected or created is based on the Linux pre-boot environment.

Red: The

The configuration you selected or created is based on the DOS pre-boot environment.

configuration you selected or created is based on the Windows PE pre-boot


environment.

To change configuration settings, right-click on a configuration folder and select Edit Configuration,
and then click Edit until you find the page for the options that you want to change. You can also make
text edits to files (selected from the treeview) in the right pane.
All other files within a configuration can be edited as needed. However, after you edit a
configuration, Boot Disk Creator rewrites certain files within the configuration so that drive
mappings and mount points are always updated. The following files are rewritten after editing
configurations:

DOS - mapdrv.bat, unmapdrv.bat


Linux - mounts.local
WinPE - mapdrv.bat

See also: New Configuration Wizard (page 268), Install Pre-boot Operating System Files (page

266)

Additional Files
Boot Disk Creator lets you add additional files to folders that will either apply to a specific
configuration or to all configurations that are of the same type of pre-boot operating system.
However, any files you add to the global <OS> additional files folders will be written to the boot
image before the specific configuration files. If a file in the <OS> additional files folder is the same
name as a file in a specific configuration folder, it will be overwritten.
Example: if a file named 5684_Drivers resides in the DOS additional files folder, and the same file
5684_Drivers exists in a specific configuration folder, then when the files are written to a boot
image, the file in the configuration folder will overwrite the file in the DOS additional files folder.
This may cause unexpected results. If you edit text files in a <OS> additional files folder, yet the
specific configuration file is the one that is written to the boot image, the result will not be as you
expected.
Add files to all configuration
When you install a pre-boot operating system, a new folder will be added to the bottom of the
treeview on the main page of Boot Disk Creator. If you install pre-boot operating system files and
the <OS> additional files folders do not display, press F5 to refresh Boot Disk Creator. The folders
that display are as follows:

DOS additional files

Linux additional files

WinPE additional files

Boot Disk Creator will copy the files from the <OS> additional files folders to all corresponding
operating system configurations and will be added to the boot images. These folders are considered
global, since they can affect configurations of the same type.

Altiris Deployment Solution Reference Guide

273

Chapter 14: PXE Configuration Utility

PXE Server Tab

Example: using the Windows Copy and Paste command, you can add tracert.exe to the WinPE
additional files folder. Each WinPE configuration you create will then add the files in the WinPE
additional files folder to the boot image.
Add files to a specific configuration
If you want to add files to a specific configuration only, and do not want to use the global feature of
the <OS> additional files folders, do the following:
1

Right-click a configuration in the treeview and select New > Folder. A new subfolder is created
in the treeview.

Enter a name for the folder so that you know they are added files.

To add files to the <OS> additional files folder, do one of the following methods:

Copy files from a network folder and Paste them into the configuration folder.

Right-click a configuration and select Add File. A browser dialog displays to navigate to the
file you want to add.

Right-click on a configuration and select File > Text file. A new empty text file is added to the
treeview. Enter a name for the file and write text as needed in the left pane.

Create PXE Boot Image Files (PXE)


This option is for Boot Disk Creator configurations created from within the PXE Configuration
Utility. Because PXE Servers download boot image files to client computers, after you select all the
properties for a New Configuration, Boot Disk Creator must know what type of image file to create.
Field Definitions
Automation PXE image: The automation agent for the type of pre-boot operating system configuration
you created will be added to the settings you selected throughout the New Configuration Wizard.
Network PXE image: The configuration you created will not contain an automation agent. When client

computers boot with this image file, they will map to a network server and be at a users prompt.
(This option is not available in Shared Configuration mode.)

Force 2.88 MB PXE image:

Select this option to increase the size of PXE boot images.

PXE Boot Image Creation Complete


This page lets you know when the PXE boot image file is completed. Click Back to change the new
configuration settings for the boot menu option. When you click Finish, the boot menu option
displays in the Boot Menu tab.

PXE Server Tab


This lets you set response times for PXE Servers and specifies how the DHCP Server will be
discovered. By default, PXE Servers inherit the shared properties from the Shared Configurations
mode. Client computers use the information defined on this page to locate the PXE Server that
provides their services.
PXE Server properties
PXE Server IP address: By default, the IP address for both Shared Configuration and Customize PXE

Server modes are already entered. If, for some reason, you need to change the IP address on a PXE
Server, enter the same IP address in this field.

Enter the IP address for the specific PXE Server you selected from the File menu. When client
computers perform a PXE boot, the IP address helps them communicate with the PXE Server.

Altiris Deployment Solution Reference Guide

274

Chapter 14: PXE Configuration Utility

DS Tab

This is selected when you are setting the properties for a Shared
Configuration. You cannot change this selection on the other pages if you are setting properties for
the Shared Configuration.

Use Shared properties:

Customize PXE Server (Shared Configuration): This option is available when you select a specific
Server from the File menu. You can keep the settings on the page or customize the properties for the

PXE Server you selected.

Response Time: This lets you set the PXE Server response time for when client computers request a

PXE boot.

Example: If you have 3 PXE Servers, you can set the first PXE Server to Short delayed response (1/
2 second), the second to Immediate response, and the third to a Delayed response of your choice. This
helps control which PXE Servers will respond to client computers when they perform a PXE boot.
In this example, the second PXE Server would respond to client computers before the first server.
DHCP Server discovery:

Auto detect Microsoft DHCP Server and configure for PXE: Select this option when installing
Altiris PXE Server on the same server where Microsoft DCHP Server is installed and
running. PXE Server will then auto detect the presence of a Microsoft DHCP server, and
install and enable Option 60 in the DHCP Global Server Options. PXE Server will not
actively monitor DCHP ports for requests, but rather wait for clients to directly request PXE
services based on option 60 being enabled. This applies only to Microsoft DHCP Servers.

Select this option


when the PXE Server is installed on a server using a non-Microsoft DCHP server, or if you
do not want PXE Server to actively monitor the DHCP requests. PXE Server does not create
or set option 60 on the DHCP Server.

No DHCP Server installed on PXE Server (Use DHCP port): Select this option if PXE Server and

Third party DHCP Server installed on PXE server (Do NOT use DHCP port):

DHCP Server are installed on different servers. This option enables PXE server to actively
listen and respond to DCHP PXE requests.

DS Tab
This lets you set properties so that all PXE Servers can communicate with the Deployment Server.
PXE Servers and the Deployment Server work together to perform tasks, such as creating and
distributing an image, scripted OS installs, and more. The PXE Server must be able to access the
Deployment Server and the Deployment Database to retrieve the information required to carry out
these tasks on client computers.
The Deployment Server IP address, the Engine Port, and the Data Manager Port are critical fields
because they define how the PXE Server will establish communication with the Deployment Server.
Example: The TCP port on the Deployment Server is set to 402 and the Engine port on the PXE Server
is set to 502. This would result in the PXE Server not being able to communicate with the
Deployment Server because the port numbers do not match. To establish communication between
the 2 servers, change the Engine port field on the PXE Server to 402.
To set the TCP port on the Deployment Server
1

From the Deployment Server, click Start > Control Panel > Deployment Solution Configuration

applet > Options > Transport tab.

Enter the TCP port number.