ALTIRIS®

Deployment Solution™ 6.8 SP2 Deployment and Migration Guide

Notice
Altiris® Deployment Solution™ 6.8 SP2 © 2007 Altiris, Inc. All rights reserved. Document Date: June 25, 2007 Information in this document: (i) is provided for informational purposes only with respect to products of Altiris or its subsidiaries (“Products”), (ii) represents Altiris' views as of the date of publication of this document, (iii) is subject to change without notice (for the latest documentation, visit our Web site at www.altiris.com/Support), and (iv) should not be construed as any commitment by Altiris. Except as provided in Altiris' license agreement governing its Products, ALTIRIS ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTIES RELATING TO THE USE OF ANY PRODUCTS, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY THIRD-PARTY INTELLECTUAL PROPERTY RIGHTS. Altiris assumes no responsibility for any errors or omissions contained in this document, and Altiris specifically disclaims any and all liabilities and/or obligations for any claims, suits or damages arising in connection with the use of, reliance upon, or dissemination of this document, and/or the information contained herein. Altiris may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the Products referenced herein. The furnishing of this document and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any foregoing intellectual property rights. No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means without the express written consent of Altiris, Inc. Customers are solely responsible for assessing the suitability of the Products for use in particular applications or environments. Products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications. *All other names or marks may be claimed as trademarks of their respective companies.

Altiris® Deployment Solution 6.8 SP2

2

Contents
Chapter 1: About Altiris® Deployment Solution™. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Deployment Solution Architecture Deployment Server . . . . . Deployment Database . . . Deployment Share . . . . . Management Consoles . . Automation Tools . . . . . . Deployment Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 22 23 23 23 24 24

Part I: Planning and Installing Your Deployment System . . . . . . . . . . . . 25
Chapter 2: Preparing To Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Step Step Step Step Step Step 1: 2: 3: 4: 5: 6: Log on to Your Deployment Server Computer as an Administrator Create a Services Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gather Automation Operating System Install Files . . . . . . . . . . . Obtain a License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install .NET and MDAC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start Microsoft’s Internet Information Server (IIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 27 28 28 28 28

Chapter 3: Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Simple or Custom Install? . . . . . . . . . . . . . . . . . Simple Install. . . . . . . . . . . . . . . . . . . . . . . Custom Install . . . . . . . . . . . . . . . . . . . . . . Running the Setup Program . . . . . . . . . . . . . . . . . . . Enable Microsoft Sysprep Support . . . . . . . . . . . Enable Microsoft Windows Vista Sysprep Support . Remotely Install Deployment Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 29 29 29 29 30 30

Chapter 4: Post-Installation Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Step 1: Grant Full Control of the Deployment Share to Your Service Account. . . . . Step 2: Create Domain Join and Deployment Share Accounts . . . . . . . . . . . . . . . Domain Join Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Share Read/Write Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3: Grant Services Account the db_owner Role to Your Deployment Database . Step 4: Configure Your Deployment System . . . . . . . . . . . . . . . . . . . . . . . . . . . Add Your Domain Join Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Security and Add Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . Grant Console Rights to Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . Grant Database Rights to Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Deployment Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5: Configure Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6: Install the Deployment Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 7: Configure Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 8: (Optional) Configure PXE Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 31 31 32 32 33 33 33 34 34 35 35 35 35 35

Chapter 5: Deployment Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
About the Deployment Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Installing the Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Altiris® Deployment Solution 6.8 SP2

3

Using the Remote Agent Installer (Windows XP). . . . . . . . . . . . . . . . Step 1: Disable Simple File Sharing on Windows XP . . . . . . . . . . Step 2: Allow File and Printer Sharing in Windows XP SP2 Firewall Step 3: Get Local User Rights (admin$ Share) . . . . . . . . . . . . . . Step 4: Run the Remote Agent Installer . . . . . . . . . . . . . . . . . . Using a Script, E-Mail Link, or Manual Installation (All Platforms) . . . . Step 1: Provide Users Access to the Agent Installation Program . . Step 2: Create the Input File for a Silent Install . . . . . . . . . . . . . Step 3: Run the Installation Program . . . . . . . . . . . . . . . . . . . . Agent Auto Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

37 37 37 37 37 37 38 38 38 39 39

Part II: Booting Computers to Automation . . . . . . . . . . . . . . . . . . . . . . . 40
Chapter 6: What is Automation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Chapter 7: Automation Boot Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Which Automation Boot Method Should I Use? . PXE. . . . . . . . . . . . . . . . . . . . . . . . . . . . Automation Partitions . . . . . . . . . . . . . . . Boot Media (DVD/CD, USB Device, Floppy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 43 44 44

Chapter 8: Automation Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Which Automation Operating DOS . . . . . . . . . . . . . . Windows PE . . . . . . . . . Linux . . . . . . . . . . . . . System Should I Use? ................ ................ ................ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 46 47 47

Chapter 9: Installing and Configuring Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Configuring Automation Operating Systems . . . . . . . . . . . . Obtaining and Installing Windows PE, Linux, or DOS. . . Adding Additional Files . . . . . . . . . . . . . . . . . . . . . . . Adding Mass Storage Drivers for Windows PE. . . . . Adding Large Files to a Linux Boot Configuration . . . . . Configuring Automation Boot Methods . . . . . . . . . . . . . . . Configuring PXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Automation Partitions . . . . . . . . . . . . . . . Configuring Boot Media (DVD/CD, USB device, Floppy) . Deploying Automation to Managed Computers . . . . . . . . . . Using Automation Partitions or Boot Media . . . . . . . . . Using PXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 48 49 50 50 51 51 51 52 52 52 53

Chapter 10: Setting Up the Altiris PXE Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
What is PXE? . . . . . . . . . . . . . . . . . . . . . . . Why Use PXE? . . . . . . . . . . . . . . . . . . . . . . PXE Services and Architecture . . . . . . . . . . . How PXE Works . . . . . . . . . . . . . . . . . . . . . Part 1: DHCP Request and PXE Discovery Part 2: PXE Bootstrap . . . . . . . . . . . . . . PXE Planning and Installation. . . . . . . . . . . . Enabling PXE on Managed Computers . . . Installing and Configuring DHCP. . . . . . . How Many Altiris PXE Servers Do I Need? Number of Client Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 55 56 57 58 58 59 60 60 60 60

Altiris® Deployment Solution 6.8 SP2

4

Network Speed. . . . . . . . . . . . . . . . . Physical Layout of your Network. . . . . PXE Request Routing. . . . . . . . . . . . . Installing Altiris PXE Servers . . . . . . . . . . Configuring PXE Settings . . . . . . . . . . . . . . . . PXE Settings . . . . . . . . . . . . . . . . . . . . . . . . Shared vs. Local. . . . . . . . . . . . . . . . . . . Session Timeout . . . . . . . . . . . . . . . . . . . DHCP Server Options . . . . . . . . . . . . . . . Boot Integrity Services . . . . . . . . . . . . . . Boot Integrity Services (BIS) Removal Boot Options . . . . . . . . . . . . . . . . . . . . . . . . Shared vs. Local. . . . . . . . . . . . . . . . . . . PXE Redirection . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

60 60 61 61 61 62 62 62 62 62 63 63 63 63

Part III: Using Deployment Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Chapter 11: Deployment Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Computers. . . . . . . . . . . . . . . . . Jobs . . . . . . . . . . . . . . . . . . . . . Creating Jobs and Tasks . . . . . . . Context Menus (Right-click). . . . . Find a Computer in the Database Using Lab Builder . . . . . . . . . . . Computer Import File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 66 67 67 67 68 70

Managing from the Deployment Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Deployment Console Basics . . . . . . . . . . . . . . . . . . . . . . Features of the Deployment Console. . . . . . . . . . . . . . Computers pane . . . . . . . . . . . . . . . . . . . . . . . . . . . Jobs pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Details pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shortcuts and Resources View . . . . . . . . . . . . . . . . . . Thin Client View of the Deployment Console . . . . . . . . . . . Installing the Thin Client View . . . . . . . . . . . . . . . . . . Switching Between Two Views . . . . . . . . . . . . . . . . . . Computers Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resources pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . Inventory Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . Toolbars and Utilities . . . . . . . . . . . . . . . . . . . . . . . . Deployment Solution Utility Tools . . . . . . . . . . . . . . . . Software Virtualization Solution . . . . . . . . . . . . . . . . . . . . Using SVS Admin Utility with Deployment Solution . Extending the Tools Menu on the DS Console . . . . . . . . . . Computer Filters and Job Conditions . . . . . . . . . . . . . . . . . Creating Conditions to Assign Jobs . . . . . . . . . . . . . . . Creating a Computer Group Filter . . . . . . . . . . . . . . . . General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Console options . . . . . . . . . . . . . . . . . . . . . . . . . . . Global options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sysprep Settings . . . . . . . . . . . . . . . . . . . . . . . . OS Product Key tab. . . . . . . . . . . . . . . . . . . . . . . Task Password options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 73 73 74 74 75 76 76 76 77 78 78 79 80 80 81 81 82 83 83 84 85 85 85 86 86 86

Altiris® Deployment Solution 6.8 SP2

5

Domain Accounts options . . . . . . . . . . . . . . . . RapiDeploy options . . . . . . . . . . . . . . . . . . . . Agent Settings options . . . . . . . . . . . . . . . . . . Custom Data Sources options . . . . . . . . . . . . . Allowed Stored Procedure List . . . . . . . . . . Virtual Centers . . . . . . . . . . . . . . . . . . . . . . . Security in Deployment Solution . . . . . . . . . . . . . . Best Practices for Deployment Solution Security. Enabling Security . . . . . . . . . . . . . . . . . . . . . Groups . . . . . . . . . . . . . . . . . . . . . . . . . . Rights . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Permissions . . . . . . . . . . . . . . . . . . . . Connecting to Another Deployment Server . . . . . . . Rejected Computers in Deployment Solution . . . . . . Refresh Deployment Solution . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

87 87 88 88 88 89 89 89 90 92 92 93 95 96 96

Managing Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Viewing Computer Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Adding New Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Creating a New Computer Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Importing New Computers from a Text File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Computer Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 General Configuration Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Microsoft Networking Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 TCP/IP Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 TCP/IP Advanced Options - IP interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 TCP/IP Advanced Options - Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 TCP/IP Advanced Options - DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 TCP/IP Advanced Options - WINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 TCP/IP Advanced Options - Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 NetWare Client Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Operating System Licensing Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 User Account Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Deployment Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Deployment Agent Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Server Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Startup/Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Deployment Agent for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Deployment Agent Settings for DOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Drive Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Remote Desktop Connection Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Agent for Macintosh Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Deployment Agent for CE .NET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Managing Client Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Computer Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Altiris® Deployment Solution 6.8 SP2

6

Network Configuration . . . . . . . . . . . . . . . . . . . . TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Deployment Rules . . . . . . . . . . . . . . . Lights-Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . Install Automation Partition . . . . . . . . . . . . . . . . . Change Agent Settings . . . . . . . . . . . . . . . . . . . . Deploying and Managing Servers . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

125 125 125 125 125 126 126 126 127 127 129 130 130 130 131 133 133 134 134 135 135 136 136 137 138 138 139 139 141 141 141 142 143 143 144 144 145

Building and Scheduling Jobs

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 148 150 151 151 151 152 152 152 152 153 153 153 153 154

Viewing Job Details. . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . Job Scheduling Wizard . . . . . . . . . . . . . . . . . . Select Job(s) . . . . . . . . . . . . . . . . . . . . . . Select Computer(s) or Computer Groups . . . Setting Conditions for Task Sets . . . . . . . . . . . Order Condition Sets. . . . . . . . . . . . . . . . .

Altiris® Deployment Solution 6.8 SP2

7

Scheduling Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Deployment Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Creating a Disk Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Creating a Mac Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Creating a Ghost Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Advanced Sysprep Settings for Creating a Disk Image . . . . . . . . . . . . . . . . . . . . . . . . . 162 Advanced Sysprep Settings for Creating a Disk Image in Windows Vista . . . . . . . . . . . . . 162 Create Disk Image Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Distributing a Disk Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Distributing a Mac Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Distributing a Ghost Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Advanced Sysprep Settings for Distributing a Disk Image . . . . . . . . . . . . . . . . . . . . . . . 166 Advanced Sysprep Settings for Distributing a Disk Image in Windows Vista . . . . . . . . . . . 166 Distribute Disk Image-Resizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Distribute Disk Image-Additional Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Imaging Computers from USB Disk on Key (DOK) Devices (JumpDrives). . . . . . . . . . . . . 167 Scripted OS Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Scripted Install for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Select Operating System Version and Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Installation Source Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Operating System-Source Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Partition and Format Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Import an Answer File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Answer File Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Add a New Variable Value or Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Add a New Variable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Command-line Switches for Scripted Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Deployment Agent Settings for Scripted Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Scripted Install Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Scripted Install for Windows Vista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Scripted Install for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Scripted Install Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Distributing Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Distribute Software Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Managing the SVS Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Import Package Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Capturing Personality Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Capture Personality Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Distributing Personality Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Distribute Personality Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Modifying Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Backing up and Restoring Registry Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Get Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Run Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Script Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Using LogEvent and WLogEvent in Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Copy File to . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Copy File to Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Modifying Tasks in a Deployment Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Modifying Multiple Change Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Creating New Script Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Copy and Paste Jobs and Job Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Altiris® Deployment Solution 6.8 SP2

8

Importing and Exporting Jobs . . . . . Setting Up Return Codes . . . . . . . . Sample Jobs in Deployment Solution Initial Deployment . . . . . . . . . . . . . Configurations . . . . . . . . . . . . . Advanced Configuration. . . . Jobs . . . . . . . . . . . . . . . . . . . . Advanced . . . . . . . . . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

192 193 195 196 196 197 197 198

Part IV: Best Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Chapter 12: Securing Deployment Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Part 1: Deployment Server Accounts . . . . . . . . . . . . . . Service Account . . . . . . . . . . . . . . . . . . . . . . . . . . Domain Join Accounts . . . . . . . . . . . . . . . . . . . . . . Deployment Share Read/Write Account . . . . . . . . . . Part 2: Deployment Administrator Accounts. . . . . . . . . . Role and Scope Based Security . . . . . . . . . . . . . . . Deployment Console Security. . . . . . . . . . . . . . . . . Manage By Exception . . . . . . . . . . . . . . . . . . . . . . Rights and Permissions . . . . . . . . . . . . . . . . . . . . . Grant Rights to Administrators . . . . . . . . . . . . . Grant Permissions to Administrators . . . . . . . . . Permission Rules . . . . . . . . . . . . . . . . . . . . . . . . . Part 3: Database Security . . . . . . . . . . . . . . . . . . . . . . Required Database Rights . . . . . . . . . . . . . . . . . . . Rights Required to Install . . . . . . . . . . . . . . . . Rights Required for the Services Account. . . . . . Rights Required for Deployment Administrators . Part 4: Securing Communication . . . . . . . . . . . . . . . . . Deployment Agent Authentication. . . . . . . . . . . . . . Key Authentication . . . . . . . . . . . . . . . . . . . . . Additional Agent Security . . . . . . . . . . . . . . . . . . . Keyboard Locks in Automation . . . . . . . . . . . . . . . . Appendix A: Remote Agent Installer Rights . . . . . . . . . . Appendix B: Managing Task Passwords . . . . . . . . . . . . . Appendix C: Managing Key-Based Agent Authentication . Backing up the Server Private Key . . . . . . . . . . . . . Enabling Key-based Authentication with Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 201 202 202 203 203 204 204 204 205 205 205 205 206 206 207 207 208 208 208 210 210 211 211 212 212 212

Chapter 13: Migrating Application Data and User Settings . . . . . . . . . . . . . . . . . . . . . 213 Chapter 14: Capturing and Deploying Disk Images . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
What is a Disk Image? . . . . . . . Imaging in Deployment Solution How Imaging Works . . . . . . . . . File Systems . . . . . . . . . . . Partitions. . . . . . . . . . . . . . Partition Size . . . . . . . . Spanning Media . . . . . . . . . Multicasting . . . . . . . . . . . . How Multicasting Works HTTP Imaging . . . . . . . . . . Capturing Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 214 214 214 215 215 215 216 216 216 216

Altiris® Deployment Solution 6.8 SP2

9

Deploying Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Post-Imaging Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Managing Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Chapter 15: ImageX Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Obtaining and Installing ImageX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Capturing and Distributing ImageX Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

: Mac Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Creating an Automation Image . . . . . . . . . . . . . . . . . . . . . . . . Step 1: Configure a Source Computer . . . . . . . . . . . . . . . . . Step 2: Provide Root Password for Automation . . . . . . . . . . Step 3: Provide Credentials to Access Images . . . . . . . . . . . Step 4: Image the Source Computer. . . . . . . . . . . . . . . . . . Configuring NetBoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1: Configure the NetBoot Image . . . . . . . . . . . . . . . . . Step 2: Start the NetBoot Service . . . . . . . . . . . . . . . . . . . Configuring AppleTalk Filing Protocol Shares to Host Disk Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 219 220 220 221 221 221 222 222

Chapter 16: Symantec® Ghost® Imaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Chapter 17: Software Packaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Why Use Software Packaging? . . . . . . . . . . Overview of the Software Packaging Process Setting up a Reference Computer . . . . . . . . . . . Accessing Wise SetupCapture . . . . . . . . . . Capturing a Software Package . . . . . . . . . . . . . What Can I Capture?. . . . . . . . . . . . . . . . . The Capture Process . . . . . . . . . . . . . . . . . Customizing a Software Package . . . . . . . . . . . Distributing a Software Package . . . . . . . . . . . . Appendix A: Migrating From RapidInstall . . . . . . . . . Appendix B: Windows Installer Format Explained . . . Advantages of Windows Installer . . . . . . . . Appendix C: SetupCapture Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 224 225 225 225 225 226 226 226 226 226 227 229

Chapter 18: Deploying Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Writing a Script . . . . . . . . . . . . . . . . . . . . . Server Scripting Commands . . . . . . . . . Retrieving Database Values Using Tokens Running Scripts on the Server . . . . . . . . Reporting Errors . . . . . . . . . . . . . . . . . . . . . DOS/CMD Error Handling. . . . . . . . . . . . Visual Basic Error Handling . . . . . . . . . . Linux Shell Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 232 233 234 234 235 236 237

Chapter 19: Creating an Image Distribution Framework . . . . . . . . . . . . . . . . . . . . . . . 238
Why Use an Image Distribution Framework? PXE Redirection . . . . . . . . . . . . . . . . . . . . What if I Am Not Using PXE? . . . . . Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Distribution Framework . . . . . . . Step One: Set Up Local Image Stores . . Step Two: Replicate Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 239 239 239 239 239 240

Altiris® Deployment Solution 6.8 SP2

10

Step Three: Configure the Server Lookup Utility. . . . Create a Configuration . . . . . . . . . . . . . . . . . . Create a Server Lookup File . . . . . . . . . . . . . . GetSRV.EXE Parameter Descriptions . . . . . . . . . Step Four: Create a Boot Disk Creator Configuration Modify Mapdrv.bat to call Getsrv.bat. . . . . . . . . Deploy the Boot Configuration . . . . . . . . . . . . . Step Five: Distribute an Image . . . . . . . . . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

. . . . . . . .

240 240 240 241 241 242 242 242

Chapter 20: Deploying and Managing Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 244 245 246 246 247 247 248 248

Part V: Operating System and Platform Reference . . . . . . . . . . . . . . . . 249
Chapter 21: 64-bit Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
64-bit Job Conditions and Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 64-bit PXE Boot Images & Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Adding Files to a Boot Disk Creator Configuration for 64-bit. . . . . . . . . . . . . . . . . . . . . . . . . 250

Chapter 22: Linux and Unix Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
ADLAgent . . . . . . . . . . . . . . . . . . . . . . Installing and Configuring ADLAgent . Distributing Software . . . . . . . . . . . . . . Imaging Linux and Unix Filesystems . . . . Linux Bootloaders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 251 251 252 252

Chapter 23: Managing Thin Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Supported Thin Client Manufacturers Thin Client Operating Systems . . . . . Windows XP Embedded (XPe) . . The Enhanced Write Filter . . Using the EWFMGR Utility . . Windows CE .NET . . . . . . . . . . . Linux . . . . . . . . . . . . . . . . . . . Licensing Thin Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 254 254 255 256 257 257 257

Chapter 24: Windows Vista. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Installing the Deployment Agent on Vista Vista Remote Control . . . . . . . . . . . . . . Vista Software Distribution . . . . . . . . . . Vista Run Script Tasks. . . . . . . . . . . . . . Deployment Agent UI on Vista . . . . . . . . Vista Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 258 258 258 259 259

Chapter 25: Power Mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Installing The Mac Deployment Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Altiris® Deployment Solution 6.8 SP2

11

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internet. . . . . . . . . . . . . . . Create Automation Boot Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Have Disk . 260 Part VI: Reference: Deployment Solution Help Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Deployment Server Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 SP2 12 . . . . . . . Option . . . . . . . . . . . . . . Install Pre-boot Operating System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Configuration Wizard . . . . . . . . . . . . . . . Drive Mappings Option Transport Option . . . Configuration Name . . . . Create PXE Boot Image Files (PXE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WinPE Boot Option Settings . . . . . . . . . . . . . . . . . . . . 262 Logon Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Toolbar Description . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Edit Shared Menu Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . Windows PE . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Edit Configurations . . . . . . . . . . . . . . . . . . . . . . . . . 290 292 293 293 Altiris® Deployment Solution 6. . . . . . . . . . . . . . . . . PXE Boot Image Creation Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . 263 264 264 265 267 268 268 269 Introduction to Altiris® Boot Disk Creator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create an Automation Install Package . . . . . . . . . . . . . . . TCP/IP Protocol Settings . . . . . . .Removing the Mac Deployment Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remove Automation Partition. . . . . . . . . . . . . . . . . . . . . . . . . . . Create Boot Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Missing Files for Processor Types . . . .. . . . . . . . Import Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 Boot Menu Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Altiris Deployment Server Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DOS . . . . . . . . . . .. . . . . . . . . . . New Shared Menu Option . . . . . . . . . . . . . . . MS-DOS . . File Server Type (DOS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authentication Option Connections Option . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . Redirect Shared Boot Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create Network Boot Disk . . . . . . . . . . . . . . . . . . . . . . . Multi-Network Adapter Configurations . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . Debug Option . . FreeDOS . . . . . . . . . . . . . . . . 272 272 272 273 273 274 274 275 275 275 276 277 277 278 278 278 279 280 280 280 280 281 282 283 283 284 284 285 285 285 286 286 286 PXE Configuration Utility . . . . . . . . Additional Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automation Partitions. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Drive Mappings and Mount Points . . . . . . . . . . . . . Network and Automation Boot Disks. . . . . . . . . . . . Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk Imaging Option . . . . . . . Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add New Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Properties for an Image File General Properties for a Volume . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . Regenerate Boot Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . .. . . . . . .Import Boot Menu Options. . . . . . . . . . . . . . . . . . . . . . . . . . . General Properties for Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAC Filter Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . Create an Image Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . Altiris Deployment Server Communication . . . . . . . . . . . . . . . . Configuration Name . . . . . . . . . Make Self-Extracting Images . . .. Create PXE Boot Image Files (PXE) . . . . . . . . . PXE Boot Image Creation Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Adapter . . . . . . . . . . . Additional Files . . . . . . . . . . . . . . . . . . . . . Find Missing Split Image Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . . . . . . . . . . General Properties for a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .8 SP2 13 . . . . . . . Disk Partition Properties . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . Define MAC Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PXE Server Tab . . . . . . . . . Multi-Network Adapter Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filter Results . . . . . . . BIS Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View Properties . . . . . . . . . . . . MS-DOS . . . . . . . . . . . . . . . . . . . . . . . . . . . New Configuration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Find Files . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote PXE Installation . . . . . . . . . . . . . . . . . . . . . . . . Have Disk . . . . . . . . .. . . . . . . . . . . . . . . . Advanced . . . FreeDOS . . . Multicast Tab . . . . . Status Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .. . . . . . . . . . DS Tab . . . . . . . . . .. . Open a File . . . Internet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCP/IP Protocol Settings . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Convert an Image . . . . . . . . . . . . . . . Opening Split Image Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows PE . . . . . . . . . . Data Logs Tab . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . Extract a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Edit Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description Properties for an Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Drive Mappings and Mount Points Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Using ImageExplorer . . . . . . . . . . . . . . 318 318 318 318 319 319 319 319 319 319 319 320 320 321 322 322 322 323 Altiris® Deployment Solution 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File Server Type (DOS) . . . . . . . . . . . . . . . Install Pre-boot Operating System Files. . .. . . . . . . 294 294 294 295 295 295 296 296 296 297 297 298 298 299 299 299 300 300 301 301 302 302 303 304 304 304 306 307 308 308 310 310 311 311 Altiris® ImageExplorer . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . Deployment Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding the Number of Licenses Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 324 324 325 325 326 326 327 328 Installing Deployment Server . . . . . . . . . . . . . . . . . . . . HP client computers and licensing. . . . . . . . . . . . . . . . . . . . Command Line Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support for Multiple Database Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Print a File . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Connectivity and Network Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Server System Requirements . Install a Regular License for Altiris Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Share . . . . . . . . . . . . . Installing Deployment Solution Agents . . . . . . . . . . . . . . Adding a License from the Deployment Console . . . . . . . . . . . . . . . . . . . . . . . . . . Simple Install for Deployment Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Print Preview . . . . . . . . . . . . . . . . . . . . Print Folder Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting a Password on an Image File Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automating the Installation of Deployment Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the License Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Altiris PXE Server . . . Select Computers on the Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Not Enough Free Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Editing the Sample. . . . . . . Thin Client Install for Deployment Server . . . . . . . . . . . . . . . . . . . . . Deployment Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Custom Install for Deployment Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .inp file . . . . . . . . 331 332 332 333 334 334 334 335 336 337 340 343 343 344 345 346 346 347 347 347 347 348 348 348 349 349 349 349 350 350 352 352 353 354 355 355 356 356 357 357 357 358 358 Altiris® Deployment Solution 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 SP2 14 . . . . . . . . . . Installing Deployment Agent on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rapid Deployment Pack Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Agent Installer . . . . . . . Specify install directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Template File using Remote Agent Installer Using the Template File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Web Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install Multiple Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatically Add to a Group. . . . . . Change Settings . . . . . . . . . . . . . . . . . . . . . . . ImageX Sample Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . Split Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enter administrator account information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Deployment Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download Microsoft Sysprep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Get Server Security Key . . . . . . . . . . . . DS Installation Help . . . . . . . . . . . . . . . . . Installing the Automation Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detecting an Expired License . . . . . . . . . Component Install for Deployment Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Deployment Agent for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Computers Not Using a Regular License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expired Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Deployment Server Components . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . Global . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance . . . . . . . . Deployment Web Console Options . . . . . . . . . . . . . . . . Configuring the Deployment Server AClient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 370 371 371 372 372 372 372 373 373 373 373 374 375 375 375 379 380 381 382 383 385 385 386 387 387 387 388 388 388 389 389 390 390 Altiris® Deployment Solution 6. . . . . . . . . . . . . . . . . Setting Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 Deployment Web Console Basics . . . . . . . . . . . . . . . Deployment Web Console Information Sysprep. . . . . . . . Deployment Server Configuration . . . . Basic Tasks from the Deployment Web Console . Enabling Security . . Pre-boot Operating System (Custom) Deployment Database Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Managing from the Deployment Web Console . . . . . . . . . . . . . . . . . . . . . Add Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Database Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Notification Server Clients without AClient . Configuring the Deployment Server Agent . Using Package Servers to Replicate Deployment Jobs . . . . . . . . Add Components Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 360 360 361 362 363 363 364 364 365 365 365 365 366 366 366 Part VII: Deployment Web Console . . . . . . . . . . . .8 SP2 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Install Configuration . . . . Details pane . Creating Deployment Server AClient Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Deployment Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Components . . . . . . . . . . . Finding and Filtering Computers and Jobs . . . . . . . . . . . . . . . . . . . . . . . . Client Connection to Server . . . . . . . . . . . Adding Deployment Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . Altiris Console Collections . . . . Console Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Server Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduling Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Jobs pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating Deployment Reports from the Altiris Console. . . . . . . . . . . . . . . . . . . . . . . . . . . Logon . Computers pane . . . . . . . . . . . . . . . Assigning and Scheduling Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task Password options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing AClient to a Notification Server Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Agent Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reject Client Computer Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-boot Operating System (Simple) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automated Deployment Services (ADS) . Automation Agent Settings . . Deployment from the Altiris Console . . . . . Altiris PXE Server Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rights . . . . . . . . . . . . . . . . . . . Installation Information Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Production Agent Settings . . . . . . . . . . . . . . . . . . . . . . . . Remote Computer Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 Deployment Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 Adding New Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Lights-Out . . . . . . . . . . . . . . . . .8 SP2 16 . . . . . 413 TCP/IP. . . . . . . . . . . . . . . . . . . . . . . . . Setting the Altiris Agent Configuration Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Location . . . . . . . . . . . . . . . . . . . . . 403 Creating a New Computer Account . . . . . . . . . . . . . . 413 Bay. . . . . . . . . . . . . . . . . 414 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 TCP/IP Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Tasks . . . Scheduling Jobs . . . . . . . . . . . . . . . . Setting the DS Agent Polling Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 User Account Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job Scheduling Wizard Select Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Polling Intervals in Deployment Solution . . . . . . . . . . . . . . . . . 412 Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up a Central Deployment Server Library Setting Up Package Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 Computer Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Scheduling Jobs from the Deployment Web Console . . . . . . . . . Modify the DS Library Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 420 422 422 422 422 422 423 Altiris® Deployment Solution 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 Viewing Job Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 Changing Task User Password options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 Importing New Computers from a Text File . . . . . . . . . . . . . . . . 408 NetWare Client Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 Operating System Licensing Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Network . . . . . . . . 412 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 Managing Multiple Deployment Server Systems . . . . . .Overview of Package Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting and Importing Deployment Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building New Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 391 392 392 393 396 396 397 Managing Computers from the Deployment Web Console . . 413 Server Deployment Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 Inventory . . 406 Networking Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Creating a Computer Group Filter . . 415 Find a Computer in the Database . . . . . . . . . . . . . . . . . . . . . . . 400 Viewing Computer Details . . . . . . . . . 410 Managing Agent Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 Remote Operations . . . . . . . . . . . . . Select a Job . . . . . . . . . . . . . . . . . 400 Scheduling Jobs from Other Deployment Server Systems . . . . . 414 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 Adding Deployment Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Computer Details . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 446 447 448 450 451 451 452 452 453 456 460 471 472 474 476 478 479 480 482 484 Altiris® Deployment Solution 6. . . . . . . .exe) Switches Keyboard and Screen Lock Utility (Kbdsclk) Switches . . . . . . . 426 Advanced Sysprep Settings for Distributing a Disk Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add Component Entries . axengine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Server Install Switches . . . . . . . . . . . . 446 Job Utilities. . . . . . . . . . 427 Distribute Disk Image—Additional Options . . . . . . . . . . . . . . . . . . ADLAgent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 Advanced Run Script Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 Setting Up Return Codes . . . . . . . . . 440 Initial Deployment . . . . . . . . . . 437 Copy File Advanced. . . . . . . . . 434 Modifying Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simple Install Entries . . . . . . . 445 Appendix A: Command-Line Switches. . . . . . . . . . . . . Deployment Agent for DOS Install (Bwinst. . . . . . . . . . . 424 Advanced Sysprep Settings for Creating a Disk Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 Run Script . . . . . . 438 Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 Capture Personality-Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428 Distributing Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 Distribute Personality Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 Part VIII: Technical Reference . . . . . . . . Schedule Job Utility . . . . . . . . . . . . . . . . . . . . .config Parameters . . . . . . . .inp Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .exe. . 442 Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create Job Utility . . . . . . . 436 Copy File . . . . . . . . . . . . . . . . . Job Import Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job Export Utility . . . . . . . . . . . . . . . . . . . . . . . 428 Imaging Computers from USB Disk on Key (DOK) Devices (JumpDrives). . . . . . . . . . . . Deployment Agent for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425 Distributing Disk Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Custom Install Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Options . . . . . . . . . . . . . . . . . . . . . . . . . 431 Capturing Personality Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 Distributing Personality Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425 Create Disk Image Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aclient. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 Importing and Exporting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .exe . . . . . . . . . . . . . . . . 434 Backing up and Restoring Registry Files . . . . Silent Install Options. . . . . . . . . . . . . . . . . . . . .config Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 Distribute Disk Image—Resizing . . . . Deployment Agent for DOS Command-line Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bootwork. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating a Disk Image . . . . 434 Get Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aclient. . . . . . . . . . . . Import Computer Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 Distribute Software-Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 SP2 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .exe Command-line Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 Copy Jobs and Job Folders. . . . . . . . . . . . . . . . AClient. . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install Office XP from UNC Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DIR Command at DOS . . The Token Replacement Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485 486 486 487 Chapter 26: RapiDeploy Technical Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIRM Command-Line Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installer Return Codes . Finding the Right Token Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 Imaging . . . . . . . . . . . . . . . . . . . . Template File Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . How FIRM Works . . . . . . . . . . . . . . . . . . . Capture User Desktop Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 489 490 502 502 503 503 504 Appendix B: Tokens: Dynamic Database Access . . . . . . . . . . . . . . . . . Token Replacement Template Files . . . . . . . . . . . . . . . . . Migrations . . . . . . . . . . Command-line Switches for the Pocket PC Agent Command-line Install Switches for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509 511 512 512 512 513 513 514 Appendix C: Error Codes . . . . . . . . . . . . . . . . . . . . . . Custom Tokens. . 509 System Tokens. . . . . . . . . . . . . . .8 SP2 18 . . . . . . . . Using File System Independent Resource Management (FIRM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribute Disk Image . . . . . . . . . . . . . . . . . SQL 2000 Unattended Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 519 520 520 522 523 524 Appendix D: System Jobs for Deployment Solution . . . . . . . . . . . . . . . . . . . . Simple Tests . . . . . . Creating Unique Files Using Tokens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create Disk Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communication Error Messages Critical Error Messages . . . . . . . . . . . . . . . . . . . . . . . DIR Command at Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 530 530 530 530 530 531 531 531 531 532 532 532 533 533 534 534 535 535 Altiris® Deployment Solution 6. . . . . . . . . . . . . . . . . Capture User Microsoft Office Settings . . . . . . . . . . . . . RapiDeploy Command-line Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Memory Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Command-line Switches with Executable Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install Office XP from Mapped Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capture User Application Settings. . . . . . . . . . . . . . . . . . SQL 2000 Unattended Install Using a RIP Copy WLogevent to Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running FIRM . . . . . . . . . . . . . . . . . . . . . 516 General Error Messages . . . . . . . . . . . . . . . . . . . . . .0 Runtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command-line Install Switches for WinPE . . . . . . . . . . . . . . . . . . . . . . . . . Capture User Printer Settings. . . . . . .Client BIOS Settings for Wake-On LAN and PXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribute RapidInstall Package . . . . . . Client Error Messages . . . Install MSI 2. . . . . . . . . . . . . . . . . . Partition Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tokens . . . . . . . . . . . . . . . . . . . . . . . . . . . . Misc Jobs. . . . . . . . . . . . . . . . . . . 489 RapiDeploy Executable Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running RapiDeploy from the Command-line . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . 563 Altiris® Deployment Solution 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logevent Script (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribute RapidInstall Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549 PXE MTFTP . . . Create W2K Install Disk Image (Target HD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PXE Manager and PXECfg Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distribute Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstall Office XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stop SQL Server Service . . . Create RH7 Install Disk Image (Target HD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550 550 551 552 552 553 553 554 554 555 Appendix F: Deployment Agent Authentication . XP Embedded . . . . . . . . . . . . . . . . . . . Deployment Agent on Windows (AClient) Deployment Agent on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Web Console (Web Console) DB Management (Middle Man) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WLogevent VB Script (Windows) . . . . . . . . .8 SP2 19 . . . . . . . . . . Restart Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 Key in the Security Folder . . . . . . . . . . . . . . . Start SQL Server Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Agent Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server-side Embedded VBScript (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create RH8 Install Disk Image (Network) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RH7 Scripted Install (Network). . . . . . . . . . . . . . . . . . . . Pocket PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WLogevent CMD Script (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . Install Altiris Pocket PC Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable Enhanced Write Filter. . .Repair Office XP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wake up Computer . . . . . . . . . . . . . . . . . . . Shutdown Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Email if Disk Space Low (Linux) . . . . . . . . . . RH8 Scripted Install (Network). . . . . . . . . . . . . . . . . . . . . . . . . . . . . RH7 Scripted Install (Target HD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Enhanced Write Filter . . . . . . . . . . . . . . . . RapiDeploy Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Console (Win32 Console). . . . . . . . . . . . . . . . . . . . . . . . . . . W2K Scripted Install (Target HD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client/Server File Transfer Port . . . . . . Send Error Email (Windows) . . . . . . . . . . . . . . . . . 556 Appendix G: Windows Registry Keys . . . . . . . . . . . . . . . . Create RH7 Install Disk Image (Network) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scripted OS Installs . . . . . . . . . . . . . . . . Move Computer to Default Container (Windows) Move Computer to Specific OU (Windows) . . . . . . . . SVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535 535 535 536 536 536 536 536 537 537 537 537 539 540 541 541 542 543 543 544 545 545 545 545 546 546 546 546 547 547 547 547 547 548 548 Appendix E: Network Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restart HTTPD Service (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . .. . . . . . . . . . Using Deployment Solution Switch Add-On . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. .. . . . . . . . . . . .. . . .. . . . . . . . . . . . . . . .. . . ... . . .. . . Deleting a Device . . . . . . . . .. .. .8 SP2 20 . . . . . . . . . . . . . .. . . .. .. . . . . . . . . . . . . . . . . . . . . . Assigning Connectivity to a Switch Port . . . . . . . . . .. . . . . . . . . . . . . . . Setting the VLAN for a Switch Port .. . . . . . . . . . . . .. . . . . . . .... .. . . . . .. . . . . . . . .. . . . . . . . . . . . . . . . . .. . 564 Appendix I: Managing Switches . . . . . . . . . . . . . . .. .. . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . .. . . Adding a Switch Device . . . . . .. . .. ... . . . . . . . Discovering a Device. . . . . . . . . . . ..Appendix H: Pocket PC . . . 568 LAN Switch Support List .. . . . . . . . . . . .. . . . . .. . . . . . . . . . . . .. .. .. . . . .. . . . . . . . . . . . . . . .. . .. . . . . . . . . . . . . . . . . . . . . . . . . .. .. . . . .. . .. . . . . . . . . . . . . . . . . . .. . . . Command-line Parameters . . . . . . . . . . . . . . . . . GUI Tools . . . . . . . Viewing and Setting Device Properties .. . . . . . . . . . . . . . . .. . . . . . . . . . .. . . 576 Altiris® Deployment Solution 6. . . . . . .. . . . . . . . . . . . . . 569 569 570 571 571 571 571 572 573 573 574 575 Index. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . . . . . . . . . . . . . Deployment Solution Switch Add-On (Command Line Command-line Examples . . . . . . . . . .. . . . . . . .. . . . . . .. . .. . . . . .. Options) . . . . . .. .. . . . .. . . .. . . . . . . . . . . . . . .

Sysprep configuration files. Quickly install the Deployment Agent on large numbers of Windows computers using the Remote Agent Installer. Managed computers are inventoried for software and hardware. CDs. Computer groups Dynamic insertion of database values (tokens) Computer discovery Inventory Altiris® Deployment Solution 6.8 SP2 21 . DVDs. Deploy. Example: a distribute software task could check the operating system and distribute the correct software version. the following technologies are integrated with the features of Altiris® Deployment Server® software to provide comprehensive deployment and migration: Deployment Server Feature Task-sequencer Description Management tasks provided by Deployment Server can be grouped and executed in order. or USB drives. and install other software packages. Remotely execute Visual basic and Linux shell scripts. Deployment Solution leverages a number of Altiris technologies to provide extensive management capabilities: Altiris Technology RapiDeploy® Imaging Scripted OS Installation and Sysprep Integration PC Transplant® Personality Migration Software Virtualization and Software Distribution Wise Package Studio® and Wise SetupCapture Script deployment engine Description Capture and deploy computer images using PXE. Scripts. In addition. Drag and drop a computer group onto a job and the job runs on all computers in the group.Chapter 1 About Altiris® Deployment Solution™ Altiris® Deployment Solution™ software provides a suite of tools to quickly install operating systems and software. and other values can use tokens to retrieve database values at run time. enabling you to perform complex management operations in a single job. Perform automated scripted operating system installations using sysprep. and manage SVS layers. Build and capture custom installation packages using the latest Windows Installer technology. Migrate user data and application settings to new hardware and operating systems. activate. and conditions and filters can be created based on this inventory. Computers can be organized into multiple groups to simplify job deployment.

multiple Deployment System components can be installed on the same computer. Power control.and 64-bit architecture. Management Consoles. The following diagram provides an overview of the Deployment System components: Depending on the needs of your environment. running Windows and Linux operating systems. you should become familiar with the different components of a Deployment System and how these components interact. Wake on LAN Deployment Solution Architecture Before installation. thin clients.Deployment Server Feature Extensive supported platforms Description Support for 32. Share. servers. Managed computers can be started or shutdown remotely. A single dedicated server could host your Deployment Server. Altiris® Deployment Solution 6. Database. and PXE Server. and Itanium. and schedules jobs to run on managed computers. blades. Deployment Server The Deployment Server is the central component of a Deployment System and manages the Deployment Database.8 SP2 22 . the communication between the different components.

Deployment Web Console: A Web application that provides browser-based administration.8 SP2 23 . and SVS layers you want accessible to managed computers. especially in distributed networks or when sharing large files. and jobs in your Deployment System. This share can reside on your Deployment Server or on another computer. Altiris® Deployment Solution 6. and is often replicated to different locations to provide better access.Deployment Database The Deployment Database provides the back-end datastore and stores details about the computers. groups. Management Consoles Deployment Solution provides three management consoles: Deployment Console: A Windows application that provides complete access to the Deployment System administration. such as installation programs. Deployment Share The Deployment Share stores all files. Most of the time. This console can be executed remotely using any Web browser. disk images. you do not need to interact directly with the database. and has built-in tools to manage multiple Deployment Servers.

Its features are the same as the Deployment Web Console. Linux computers can install the agent using startup scripts and other automated processes.Deployment Tab in the Altiris Console: This interface is integrated into the Altiris Console to provide integrated management with other Altiris Solutions. Altiris® Deployment Solution 6. and boot the computer into automation. or booted a computer using an installation CD. perform power control. run software and scripts. Deployment Agent This agent runs on managed computers to report inventory. you are probably familiar with running computers in a similar environment.8 SP2 24 . A Remote Agent Installer is provided to quickly install the agent on multiple Windows computers. Automation Tools Automation is the preboot environment loaded by Deployment Server to perform tasks which need to happen outside of the normal operating system. If you have ever used a disk imaging utility. Deployment Solution provides several tools to boot computers to this environment and supports several automation operating systems.

This section provides steps for installing Deployment Solution components. management.8 SP2 25 . medium and large organizations with diverse topologies and varying computer management requirements. but also includes system architecture details and discusses planning strategies to install and optimize your Deployment Solution system. and migration needs for small. The installation process is divided into the following sections: Preparing To Install (page 26) Installing (page 29) Post-Installation Configuration (page 31) Deployment Agent Installation (page 36) Altiris® Deployment Solution 6.Part I Planning and Installing Your Deployment System Deployment Solution is designed to meet deployment.

If you want to use a different account to create the database. This must be enabled before you install Deployment Solution. Open Enterprise Manager and connect to your SQL Server. To grant database rights 1. These database rights can be granted temporarily and revoked after the installation completes. you must select a custom install and provide SQL credentials instead of Windows NT authentication. Important In SQL Server 2005 TCP/IP is disabled by default. 2.NET and MDAC (page 28) Step 6: Start Microsoft’s Internet Information Server (IIS) (page 28) Step 1: Log on to Your Deployment Server Computer as an Administrator The account you use to install Deployment Solution must be a Windows Administrator and must possess System Administrator rights on the SQL server that will host your Deployment Database to install the Deployment Database.Chapter 2 Preparing To Install This sections lists the tasks you need to complete before you install Deployment Solution. Browse to Security > Logins: Altiris® Deployment Solution 6.8 SP2 26 . Step 1: Log on to Your Deployment Server Computer as an Administrator (page 26) Step 2: Create a Services Account (page 27) Step 3: Gather Automation Operating System Install Files (page 28) Step 4: Obtain a License File (page 28) Step 5: Install .

This is typically not recommended due to the lack of database management tools. The account should not be part of a group and should not posses interactive login privileges. MSDE must be installed on the same computer as the Deployment Server component. If your Deployment Database or Share will be on a different computer than your Deployment Server. 4. We recommend using the Simple Install Helper to install MSDE as this version is usable by Deployment Solution immediately after installation and requires no additional configuration on your part. Step 2: Create a Services Account Create an account to run the services and connect to the database. Click OK and verify that the role was added. Server. MSDE Database Engine Optionally. If your Deployment Database. Select the Administrator account you are using to install Deployment Solution.8 SP2 27 . it can be installed by selecting the Simple Install Helper option in the installation program. If it does not exist. and Share are installed on the same computer. we don’t recommend using an existing administrator account which might possess rights beyond those needed by Deployment Server. Altiris® Deployment Solution 6. and enable System Administrators: 5. For security reasons. Click the Server Roles tab. If you decide to use MSDE. This account is used only by Deployment Server. Example: If your SQL Server is on another computer and you are not using a domain-level account.3. The same situation applies if your Deployment Share is hosted on another computer. create a local account on that computer. create a domain-level account. or create local accounts with the same credentials on each computer hosting a Deployment Solution component. you can use the MSDE database engine instead of SQL Server. and is not tied to a user. create a local account with the same credentials on your SQL Server computer. add it. in smaller installations.

On each computer where you host a Deployment System component. Step 5: Install . Place your automation install files (BDC*. During install.NET 1. these files are detected automatically. or you can use the 30-day 10node trial license that is sent automatically when the software is downloaded.lic license file available during installation. Step 3: Gather Automation Operating System Install Files If you are ready to install an automation operating system. Browse to Local Users and Groups. Altiris® Deployment Solution 6.To create a services account 1. we recommend skipping this step and installing automation operating systems later. click Start > Administrative Tools > Computer Management.frm) in the same folder as the Deployment Solution installation program (by default. this is c:\DSSetup). the Deployment Web Console is installed automatically. Step 6: Start Microsoft’s Internet Information Server (IIS) If IIS is running during the Deployment Solution installation. you can use the integrated 7-day license. If you have purchased a license. you need to have the . Step 4: Obtain a License File For evaluation. This software is available on the Microsoft download site.7 SP1 or later.8 SP2 28 . and add a new user: The process for creating domain-level accounts is similar. 2. If you are new to Deployment Solution and are not familiar with automation.NET and MDAC Your Deployment Server computer requires .1 and MDAC 2. this can be done during the installation. This is the only account that needs to be created before you install.

These are located on your Windows installation CDs. select the Simple install. If you need clarification during any of the installation steps. and provide the services account you created when prompted. select Custom. Lets you select a different computer to host the Deployment Share. If you select to do this. Otherwise. Enable Microsoft Sysprep Support If you plan on using Sysprep to deploy standard images and scripted operating system installs. After Deployment Solution is installed. If you plan on doing this. certain values regarding the installation are stored in the local Windows registry. provide the location of the deploy.exe. This simplifies adding components or installing add-ons such as the Altiris packaged WinPE. Lets you select a computer other than the computer the install was launched from to install each Deployment System component. Running the Setup Program After you have completed the steps outlined in the previous section. Lets you install a single automation operating system (more can be added later).cab file for the operating systems for which you want to enable Sysprep. Use the administrator account you configured in the previous section to perform the installation. click Help. Altiris® Deployment Solution 6.Chapter 3 Installing Simple or Custom Install? If you plan to install your Deployment Server. you must create the share and grant the account you created in Step 2: Create a Services Account (page 27) full control before installation. Simple Install Installs to the C drive. The Simple Install Helper installs the MSDE database engine if no database is detected. Installs each of the Deployment System components (with the exception of the Deployment Agent) on the computer where the install was launched.8 SP2 29 . you have the option of enabling Sysprep support and remotely installing the Deployment Agent. and Share on the C drive of the same computer. launch setup. Lets you install multiple automation operating systems (more can be added later). Lets you select a custom name and instance for the Deployment Database. Database. Custom Install Installs to a drive other than C.

Remotely Install Deployment Agent After the installation completes.exe and selecting Component Install. A full discussion of Deployment Agent rollout is contained in Deployment Agent Installation (page 36). After building the basic image. Enable Microsoft Windows Vista Sysprep Support Microsoft Windows Vista Sysprep lets Sysprep run on a Vista Client after an Imaging event.8 SP2 30 . Unless you are familiar with Deployment Solution and the Remote Agent Installer. Vista Sysprep lets Administrators prepare generic images for deploying images to different types of systems within an environment to eliminate the support for multiple images.This can be installed later by running setup. Altiris® Deployment Solution 6. we recommend you do not install the agent at this time. you have the option of remotely installing the Deployment Agent. the Administrator can run Microsoft Sysprep on a computer to delete unnecessary information and prepare the system for imaging and distribution to other systems.

The domain join account is used to join or re-join computers to a domain after imaging or initial deployment. grant the services account full control of this share. granting the rights recommended in the following table: Rights Domain Description Grant privileges to add computer to domain. The Deployment Share read/write account is used to access this share from the automation environment. Altiris® Deployment Solution 6. These accounts are different than the accounts used by the people who are going to manage computers. Step 2: Create Domain Join and Deployment Share Accounts After installation. we recommend creating some additional accounts. and should not possess interactive login or any rights beyond what is recommended here. By default.Chapter 4 Post-Installation Configuration This section contains the tasks you should perform after installation to complete the set up of your Deployment System: Step 1: Grant Full Control of the Deployment Share to Your Service Account (page 31) Step 2: Create Domain Join and Deployment Share Accounts (page 31) Step 3: Grant Services Account the db_owner Role to Your Deployment Database (page 32) Step 4: Configure Your Deployment System (page 33) Step 5: Configure Security Settings (page 35) Step 6: Install the Deployment Agent (page 35) Step 7: Configure Automation (page 35) Step 8: (Optional) Configure PXE Server (page 35) Step 1: Grant Full Control of the Deployment Share to Your Service Account If your Deployment Share was created during the installation. These accounts are not tied to users. this folder is C:\Program Files\Altiris\eXpress\Deployment Server. Domain Join Accounts Create a separate domain-level account for each domain in which you manage computers.8 SP2 31 .

Browse to Security > Logins: 3. If the login is not listed. Step 3: Grant Services Account the db_owner Role to Your Deployment Database 1. and enable the db_owner role: Altiris® Deployment Solution 6. select the eXpress database. Open Enterprise Manager and connect to your SQL Server.Deployment Share Read/Write Account Create this account on the computer hosting your Deployment Share. Double-click the account you are using to run the Deployment services. 2. Click the Database Access tab.8 SP2 32 . add it. granting the rights in the following table: Rights File System Description Grant read/write privileges to your Deployment Share. 4.

To add domain join accounts 1. and you have a group of administrators who will have full access to deployment functionality. Provide the accounts you created in Step 2: Create Domain Join and Deployment Share Accounts (page 31). 2. click Tools > Options > Domain Accounts. To enable security You must add at least one user or group to enable security.8 SP2 33 . Click OK and verify that the change was successful. Click Start > Programs > Altiris > Deployment Solution > Console.5. In the Deployment Console. the Deployment Console can be used on your Deployment Server by any user who possesses rights to log in and run applications. you can enable security. To open the Deployment Console 1. jobs. This works well in situations where you already have policies in place to control server access. If you want to provide more granular access to configuration options. Step 4: Configure Your Deployment System The majority of tasks you perform in your Deployment System use the Deployment Console. Altiris® Deployment Solution 6. Enable Security and Add Administrators By default. and computers. Add Your Domain Join Accounts If you are using accounts to join computers to a domain you need to provide the account credentials.

Add a new user or group. click Tools > Security. 3. Enable the rights you want granted. 2. This prevents you from manually granting this access to individual administrators as they are added or removed from Deployment management responsibilities. grant the public role for the eXpress database: Altiris® Deployment Solution 6. Select a user or Group and click Rights. We recommend clicking AD Import and importing Active Directory groups. see See Securing Deployment Solution 6. 4. on the Database Access tab. For each user or group. click Tools > Security. The best way to do this is by assigning public access to the Active Directory groups containing your Deployment administrators. 2. For a more complete discussion. 1. Security is automatically enabled after a user or group is added.8 on the Altiris Knowledgebase. Browse to Security > Logins. Each additional user or group after the first are granted no rights and must be assigned rights explicitly. In the Deployment Console. Open Enterprise Manager and connect to your SQL Server. 2. as this simplifies rights management. Grant Database Rights to Administrators Each Administrator with console access must be granted public rights to your Deployment Database. Additional users or groups can be added using this same method.8 SP2 34 .1. The first user or group added is granted administrator rights. In the Deployment Console. Add a login for each user or group that will manage computers using Deployment Solution. Grant Console Rights to Administrators 1. 3.

Configure Deployment Server The Deployment Server Configuration Utility lets you configure advanced settings for the Deployment Server component. To Open the Deployment Server Configuration Utility: 1.8 Preboot Automation Environment on the Altiris Knowledgebase for an in-depth discussion of automation.8 SP2 35 . Step 6: Install the Deployment Agent The Deployment Agent needs to be installed on all computers you want to manage using Deployment Solution. Altiris® Deployment Solution 6. Step 8: (Optional) Configure PXE Server Preboot Execution Environment (PXE) is an open industry standard that enables computers to boot remotely using a network card. or restart the Deployment Server services. and configure additional options. Click Start > Programs > Altiris > Deployment Solution > Configuration. You do not need to perform any configuration at this time. See Deployment Solution 6. Step 7: Configure Automation If you plan on imaging computers or deploying computers using scripted installs you need to configure your automation environment. update the services account. start. You can stop. See Deployment Agent Installation (page 36). though you should become aware of the configuration options provided.8 on the Altiris Knowledgebase for an in-depth discussion of Deployment Solution security. Step 5: Configure Security Settings See Securing Deployment Solution 6.

About the Deployment Agent The Deployment Agent can be installed in the production environment of all the computers you want to manage.Chapter 5 Deployment Agent Installation The Deployment Agent runs on managed computers to perform local management tasks as directed by Deployment Server. Installing the Agent There are two standard methods to install the Deployment Agent on multiple computers: Using the Remote Agent Installer (Windows XP) (page 37) Using a Script. or ADLAgent refer to the specific executable.8 SP2 36 . you should install the Deployment Agent on managed computers. Without installing the Deployment Agent. There are three versions of the Deployment Agent: DAgent . UNIX. The agent simplifies these tasks by automatically restarting the computer and controlling when to boot the embedded partition. Mac References in this document to the Deployment Agent refer to all versions. references to DAgent. Altiris® Deployment Solution 6. or boot media to perform some tasks. you can still boot computers to automation using PXE.Windows Vista AClient . Additionally.Windows XP and previous ADLAgent . Solaris. but it is not required. or boot media. AClient.Linux. the Deployment Agent is automatically included in each of the automation boot configurations you create using PXE. Linux and Mac agent see Operating System and Platform Reference (page 249). automation partitions. embedded partitions. or Manual Installation (All Platforms) (page 37) For Additional details on the Vista. E-Mail Link. Some of these tasks include: Software installations SVS layer management Script execution Remote control Inventory and configuration If you plan on doing more than computer imaging or scripted installations.

works for Linux and Unix computers. Does not work on Vista. Step 4: Run the Remote Agent Installer In the Deployment Console. In Windows Explorer. Using a Script. Disadvantage: Requires Local User rights on each computer. click Tools > Folder Options > View tab. To determine whether you have sufficient rights. Step 1: Disable Simple File Sharing on Windows XP 1. After the agent is deployed. If you need clarification during any of the installation steps. click Tools > Remote Agent Installer. Disadvantages: Not as automated as the Remote Agent Installer. Step 2: Allow File and Printer Sharing in Windows XP SP2 Firewall 1. If you can access this share you have sufficient rights. 2. troubleshooting will likely require direct intervention. Step 3: Get Local User Rights (admin$ Share) To initially install the agent on managed computers. 2.8 SP2 37 . or any other account with local rights. you no longer need access to this account. You need access to this account only when performing the one-time agent installation. The remaining installation methods are grouped together because they perform the same functions: Execute the agent installation while providing a configuration file for a silent install. you need an account with Local User rights. click Help. so either use your domain administrator. Manage the security settings for the Windows firewall to add an exception for File and Printer Sharing. monitor installation status in real time. and retry failed installations. a domain account with local user rights. Does not work with simple file sharing in Windows XP. E-Mail Link. Clear the Use simple file sharing check box in the Advanced settings section. Altiris® Deployment Solution 6.Using the Remote Agent Installer (Windows XP) Advantage: Browse your network to quickly select computers. Open the Security Center from the Windows Control Panel. or Manual Installation (All Platforms) Advantages: You do not need Local User rights to install if you have individual loggedin users initiate the install. browse to: \hostname\admin$ Replacing hostname with the name of the computer where you want to install the Deployment Agent.

Step 3: Run the Installation Program On each computer. Configure each file and place a copy with the agent installation program. or send the link in an email message. Place it in a startup script.inp file.Step 1: Provide Users Access to the Agent Installation Program The agent installation programs are stored in the Agents folder on your Deployment Share. Windows computers installing AClient use aclient.8 SP2 38 . we do not recommend granting any users direct rights to your Deployment Share. for Windows computers. you can use the Force Deployment Agent Settings on New Computers feature to reduce the amount of configuration you need to perform in the input file. 3./adlagent To run this. Details on the options are contained within each file and are also described in the Deployment Solution Reference Guide. 2. you can install the 32-bit agent on both hardware types. you can specify an input file containing configuration settings. Linux and UNIX computers installing ADLAgent use adlagent. Altiris® Deployment Solution 6. Copy this file to a location that your users can have access. the agent receives global settings you have specified when it connects for the first time. especially if you are storing software or computer images on this share.and 64-bit computers. In the Deployment Console.inp -install or . ensure you use a text editor that properly handles UNIXformat line endings. For security purposes.conf. When modifying adlagent. Tip If you are managing 32. To force agent settings on new computers: 1. you need to run a command similar to the following: \myshare\AClient.conf. you could: Have users copy and paste it into the Windows Run dialog. Execute it remotely using Telnet or SSH. the 32-bit computers automatically update to the 64bit version. After connecting. Click Change Default Settings to define default settings. Step 2: Create the Input File for a Silent Install To configure new computers using a silent install.exe aclient. When this is enabled. Click the Agent Settings tab and select the Force new agents to take the default settings check box. Optionally. click Tools > Options.

See the release notes on the Altiris Knowledgebase for specific information on Agent upgrades.Agent Auto Update The Deployment Agent has the ability to update itself to a newer version automatically.8 SP2 39 . This greatly reduces the effort required when upgrading. and is set to update computers in batches to prevent network overload. Troubleshooting See the following article on the Altiris KnowledgeBase: 18248 Remote Agent Installer Fails for AClient Additional articles can be found by searching the Altiris KnowledgeBase. Altiris® Deployment Solution 6.

you must implement a way to boot computers into this environment. This section provides the information you need to configure a boot method. scripted installs. To do this. a managed computer is booted into an environment where it can communicate with your Deployment Server to perform tasks. or execute certain scripts. and select an operating environment for automation tasks. This preboot environment is called automation.Part II Booting Computers to Automation Deployment Solution has the ability to perform work on computers before the normal operating system loads. In order to perform image capture and deployment.8 SP2 40 . Altiris® Deployment Solution 6. including PXE.

this section helps you decide which works best for your environment. In order to set up automation. you must select a method to boot computers to automation and decide which operating to use in the automation environment. you must make the following decisions: Which Automation Boot Method Should I Use? (page 43) Altiris® Deployment Solution 6. this pre-boot environment is called the automation environment. Production The normal operating system of the computer. If you have ever used a disk imaging utility.8 SP2 41 . other tasks. Production tasks include software installation and personality capture. or booted a computer using an installation CD. or booting into “automation mode”. The following table contains a list of Deployment Solution tasks and the environment in which they execute: Production Tasks Distribute Software Capture Personality Distribute Personality Get Inventory SVS Copy File to Modify Configuration Power Control Run script Automation Tasks Create Disk Image Distribute Disk Image Scripted OS Install Run script In order to manage computers in automation. Several of the tasks you perform to manage your network can be completed in the production environment. must be performed before the operating system boots.Chapter 6 What is Automation? Deployment Solution uses two modes to manage computers: Automation Automation is to the pre-boot environment loaded by Deployment Server to perform tasks which need to take place outside the normal operating system. In Deployment Solution. you are probably familiar with running computers in a similar environment. primarily imaging. However. Deployment Solution provides support for a broad range of boot methods and automation operating systems.

Which Automation Operating System Should I Use? (page 46) Altiris® Deployment Solution 6.8 SP2 42 .

At the same time however. or floppy). it is assigned an initial deployment job. especially on several computers simultaneously. you could use the initial deployment features of PXE for arriving computers and install an automation partition in case you need access to automation at a later time. automation partitions. PXE also provides an advantage if you need to use multiple automation operating systems in your environment. USB Device. When this unknown computer contacts the Deployment Server. PXE can boot computers regardless of the disk configuration or operating system installed. embedding the automation operating system on the disk is faster and significantly reduces network traffic. since the entire image must be downloaded each time you run an automation task. PXE provides a number of advantages. The computer is now ready for delivery with minimal effort. Example: the receiving department of your company could have PXE enabled on their subnet. If you often run automation jobs. Altiris® Deployment Solution 6.Chapter 7 Automation Boot Methods Which Automation Boot Method Should I Use? Deployment Solution supports a broad range of methods to boot computers into the automation pre-boot environment: PXE. USB device. this can be a disadvantage if you are using an operating system with a large footprint. different operating system environments can easily be assigned to different tasks. and contains the following: PXE (page 43) Automation Partitions (page 44) Boot Media (DVD/CD. When a new computer arrives. install additional packages. which enables you to remotely deploy an image to a computer which has no software installed. This section provides an overview of the available boot methods to help you select the method that works best for your environment. a computer can communicate with your DS PXE server to receive automation jobs. 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.8 SP2 43 . such as Windows PE. Since the image containing the automation operating system is downloaded when a task is executed. or boot media (CD/DVD. It is also possible to use PXE for initial deployment and install an automation partition as part of the deployment. especially when you are using the initial deployment features of DS. In this case. and power off the computer. which could image the computer with the corporate standard image. Floppy) (page 44) PXE Pre-boot Execution Environment (PXE) is an industry standard developed to boot computers using a network card. and doesn’t require any files or configuration settings on a client. After PXE boot is turned on in the BIOS.

it might be a good choice. This partition contains the automation operating system and the files needed to contact your Deployment Server. USB Device. Deployment Solution is designed to manage computers remotely. this might limit you to DOS for all automation tasks on a particular managed computer. Although multicast imaging is supported in WinPE and Linux. it is often difficult to schedule a job and coordinate booting the managed computer to the right environment at the right time. Optionally. Floppy) Generally. the time needed to create and restore images is greatly reduced and network traffic is significantly reduced as well. If you have tools that are supported only in DOS. called a hidden partition. they require an existing partition on the drive. and they must be manually installed from a disk on Linux and Unix operating systems. However. you can create a different type of automation partition. yet it still enables you to boot into automation remotely. might be the fact that only one automation operating system can be installed to a managed computer that is using an automation partition. but you cannot use multicast to boot these computers. multicast PXE booting is not provided in WinPE and is not supported in Linux. but still provides access to the automation environment without physical access. If you assign a job which Altiris® Deployment Solution 6. even in the automation mode. The biggest advantage to an embedded partition is that it does not require PXE. Automation Partitions An automation partition is a sector of your hard disk drive partitioned and managed by DS. and must be present on each managed computer. This enables your PXE server to simultaneously boot up to 100 computers in a single session to perform automation work. the biggest drawback to boot media is that it forces you to physically access the managed computer.This configuration does not require PXE in your general network environment. Example: An imaging operation first captures configuration details from the production operating system before booting to automation to capture the image. Boot media has some configuration limitations though. Since the image is stored locally. if you have employees with the ability and access to boot their own computers using disks you provide. to store an image (or other files) locally. Because of this. Another drawback. if you are managing smaller numbers of computers or do not plan to access the automation environment often. an imaging task can be multicast. this could also be a good solution.8 SP2 44 . Boot Media (DVD/CD. PXE provides an additional advantage: multicast boot. Also. When using the DOS automation environment. The biggest disadvantages to embedded partitions are that they consume space on the drive. This provides advantages in environments where computers need to be re-imaged often or in environments where there is limited bandwidth or network connectivity. and several tasks and jobs require access to both the production operating system and the automation environment. depending on your configuration. That means that after each computer has booted to automation. After imaging. this configuration is restored. Automation partitions have an additional advantage in some configurations.

the BIOS will most likely continue to boot to automation until the boot media is removed. execute the necessary commands. To avoid these issues. the boot disk must be present at the right time to boot automation. but it does not require network access. the boot media must be re-inserted. In this circumstance. and the image on bootable physical media. or a subsequent job.requires booting into automation mode. They boot a computer. This works especially well when managing thin clients or other computers where all necessary files can fit on a single disk or USB device. Altiris® Deployment Solution 6. the remote management capabilities of Deployment Server are not being used. If this job. requires automation access again. If a complex job requires access to the production environment during this time. some customers load the automation operating system.8 SP2 45 . and provide the required image files. the RapiDeploy imaging executable. so the process is more manual.

boot to Windows PE or Linux to perform an imaging task. All of the DS automation tools support these operating systems.8 SP2 46 . DOS typically requires only around 1 MB of space. and so on). The largest roadblocks most companies face when using DOS are access to drivers that support modern hardware. so you can perform DS automation tasks in any operating system (Linux computers can be imaged from DOS. You might even use two automation operating systems for different tasks within the same job. When you set up your test environment. When performing an automation task on multiple computers.Chapter 8 Automation Operating Systems Which Automation Operating System Should I Use? After you have selected a method to boot computers into automation. The following sections contain an overview of the automation operating systems: DOS (page 46) Windows PE (page 47) Linux (page 47) Although you can use these environments to perform a wide-variety of management using scripts and other tools. DOS still performs well for several tasks though. support for these environments is limited to the task performed by Deployment Solution. Example: you might use a vendor-supplied tool to perform a BIOS update in DOS. In the past. you need to decide which operating system you want to use. which enables large numbers of managed computers to boot DOS simultaneously. This section provides an overview of the available automation operating systems so you can find an environment (or environments) that suit your needs. the PXE server can use multicast to boot automation. MS DOS was the only supported option. DOS provides an additional advantage in a PXE environment. though new technologies have emerged that might better suit your environment. and security concerns. Altiris® Deployment Solution 6. An important thing to note is that the automation environment you use is not constrained by the production operating system on the computer. MS DOS. and FreeDOS. and can be a good choice if you have the proper driver support. you might want to run automation jobs in multiple operating systems to see if one performs better in your environment. Linux. such as Windows PE. Windows computers can be imaged from Linux. DOS DOS is still used often today as a pre-boot environment. Deployment Solution now supports Windows PE.

Linux Linux provides an alternate pre-boot environment to DOS or Windows PE. Altiris® Deployment Solution 6. and its licensing requirements. 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. Many vendors provide gigabit and wireless drivers for Linux that are not available in DOS. and generally more functionality. including better driver support (Windows PE uses the same drivers used by the other modern versions of Windows). Windows PE provides several advantages over DOS. which causes increased boot time.8 SP2 47 . especially when booting over the network using PXE. Windows PE typically requires around 150 MB of space. clients using Windows PE require at least 256 MB of RAM.Windows PE Windows PE (Windows Pre-boot Environment) is the next generation boot environment for Windows computers. The biggest drawbacks are its size. increased speed. but you need updated driver support. Additionally.

Windows 2003 Server SP1 installation CD or Windows Server 2003 x64 installation CD.altiris.Chapter 9 Installing and Configuring Automation This section explains: Configuring Automation Operating Systems (page 48) Configuring Automation Boot Methods (page 51) Deploying Automation to Managed Computers (page 52) Configuring Automation Operating Systems The following sections guide you through installing and configuring the automation operating systems supported by Deployment Solution. Windows PE is available to volume licensing customers through Microsoft.org.freedos. FreeDOS Altiris® Deployment Solution 6. Click the Linux and FreeDOS Automation Environment link and save the file. Browse to the downloaded file when prompted during the installation. MS DOS A Windows 98 installation CD (Windows 98 SE is preferred).aspx. Obtaining and Installing Windows PE. The FreeDOS preboot environment is contained in the same file as the Linux preboot. Currently. or when adding preboot operating systems using the Boot Disk Creator. which is available in the Deployment Console by clicking Tools > Boot Disk Creator. and the proper licensing to use this on the intended computers. The following files are required to install the listed automation operating system: WindowsPE Windows PE 2005 installation CD. Files are copied from the win98 folder from this installation CD. or DOS Automation operating systems are installed using the Boot Disk Creator.mspx for information on obtaining Windows PE. See http://www.8 SP2 48 . Linux The Linux 32 and 64-bit and FreeDOS preboot environments are available on the Deployment Solution for Clients or Servers download page at http:// www. Linux. For additional information on FreeDOS visit www. see the Linux instructions for details.com/licensing/ programs/sa/support/winpe.microsoft.com/Download.

or to select configurations only. Adding Additional Files Occasionally. These files can be added to every automation configuration of a specific type. you might need to make additional files available within an automation environment. For complete details on this process see the Boot Disk Creator help. 3. such as utilities or mass storage drivers.8 SP2 49 . This is determined by the location you add the files in Boot Disk Creator: Altiris® Deployment Solution 6. click Tools > Boot Disk Creator. In Deployment Console. providing the files listed in the previous table when prompted.To install 1. In Boot Disk Creator. click Tools > Install Pre-Boot Operating Systems. 2. Click Install and complete the wizard.

oem file. Right-click and select add > Folder. This is done by creating a folder named “. create the following path: i386\system32\diskdrivers Within the diskdrivers folder.8 SP2 50 . 3. or a specific Boot Disk Creator configuration. Adding Mass Storage Drivers for Windows PE 1. 1. and at least one *. 2.sys file.oem are included. Adding Large Files to a Linux Boot Configuration Linux automation is typically loaded into RAM. The diskdrivers path is for adding mass storage drivers. create the necessary folders to contain your drivers. If you need to access larger files locally (such as a disk image).). there is a size constraint on the files that can be included. letting you access files that are too large to fit on the ramdisk. Altiris® Deployment Solution 6. 2. and that the [defaults] section references the proper device driver (some textsetup. The folders you add should contain a txtsetup.” (do not include the quotes. just . and possibly additional files. and the proper device must be specified in the [defaults] section).oem files might support multiple devices and drivers. Name this folder “.” in the root of your boot configuration. You must also ensure that any sub-folders specified by txtsetup. If you are adding different driver types. Boot Disk Creator provides a mechanism to mount a folder outside of the ramdisk. you might need to modify this path. Using this add folder command.The following example provides an overview of this process. Due to limitations on the amout of RAM available on most computers. Select either the Windows PE Additional Files folder. Right-click your configuration and select New > Folder.

Setting up and configuring PXE is covered in detail in a separate document. This includes a shutdown command issued from DS. USB device. After the automation tasks run. and requires additional components on your DS server. Depending on the operating system. but to provide room to store images and other files. Hidden Partition Altiris® Deployment Solution 6. DS sends a message to the client computer to restart in the automation environment.8 SP2 51 . a status message is sent to the Deployment Server indicating that all work is complete. This partition is not normally viewable in the production operating system. The Deployment Server sends a message that the client computer should reboot back to the Production environment (the MBR is restored when using automation partitions). the Deployment Server sends the client computer its assigned jobs and tasks.img Configuring Automation Boot Methods When pre-boot tasks need to be performed. Floppy) Configuring PXE PXE is a server-based technology. 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 operating system. Example You can place a disk image and the rdeployt executable in this folder. create a boot DVD. using a command similar to the following: /mnt/atrsboot/rdeployt -md -f/mnt/atrsboot/[imagename]. A larger partition installed on the hard drive of a managed computer to contain not only the automation operating system. The following sections guide you through the process of setting up PXE. an automation partition. After a connection is established. and possibly other computers. the automation environment is loaded from PXE. or media to boot your computers into the automation mode: Configuring PXE Configuring Automation Partitions Configuring Boot Media (DVD/CD. or from boot media. the size varies from 5 to 200 MB (you can specify the size when the partition is created based on recommendations). The deployment agent now contacts the Deployment Server. PXE in Deployment Solution. automation partitions. and a modification to the MBR if using an automation partition. and restore the included image without network access.Files placed in this folder are mounted in Linux automation at /mnt/atrsboot. After the managed computer reboots.

or DOS. but the media must be used each time you want to access automation. Linux. automation partitions. This is different than using boot media to access automation. Install the automation operating systems you want to use. while PXE uses a configurable menu to provide boot options. or floppy disks.An embedded partition doesn’t create an actual disk partition. or boot media configurations and deploy these configurations to managed computers. CDs. Altiris® Deployment Solution 6. USB device. The partition is listed as a non-DOS partition. The target drive must have an existing partition before an embedded partition can be installed. with each option on the PXE menu linked to a specific automation configuration. Boot media boots a managed computer to automation without leaving any files on the computer. or floppy. Using boot media to access automation doesn’t leave any files on the computer. 2. or installed from a CD. Floppy) Creating and using boot media is a straightforward process. you may want to quickly re-image to ensure that the next visitor finds the computer in good working order. PXE configurations are created using the PXE configuration utility. a hidden partition enables you to quickly restore an image without needing access to a high bandwidth network. USB device. After the visiting person is done using this computer. but this partition is hidden from normal view within the production system. and can be installed to DVDs. such as those in a test lab or provided for general use (such as a hotel or a library). though it is still viewable by FDISK or by an administrator. USB devices. Configuring Boot Media (DVD/CD. Deploying Automation to Managed Computers Automation partitions and boot media configurations are created using the Boot Disk Creator utility.8 SP2 52 . Hidden partitions are very useful for computers which are imaged often. as explained in Obtaining and Installing Windows PE. it reserves space on an existing partition by marking the sectors on the disk as unusable. The wizard is accessed by clicking File > New configuration. After the work is completed. Create a new configuration. This difference is due to the way in which the automation operating system is deployed to the managed computer. the MBR is restored to the previous configuration. the Master Boot Record (MBR) of the computer is modified to boot to this hidden partition. In Boot Disk Creator. In these circumstances. This section contains guidelines to create PXE. later the partition is used to perform tasks. because the automation partition media is used once per computer to install. A hidden partition creates an actual disk partition. Using Automation Partitions or Boot Media 1. When a computer using an automation partition is assigned jobs. Automation partitions can be installed using an installation package deployed from DS (windows only). Boot media is created directly from the Boot Disk Creator utility. Automation partitions and boot media use install packages or boot disks.

the computer executes any automation work previously scheduled. so the media must be used each time you need to access automation. USB device. or waits for work to be assigned. After booting. you need to use a CD.This configuration contains the automation operating system files. See the Boot Disk Creator help for additional details. After that. or DOS. or floppy from Boot Disk Creator. which is launched automatically after you create a configuration. This process is executed once per device. The Create Boot Disk wizard provides three options: Creates an executable. None of these files are installed to the managed computer. Install the automation operating systems you want to use. or configures a CD. 2. Select this if you are using automation partitions. as your Deployment Server is not contacted in this scenario. This is useful if you have management task to perform that doesn’t require interaction with DS. Create an automation boot disk Configures a CD. This is done using the Create Boot Disk wizard. You can also uninstall an automation partition using an install package. USB device. complete the wizard. or floppy with the files necessary to boot to a prompt. USB device or floppy because no executable is provided for this platform. and other settings which control how the managed computer communicates with your Deployment Server. Using PXE 1. or configure a CD. 3. Select this if you are using boot media to boot computers to automation. as explained in Obtaining and Installing Windows PE. After selecting how you want to install automation. Altiris® Deployment Solution 6. create a new menu item to correspond to the automation configuration you want to install. or floppy with the files necessary to boot a computer to automation mode. or floppy to install the automation environment. USB device. Create an automation partition install package 4. Linux. This configuration does not specify how this automation configuration is installed. For managed linux computers. IP address of your server. In the PXE Configuration utility (Start > All Programs > Altiris > PXE Services > PXE Configuration Utility). Create a network boot disk Configures a CD. None of these files are installed.8 SP2 53 . the computer uses the files from the automation partition. USB device. network drivers.

When this option is selected from the PXE menu. This wizard is identical to the wizard used when creating configurations for automation Partitions or boot media. the computer boots to the production operating system. Altiris® Deployment Solution 6. the job is performed. Click Create Boot Image to launch the configuration wizard. None of these files are saved on the managed computer.8 SP2 54 .3. the necessary files are loaded. they are downloaded each time the computer boots to automation. Provide any additional configuration options and click Save. 4.

this pre-boot state is called the automation environment. After this computer is assigned to a user. This limits the extent of the PXE environment. Altiris PXE Server now boots the computer into the automation environment indicated in the Deployment Solution job automatically. Deployment Solution leverages PXE to provide the following advantages: When a managed device needs to boot into automation. PXE can perform an initial deployment of a new system by checking to see if a computer exists in Deployment Solution. PXE is not used in the normal production environment.Chapter 10 Setting Up the Altiris PXE Server What is PXE? Preboot Execution Environment (PXE) is an open industry standard which enables computers to boot remotely using a network card. Many organizations use PXE only on a subnet in a receiving department to deploy corporate images and initial configuration of new computers. enabling you to remotely configure all PXE servers in your network. but prevents you from accessing the automation environment to capture images and perform other automation-only tasks. and has several other advantages such as image multicasting and tight Deployment Solution integration. In Deployment Solution. Other companies which often use automation select PXE because it leaves no footprint on the managed computer. and WinPE are currently supported as pre-boot operating systems. An advanced.8 SP2 55 . Deployment Solution restarts the computer and notifies the Altiris PXE Server. and DOS. Altiris® Deployment Solution 6. Deployment Solution: Automation Preboot Environments. PXE uses standard network protocols to establish a communication channel between a computer and an Altiris PXE server during the boot process. An overview of the automation boot methods and environments is contained in a separate document. Linux. an Altiris PXE server sends an execution environment to the computer so that work can be performed in a pre-boot state. Using this channel. All PXE configuration is done using the PXE Configuration Utility from the Deployment Solution console. tightly integrated PXE environment is provided with Deployment Solution. Why Use PXE? PXE is used in Deployment Solution 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.

making it unnecessary for you to individually configure each PXE server. MTFTP The PXE Manager service interacts with Deployment Server. Altiris PXE Server Provides the PXE listener and proxy DHCP to respond to PXE requests and send the location of bootstrap files. The following table contains an overview of the PXE services: Service PXE Manager Description Provides all boot options and configuration settings for each Altiris PXE Server in your environment. This shared configuration is inherited by all Altiris PXE Servers in your environment. Configures. This section contains the following topics providing an overview of PXE in Deployment Solution: PXE Services and Architecture How PXE Works PXE Services and Architecture PXE services use a tiered-architecture which enables you to provide global settings and boot options shared across all Altiris PXE Servers. Boot options and PXE settings can be applied to a shared configuration.8 SP2 56 . and stops the additional PXE services on the Altiris PXE Server. and the PXE config utility to perform centralized PXE management: Altiris® Deployment Solution 6. Sends bootstrap files to managed computers using TFTP. The PXE Manager Service is installed on your Deployment Server regardless whether or not you have also installed an Altiris PXE Server.Regardless of how broadly you implement PXE. so you can override settings and add additional boot options as needed. PXE Config Helper Interfaces with PXE Manager to receive data and configuration. Each Altiris PXE Server still has its own specific configuration. override configuration and expand boot options on a local level. Interfaces with the PXE Config Utility to replicate data and apply PXE configuration. New services have been provided to replicate settings and data automatically. starts. Deployment Solution provides tools and services to simplify management of PXE in your environment. Manages all communication between your Deployment Server and your Altiris PXE Servers. PXE Helper service.

On each individual Altiris PXE Server. Clients connect directly to these services during the PXE boot process: How PXE Works Before a computer can boot over a network. and the location of an Altiris PXE Server to contact for boot instructions. started and stopped by the PXE Config Helper service. it needs two things: an IP address to communicate. These services are configured.8 SP2 57 . The following sections outline the PXE boot process: Part 1: DHCP Request and PXE Discovery Part 2: PXE Bootstrap Altiris® Deployment Solution 6. the Altiris PXE Server service and the MTFTP service are installed to perform the work of an Altiris PXE Server.

the IP address they offered is reclaimed. When a packet is recognized. During this process. If no automation work is required. Altiris® Deployment Solution 6.1 file.255. When the client has chosen a target DHCP server.255) to port 67 on its local physical subnet to discover a DHCP server. the Altiris PXE Server monitors the wire for DHCPREQUEST packets with an option 60 (PXE client).Part 1: DHCP Request and PXE Discovery Request and Receive an IP Address Initially. PXE Option 60 DHCP lets clients to receive options from the DHCP server indicating various services that are available on the network. It creates a RAM disk and manipulates the BIOS interrupt vectors.8 SP2 58 . This file copies the . If the request is intended for a different server. Any available DHCP servers respond with a broadcast DHCPOFFER packet indicating their server IP. so this is transfered to the client. If the Altiris PXE Server is located on the same server as DHCP. If there is work to do. At this point.0 file functions as a bootstrap loader.1 file byte by byte into the newly created RAM disk. A number of standard and custom options are available that can convey a vast amount of information to DHCP clients. the boot agent directs the execution of normal DHCP operations by broadcasting a DHCPDISCOVER packet (255. The . and a DHCPACK with option 60 containing an Altiris PXE Server. the Altiris PXE Server does not respond to the client and it boots normally. The DHCPREQUEST also contains option 60 to identify the client as a PXE client. it broadcasts a DHCPREQUEST packet that includes its MAC address and the IP address of the selected DHCP server. Most of the time. the correct boot option has already been selected by the Deployment Server.0 and a .255. Option 60 deals specifically with PXE related services. the client has received a DHCPACK containing an IP address. both are contained in the same DHCPACK packet. Contacting the Altiris PXE Server All DHCP servers examine the DHCPREQUEST packet. interrupt structures and hardware information tables to make the RAM disk function exactly like a typical floppy disk. After the selection is made. Both PXE clients and servers use option 60 to convey specific information about the PXE services they need or are providing. After this request. the client requests the necessary boot files using MTFTP. the Altiris PXE Server responds with its address using a DHCPACK with option 60. Part 2: PXE Bootstrap The client is ready to contact the Altiris PXE Server for boot files. the client’s MAC address is used to find any pending automation work in Deployment Server. This consists of a . The DHCP server providing the accepted offer supplies a DHCPACK packet to the client to acknowledge the client’s receipt of its IP. clients are provided with a boot menu containing all boot options that the Altiris PXE Server can provide.

The . in the following sections: Enabling PXE on Managed Computers Installing and Configuring DHCP How Many Altiris PXE Servers Do I Need? Installing Altiris PXE Servers Altiris® Deployment Solution 6. The following diagrams contain a basic outline of this process: PXE Planning and Installation This section contains an overview of the PXE deployment process.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.8 SP2 59 .

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. In these configurations. and configure this component separately. a Wake on LAN signal is sent to the managed computer if the device is disconnected from Deployment Server when a job is scheduled to start. multicast boot is not available. A single Altiris PXE Server on a gigabit network can capture and deploy several times as many images over a period of time than even multiple servers on a slower network. the more work a single Altiris PXE Server can do. Usually a single Altiris PXE Server in a specific location is enough if you either use multicast to deploy images or spread out your image capturing jobs to be in line with the capabilities of your server. the deployment share can be mirrored to a local server. Installing and Configuring DHCP DHCP is an integral part of the PXE process. and not consume any more resources than it would while deploying a single image. Altiris® Deployment Solution 6. Network Speed Since the majority of the resources on an Altiris PXE Server are used for transferring files over the wire. See PXE Redirection (page 63) for an example of this type of configuration. How Many Altiris PXE Servers Do I Need? Number of Client Connections Altiris PXE Servers do not typically require a lot of resources. Additional Altiris PXE servers can easily be added if necessary.8 SP2 60 . the faster the network. and images are usually taken from and restored to local file servers. If this is enabled. install. This is done using the PXE Configuration Utility. Physical Layout of your Network Your PXE configuration might be set up according to the physical layout of your network. It is also a good idea to apply the latest BIOS updates. you need to configure how your Altiris PXE Servers interact with the DHCP server. you must obtain. After DHCP is set up and your Altiris PXE Servers are installed. A DHCP server is not provided with Deployment Solution. By using multicast. Deployment Solution also supports Wake on LAN to power on managed computers remotely. and must be installed and configured in order to use PXE. If you are using WinPE or Linux however. especially if your network card is integrated on the motherboard. it might make sense to install an Altiris PXE Server at each location to reduce traffic and resolve routing issues (see PXE Request Routing). a single Altiris PXE Server can deploy a DOS boot image to up to 100 computers at a time. If you have three offices in different locations.

Altiris® Deployment Solution 6. You can install an Altiris PXE Server at the same time as you install Deployment Solution. If both PXE and DHCP services are located on the same computer. but any forwarded broadcast traffic targets specific computers. An Altiris PXE Server can be installed on your Deployment Server. Installing Altiris PXE Servers After you have determined the PXE needs of your network.PXE Request Routing PXE clients use broadcast packets to find DHCP and PXE services on a network. and DHCP packet forwarding is enabled. or you need to install an Altiris PXE Server on each subnet. they are configured using the PXE Configuration Utility. or as a standalone server. on another server in your network (such as a file server). or you can install one later by running the installation program and selecting the add additional components option. the routing of multicast traffic must be considered. These settings include timeout values. If these services are located on different computers. The source subnet experiences the broadcast. Configuring PXE Settings All PXE configuration is done using the PXE Configuration Utility. you shouldn’t have any problem transferring broadcast packets. and multicast packets (MTFTP) to transfer files. Once the broadcast issues are resolved. you must to determine where to install these Altiris PXE Servers. The PXE config utility is used to create and modify two things: Global and local configuration settings. See the following section.8 SP2 61 . Please consult the documentation provided by your router vendor for additional information on packet forwarding. After these servers are installed an running. additional configuration might be required. on your DHCP server. You can also use a combination of these (example: an Altiris PXE Server on your Deployment Server and your DHCP server). Enabling a router to support DHCP is common. ensure your router configuration lets DHCP traffic to access the proper ports and IP addresses for both DHCP and Altiris PXE servers. These packet types can present challenges when planning a PXE deployment because most default router configurations do not forward broadcast and multicast traffic. Because of this. The actual installation process is straightforward. routers can be configured to support multicast traffic between PXE Clients and Altiris PXE Servers. If you are going to forward packets. either your routers need to be configured to forward these broadcast and multicast packets to the correct server (or servers). replication and logging options. and so on. Routers generally forward broadcast traffic to specific computers. Multicasting leverages significant efficiencies in transferring files but also introduces challenges similar to broadcast packet forwarding. Like the broadcasting solution.

If no other connections are attempted. network and other drivers. If you have DHCP installed on your Deployment Server but it is not active. This is changed by selecting option 3. All Altiris PXE Servers inherit the shared values unless they are overridden on the local server. see the help for the PXE Configuration Utility.8 SP2 62 . especially in security-conscious business and government settings not willing to risk network boot ups unless safeguards are in place (example: it is important ensure that the boot image comes from a trusted source and has not been tampered with in transit). Boot Integrity Services (BIS) addresses these security needs. You can also designate and enforce which boot images can be installed on selected groups of platforms. PXE Settings Shared vs. This timeout only applies if someone else is attempting to launch PXE Configuration. If you are using a 3rd party DHCP server which automatically sends the client 60 message. only one instance of PXE config can connect to PXE manager at any given time. Boot Integrity Services PXE is potentially vulnerable to hackers. For complete details. Deployment Server might still attempt to communicate with that instance. you want option 1. 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. If you attempt to launch PXE Configuration when another instance is running. Each boot option corresponds to a specific configuration which includes an operating system. and so on. you receive an error.Boot options. utilities. Local Deployment Solution provides a PXE settings hierarchy enabling you to provide shared and local PXE configuration values. To ensure your changes are not overwritten by another instance of the PXE Configuration Utility. select option 2. To prevent you from being completely locked out for extended periods (example: an instance is inadvertently left open on another computer). DHCP Server Options For most circumstances. BIS can validate (before executing a boot image) that the image came from a trusted source and was not tampered with en route. Altiris® Deployment Solution 6. the timeout is never enabled and your session remains active. Session Timeout The PXE configuration utility connects the PXE Manager service on Deployment Server. mapped drives. Using BIS firmware built into the client computer. This section contains a brief overview of selected PXE configuration and boot options. a timeout has been added which terminates a connection after 30 minutes of inactivity after someone else attempts to connect.

on each Altiris PXE Server.8 SP1 is installed all references to BIS are removed. In the released version of Deployment Solution 6. 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. and one office in Alberta. while local boot options are available on a specific Altiris PXE server. Shared vs. and set the schedule. and stores captured images on alb1\images. each office has a local Altiris PXE Server. Consider the following example: You manage computers in three locations: Two offices in Ontario. To limit transfer between each site. there are very few computers that support BIS.5 with active BIS support. This is due to the role redirection plays in your PXE environment. Each boot option has a corresponding automation operating system. You could go ahead and create three global configurations and three different jobs. If you are currently running DS 6. select a PXE boot option. but that is confusing and could potentially cause problems if the wrong selection is made. The Alberta office uses a mirror of the deployment share on alb1\eXpress. Shared boot configurations are available on all Altiris PXE Servers. two of the three global configurations could potentially cause problems (they are mapped to drives in remote offices). network drivers. Local Deployment Solution provides a PXE boot option hierarchy enabling you to provide shared and local PXE boot options. Boot Integrity Services (BIS) Removal With the advent of Deployment Solution 6. they are always specific to an individual Altiris PXE Server. The two Ontario offices use the ont1 and ont2 servers respectively. To avoid Altiris® Deployment Solution 6. once a month.Deployment Server supports the BIS technology.8 SP2 63 . and a file server with a mirror of the deployment share.8 and 64-bit support the Boot Integrity Services (BIS) could no longer be managed. you are going to have problems. Boot Options Boot options are the boot configurations provided to a client by an Altiris PXE Server. If you select the same PXE boot option for each office.8 the BIS configuration was removed from PXE Config utility. If you took this route. BIS will not work unless the physical computer supports it. In SP1 the BIS CDSA database has been removed and is no longer supported. At the present time. Redirection settings are not available globally. please remove the BIS support before upgrading to Deployment Solution 6. Hold on. PXE Redirection Lets you redirect a global PXE menu option to a local PXE menu option.8 because when Deployment Solution 6. This enables clients at each location to contact the local Altiris PXE Server to boot and use the local deployment mirror to access the network tools and to store images. To create this job. you add an imaging task. You need to create a job to capture an image of each managed computer on Friday evening. and other settings. However.

Now the imaging job can be applied to all computers at once. simplifying the process and reducing the chance of errors. you create a local configuration for each office with the correct server mappings. select a single global configuration for a job and update it based on the location of the Altiris PXE Server. This is exactly what redirection does. On each Altiris PXE Server. You create a global configuration (example: named “Imaging Environment”). Altiris® Deployment Solution 6. and the process is simplified.8 SP2 64 . The “Imaging Environment” global option is redirected to the local option.problems.

Altiris® Deployment Solution 6.Part III Using Deployment Solution This section provides feature identification and basic procedures for deploying and managing computers using Altiris® Deployment Solution™ software.8 SP2 65 .

Chapter 11

Deployment Basics
Deployment Solution provides a graphical, object-based interface to manage computers. After you have installed the Deployment Agent and the computer has connected, the computer can be managed using the Deployment Console.

Computers
Each computer and computer group in your environment is represented in the computers pane:

Computers can be dragged into a group, or automatically assigned to a group when the agent is installed. Computers can belong to only one group. When a new computer connects, it is placed in the New Computers group.

Jobs
Jobs contain a sequence of tasks to perform work on managed computers. Example: a job might be “install and activate Winzip 10.” This job might have a condition specifying that it should only execute on Windows XP computers with 500 MHZ or greater processors.

Altiris® Deployment Solution 6.8 SP2

66

Each job that can be assigned to a computer or computer group is represented in the jobs pane:

Computers are assigned jobs by dragging and dropping computers onto a job. Jobs can also be scheduled by right-clicking and selecting the Job Scheduling Wizard.

Creating Jobs and Tasks
Jobs are created by adding one or more tasks to a job. Tasks include create disk image, distribute software, manage SVS layer, and run script. These tasks run sequentially and can trigger other events, such as a stop job or execute other job depending on the return code of the task.

Context Menus (Right-click)
In the Deployment Console, you can right-click almost any object for a context-specific list of management options. Example: if you right click a computer or group, you are given the option of viewing computer details or job history, remote controlling or opening a chat session, renaming, power control, and several other options.

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 the property values appearing in the Computer Properties (page 124).

Altiris® Deployment Solution 6.8 SP2

67

Click <CTRL> F or click Find Computer 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 field, type all or part of the computer’s property values 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 you want to search in the Deployment Database. Example: to find a computer by searching for its IP address, type the address in the Search For field and select IP Address from the In Field drop-down list.

2.

Name MAC Address IP Address ID Serial Number Asset Tag UUID Product Key Physical Bay Name

BIOS name of the computer. Example: 0080C6E983E8. Example: 192.168.1.1. Example: The computer ID. 5000001. Serial number installed in BIOS. A primary lookup key. Asset number in BIOS. A primary lookup key. A primary lookup key. Product Key for the operating system. The actual bay number. Example: 7x.

Computer Name Deployment Solution name of the computer.

Registered User Name entered when the operating system was installed. Logged On User Name of the user currently using the computer.

The computer you are looking for appears highlighted in the Computers window in the console. Note This search is not case-sensitive and lets wildcard searches using the *.

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 Lab Builder on the console toolbar or click File > New > Lab Builder to set up jobs specifically created for managing multiple computers in a lab environment.

Altiris® Deployment Solution 6.8 SP2

68

You can set up jobs to:
Create Disk Image Deploy Lab Restore Lab Update Configuration Upload Registries Each job 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 tasks in the jobs are assigned default paths and file names that let them use the same images and configuration information, registry data, and so on. We recommend 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 jobs where the image is used.

To use Lab Builder
1. 2. 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 lab jobs, so if you change the name later you must change it in all jobs that use the image. 3. 4. 5. Enter a lab description to help you differentiate the lab from others. This field is optional. Click OK. 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, drag it to the computer or computer group 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 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 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 6.8 SP2

69

Computer Import File
Use the following format to import new computers from a text file. You can easily create a computer import file by entering data in the provided Microsoft Excel spreadsheet (ImportComputers55.xls) located in the Samples folder of the Deployment Share. A semicolon as the first character denotes comment lines. Quotes around fields are optional. Leaving the job name blank does not assign the computer to any job. Leaving the start time blank makes an entry in the job for the computer, but does not schedule it for a specific time. Only the Name field is required. Quotes around fields are optional. You can populate your computer database using the format provided below. The Import Computers text file can be imported into Deployment Solution using the File > New Computer > Import or File > Import/Export > Import Computers.

Tips for creating a new computers import file
When using Boolean references, do not use quote marks. These fields are marked with a B: 1=On/True and 0=Off/False. For some fields, this input format supports multiple IP Addresses, delimited by a “;” (semicolon) within the field. These fields are marked with a “(;)”. Example: the gateway field could read, 30.11.11.2, for a single IP address or, 30.11.11.2;30.11.11.3;30.11.11.4, to support three IP addresses. All fields (up to and including “site”) must be present in the file, but all data except for “Name” is optional. To use optional fields for multiple network adapters, the preceding fields are required. Example: to use Nic3 fields, all fields for Nic2 are required. For Deployment Server to read the import text correctly, ensure there is a final hard return at the end of the file.

Format for the New Computers text file
Outlined below is the field order for the database input. Fields marked “(ignored)” are not used by version 5.5 and later, but are included to support previous versions. ;Name,MAC Address 1,Serial Number,Asset Tag,Computer Name,Domain(B),Domain/ Workgroup Name,Domain Controller Name(ignored),DHCP(B),IP Address(;),Netmask(;),Gateway(;),Preferred DNS(;),Alternate DNS,Alternate 2 DNS,Preferred WINS,Alternate WINS,Hostname,Domain Suffix,Use Preferred Tree(B),Preferred Server,Preferred Tree,Netware User,NDS Context,Run Scripts(B),User,Organization,Key,Password Never Expires(B)(ignored),Cannot Change Password(B)(ignored),Must Change Password(B)(ignored),Username(ignored),Full Name(ignored),Groups(ignored),Password(ignored),Contact,Department,Email,Mailstop ,Phone,Site,Computer Group,Job,Job Start Time,NIC2 MAC Address,DHCP(B),IP Address(;),Netmask(;),Gateway(;),DNS(;),WINS(;),Domain Suffix,NIC3 MAC Address,DHCP(B),IP Address(;),Netmask(;),Gateway(;),DNS(;),WINS(;),Domain Suffix,NIC4 MAC Address,DHCP(B),IP Address(;),Netmask(;),Gateway(;),DNS(;),WINS(;),Domain Suffix,NIC5 MAC Address,DHCP(B),IP Address(;),Netmask(;),Gateway(;),DNS(;),WINS(;),Domain

Altiris® Deployment Solution 6.8 SP2

70

Suffix,NIC6 MAC Address,DHCP(B),IP Address(;),Netmask(;),Gateway(;),DNS(;),WINS(;),Domain Suffix,NIC7 MAC Address,DHCP(B),IP Address(;),Netmask(;),Gateway(;),DNS(;),WINS(;),Domain Suffix,NIC8 MAC Address,DHCP(B),IP Address(;),Netmask(;),Gateway(;),DNS(;),WINS(;),Domain Suffix

Example Import File
DB Computer 1,00a0c95c2640,6X18FHGZP21P,6X18FHGZP21P,Computer1,1,Altiris,,1,,,,,,,,,computer 1h,altiris.com1,1,server1,tree1,user1,context1,1,John Doe,"Altiris, Inc.",12345-OEM1234567-12345,,,,,,,,John Doe,Engineering,jdoe@altiris.com,111,(801) 8051111,Lindon,Test Group,Test Job,12/31/2001 17:30,00a0c95c2641,0,172.25.10.180,255.255.0.0,172.32.0.4,172.32.0.1;172.32.0.7, 172.32.0.4,altiris.com2,00a0c95c2642,1,,,,,,altiris.com3,00a0c95c2643,0,1.1.1.1;2.2.2 .2,255.255.255.255;255.255.255.0,1.1.1.2;2.2.2.1,3.3.3.3;4.4.4.4,5.5.5.5;6.6.6.6,alti ris.com4,00a0c95c2644,1,,,,,,altiris.com5,00a0c95c2645,0,1.1.1.1,2.2.2.2,3.3.3.3,4.4. 4.4,5.5.5.5,altiris.com6,00a0c95c2646,1,,,,,,altiris.com7,00a0c95c2647,0,5.5.5.5,4.4.4 .4,3.3.3.3,2.2.2.2,1.1.1.1,altiris.com8

Altiris® Deployment Solution 6.8 SP2

71

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. It also provides a Thin Client view of the Deployment Console. 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, Altiris PXE Server configuration, image editing, and other deployment utilities and features. See Deployment Console Basics (page 73). 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. The Thin Client View of the Deployment Console provides a simplified experience when dealing exclusively with Thin Clients. The functionality of the Thin Client Console is identical to that of the current Deployment Console. However, you can toggle from Full View to Thin Client View. 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 Start > Programs > Altiris > Deployment Solution > 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 (page 73). Set Program Options. From the Tools > Options dialog, you can set preferences for each Deployment Server system. See General Options (page 85). Set Security. From the Tools > Security dialog, you can set security rights and permissions for all Deployment consoles. See Security in Deployment Solution (page 89). 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 (page 95). 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 (page 82).

Altiris® Deployment Solution 6.8 SP2

72

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 the status and settings. From the Deployment Console you can build simple or complex deployment jobs, assign them to a computer group, and verify deployment execution. Because the Deployment Console can reside on its own computer, you can have multiple consoles running from different locations. The Deployment Console needs to be running only while creating assignments or viewing information about the managed computers. You can turn on the console, run management tasks, and turn off the console. 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 is assigned those tasks in the order they are received. See Console options (page 85) 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 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 (page 127), or view Computer Properties (page 124). You can also create computer groups to organize collections of similar computers.

Create computer groups by clicking Computer Groups on the toolbar, or right-clicking 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, a list of computers in the group appears in the Details pane and provides the basic information about each computer. The Filter detail bar appears 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 are run or scheduled to run on the computer, and the status of each job. To get more details about all tasks that are run on computers, click Status Detail. Status Detail displays a more detailed breakdown of the processes that 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 (page 97) for

Altiris® Deployment Solution 6.8 SP2

73

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 according to your specifications. 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.

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

When a job is selected, the Details pane displays a list of computers in the folder and gives a 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 also appears, letting you assign jobs to computers. See Setting Conditions for Task Sets (page 153). 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 Shortcuts and Resources View (page 75). 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 (page 147) for complete information about setting up, importing, and managing computers from the Jobs pane.

Details pane
The Details pane extends the user interface features when working in the Computers, Jobs, or Shortcuts panes. 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.

Altiris® Deployment Solution 6.8 SP2

74

When you select a job icon in the Jobs pane, the Details pane displays the 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 the 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, and information about the included partitions. When you click on the package files, the Details pane displays the title, description, version, creation date, and platform of a .RIP file 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.

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 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 as a storage to save commonly-used jobs and computer icons. The Resources view lets you see a filtered view of the package files—.MSI files, .RIPs, image files, Personality Packages, and other resource packages—stored in folders in the Deployment Share. From the Resources view, you can drag packages directly to the computers in the Computers pane to deliver the 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. 2. 3. Enable the Shortcut view. Click Resources 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 (page 191). See Console options (page 85) for options to set refresh intervals for Resources view.

Altiris® Deployment Solution 6.8 SP2

75

Thin Client View of the Deployment Console
The Thin Client view of the Deployment Console provides a simplified experience when dealing exclusively with Thin Clients. The functionality of the Thin Client view is identical to that of the current Deployment Console. However, you can switch from Full View to Thin Client view. The Thin Client Console has four panes: Computers Resources Software Packages Inventory The Computers, Resources, and Software Packages panes are on the left side of the Thin Client view, while the Inventory pane is on the right side of the Thin Client view.

Installing the Thin Client View
During installation, you can install the Deployment Solution Thin Client view. By default, the traditional Deployment Console is installed. If you select Thin Client view, a Thin Client Jobs system folder is created. All the jobs created from the Deployment Solution Thin Client view are stored in this folder. During the installation process, the following folders are created in this hierarcy for the Thin Client resources: Configuration Packages Images Software Packages Deployment Solution for Thin Clients uses the same installation program as Deployment Solution. No licensing is required even if you select Thin Client Install.

To install Thin Client
1. On the Deployment Server Installation dialog, select the Install Thin Client option. The Thin Client view of the Deployment Console appears. or On the Deployment Server Installation dialog, select the Simple Install option. The Deployment Console appears. 2. Click View > Thin Client View. The Thin Client view of the Deployment Console appears.

Switching Between Two Views
When you switch between the traditional view and the Thin Client view, you can maintain the last state in which you viewed the console. This ensures that you open the console in the same view that you last closed it in.

To switch between the traditional and the Thin Client view
1. Click View.

Altiris® Deployment Solution 6.8 SP2

76

Images. all the automation jobs have the default option selected for boot image. By default. a list of the available resources for the selected type appears. such as Configurations. Select Show Thin Client View. These are visible when you switch to the traditional view. you can view the following options: Capture Configuration Capture Images Deploy Configuration Deploy Image Install Automation Partition Get Inventory Power Control Properties Remote Control Manage Inventory View If you select a Capture option. a text field appears. You can select a resource from this list. To create a job You can create a job in one of the following ways: Select any of the first six options from the Computers pane. all the menus and items not necessary for the Thin Client view are unavailable. that you can change. If you select a deploy option. When you switch to the Thin Client view.8 SP2 77 . When you right-click a thin client. Altiris® Deployment Solution 6. You can right-click this pane to view a new menu. However. or Software Packages appears.2. only thin clients are displayed. Drag resources to the Computers pane or computers to the Resources pane to schedule jobs at the current time. Computers Pane This pane is the same as that in the traditional view. prompting you for the name of the captured resource. Note By default. the name is the same as the serial number on the thin client. the Thin Client view is visible if you select Thin Client Install. Note The Schedule Computers for Job dialog does not have the Job Schedule tab. Also. All these jobs are scheduled at the current time. Note Ensure that you have the required permissions to drag and drop resources.

Open the Thin Client view. 2. Select this option to create a new folder. See To import a job. an appropriate message appears. Select this option to find software packages. Find Software Packages. When you click any of the three submenus corresponding to the subdirectories within the ThinClient directory. Import. are disabled when the client is not active. All the above options. Example: HP Tools. You can rename or delete the resources. When creating the jobs. Select this option to import a job. Note All the jobs on the thin clients are automatically created and scheduled by the console. Example: Captured Registry Settings. Delete. The Import Job dialog appears. Note You cannot rename the Software Packages pane. you can view the following options: New folder. You cannot delete or rename this new system folder from the console. You can drag and drop this resource to the thin clients and vice versa. Resources pane This pane is a tree view listing all the resources that you can drag and drop to the thin clients and vice versa. 3. Select this option to rename a folder. Rename. If the folder is empty. Select this option to delete folders. When you right-click the Software Packages pane. Three types of resources appear in this pane: Configuration Packages. except Properties. Note All these resources reside in the express share in the ThinClient directory. the tree expands and displays all the resources included in the directory.8 SP2 78 . the console refers to the operating system type (platform) of the client. To import a job 1. You can only rename a folder. Images Software Packages. Altiris® Deployment Solution 6. Software Packages The Software Packages pane displays the software packages that can be created for the available computers. Browse to specify the file to be imported in the Job file to import field.All thin client job details are saved in the Thin Client Jobs system folder. and this is done only when the clients are active. Right-click the Software Packages pane and select Import.

select System Jobs > Thin Client Jobs > Software Packages. Click Yes to confirm the deletion. select the Preserve Scripted Install OS source paths option. You can delete the Software Packages pane from the Thin Client view through the Deployment Console view. listing all the thin clients identified by the console. Note The Software Packages option is automatically added in the Jobs pane in System Jobs > Thin Client Jobs when you switch from the Deployment Console view to the Thin Client view. The following columns appear in the Inventory pane: Name Computer Status Action Status Product Name Operating System Image Version Flash Size Memory Size BIOS Version You can select which columns to view. but do not appear: Automation Partition CPU Domain Name IP Address Altiris® Deployment Solution 6. 4. 5. Open the Deployment Console.8 SP2 79 . The Software Packages option is deleted from the Deployment Console view. Right-click Software Packages and select Delete. A confirmation dialog opens. and Delete existing Jobs in folder options are disabled. The following columns are available.Note By default. 3. Overwrite existing Jobs and Folders with the same names. To preserve the source operating system file paths of Scripted Install. Inventory Pane The pane displays a table. 2. Click OK. To delete the Software Packages option from the Deployment Console 1. the Import to Job Folder. 4. In the Jobs pane.

Add columns to either the Selected columns list or the Available columns list by clicking the required arrows. Use this tool to create boot disk configurations. Remotely install the Deployment Agent on client computers from the console. It also includes icons to quickly run commonly used Remote Operations Using Deployment Solution. which make up the boot menu options that appear on client computers. Right-click the Inventory pane. You can launch Deployment Solution administration tools (Boot Disk Creator. Administration tools Boot Disk Creator. 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. PXE Configuration. you can launch Deployment Solution administration tools and package editing tools. Deployment Solution Utility Tools The Deployment Console lets you open utility programs from the Tools menu or from the Tools toolbar. Wise SetupCapture and Remote Agent Installer) and package editing tools (Wise MSI Editor. This is another solution to boot computers to automation.MAC Address To view Inventory columns 1. The Manage Inventory Column dialog appears.8 SP2 80 . Remote Agent Installer. See the Altiris PXE Configuration help. From the Main toolbar. you can create new jobs and computer accounts and run basic deployment tasks. 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. See Altiris Boot Disk Creator help. This utility lets you push the agent installation to client computers from the Deployment Console. After installing the Altiris PXE Server. PC Transplant Editor. On the Tools toolbar. Altiris® Deployment Solution 6. you can create and modify configurations. and Image Explorer) from the toolbar. 3. PXE Configuration. 2. Click OK.

see the Software Virtualization Solution Reference Guide.Carbon Copy. Your base computer should not be running an antivirus program or any other computer management program. deactivate. data files. See the Altiris PC Transplant Help located in the Deployment Share. SVS places applications and data into managed units called virtual software packages. It creates. 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.8 SP2 81 . The Deployment Solution computer should have a clean installation of the Windows operating system. see Using SVS Admin Utility with Deployment Solution (page 81). The computer should not have any background processes or programs running that can be captured into the layers. and manage virtual software layers. the computer should not have an active Internet connection. Image Explorer. If possible. import. Edit . create and index. You can edit and split an image. or reset applications to avoid conflicts between applications without altering the base Windows installation. imports and manages virtual software layers. Remotely control managed computers to view and troubleshoot problems from the Deployment Console. Using SVS Admin Utility with Deployment Solution On a Deployment Solution computer. you can capture application and data files. Create. See Software Virtualization Solution (page 81). Using SVS you can activate. SVS Admin Utility. this tool lets you view and manage data in the image file. Wise MSI Editor.MSI packages generated from the Wise Setup Capture tool or other . and more. The installed application. and settings are captured into the virtual software layers. Altiris® Deployment Solution 6. Software Virtualization Solution Altiris® Software Virtualization™ solution (SVS™) is a revolutionary approach to software management. For information on the integration of the SVS Admin Utility with Deployment Solution.MSI files used to distribute software and other files. The SVS Admin Utility is a part of SVS. See the Altiris Image Explorer help file located in the Deployment Share. Use this tool to edit a Personality Package to add or remove data. which are part of the packages. Package Editing Tools PC Transplant Editor. For information on installing and using the SVS Admin Utility. After a disk image is saved to the Deployment share.

8 SP2 82 . The . and two additional menu items.INI files are located in the Deployment Share. Place both types of . This sample file contains one submenu. See Distributing Software (page 175).INI files to create submenus.RIPs.INI files in the same directory where the Deployment Console executable (eXpress. These .You can create layers on a virtual computer. personality settings.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> The ATools. and other package files to computers or groups. Commands are added by modifying or adding new . Executable=C:\Program Files\NetMeeting\conf.exe [NetMeeting] MenuText=NetMeeting Description=NetMeeting WorkDir=.ini file extends the main Tools menu on the console. You can also distribute .exe) is located (the default location is the Program Files\Altiris\ eXpress\Deployment Server).exe Altiris® Deployment Solution 6. You can insert commands to the root ATools. and eight menu items for each submenu. You can add up to eight menu items to the main menu. Executable=C:\WINNT\notepad. and Netmeeting. scripts. 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. Notepad. [Submenus] Web Tools=wtools.INI files.ini [Notepad] MenuText=Notepad Editor Description=Simple Editor WorkDir=. (See Managing the SVS Layer on page 177) This lets you disconnect a computer from the network and reset the computer after each capture. . This ensures that you have a clean operating system.MSI files. This lets easy access to applications commonly used with Deployment Solution. Web Tools.ini file for the main menu or add new .

INI file is wtools. including the type of the operating system. The Condition feature appears in the Details pane. free disk space. processors. The job runs only on the computers that meet the specified criterion.This filters out only the jobs with the registered license user named Milo. [Explorer] MenuText=Explorer Description=Windows Explorer WorkDir=. in the Conditions dialog . You can now create task sets for each job that are applicable only to the computers matching those conditions. Altiris® Deployment Solution 6. network adapters. enter the following custom token:%#!computer@lic_os_user%.8 SP2 83 . 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. On the main menu this is titled “Web Tools” (see Tools. and other computer properties. select from a list of predefined database fields or create custom tokens that key on other fields in the database.Another Tools . Example: select User Defined Token from the drop-down list in the Fields box.exe Computer Filters and Job Conditions Use this dialog while Creating a Computer Group Filter to filter only the specified computers in a computer group. or while Setting Conditions for Task Sets when running a job only on the specified computers in a group.ini.ini) and contains two applications. Creating Custom Tokens You can create custom tokens to set conditions based on the database fields not provided in the available preset conditions. and enter Milo in the Value field.ini file. Click a job in the Jobs pane. When you are setting conditions to schedule a job. In the Token field. It is a submenu file referenced by the main ATools. you can create a single job with tasks defined for computers with varying properties. As a result. Click Setup to add new conditions or edit existing conditions. Executable=C:\Program Files\Adobe\Acrobat\acrobat. Select contains in the Operation field. Executable=C:\Program Files\Internet Explorer\explorer.exe [Acrobat] MenuText=Acrobat Reader Description=Acrobat Reader WorkDir=. Internet Explorer and Adobe Acrobat.

Type a name for the filter. 2. and delete existing computer filters. Displays all the computers where jobs have failed to execute. Click the All Computers group or any other computer group. Or Click Setup > Modify. Displays only the Pocket PC computers. Displays only the computers with Windows 2000 or 2003 operating systems.8 SP2 84 .NET operating systems. Example: you can create a filter to view all the computers in a particular group that have Windows 2000. Click a computer group in the Computers pane. Define the conditions you want to filter.Filter Name Active Computers Inactive Computers Computers With Failed Jobs Windows 98 Windows 2000/ 2003 Windows XP Windows CE (PDAs) Linux Windows XP Embedded Windows CE . Creating a Computer Group Filter The Computer Filters dialog displays a list of all computers in a group according to the specified criteria. Displays only the computers with Windows CE operating systems. and click Add. The Filter Definition screen appears. On the Filter bar in the Details pane. Displays only the computers with Linux operating systems. Click the Field box to see a list of computer values stored in the Deployment Database. Displays only the computers with Windows 98 operating systems. Displays only the computers with Windows CE . 256 MB of RAM. Displays only the computers with Windows XP Embedded operating systems. To create or modify a computer filter 1. or modify. By applying the filter. 4. you can view all the computers that meet the specified criteria in the Details pane of the Deployment Console. and 20 GB hard disks only. The Filter feature appears in the Details pane for the selected computer group. click Setup > New to create a new filter. Select a computer value and set the appropriate operation from the Altiris® Deployment Solution 6. Displays all the inactive computers. Click Setup to add new filters. 3.NET Pocket PC (PDAs) Description Displays all the active computers. Displays only the computers with Windows XP operating systems.

see Shortcuts and Resources View (page 75). log entries remain in the history. 5. This lets you refresh console data at defined intervals rather than updating every time the Deployment Console receives a command from the server. Automatically update the displayed name of the managed computer names in the console when the client computer name changes. Delete history entries older than _____ days. See Setting Conditions for Task Sets (page 153). Click Tools > Options to view the Program Options dialog. Synchronization is off by default. Enter any number between 1 and 10. Click OK. Refresh the display of data accessed from the Deployment Database. which can be excessive traffic in large enterprises. When a job is assigned to computers and the Default condition has no tasks assigned. Console options (page 85) Global options (page 85) Task Password options (page 86) Domain Accounts options (page 87) RapiDeploy options (page 87) Agent Settings options (page 88) Custom Data Sources options (page 88) Console options Set basic console features for miscellaneous refresh actions and warning messages. and Sales as the Value.000. a message appears.8 SP2 85 . Specify the number of days you want to keep inactive computers in the Deployment database before they are deleted. Remove inactive computers after ____ days. but any number between 1 and 10. Synchronize display names with computer names. Altiris® Deployment Solution 6. The names do not have to be synchronized for the Deployment Server to manage the computer.Operations list.000 is valid. The default value is 30 days. Refresh displayed data every ____ seconds. If you don’t select this option. If this option is not selected. Warn user when no tasks are assigned to the 'default' condition. changes to the computer names is not reflected in the console. Scan resource files for changes every ____ seconds. Example: you can choose Computer Name as the Field. Repeat to include other conditions. Global options Set global options for the Deployment Server system. The job has no secondary default tasks assigned if a computer in the group does not meet the primary conditions. In the Value box enter an appropriate value for the selected database field. Contains as the Operation. Specify the number of days an entry is kept in the history until it is deleted. Specify how frequently (in seconds) the Deployment Console updates its view of package files in the Resources view. General Options Use Program Options feature to set the general options for Deployment Solution.

select the product key to be modified. and click Add to type the Product Key. or MAC Address.Reschedule failed image deployment jobs to immediately retry. the password becomes invalid and all jobs and tasks using the user name whose password changes must be Altiris® Deployment Solution 6. Ensure that you do not give a permanent license to computers you do not want to manage after their trial license expires. select the product key to be deleted. The program continues to retry until the job succeeds or until the job is cancelled. Primary lookup key. This setting is useful if you have a firewall and need to use a specific port rather than a dynamically assigned port. Display Imaging status on console. Automatically replace expired trial licenses with available regular licenses. Specifies the lookup key type used to associate a new computer with a managed computer. Note If the product key is being used by another task. Lets Deployment Solution to automatically assign a permanent license to the computer after the trial license expires. To modify a product key. You are prompted with a message stating that the product key is being used by another task. Specifies ports for using the Remote Control feature. Client/server file transfer port: _____. and click Edit. 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 operating system. Displays the status of the imaging job on the Deployment Console. OS Product Key tab In the OS Product Key tab. Specifies a static TCP port for file transfers to the clients. Sysprep Settings View and configure the Sysprep settings for the Deployment Server. UUID. a list of all product keys for the selected operating system appears. select the suitable operating system from the Operating System drop-down list. Remote control ports. Note Be careful when using this option. Sysprep Settings. This lets you enter global values for Sysprep. you cannot delete the product key.8 SP2 86 . the passwords for administrators and users change after a certain number of days. The default value is 0 and causes the server to use a dynamic port. Select an operating system from the Operating System drop-down list. In such a scenario. See Sysprep Settings (page 86). and click Remove. To remove a product key. After you select the operating system. The options are Serial Number. You have the option to enter a primary port address and a secondary port address (Optional). Immediately retry a failed image deployment job. Asset Tag. Task Password options According to the network and security properties.

Enter the name of the selected domain and provide the administrator credentials. Run Script. the Status field displays the message: Password for 10 tasks updated. The Task Password option provides administrators with a simple option to manage all password changes from a centralized location. you can also identify a range of ports to identify these computers. Note To enter the administrator user name for a Windows XP domain. Example: User A’s user name and password is used in ten tasks. On the first pass Deployment Server accesses the selected computers using the list of IP numbers. Click Reset to set the default values. Example: instead of entering just the user name jdoe. you can do so through the Task Password option. Altiris® Deployment Solution 6. Note Multicasting images are not supported when using the UNDI driver on PXE. download an image from a file server. letting you deploy images to a group of computers simultaneously. Domain Accounts options This sign-on feature retrieves the name of the administrator (or user with administration rights) and the password for each domain. or access a local hard drive. The Add Domain account appears. you need to enter domainName\jdoe. avoiding the need to log on for each managed computer when completing imaging and configuration jobs. Deployment Server accesses the range of computers using the defined IP pairs and avoids retrieving the computers through the port and operating system layers. Distribute Software. you can enter a range of IP addresses when using the multicasting feature to speed computer deployment and management.8 SP2 87 . and are disabled on the client. you need to add both the domain name with the user name. However. this tab is enabled only to administrators and select users who have been granted the appropriate privileges. The Status field displays the results of password updates. On the second pass. This feature lets you set or change user passwords from a central location. so you can modify the password for the Copy File to. because some network adapter cards do not handle multiple multicast addresses. RapiDeploy options This feature optimizes the multicasting ability of the RapiDeploy application in Deployment Server. However. Deployment Server accesses the selected computers using the port numbers or higher level operating system ID's. Click Add to enter the Domain name. The administrator name and domain are listed in the Domain Accounts list box. Click OK. and manage the imaging of several client computers concurrently.modified to use the new password. and Capture Personality tasks when creating or modifying jobs. Distribute Personality. After the password is updated. Because RapiDeploy is more efficient when writing directly to the IP address of the network adapter driver. If you want to update the password for these ten tasks.

The name of the external database from which you want to extract data. These default settings are applied only for new client computers that have never connected to the Deployment Server. See Allowed Stored Procedure List (page 88). you must provide a user name and password to authenticate to the external database. Select this option to force the default settings when adding a new automation agent connects. If the client computer is new and if the Force new agents to take these default settings option is selected. Force new Automation agents to take these default settings. These settings are not for the existing managed computers nor are these settings applied when setting properties using the Remote Agent Installer. When the integrated authentication is not being used. When the Deployment Agent connects. Use Integrated Authentication. The information required to create a custom data source entry are listed below: Alias. it uses the existing agent settings. Database. The same process occurs for automation agents if the Force new Automation agents to take these default settings option is selected. Set Deployment Agent Settings for new computer accounts or set Deployment Agent Settings for DOS for new computers. Click Change Default Settings to change Windows Agents Settings for Windows and DOS. The alias name you would like to use when referencing the external SQL database. the Deployment Agent on the client computer receives the default settings established in the Options > Agent Settings dialog. and have no information stored in the Deployment Database. Deployment Server verifies if the computer is a new or an existing computer. Allowed Stored Procedure List Click Allowed Stored Procedures to identify the stored procedures from the selected custom data source. User name and Password. Select this option to force the default settings when adding a new computer. If the computer is recognized as an existing managed computer. Click Add to enter an administrator alias and other login information for the Microsoft SQL Server (or MSDE) hosting the desired Deployment Database. 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. This option authenticates to the external database using the domain account you are currently logged on as. This lets you call stored procedures outside of the Deployment Database (express database) using custom tokens within scripts or answer files. Force new agents to take these default settings. Server. Click Allowed Stored Procedures to modify the existing list. The name of the external SQL database server or IP address. Altiris® Deployment Solution 6.8 SP2 88 . You can now select from the list of available stored procedures in the data source.Agent Settings options These are the default agent settings for new computers.

Each security group can perform only a defined scope of deployment operations on each computer group or job folder. You can also set up a password for the selected user. This group will have access to run all operations on all computers using all types of jobs. These virtual computers appear under the Virtual computers node in the Computer pane. you can also set up a Technician group that has only basic access and permissions limiting deployment operations. Click Add on the Virtual Center page. To set general security rights. right-click and click Security.Virtual Centers You can keep a list of all VMware Virtual Center Web services. and user name. This prohibits members of the group from re-imaging the Server computer group or scheduling Distribute Disk Image jobs. select the object in the console. Additionally. You Altiris® Deployment Solution 6. each user can be assigned rights to access general console features. The hosts and virtual computers from each Virtual Center that have corresponding computers in the Deployment Database appear in the computer tree. See also Best Practices for Deployment Solution Security (page 89) Enabling Security (page 90) Setting Permissions (page 93) Groups (page 92) Rights (page 92) Best Practices for Deployment Solution Security Deployment Solution is based on defining groups of users and groups of computers and jobs. To set feature-based permissions for specific computers or jobs. display name. and associating one with another. click Tools > Security and add a user name and password. and enter the Server host name. However. Note Security rights and permissions set in one console is enforced in all Deployment consoles. Altiris recommends that you first create user groups based on administration duties or access to levels of deployment operations. letting IT personnel to be assigned to different security groups to manage operations on specific computer groups or job folders. Security in Deployment Solution Deployment Solution provides a security system based on associating job and computer objects with user and group permissions.8 SP2 89 . 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. Example: you will most likely set up a group with full Administrator rights. You can create users and groups and set scope-based rights.

see Adding users from the Active Directory (page 91). Altiris® Deployment Solution 6. Note When the Administrator Right is selected. you can limit their rights to set General Options and set permissions on each computer groups and job folder for the group. You can add a DS user or a user from the Active Directory. On the main Security dialog. and click Close. The Add User Account dialog appears. You can select the computer group. Select the authentication type. 9. If users are assigned to multiple groups. 10. Select the group name in the left pane. The Security dialog appears. Click Manage User Groups tab and click Add. adding a user to the Administrator group. Select the authentication type. 6. Select Administrator in the Rights dialog. Additional groups can be created with different rights and permissions depending on the needs and responsibilities in the IT team. Click OK. click the Manage Users tab. The group name appears in the window. see Adding groups from the Active Directory (page 92). 4. 7. Click DS User in the Add User Account dialog. 5. and selecting Enable Security.8 SP2 90 . Type a name and description in the Add User Group dialog. you do not need to select any other rights because the Administrator Right implies that all other rights are selected. Click DS Group Note The Browse option is disabled for Local Group. and click Allow or Deny for a list of deployment operations. Click Tools > Security. You can add a DS group or a group from the Active Directory. 8. After creating the Technician group. Schedule Create Disk Image. Click OK. and click Add. and Schedule Distribute Disk Image. This assigns complete rights and permissions to the group. 1. Select the new group name and click Rights. 2. To add users from Active Directory. Example: you can select the Deny check box for Restore. 3. To add groups from Active Directory. right-click it and select Permissions. Note The Browse option is disabled for DS User. The Add User Group dialog appears.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. Enabling Security You can enable security by first creating a group with Administrator rights. the Evaluate Permission and Evaluate Rights features are sorted and display effective permissions and rights.

Type a description for the user in the Description box. 1. and password. Security is now enabled. 14. not groups. In the main Security dialog. You can now create users and groups and assign permissions to computer groups and job folders. and click Add. Retype the password. Evaluate Rights Click Evaluate Rights to identify the combined rights of the selected user and its user group(s). To import users. full name. Note When logging on with the imported AD account. The users are added to the Deployment Database. 3. Type user name. 12. 4. See Best Practices for Deployment Solution Security (page 89). Click AD User in the Add User Account dialog. Deployment Solution accessed the Windows Active Directory server to validate the user password. Altiris® Deployment Solution 6. This feature identifies effective rights for each user by resolving any possible conflicts between multiple group settings. Importing users from the Active Directory You can also import users from the Active Directory. 2. click the Manage Users tab. see Importing users from the Active Directory (page 91). and click AD Import. 5. or click Browse to select the user from the Active Directory. from the main Security dialog. Add users from Active Directory. If you know the user name. Note You can add only one user at a time. you still need to assign the users to security groups with appropriate rights and permissions. Note You can assign the user Administrator rights directly. Click OK.8 SP2 91 . and provide a description for the user. 13. Now that you have a user with administrator rights. click Manage Users tab. Click Rights. select the Enable Security box. Click OK. However. This assigns the new user to the new group with Administrator rights. Adding users from the Active Directory You can add users from the Active Directory. type it in the User name box.11. Click the name of the new Administrator group in the Groups window. To open a standard Windows Active Directory dialog. Select the user name in the main Security dialog. The password field is deactivated as the user is being added from the Active Directory. but we recommend you to assign users to groups. Click OK.

click OK to save your changes. To verify. After selecting all applicable rights. and Enabling Security (page 90). Click AD Group in the Add User Group dialog. and upon matching does not prompt for user credentials. However.Groups Assign the user to previously created groups. you can modify the description. Add groups from Active Directory. The group is added to the Deployment Database. click Manage User Groups tab. and tries to access the Deployment Console. appears in a new dialog. You can choose a domain from the Domain List. 3. who is a part of the AD group. click the Manage User Groups tab. and if a system logged-on user. and click AD Import to open a standard Windows Active Directory dialog. type it in the Name field. and click Add. use the following steps: 1. click the Manage User Groups tab. you can assign the user to a group with Administration rights. 2. Deployment Server checks the authentication with the logged on user. The Name. and Description gets automatically filled. Click OK. and click Add. See also Best Practices for Deployment Solution Security (page 89). Select a group from the list. In the main Security dialog.8 SP2 92 . along with their descriptions. 4. or click Browse to select the group from the Active Directory. The newly added group appears in the main Security dialog. From the Security screen. Rights This dialog lets you set general rights for a user or group. click the Rights tab. 1. 2. Domain. add or change the rights assigned to each console user. select a user and click Rights. 3. In the main Security dialog. DS Authentication If the user is already in the DS database. If you are enabling security. tries to access the Deployment Console. Select the check box for each right you want to grant. from the Security dialog. and type the required details. From the Set Rights For window. You can view the members of any group by clicking the group in the Manage User Groups dialog and clicking View Members. Similarly. 4. if a group has already been added in the DS database. Adding groups from the Active Directory You can add users from the Active Directory. To add groups. and click OK. Importing groups from the Active Directory You can also import users from the Active Directory. you still need to assign the users to security groups with appropriate rights and permissions. Deployment Server does not prompt for credentials. and select a group from the displayed list. A list of groups. Select the authentication type. If you know the group name. Altiris® Deployment Solution 6. However.

Lets you set Console options. Lets you view Rejected Computers in Deployment Solution and change status. Right-click on a computer group or job folder (or individual computers and jobs) and select Permissions. The Object Security dialog appears. you can set the view and set the console options. Allow scheduling on All Computers. Lets you schedule jobs on All Computers. You must have administrative rights to access this option.8 SP2 93 . you can view and set the global options. Options Task Password. 2. and Capture Personality when creating or modifying. Options Console. You can view. Refresh Clients. Lets you create Custom Data Sources options. Import/Export. and computer groups. Options Custom Data Sources.A brief explanation of each Deployment Server right that can be assigned is detailed below: Administrator. Lets user access all features available on the Deployment console. Lets you set RapiDeploy options. Options RapiDeploy. Click the Groups tab and select a group name. Options Global. See Best Practices for Deployment Solution Security (page 89) for additional design tips. If this check box is selected. job folders. Lets you import and export jobs and import computers as well. Setting Permissions Set permissions for jobs. by default you have the rights to schedule job on all computers. Altiris® Deployment Solution 6. Manage Rejected Computers. Use PXE Configuration Utility. Lets you centrally update passwords for users and groups so they can access the tasks: Copy File to. Lets you view and add options for Virtual Centers. See Enabling Security (page 90). See Task Password options (page 86). Lets you to set Global options. computers. Options Domain Accounts. irrespective of the check box state. See Virtual Centers (page 89). If you have administrator rights. You can grant this right to a specific user or a group. You can view and set the agent settings. You must have Administrator rights to enable security. Options Virtual Centers. You can view and set the domain accounts option. See Importing and Exporting Jobs (page 192) and Importing New Computers from a Text File (page 102). Lets you Refresh Deployment Solution clients. Distribute Personality. You can use the View > Refresh clients <CTRL +F5> feature to disconnect and reconnect client computers. Options Agent Settings. create. Run Script. Or click the User tab and select a user name. Lets you use the PXE Configuration Utility. and set database aliases. Distribute Software. Lets you set Domain Accounts options. If this check box is selected. Lets you set Agent Settings options. 1. You can view and set the RapiDeploy options.

Note Administrators have access to all objects with unrestricted rights and permissions. one group could be allowed a permission at a particular level while the other group is denied the same permission. When a user is associated with multiple groups.3. Evaluate Permissions Click Evaluate Permissions to identify the combined permissions of groups and containers with contrasting permissions. These permissions include access to Remote Operations Using Deployment Solution and features for scheduling Deployment Tasks. You cannot explicitly deny permissions to computer or job objects for users with administrator rights. Example: if a job contains errors and does not run. 6. Note Permissions to schedule jobs also lets a user to delete jobs in the Details pane after a job runs. If a job includes multiple tasks and one of the tasks does not have sufficiently assigned permissions. the object in question looks in the current location and up the tree for the first permission it can find and uses the same. the user cannot run the job. In this scenario. 4. To assign permissions to multiple groups.8 SP2 94 . select if you want to Accept or Deny permission to run the operations on the selected computers or job objects. the permission to deny the privilege is enforced. If a console user does not have permissions to run all tasks the job contains. the whole job fails due to lack of access permissions. 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. From the list in the right pane. 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. Permission Rules Permissions received through different sources may conflict with each other. User permissions take precedence over Group permissions. Altiris® Deployment Solution 6. Deny overrides Allow. Select the Allow or Deny check box to explicitly set security permissions for these Deployment Solution features for the selected objects. Permissions do not flow down an object tree. The user must delete the job before scheduling a new job. 5. no other jobs can be scheduled. Instead. This feature identifies effective permissions for each object by resolving any possible conflicts. click Set permissions on all child objects to assign the values without closing the dialog.

Click New. for example: Altiris® Deployment Solution 6. executables. You need to browse to the new connection’s Deployment Share to access its shared folder containing its RIPs.8 SP2 95 . Windows remembers the last place you browsed to. Connecting to a new Deployment Database 1. Enter requisite information to connect to the external Deployment Server connections using an ODBC driver. g. b. Using the menu in the ODBC Data source name dialog. Click OK. a. The Define Connection Information dialog appears. 2. e. select it from the menu. Select the Change the Default Database to check box and select eXpress from the menu. Click ODBC Administrator. 4.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 you are currently logged on to. Enter a name for the connection to be opened. You return to the main ODBC Data Source Administrator dialog with your new data source listed in the System DSN tab. 3. 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. Select the SQL Server driver source and click Finish. j. If an entry for your server already exists. c. and other resources. f. which would be the Deployment Share of the previous Deployment Server connection. select the new Data Source name you just created. Opening a connection requires that you connect to the Deployment Database of the preferred Deployment Server connection using the ODBC Data Source Administrator. d. In the Create a New Data Source to SQL Server dialog. images. enter the name of the server hosting your remote SQL server in this box. The specifications for the ODBC data source appears. Click Finish. Note Although you are accessing another connection (another Deployment Database). h. and click Add. Otherwise. Establish an ODBC data source. Click File > Connect to or press CTRL+O to open the Connect to Deployment Server dialog. Click Next. Click Test Data Source to verify that the source is reachable. i. Click Next. enter a name and description for the data source. Click the System DSN tab. 5. Click OK. Click Next in the Create a New Data Source to SQL Server dialog to accept the default settings.

you are asked if you want to disconnect all computers. Refresh Deployment Solution You can refresh the Deployment Console by clicking View > Refresh Console (or pressing <F5>) to update data from the Deployment Database. This lets the computer to attach again and be managed by the Deployment Solution system. It also creates additional network traffic when all computers connect and disconnect. The rejected computers are prohibited from being active in the Deployment Database. Click OK. This tells the Deployment Agent to shut down and restart. You can remove computers from the Rejected Computers list by selecting it and clicking Accept Computer(s). you ensure that you are viewing the current status and state of all computers resources in your system. Click Yes.\SalesServer\express or H: 6. Rejected Computers in Deployment Solution When an unwanted managed client computers attaches to your Deployment Solution system. By refreshing the managed client computers.8 SP2 96 . When you refresh the managed client computers. They are identified and rejected by their MAC address. Altiris® Deployment Solution 6. You can view these rejected computers by clicking View > Rejected Computers. you can right-click the computer in the Computers pane and select Advanced > Reject Connection. You can also click View > Reset Client Connections (or press Ctrl+<F5>) to disconnect and reconnect all managed computers in a Deployment Server system.

hardware configuration. operating system. Major computer types are identified by a computer icon in the console. with a listing of scheduled jobs and operations associated with each computer.Managing Computers From the Computers pane of a Deployment Solution console. or set filters to sort computers by type. Manage with Computer icons. Click New Computer on the console to create a new computer account. you can identify. or other criteria. like completely re-imaging the hard drive. network and Web servers. When the new computer starts up you can assign it a preset account. Deploy to groups of computers. letting you run deployment jobs or execute operations on multiple computers simultaneously.8 SP2 97 . In the Deployment Console. drag a computer icon or group icon to a job icon. You can also click File > New > Computer Group or right-click in the Computers pane and select New Group. you assign and schedule deployment jobs to computers or groups by dragging the computer icon to a job in the Jobs pane. See Adding New Computers (page 100). deploy. network container. Preset computer accounts automatically associate with new computers when they start up. and network switches. handhelds. You can use search features to locate a specific computer in the Deployment Database. 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. including desktop computers. You now have management of all your computer resources available from a Windows or Web console from any location. See Viewing Computer Details (page 98). restoring software and migrating personality settings for a whole department. and manage all computer resources across your organization. or vice versa. You can also click File > New > Computer or right-click in the Computers pane and select New Computer. software requirements. Computer icons appear in the Computer pane of the Deployment console where they can be organized into groups. or any other structure to Altiris® Deployment Solution 6. configuration. To assign and schedule a computer in the Deployment Server Console. notebooks. or can be associated with pre-configured computers. Or you can take on big projects. You can quickly modify any computer’s configuration settings or view its complete management history. All computer resources can be accessed and managed as single computers or organized into computer groups with similar hardware configurations or deployment requirements. Click New Group on the console to add a new group in the Computers pane of the Deployment console. Organize computers by department.

handheld. Altiris® Deployment Solution 6. set security. a computer resource is identified in the console with a distinctive icon to display the computer type — Windows desktop or notebook. Manage Servers. See the property pages for modifying Deployment Agent settings. or user with a timed license status. Restore a computer to a previous state. Computer connected to Deployment Server but the user is not logged on. server waiting status. software. add tasks. Or you can view the Computer Properties page for detailed access to a computer’s hardware. run deployment jobs or select from additional management commands. send a file. Computer with a time-limited user license and a user logged on. See Computer Configuration Properties (page 103). Build deployment jobs with one or more management tasks to run on selected computers. Viewing Computer Details In Deployment Solution. You can also view the status of the jobs assigned to the selected computer in the Details pane of a Deployment console. configure property settings. You can deploy and provision computers on a mass scale.meet your needs. See the Deployment Solution Reference. identifying computer type and state. see Computer Filters and Job Conditions (page 83).8 SP2 98 . See Remote Operations Using Deployment Solution (page 127). See Building and Scheduling Jobs (page 147). Build and schedule jobs. chat. Computer connected to the Deployment Server with a user logged in. server. such as the log on status. and assign the job to computer groups. See Computer Properties (page 124). Deployment Solution also manages network or Web servers to administrate high-density server farms or server network resources across your organization. See Deployment Agents on page 112. You can modify computer settings for each computer from the console. and network property settings. View and configure computer properties. The following is a sample list of computer icons displayed in each Deployment console. or Linux operating system — and its current status. To filter computers in a computer group to schedule jobs only to the appropriate computer types. remote control. Perform operations quickly in real-time from a Deployment console. Configure Computer Agents. These computer icons change to convey the state of the computer. Create jobs. See Viewing Job Details (page 147). Jobs can be organized and assigned for daily tasks or to handle major IT upgrades. Run remote operations from the console.

8 SP2 99 . As soon as the computer connects and the Deployment Server recognizes the new computer and changes the icon. A master computer is identified as a computer used to broadcast images to other client computers. Additional icons identify different states of Linux computer deployment. This icon appears if the Workstations check box is selected in Initial Deployment. Click New Group or select New > Computer Group to create a new group. Altiris® Deployment Solution 6. A pre-configured computer with values defined in advance using the New Computer feature. A managed Linux computer connected to the Deployment Server with a user logged on. server icons identify logical server partitions. See Adding New Computers (page 100).Computer not currently connected to the Deployment Server but known to the Deployment Database. Additional computer groups can be added to the Computers pane to organize similar computer types or to list computers of similar departments or locations. See Bay (page 126) for properties and rules to deploy Rack/Enclosure/Bay servers. In addition. 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 icons identify different states of server deployment. See Sample Jobs in Deployment Solution (page 195). A managed server connected to the Deployment Server with a user logged on. Physical view of Rack/Enclosure/Bay components for high-density server systems. A connected handheld computer. These icons appear as physical representations to allow management of different levels of the server structure. A managed computer waiting for user interaction before running deployment tasks.

if Deployment Server recognizes the MAC address provided in a New Computer account or import file. A pre-configured computer account can be associated with a new computer using the Initial Deployment feature. The New Computer icon appears for a new computer if the MAC Address is provided when creating a new computer account using any import or new computer account feature. Using Initial Deployment you can associate new computers with pre-configured computer accounts. Starting up a new computer with the Automation Agent lets you image the hard drive. distribute personal settings and software. Create or import computer accounts from the Deployment console. These newly configured computers appear in the New Computers group. New computers with the Deployment Agent installed are added to the All Computers groups (unless otherwise specified in the Deployment Agent configuration). it automatically associates the user account at startup with the New Computer icon. the computer appears as a pre-configured computer account. As soon as the computer starts up and is associated with a pre-configured computer account. A pre-configured computer account icon appears if specific hardware data (MAC Address) is not known. letting you associate it to a new computer. assign IP and network settings. the configuration settings and jobs assigned to the pre-configured computer account can be associated with the new computer.8 SP2 100 . At startup. You can move the computer to another group if desired. Use Initial Deployment to configure and deploy new computers booting to automation. See Creating a New Computer Account (page 101). See Sample Jobs in Deployment Solution (page 195). Deployment Server recognizes the new computer and the icon changes. Adding New Computers Computers can be added to the Deployment Database using three methods: Install the Deployment Agent. You can pre configure computer accounts by adding names and network settings from the console. About New Computers When a new computer starts up. the computer is added automatically to the Deployment Database at startup. and install the Deployment Agent for new computers. If you install the Deployment Agent to a computer with the operating system already installed. If this value is not provided.See also Deployment Agents (page 112). You can add new computers using the New Computer feature or import computers using a delimited text file. You can create multiple pre-configured computer accounts and associate the account with a new computer when it boots to automation. Pre-configured Computer Account Deployment Solution provides features to create a pre-configured computer account to pre-define a computer’s configuration settings and assign customized jobs to that Altiris® Deployment Solution 6.

you are ready to deploy it because you have done all the work ahead of time. You can also click File > New > Computer or right-click in the Computers pane and select New Computer.computer even if you do not know that computer's MAC address. for example) you know about the computer and apply it to the new computer as it comes online. especially when you need to deploy several computers to individual users with specific needs. Now you can perform an Initial Deployment.MSIs and RIPs based on a user's specific needs. the computer you create or import becomes a virtual computer. bookmarks. To create a new computer account 1. Boot the client computer to automation. Pre-configured computer accounts offer a great deal of power and flexibility. 4. See Computer Configuration Properties (page 103) for a description of the configuration settings. When creating new accounts for computer groups. You can build any job. or run a deployment imaging job on the new computer. When a new computer starts up. and IP address. Example: a user might request Windows 2000 with Office 2000 and virus scanning software installed on the new computer. and assign it to a pre-configured computer account. address books. When the new computer finally arrives. See Importing New Computers from a Text File (page 102). You can also prepare jobs prior to the arrival of the new computer to deploy the computer using customized images. . workgroup name. You can set up as much configuration information (computer name. 3. (Optional) Click Import to add new computers from a delimited text file. Click Add. The pre-configured computer account saves your time because you can configure the computer before it arrives on site. you can automatically assign new names and associate them with existing computer groups or the New Computer group. Click OK. Note If you do not enter a MAC address. Altiris® Deployment Solution 6. and the new computer can connect to the server and become a managed computer. familiar desktop settings) be migrated from the old system.8 SP2 101 . The user also might request that the computer personality (customized user settings. Click New Computer on the console to create a new computer account. you can assign it to this preset account. 2. Creating a New Computer Account You can create computer accounts for individual computers or for computer groups. Enter names and configuration settings for each new computer account using the Computer Configuration screens. This type of computer is known as a pre-configured computer account. including any of the available tasks. A pre-configured computer account icon appears in the Computers pane.

3. Example: enter Sales.imp files) to establish multiple computer accounts in the Deployment Server database. type a base computer name.CSV. a message appears. Click Open. 2. Altiris® Deployment Solution 6. Select a computer group. A dialog appears letting you select import files. . Clear the check box to add names before the computer name. including the New Computers group (empty groups cannot access features).txt. 4. These files can have . Click the Microsoft Networking category and click Define Range. 1. New computers appear as pre-configured computer accounts in the Computers area of the console (as single computers or in groups). Click OK. and any jobs imported from the import file are listed in the Jobs area. 1.IMP extensions. The range of numerals and letters is assigned to the computer name. 5. Select Append to add the range of numerals after the computer name. The example computer names begin with Sales3 and end with Sales7. This is optional. Note Jobs can be added to the import file. b. See Computer Configuration Properties (page 103). If a correctly formatted computer import file is selected. This file contains all configuration data for a new computer.8 SP2 102 . Importing New Computers from a Text File You can import computer configuration data using delimited text files (. Click Associate. a. 2.TXT. or . They can be created and associated with the new computers.csv. Example: enter 3. You can now associate computers in a group (including the New Computers group) with the multiple computer accounts. c. a warning appears. Select the import file. d. including all settings in the Computer Properties of a selected computer. or . In Fixed Text box. If the computer import file is incorrectly formatted. Right-click and select the Configure command. Click File > Import/Export > Import Computers. . informing you that the computer import is complete and identify the number of computers added. Click OK. Type a numeral or letter in the Range Start box to add to the Fixed Text name. Click OK. These computer accounts can be associated with computers in a selected computer group. This creates a unique name for a group of computers starting with the specified character. Enter names and configuration settings for each new computer account using the Computer Configuration screens. stating that the computer import file is incorrect.To create and associate multiple computer accounts You can create computer accounts and automatically assign predefined names.

set. The imported computers appear in the Computers pane of the Deployment console. Edit computer settings by selecting a computer from the list and clicking Properties. Computer Configuration Properties These computer property settings can be viewed.5 format for importing computers.3.xls file in the Samples folder of the Deployment Share.xls file is a Microsoft Excel spreadsheet that lets you add values to each identified column and save the file as a delimited TXT file to import to the Deployment Database. The ImportComputers55. UUID. Modifying Configuration (page 182). Referencing the Sample Import File When creating an import file. consider using a barcode scanning system to collect user information (names. Previous versions of Deployment Solution use the 4. The Computer Properties sheet opens to edit or add values not set in the import file. You can save this information to a file.0 format. and modified when performing the following computer management operations: Adding New Computers (page 100). Depending on the number of incoming computers. The primary lookup key can be the Serial Number. the amount of information you have about those computers. and the needs of individual users. Deploying New Computers on a Mass Scale If you need to deploy large numbers of computers (100 to 5. 4. use either the ImportComputers55. serial numbers. If you are using an import file. Note Altiris Deployment Solution 5. TCP/ IP settings. which can be imported into the New Computers List View. See the sample import file for additional information. 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). Click OK. and application needs) and computer information (MAC address.5 and later use the 5. 5. and other configuration settings. operating system. This is the piece of information that Deployment Server needs to set up a unique computer.000).8 SP2 103 . Altiris® Deployment Solution 6. 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. or MAC address. The ImportComputers55. such as computer name.txt file provides a sample import template you can access to test the Import feature. ensure you know the primary lookup key. Create or edit property settings in a deployment job. user name. asset tags). Asset Tag. 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.txt file or the ImportComputers55.

Set the Windows name of the computer and the Workgroup or Domain settings. Click other category icons to view and set additional configuration properties. the MAC address and other settings. Microsoft Networking Configuration Settings TCP/IP Configuration Settings NetWare Client Configuration Settings Operating System Licensing Configuration Settings User Account Configuration Settings General Configuration Settings The General category provides access to important property settings that are also listed in other configuration categories. After you edit these computer property settings. if available. The serial number of the computer’s motherboard. Set the TCP/IP addresses for one or more network adapters. It includes the name of the computer in Deployment Solution. the computer restarts so that the changes can take effect. MAC address Serial Number Asset Tag Computer Name IP Address Registered User The unique identification address of the network adapter. Set the registered user name and view the hashed installation license key for the installed operating system. the NetBIOS name of the computer.Sample Jobs in Deployment Solution (page 195) configuration settings. Multiple IP addresses are listed in this box. Current IP address of the computer. Set the local Windows user account values. Note The Name box is disabled for multiple computer configuration.8 SP2 104 . The name of the user who registered the operating system software Altiris® Deployment Solution 6. The Windows name of the computer. Field Name Description Provides a name that appears in the Deployment console (not the BIOS name of the computer). Set Novell Directory Services client logon options. The asset tag of the computer. General Configuration Settings Set the most important value from this property sheet. Click the configuration group icons to set additional computer property values.

If you are using Active Directory. you can add computers to a domain and a specified organizational unit (OU). Note The Computer Name box is disabled for multiple computer configuration. Password Description The hash value rendered from the OEM key or 25-digit license key required when installing the operating system. Use Sysprep to generate unique SIDs. Field Computer Name Description This is the NetBIOS name for the computer.Field License key User name Full name. Microsoft Networking Configuration Settings Enter the computer name and workgroup or domain property settings for the managed computer. This can be done by manually running the utility or selecting this feature while installing the Deployment Agent. The full name for the local Windows user account. The password for the local Windows user account. See also Computer Configuration Properties (page 103). The user name for the local Windows user account. The name must be unique in the network and is limited to 15 characters. Altiris® Deployment Solution 6.8 SP2 105 .

Select Token: You can select one of the six tokens from the drop-down list. Selecting this option enables the NIC Number option. Append. You need to specify the NIC number. For new computers. the computer names increment irrespective to the base name. for example: Marketing.MAC address of the computer with NIC specific number. the default value is 1. Result.Marketing6. See also Computer Configuration Properties on page 103. The NIC Number textbox is visible for NIC number input.Serial number from SMBIOS. set a range of names for multiple new computers: Fixed text. which ranges from 1-8. %NICyMACADDR%. Define Range Click to create a sequential range of computer names. Example: Marketing. Select this check box to add the range after the fixed text in the computer name. If you set up two separate name ranges to be assigned by separate conditions. do not set names using multiple Modifying Configuration tasks and assigning the names by Setting Conditions for Task Sets. View an example of the selected names that is assigned to each computer. Selecting this option enables the Select Token option and disables the Define Range option.Field Use Token for computer name Description Select the check box to specify the computer name using tokens. Enter a whole number to add to the fixed text. Workgroup Click and enter the name of the workgroup to place the managed computer. Note This option is applicable for multiple computers and not for single computers. Altiris® Deployment Solution 6. Note When setting name ranges. The Computer Name Range dialog appears..8 SP2 106 . Range start. %NAME%.. If you clear this box the number is added as a prefix to the fixed text. %SERIALNUM%. for example: 1.First 8 characters of actual computer name. %NODENAME%.Complete computer name. Enter the text portion of the name which you want associated with each computer.

Click Advanced to setup IP interfaces. DNS. and function number is the first listed (NIC0 . If you add a new network adapter. device. and WINS.yourcompany.8 SP2 107 . You can remove the new network adapter by clicking Remove. it is configured only with the IP settings listed first.org/New Corporate Computer OU/ Mail Room/Express Mail Servers TCP/IP Configuration Settings Enter TCP/IP settings for one or more network adapters. See also Computer Configuration Properties (page 103). the Remove button is populated. it is enumerated in the order it is detected. The name is used to locate a computer on the network. If a computer in the group has only one network adapter. or the WINS domain name. The network adapter with the lowest bus. If one network adapter uses the native driver and one uses an UNDI driver. When configuring multiple network adapters. For computer groups. they are disregarded. The complete entry to place the computer in the users OU is the following: mjones. If IP settings are provided for additional network adapters not present in the computer. You can enter the fully qualified domain name (example: mjones. the DNS domain name. device.yourcompany. your computer appears twice in the console.myServer. If the bus.com/OU/newOU/users internal. and function information cannot be determined for a network adapter. Add.zero based).com). A list of all network adapters installed in the selected computer. Altiris® Deployment Solution 6. and specify the organizational unit (OU) using this format: OU/ newOU/users.Field Domain Description Enter either the fully qualified domain name. Field Host name Network Adapter Description The DNS name of a device on a network. click Associate to assign a range of pre-defined IP addresses. ensure that one network adapter is not using an Intel Universal NIC driver (commonly called UNDI driver) to connect to Deployment Server. 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.

Click Add to set named interfaces for this network adapter. Reboot After Configuration. See also Computer Configuration Properties (page 103). which denotes that the named interface is operating. Field Interface Name Description Establish Linux-specific IP interface settings. select this option. This box is disabled when creating a Modify Configuration task. Ensure you use the “eth” syntax when naming new interfaces.8 SP2 108 . You can shut down the named interface by selecting Down. The default value of the interface state is Up. Enter the appropriate subnet mask.IP interfaces IP Interfaces (Linux and Windows type only). You are unable to change this number. for example: eth0:1 or eth0:new interface. Use the following IP address.Field Description Description MAC Address. Field IP Address Subnet mask Description Add or modify an IP address common to all interfaces. Obtain DNS server address automatically. TCP/IP Advanced Options . Obtain an IP Address automatically. The MAC address is a unique number assigned to the network adapter by the manufacturer. To restart the computer after configuration. Enter this to add domain suffixes to the root address. Broadcast Address Interface State Altiris® Deployment Solution 6. The MAC address appears in this box when viewing computer configuration settings. Use this tab to add TCP/IP addresses to an existing network adapter card on Linux or a Windows operating system. DNS connection Suffix. Obtain the following DNS server addresses. Enter the Broadcast address for the specified IP interface.

or Use NetBIOS settings from DHCP server option for this network adapter. Note You cannot edit this information in the Windows 98 operating systems. See also Computer Configuration Properties (page 103). Altiris® Deployment Solution 6. Note You cannot edit this information in the Windows 98 operating systems. Append these DNS Suffixes (in order): Add the name of the Domain Suffix and use the up and down arrows to set the DNS suffix search order. or Use NetBIOS settings from DHCP server for this network adapter. DNS Server Address: Add additional Domain Naming Servers (DNS) for this network adapter. See also TCP/IP Advanced Options .Gateway View Gateway addresses. Append these DNS Suffixes (in order): Add the name of the Domain Suffix. which acts as primary address. TCP/IP Advanced Options .WINS Click Add to set a new WINS address.TCP/IP Advanced Options . Static Routes This displays the static route information for the computer you are viewing. Field Gateway DNS Description Add additional gateways for this network adapter. Select the Enable NetBIOS over TCP/IP. WINS Add additional WINS settings for this network adapter.DNS Click Add to set a new DNS address. Use the up and down arrows to move an address to the top of the list. The Deployment Console disables the edit feature on those types of clients. Add additional WINS settings for this network adapter. DNS Server Address: Add additional Domain Naming Servers (DNS) for this network adapter.8 SP2 109 . Disable NetBIOS over TCP/IP. Review all selection by clicking the TCP/IP option on the Configuration page. and use the up and down arrows to set the DNS suffix search order. TCP/IP Advanced Options . Select Enable or Disable NetBIOS over TCP/IP.Static Routes (page 110). The Deployment Console disables the edit feature on those types of clients. Click Modify to edit an existing IP address.

This is the primary login server for the NetWare client. 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) NetWare Client Configuration Settings Set Novell NetWare client values for a new or existing computer. Field Ignore NetWare settings Preferred server Description Select to disregard all Novell NetWare client settings for this computer. Additional gateways required to reach the destination server. server name.Static Routes Field Destination Netmask Gateway Interface Metric Flags (Linux) Description IP address of the destination Deployment Server. Click and enter the name of the NetWare server. Select whether you want to log in directly to a NetWare server or to a NetWare tree in the Novell Directory Service (NDS). Cost associated with the route Enter the flag associated with a linux specific operating system. You can specify the preferred tree. Click and enter the organizational unit context for the user.TCP/IP Advanced Options . Click and enter the name of the user object for the NetWare client. for example: \OneServer. Preferred tree NDS User name NDS Context Click and enter the name of the NDS tree. Clear to specify the required information. IP address for the interface over which the destination can be reached. Altiris® Deployment Solution 6. and NDS context. Subnet mask.8 SP2 110 .

See also Computer Configuration Properties on page 103. and password. full name. See also Computer Configuration Properties (page 103). Operating System Licensing Configuration Settings Enter or view the license information for your Windows operating system software (Windows 98. Enter the alpha-numeric license key. The password for this local Windows user account. Enter a user name. Marketing. Confirm the password for the local Windows user account. Specify the Windows groups that this user belongs to as a comma-delimited list. 2000. Management Altiris® Deployment Solution 6. The full name for this local Windows user account. Field User name Full name Password Confirm Password Groups Description The user name for this local Windows user account.Field Run login scripts Description Select this option to run the NetWare client login scripts. for example: Administrators. Field Registered user Organization License key Description Enter the name of the registered user.8 SP2 111 . Enter the name of the organization. and set standard Windows login options. User Account Configuration Settings Set up local user accounts for the newly imaged computer or when running a configuration task. This is the hash value rendered from the OEM key or 25-digit license key required when installing the operating system. and 2003 Servers). XP.

See Deployment Agent Settings (page 113). and servers.NET Altiris® Deployment Solution 6. Linux. Deployment Agents To remotely manage computers from a Deployment console. The following Deployment Agents reside on the client computer and communicate with the Deployment Server. right-click a computer or group and select Change Agent Settings and click Production or Automation. See Deployment Agent for CE . Select to maintain the user password. See also Computer Configuration Properties on page 103. notebooks. See Boot Disk Creator Help and Install Automation Partition (page 137). and PPC Handhelds.NET (page 122). This Deployment Agent runs on Linux workstations and servers. Prohibit the user from changing the password at any time. To set or modify Deployment Agent settings from the Deployment Server Console. including desktops. Automation Agent Deployment Agent on CE . click Agent Settings.2 operating system.NET 4. Deployment Agents are provided for various computer types. click Tools > Options. This agent runs on the HP T5000 computer devices running the CE .Field User must change password at next logon User cannot change password Password never expires Description Select to force the user to change the password after setting the configuration properties. including Windows.8 SP2 112 . This is done through Boot Disk Creator. The Automation Agent is used when you create configurations to boot client computer to automation. To set or modify agent settings for new computers. See Deployment Agent Settings (page 113). DOS. Deployment Agent on Windows Deployment Agent on Linux The Deployment Agent runs on Windows computers. a Deployment Agent is installed on each computer in the Deployment Server system.

4. Automatically update to newer version of Deployment Agent At times. 1. When the Deployment Agent for Windows is running on a computer. This agent runs on the Deployment Server computer when running Deployment on Notification Server. Click Transport.8 SP2 113 . The agent may be configured incorrectly. The Deployment Server Configuration utility appears. we recommend that all managed computers run the latest version of the Deployment Agent. When the icon is blue. it shows that the client computer is not connected to the Deployment Solution system. Select the Automatically update clients option. the user sees a small icon in the system tray. 3. the managed computers automatically update the Deployment Agent. Click Options. For best performance. This agent runs on the Deployment Server computer when running Deployment Solution on Notification Server. From the computer where Deployment Server is installed. When a Deployment Server is located by the Deployment Agent. 2. the Deployment Server is down. Altiris may update versions of the Deployment Agent to enhance features.Notification Server Client The NS client is an Altiris agent that runs on computers supported by Notification Server. or other network problems exist. the client computer is added as a record to the Deployment Database. When the Deployment Agent for Windows icon is clear. click Start > Programs > Altiris > Deployment Solution > Configuration. Altiris® Deployment Solution 6. Deployment Server Agent Install Deployment Agent to add a managed computer When a Deployment Agent is installed on a computer. the client computer running the Deployment Agent is connected to the Deployment Solution system. Deployment Agent Settings You can set the default agent settings for when new client computers are added to the system that the Deployment Server will manage. When a new version of the Deployment Agent is saved to the Deployment Share file server. it searches across the network for a Deployment Server to attach to.

You can also modify the properties’ settings for the Production or Automation Agent through the Automation Agent. Passwords have no effect on this option. The agent service is started and initialized. 5. Clicking Properties lets you edit the Deployment Agent properties. A connection is made to the Deployment server. You can also see the computer name. To view or modify settings from the Windows client. 3. 2. Click each agent setting tab to set properties. Displays the version and licensing statement for Deployment Agent. no additional data needs to be sent to or from the Deployment Server for the client agent to remain connected. Click OK. View the Deployment Agent log file. When the client agent is first started. To set or modify agent settings in the Deployment Server Console for Windows or Linux clients. if required. Click the Agent Settings tab. 4. Clear the log file that has been created. Altiris® Deployment Solution 6. After the initial connection process is complete.8 SP2 114 . click Tools > Options. right-click the computer and select Change Agent Settings > Production Agent Settings. if you have chosen the option to create a log file. Passwords have no effect on this option. To set or modify agent settings for the Deployment Agent. right-click the Deployment Agent icon in the system tray (or double-click the client icon in the system tray and click Properties). the TCP/IP protocols send an occasional watchdog packet (approximately every 24 hours) to ensure that the connection is still valid. The agent is updated. A TCP socket is created. Select the Force new agents to take these default settings check box to set the Deployment Agent settings for all new computers. IP address. You can also watch Deployment Agent communicate with the Deployment Server. Brings up the Altiris Client Service box to observe the current status of the Deployment Agent. and MAC address. Passwords protect this option. About. Clear log file. A basic inventory of the client is sent to the Deployment Server. Deployment Agent Properties Right-clicking the Deployment Agent icon gives you access to the following options: View status. View log file. multicast address. the agent establishes a connection to the Deployment Server using the following general steps: 1. deployment server connected to. Note If no Deployment Solution traffic is sent to the Deployment System agent.

Enter the IP address or NetBIOS name of the Deployment Server computer. Enable key-based authentication to Deployment Server. This makes the required preparatory changes to the computer before an image is made. This helps keep rogue computers from connecting to unauthorized Deployment Servers. Passwords protect this option. Select this option so that the client receiving the Deployment Agent connects to the Deployment Server you selected to configure. Exit. Uninstall Deployment Agent from the computer. View what network cards are in your computer. Stops all Deployment Agent services from running but does not uninstall Deployment Agent. 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. Enter the port number communicating with the Deployment Server. Passwords protect this option. Server Connection Access Security Log File Proxy Startup/Shutdown Server Connection Connect directly to this Deployment Sever. Change Name in Console. Admin Properties. Select this option to require that the client computers that are trying to connect to the Deployment Server. Quickly go to the Admin Properties page to view or make changes. Ensure that the multicast address and port match those set up on the Deployment Server. Port. Failure to do this breaks the reconfiguration phase when deploying the image using a job.8 SP2 115 . User Properties. Passwords protect this option. Passwords protect this option. Address/Hostname. Quickly go to the User Properties page to view or make changes. Altiris® Deployment Solution 6. Remove. Discover Deployment Server using TCP/IP multicast. This option does not change the NetBios name of the computer or the name of the computer in the database. Change how this computer is listed in the deployment server console. Passwords protect this option. Try using defaults on both the client and Deployment Server if you are having problems connecting. but only changes the name of the computer displayed in the Computers window. 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. Make an image of a computer without using a job. Otherwise. Passwords protect this option. The port number must match the number set on the Deployment Server. The following configuration properties (organized using tabs in the dialog) are included in the Production Agent Settings dialog. Show Network Interfaces. Deployment Agent loads normally the next time you boot the computer.Shutdown for imaging. Passwords protect this option. your clients cannot connect.

Select for the user to be prompted before running the Remote Control commands. 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. Enter the port number distributing the multicast address. Enter the group multicast address. We recommend keeping this setting above 28800. Enter the NetBIOS name of the computer running the Deployment Server. Access Set these commands to control how the client handles requests from the server. This feature overrides the Power Control option from the Deployment Server to Force applications to shut down without a message. Abort files transfers if the rate is slower than. Select to let the administrator to remote control the selected computer. Specifies the number of routers the multicast request can pass through. Select the time for the user to respond and either continue with the operation or abort the operation. TTL. Do not set this option too low—reconnecting to the Deployment Server increases bandwidth when connecting. Prompt the user before performing actions. The Deployment Server closes the connection after the specified time and immediately tries to re-open the connection. Click to continue without receiving a response from the user. making it easier to find the closest Deployment Server. Click to not continue without receiving a response from the user. This forces clients to realize the network is down.Server Name. Preserve bandwidth on slower connections by selecting this option. Select the amount of time you want to wait for a response. Copy file and Run command. Select the Refresh Connection after idle check box and set the refresh time by hours or days. Altiris® Deployment Solution 6. The default setting is to NOT allow the computer to be remote controlled. Shutdown and Restart. Select for the user to be prompted before shutting down or restarting the computer. you need to decide whether to continue or abort. The default checking is of 28800 seconds or 8 hours. Multicast Address. If one of the Prompt the user before perform actions is selected and the user is not at the computer to respond. Select for the user to be prompted before running a program or executing file copy commands Remote Control.8 SP2 116 . and select one of the following: Continue the operation. Time to wait for user response. which saves bandwidth when running deployment tasks on slower connections. You can set a default time before running or aborting the commands. Abort the operation. Refresh connection after idle. 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. Port. Allow this computer to be remote controlled.

Select to require encryption between the managed client computer and the Deployment Server. Hide client tray icon. Security This page lets you secure data between the Deployment Server and the Deployment Agent. If selected. Click to save information to a log file. Require encrypted session with any servers. informational errors. You can maximize the size of the log file to save all selected data. which includes only the User Prompts and Remote Control tabs on the Altiris Client Settings dialog. You can save a text file with log errors. Encrypt session communication with Deployment Server. Save log information to a text file. The default is to save the log file to the \Program Files\Altiris\AClient\AClient. the Deployment Server does not communicate with the Altiris Client on the managed client computer. Enter the name and path of the log file. 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 the days and set the start and end times when access to the Deployment Agent is denied. To enable encryption protocols. File name. they will have rights only to open the User Properties. the client computer can connect (but is not required to connect) using encryption. If the log exceeds the specified size. Note Selecting encryption options slows down the communication path between the agent and the Deployment Server. Altiris® Deployment Solution 6. This lets encrypted data transmissions between the Deployment Server and the Deployment Agent on the client computer. you must open the Deployment Configuration tool and select the Transport tab.Select when the Deployment Server is denied access to the Deployment Agent. Select the Allow encrypted sessions with the servers check box to let Deployment Server transmit using encryption protocols. and debugging data using this dialog. Select to hide the Altiris Client icon in the system tray of the managed computer. If this option is selected and the option to allow encryption in the Deployment Configuration tool is not selected. Enter the password in the Password field and reenter the password for confirmation in the Confirm Password field. Select to ALLOW encryption from this managed client computer to the Deployment Server.log file. letting you save different types and levels of information to the log files. If you hide the icon. Select to let users on the managed computer to access the Admin properties only if they enter the set password. you are required to run AClient.exe -admin to view and modify the complete administration properties from the managed client computer. the older data is dropped from the files. Log File The Log File property page controls how data is logged and saved in a Deployment Server system. If the box is selected and the user does not know the password. Password protect Admin properties from user.8 SP2 117 .

Select this option to prompt for a boot disk while doing any automation jobs. Log errors. Startup/Shutdown Delay starting jobs after system startup. Note If the log exceeds the specified size. 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. the option Save log information to a text file is cleared. Use this tab to save the Deployment Agent log file. Select it to enter a file name for the log and the maximum size for the log file. Specify the Windows boot drive.Maximum size. Send multicast advertisement every.8 SP2 118 . By default. minutes. identifying the type of traffic this managed computer forwards from the server. Set the time by seconds. Advanced Altiris® Deployment Solution 6. or days for managed computers to delay jobs until after system startup. Specify the drive that the client computer boots from. Forward Wake-On-LAN packets. remote networks on the other side of a router or switch cannot receive multicast or Wake On LAN packets from the Deployment Server. the older data is dropped from the files. Force all programs to close when shutting down. Select this option to shut down applications when using Power Control features. Set the time by seconds. Select this option to save only the errors returned when running a job or operation between the Deployment Server and the Deployment Agent. Log debugging information. minutes. or days for managed computers send multicast advertisement. A managed client computer setup as a multicast proxy simply acts as a Deployment Server and advertises the server’s name and IP address through multicasting. Synchronize date/time with Deployment Server. The user is still prompted to Abort or Continue the shutdown. Enter the maximum number of bytes for each log file. Proxy Typically. Log informational messages. hours. Select if you want the managed computer to forward Wake on LAN packages. 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. The default is the C drive. so it is recommended to provide maximum file size. Set these options to control how the managed computer acts as a proxy agent. Forward Deployment Server discovery multicast packets. Setting the managed computer as a proxy client computer forwards or re-creates the multicast packets. Or you can set the managed computer as a proxy to send Wake On LAN packets. Select this option to save a list of procedural steps run on the client computer. Select this option to list comprehensive debugging information in the text file. hours.

When a new client computer connects. letting you deploy and manage computers just like the Deployment Agent for Windows. with the following exceptions: Deployment Task Create Disk Image Distribute Disk Image Scripted OS Install Distribute Software Capture Personality Distribute Personality Change Configuration Run Script Copy File Shutdown/Restart Deployment Agent for Windows Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Deployment Agent for Linux Yes Yes Yes Yes No No Yes Yes Yes Yes Deployment Agent Settings for DOS You can configure property settings for the Automation Agent for specified computers or computer groups. To set or modify agent settings for a specific computer. and runs management processes as directed from a Deployment console. click Tools > Options. Select this option to disable the direct disk access for Automation communication. To set or modify agent settings for ALL computers. The agent collects and sends data from the managed computer to the Deployment Server system. See Installing Deployment Agent on Linux (page 350) for additional information.Disabled direct disk access for Deployment Agent for DOS (BootWorks) communication. Each client computer still has the capability to maintain its unique settings for the Deployment Agent for DOS as set in the Boot Disk Creator. it receives the default agent settings from Deployment Server for drive mappings. Automation Agent Settings include the following property settings: Altiris® Deployment Solution 6. authentication. You can remotely maintain important agent settings and update settings as required from the console. click Agent Settings > Change Default Settings. installs packages. executes deployment tasks sent from the server. right-click the computer icon and select Change Agent Settings > Automation Agent in the Deployment Server Console.8 SP2 119 . Deployment Agent for Linux The Deployment Agent for Linux is an agent software that runs on managed Linux computers. and LMHost entries. A Linux managed computer is identified in the Deployment console by unique Linux icons reflecting deployment and process status.

Drive Mappings (page 120) Authentication (page 120) Network (page 120)

Drive Mappings
Set drive mappings used by the Deployment Agent for DOS 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. Enter the drive letter and volume of a shared folder, for example:

F: \WebDeploy\Image files.
Note You must select a shared folder in this field. From the browse window you can select any type of folder, but the Deployment Agent for DOS only maps to and accesses files from a shared folder. Path. Enter a UNC path. See also Deployment Agents (page 112).

Authentication
Provide the login credentials that Deployment Agent for DOS requires to map network drives. The associated credentials for each network drive must have the rights that the Deployment Agent for DOS requires administrative rights to access files. Domain/Workgroup. Enter the name of the Domain or Workgroup of the user that the Deployment Agent for DOS uses to log on as to map the network drives. User name. Enter the name of the user that the Deployment Agent for DOS logs on as to map the network drives. Password. Enter the password. Confirm Password. Retype the password for confirmation. See also Deployment Agents (page 112).

Network
These settings let you match the IP address with the computer name, as maintained in the LMHosts file in the Deployment Agent for DOS partition. 1. 2. 3. Click Add. The Add LMHosts Entry dialog appears. Enter the Computer Name. Enter the name of a computer to associate with an IP address. Enter the IP Address. or Click Lookup IP. This automatically populates the field with the IP address of the entered computer name. 4. Click OK.

Altiris® Deployment Solution 6.8 SP2

120

See also Deployment Agents (page 112).

Remote Desktop Connection Client
The option to remotely connect to a Vista computer using the Remote Control option has been disabled. You cannot use the Remote Control option for a Vista computer. However, a new option has been added. You can connect remotely using the Remote Desktop option for a Vista computer.

To remotely connect to a Vista computer
1. 2. Open the Deployment Console and right-click the Vista computer you want to remotely connect. Click Remote Desktop. The remote desktop window for the computer appears. The remote desktop connection is established to the Vista computer.

To remotely connect to multiple computers using the Remote Desktop option
1. 2. Open the Deployment Console and right-click the computer you want to remotely connect. Click Remote Desktop. The remote desktop window for the computer appears. The remote desktop connection is established to the computer.

To remotely connect to multiple computers
1. 2. 3. Open the Deployment Console and right-click the computers you want to remotely connect. Click Remote Control. The Remote Control Options dialog appears. Select Control each client separately in its own window to remote control each computer separately. or Select Control all clients together, in the same window, using the following master to remote control the selected computers together and select the master computer. 4. Click OK. The remote control connection is established for the computers.

Agent for Macintosh Management
The Agent for Macintosh management can be installed on Macintosh Platforms 10.2 and later. It lets the running of scripts, configuration changes and basic Deployment Solution inventory. The agent is installed on Macintosh platforms by the Deployment Console through an Agent Installer. The agent can also be removed through a script or a remote agent install/uninstall mechanism. Macintosh computers have the operating system already installed. You can install the agent on the Macintosh computers through the Deployment Console and the remote agent installer. After the agent is installed, you can schedule a job to copy files from the Macintosh computers to a remote file share.

Altiris® Deployment Solution 6.8 SP2

121

You can run a script that makes a configuration change to the Macintosh operating system. You can also run a script that copies an install file from a remote share and another script that installs the package to that computer.

Deployment Agent for CE .NET
Deployment Solution manages Hewlett-Packard T5000 computer devices running the Windows CE .NET 4.2 operating system. These computer devices ship with the Deployment Agent for CE .NET already installed and appear in the Deployment Console as managed computers when attached to the network. The Deployment Agent performs the following limited tasks on the Windows CE .NET platform: Modify Computer Configuration (the computer name and TCP/IP Setting only) Distribute software (.cab and .exe files) 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 through Windows and Linux agent settings Additional features included with other Deployment Agents are not supported in the Deployment Agent for CE .NET.

To install the Deployment Agent for CE .NET if deleted
If the Deployment Agent for 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 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.1.xxx.exe install Notes for Deployment Agent for CE.NET
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 let more than half of the memory to be allocated to Storage Memory, you can 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###BOT_TEXT###lt;Embedded BootWorks Package.exe>. This installs the Automation Agent and leaves 1 MB of free disk space on the device. If the slider shows less than half the memory available allocated to Storage Memory, Windows CE may not restart.

Altiris® Deployment Solution 6.8 SP2

122

Another option for freeing up additional disk space is to uninstall the pre-installed HP applications, letting you 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, an Error 112 may occur. See also Deployment Agents (page 112).

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 turns gray. The computer should reconnect and its icon color returns to its original active status color.

Reject or Retrieve a Rejected Computer
If a computer 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 are denied. Although the computer is not deleted, any history or schedule information associated with the computer is deleted. 1. 2. 3. 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. 2. 3. 4. Click View > Rejected Computers. From the list, select the computer you want to retrieve. Click Accept Computer(s) to remove the computer from the rejected list (this doesn’t delete the computer, just removes it from the list of rejected computers). Click Yes to confirm the action, click Close.

This client computer may now be managed from within the Computers pane. Connection requests from this client computer are now allowed. See also Deployment Agents (page 112).

Altiris® Deployment Solution 6.8 SP2

123

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 Computers pane, or right-clicking and selecting Properties, or clicking the icon in the toolbar.

General

Services Devices Location Bay Lights-Out

Hardware Drives Network Configuration TCP/IP Applications

General
View or change the name of the computer as it appears 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 (page 103).

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 (page 103).

Drives
View information about each drive on the computer. If you have multiple drives, you can select a drive from the list to view its settings, such as the capacity, serial number, file system, volume label, and number of drives installed.

Altiris® Deployment Solution 6.8 SP2

124

See also Computer Configuration Properties (page 103).

Network Configuration
View Microsoft Networking, Novell Netware settings, and user information for the selected managed client computer.

See also Computer Configuration Properties (page 103).

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 to modify settings (see Configuring Computers on page 130).

See also Computer Configuration Properties (page 103).

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 (page 103).

Services
View the services installed on the computer as well a description, start type, and path for each service.

See also Computer Configuration Properties (page 103).

Devices
View the devices installed on the computer, including display adapters, disk drives, ports, storage volumes, keyboards, and other system devices.

Altiris® Deployment Solution 6.8 SP2

125

See also Computer Configuration Properties (page 103).

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 (page 103).

Bay
View location information and other properties for Rack / Enclosure / Bay components for high-density and blade servers. Set rules for automatic re-deployment of blade servers based on physical location changes. This property is available only to systems using blade servers.

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
Re-Deploy Computer

Action
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 129.) All deployment tasks in the bay's history are 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 Ignore the Change

The server processes any specified job. Select a job to run automatically when a new server is detected in the bay. 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), the established process for managing new computers is executed. (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.

Wait for User Interaction

Altiris® Deployment Solution 6.8 SP2

126

See also Computer Configuration Properties (page 103).

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 (page 103).

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.

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 (page 129). View, print, delete, and save to file a history of deployment tasks. See Viewing a Computer’s History (page 129). Set network and local configuration properties for each computer, including computer name, IP address, domains, Active Directory context. See Configuring Computers (page 130). Select a computer and image its hard disk. This creates and stores the image to distribute now or later. See Quick Disk Image (page 130). Wake up, restart, shut down, and log off remotely. See Power Control (page 130).

History Configure

Quick Disk Image Power Control

Altiris® Deployment Solution 6.8 SP2

127

Remote Control

Open a remote control window directly to a selected client computer. Investigate problems directly from your console. See Remote Control (page 131). Type and run commands remotely. See Execute (page 135). Copy selected files, directories, or entire directory structures and send them to the selected computer(s). See Copy File to (page 187). Start an individual chat session with one or more selected client computers. Communicate actions or query for symptoms during administration. See Chat on page 136.

Execute Copy File to

Chat

ADVANCED >
Clear Status Prompt User for Properties Reset Connection Install Automations Get Inventory Clear computer status as shown in the title bar of the List View. Query the user for personal information. This feature sends a form to the user to fill out. See Prompt User for Properties on page 136. Disconnect and reset the connection between Deployment Server and the Deployment Agent on the selected computer. Embed automation partitions onto the selected computer’s hard disk to enable a managed computer to run automation tasks. Update property settings for a selected computer. These inventory settings can be viewed in Computer Properties on page 124. 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 Install BIS Certificate Remove BIS Certificate Apply Regular License New Job Wizard New Group New Computer Rename Delete Change Agent Settings Refuse communication with the selected computer. Install a BIS certificate for the selected computer. Remove a BIS certificate from the selected computer. Apply a permanent license if a client computer is using a timelimited license or requires an updated license. Open this to schedule deployment jobs for the selected computer. See New Job Wizard on page 148. Click to create a new computer group in the Computers pane. Create a new computer account. See Adding New Computers on page 100. Assign the computer or group a new name in the console. Rightclick a computer or group to edit in the Computer pane. Delete a computer, a computer group, or any combination of computers and groups from the database. Update property settings for the Deployment Agent running on selected computer(s). See Deployment Agents on page 112.

Altiris® Deployment Solution 6.8 SP2

128

Security Properties

View security settings for the selected computer(s). See Security in Deployment Solution on page 89. View computer configuration and network properties. See Computer Properties on page 124.

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 computer’s past deployment history appears in the Restore Computer dialog, where you can restore a computer by selecting the tasks from its history file. You can 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 appears with a list of previous tasks with check boxes.

2. 3. 4. 5.

Click the Show only list box and select the type of tasks to be 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 155). Click Finish.

When you finish this computer operation, a new job appears in the Jobs pane of the Deployment console under the System Jobs > Restoration Jobs folder. The job name has a generic format of Restore: <computer name>.

Viewing a Computer’s 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 computer’s history, cannot access this option. 1. Right-click a computer and click History. The History of <Computer Name> dialog appears with a list of previous tasks, including when the task was scheduled, its deployment status and other deployment information. 2. 3. 4. 5. 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 (page 127).

Altiris® Deployment Solution 6.8 SP2

129

Configuring Computers
From the Operations menu you can enter and modify configuration settings for computers. See Computer Configuration Properties (page 103) for complete information about configuration settings. 1. Right-click a computer and click Configure. The Computer Configuration Properties dialog appears. 2. 3. 4. 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 (page 127).

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 an Altiris PXE Server. 1. Right-click a computer and click Quick Disk Image. The Schedule Computers dialog appears. See Scheduling Jobs (page 155). 2. 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 does 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 appears in the Jobs pane of the Deployment console under the System Jobs > Image Jobs folder. The job name has a generic format of Create Image: <computer name>. See also Remote Operations Using Deployment Solution (page 127).

3.

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-On-Lan 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 on the toolbar.

1.

Right-click a computer and select Power Control. A secondary menu appears with these options:

Altiris® Deployment Solution 6.8 SP2

130

the user is prompted to save work before the power operation is continued. For NICs and operating systems that support Wake on LAN Power Management features. You have to enable this feature for some computers in their BIOS. Click to shut down the selected managed computer. Select a Power Control option. Select Force Applications to close without a message box to shut down immediately without prompting the user. A Confirm Operation dialog appears. If you do not select Force application to close without a message. Restart Click to reboot the selected managed computer. See also Remote Operations Using Deployment Solution (page 127). Remote Control Remote Control is a computer management feature built in to the Deployment Server Console.8 SP2 131 . Example: 3Com NICs have an extra header cable that enables Wake on LAN. you need to go to Properties of the network adapter driver and select the Power Management tab. Altiris® Deployment Solution 6. It lets you control all types of computers to view problems or make immediate changes as if you were sitting at the managed computer’s screen and using its keyboard and mouse. Click to log off the selected managed computer. Click Yes. 3. Check the documentation that came with your network adapter for more information about Wake on LAN. Shut down Log off 2. Select Force Applications to close without a message box to restart immediately without prompting the user. Select Force Applications to close without a message box to log off immediately. Click the Allow this device to bring the computer out of standby option for this device to bring the computer out of standby status. Select this command to start a computer that has been turned off. Select the Force application to close without a message option to shut down users without a warning. Notes Your operating system and network adapter must be capable of recognizing and processing the Wake on LAN packets. Nonembedded network adapters must be properly configured.Wake up The Wake Up feature is hardware-dependent and is only available for inactive computers.

8 SP2 132 . Note The managed computer must be running Windows 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 (page 133). The client and Deployment Server Console must be able to communicate to each other through TCP/IP. Remote Control also provides Chat. the Deployment Agent icon in the managed computer’s system tray flashes alternate icons. Before you can remote control a managed computer: The managed computer must have the Altiris Agent for Windows installed and properly set up. To remote control a managed computer 1. Click to update the screen view of the managed computer. Note You cannot disable the flashing eye icon while the computer is being remote controlled. Note If you cannot perform a remote control operation from the selected managed computer. Copy File to. Refresh CTRL+ALT+DE L Altiris® Deployment Solution 6. Right-click a computer and click Remote Control. Click to select restart or logon options for the managed computer. you can change this client setting by using the Remote Control options in the Change Agent Settings command. The client must have the appropriate Proxy option checked in Altiris client properties. This starts a chat session between the console computer and the managed computer. and CTRL+ALT+DEL features to assist in administrating managed computers from the console. See Deployment Agent Proxy (page 118) options. 2. The chat session opens a chat window that lets you send messages back and forth between the Console and the managed computer. The default setting is to not allow remote control of the managed computer. This opens the Remote Control window displaying the managed computer’s screen. From the Remote Control window you can execute the following commands: Toolbar Chat Click to open a chat session with the selected managed computer. If you are controlling multiple computers in a single window and start a chat session.When a managed computer is being remote controlled. the chat session is only between the Console and the master client.

Destination path. If this option is not selected. Encrypt Data. Source filename. See Remote Control Properties (page 133). the client display image becomes the same size as the Remote Control window. Click to specify the color depth (number of colors) used by the Remote Control window. Select to compress the file during the copy process to decrease network traffic. Select to encrypt data package for security. You can also drag entire folders from the Console computer to the remote control window. this dialog sends a file to the master client only.Toggle Control Control menu Disable Input from the Client Close Window View menu Refresh Fit to Window Click to change between control access of the managed computer (default) or view access only of the managed computer. Enter the name of the source file to be copied and the destination path on the managed computer. If this option is selected. Enter the path where you want the file to reside on the managed computer. Click to specify the width and height of the image that represents the client display. Altiris® Deployment Solution 6. which copies the files to the remote client computer. Select required compression and encryption options. Send Files during Remote Control Click to send files to the managed computer being remotely controlled. Click to prohibit the user of the managed computer from using the keyboard or mouse during the remote control session.8 SP2 133 . Color Depth Properties 3. Compress Data. The benefit of lower colors is improvement in speed. Click to refresh the view of the screen. See Remote Control Properties (page 133). the image retains the size of the client display. Remote Control Properties Color Depth. Use specific image resolution. There is no benefit to setting a color depth on the Remote Control window greater than that of the managed computer. click Control > Close Window in the Remote Control window. To end a Remote Control session. Enter the name of the file to be sent. Click to close the remote control window of the managed computer. This setting applies only to the Remote Control window at the console. If you are controlling multiple clients within a single window. not the display of the managed computer.

select the Remote Control commands option. Also. 2. Under the Choose the commands you would like to be prompted before executing options. Click either Continue the operation or Abort the operation.Update interval. A new window appears for each selected computer. In certain environments. To lock the keyboard and mouse during a remote control session. click the User Prompts tab. 4. Note After selecting this option (either enabling or disabling the keyboard and mouse) you must restart the 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). The more frequently the display is updated. 5.8 SP2 134 . b. This is optional. Set Remote Control Permissions Deployment Solution provides multiple features for ensuring privacy and security when a managed computer is remotely controlled. using a prompt to ask for permission might not be preferred. This provides an opportunity for the user to allow or reject the request. Altiris® Deployment Solution 6. such as a lab or classroom. the more computers you include in the session the larger the bandwidth over the network. Start Multiple Sessions You can manage multiple computers using the Remote Control feature. 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. Select to refresh only the selected window in the remote control session. Specify the number of seconds you want the prompt to wait. After opening the Deployment Agent property page. Before a managed computer can be remotely controlled. Select Allow this computer to be remote controlled to provide access from the Deployment Server Console. This option works only on Windows 2000/XP/2003. select the Enable keyboard and mouse driver box. However. 3. This can be done using a Power Control operation. 1. specify what will happen after the prompt time is up. the more bandwidth is required. Open a separate Remote Control window for each managed computer. select the Remote Control tab. Only update foreground window. Right-click each computer and select Remote Control. Select to specify how often the image in the Remote Control window is updated (in milliseconds). a. If you want the user to be prompted before a remote control session begins. the Remote Control preferences on the Deployment Agent for Windows must be set to allow remote control access. Click OK. To remotely set security options on each managed computer.

you are asked to select a master computer. See also Remote Operations Using Deployment Solution (page 127). 2. click User and enter the user name and password. This option runs with the current user credentials. Altiris® Deployment Solution 6. clicking Operations > Execute from the menu. Type a command you would like executed on the selected remote computer(s). Execute Send a command from the Deployment console as if you were entering a command from the command-line prompt on the client computer. Right-click a computer group icon and select Remote Control. however all actions taken from the console also run on the other computers in the group. User Account Use this dialog to run a script using another local user account. individual windows appear for each computer. You can log in with another user name and password with rights to run an execute command. To run the command as another user on the managed computer. This is the default option. See also Remote Operations Using Deployment Solution (page 127). Run with the following credentials. All computers in the group should be similar in configuration to work properly.Open a Remote Control window for a group of managed computers. 1. Run with default security credentials. or clicking the icon in the toolbar. See Copy File to (page 187). The Remote Control Options dialog appears with options to Control each client separately in its own window or to Control all clients together. Execute a command to a client computer by right-clicking a computer icon in the Computers pane and selecting Execute. Example: type regedit to open the Registry on the computer. Note If you are controlling multiple computers in a single window. use the Copy File to feature. Click this option to log on with another user name and password. The master computer is the computer that appears in the Remote Control window. To end a Remote Control session. or select from a list of previously run commands. click Control > Close Window. If you select to control clients together. If you select to control clients separately. If you want to send a file to multiple clients at the same time.8 SP2 135 . you can send a file only between the console and the master client.

Open a chat session. See also Remote Operations Using Deployment Solution (page 127). Prompt User for Properties This feature lets an administrator prompt a user for computer location and user information. 3. From the Deployment Server Console. Click OK. The Chat with <computer name> window appears identifying the computer you are sending messages to. 2. A dialog appears in the Deployment Server Console with a list of properties. select an individual computer or a group of computers to open an individual chat session with each logged-in user. The properties selected in this dialog are active on the property form sent to the user. The information supplied in this form appears in the Location properties in the Computer Properties dialog. 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. right-click a computer and click Advanced > Prompt User for Properties. Type a message in the lower text box. Select the properties to prompt the user. 1. Altiris® Deployment Solution 6. Note All properties are selected by default. or clicking the icon in the Remote Control window. The properties form appears for the logged-on user of the computer. Open text messaging with a user by right-clicking the computer icon in the Computers pane and selecting Chat. letting the user type information for the selected properties. you must deselect the properties you don’t want included when the client is prompted. The exchange of text messages appears in the upper text box. In the Computers pane of the Deployment Server Console. asking for location properties.Chat You can communicate with managed computers using the Chat text messaging system. 2. 3. To prompt a user for location properties 1.8 SP2 136 . Click Send or press <Enter>.

the name in the Computers pane of the Deployment Console also changes. You can have multiple tasks within a deployment job. When the Deployment Server sends a deployment job. These settings are stored directly to the Deployment Database. See Boot Disk Creator Help. or one of DOS. Linux. If the user changed the computer name.8 SP2 137 . the Pre-boot Operating System page appears for you to select a default pre-boot operating system. Run script Create disk image Distribute disk image Scripted OS install During the Deployment Server installation. See also Chat (page 136) and Remote Operations Using Deployment Solution (page 127). See Automation Pre-boot Environment in the Deployment Server Reference Guide. the Location properties in the computer properties fields is updated for the selected computer. If you are running Altiris PXE Servers. Install Automation Partition When the Deployment Server sends a deployment job to client computers. or Windows PE. depending on the task and end result you want. With an embedded (recommended) or hidden automation partition installed on the client computer’s hard disk. tasks within the job can be assigned the default automation pre-boot environment. You can install additional pre-boot operating system files through Boot Disk Creator. you do not need to install an automation partition on each client computer’s hard disk. The following are the automation tasks you can add to the deployment jobs.When the user enters information and selects OK. PXE-enabled client computers search for an Altiris PXE Server to receive the boot menu options and the boot menu files that are required to boot to automation. which is used by Boot Disk Creator to create the configurations that boot client computers to automation. and each task can be assigned to run in a different automation environment. deployment jobs can run automatically. Altiris® Deployment Solution 6.

Select either Production Agent or Automation Agent.To install an automation partition 1. You can set properties for the Production Agent (Deployment Agent). Edit the properties settings. Right-click a computer and click Advanced > Install Automation Partition. the client computer reboots automatically. 3. To change agent settings 1. deploy and manage network and Web servers. and specific vendor server models. and quick server restoration from a deployment history give you new tools to manage all servers throughout your organization. and manage servers throughout their life cycle. right-click a computer and select Change Agent Settings. From the Computers pane. the icons change to identify the status and state of the computer. 2. you can configure new server hardware. Change Agent Settings This feature lets you modify most of the agent settings for a selected computer or computer group. After the installation completes. such as user logged on or Server Waiting. Features like rules-based deployment. multiple processors. From the Deployment Server Console. The Automation Agent you selected installs as an embedded partition on the client computer’s hard disk. or any Linux operating system). Select the pre-boot operating system environment you want to install from the drop-down list. Like all managed computer icons. Windows Server 2003. You can now run automation-specific deployment tasks this computer. 2. Click OK. Note Servers are recognized by their operating system (such as Windows 2000 Advanced Server. support for remote management cards. install operating systems and applications. such as enhanced task logging and history tracking features to let you recall administrative actions and quickly redeploy mission-critical servers. Manage Servers from the Console. And because servers are mission-critical. Click OK. Altiris® Deployment Solution 6. Deploying and Managing Servers Deployment Solution provides additional features to remotely install. The Deployment Server Console includes features specifically designed for deploying and managing servers. Servers are identified in the Computer pane with distinctive server icons. 3.8 SP2 138 . you can set up a system to quickly deploy new servers or automatically re-deploy servers that have failed. 4. or for an Automation Agent.

You can deploy multiple tasks per deployment job and boot to DOS multiple times when configuring and deploying a clean server. Server Management Features Deployment Server provides various features for deploying and managing servers. Server icons. Deployment Server provides property pages to access and configure multiple network adapters remotely from the console. and track each job to provide a history of tasks for redeploying a server. Deployment Server also lets you view and debug each step in the deployment script. Enhanced scripting capabilities.8 SP2 139 . See Scripted OS Install (page 168). Deployment Agents include an option to disable this feature (it is off by default). Support for multiple network adapter cards. Deployment Server provides serverspecific features to automatically deploy new servers and maintain existing servers. Servers are essential to any organization and require special planning and management strategies. The Deployment consoles shows the icons to identify servers across the network. Synchronized server date and time. Deployment Server automatically sets the server’s date and time after installing or imaging (as part of the configuration process). Altiris® Deployment Solution 6. Server Deployment Options Deployment Server includes features to automatically reconfigure and redeploy new servers. unattended installs across the network for both Microsoft Windows and Linux servers. 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 in a waiting state. See Server Deployment Options (page 139). Because servers may require more than one network interface card. you can (1) safeguard against mistaken disk overwrites.Set Server-specific options. or (2) run automatically for every server not identified as a managed computer in the database. Follow steps to create answer files and set up operating system install files using a wizard. These features are supported for client and handheld computers as well. Run Scripted Installs. Execute scripted. Indicates a server is disconnected from the console. but are essential in deploying servers. These contrasting settings are based on polices you define for managing servers in your organization. Like other computer icons in the console. If you are using Initial Deployment to automatically re-image new servers or run installation scripts. See TCP/IP Configuration Settings (page 107).

Select Change Default Settings. Altiris® Deployment Solution 6. Select the BootWorks tab. Click the Advanced tab. a message appears stating that no BootWorks partition or PXE stamp is found. Initial Deployment runs automatically for every identified server.Example: if you rely on PXE to boot the new server and you want to deploy new servers automatically without halting the process. Halt the Initial Deployment of Servers When a server boots from the Altiris PXE server or from Automation (if the option is set). Click on Start > Programs > Altiris > PXE Services > PXE Configuration Utility. Clear BootWorks Prompt for Remote Install When you run a deployment job on a computer where the Deployment Agent has been remotely installed. 5. It waits until a boot option is selected from the client computer. Select the Agent Settings tab. 2. Click the DS tab. 2. Initial Deployment does not run for any computer identified in the console as a server. In the lower section. which delays executing the scheduled job as part of an automated redeployment process. 3. Select a pre-boot operating system from the Initial Deploy boot option dropdown list. 6. the server attempts to install but does not run automatically using default settings. You can change the default setting in the PXE Configuration Utility to allow Initial Deployment to run automatically and not sit at the prompt.8 SP2 140 . 5.The Altiris Program Options dialog appears. Change PXE Options for Initial Deployment If installing a server using an Altiris PXE Server. you need to set the options in the Advanced section of Initial Deployment. Click the Servers check box and click OK. 1. Select Tools > Options. Click Initial Deployment and select Properties. select Never prompt me from the list. Click Save. The message remains open until the user clicks OK on the message dialog. Click Execute Immediately. if you want to ensure that the server waits before being deployed (or waits a set time before proceeding) to avoid erroneous redeployment. 6. Click OK. To fix this delay: 1. Deployment Server recognizes it as a new computer and attempts to configure the computer with Sample Jobs in Deployment Solution. 4. In contrast. Click OK. you must change the default settings in the PXE Configuration Utility. 4. Initial Deployment includes a feature to prohibit servers from being deployed automatically. 3. 2. 3. 1.

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. Initial Deployment setup: Clear the Servers check box in the Advanced dialog. See Bay (page 126) for properties and rules to deploy Rack/Enclosure/Bay servers. the Bay object is identified in the physical view). and patches are applied to the new server from the history of jobs assigned to the previous server blade. letting you replace any downed server and get it back on line quickly. To Create Virtual Bays: Set up Virtual Rack/Enclosure/Bays for Hewlett-Packard Rapid Deployment Pack installations of Deployment Solution. 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). Managing Server Blades Deployment Solution lets you manage high-density server blades with Rack/Enclosure/ Bay (R/E/B) hardware and properties. both the Initial Deployment and Virtual Bays features can be set up to automatically run configuration tasks and deployment jobs. or to a specific blade server in the Bay. 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. both Sample Jobs in Deployment Solution and Server Deployment Rules can be set up. From the Deployment Console you can deploy and manage these space-efficient server blades using the physical view to assign jobs to the Rack. or Bay level of the server cluster.8 SP2 141 . 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. Managing New Server Blades Deployment Solution lets you automatically deploy. the Enclosure. including Sample Jobs in Deployment Solution.Following these steps ensures that the BootWorks message does not appear and things move forward when a job is scheduled. the Create Virtual Bay feature executes and Initial Deployment does not execute. software. Altiris provides fail-safe features to ensure that no server is mistakenly overwritten and ensures that all disk images. Using Deployment Solution. Virtual Bays Hewlett-Packard blade servers now have a Virtual Bay feature that lets you pre-assign deployment jobs to the Rack. configure and provision new server blades using a variety of features. data. or you can manage each server blade directly from the logical view. Any Altiris® Deployment Solution 6. However. and Server Deployment Rules. when both are set up the Server Deployment Rules executes and Initial Deployment does not execute. Enclosure.

Enter or edit the name of the Enclosure. if you create Virtual Bays with fewer bays (8) and install an enclosure with additional bays (20). Select the Server Deployment Rules to run on the Bay when a new server blade is installed.) The Virtual Rack/Enclosure/ Bay icons change from virtual icons to managed server icons in the Deployment console as live blade servers are inserted and identified by Deployment Solution.com/servers/ rdp). you need to recreate the virtual bays in the enclosure (right-click the enclosure name in the physical view and click New Virtual Bays). with all subordinate Enclosures and Bays also identified.8 SP2 142 . Select an existing job to run when the pre-configured computer account is associated with a new server blade. Server Change rule.hp. Hewlett-Packard Server Blades Hewlett-Packard high-density blade servers can be deployed and managed from the Deployment console. See also Managing New Server Blades (page 141). Enter or edit the name of the Rack. For HP blade servers in the physical view the Rack name can be a custom name in the console. These names are collected from the SMBIOS of the server blade and appear in both the physical and server views within the Computers pane of the Deployment console. the excess virtual bays are truncated automatically. Note If you create Virtual Bays for an enclosure (such as the BLe-class with 20 bays) and if another model of server blade with an enclosure containing fewer bays is connected (such as the BLp-class with 8 bays). Enclosure name.HP blade server can have predefined deployment jobs and configuration tasks associated with it to execute automatically upon installation. Initial Job. Enclosure type. The following HP server blades are supported: HP Proliant™ BL e-Class Proliant™ BL 10e Proliant™ BL 10e G2 HP Proliant™ BL p-class Proliant™ BL 20p Proliant™ BL 20p G2 Proliant™ BL 40p HP blade servers let you employ all features provided in the Deployment Console when you install the HP Proliant Essentials Rapid Deployment Pack (see www. Example: <rackName> <enclosureName> <bayNumber> See also Server Management Features (page 139) and Server Deployment Options (page 139). The name of each Rack for an HP Server appears along with the assigned name for the Enclosure and Bay. including the Virtual Blade Server feature. (This feature requires that the Hewlett-Packard Rapid Deployment Pack is installed. Rack name. Conversely. Select the type of HP server blade from the list. Altiris® Deployment Solution 6.

Also. All subordinate Enclosures and Bays are identified with custom names under the Fujitsu-Siemens rack name. the Rack name is always Dell. The following servers are supported: Fujitsu-Siemens Rack Servers All Primergy™ rack servers Fujitsu-Siemens Server Blades Primergy™ BX300 blade servers For Fujitsu-Siemens blade servers in the physical view. ensure that the SNMP service is running on the Deployment Server. Deployment Servers cannot receive traps from remote computers. By default. All Fujitsu-Siemens Rack Servers are supported by Deployment Solution. Note If you have Fujitsu-Siemens Server blades managed by the Deployment Server. Example: Fujitsu-Siemens <enclosureName> <bayName> See also Server Management Features (page 139) and Server Deployment Options (page 139). All subordinate Enclosures and Bays are identified with custom names under the Dell rack name. Altiris® Deployment Solution 6. The following servers are supported: Dell Rack Servers All PowerEdge™ rack servers Dell Server Blades PowerEdge™ 1655MC For Dell blade servers in the physical view. the Rack name is always Fujitsu-Siemens. ensure that the security is set correctly to receive traps from remote computers. Example: Dell <enclosureName> <bayName> See also Server Management Features (page 139) and Server Deployment Options (page 139). if the Deployment Server is installed on a Windows 2003 server. Fujitsu-Siemens Server Blades Fujitsu-Siemens high-density blade servers can be deployed and managed from the Deployment console.Dell Server Blades Dell high-density blade servers can be deployed and managed from the Deployment console. but the server blades can also be managed from the physical view in the Rack/Enclosure/Bay view. All Dell Rack Servers are supported by Deployment Solution.8 SP2 143 . but the server blades can also be managed from the physical view in the Rack/ Enclosure/Bay view.

type all or part of the computer’s property values you would like to search for. Example: to find a computer by searching for its IP address. All IBM blade servers are supported by Deployment Solution. licensing or location information. The computer ID. 5000001. or UUID.8 SP2 144 . Name Computer Name MAC Address IP Address ID Serial Number BIOS name of the computer. In the Search For field. the Rack name is always IBM. 0080C6E983E8. 2. for example.1.168.IBM Server Blades IBM high-density Blade Centers can be deployed and managed from the Deployment console. For IBM blade servers in the physical view. Serial number installed in BIOS. Deployment Solution name of the computer. serial number. This search filter queries property values appear in the Computer Properties (page 124) pages. or the end of the computer list is reached. for example. type the address in Search For field and select IP Address from the In Field drop down list. You can search for user or computer names. but the server blades can also be managed from the physical view in the Rack/Enclosure/Bay view. A primary lookup key. This alpha-numeric string is compared with specified database fields.1. The search begins at the top of the computer list and highlights the computer name in the Computers pane when a match is found. or primary lookup keys: MAC address. asset number. Altiris® Deployment Solution 6. All subordinate Enclosures are identified with custom names under the IBM rack name and Bays are identified by number. Find a Computer in the Database This search filter lets you type a string and query specified database fields for specific computer properties. 192. From the In Field drop-down list. for example. Click <CTRL> F or click Find Computer on the console toolbar to search the Deployment Database for computers by property settings. Press F3 to find the next computer that matches the search criteria until there are no more results. 1. Example: IBM <enclosureName> <baynumber> See also Server Management Features (page 139) and Server Deployment Options (page 139). select the field you want to search in the Deployment Database.

See also Computer Filters and Job Conditions (page 83). The computer you are looking for appears highlighted in the Computers window in the console. Lab Builder places these five new jobs under a folder (which you name) located under the Lab folder. Click Lab Builder on the console toolbar or click File > New > Lab Builder to set up jobs specifically created for managing multiple computers in a lab environment. registry data. The actual bay number: 7x. Product Key for the operating system. We suggest that you do not change the file names and paths. Enter the name of the lab setup. for example.Asset Tag UUID Registered User Product Key Logged On User Physical Bay Name Asset number in BIOS. 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. A primary lookup key.8 SP2 145 . Name entered when the operating system was installed. 2. A primary lookup key. Click the Lab Builder icon on the toolbar. and so on. Name of the user currently at the computer. If you change the default settings (example: changing the image name). Note This search is not case-sensitive and lets wildcard searches using the *. Altiris® Deployment Solution 6. All tasks in the jobs have been assigned default paths and file names that let them to use the same images and configuration information. or choose File > New > Lab Builder. To use Lab Builder 1. 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. you must change it in all jobs where the image is used.

Update Configuration.8 SP2 146 . 3. but not the same configuration settings. This job lets you set unique configuration information (such as computer names and network addresses) for client computers. This is also optional. You can quickly get a computer running again by restoring the lab on that computer. This job uploads an image of a computer to the server and an image name is created automatically based on the lab name. Upload Registries. The image that is uploaded using the Create Disk Image job is deployed when you use this job. Click OK. Deploy Lab. and the computer registry files are uploaded to the Deployment Server. Apply configuration settings. The configuration settings you specify in the Update Configuration job are applied to the computers. This job has three default tasks: Deploy image. and the image file name must be unique. Enter a lab description to help you differentiate the lab from others (optional). so if you change the name later you must change it in all the jobs that use the image. This job backs up computer registry files to the Deployment Server. The default image name is synchronized in all lab jobs. When a lab is deployed. 5. This means you don't have to visit each computer to reset the IP addresses and other settings when you deploy an image. each computer has an identical image. there is no actual image in the job until you drag the image source computer to this job. 4. Identify an image in the Create Disk Image job. This job restores the image and registry files to a computer where a lab was previously deployed. simply drag it to the computer or computer group you want it applied to. However. Altiris® Deployment Solution 6. To run one of these jobs. and Back up registry files. The following information describes the default jobs. Set computer names and addresses in the Update Configuration job. Restore Lab.Note The lab name must be unique because the program creates a default image file name based on the name. Create Disk Image.

drag the job icon to selected computer icons. copy and pasting.8 SP2 147 . add printers.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. copy files and back up registry settings. Or you can write and run a script task. See Building New Jobs (page 152). Sample jobs are installed with Deployment Solution and appear in the Samples folder of the Jobs pane. or stored and scheduled for daily or long-term administrative duties on multiple computer groups. Jobs include one or more Deployment Tasks. The New Job Wizard guides you through common deployment and management jobs. Initial Deployment lets you run predefined jobs and configuration tasks on new computers when they start up. or deleting tasks to fit your needs. See Setting Conditions for Task Sets (page 153). The Deployment Console provides job icons to show state and status of the job in the Details pane: Altiris® Deployment Solution 6. restore computers. It is an easy way to set up new users or migrate users to new computers. it is helpful to know specific details about their status and assignments. and avoid mistakes by ensuring that the right job runs on the right managed computer. modifying. You can also modify existing jobs by adding. Jobs can be run immediately for a specific computer. You can build one job to run on different computer types for different needs. See Sample Jobs in Deployment Solution (page 195). You can automatically deploy new computers by imaging and configuring TCP/IP. Viewing Job Details As jobs are assigned. and more. Job status icons also appear in the Details pane of the Deployment Console to indicate various deployment states. See Sample Jobs in Deployment Solution (page 195). or run scripted installs. See Viewing Job Details (page 147). scheduled and executed. distribute software packages. and perform all aspects of IT administration. You can add tasks to capture and distribute images. You can run many sample jobs as they are. and other network settings and installing basic software packages. and personality settings. configure settings. configure computer settings. SIDs. You build jobs by adding tasks to a job and customizing the task for your specific needs. software packages. To assign and schedule a job in the Deployment Console. Set conditions on jobs to run only on computers with properties that match the criteria you specify. back up and distribute software or personality settings. Job icons appear in the Jobs pane of the Deployment console. or you can set environmental variables. create and distribute images of computers on the network. You can build jobs with tasks to automatically create and deploy hard disk images.

Features to add. These icons are graphical symbols in the Deployment console used to identify the status of an assigned job. Indicates error conditions when individual tasks run.8 SP2 148 . beginning when the job started and ending when it completed successfully. Change the order of the task execution with the up and down arrows. This is the job's run time. Job Schedule details. The currently applied conditions appear in a list box with a Setup option to add conditions to different task sets for different computer properties within a job. A list of tasks assigned to the job and task descriptions also appears. See also Viewing Computer Details (page 98). A list of assigned computers and its deployment history. Example: click the Status column heading to organize and display the progress status of the job. It lets you quickly build image files and deploy new computers. the Status field displays any errors incurred and the tasks that completed successfully. If a job defines error conditions when individual tasks run. New Job Wizard The New Job Wizard provides integrated features to build. In the Details pane. modify. See Setting Conditions for Task Sets (page 153). and more. Indicates that a job is associated with a computer or group of computers but is not scheduled. . It helps you build the most common jobs. Tasks are executed in the order they are listed. assign. To sort jobs or computer details. A description of the job. distribute software packages. Conditions specify characteristics that a computer must have before the job will execute. See Deployment Tasks (page 156). indicates that a job has executed successfully. and delete tasks for each job.Job status icons that update the state of the job in running deployment tasks. Altiris® Deployment Solution 6. Indicates that a job is in progress. migrate users. if available. and guides you through additional steps to assign and schedule the jobs to selected computers. and schedule common deployment jobs. You can also use Add or Modify in the main window to edit the description as well. Indicates that a job is scheduled to run on a computer or computer group. just point and click on the category in the Details bar.

See Restoring a Computer from its Deployment History (page 129). 2. select packages. Altiris® Deployment Solution 6. and defining configuration values. See also Modifying Tasks in a Deployment Job (page 189).Note When a software package or deployment job is scheduled to run on client computers. Deploy and configure computers. See Building New Jobs (page 152) to build customized jobs and set up return codes. This wizard guides you through the steps required to move a computer hard disk image. See Distributing a Disk Image (page 163). assign to computers. applications. This option reschedules jobs saved in each managed computer’s history record. You can type a name with up to 64 characters. clicking File > New > Job Wizard. This wizard guides you through the steps required to create an image of a computer’s hard disk and schedule the job. or right-clicking in the Jobs pane of the Deployment Console and selecting New Job Wizard. You can set conditions. which contains all deployment tasks previously processed. Select a job option: Create an image. If a user clicks Abort when the message appears. an event is logged to the client's history so that Deployment Solution administrators know when users abort a scheduled event. 1. Migrate computers. See Distributing Software (page 175). the job appears in the Jobs pane of the Deployment console with deployment tasks listed in the Tasks list for each job selected. 3. Deploy software packages.8 SP2 149 . You can perform one or more migration operations using provided options. and schedule the job. Follow the steps in each wizard to create a job (some New Job wizards build multiple jobs). personality settings. See Creating a Disk Image (page 158). the Altiris Client Service Message dialog appears. The New Job Wizard appears to guide you through basic deployment jobs. This wizard guides you through the steps required to lay down a new disk image on a selected computer and install software and personality settings. Create a new job by clicking New Job Wizard on the Deployment Console. warning them that a job is about to execute. and personality settings from a source computer to a destination 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. Give the job a unique name. Restore a computer. This wizard guides you through steps required to install software packages. Note You cannot define return codes when using the New Job Wizard. After creating a job.

Note This option creates two jobs that appear in the Jobs pane: Job (Capture) and Job (Distribute). Additionally. Click the option to deploy a disk image and migrate the 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. distribute software packages. It creates jobs and tasks to capture the personality settings. Or perform different levels of migration to distribute only software or to simply capture and distribute personality settings to the new computer. Job (Capture) includes a Capture Personality Settings task (see Capturing Personality Settings on page 179) to capture the personality of the source computer. a Modify Configuration task to update settings to the destination computer. distribute software and redistribute the saved personality settings from the source computer to the new destination computer. Note This option creates two jobs that appear in the Jobs pane: Job (Capture) and Job (Distribute). Capture personality settings. Altiris® Deployment Solution 6. Job (Distribute) includes a Deploy Image task (see Distributing a Disk Image on page 163) if selected. and one or more Install Package tasks to update software (if selected) and migrate personality settings. software.8 SP2 150 . See Distributing Software (page 175). 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). Click the option to migrate only personality settings to one or more computers. Migrate the same computer to another operating system Click this option to upgrade the operating system on a computer and reinstall personality settings and software packages on the same computer. and settings from a user’s current computer to a new computer.Migrating Computers From the New Job Wizard you can select Migrate computers to quickly distribute hard disk images. You can image a new computer’s hard disk with a new operating system and install software and personality settings. and migrate the personality settings. distribute a new hard disk image. The source computer is named computerName (Old). 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. Job (Capture) includes a Capture Personality Settings task (see Capturing Personality Settings on page 179) 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 182). distribute a new disk image.

the personality settings of the selected computer(s). and can be saved and assigned to other computers at a later time. Apply Computers to a Job When deploying software in the New Job Wizard. You can select a personality template and save Personality Packages to the Deployment Share. See also New Job Wizard (page 148). See also Migrating Computers (page 150). Simply capture the personality of the computers Click this option to capture and save. Open an Adding New Computers dialog to create new user accounts to assign the job. Note This option creates a single job with a Capture Personality Settings task (see Capturing Personality Settings on page 179). You can also schedule jobs for the specified computers in the wizard. click Automatic to assign source computers with destination computers using an alpha-numeric order.Job (Distribute) includes a Deploy Image task (see Distributing a Disk Image on page 163) and one or more Install Package tasks to update software. the job appears in the Jobs pane to use at another time. Regardless of the scheduling option selected. Right-click a computer in the Destination column to replace it with another destination computer and assign it to a new source computer.8 SP2 151 . See Scheduling Jobs (page 155). Associating Destination Computers Use this dialog to associate source computers with destination computers when migrating personality settings. Depending on the computers selected in the previous Select Computers dialog. See also Scheduling Jobs (page 155). Altiris® Deployment Solution 6. New Computers. letting you distribute these personality settings later to new computers. The jobs created in the New Job Wizard appear in the Jobs pane. To automatically assign multiple computers. you can select computers to assign the Distributing Software job created in the wizard. rather than requiring you to create a job and assign it to computers when Building New Jobs. You can also select an option to simply store the job and use it at another time without scheduling the job. 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. if selected (see Distributing Software on page 175). but not distribute. you can migrate personality settings captured from the source computers to new destination computers. Right-click a computer in the Source column to replace it with another source computer. The associated computers share personality settings after running the jobs.

This is optional. See also New Job Wizard (page 148) and Job Scheduling Wizard (page 153).8 SP2 152 . and Personality Packages. If the selected package is not a .Setting up Conditions in the New Job Wizard The New Job Wizard also provides steps to set up conditions. Summary of Options After selecting the options in the New Job Wizard. you can view a summary of the job names. conditions. Add tasks to each job by clicking Add. Create a new job by clicking New Job on the Deployment Console. A new job is added to the Jobs pane in the Deployment console. Building New Jobs A job can be a single task to distribute software or change computer property settings. You can type a name with up to 64 characters. Set conditions to apply the job to specified computers meeting defined criteria. Click File > New > Job. See Deployment Tasks (page 156). See Setting Conditions for Task Sets (page 153).RIP or Personality Package. You can modify jobs by double-clicking the job or right-clicking.MSIs. You can install any type of software to the managed client computer. a message appears asking if you want to continue. including . Click Add to open a list of possible deployment tasks to add to each job. set postinstallation TCP/IP and SID values. or a job can be a series of tasks sequenced to migrate hard disk images. See Setting Conditions for Task Sets (page 153). Click Finish to complete the steps in the wizard. Create a new job. Install Software Packages The New Job Wizard provides steps to install software packages to the selected computer(s). and install software packages and personality settings. To change any options. Click Setup conditions for this set of tasks to open the Define Conditions dialog from the New Job Wizard. and access and apply them to computers or computer groups from an index of prebuilt jobs. Setting conditions lets you run selected tasks only on computers matching defined criteria. Enter a unique name and description for the job. and other selected choices. You can group and organize jobs. Order multiple conditions to run jobs on computers that match the first applicable condition. or right-click in the Jobs pane of the Deployment Console. assigned computers. a step usually performed independently for each job during its build phase. See Distributing Software (page 175) for additional information. 2. Altiris® Deployment Solution 6. 1. and selecting Properties.RIPs. click Back to return to the previous dialog. 3. . and select New Job.

ensure you do not run a task that overrides the previous tasks. including operating system types. After you complete the steps to create a task. Note The default condition (named default) has no parameters or values associated with it. Set task options using the provided wizards. If this is the only condition that a job contains. Use the SHIFT and CTRL keys to select multiple computers or groups. The Schedule Jobs dialog appears. free drive space and other computer properties. The last action in each task wizard lets you set return codes for each deployment task. Click Next. 7. Setting Conditions for Task Sets Setting conditions on a job lets you run selected tasks only on computers that match defined criteria. See Setting Up Return Codes (page 193). See also Importing and Exporting Jobs (page 192). After adding tasks.4. you can create a single job with tasks defined for computers with varying properties. As a result. As a result.8 SP2 153 . Click Add to add another task. the tasks associated with the default condition will always work on all computers to which the job is assigned. Select Computer(s) or Computer Groups Select the computer(s) or group(s) of computers to assign the jobs selected in the previous dialog. 6. To schedule the job. Altiris® Deployment Solution 6. This is optional. You can create task sets for each job that apply only to the computers matching those conditions. Example: list Distribute Disk Image above Distribute Software or Distribute Personality. processors. Use the up and down arrows to change the order of execution of the tasks in the Task list box. letting the hard disk to be imaged before installing applications and settings. Use the SHIFT and CTRL keys to select multiple jobs or job folders. Select Job(s) Select the job(s) or group(s) of jobs to assign to computers or computer groups. 5. Click when Adding New Computers. This new feature meets Section 508 requirements to improve disability access and lets integration of voice activation software and other user interface features. Tasks are executed in the order that they appear in the task list. click OK. New Computers. drag it to a computer or computer group. and to schedule the jobs to run without using a mouse. Set Return Codes. Click Next. Default condition is like having no conditions. See Scheduling Jobs (page 155). it is added to the task list box. network adapters. Job Scheduling Wizard The Job Scheduling Wizard provides features to assign jobs to selected computers and computer groups.

In addition. it runs the default condition. or IP address. Note When using User Defined Tokens to set conditions for some client property values. Enter a name for the condition up to 64 characters. the conditions are evaluated for each computer and the appropriate task executes on the appropriate computer. or Delete a condition. The task set you create appears in the Task list for each condition. Click Operation and select a compare statement. 5. See also Setting Conditions for Task Sets (page 153). When the job is applied to a computer group. In the Value box. The Job Properties dialog appears. operating system language. Example: you can set a condition to match a particular asset tag. Click the Field list and select a data field heading from the list. A menu appears with options to create a New condition. 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. RAM. select User Defined Tokens from the Field list. Click Add to open the Condition dialog. Click New in the menu to open the Condition Settings dialog. You can set Condition A to distribute the XPImage. hard drive space. You can use wildcard characters and AND/OR operators. Altiris agent version. You can define conditions based on common client features such as operating system. Select a job in the Jobs pane of the Deployment Console. Each condition is processed in sequence until the computer matches the condition defined within a set. 2.8 SP2 154 . See also Deployment Tasks (page 156). Order Condition Sets By specifying and ordering different sets of conditions. if a task is associated with the default condition the task always executes when a computer does not meet any other conditions associated with this job. the set of tasks for this condition set is processed.img file to Windows 2000 computers using another Deploy Image task. click Order and reorder them using up or down. you may be required to use the decimal value rather than the hex value.img file to Windows XP computers using a Deploy Image task. 1. Modify a condition. software and hardware version. If the computer does not meet any of the defined conditions. type a string to search for in the selected database field. When you select a new condition. Once a match is found. 3. To reorder conditions. You can set Condition B to distribute the W2KImage. See Order Condition Sets (page 154). 4. and other characteristics. you can determine when a task executes based on defined computer properties. Click Setup next to the Condition field. Altiris® Deployment Solution 6. You can set conditions based on computer properties stored in fields in the Deployment Database. Click OK. the tasks for that condition appear. 6. To set up custom conditions based on custom tokens.

A job can be scheduled to execute by minute(s). If you selected a computer icon. The following options are available: Do not schedule. To reschedule a job 1.8 SP2 155 . This option lets you run the job now. letting you schedule the job to run immediately. By default all jobs are deferred up to five minutes. 3. To run it at regular intervals. 4. This option lets you apply jobs to computers but does not run the job until you return to the Schedule Job dialog and set a run time. To schedule a job 1. Schedule in batches of x computers at y minute intervals. the Schedule Job dialog appears. Use the up and down arrows to change the order of the scheduled jobs. 5. at a scheduled interval. The job name and folder located in the Jobs pane appear. click the Job Schedule tab. Click the Job(s) Selected tab. right-click the job icon and select Start Now. Schedule this Job. The Schedule Job dialog appears. This is a list of computers. Note The Schedule Job dialog is the same for Rescheduling Jobs. and IP address that the job is scheduled to run. This option lets you schedule computers in batches to maximize efficiency. and it has been assigned to multiple computers or computer groups. New Job Wizard. click the job icon in the Details pane. Job and job folders selected from the Jobs pane of the Deployment Console are scheduled in the order they were selected. Altiris® Deployment Solution 6. The Schedule Jobs dialog appears.Scheduling Jobs After a job has been created. Allow this job to be deferred for up to x. select a job or computer that has been previously scheduled. A job can be deferred when the server is busy executing other jobs. 2. their associated group. Drag a job to a computer or computer group. day(s). specify a time and date to repeat. click the scheduled computers in the Details pane. Select the job icon. Click the Computer(s) Selected tab. From either the Computers or Jobs panes in the Deployment console. A job icon appears in the Details pane identifying the computers assigned or the name of the job. right-click and click Reschedule. 2. hour(s). even across multiple Deployment Servers. week(s). or assigned but not scheduled. right-click and click Reschedule. 3. Repeat this job every x. This option lets you type the date and time to run the job at a specified time and date. In the Schedule Job dialog. To immediately start a scheduled job that has not yet run. Run this Job immediately. and Job Scheduling Wizard. Click OK. setting a lower priority for particular jobs.

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. 2. image file. 2. 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. . right-click the job in the Details pane and click Discontinue Repeat.RIP. To remove scheduled jobs from a computer 1. At this point you need to schedule a new time to run the job or click the Do not schedule option. including: Altiris® Deployment Solution 6. This lets you view a greater number of tasks in a deployment job without using the scroll bar to navigate up and down. (Edit features also open in the Details view of the Deployment Console when you select the job from the Jobs pane). Select one of the assigned tasks in the Task list. and press Delete or right click the job(s) and select Delete. Click a computer in the Details view and press Delete or right click the job(s) and select Delete. press Delete or right click the job(s) and select Delete.8 SP2 156 . 1.MSI. See also Building New Jobs (page 152) and Modifying Tasks in a Deployment Job (page 189). 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.4. 1. 2. To remove multiple jobs. or executable file assigned to a job or stored in the Deployment Share. The Deployment Console has multiple tasks available from the Add menu. A job is created automatically for each assigned package in the Systems Jobs > Drag-n-Drop folder. Click the computer. . Select the scheduled job in the Details window. hold down the SHIFT or CTRL key while you select the job(s). Click Delete. Click a job in the Jobs pane. To stop a repeating job. 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). these files and packages appear in the Resources view (see Shortcuts and Resources View on page 75). To run a job immediately from the Resources view If you have a batch file. The icon for a scheduled job is yellow. Jobs are built with tasks. Deployment Tasks A task is an action of a job. Each task is executed according to its order in the task list contained in a job.

and log off. This lets you gather inventory information from client computers to ensure that the deployment database is up-to-date with the latest computer properties. Distribute previously created disk images (. Supported Live Task Types Following is the list of the live tasks supported for the x64. PC Transplant ships as a part of Deployment Server. computer and user name. Modify the IP address. without altering the base Windows application. Use the Wait dialog to retain a computer in automation mode after a task is performed. Distribute . power off.IMG or . It identifies valid Altiris packages and assign passwords and command-line options to Personality Packages.EXE files) for later distribution.RIPs. . See Scripted OS Install (page 168). See Modifying Configuration (page 182). Distribute Disk Image. Perform power control options to restart. Distribute Personality Package. Scripted OS Install. See Power Control (page 189). Use the Run Script dialog to select or define a script file to run on specified computers or groups. See Creating a Disk Image (page 158).IMG or . Capture Personality.IMG or . See Copy File to (page 187). Capture the personality settings of a selected computer on the network using the PC Transplant software. deactivate or reset layers and completely avoid conflicts between applications. scripts. Modify Configuration.8 SP2 157 . Tasks are listed for each job in the task list box. See Capturing Personality Settings (page 179). See Distributing Personality Settings (page 180). See Get Inventory (page 183). Copy a file from the Deployment Share or another source computer to a destination computer. Copy File to. See Distributing Software (page 175). You can change the order using the up and down arrow keys. Power Control. domains and Active Directory organizational units. Create custom commands using scripts to perform jobs outside the bounds of the pre configured tasks. Manage the SVS Layer. Wait. Create a disk image from a reference computer and save the image file (. Distribute Software.EXE files) or create a disk image from a reference computer on the network and simultaneously distribute it (.MSI files.Create Disk Image. See Managing the SVS Layer (page 177). See Run Script (page 183). and other network information and computer properties. Run scripted (unattended) installs using answer files to install computers remotely over the network. Send a Personality Package to computer or groups. Each task executes according to its order in the list. and SPARC platforms. Task Restore Computer History x64 Yes Yes IA64 Yes Yes SPARC Yes Yes Altiris® Deployment Solution 6. Get Inventory.EXE) to other managed computers on the network. shutdown. Instantly activate. IA64. See Wait (page 189). See Distributing a Disk Image (page 163). Run Script. personality settings and other package files to computers or groups.

8 SP2 158 .IMG file. This task will run Altiris RDeploy. You can distribute the disk image file using the Distributing a Disk Image task.WIM file. .exe from the console to capture and migrate hard disk images.Task Configure Quick Disk Image Power Control: Wake Up Power Control: Restart Power Control: Shutdown Power Control: Log off Remote Control Execute Copy File Chat Advanced: Clear Computer Status Advanced: Prompt User for Properties Advanced: Reset Connection Advanced: Install Automation Partition Advanced: Get Inventory Advanced: Reject Connection Advanced: Uninstall Windows Agent Advanced: Install BIS Certificate Advanced: Remove BIS Certificate Advanced: Apply Regular License New Job Wizard New Group New Computer Rename Delete Change Agent Setting Permissions Job Scheduling Wizard x64 Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes No No Yes Yes Yes Yes Yes Yes Yes Yes Yes IA64 Yes Yes Yes Yes Yes Yes No Yes Yes No Yes Yes Yes SPARC Yes Yes Yes Yes Yes No No Yes Yes No Yes No Yes Yes Yes Yes No No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Creating a Disk Image This task creates an image of a computer’s hard disk. . or as a . . Altiris® Deployment Solution 6.EXE file. You can save the disk image as an .GHO file Create an image file using the New Job Wizard or adding the task when Building New Jobs.DMG file.

Important Linux (RDeploy) and Ghost options are available only when the ImageTools. This facilitates the imaging of thin client computers. If you do not select this option and do not specify a Deployment Share path. the image is created as a .DMG file. You can also select the Ghost option for imaging. or Windows PE. a Mac image with a . If you select ImageX. you must boot to DOS. You can use this option to store images locally on the managed computer's hard drive or to an additional server used to store images. You can add command-line options specifically for the RapiDeploy program to execute imaging tasks. The following are the RapiDeploy options for imaging. the image is created as a .ini file is stored in the eXpress folder. ImageX. Select an imaging tool from the drop-down list. You can still save your image to a location outside of the Deployment Share file structure even when you do not select this option. 4.DMG extension. If you select Ghost.EXE extension makes them into self-extracting executable files (the run-time version of RapiDeploy is added in the file). You can select the ImageX or Mac Image option for imaging. RapiDeploy (Linux mode). Linux. RDeploy Options RDeployT is the default imaging executable. This option only eliminates the warning message. the image is created as a . Select this option to run the RDeploy in a GUI mode.GHO file. RapiDeploy (Graphics mode). You can also save ImageX files with a . Select Disable image path validation if you want to store the image file outside of the Deployment Share file structure. 2.8 SP2 159 . See the Command-line Switches in the Deployment and Migration Guide. To create a disk image 1. You can select RapiDeploy (Text mode). For information on creating and deploying a Ghost Image. This requires that you set up an Altiris PXE Server or install an automation partition. Text Mode (RDeployT). Mac Image or Ghost. You can store image files to access later when a managed computer is assigned a job that includes the image file. If you select Mac Image. Linux (RDeploy). Graphical Mode (RDeploy). you can see a warning message indicating this and reminding you that your automation process must be configured to use the path indicated in the Name field. see Creating a Ghost Image (page 161). see Creating a Mac Image (page 160). and a Ghost image with a . Select this option to run the RDeploy in a text mode. Select this option to run the RDeploy in Linux mode.WIM extension.WIM file. Enter a path and file name to store the disk image file. Altiris® Deployment Solution 6. Saving image files with an . 3. The default file name extension is .GHO extension.IMG.Note To create an image of a computer. For information on creating and deploying a Mac Image. Enter any additional parameters in the Additional Parameters field.

select the operating system. 8. select Mac Image (. Select Prepare using Sysprep to use Sysprep to prepare system for imaging and click Sysprep Advanced Settings. 5. Tip If an imaging Job fails on a managed computer. The task appears in the Task list for the job. click Advanced. 11. be sure to enter the path relative to the managed computer (Example: C:\myimage.When storing images locally on the managed computer's hard drive. use the option to remove the automation partition only when you want to clear all images from the computer. By default. 9. Prerequisite: To store images locally on the managed computer’s hard drive. Click Finish. From the Operating System drop-down list. select the product key. Click OK (if you are using the New Job Wizard) or click Next.8 SP2 160 . From the Product Key drop-down list. you must have a hidden automation partition installed on the managed computer's hard disk with the required disk space to hold the images you want to store. 6. See Advanced Sysprep Settings for Creating a Disk Image (page 162). See Create Disk Image Advanced (page 162). select Cancel > Restore Original Settings. When you store an image locally on a managed computer instead of a file server. On the client screen. Creating a Mac Image You can create a Mac Image using the Create Disk Image job.dmg). the DOSManaged Boot Option type is selected. Note Click Add new to go to the Sysprep Settings dialog and select the OS Information. 12. Note ImageX requires a Windows PE x86 pre-boot environment.img). See Setting Up Return Codes (page 193). select the required pre-boot environment to perform the Create Disk Image task in the selected pre-boot environment. 10. See also Deployment Tasks (page 156). you save server disk space and reduce network traffic. From the Imaging Tool drop-down list. To create a Mac Image 1. 7. From the Automation pre-boot environment (DOS/Windows PE/Linux) dropdown list. This screen displays a prompt to confirm if the user wants to configure the client or restore the original settings. Altiris® Deployment Solution 6. (Optional) Set Return Codes. Caution When imaging computers where images are stored on the managed computers hidden automation partition. the Deployment agent configuration page appears on the client. (Optional) To select Media Spanning and additional options.

Note The Sysprep settings option is disabled if you select Mac Image as the Imaging Tool. or if you are retrieving the image from a remote server. Add any additional parameters in the Additional Parameters field. 4. See Setting Up Return Codes (page 193). You can create a Ghost Image using the Create Disk Image job. provide the disk number in the Additional Parameters field using the same format.gho). the guest account is used by default. For more information on configuring PXE. Important To use the Ghost Solution for creating a disk image.dmg If no credentials for this server are provided in the automation configuration.dmg 6. 2. 4. Click Finish. see the PXE Configuration Utility Help. select the Disable image path validation check box. Provide the disk number in the Additional Parameters field using the following format: -d[disk#] By default. It also provides operating system migration. (Optional) To disable the validation of the image path. hardware and software inventory. you have to store the ghost. Provide the account credentials as part of the path using the following format: //username:password@server/sharepoint/path/filename. software distribution. 5.2. From the Imaging Tool drop-down list.exe and ImageTools. 3.ini files in the Program Files\Altiris\eXpress\Deployment Server directory. This is useful if the image is stored locally. Click Next. 8. select Ghost Image (. The Mac image is created. (Optional) Set Return Codes. To create a Ghost Image 1. To image a different disk. The Automation pre-boot Environment for Mac Image is the Default Automation when capturing Mac images. 3. 7. Creating a Ghost Image Symantec™ Ghost Solution Suite is a corporate imaging and deployment solution. Altiris® Deployment Solution 6. This option uses the PXE functionality of the operating system of the specified server. Enter the path and file name to store the disk image. Specify the share using the following format: //server/sharepoint/path/filename. Caution The captured disk image must be stored on an AppleTalk Filing Protocol (AFP) share. and secure system retirement. Enter the path and file name to store the disk image. The Return Codes dialog appears. all partitions of disk 1 are imaged.8 SP2 161 . computer personality migration.

the Enable mass storage device support using built-in drivers option is selected. The Maximum file size supported is 2 GB. From the Automation pre-boot environment (DOS/Windows PE/Linux) dropdown list. Disable mass storage device support. To save an image larger than 2 GB. the Sysprep. When this option is selected. Enable mass storage device support using built-in drivers. The Ghost image is created. the Sysprep. From the Maximum file size list.5. 6. Click Finish. Create Disk Image Advanced Media Spanning Maximum file size. Click Next. as well as Sysprep options. the Sysprep. 8.inf file contains the section [SysprepMassStorage] and is appended by contents of the file mentioned in the Mass storage section file field. enter the file size you want in the field. Enable mass storage device support using the following: When this option is selected. By default. 9. the Default Automation (Auto-select) type is selected. If the preferred type is not on the list. The Return Codes dialog appears. By default. 7. such as command-line options. Advanced Sysprep Settings for Creating a Disk Image You can use the Advanced Sysprep Settings dialog to specify Sysprep mass storage device support. When this option is selected.8 SP2 162 . See Setting Up Return Codes (page 193).inf file contains the section [Sysprep] with the key value pair as BuildMassStorageSection = No. Advanced Sysprep Settings for Creating a Disk Image in Windows Vista You can use the Sysprep advanced settings dialog to specify the settings for any Windows Vista operating system. the Sysprep advanced settings dialog for Windows Vista appears.inf file contains the section [Sysprep] with the key value pair as BuildMassStorageSection = Yes. To use Microsoft Sysprep. Altiris® Deployment Solution 6. Specify ___ MB. You can also copy the drivers directory mentioned in the Mass storage drivers field. (Optional) Set Return Codes. select a media type. This dialog lets you select Plug-n-Play (PnP) drivers options. select the Prepare using Sysprep check box and specify the operating system and product key. If you select Windows Vista as the operating system under Sysprep settings on the Create Disk Image dialog and click Advanced Settings. Deployment Server automatically breaks it into separate files regardless of your storage capacity. select the required pre-boot environment to create the disk in the selected pre-boot environment.

3. select Disable image path validation. From the job wizard. SID. resulting in network conflicts when the computer starts up. these network settings are not reapplied to the computer after the imaging task. You can create the disk image file using the Creating a Disk Image task. Enter an image description (optional) in the Description field to help identify the image. computer name. but use more disk space. Enter the name and location of the source computer to both create an image and distribute the newly created image file.8 SP2 163 . Compressing an image is a trade-off between size and speed. Distributing a Disk Image Distribute an RDeploy. Enter the name of an existing image file. 4. If you select this option. Click Select a disk image file to select a stored image file. ImageX. To distribute a disk image 1.Additional Options Do not boot to Production. Uncompressed images are faster to create. 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. Select Optimize for Size to compress the image to the smallest file size. 2. click Add > Distribute Disk Image. This lets you set down a new image file from a previously imaged computer. and so on). The default setting is Optimize for Speed. Click Select a computer on the network to image a source computer on the network. or if you are retrieving the image from a remote server. Compression. This is useful if the image is stored locally. Select Optimize for Speed to create a larger compressed image file with a faster imaging time. you must change the path of the Deployment Agent for the Windows log file. Altiris® Deployment Solution 6. Distribute a hard disk image using the New Job Wizard or adding the Distribute Disk Image task when Building New Jobs. Note If you deploy a Windows image over a Linux computer or a Linux image over a Windows computer. Open the New Job Wizard (page 148). If you do not want the Deployment Server to validate the selected path. or Mac image file to managed computers to lay down a previously created hard disk image. Note Configuration restoration after imaging a compressed drive is not supported for this release. The Distribute Disk Image dialog appears.

5. Distributing a Mac Image You can deploy a Mac Image using the Distribute Disk Image job. From the Product Key drop-down list. Provide the credentials as part of the path using the following format: //username:password@server/sharepoint/path/filename. select the operating system. Select Automatically perform configuration task after completing this imaging task to run the configuration task after the imaging task is complete. Then. Select the Select a disk image file option. 2. 7. If you are using the New Job Wizard. 11. (Optional) Click Advanced to resize partitions and set additional options. the guest account is used by default.dmg If no credentials for this server are provided in the automation configuration. Select the check box to save the image and type in or browse for the location where you want to store the file. Select the Save the disk image as a file while distributing option to save the newly created image file to a specified disk drive. From the Automation pre-boot environment drop-down list. 9. 3. provide the path to the Mac (. See also Deployment Tasks (page 156). click Advanced Sysprep Settings.dmg 4. If you use a reference computer as the image source.This option saves an image of a selected computer’s hard disk in its current state each time the job executes. 10. select the product key. 13. In the Name field. 6. 12. Altiris® Deployment Solution 6. you can also choose to save the image as a file for later use. click Next. See Advanced Sysprep Settings for Distributing a Disk Image (page 166). Click Finish. See Distribute Disk Image-Resizing (page 166). From the Operating System drop-down list. See Setting Up Return Codes (page 193). You can schedule the job to image a specified computer every time it runs. (Optional) Set Return Codes. The option reported by the PXE Manager is the default pre-boot environment option. Select Prepared using Sysprep to use Sysprep to prepare the system for imaging. which updates the image each time. click OK. Otherwise. Note Click Add New to go to the Sysprep Settings dialog and select the OS Information. To deploy a Mac Image 1. 8.DMG) image stored on an AppleTalk Filing Protocol (AFP) share by using the following format: //server/sharepoint/path/filename. Click Automatically perform configuration tasks after completing this imaging task to restart the computer and push the configuration settings to the imaged computer. select the required pre-boot environment to perform the Distribute Disk Image task. Click OK.8 SP2 164 .

8. the Default Automation (Auto-select) type is selected. (Optional) Set Return Codes. By default. select the product key. From the Product Key drop-down list. Note Click Add New. Note The Image is stored locally on the client and the Sysprep settings options are disabled when you select a Mac image. The Automation pre-boot Environment for Mac Image is Default Automation when deploying Mac images. To restart the computer and push the configuration settings to the imaged computer. The Select a computer on the network feature is not supported when using Mac Imaging.GHO) image using the Distribute Disk Image task. See Setting Up Return Codes (page 193). select Disable image path validation. 6. Click Next. The Ghost image is deployed. Add any additional parameters in the Additional Parameters field. To use Sysprep to distribute the image.GHO image. The Mac image is deployed. To distribute a Ghost image 1. 7. From the Operating System drop-down list. This is useful if the image is stored locally. Click Finish. or if you are retrieving the image from a remote server. select the required pre-boot environment to perform the Distribute Disk Image task. Click Next. 6. Altiris® Deployment Solution 6. This option uses the PXE functionality of the operating system of the specified server.8 SP2 165 . From the Sysprep Settings dialog. For more information on configuring PXE. On the Distribute Disk Image dialog. 10. 7. select Prepared using Sysprep. 2. From the Automation pre-boot environment drop-down list. select the operating system. If you do not want the Deployment Server to validate a selected path. (Optional) Set Return Codes. 5. see the PXE Configuration Utility Help. Distributing a Ghost Image You can distribute a Ghost (. 9. select Automatically perform configuration tasks after completing this imaging task. 4. Browse and select a . 11. See Setting Up Return Codes (page 193). The Return Codes dialog appears. Click Finish.5. select the operating system information. select the Select a disk image file option. 3.

you have the option to resize the partition to take advantage of the available disk space. remove.inf file for the Distribute Disk Image task. depending on the option selected in the Advanced Sysprep Settings dialog. Advanced Sysprep Settings for Distributing a Disk Image in Windows Vista You can use the Sysprep advanced settings dialog to specify the settings for any Windows Vista operating system. Percentage. This dialog lets you select Sysprep answer file options. Max. the Deployment Server generates the Sysprep. Distribute Disk Image-Resizing By default. View the minimum size of the partition.inf file from it. Min. Drive Size gives you information about the size of the image. Use the following answer file. the Sysprep advanced settings dialog for Windows Vista appears.inf file depending on the data present in the database. the option defaults to Leave the client’s existing Automation or OEM partition as it is. HP partitions remain a fixed size. View the maximum size of the partition. When this option is selected. Original indicates the image source disk size. If you select Windows Vista as the operating system under Sysprep settings on the Distribute Disk Image dialog and click Advanced Settings. the Deployment Server picks up the contents of the file mentioned in the Sysprep answer file textbox and prepares the Sysprep. Minimum indicates the amount of space the image will use on the target computers. Fixed Size. Click this option to choose the imaging executable as RDeploy. whenever you deploy an image. RDeploy Options: Graphical Mode[RDeploy]. Altiris® Deployment Solution 6. When this option is selected. Use default answer file. The options are as follows: leave the partition as it is. 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). Distribute Disk Image-Additional Options This option lets you specify operations for existing Automation Agents and OEM disk partitions.8 SP2 166 . Select this option and enter the percentage of free space you want the partition to occupy. If the image file does not contain any information for an automation or OEM partition. Select this option and enter the desired partition size. so you can determine if you need to change partition sizes. or replace the existing partitions.Advanced Sysprep Settings for Distributing a Disk Image You can generate the Sysprep.

3. Replace the client's existing BW partition from image file [-forcebw]. this option is selected. 5. To image computers from USB Disk on Key Devices 1. Copy the <Filename>. You can add command-line options specifically for the RapiDeploy program that runs imaging tasks. If the image file contains no OEM partition information.8 SP2 167 . The automation partition remains unchanged when distributing disk images. by default. OEM Partition: Leave the client's existing OEM partition as it is. If the image file contains no automation partition information. The post-configuration task fails after an image restore. Copy RDeployT. See also Deployment Tasks (page 156). Text Mode or RDeployT is the default choice. create a new automation boot disk while creating a new configuration. Format the USB DOK using HP’s USB Disk Storage Format tool as FAT and make it a DOS startup disk.SYS to the device. by default. The OEM partion remains unchanged when distributing disk images. Delete the client's OEM partition [-nooem]. Select this option to delete the existing OEM partition from client computers. Select Bootable disk-Removable disk to install on the USB Disk on Key. 2. Copy HIMEM.img file to the device. Select this option to replace the existing automation partition on the client computer with the automation partition from the image file. Select this option to replace the existing OEM partitions on the client computer with the OEM partition from the image file. 4.Text Mode[RDeployT]. Imaging Computers from USB Disk on Key (DOK) Devices (JumpDrives) Deployment Solution supports imaging clients from bootable USB Disk on Key (DOK) devices. Note The checkdisk command-line option should not be used from a Deployment console. Automation Partition: Leave the client's existing BW partition as it is. Delete the client's Automation partition [-nobw]. Altiris® Deployment Solution 6. Click this option to choose the imaging executable as RDeployT.exe from the <InstallPath>\eXpress\Deployment Server\RDeploy\DOS directory to the device. this option is selected. Select this option to delete the existing Automation partition from client computers. Additional Command line switches. In Boot Disk Creator. Replace the client's existing OEM partition from image file [-forceoem].

Configured operating system install sets can be reused to build and run scripted install jobs as needed.sys with the following: DEVICE=C:\HIMEM.bat with the script and command-line option. This task provides easy-to-use features to create an answer file for each scripted installation. Complete network and Web server installation and configuration tasks profit most from scripted installs.com /p /E:1024 BUFFERS=20 FILES=20 STACKS=0. You can run scripted installs for Windows or Linux computers. Using embedded automations causes the selected image (DOS. It does not let the scripted install to run. and unattended operating system installations over the network using answer files to input configuration and installation-specific values. 7. but much slower and bandwidth intensive.6. Create an Autoexec. Windows PE) to load and halt. Linux. run the scripted install. and update with service pack installations. Use complete unattended install features to copy Windows operating system source files quickly to the Deployment Share and easily create an answer file.0 FCBS=1. Linux.SYS switches = /f DOS=HIGH. Create a Config. When running a Scripted OS Install task. Windows. Boot from the USB Disk on Key (recognized as C:) and rdeployt executes and images correctly. Note Scripted Install requires either an automation boot disk or an Altiris PXE Server. as it specifies the flash drive. See Scripted Install for Windows on page 169. rdeployt -md - fc:\IMAGE. Scripted OS Install The Scripted OS Install task performs remote. Scripted installs are flexible in performing post-configuring tasks.UMB SHELL=command. Run scripted install jobs to remotely install different versions of Linux. automated. Scripted installs let you deploy server and client computers across the network from installation files and perform post-installation configuration tasks.8 SP2 168 .0 LASTDRIVE=Z 8.img -d2 Note The -d2 switch is the most important part of the script. You can customize sample scripted install jobs installed with the Deployment Server system and Altiris® Deployment Solution 6. you can identify the type of operating system to install for supported languages.

After selecting Add > Scripted OS Install. See Scripted Install for Linux (page 174). Scripted Install for Windows 1. Select source files. See Select Operating System Version and Language (page 170). when running subsequent scripted installs you do not need to add new source files for this version of Windows.create a kickstart answer file to remotely run a scripted install. 3. 5. 7. Note Before running a scripted install. See Installation Source Files (page 171). Click to distribute a DOS disk image (default). Click OK after entering a unique name and the path to the operating system installation source files.img file.8 SP2 169 . Select the type of Windows operating system to install. See Operating System-Source Files (page 171). See Operating System-Source Files (page 171). This process could take a few minutes. After the source files are copied. Service Pack source files are also stored as an WinSP00x. 6. Altiris® Deployment Solution 6. Click Next. However. They can be selected from the list of installation source files. delete hidden partitions or set RapiDeploy command-line parameters. Because the installation source files are copied over to the Deployment Share. Click Add New from the list to set up the new operating system installation files. The option reported by the PXE Manager is the default pre-boot environment option. Click Next. Click Next. Click the list to select the Windows operating system source files already copied to your Deployment Share. click the Windows option. Note When importing Scripted Install jobs. The source files will be copied over to the Deploy folder in the Deployment Share directory. See Installation Source Files (page 171). This is required for both the main installation and service pack installation files. you must edit the job files to point to the installation source files on the new Deployment Server system.PXE or BootWorks environments (DOS/Windows PE/Linux) drop-down list to perform the Distribute Disk Image task in selected pre-boot environment. select the newly created operating system source name from the Installation Source Files list. WinOS003 and so on. 4. DOS is not required if you are using your own scripts or utilities to partition and format the client computer. you must install DOS. with additional operating system source folders named to WinOS002. 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. 2. or continue without distributing a DOS image and partition and format the hard disk of the destination computer using custom scripts or setup utilities. The first source files added are given a generic name of WinOS001. Select the required pre-boot environment from the Automation . See also Importing and Exporting Jobs (page 192). Click Advanced to set partition size.

Select Operating System Version and Language Identify the operating system version to run in a scripted install. Select the operating system language. Click Template if you want to install another version or language of a Windows operating system not provided in the list. Select the language version of the operating system to install. List of supported multiple languages German French Spanish Japanese Simplified Chinese Altiris® Deployment Solution 6. 9. The selected version and language must correspond to your Windows installation files. Set up return codes for the Scripted Install task. The option reported by the PXE Manager is the default pre-boot environment option. Click Next. The language must correspond to the operating system source files. See Deployment Agent Settings for Scripted Install (page 173). Set command-line options for cmdlines. Select the required pre-boot environment from the Automation (Pre-boot Environment) drop-down list. If you selected the Template option. See Answer File Setup (page 172). Select the Windows operating system you want to install from the list.txt files and for the WINNT installation program. Click Next. Automation (Pre-boot Environment). View and modify the Deployment Agent for Windows configuration file from the dialog. 12. Click Finish.8 SP2 170 . See Setting Up Return Codes (page 193). See Scripted Install Summary (page 174). only the Multilingual language option can be selected (this is a generic language option). Boot Disk creator Image Explorer PXE Configuration Utility Remote Client Installer Control Panel Applet DS Info PW Util (Password utility) Switch Management Select the operating system version. 10. Click Next. Click Next. View the summary of the selected options. Import an answer file to the Deployment Database.8. Click Next. We support multiple languages for the following Deployment Solution utilities. See also Scripted OS Install (page 168). Create the Answer file. See Import an Answer File (page 172). See Command-line Switches for Scripted Install (page 173). 11. 13.

See also Scripted Install for Windows (page 169). Enter a description of the Windows operating system source configuration.img file. Installation Source Files If you copied installation files to the Deployment Share for previous scripted installs. the name of this install source configuration appears in the list box for each operating system type and language. Previous scripted install jobs will create a WinOS00x. Click OK and the files will copy from the source CD (or other volume) to the Deployment Server\Deploy directory in the Deployment Share.img file in the Deploy directory of the Deployment Share. The Windows operating system identified previously in the Installation Source Files dialog must match the source files selected here. Click this option to distribute a DOS image from the Deployment Share. This is optional. If the name and language of the operating system does not match the installation files. Enter a unique name for the operating system source files. Enter a short description. select Add new source files from the list box. Enter a name for the operating system source configuration files to assign an alias to associate with the install files for a specific operating system version and language.exe. A DOS image is provided in the Images directory in the Deployment Share (default path in the Name field). Enter the path to the I386 folder on the CD where the Windows installation programs and support files are stored. This process will take a few minutes. Partition and Format Disk Select a DOS disk image to distribute to the client computers before starting the Windows scripted install. To create new source configuration sets for additional operating system installs.8 SP2 171 . Example: browse to the CD drive and select I386\WINNT. Select the assigned name for each operating system source configuration in the list. Select or add new service pack source files. or select Add new source files from the list to create a new install task. 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). identify path and automatically copy Windows installation files to the Deployment Share. Enter path to operating system source files.See also Scripted Install for Windows (page 169). Select a DOS disk image. Operating System-Source Files Name operating system source configuration. for example: W2K Advanced Server SP3 English. Select or add new operating system source files. Run service pack updates immediately after installing the operating system during the scripted install process. See also Scripted Install for Windows (page 169). you receive an error. Click Open. The Deployment Server system includes a DR DOS image file that is Altiris® Deployment Solution 6. Previous scripted install jobs will create a WinSP00x.

Select to import a previously created answer file to the Deployment Database. click the right arrow until the Add new Section tab appears (the last tab on the right). select a value (a row) in the table. and distributed as an unattend. See also Scripted Install for Windows (page 169). A list appears in the Values column to change values for each entry. edited in the console (if required). See also Scripted Install for Windows (page 169). Select advanced options to set the size of the partitions. You can create your own MS DOS image from your Windows 98 CD and build a job. Advanced. Optional but selected values have a green check. Other optional values will be cleared. Required answer file values are selected automatically in the dialog with a gray check (you cannot clear these variables). An answer file is generated from the database (unattend. Select these optional values if you want to add them to the answer file when it is generated.txt.8 SP2 172 . Continue without distributing DOS image. To add a new section to the answer file. The answer file is imported to the database. You can add new variables to each section by selecting the bottom row named Add new Variable.txt) and distributed to each managed computer when the job executes. Click this option to not install a DOS image from Deployment Server. These values are stored in the Deployment Database. You can also view a summary of the operating system source configuration. See also Scripted Install for Windows (page 169). Import an Answer File Reference a previously created answer file for a Windows scripted install. Add a New Variable Value or Section Use this dialog to add new values to each variable or to add new variable sections to the answer file. Import existing unattend. The values for the answer file are imported from the delimited text file and appear in the Answer File Setup dialog.selected by default. Answer File Setup Use these dialogs to enter values to create an answer file for a scripted install. You can enter a path and select an answer file with any name. or to remove hidden partitions and add command-line options. The various tabs in the Answer File Setup dialog correspond to the general answer file sections. Skip this step if you are installing DOS using custom procedures for your environment. See Create Disk Image Advanced (page 162) and Distribute Disk Image-Resizing (page 166). See the Microsoft Windows Unattended Setup Guide for specific values for an unattended setup file.txt file to the client computer. In the Answer File Setup. Altiris® Deployment Solution 6.

See also Scripted Install for Windows (page 169). Altiris® Deployment Solution 6. password. or IP address types. Enter a value to be displayed instead of the real value.8 SP2 173 . You can change agent settings using this text-edit dialog. See Deployment Agent Settings (page 113) for a list of the Deployment Agent properties. Enter comments to describe the new variable. Enter additional Windows scripted install commands in this dialog. It appears in the Description column of the Answer File Setup dialog. You can also add scripted install command-line options. Default value of the variable. The commands execute in the order they are listed. Select this option to apply these settings globally. Command-line Switches for Scripted Install Use this dialog to enter Windows commands that are executed from the cmdlines. The provided command installs the Deployment Agent for Windows during the Install Component phase of the installation. This variable appears as a row in the Answer File Setup dialog. Enter an alias for list item types to appear instead of the real variable value. This is to maintain consistency in the way agent settings are applied. See also Scripted Install for Windows (page 169). Save these settings globally. See also Scripted Install for Windows (page 169).Enter a name for the value or section. See also Scripted Install for Windows (page 169). Description. Enter an alias that appears in the cell or on the tab. Add or edit switch commands to this line for the install program for the scripted install. this name appears in the new tab in the Answer File setup dialog.txt file. Select a variable data type. You can view and edit Deployment Agent settings in the next dialog. Displayed value of the variable. Select a variable name. Additional commands in the cmdlines. this name appears in the list and entered in the cell if selected. See the Microsoft Windows Unattended Setup Guide for your specific operating system values for an unattended setup file. text. Name of the variable. If you add a value. Enter values for a list. Add a New Variable Use this dialog to add new variables to the answer file.txt file. Deployment Agent Settings for Scripted Install View or edit Deployment Agent for Windows settings in this dialog. If you are adding a section. The Default value and Displayed value boxes are enabled depending on the variable type selected. Type of new variable. Switches.

set the command-line options for the cmdlines. Follow steps in the wizard to identify the type of scripted install Altiris® Deployment Solution 6. Click Next. 7. The answer file is prepared using the information entered so far. Note You can select the Continue without selecting DOS image\Diskpart Tool option to partition and format the hard disk using your own scripts and setup utilities. 3.txt file. Follow the steps in the wizard to identify the type of scripted install as Vista. Click Next.XML file. 5. Scripted Install for Windows Vista The Scripted OS install for Windows Vista provides a wizard to help set up Vista installation files and run sample jobs. select Vista. 2. From the drop-down list on the Scripted Operating System Installation screen of the Scripted OS Install dialog. See also Scripted Install for Windows (page 169).txt files and enter the additional commands in the cmdlines. Scripted Install for Linux The Scripted OS install for Linux provides a wizard to help set up Linux installation files and run Sample jobs. From the Select or add new service pack source files drop-down list on the Installation Source Files screen of the Scripted OS Install dialog. select the Modify Product Key check box. Click Finish. but the server does not build any answer file. browse to select the path of the unattended . You can gather all the files for Vista for the job. Also.Scripted Install Summary View a summary of the selected options for the scripted install. On the Answer File Setup screen of the Scripted OS Install dialog. 6. select the none option. On the Scripted Operating System Installation screen of the Scripted OS Install dialog. Enter the product key. Instead. To perform a Scripted Install for Windows Vista 1. 4. you are asked for the location of the answer file. select the following options: Windows Vista as the operating system Operating system language Automation pre-boot environment Click Next.8 SP2 174 . Click Back to change any of these settings or click Finish to complete the Scripted Install task. Click Next. From the Select or add new source files drop-down list on the Installation Source Files screen of the Scripted OS Install dialog. On the Scripted OS Install Commands screen of the Scripted OS Install dialog. Select the Select a DOS disk image\Diskpart tool option on the Partition and Format Disk screen of the Scripted OS Install dialog to partition and format the disk. a sample answer file is provided.

Browse to or enter the path and name of the Linux answer file (Kickstart file).RIP or a Personality Package. Command-line.CAB.TMaya. Specify the users to associate with the . Example: to install a . If you want to send the package to a managed computer with multiple users and to install it for certain users with a unique password. Note Information about the package appears in the Description area for valid packages. 4.RPM files for Linux computers. .MSI Packages. Enter the command-line options. For .EXE. The option reported by the PXE Manager is the default pre-boot environment option. Directory. Enter the name and location of the package to distribute in the Name field. Scripted Install Summary View a summary of the selected options for the scripted install. 2.RIP for a specific user accounts on a computer add values to the Additional command-line switches field: -cu:”JDoe.8 SP2 175 . Select Run in quiet mode to install the package without requiring user interaction.Domain\BLee” Altiris® Deployment Solution 6. Distribute software packages to managed computers using the New Job Wizard or adding the Distribute Software task when Building New Jobs. 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.RIP. Click Back to change any of these settings or click Finish to complete the Scripted Install task. the file is not a . Automation . This task identifies valid Altiris packages and assigns passwords and command-line options. 1.RIP or the Personality Package. 3.RIPs. and other package files to selected computers or computer groups.PXE or Bootworks environment (DOS/Windows PE/Linux). and . If no description appears. if you set the password option when you created the . Click Apply to all users to run the package for all users with accounts on the computer. By default the DOSManaged Boot Option type is selected. clear the Apply to all users box. See also Scripted OS Install (page 168) and Scripted Install for Windows (page 169).and locate the answer files. . Distributing Software Send . You can also modify and run Sample deployment jobs to remotely run a scripted install on Linux servers and workstations. you must enter the password for the package to run. including EBS.

for protection against harmful software. not the files that actually get installed to various locations on the target computer. Click Next. For a complete list of command-line options.MSI and Personality Packages.8 SP2 176 . 9. as the "Value data" of a string value named "RenameDistPkg" under the "HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Altiris eXpress\Options" key. or of manually renaming distribution packages. Click Finish. This feature only affects files that are temporarily copied to the client computer as part of a "Distribute Software" task. only lets software programs on a list of "well-known" executables to run. only the main (installable) file is renamed. the system administrator may update the well-known-executable list once with a filename of their choosing.Note The command-line switches are specific to any package you are distributing that supports command-line options.exe). whenever the system administrator wanted to install a patch on client computers.RIP or Personality Package is executed through Deployment Server. you can click Copy all directory files to install all peer files in the directory. the quiet mode command-line option is applied. is the file that gets renamed. If the RenameDistPkg registry entry is set. 7. The well-known filename may be entered into the Windows registry of the Deployment Server computer (the computer running axengine. Provide additional command-line options for distributing software. See Setting Up Return Codes (page 193). The file that is to be executed only during the installation. Deployment Server renames the installation files that are copied to the client computers. 8. Now. You can copy through Deployment Server. To save the work of updating that list. See Distribute Software Advanced (page 177). sometimes referred to as the "package". Note Some clients may have software installed on the client computer that. If distributing an install package or other types of packages with associated support files. such as . he or she would have to update the well-knownexecutable list on all the client computers. If the Copy all directory files option is enabled task. or copy and run directly from the Deployment Share or from another file server. the "RenameDistPkg" feature was added. Altiris® Deployment Solution 6. which could be a lot of work. 5. This means the user cannot interact with the user interface on the managed computer. Notes When a . Click Copy subdirectories to distribute peer files in the directory and all files in associated subdirectories. (Optional) Set Return Codes. Therefore. see the Wise MSI Product Guide and the Altiris PC Transplant Pro Product Guide. 6. Click Advanced to specify how files are distributed to the managed computer.

deactivate or reset SVS layers. without altering the base Windows application. We recommend that you use the Copy files using Deployment Server option for these types of computers or plan a proper security strategy for direct copying. Managing the SVS Layer The Manage SVS Layer task lets you instantly activate. File source access and credentials. See also Modifying Tasks in a Deployment Job (page 189).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. For more information on SVS Help. It copies the file and runs it. Note This task runs only on Windows computers. the package runs the next time that user logs in. Click this option to run files remotely from the Deployment Share or another selected file server. and activate or deactivate the layers as required. Distribute Software Advanced Copy files using Deployment Server then execute. Note Windows 98 computers have security limitations when copying files directly from the source to the Deployment Agent using the UNC path name. 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. Click this option to copy packages directly from the Deployment Share if this data store is located on another server (a Custom install). Both must have the same user name and password (this is not an issue if both are on the same domain). If the user does not have an account. This option is run for Simple installs and is the default option. refer to the Software Virtualization Solution (page 81)section. Copy directly from file source then execute. Execute directly from file source. as you can install different versions of an application on the layers at the same time. You can reduce the testing time for applications. This task helps in avoiding conflicts between applications. If the package is not run through Deployment Server.8 SP2 177 . a message appears on the managed computer and the user is prompted to abort or continue. the package aborts and sends an error back to the console through the Deployment Agent. avoiding running through Deployment Server and diminishing processor output. Altiris® Deployment Solution 6. Enter the user name and password for the client computer and the Deployment Share. Manage the SVS Layer using the New Job Wizard or adding the Manage SVS Layer task when Building New Jobs.

Activate layer on startup. Select Manage Layer to manage the selected layer using actions present in the Action drop-down list. Deactivate layer on startup. After creating a job.8 SP2 178 . 5. Activate layer and activate it whenever the computer starts up. 4. instead of browsing or typing the . If it finds that the file path is correct and it is a valid . it replaces the path name with the layer name in the . This makes it easier for you to select a layer from the list. 3. and immediately activate it and activate it whenever the computer starts up. You can also enter a . 2. Click Advanced to copy files using the Deployment Server or copy files directly from the file source. SeeImport Package Advanced (page 179). Note The console displays a list of the previously selected layers in the Layer name drop-down list.VSA file name again. or browse and select a .VSA file. Enter the .1. Deactivate layer and deactivate it on startup.VSA file. Delete layer.VSA file path in the Layer name drop-down list. Deactivate layer.VSA file name in the Layer name drop-down list.VSA file. Reset layer. The actions are: Action Name Activate Activate on startup Activate and Activate on startup Deactivate Deactivate on startup Deactivate and Deactivate on startup Delete Reset Description Activate layer. click Add > Manage SVS Layer. Import package and immediately activate it. Altiris® Deployment Solution 6. Import package. Select Import Package to import the selected layer and apply the actions present in the Action drop-down list. The Console checks if the path entered is correct. The actions are: Action Name (none) Activate Activate on startup Activate and Activate on startup Description Only import package. Import package and activate it on startup.

Reset and deactivate layer. The personality template lets you define the settings. A default personality template is included in the PCT folder of the Deployment Share (DEFAULT. Capture personality settings using the New Job Wizard or adding the Capturing Personality task when Building New Jobs. files. To purchase a permanent license. Set Return Codes. 2. and options to be captured during run time. Enter the name of a personality template. 7.8 SP2 179 . Import Package Advanced Copy files using Deployment Server. click Add > Capture Personality. This is optional. Reenter the password in this field. Click Template Builder to open a wizard to build a custom template. Select this option to copy files using the Deployment Server. Select this option to copy files directly from their source. Note SVS clients have an automatic 120-day license. Password. Click OK. you need to enter the following File source logon details: User name. After creating a job. Enter the password in this field. Copy directly from file source. Description Reset and activate layer.PBT). Select User defined action to enter a command line. Enter the user name in this field. or browse and select a template. please visit the Altiris Sales Web site (www.aspx). 1. Confirm Password.com/sales. You can create a Personality Package that can be saved and distributed when migrating users.altiris.Action Name Reset and Activate Reset and Deactivate 6. If you select this option. Altiris® Deployment Solution 6. Enter the name of the folder where you want to store the package. This task runs Altiris PC Transplant from the console to capture and distribute settings. See Setting Up Return Codes (page 193). Capturing Personality Settings The Capture Personality task lets you save personal display and user interface settings defined in the operating system for each user. See Distributing Personality Settings to migrate settings to another user.

8 SP2 180 . 4. You can distribute Personality Packages to migrate personality settings. An error is returned if you attempt to capture personality settings on Windows 9x computers that are not authenticated. Altiris® Deployment Solution 6.3. enter the login credentials for the managed computer from which the personality settings are captured. ensure that the User account and folder login fields are blank. 8. Specify users or groups to capture personality settings. A user must also be logged on at the client computer to capture the client profiles. Set the Advanced options and click OK. See the Altiris PC Transplant Reference Guide in the docs folder of the Deployment Share. ensure 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). The Capture Personality task appears in the Task list. Select this option to capture personality settings for all domain users on the computer. See Distributing Personality Settings (page 180). You have now captured a personality setting and saved it as a PCT file in the selected location (most often in the PCT folder on the Deployment Server shared directory on the Deployment Share). 5. instead of specifying names. Set Return Codes. This is a run time password that is required when the Personality Package runs on the destination computer. In Package login. Custom. Select this option to capture personality settings for all local users on the computer. We recommend that you don't capture personalities for mixed groups of Windows 98 and Windows 2000/XP/2003 computers. Click Finish. See Setting Up Return Codes (page 193). you can also select users that have been either created or last accessed in a specified number of days. and the file server where the Personality Package is stored. Distributing Personality Settings The Distribute Personality task lets you save personal display and user interface settings defined in the operating system for each user. Set the conditions on the job for either Windows 98 or Windows 2000/XP/2003 computers to ensure that the appropriate Capture Personality task runs on the appropriate computers. Click Advanced to specify additional features. Also. Local Users. 6. You can add command-line options specifically for the PC Transplant program that migrates personality settings. Notes To capture a personality on a Windows 98 computer. Also. In User account and folder login. 7. Click Next. This is optional. This task runs Altiris PC Transplant from the console to capture and distribute settings. Capture Personality Advanced Domain users. Select the Custom check box and enter the Users or Groups you want to capture personality settings. enter a password for the Personality Package. Additional command-line switches.

Note The information about the Personality Package appears in the Description area for valid Personality Packages (PCT files). 9. For a complete list of command-line options. 8. If you want to send the package to a managed computer with multiple users and to install it for certain users with a unique password. the user must enter input before the job completes. See Capturing Personality Settings to create a Personality Package. see the Altiris PC Transplant Reference Guide.8 SP2 181 . In the Name field. and you proceed with the job. This is optional. 5. Set Return Codes. clear the Apply to all users box. or copy and run directly from the Deployment Share or from another file server. If you use a token. BLee Note The command-line options are specifically for Personality Packages. See Distribute Personality Advanced (page 182). If no description appears. 4. Click OK (if you are using the New Job Wizard). This is optional. In the Password field. You can copy through Deployment Server. Example: to install a Personality Packages for a specific user accounts on a computer. Select Run in quiet mode to install the package without displaying the PC Transplant screens. such as %COMPNAME% in this field. when you apply the job to a Windows XP computer. Set Advanced options and click OK. See the Altiris PC Transplant Reference Guide for a complete list of valid commandline options. Altiris recommends you enter a valid Personality Package name and use the Additional command-line switches fields for token values. type the password set for the PCT file when created. TMaya. 3. Click Apply to all users to run the package for all users with accounts on the specified computer. Click Finish. See Setting Up Return Codes (page 193).Distribute personality settings using the New Job Wizard or adding the Distribute Personality task when Building New Jobs. 2. 6. 1. add values to the Additional command-line switches field: -user: JDoe. enter the file name and location of the PCT file. Altiris® Deployment Solution 6. the file is not a valid package. 7. Click Advanced to specify how Personality Packages are copied to the managed computer. Specify the users to associate with the Personality Package. or Click Next.

Set Return Codes. See Computer Configuration Properties (page 103). you need to identify a user name and password for the data share computer from the target computer. the check box for Reboot after Configuration is selected.For more information about capturing a computer's personality settings. This is optional. Enter or edit the property settings in the Configuration dialog. Run directly from file source. 1. requiring two file copy transactions if the Deployment Share is on another file server. and click Add > Modify Configuration. See Setting Up Return Codes (page 193). Enter the user name and password for the client computer and the Deployment Share. double-click the job. Click this option to run files remotely from the Deployment Share or another selected file server. This is the default option. See also Modifying Tasks in a Deployment Job (page 189). Use this option for Simple installs to take advantage of security rights defined by Deployment Server. The Deployment Agent updates the property settings and restarts the computer for changes to take effect. 6. Click this option to distribute software packages through Deployment Server to the managed computer. Because the Deployment Agent doesn't recognize shared rights and is not guaranteed to have a mapped drive to the data source. see the Altiris PC Transplant Help. Copy directly from file source. After creating a job. sending only one copy across the network. Both must have the same user name and password (this is not an issue if both are on the same domain). 2. Modifying Configuration You can add a task to configure or modify the configuration of computer property settings using the Modify Configuration dialog. It copies the file and runs it and avoids running through Deployment Server and diminishing processor output. Click Next. File Source Credentials. See also Distributing Software (page 175) and Modifying Tasks in a Deployment Job (page 189). 4. 5. Click Finish. Select the Reboot after Configuration check box to restart client computer after the configuration changes are complete.8 SP2 182 . By default. 3. Backing up and Restoring Registry Files Note This feature has been deprecated and removed from the product in a later release. Altiris® Deployment Solution 6. Distribute Personality Advanced Copy files using Deployment Server. Click this option to copy packages directly from the Deployment Share. Click the category icons in the left pane to set additional values for each property setting group. This option also requires a full UNC path name in the Source Path field in the Copy File dialog.

and select Get Inventory from the list. Click Advanced if Windows was installed on client computers in a directory other than the default. You can view the history of the Get Inventory task in the Computers History pane.PXE or Bootworks environment (DOS/Windows PE/Linux) drop-down list to perform the Backup and Restore task in the selected pre-boot environment. See Setting Up Return Codes (page 193). 6. See Viewing a Computer’s History (page 129). This is optional. By default the DOSManaged Boot Option type is selected. only the Administrator and Guest user accounts are backed up or restored.8 SP2 183 . See also Modifying Tasks in a Deployment Job (page 189). Copy registry settings by adding the Back up Registry task when Building New Jobs. Select Include registry information for all users to back up registry keys for all user accounts.PXE or lets you environments (DOS/Windows PE/Linux) drop-down list to perform the Backup and Restore task in selected pre-boot environment. Enter the correct path to the root of the Windows directory. Restore registry settings by adding the Restore Registry task. Enter the directory path to back up or restore registry files.Copy registry files of selected computers using the Back up Registry task and save the registry file settings to a selected directory. Set Return Codes. 7. Note If you clear this check box. Click Next. The option reported by the PXE Manager is the default pre-boot environment option. 4. 3. Select the required pre-boot environment from the Automation . Run Script Select an existing script or write a new script file to run on selected managed client computers. Click Add. Select the required pre-boot environment from the Automation . 5. The option reported by the PXE Manager is the default pre-boot environment option. Altiris® Deployment Solution 6. Get Inventory Use this task to gather inventory from an individual or group of client computers. 1. Click Finish. This ensures that the Deployment database is up-to-date with the latest computer properties information. 2. You can also create a Restore Registry task to copy the registry settings to a managed computer.

This option runs a server-side script on the Deployment Server of the managed computer. or click Import and select a script file to import. 8. click Modify. or Linux. Click Next. Script Information Click an option to run the script on a selected managed computer or to run the script on the Deployment Server computer. Note To run scripts that call an executable. 3. FIRM can only copy files and delete files. Some programs return a code of one (1) to denote a successful script execution. 1. Click Finish. Example: you can add a task to Altiris® Deployment Solution 6. See also Modifying Tasks in a Deployment Job (page 189). If you have a script file defined. See Script Information (page 184). Type the script in the provided text box. Set Return Codes. Notes When a computer is in an automation mode using a DOS configuration. 4.Run script files on client computers by adding the New Script task when Building New Jobs. Locally on the Deployment Server. 6. it cannot run code on a drive. The option runs the script on the managed computer to which you assign the job. 2. you can edit the script file to return a code that the console interprets correctly. Click Next. To modify the return codes.8 SP2 184 . To run a script using the DOS Automation Agent. In most cases you can create a serverside script task that runs in context with other tasks. Example: start C:\windows\notepad. and an option for server-side execution of the script. click Run the script from file and browse from the folder icon to select the file. Set Script Information. 5. you see an error message at the Deployment console even though the script ran correctly. To read or edit the script file. click Run this script. 7. script security. Windows.exe opens the Notepad application on the client computer. use FIRM (Filesystem Independent Resource Manager) commands. use the start command. See Script Information to identify how the script appears. When a script is imported you can modify it in the text box. To create a new script. Deployment Server assumes a return code of zero (0) as a successful script execution. This is optional. Specify whether the script should be run from DOS. See Setting Up Return Codes (page 193). it does not see DOS partitions. Script Run Location On the client computer. If a program returns a one (1).

Click to run the script in the automation environment. Script Options .8 SP2 185 . If you have selected to run the task on the local Deployment Server. You can run in either production or automation mode. Automation . The script runs on the Deployment Server of the managed computer. Use the network security account established to administrate all managed computers. Default (local system account). Example: if you run a DOS command locally on the Deployment Server. Select a pre-boot automation environment from the drop-down list. If you select DOS as the operating system type. (In most cases Deployment Server does not have the Deployment Agent installed. Select how you want the script window to appear: minimized. normal.(Windows/Linux) Additional command-line switches. If you select Linux as the operating system type. When running the script on the Deployment Server. You can make similar changes to your script files as needed. See Using LogEvent and WLogEvent in Scripts (page 186). Example: if you create a job with a script to run locally on the Deployment Server and assign the job to 500 computers. the script runs on the Deployment Server 500 times.image a computer and 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. This identifies the security options for running scripts. prohibiting it from using a network security account. 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). but is not visible. Client Run Environment Select the environment for your client. Note Scripts requiring user intervention do not execute using this feature. you are required to enter an administrator user name and password for that Deployment Server account.PXE or Bootworks environment (DOS/Windows PE/Linux). CONVERT /FS:NTFS Altiris® Deployment Solution 6. the Locally on the Deployment Server option and the Production . the Locally on the Deployment Server option is disabled and only the Additional command-line switches under the Production Client installed OS (Windows/Linux) is enabled. Example Script The process to convert NT4 from FAT16 to NTFS normally returns a 1 after a successful completion. the Command Prompt window does not open on the Deployment Server computer when the script executes. Specific user. maximized. Enter in commands to execute when the script runs in Windows or Linux.Client-installed OS (Windows/Linux) This is the type of Security Context. Production . it executes specifically for the assigned managed computer.Client-installed OS (Windows/Linux) option is disabled. Use the -id option for running scripts on Deployment Server when using the WLogEvent and LogEvent utilities. or hidden.) Script Window.

accommodates detailed logging to help debug complex scripts. See the Locally on the Deployment Server option on Script Information to select a server-side script. Specifying a severity level of 3 causes the script job to fail. For server-side scripts you must add the id:%ID% switch.if ERRORLEVEL 1 goto success goto failure :success set ERRORLEVEL = 0 goto end :failure echo Failed set ERRORLEVEL = 1 goto end :end Using LogEvent and WLogEvent in Scripts The logging features. See Setting Up Return Codes (page 193). A DOS-based tool can be called from any script file to log status and error codes. The following levels are used: 1 = Information message 2 =Warning message 3 = Critical failure message. id is used for server-side scripting only. level is the severity level. LOGEVENT -c:code -id:%ID% -l:level “-ss:message” code is any number for a return code level. The console displays and works with the new status messages. the string must be contained in quotes. Only this level can be used to set up a return code. The response does not execute for a return code unless a level 3 is specified when using the LogEvent and WLogEvent command in a script.8 SP2 186 . It is a light-weight reporting tool that can log both status strings and status codes to the history file and the console. WLogEvent — Use the WLogEvent utility for Windows scripts. These utilities include the following features: Logging is stored in the database instead of a log file. The LogEvent and WLogEvent utilities are command-line driven only — there is no user interface. If spaces exist in the message. LogEvent and WLogEvent. message is the status string. LogEvent posts status messages back to the Deployment Console. LogEvent — Use the LogEvent utility for DOS and Linux scripts. Use both utilities with the following switches. letting you view the status of the script. Altiris® Deployment Solution 6.

exe -c:0 -l:1 “-ss:Finished with the DIR command on %NAME%" Copy File to Copy all types of files to managed computers.” REM Execute WLogEvent. Click Copy Subdirectories to copy all subdirectories.8 SP2 187 . 3.exe from CMD script REM This script requires WLogevent. 2. The Source path defaults to the Deployment Share. 1. Specifically. 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. See Copy File to Advanced (page 188). To copy files or directories through Deployment Server from the Deployment Share.exe -c:0 -l:1 “-ss:Running Dir on %NAME%" dir . Select the Allow to run in automation check box to run this task in automation mode. Note When entering the source path for copying files through the Deployment Server. but you can type or browse to a file or directory.\WLogevent. you must enter the full UNC path name. you can only use UNC paths when you have sufficient authentication rights established.exe to reside on the client REM in the temp directory . you can only access the shared directories through an established user account.Example Scripts REM Bootwork unload Set ImageName=F:\Images\XPIntel.\WLogevent. You can send selected files or directories to a computer or computer group. To copy files or directories directly from the Deployment Share to the managed computer. Altiris® Deployment Solution 6. you can enter a relative path in this field.img rdeploy -mu -f%ImageName% -p1 logevent -l:1 “-ss:Created %ImageName. Enter the directory path and name of the file or directory. Click either the Copy File or Copy Directory option.

Use this option for Simple installs to take advantage of security rights defined by Deployment Server. requiring two file copy transactions if the Deployment Share is on another file server. The current variables include: Temp. Both must have the same user name and password (this is not an issue if both are on the same domain). Using Location Variables Location variables are being added to Deployment Server for the Copy Files feature.Note This option is only applicable for Linux and WinPE automation. This is the default option. It copies the file directly to avoid running through Deployment Server and diminishes processor output.exe. See also Modifying Tasks in a Deployment Job (page 189). Type the destination path. Copy files using Deployment Server. See Setting Up Return Codes (page 193) (Optional). you need to identify a user name and password for the data share computer from the target computer. See Copy File to Advanced (page 188). Set Return Codes.8 SP2 188 . Note Windows 98 computers have security limitations when copying files directly from the source to the Deployment Agent using the UNC path name. Click Advanced to specify additional features to copy files through Deployment Server or directly from a file server. 6. The Destination path field automatically enters a sample path. sending only one copy across the network. Enter the user name and password for the client computer and the Deployment Share. 5. 8. If the destination path does not exist on the destination computer it is created. but you can enter the directory path you require. This option also requires a full UNC path name in the Source Path field in the Copy File dialog. Click this option to copy packages directly from the Deployment Share. Because the Deployment Agent doesn't recognize shared rights and is not guaranteed to have a mapped drive to the data source. We recommend that you use the Copy files using Deployment Server option for these types of computers or plan a proper security strategy for direct copying. You can use a relative path name entered in the Source Path field in the Copy Files dialog. Copy directly from file source. Click Next. Copy File to Advanced Select options to copy files directly from the Deployment Share. 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. This option distributes software packages through Deployment Server to the managed computer. 4. Altiris® Deployment Solution 6. 7. Click Finish. letting you 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). File Source logon. This option is for files stored on another network server in a distributed Deployment Server installation. just enter temp:setup.exe in the Destination path.

(Optional) Set Return Codes.8 SP2 189 . Create a job. The Wait Information dialog appears. 5. 1. Click Add > Power Control. 3. To add a task to a job 1. Wait Use the Wait task to boot a computer in the automation mode and wait for user interaction. See the Power Control operation to send commands quickly from the console. See Setting Up Return Codes (page 193) (Optional). or log off the current user. it appears on your Resources list in the Shortcuts pane. shut down. Click Finish. any computer already scheduled to run the job runs the modified job. Shut down (if available). and so on) is saved in the product directory. Altiris® Deployment Solution 6. 3. To add a task to a job immediately If the task (image. 4. Click Add > Wait. select the appropriate pre-boot environment. 5. When you modify the tasks in a job. 1. 6. Set Return Codes. Modifying Tasks in a Deployment Job You can build jobs by adding or modifying deployment tasks. Select an option: Restart. Simply drag it to an existing job and it is added. 2. Select Force application to close without message. 7. From the Select automation pre-boot environment (DOS/Windows PE/Linux). if applicable. 4. Create a job. executable. Wake up. 2. See Setting Up Return Codes (page 193). 6. batch file. Click Finish. shut down or log off client computers by adding the Power Control task when Building New Jobs. Click Next. Double-click the job you want to modify in the Jobs pane.Power Control Start the computer using Wake on LAN or run standard power control options to restart the computer. Log off or Wake up (Send Wake-On-LAN). Click Next.

(To copy multiple tasks. 2. The tasks appear at the bottom of the task list.8 SP2 190 . 3. 1. After finishing task configuration. 5. Click Modify and follow the directions to make your changes. The tasks that are highlighted are copied when you select Copy. To copy and paste a task Use the steps below to copy and paste tasks within the same job. Change the order of the tasks using the up and down arrows. To modify a task in a job 1. 5. 3. 4.2. a new task appears in the Jobs list. You can use CTRL+C and CTRL+V to copy and paste tasks. right-click the task. or from one job to another. and use the condition settings of the current job. Click the job that contains the task you want to copy in the Jobs pane. Right-click in the Details pane and select Paste Task. 2. To copy and paste tasks Use the steps below to copy and paste tasks within the same job or from one job to another. 2. In the Details pane. right-click the task. The tasks execute in the order listed. click the destination Job where you want to paste the task. 1. Click the job that contains the task you want to copy in the Jobs pane. and select Copy Task. To remove a task from a job 1. In the Details pane. (To copy multiple tasks. Double-click the job you want to modify in the Jobs pane. Follow the basic instructions on each dialog provided for each task. press the CTRL key and select the desired tasks. Click Add and select another task from the menu. The tasks appear at the bottom of the task list and use the current condition settings of the destination job. Altiris® Deployment Solution 6. 3.) In the Jobs pane. The tasks that are highlighted are copied when you select Copy Task. The tasks execute in the order listed.) In the Jobs pane. Click Delete. You can also use CTRL+C and CTRL+V to copy and paste tasks. and select Copy. press the CTRL key and select the desired tasks. Right-click in the Details pane and select Paste. 3. Select the type of task you want to add and follow the directions. Change the order of the task using the up and down arrows. The tasks execute in the order listed. 3. Double-click the job you want to modify in the Jobs pane. 5. Select the task you want to remove from the task list. 4. Click OK. click the destination Job where you want to paste the task. 2. Change the order of the task using the up and down arrows. Click OK. Select the desired task from the list. 4.

A message appears. To create new script files 1. 5. The new task is inserted above the task you highlighted. and save it. Go to View > Shortcuts View. Note The Script File option is activated only if the focus is on the Resources view. Altiris® Deployment Solution 6. Use the up and down arrows to change the order of the tasks within the job. The default file name is Batch. 4. Type the script in the open file. 2. and all other jobs shift down one position. Note You can rename the batch file. Go to File > New > Script File. Select a job from the Jobs pane. Click Finish. Select one or more computers and click Next. Click on one of the tasks within the job and add a new task. a Modify Job wizard appears with a list of each managed computer scheduled to change configuration settings.bat. 4. Set Return Codes. See Setting Up Return Codes (page 193).bat file.8 SP2 191 . Creating New Script Files You can create script files and directly schedule the script file to run scripts on any computer or computer groups. Click NO to modify the Change Configuration task when the job is scheduled again (the current job sends modified configuration files already created). If you click YES. 2. In the Computer Configuration Properties property page. 3. 1.To add a new task to an existing task list 1. 2. Click Resources in the Shortcuts view to move the focus to the Resources view. Click the job in the Jobs pane with a Change Configuration task. Right-click the Batch. Double-click the Change Configuration task. and select Modify. Click Next. and selecting Rename. Click YES to modify configuration settings individually for each scheduled computer. modify settings. Modifying Multiple Change Configuration Tasks If you have scheduled multiple Modifying Configuration tasks to a computer group. you can double-click Change Configuration in the task list of the Details pane to modify each computer’s configuration settings independently. by right-clicking the file. 3. 3. A script file is created by default at the root of the resources.

Copy and Paste Jobs and Job Folders Jobs or job folders (including their subfolders) can be copied to any other job folder in the left pane of the Jobs pane of the Deployment Console. it appears in the edit field. and click OK. 4. 2. Drag the Batch. Select Delete existing jobs in folder to overwrite and replace all jobs in the selected Jobs folder. To export jobs 1. Right-click in the Job pane. Click OK to import the job(s). Select Import to Job Folder to import the jobs to an existing folder in the Jobs pane. 2. 3. and cannot be copied to a child level folder. To import jobs 1. To copy jobs and job folders 1. Select Overwrite existing Jobs and Folders with the same name to replace identical jobs and folders. and select Import or Click File > Import/Export > Import Jobs. In the Jobs pane. Browse to or type the path and name of an existing import file (a . Importing and Exporting Jobs Jobs can be exported to back up Deployment Server data or to share jobs between Deployment Server installations. 4. Specify the scheduling options. This feature can only be performed by administrators or users who have been granted permissions to create jobs. which has a limit of 30 subfolders. 3. 7. Click Export subfolders to export all folders subordinate to the selected job folder.BIN file). and click Copy. Right-click the job or Jobs folder you want to export and select Export. the copied job or folder is automatically named Copy of <job or folder name>. A Job folder can only be copied to a root level folder. right-click a job or job folder you want to copy. Click OK.8 SP2 192 . Right-click the destination job folder in the Jobs pane and click Paste. or Click File > Import/Export > Export Jobs. If you have a folder already selected.6. If you copy a job or folder with the same name as the destination job or folder.bat file to a computer or computer group where you want to schedule the job. or job folders. 2. 5. See Scheduling Jobs (page 155). Select the destination folder and enter a file name. Altiris® Deployment Solution 6.

it runs the action in the Success box. Altiris® Deployment Solution 6. personality settings. any other return code value denotes some type of failure in running the task. select the status from the Status list to specify the interpretation of this return code as Success or Failure. Note If you are using LogEvent and WlogEvent in Scripts.8 SP2 193 . you can determine these specific actions: Stop. Subsequent tasks do not run. If the task returns as successful. Custom Return Codes In the Other return codes area. the selected action for that custom code is executed. Note Return code handling cannot be set up for jobs created in the New Job Wizard. you can view custom return codes set specifically for your system. When creating a task. These actions also apply to custom return codes designed specifically for your system. Return Code Actions For both successful tasks (in the Success field) and failed tasks (in the Default field). or select an action in the Default field if the return code is not a 0 (zero). You can determine the response if the task runs successfully or if the task fails. it determines if the return code has been assigned a custom code value.Setting Up Return Codes When you create a task in a job. the action set in the Default is executed. You can add return codes by clicking Add below the Other return codes area. You can also set up custom return codes generated from scripts or batch files that are unique to your environment or deployment system. These custom codes can respond to any return codes set up in scripts or batch files in the Run Scripts task. select a response action from the Response list. or by clicking Master Return Code. This action lets you select existing jobs to run after the task completes. Return codes are first evaluated to be successful (zero) or failed (non-zero). Any task can have custom codes that respond to different return code values. and provide a message in the Message field. As a result. This action continues with subsequent tasks in the job after the task runs. If no custom code is assigned to the return code. If the return code is defined as a custom code. or disk images. you can define a response to specific return codes generated from that task after it runs. If it is not successful. or these custom codes can respond to system return codes thrown from Deployment Server or external codes generated when distributing applications. Specifying a severity level 3 causes the script job to fail and lets you respond using this return code feature. in the Success field you can select an action if the return code is 0 (zero). the Return Codes dialog appears so you can set a response if the task was successful or to determine a default response if the task failed. Select a job. you can generate return codes only when the level 3 message is specified. This action stops the job after the task runs. Continue. Because Deployment Server returns a 0 (zero) if the task runs successfully. Type a custom code in the Code field.

The code is added to the master list.Master Return Codes. but not from the Master Return Codes list. 5. Click Modify. This lets you delete return codes listed in the Other return codes area. Modify. Enter data in the Response. 2. Click Next until the Return codes page appears. 3. To add Master Return Codes 1. This lets you add a new custom return code for the task. Click Add in the right pane to add a task. The Modify Return Code dialog appears. A warning message appears to confirm the deletion. OK is disabled. 4. The Add Return Code dialog appears. This is a list of all the return codes existing in the Deployment database. 2. Delete. modify. Click Delete. Select the task. To delete Master Return Codes 1. Click OK to delete the return code from the Master list. Enter the return code in the Code field and click OK. Click OK on the Master Return Codes List dialog to add the selected return codes to the current job. This lets you modify the return codes listed in the Other return codes area. The task dialog appears. 6. and remove return codes in the master list. Note You can add Master Return Codes for all tasks except Get Inventory. Result. how to respond to a failure Altiris® Deployment Solution 6. Note The OK and Cancel options apply to the return codes selected. 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. To set up Master Return Codes The Master Return Code List dialog lets you: Add. or none exist in the list. If no return codes are selected.8 SP2 194 . and Status fields and click OK. Click Add. Add. Select return codes for the current job from the drop-down list. 2. The changes you make do not update the Master Return Codes list. Select a job from the Jobs pane. You can add. The code is modified. Click OK. Click Master Return Codes. and delete the codes and their values so that setting codes for other tasks is easier. The Master Return Codes List dialog appears. You can also add the return code to the Master Return Codes list. modify. To modify Master Return Codes 1.

The Add Return Code dialog appears. Sample Jobs in Deployment Solution Sample jobs are installed with each Deployment Server system.return code (a non-zero) in the Default box. Even if the return code was not zero. keep the default value Continue. Click Add to add custom return codes. Click the Response drop-down arrow and select Continue from the list. letting you quickly modify or add parameters. 4. the Other return code and Master Return Codes list. However. or to run the sample jobs as they are. 3. 10. Click each job and identify its features in the Description field of the Details pane. 9. The example below describes how to set up a simple process to deal with custom and system return codes. you may get an error. If the code you added already exists. Click the Result drop-down arrow and select Success from the list. enter a value of 10 (ten). All files without an asterisk (*) can be used to perform the identified functions without modification. 5. 6. Note The status of the tasks executed in a job also appears in the history of a computer. Jobs requiring input parameters or customizing do not function properly if you do not edit the job with the information specific to your environment. and how to respond to a custom or externally generated return code defined in the Other return codes box. This lets the job continue running additional tasks in the job after successfully completing this task. and how to interpret the status of user defined return codes: 1.bin file to the Deployment Server system where they can be viewed in the Samples folder in the Jobs area of the Deployment console. and click No to return to the Add Return Code dialog. 7. 2. This is the message that appears when the task within a selected job. The return code is added to the list of Other Return Codes. a message dialog displays the return code and asks if you want to replace it. executes. if the job conditions are not met or are not consistent with the computer type. Jobs in each folder marked with an asterisk (*) require input parameters or other minor modifications added before running on your system. During installation. Select Select a job from the Default box to select a job to be executed when a default condition is reached. letting you 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. In the Code field. Enter a description for the return code in the Status field. The code is listed in both. Select the Add to Master return code list check box to add the custom code to the master return code list. such as user name and password or other required data for the job to be functional. Example: if the Repair Office XP job runs on a computer without MSOffice XP. the task is considered a success as per the user’s choice. Click Yes to replace the return code. The Select a Job dialog opens. Altiris® Deployment Solution 6. which is success by default. you get an error when running the job. 8.8 SP2 195 . These modifications let you add parameters to the job. This is helpful if you want to use the return code again. In the Success list box. jobs are automatically imported from the samples. Click OK.

the image you deploy must include automation pre-boot environment so that post imaging tasks can run successfully. Each configuration set is presented to the user as a menu. The Properties of Initial Deployment dialog appears. and the computer import feature.from 10 to 100 computers .or mass deployments -. you can also configure a boot disk to run Initial Deployment. we recommend that you copy and rename modified sample jobs to avoid overwriting by new sample jobs. and personality settings for their specific needs and environment. Initial Deployment lets you define how computers are initially set up after being identified by the Deployment Server. We do not recommend this feature for large deployments -. New computers appear in the New Computers group in the Computers pane of the Deployment Console. double-click Initial Deployment from the Jobs pane or right-click Initial Deployment and click Properties. letting the user select the computer settings and hard disk images. In this case. Note To completely deploy and configure a computer using Initial Deployment. You can define various computer configuration sets and deployment jobs for the user during startup. The Altiris® Deployment Solution 6. you must define at least one Configuration and one Job. Although Initial Deployment is commonly used on computers that support PXE.from 100 to 5000 computers.8 SP2 196 . customized jobs. To access Initial Deployment. Installing an Automation Partition on the client computer’s hard disk ensures that future imaging deployment jobs run successfully. We also do not recommend this feature where you use virtual computers. Initial Deployment consists of a dialog with three tabs with separate features to deploy new computers: Configurations Jobs Advanced Configurations Click the Configurations tab on the Initial Deployment dialog to configure different sets of computer properties. from 1 to 10 computers. Initial Deployment Initial Deployment is a default job designed to help in the process of setting up computers that do not exist in the Deployment Database.Note When upgrading versions of Deployment Solution. software. Notes Initial Deployment is ideal for small-scale deployments.

Enter values to set computer and network properties for new computers. Compare the Jobs tab with the Configurations tab. Double-click Initial Deployment in the Jobs pane drop-down list. The user can select the deployment jobs to image the computer and install applications and personality settings. 3. After setting the properties. The conditions on jobs are limited to the data that can be accessed at the DOS level (Example: serial number. or click the Jobs tab to define a task. See Modifying Configuration (page 182) for a list of property categories. Click the Default Menu choice drop-down list and choose a configuration set as the default configuration. depending on what is available. serial number or MAC address -. 4. NIC information. Double-click Initial Deployment in the Jobs pane drop-down list. Select Process this job in batch mode. 7. Advanced Configuration Click Advanced on the Configurations tab to open the Advanced Configuration dialog. 6. the deployment process automatically sets TCP/IP information to use DHCP and names the computer to match the computer’s asset tag. which runs for all clients at the specified time. This dialog lets you set advanced configuration settings for client computers and provides different options for processing jobs for client computers. You can add multiple configuration sets for the user to select from a menu after connecting to Deployment Server. click Apply. Click the Timeout after ___ seconds and proceed check box to specify that the default job runs automatically after a specified time. manufacturing number. Click Add. Click OK. Select Process this job as each client becomes active. Select Hold all clients until this time. The Initial Deployment dialog appears. This job is processed for a batch of clients after specifying Minimum clients and the Timeout in minutes.user can select the configuration set designed for their environment. This job is processed only when clients become active. 1. Click Add again to configure another set of property settings.8 SP2 197 . Jobs Click the Jobs tab on the Initial Deployment dialog to add existing jobs or create new jobs to run on the new computer. Altiris® Deployment Solution 6. 5. Note If you do not create any configuration sets. Click the Configurations tab. Compare the Configuration tab with the Jobs tab. The Properties of Initial Deployment dialog appears. manufacturing name). 2. You can specify the Start time for this job. Click OK. The jobs you add or build using this dialog are listed in a menu and presented to the user during startup.in that order. 1. 8.

The default setting is 60 seconds. laptop. 7. 4. Click the Jobs tab. such as desktop. such as Web and network servers identified by Deployment Server. Identifying a computer as a server by the operating system cannot be accomplished for new computers until the server operating system has been installed. and handheld computers to stop before automatically running Initial Deployment. Click the Default menu choice drop-down list to select the job as a default.8 SP2 198 . See Building New Jobs (page 152). Example: both an HP Proliant and a Dell computer with multiple processors are identified as servers. Click OK. 5. This avoids accidental re-imaging or overwriting of data and applications for either workstations. When a computer not yet identified by the Deployment Database is first detected. Click New to build a new job. Altiris® Deployment Solution 6. However. Select Workstations/Clients to force desktop. 3.2. it is placed in the New Computers group and run an Initial Deployment configuration set and job. Advanced Click the Advanced tab to set options to stop Initial Deployment from running the default configuration task sets and jobs automatically. laptop. or click the Advanced tab to stop servers or workstations from running configuration task sets and jobs automatically. handheld computers. Select Timeout after ___ seconds and proceed and type the number of seconds to wait before the computer automatically starts the default job. or servers. See also Sample Jobs in Deployment Solution (page 195). Servers are identified as the managed computers running multiple processors or identified as a specific server model from specific manufacturers. Stops servers from automatically running Initial Deployment configuration jobs. in many cases you do not want Web or network servers to be automatically re-imaged without confirmation from IT personnel. Select Servers. Click Add Existing to add an existing job. 6.

8 SP2 199 .Part IV Best Practices This section provides details on many of the management tasks available in Altiris® Deployment Solution™ software. Altiris® Deployment Solution 6.

and securing communications. Explains the privileges needed to rollout the Deployment Agent. Part 1: Deployment Server Accounts To run the Deployment services. Altiris® Deployment Solution™ software requires access beyond the files and database owned by the application. This guide walks you through the phases of security planning. and settings within the Deployment Console. These security policies control administrator access to computers. Contains information on backing up authentication keys and enabling server redirection when using key-based authentication. including setting access rights. This minimizes security risks while still allowing Deployment Solution to manage computers. and mange the Deployment Share.8 SP2 200 . The broad range of tasks performed by Deployment Solution enables simplified management but also introduces a greater need for strong security policies. We recommend creating the following accounts: Account Service Description The main account used to run the Deployment services. Altiris® Deployment Solution 6. and connect to the Deployment Share in automation. Provides the information you need to secure and control database access.Chapter 12 Securing Deployment Solution To effectively manage computers. database security. Example: Deployment Solution requires rights to install software on managed computers and rights to join computers to a domain during configuration. Explains how to secure communication between your Deployment Server and Agent. join domains. This guide is divided into the following parts: Deployment Server Accounts Administrator Accounts and Role and Scopebased security Database Security Securing Communication Appendix A: Agent Installation Rights Appendix B: Managing Task Passwords Appendix C: Managing Key-based Authentication Contains instructions to set up the accounts you use to run Deployment Server services. and provide automation access to the Deployment Share. jobs. Explains how to manage the passwords associated with specific tasks. we recommend creating separate accounts with minimal privileges to perform each of these tasks. perform domain tasks. manage the database.

Altiris® Deployment Solution 6. If not. If your Deployment Database or Share is on a different computer than your Deployment Server. and Share are on the same computer. this can be changed using the Services applet.Account Domain Join Deployment Share Read/Write Description Used to join computers to a domain during configuration. This account requires the following rights: Rights Services Description This account executes the following services: Altiris Deployment Server Console Manager Altiris Deployment Server Data Manager Altiris Deployment Server DB Management Altiris eXpress Server Altiris PXE Manager If this account is provided during installation. create a domain-level account. This is the account provided when you install Deployment Solution: If your Deployment Database. create a local account or optionally use the local system account. these services are already configured with the proper credentials. These accounts should not be part of any group. Server. The following sections outline each Deployment Server account: Service Account (page 201) Domain Join Accounts (page 202) Deployment Share Read/Write Account (page 202) Service Account This account executes the Deployment Server software and manages the Deployment Database. and should not posses interactive login privileges. Provides access to the Deployment Share in the automation environment.8 SP2 201 . or create local accounts with the same credentials on each computer hosting a Deployment Solution component.

This account is used to access files in the automation environment. Provide the accounts you created: Deployment Share Read/Write Account This account provides read/write access to the Deployment Share. See Part 3: Database Security (page 205) for more information. After these accounts are created in Active Directory. To add domain join accounts 1.Rights File System Description This account requires full control of your Deployment Share. click Tools > Options > Domain Accounts. This account requires the db_owner role on your Deployment Database. and optionally in some tasks if it is more Altiris® Deployment Solution 6. In the Deployment Console. Database Domain Join Accounts These accounts provide the privileges required to join computers to a domain during configuration. You need a separate account for each domain in which you manage computers. and does not require administrative privileges on the computer hosting your Deployment Share.8 SP2 202 . Grant the rights recommended in the following table: Rights Domain Description Grant privileges to add computer to domain. 2. complete the following procedure to add them using the Deployment Console.

have interactive login. This account is provided when creating boot configuration using Boot Disk Creator: Part 2: Deployment Administrator Accounts Deployment administrators are the people who perform day-to-day work in Deployment Solution.efficient to access the Deployment Share directly rather than accessing it through the Deployment Server. adding and removing accounts from these groups as necessary. We recommend creating groups in Active Directory to manage these rights. Note Each Deployment administrator needs to be granted public access to your Deployment Database. See Rights Required for Deployment Administrators (page 207). These accounts are tied to people. Grant the rights recommended in the following table: Rights File System Description Grant read/write privileges to your Deployment Share. and usually have additional rights across your network. Role and Scope Based Security Role and Scope-based security controls who has access to what in the Deployment Console. Altiris® Deployment Solution 6.8 SP2 203 . You should select a group of administrators to grant full administrator rights and determine how to grant rights and privileges to other administrators as necessary.

To enable security You must add at least one user or group to enable security.One major advantage of the Deployment Solution security model is that administrators do not need to be granted explicit rights on any managed computers. and computers. jobs. This works well in situations where you already have policies in place to control server access. Implementing a strong policy to manage the access granted to your Deployment administrators protects managed computers from unauthorized access. In the Deployment Console. If you want to provide more granular access to configuration options.8 SP2 204 . 1. and you have a group of administrators who will have full access to deployment functionality. The first user or group added is granted administrator rights. database connections. you restrict most rights to one or more main administrators. as this simplifies rights management. We recommend planning administrator. click Tools > Security. it does not allow him to log in to that computer and install software. Typically. Manage By Exception The Deployment Solution role and scope-based security model uses the concept of managing by exception. Deployment Console Security By default. domain accounts. and job groups so that all permission assignments can be made at the group level. These permissions are usually distributed across all administrators who perform work in Deployment Solution. Each additional user or group after the first are granted no rights and must be assigned rights explicitly. you make an assignment at a container level that applies to most of the members of the container and you manually add exceptions where needed. Security is automatically enabled after a user or group is added. All actions must go through the Deployment Console. Example: if you grant an administrator rights to install software on a managed computer in the Deployment Console. To manage permissions. All access is filtered through the integrated role-and-scope based security in the Deployment Console. Permissions Altiris® Deployment Solution 6. 3. 2. We recommend clicking AD Import and importing Active Directory groups. Controls access to jobs and managed computers. Rights and Permissions The Deployment Console separates privileges into two categories: Rights Provide access to console settings. and other options. Add a new user or group. computer. you can enable security. the Deployment Console can be used on your Deployment Server by any user who possesses rights to log in and run applications. Additional users or groups can be added using this same method.

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. Select a user or Group and click Rights. one group could be allowed a permission at a particular level while the other group is denied the same permission. 2. Permission Rules Permissions received through different sources may conflict with each other. file system ownership of a single folder (Deployment Share). Instead. In this scenario. and an intruder would need to compromise a higher level administrator account in order to access these credentials. or Job and select Permissions.Grant Rights to Administrators 1. the user is not allowed to run the job. This account should be secured by a central Deployment or domain administrator. 3. When a user is associated with multiple groups. and ownership of the Deployment Database. the object in question looks in the current location and up the tree for the first permission it can find and uses the same. 2. Select a user or group and enable or disable the permissions you want granted. In the Deployment Console. Enable the rights you want granted. Permissions do not flow down an object tree. Part 3: Database Security Securing your Deployment Database is tied directly to securing the account you use to connect to the database. click Tools > Security.8 SP2 205 . User permissions take precedence over Group permissions. No additional Deployment administrators need this password. Computer Group. Deny overrides Allow. you can greatly reduce the risk of your database being compromised. The password is provided to run the Deployment Solution services and is stored securely. Right click a Computer. Grant Permissions to Administrators 1. Deployment Server requires only one account to have non-public access to the database (the Service Account (page 201)). If a console user does not have permissions to run all tasks the job contains. Example Your domain or central Deployment administrator creates a new domain-level account with no interactive login. If you follow this process outlined in this document to create accounts and separate privileges. Altiris® Deployment Solution 6. the permission to deny the privilege is enforced.

Select the Administrator account you are using to install Deployment Solution.8 SP2 206 . These rights can be revoked after the installation completes. add it. Click the Server Roles tab. Click OK and verify that the role was added. Altiris® Deployment Solution 6. and covers: Rights Required to Install (page 206) Rights Required for the Services Account (page 207) Rights Required for Deployment Administrators (page 207) Rights Required to Install To create the Deployment Database during the Deployment Solution installation. Browse to Security > Logins: 3. If it does not exist. 2. and enable System Administrators: 5. you need to grant the System Administrators database role to the administrator installing Deployment Solution. Open Enterprise Manager and connect to your SQL Server. 4.Required Database Rights This section contains a list of the database rights that need to be granted to use Deployment Solution. 1.

Click OK and verify that the change was successful.Rights Required for the Services Account The account used to run your Deployment Services needs to have database owner rights: 1. Double-click the account you are using to run the Deployment services. 4. Click the Database Access tab. and enable the db_owner role: 5. Altiris® Deployment Solution 6.8 SP2 207 . Browse to Security > Logins: 3. Open Enterprise Manager and connect to your SQL Server. Rights Required for Deployment Administrators Each Administrator with console access must be granted public rights to your Deployment Database. The best way to do this is by assigning public access to the Active Directory groups containing your Deployment administrators. 2. If the login is not listed. add it. select the eXpress database.

1. grant the public role for the eXpress database: Part 4: Securing Communication This section contains guidelines to secure Deployment Solution communication between the Deployment Server and Deployment Agent. on the Database Access tab. After you enable this option. Open Enterprise Manager and connect to your SQL Server. Key-based authentication prevents agents from connection to un-trusted Deployment Servers if hostname resolution is somehow compromised.8 SP2 208 . 4. For each user or group. 3. This key is located on your Deployment Share.This prevents you from manually granting this access to individual administrators as they are added or removed from Deployment management responsibilities. Altiris® Deployment Solution 6. After enabling this option the Agent connects only to the trusted Deployment Server. Key Authentication Key authentication is enabled on the Server Connection agent configuration page.key file containing the server public key for your trusted Deployment Server. and discusses the following: Deployment Agent Authentication (page 208) Additional Agent Security (page 210) Keyboard Locks in Automation (page 210) Deployment Agent Authentication We recommend providing a Deployment Server hostname rather than using multicast. you are prompted to provide the server. and implementing key-based authentication if additional security is needed. 2. Add each user or group that will manage computers using Deployment Solution. Browse to Security > Logins.

key file on your Deployment Share: Altiris® Deployment Solution 6. Select to Enable key based authentication to Deployment Server and provide the path to your server. 3. right-click a computer or group and select Change Agent Settings > Production Agent. 2. In the Deployment Console. Select Connect directly to this Deployment Server and provide the hostname.8 SP2 209 .To enable server connection security 1.

this risk is greatly reduced as the account you are using has only read/write access to the Deployment Share. including the ability to encrypt communication and password protecting admin settings on the managed computer: Keyboard Locks in Automation Lock the keyboard whenever possible in automation. However. if you are using an account with broad network privileges this could potentially introduce a large security risk. Altiris® Deployment Solution 6.Additional Agent Security The Security tab on the Agent Settings screen provides additional security options.8 SP2 210 . If you set up your account according to the instructions in this document. This prevents the session from being broken manually on the managed computer.

To lock the keyboard. enable the lock option when creating boot configurations in Boot Disk Creator: Appendix A: Remote Agent Installer Rights To initially install the agent on managed computers using the Remote Agent Installer. Provide the username and old and new passwords for the administrator who executed the task. Appendix B: Managing Task Passwords When a task executes. it remembers information about the administrator who executed it as part of the history. You only need access to this account when performing the one-time agent installation. click Tools > Options. you no longer need access to this account. Select the Task Password Tab. or any other account with local rights. so either use your domain administrator. these credentials are used. browse to: \hostname\admin$ Replacing hostname with the name of the computer where you want to install the Deployment Agent. Altiris® Deployment Solution 6. Next time the job executes.8 SP2 211 . To determine whether you have sufficient rights. In the Deployment Console. a domain account with local user rights. 3. you need an account with Local User rights. 2. you need to update the jobs for a specific account: 1. If you can access this share you have sufficient rights. After the agent is deployed. If the password for the account used to execute the job changes.

Backing up the Server Private Key During installation. The public key is located on your Deployment Share and should be backed up as well.8 SP2 212 . 1. select Options > Authentication. Altiris® Deployment Solution 6. Copy the public key file from each additional Deployment Server and use the Add Key to add each server to the list.4. Enabling Key-based Authentication with Redirection If your Deployment Server is set up to redirect Agents to another Deployment Server. This appendix contains information on backing up your authentication keys and enabling redirection to another Deployment Server. Appendix C: Managing Key-Based Agent Authentication Key authentication is configured and ready to be enabled after installation. Click Update.key file. each agent using key authentication needs to be updated to use the newly generated server. you need to import the server. If you re-install without this key. In the Deployment Configuration tool.key from each additional Deployment Server to the server which clients initially connect. a private key is generated on the Deployment Server and stored in the registry at the following location: HKLM\Software\Altiris\Altiris eXpress\Options\Security\ServerSecurity This security key should be backed up to a secure location in case this Deployment Server needs to be re-installed. 2.

8 SP2 213 . Deployment Solution uses an integrated technology called Altiris PC Transplant. A complete guide to PC transplant can be viewed by launching the PC Transplant Editor (Deployment Console > Tools > PC Transplant Editor). Altiris® Deployment Solution 6.Chapter 13 Migrating Application Data and User Settings To perform migration.

the image is stored as %COMPNAME%. Other File Formats. or one or more of the partitions on the hard drive. The source disk or partition is not changed. So. an image of an 80 GB hard drive only requires as much space as the data on the disk. These formats are not resizable. and EXT3. understands the Windows file system and captures just the data. FAT. including tools to perform hardware independent imaging using sysprep. This file can be used to restore the structure and contents of the imaged hard drive. the disk is read sector by sector regardless of which sectors are in use. Tokens Database tokens are used throughout the imaging process. Altiris® Deployment Solution 6. the imaging engine used by Deployment Solution. How Imaging Works 1. For other file systems. and the image description contains the name of the operating system. Computer boots to automation. File Systems RapiDeploy.Chapter 14 Capturing and Deploying Disk Images What is a Disk Image? A disk image is a file containing the complete contents and structure of a hard drive. The rapideploy executable creates the disk image and transfers it to a remote location or reads the disk image and restores the target partition or hard drive. RapiDeploy copies real data file by file.8 SP2 214 . When you schedule an imaging job using the sample imaging job (Jobs > Samples > Imaging > Create Disk Image). Imaging in Deployment Solution Deployment Solution provides several tools to simplify the imaging process. 2. The image mirrors the contents of the disk. EXT2. resulting in a clean. NTFS.img. defragmented image that can be resized and restored to a disk of a different size. Imaging is file-based. File Systems Hard disks are imaged differently depending on the file system that is used.

8 SP2 215 .Partitions When you create an image. a Client PC with a 200 Gigabyte disk will use the same percentages. you can specify which partitions to download and which to ignore. the following files are created: basepc. Spanning Media The maximum size for a single image file is 2 GB. the partition size percentage of the Client PCs will.img. To keep an existing partition. If there are multiple partitions. By default. the following partition types will not be overwritten: Automation partitions OEM system partitions The default behavior can be overridden. Partition slots on the target computer will be.002 basepc. The default setting is to restore all partitions. a group of partitions. the same as the image source PC. or an entire hard disk. When a computer receives an image. by default. you can image a partition. Altiris® Deployment Solution 6.img basepc. be the same as the image source. and the image is split into four files.004 You can set the split image file size to be between 1-2040 MB. Partition Size When you are restoring an image to a computer. The size of the Windows XP partition will be 80 GB and the data partition will be 120 GB. Example: If you image a 100 GB hard disk where 40% (40 GB) of the disk is a Windows XP partition and 60% (60 GB) is a data partition. the destination hard disk may be a different size than the disk imaged. RapiDeploy also offers a partition resize feature that allows you to manually resize the partitions to a size you specify. by default.003 basepc. you can select which partitions to download. Images which exceed this amount are automatically split into multiple files. Any partition on a hard disk can be imaged. A partition occupying slot 3 in the image file will be by default in slot 3 on the target computer. which would overwrite any existing partitions. Example: If you named your image file basepc. You can also use command-line switches to keep existing partitions.

Post-Imaging Configuration Because images contain a generic operating system. This is non-typical interaction. consult your documentation for information on enabling keep alives and uploads. networking. You might also need to specify a file type of application/octet-stream for your images to prevent errors. The Master PC can multicast images to Client PCs in the following three ways: While the Master PC downloads an image from a file server and manages the simultaneous imaging of the Client PCs While the Master PC creates an image on a file server and manages the simultaneous imaging of the Client PCs While using its own hard disk as the source and sending the contents to Client PCs HTTP Imaging When capturing or deploying an image. If a single computer fails. Upload access if you want to upload images In Apache 2. it will drop out of the session and the session will continue. In IIS. Windows digest authentication is not supported. Capturing Images See Creating a Disk Image on page 158. The multicast transmission is synchronized by the Master PC.8 SP2 216 . You also need to obtain and install mod_put module to enable image uploading. TCP/IP. Altiris® Deployment Solution 6.conf file. and user account settings on each computer that receives an image. Your Web server needs the following: Unlimited keep alives enabled. Basic authentication is supported. enable unlimited MaxKeepAliveRequests in your httpd. Deploying Images Distributing a Disk Image on page 163. This section briefly describes the options that are available in the Post-Imaging Configuration wizard page. and requires some configuration on your Web server. you will probably want to set up unique configurations such as operating system license. you have the option of providing a URL as the path to an image file.Multicasting How Multicasting Works The Master PC manages the multicast session. so it will only go as fast as the slowest computer in the group.

you must ensure that the Deployment Agent is installed on the computer you will create the image from. the Deployment Agent applies the configurations you set.8 SP2 217 . For more information. and reboots the computer so the changes take effect.Important To use this feature. Managing Images You can view and make changes to RapiDeploy image files (*. Altiris® Deployment Solution 6.img) using the Altiris ImageExplorer. see Altiris® ImageExplorer on page 313. After a computer has received an image.

This is available as part of the Business Desktop Deployment (BDD) Workbench. The default capture mode is fast.Chapter 15 ImageX Imaging Deployment Solution provides native support for imaging computers using ImageX.8 SP2 218 . Windows Vista and Windows XP are currently supported. the following restrictions apply: Only the C drive is imaged. After copying. customize the ImageX Imaging sample jobs for your environment. See the release notes for additional information. the computer might be left in an unusable state. the WAIK directory will contain a Tools subdirectory. Altiris® Deployment Solution 6. the following restrictions apply: The target disk is formatted before the image is deployed. After installation. Capturing and Distributing ImageX Images As ImageX is a 3rd party tool. WinPE must be used in automation for for all ImageX jobs. copy the following directory: C:\Program Files\Windows AIK\Tools to the WAIK directory on your Deployment Share. you must download and install the Microsoft Windows Automated Installation (WAIK) toolkit. When using the Distribute Disk Image task. limited support is provided in the imaging wizard. If there is a problem with the deployed image. To access the full functionality of ImageX. Obtaining and Installing ImageX Before using ImageX. When using the Create Disk Image task.

Use of OS X is subject to the Apple license agreements. A separate image is required for PowerPC and Intel-based computers. 3. One or more AppleTalk Filing Protocol (AFP) shares to host disk images.4 to provide the source for the automation image. see your operating system documentation for information. Deployment Solution can capture and deploy images to most Mac computers.Mac Imaging Deployment Solution supports native imaging of Mac PowerPC and Intel-based computers. Creating an Automation Image The automation operating system is a basic OS X image with the Deployment Agent installed. Instructions for creating this image are contained in Creating an Automation Image (page 219). Enable NetBoot.8 SP2 219 . Create an automation image. The computer then receives any automation jobs assigned. 2. OS X Server. the Mac agent in the production operating system shuts the computer down and instructs it to restart and contact your NetBoot server. To create an automation image. When the NetBoot server is contacted. complete the following procedures: Step 1: Configure a Source Computer (page 219) Step 4: Image the Source Computer (page 221) Step 1: Configure a Source Computer In this step. and then the Deployment Agent inside this image starts and contacts your Deployment Server. When an imaging job is assigned to a Mac computer. Requirements: A Mac computer running OS 10. This is an OS X Server feature that enables network booting similar to PXE Server. Altiris® Deployment Solution 6. This image is a standard OS X operating system with the Deployment Agent installed and configured for automation. the automation image is loaded. Intel-based Macintosh computers are not currently supported. Add your automation image as the default NetBoot image. Using an OS X Server to provide the boot image. Process Overview The following provides a basic overview of the Mac imaging configuration process: 1. Instructions for enabling NetBoot to provide the boot image are contained in Configuring NetBoot (page 221). a basic OS X system is prepared to provide the source for your automation boot image. Mac PowerPCs.

From the source computer you are configuring. open /etc/altiris/deployment/agentinstall.html. 3. Continue to Step 2: Provide Root Password for Automation (page 220). 5.2 is installed by browsing to /System/Library/ CoreServices/RemoteManagement.com/support/downloads/appleremotedesktop22client. Disable the Sleep option (System Preferences > Energy Saver). Re-install the Deployment Agent.) Complete the following procedure to store the credentials required to access these servers. Install the Altiris Agent. (see Configuring AppleTalk Filing Protocol Shares to Host Disk Images (page 222). 3. After the installation completes.x. Step 2: Provide Root Password for Automation 1. Configure a computer with OS 10. Continue to Step 3: Provide Credentials to Access Images (page 220).3. replacing domain with the domain containing your Deployment Server.1. providing the password for the Administrator account you created during installation. From the source computer you are configuring. Optionally. connect to the Deployment Share using Finder > Go > Network > domain > Express. For instructions see Installing The Mac Deployment Agent (page 260). Extract and run the program contained in AutomationImageEssentials. Verify Apple Remote Desktop 2. you can create an additional volume on an existing computer to store this operating system. Change the following: 6. and then log in using the Administrator account you created during installation. export OS_TOOLBOX=darwin To: export OS_TOOLBOX=automation 8. Disable software updates (System Preferences > Software Update). 7. download and install from apple. Credentials can also be provided directly in imaging tasks. Step 3: Provide Credentials to Access Images Images are retrieved and stored on AFP Servers. 2. Change any settings that might require user interaction. 2. 1. For example: Enable automatic login (System Preferences > Accounts).conf in a text editor. Browse to the techsup/macintosh folder. connect to the Deployment Share using Finder > Go > Network > domain > Express. In network options select Using DHCP. Altiris® Deployment Solution 6. 4. 2. Start the operating system you installed in the previous step.8 SP2 220 . replacing domain with the domain containing your Deployment Server. If this folder is not present. Browse to the techsup/macintosh folder.

Connect to your NetBoot Server and mount a NetBoot share. Provide Automation as the image name. you can delete SystemRO. Extract and run the program contained in AddCredentialstoKeyChain.dmg 3. Convert the existing read-only image to read-write using the following command: hdiutil convert /Volumes/NetBootSP0/SystemRO.3) or System (OS 10.dmg -format UDRW o /Volumes/NetBootSP0/System. Provide an image ID. 4. Step 4: Image the Source Computer 1. to capture and store an image of this computer. hdiutil. run the following command to capture and store the disk image: hdiutil create -srcfolder / /Volumes/NetBootSP0/SystemRO.dmg 4. This computer is ready to be imaged. (If using a different share.3. Example: 1300 Altiris® Deployment Solution 6.dmg Replacing newsize with the current size of your image plus 1 GB.4) Image Utility). typically NetBootSP0. password.dmg When this operation completes. Connect (command + K) using a command similar to the following: afp:\server_ip\NetBootSP0 Replacing server_ip with the IP address of your server. 2. Add an additional 1 GB padding to the image using the following command: hdiutil resize -size newsize /Volumes/NetBootSP0/System.dmg to mount the captured image as a volume. Run the System Image utility (Applications > Server > Network (OS 10. From the terminal on the source computer. In the upper pane. and hostname for each AFP share hosting images. providing the username. double-click /Volumes/NetBootSP0/System.8 SP2 221 . 5. On your NetBoot server. 2. select New Boot. replace NetBootSP0 with the share you are using in these instructions). we use the imaging utility. In Step 4: Image the Source Computer (page 221). Configuring NetBoot NetBoot provides Mac computers with the automation operating system. 3. To configure NetBoot complete the following procedures: Step 1: Configure the NetBoot Image (page 221) Step 2: Start the NetBoot Service (page 222) Step 1: Configure the NetBoot Image 1. You are now ready to configure NetBoot.

7. 3.mkext NBImageInfo. Configuring AppleTalk Filing Protocol Shares to Host Disk Images Images captured and deployed to Mac computers must be stored on an AppleTalk Filing Protocol (AFP) share.3 only) mach.nbi containing the following: System. If that location is unavailable. On the Images tab. save the folder to a different location and then copy it to the correct location after the operation completes. Start the AFP service (if not already started). 6. Running the service but not enabling any adapters prevents your NetBoot server from responding to DHCP requests on your network.6. 9. Leave the default NFS option selected. 4. Click Create. It is not necessary to click enable. Select it as default. Altiris® Deployment Solution 6. Step 2: Start the NetBoot Service 1. Provide Automation as the folder name and save it to the /Library/netboot/ NeBootSP0 folder. select the Automation image and: Enable the image.macosx (10. open the Server Admin utility. On your OS X Server.8 SP2 222 . Select the NetBoot service. Continue to the next section to configure network shares to host disk images. select the volume containing your images. select disk image.plist You are now ready to start the NetBoot service. On the Contents tab. 5. 7. NetBoot is now configured. Follow the instructions provided with your OS X Server to create AFP shares to host images. but allows your NetBoot server to provide IP address when booting clients. Start the DHCP service.dmg booter mach. 8. On the General tab. Your NetBoot server should now have a folder at /Library/netboot/NetBootSP0/ Automation. Expand the services on the localhost. then browse to the image file volume you mounted in step 1. 2.macosx. Enable the diskless option.

contains settings you can change to customize the behavior of Ghost.exe imaging executable to enable this support.ini.ini. You must provide a copy of the ghost.exe (for DOS support) and/or ghost32.MODE=create. located in the root of your Deployment Share.Chapter 16 Symantec® Ghost® Imaging Important Deployment Solution does not include the Ghost executable or a license to use Symantec Ghost. Copy ghost.exe and/or ghost32. On the Deployment Share. Customers currently using Ghost imaging solutions have the option of copying the Ghost executable to the Deployment Server to enable Ghost imaging from the Create Disk Image and Distribute Disk Image tasks.8 SP2 223 . create a folder called ghost. For example. To add support for Symantec Ghost 1. A configuration file called ImageTools.SRC=1. the default command-line in DOS is: CreateImageCommandLine=clone.DST=%IMAGE_FILENAME% -sure This setting and others can be customized by modifying ImageTools.exe (for WinPE support) to this folder. Altiris® Deployment Solution 6. Symantec Ghost is now available for selection in the Create Disk Image and Distribute Disk Image tasks.

8 SP2 224 . all the way up to a pre-configured. bundles these changes into a Windows Installer package (. Any changes detected are added to an installation package. and Wise MSI Editor. To repackage software. you use Wise SetupCapture to create a snapshot of the files and settings on a computer execute an existing installation. flexible software installation packages. or include a large number of programs in your standard images which can require frequent updates. Information for users migrating from RapidInstall to the Wise tools is provided as well. Changing the source paths in the installation to UNC paths. Other reasons you might want to repackage include: Supporting corporate standards by customizing the way applications are installed. Overview of the Software Packaging Process The software packaging process uses the tools that compromise the Wise Packager: Wise SetupCapture. These situations can require you to manually install and configure software. You can use Wise MSI Editor to customize the installation. The Wise Packager repackages and customizes your existing installations to create consistent. Creating transforms for the repackaged installations. These packages use the Windows Installer format (MSI). a software package you require does not provide options for remote or automated installation. Wise MSI Editor lets you customize and create MSI installation programs. Altiris® Deployment Solution 6. and might require additional configuration after installation. which provides many benefits over traditional installations. including a walk-through of the software capture and distribution process. silent installation of a complete application. Building complex launch conditions using Windows Installer runtime properties that test aspects of the destination computer. These software packages can be as simple as a single file copy or a registry change. Why Use Software Packaging? Installing and managing software is a major part of successful computer management. SetupCapture records the changes made by the installation and compares these changes to the initial snapshot. Creating silent installations or limit the options available to end users.MSI). Wise SetupCapture records changes made to a computer by an installation program. Often. This article presents an overview of the Wise Packager.Chapter 17 Software Packaging Deployment Solution includes the robust Wise Packager for Altiris Deployment Solution. This format is explained in Appendix B: Windows Installer Format Explained (page 226).

and applications that make API calls (such as antivirus software) can be very difficult to repackage. are simple to repackage. The capture process is not resource intensive. continue to the next section. This helps prevent situations where the necessary changes are not captured due to pre-existing software or other conflicts. Installations already using the MSI format should not be repackaged because remote installation and other advanced features are already supported. Adding and removing files. registry settings. Making modifications to Altiris® Deployment Solution 6. Installations that perform simple file copies and registry changes. The easiest way is to first install AClient and use the Create Wise Packager Shortcuts sample job to add shortcuts to execute the software from the Deployment Share. Client/server applications. or create the shortcut manually (use the sample job as a starting point). we recommend setting up a computer with just the basic operating system and no additional software. certain programs are better candidates for repackaging than others. many of these applications already provide their own tools for automated and remote installations. you need to provide the reference computer access to Wise Setup Capture. it can be executed directly from the Deployment Share. Accessing Wise SetupCapture After the operating system is installed. Setting up a Reference Computer To host the capture process.The following sections provide additional details on this process: Step Setting up a Reference Computer (page 225) Capturing a Software Package (page 225) Customizing a Software Package (page 226) Distributing a Software Package (page 226) Description This computer hosts the capture process. This tool does not need to be installed.) You could also copy the Wise Packager folder from your Deployment Share to the reference computer. Capturing a Software Package (page 225). After you have a way to execute Wise Setup Capture on the reference computer. and other installation options.8 SP2 225 . Adobe Reader. (Shortcuts are placed at Start > All Programs > Altiris > Deployment Solution. Capturing a Software Package What Can I Capture? Depending on the complexity of the installation. in fact. so any recent desktop computer should work fine as the reference computer. additional customization is often required. Getting your package to the right managed computers. Using Wise Setup Capture to capture changes to the reference computer. and others. such as WinZip. Fortunately. As the complexity of the installation increases.

Microsoft developed the Windows Installer service. Copy the installation programs you want to repackage to the reference computer or to an accessible share and launch Wise SetupCapture.chm help file on your Deployment Share.) After providing a name. use the powerful automation tools provided by Deployment Solution or Software Delivery Solution to distribute this package to managed computers. Hardware drivers. Distributing a Software Package After you have created a software package.8 SP2 226 . It consists of the following: Altiris® Deployment Solution 6. The Capture Process Before you begin. Start > All Programs > Altiris > Deployment Solution > Wise MSI Editor. Customizing a Software Package (page 226). review the guidelines in Appendix C: SetupCapture Guidelines (page 229). capturing changes. (If you added shortcuts. The default options should work fine.exe migration utility. Appendix A: Migrating From RapidInstall We recommend migrating from RapidInstall to the Wise Packager to leverage the benefits of the MSI format. Appendix B: Windows Installer Format Explained To create a streamlined process for installing and managing applications. automatic uninstall and rollback. operating systems and updates should not be captured. you should review and update the properties on the Installation Expert pages.) Complete details on using Wise MSI Editor are in the Wise Packager\Help\WisePackager. review the captured changes and add stand-alone files and registry settings in the next section. and completing the process. (If you added shortcuts. Start > All Programs > Altiris > Deployment Solution > Wise SetupCapture. Customizing a Software Package Open the Wise MSI Editor and open the MSI you captured. Ensure you run it on the reference computer. including self-healing.vendor-supplied MSIs is not recommended since it could introduce incompatibilities with future updates. To convert existing RIP packages to MSI format. This utility is in the RInstall folder on your Deployment Share. though if you want to capture file and registry deletions you need to select these options. At a minimum. use the RiptoMSI.chm help file on your Deployment Share. After this process completes. due to their complexity and Windows File Protection. Complete details on these options are in the Wise Packager\Help\WisePackager. The remaining on-screen prompts guide you through performing an initial scan. not the server. select options for this capture.

and Registry. Files. The .MSI. If the installation fails.exe) reads the installation database (. Logic built into the Windows Installer engine prompts for a reboot. Instead of an installation executable (such as setup. The database stores the application’s program files and setup instructions and can readily access this information if the application requires maintenance. A runtime service that makes application installation and management part of Windows services. Windows Installer implements a single built-in execution engine and replaces the installation executable with a database file (. it provides benefits that are unavailable in traditional installation technology. the Windows Installer executable (msiexec. Although many software manufacturers used common installation tools like Wise Installation System. and follows file-version-replacement rules. and the operating system had to contend with redundant code in different applications. Windows Installer is not a installation authoring tool.A set of guidelines. uniform data tables. Using Windows Installer results in a solid. checks disk space. so individual files are restored to repair damaged applications.exe reads the database and builds a transaction list that it follows to complete the installation. Altiris® Deployment Solution 6. Because Windows Installer is part of the operating system. There is 100% accountability of where each file installs and a thorough log of which files belong to which applications. Components. others used highly proprietary installation technologies. An Application Programming Interface (API).exe). Execution Sequence. When opening an . every software application had its own setup executable file (usually setup. Features.MSI).8 SP2 227 .exe or install. Applications could not be administered after installation. robust installation that reduces the total cost of ownership and enables compliance with the Microsoft rules for software installation. Windows Installer performs a rollback. This made the user’s experience inconsistent from one installation to the next.MSI uses highly structured. except to rerun the setup program.exe). msiexec. Each table contains different installation information such as Class. which returns the computer to its previous state. but rather an installation engine and rule set. Advantages of Windows Installer Before Windows Installer.MSI) which contains instructions and installation files. The Windows Installer engine resides on the destination computer as part of the operating system.

DLLs to prevent conflicts between applications. restricts data and commands. Msiexec. Lets you choose from a variety of authoring software and allows you to customize previously created installations. Assigns advertised or installed applications to a user’s profile so when the user logs in. Tracks which applications have installed every file and registry key on the computer on the component level. advertised features do not install but appear installed to the user. When an application starts. the application repairs missing components. Applications appear in the Add/Remove Programs applet and can be installed to the destination computer by the user. When the user selects an advertised feature. which gives you more control during installation. maintain. so the Windows Installer service always knows exactly what is needed for an application to run. Also called install-on-demand. and enforces rules when running the installation. the installation occurs.8 SP2 228 . Components group resources together so they move as a unit. If it detects any problems. and the modified date on a non-versioned file. version. When the installation fails. Windows Installer checks a list of key files and registry entries. Runs an installation using administrative rights. Publishing Rollback Advertisement Componentization Standardization Version Rules Reference Counting Customization Elevated Privileges Assignment Open Architecture Total Cost of Ownership Altiris® Deployment Solution 6. and what is no longer used during uninstall. This invokes the system’s security rights. Decides whether to install a file to a directory by looking at a file’s date. these applications appear on the destination computer. Windows Installer makes installations easier to install. language. and support. Applies rules to installed application files that look at a file’s version and its shared . Transforms customize an . Windows Installer repairs the application using a cached database that contains key paths to application components. This prevents having an incomplete or broken application.exe and the Windows Installer service approve the elevated privileges request. the installation reverts to the previously installed state.Windows Installer Benefits Self-healing Description With self-healing (also called automatic repair and selfrepair).MSI to a particular user group’s needs.

MSI-based installation. the changes are recorded as a file change. Do not run SetupCapture from the Deployment Solution Console.EXE components into features results in more efficient repairs.8 SP2 229 . Group Policy and Security User Policy System Policy Appendix C: SetupCapture Guidelines Run SetupCapture on a clean reference computer. To customize it for specific workgroups. Part of this process includes searching for the computer name and currently loggedon user name.INI file format. run it on a client computer.INI file follows standard . ensuring access even between different networks. Multiple possible locations for the MSI package are listed. Lets you set policies on a per-computer basis. To capture an uninstall. deleted items are located in the RemoveFile and RemoveRegistry tables in Setup Editor > Tables tab. To make the search for computer and user names as accurate as possible. Do not capture an . SetupCapture attempts to convert computer. Before you run SetupCapture.EXE that's installed that has a shortcut. An example of a unique user name is: repackage-1-user. Isolating . Otherwise. Altiris® Deployment Solution 6. only the problem component and the . It does this by searching for standard paths (example: C:\Winnt) and replacing them with Windows Installer properties (example: [WindowsFolder]). (Example: Norton AntiVirus.Windows Installer Benefits Dynamic Source List Description Provides sources for the MSI to repair from and enable advertising. create a transform. ensure the computer name and user name on the capture computer are set to unique names 4 or more characters in length.INI file are recorded as changes to an . exit all other applications. you must mark Include files deleted during capture and Include registry keys deleted during capture in SetupCapture Configuration General Settings. SetupCapture creates a separate feature for each . which lets you run an entire installation in elevated privileges and define only those rights users have while an installation runs. Sets privileges to control the user and application rights. In Wise MSI Editor. including background services or applications.and user-specific data in the registry to generic data that will work on any computer.MSI directly in Wise MSI Editor. Avoid having the user name or computer name set to any common file or folder names. Instead.EXE are reinstalled instead of the entire feature containing the problem component. because if there is a problem with a component. During a capture. and provides a more secure environment. SetupCapture does not monitor any internal logic within the installation and it does not replicate the user interface of the original installation.INI file only if the . open the .) During SetupCapture. Defines a user’s privileges. changes to an .

Registry keys that define an environment variable are converted to an environment variable in the repackaged installation.8 SP2 230 . Altiris® Deployment Solution 6.

you target it for the automation or production environment. Each step of this process is discussed in greater detail in this section: When creating a script. When a scripting task runs. DS provides an environment to pre-process. logevent. the server preprocesses the script for database tokens. Firm. batch files.8 SP2 231 . and shell scrips. These scripts have access to the full processing capability of the operating system command processor. Altiris® Deployment Solution 6. deliver. DS retrieves values based on the computer currently running the script. and other Altiris tools. and specify the operating system for the script. returns any error messages generated by the script.Chapter 18 Deploying Scripts Altiris Deployment Solution provides a number of pre-defined tasks you can combine to create complex management jobs. as well as several additional features provided by Deployment Server: Access to your eXpress share and any other network resources available in the production or automation environment. Intelligent access to values stored in your DS database. When you need to perform a management task that isn’t covered effectively by the predefined tasks. delivers and executes the script. so a single script can provide unique values for 1000’s of computers. The following diagram illustrates how scripts are processed by DS. and execute VBScripts.

Tokens are replaced. saving you from polling the computer and executing a database query before you can perform a task. These commands are processed before a script is deployed to a client. There are utilities and commands for each environment to perform a broad range of management tasks.Using the flexibility of tokens and the processing power of the command processor of your OS. WinPE. Database values specific to each computer can be retrieved using the same token in your script. unloading BootWorks. Writing a Script Scripts can be deployed to the DOS. When a script is processed. you can develop and deploy scripts ranging from a simple file search to a full system customization. or to the Windows or Linux production environment. The same %COMPNAME% token can provide a unique value for each computer that runs this script. the scripts you write vary greatly depending on the target environment and OS. and Linux automation environment. Server Scripting Commands DS provides several predefined commands you can use when deploying scripts. This chapter discusses how to effectively create and deploy scripts in your DS environment. One of the biggest advantages to deploying scripts using DS is that a script is processed independently for each computer. The core of each script you write uses the functionality provided by the command processor of your OS. and predefined server scripting commands. These additional keywords are discussed in the Server Scripting Commands section. The predefined server scripting commands are keywords defined for replacing tokens in other files. DS first parses each script for two things: tokens. ‘ [servercommand] Altiris® Deployment Solution 6. and a special deployment command for Blade servers. performing scripted installs. Unlike other tasks. additional action might be taken based on the commands found before the script is delivered to the target. REM REM [servercommand] # Linux shell scripts. Each of these scripting commands must be marked by the correct comment flag to prevent them from being processed by the OS: The following table contains the comment flags for each scripting environment: Comment Flags Flag Location Used Batch files. # [servercommand] ‘ Visual Basic scripts. running vbscripts.8 SP2 232 .

A server command is also provided to replace tokens in other files.inf .\temp\%COMPNAME%.txt PROD:\sysprep.The following table contains the predefined server scripting commands: Server Scripting Commands Command Description Unloads BootWorks to provide additional memory for complex scripts. Source represents the source file containing the tokens you want replace. ‘ vbscript Retrieving Database Values Using Tokens Any tokens contained in a script are replaced automatically. named machinename with the same extension as the original script. Example: to deploy a custom sysprep.inf file to several computers. If a redeployment is later executed on this computer. this file could be copied with the correct database values to the production drive of the computer. This command replaces tokens in additional files.8 SP2 233 .txt Firm Copy f:\temp\%COMPNAME%. The ‘ comment flag is always used with the vbscript server command when writing Visual Basic scripts to ensure that it is ignored by the VB processor. the entire script is executed as a vbscript (you cannot execute batch commands and vbs commands in the same script). A script to perform this task might look similar to the following: REM ReplaceTokens . Deployment Start vbscript Indicates that this script contains vbscript. 394k of free memory is required for the Windows scripted install to run. such as those used when configuring a computer. the server creates a temporary file in the \tmp folder.inf. BootWorks is unloaded automatically when you specify ScriptedInstall. the computer is restored from the deployment start mark in the history. BootWorks is automatically unloaded for scripted installs.inf When replacing tokens. Altiris® Deployment Solution 6. ReplaceTokens [source] [destination] ScriptedInstall Indicates that this script is launching a scripted install. and is a valuable tool for troubleshooting. BootWorks Unload BootWorks Unload ReplaceTokens Tokens are replaced automatically in your scripts.\temp\sysprep. and destination represents the output file after tokens are replaced. If this appears anywhere in your script. the ReplaceTokens command could be contained in a script to replace tokens in sysprep. this option places a note in the history to mark a starting point. This file contains a copy of the script with all token replacements made by the server. ScriptedInstall Deployment Start When using blade servers. called ReplaceTokens.

Example: consider the script we reviewed in the previous section: REM ReplaceTokens . when a script runs server-side. However. A similar process can be used to deploy configuration files to Linux computers. Running Scripts on the Server Scripts can optionally execute on the server on behalf of the client. This might be sufficient for a simple script. By default. the initial token replacement still contains the name of the computer targeted by the scripting task. This is valuable when you want to retrieve tokens specific to a number of computers. but the script can execute successfully on the server. the ReplaceTokens command works as expected and creates a unique system. If you have processor intensive commands. avoid commands that require interaction.txt Firm Copy f:\temp\%COMPNAME%. A task assigned to 500 computers causes any serverside scripts in the task to execute 500 times on the server. In DS. The first two commands might return errors.8 SP2 234 . the server processes the next command in this script: ReplaceTokens. when running scripts server-side.After replacing tokens in the script itself. not the client. Also. but scripts can often execute successfully yet still fail to perform the intended tasks.\temp\sysprep. so there is no way to provide even simple feedback in scripts that run server-side. Since the token replacement process already replaced the compname token. a scripting task returns a 0 for success. Additionally. because token replacement and other commands are based on the client assigned the job. and a 1 if the script fails to execute. This can relieve network traffic and prevent interruptions on managed computers. Reporting Errors One of the biggest challenges when running scripts is implementing effective error reporting and feedback. This is very important to understand. and take action based on this code. However.inf If we marked this script to execute on the server. every task has the ability to handle error codes returned from a job. The DS service does not have interaction with the desktop. Altiris® Deployment Solution 6. The script is delivered to the client. the command in the second line fails because the server looks for the paths specified by Firm on the server. the script is executed separately for each computer assigned to the task. and the Firm utility finds the correct file on the eXpress share to copy to the production drive. but if the final command is successful you receive a status of success. or perform the task during off-hours. the status reported on completion is the status of the final command in the script. you might want to set up an additional database containing common configuration values you can retrieve using tokens. as a large number of Linux configuration files are text-based.txt PROD:\sysprep. if you create a batch file with three commands.\temp\%COMPNAME%. containing values unique to that computer. you might want to avoid server-side execution to prevent disruptions on your server. If you perform Linux configuration often. not the server.inf file for each computer.inf .

LOGEVENT can be executed directly in your scripts. This utility lets you send error. 0 = Unknown.exe. for DOS. The Windows and Linux utilities return messages as soon as they are encountered. Any string enclosed in double quotes. either by providing it with an image. In the Windows production environment.To provide additional feedback when running scripts.exe IF ERRORLEVEL 2 GOTO TWO IF ERRORLEVEL 1 GOTO ONE GOTO END :TWO Altiris® Deployment Solution 6. called logevent.exe. DS does not automatically stop script processing when an error is encountered.Where # = 0-3. it is important to note that DS cannot stop script execution directly. warning.8 SP2 235 . requestNewHardware. Altiris provides an error logging utility. In order to use WLogevent. and job execution can be stopped based on the messages you return. and uses logevent to return the script status: @ECHO OFF REM Call requestNewHardware. Default = "User Defined" DOS/CMD Error Handling In the DOS automation environment. The following script uses GOTO commands to control how a script is processed based on the outcome of executed commands. Since this is the default directory in the automation environment. and informational messages back to your server from within scripts. a software deployment. or by simply copying the file directly before your script executes. 1 = Information. Default = 0 Additional indicator of type of message.exe. and is available on your eXpress share. you must provide that logic in your script. This fails and returns an error. DS delivers the script and returns the execution status. the logevent utility is called WLogevent. Default = "No Message" Name of the program that was executed. Windows. events are queued until the script completes and they are returned to the server. but the operating sytem handles the actual execution. Usage: LOGEVENT [-c:#] [-l:#] [-ss:Msg] [-n:Prog] Logevent Parameter [-c:#] [-l:#] [-ss:Msg] [-n:Prog] Description A ReturnCode between -32768 and +32767. When executing scripts. On DOS. 2 = Warning. you must make the executable available to the Windows client. and Linux. the logevent utility is called LOGEVENT.

use WLogevent.0. integrated method to handle errors.17.17.” GOTO END :ONE LOGEVENT -c:1 -l:1 -ss:”Error 1. "172. In these scripts." Set objWMIService = GetObject("winmgmts:\" & strComputer & "\root\cimv2") ErrNum = Err. 1. The following script contains an example of error handling in Visual Basic script: On Error Resume Next Set WSHShell = Wscript.0.exe -c:0 -l:1 -ss:""Changing DNS for NIC1""".IPAddress If objAddress = "%NIC1IPADDR%" Then ' Set up the array of DNS entries for the NIC arrDNSServers = Array("172.\WLogevent. DS executes the script using Visual Basic.CreateObject("Wscript.ExecQuery _ ("Select * From Win32_NetworkAdapterConfiguration Where IPEnabled = True") 'cycle through all of the nics For Each objNetCard in colNetCards ' if it is the nic we are looking for change the dns For Each objAddress in objNetCard.” :END Visual Basic Error Handling By including the 'vbscript server command in a script deployed to a Windows or DOS environment. Visual Basic has a powerful.SetDNSServerSearchOrder(arrDNSServers) WSHShell.Number If ErrNum = 0 Then Set colNetCards = objWMIService.exe to report script status to the server after you have used the built-in mechanisms to retrieve errors.8 SP2 236 .202".Run ".LOGEVENT -c:2 -l:3 -ss:”Bad command or file not found.201") objNetCard. true Altiris® Deployment Solution 6.shell") ' look on the local computer strComputer = ".

use logevent to report the status to the server after you have used the built-in mechanisms to retrieve errors.txt ERRVAL = $? if [ $ERRVAL -ne 0 ]. then logevent -c:$ERRVAL -l:3 -ss:“error executing grep" fi. true Err.8 SP2 237 . Similar to Visual Basic script. so any Linux computer with the agent installed has local access to logevent.Run ".exe -c:" & ErrNum & " -l:3 ss:""Error:" & _ Err.\WLogevent.End If Next Next Else WSHShell. Altiris® Deployment Solution 6.Description & """" . Linux provides a powerful method to track error values.Clear End If Linux Shell Error Handling The logevent command is provided in the Linux agent. 1. The following script contains an example of error handling on Linux: #!/bin/sh export PATH=$PATH:/opt/altiris/deployment/adlagent/bin grep foo foo. When running scripts on Linux.

limiting your ability to manage computers at these remote locations. Implementing an image distribution framework enables you to replicate your images to a local image store for use during imaging tasks.Chapter 19 Creating an Image Distribution Framework Why Use an Image Distribution Framework? In distributed networks. Altiris® Deployment Solution 6. managed computers at remote locations would be required to access image files often over several gigabytes over this LAN link. In Deployment Solution. reliablebut-slow WAN links: Typically. your ability to effectively manage computers is often limited by the speed of your network link to remote locations. This can cause centralized management to become a major bottleneck. even when multicasting. computer imaging can often require file transfers in excess of several gigabytes. It consists of a distributed network with several remote locations and subnets connected using routers over permanent.8 SP2 238 . The following diagram outlines a typical network topology that can benefit by implementing an image distribution framework.

are available on your Deployment share in the TechSup\DOS\getsrv folder. or alternately. and have computers at each location boot using a local PXE server with configuration specific to this location. Deployment Solution provides a set of tools to let computers automatically retrieve the correct image file locally. Each share hosting an image store should have the same name and folder structure. we recommend creating a domain-level account with read/write access to each share. Using this method. This lets you assign a job across multiple locations.lst. such as getsrv. All managed computers. This eliminates downloading an image over the WAN link before an imaging operation. In other words. a local account with the same username Altiris® Deployment Solution 6. regardless of location. you can map local file shares containing disk images. What if I Am Not Using PXE? If you are not using PXE. The location of each managed computer is determined automatically based on IP address using a custom utility. Important: If PXE is available. Complete the following tasks to implement an image distribution framework: Step One: Set Up Local Image Stores (page 239) Step Two: Replicate Images (page 240) Step Three: Configure the Server Lookup Utility (page 240) Step Four: Create a Boot Disk Creator Configuration (page 241) Step Five: Distribute an Image (page 242) Step One: Set Up Local Image Stores A local image store should be set up on a file share at each remote location. To control access to these shares. the same distribute image task can be used to image one or more computers regardless of location.PXE Redirection PXE solves this problem by enabling you to redirect a shared PXE configuration to a configuration on a local PXE server. connect to the local image store to retrieve images. Creating a Distribution Framework The following provides a basic outline of an image distribution framework: Each subnet has a file server to host a local image store. Tools The tools referenced in this document. we recommend using up PXE redirection instead of following the process outlined in this document. the path to your images must be identical with the exception of the server name. Using these tools is described in this document.8 SP2 239 . Within this configuration.bat and server.

0. a tool called getsrv.2.lst C:\tools\getsrv.0/255. from the Deployment Share to the automation drive.0/255. Getsrv. and most companies already have a process in place for replicating data between remote sites. server.168.lst c:\tools\server.lst /v SERVERNAME > call C:\tools\srvenv. To use this example in your environment. Altiris® Deployment Solution 6.lst. Create a Server Lookup File Each server in the lookup file consists of two entries: the IP address/subnet entry and the corresponding server name. since PXE uses a virtual boot floppy represented by A:.exe to populate the server name variable.0. interactive login privileges.168.SERVER1 192.0/255. This batch file calls getsrv.255.0.exe is called with these parameters set correctly.exe /s c:\tools\server.255. The IP address and subnet are separated by a slash ( / ). SERVER 2 192. This account should not possess group membership. If you are using PXE. Step Three: Configure the Server Lookup Utility To simplify the process of accessing images at remote locations. Create a Configuration Open getsrv.and password on each server. SERVER 3 Create entries in this file for each IP segment to which you might deploy images. place your server lookup file in a tools folder on your deployment share and name it server.255. This account is specified when creating the boot configuration in Boot Disk Creator. This modified file is added to your boot configuration in a later section. ensure the necessary image files have been replicated to the local image store.bat This example copies the server lookup file.16.0. or any additional rights. and the corresponding server name is separated by a comma (. There are a number of file replication solutions available.8 SP2 240 . change the drive references from C: to A:. Getsrv. and the username and password must be the same for each share.0. Before attempting an imaging job. Step Two: Replicate Images Before an image can be used.1.bat should look similar to the following: copy F:\server. it must be replicated to the image store file share at each location. For example: 172.255.bat in a text editor.255.bat c:\tools\srvenv.lst.).exe was developed to retrieve the IP address of each managed computer and compare it to a lookup file to find the local image store.

GetSRV. create a folder named Tools and copy the following files: getsrv. After the wizard completes. This configuration is used to boot managed computers to the automation environment for imaging.bat. This drive mapping should look similar to the following: \%SERVERNAME%\[share] Replace [share] with the share name of your local image stores. Environment variable containing the selected server. We recommend using SERVERNAME). create a new boot configuration using your selected automation boot method and environment.EXE Parameter Descriptions The following table contains descriptions of the getsrv. Altiris® Deployment Solution 6. Create a drive mapping for your image share. within the configuration.bat 4. This token is used when creating the boot configuration. and is set to SERVERNAME in these examples. This file is typically placed in the deployment share. 2. Managed computers must be able to resolve the name of the central Deployment Server. We also recommend adding the name and IP address of each server hosting an image store. In Boot Disk Creator. See Create a Server Lookup File (page 240). you need to create and modify a boot configuration. 1. using the %SERVERNAME% variable rather than an actual servername. 3. (The name of this environment variable is specified using the /v flag of getsrv. NetBIOS is used to resolve names. so we recommend adding your Deployment Server to the lmhosts file. If using DOS automation. /v [variablename] Step Four: Create a Boot Disk Creator Configuration After you have configured getsrv.exe parameters: Parameter /s [filename] Description File containing the list of servers hosting local image stores.exe.exe getsrv.8 SP2 241 .

Computers must boot this configuration when performing imaging tasks.bat is called to map drives in the automation environment. The server lookup file must be accessible.bat to add the following line after the first line of the file: call c:\tools\getsrv. Launch Boot Disk Creator. 2. and your images are located in the root folder of that share. the path is G:\imagename.bat Mapdrv. Use the standard deploy image task in the Deployment Console. 1. or copied to boot media.Modify Mapdrv.img. installed to an automation partition. This file is modified to call the getsrv. After this executes.bat net use [drive]: “\%SERVERNAME%\[share]” /yes Deploy the Boot Configuration This configuration is now ready to be deployed using PXE.bat The completed file should look similar to the following: net use F: “\[your_ds_servername]\eXpress” /yes call \tools\getsrv. 3. Expand the configuration you created in the previous section. Step Five: Distribute an Image You are now ready to test your configuration by deploying an image. keeping in mind the following: Images must be replicated before the task executes. Altiris® Deployment Solution 6.bat to call Getsrv. The path to the image file specified in the Deploy Image task should be based on the image store drive you mapped when creating your boot configuration. the server name variable is available to map the drive to your local image store. Modify mapdrv.8 SP2 242 . Example: if you selected G and mapped \%SERVERNAME%\ds_images.bat file you modified in a previous step.

Note Servers are recognized by their operating system (such as Windows 2000 Advanced Server. you can set up a system to quickly deploy new servers or automatically re-deploy servers that have failed. support for remote management cards. See Server Management Features on page 243. such as user logged on or Server Waiting. And because servers are mission-critical. Manage Servers from the Console. Set Server-specific options.Chapter 20 Deploying and Managing Servers Deployment Solution provides additional features to remotely install. See Server Deployment Options on page 244. Windows Server 2003. Features like rules-based deployment. Like all managed computer icons. deploy and manage network and web servers. Servers are identified in the Computer pane with distinctive server icons. The Deployment Server Console includes features specifically designed for deploying and managing servers. and quick server restoration from a deployment history give you new tools to manage all servers throughout your organization. Servers are essential to any organization and require special planning and management strategies. you can configure new server hardware. and specific vendor server models. but are essential in deploying servers. Deployment Server provides serverspecific features to automatically deploy new servers and maintain existing servers. or any Linux OS). From the Deployment Server Console. These features are supported for client and handheld computers as well. the icons change to identify the status and state of the computer. install operating systems and applications. such as enhanced task logging and history tracking features to let you recall administrative actions and quickly redeploy mission-critical servers.8 SP2 243 . multiple processors. Server Management Features Deployment Server provides various features for deploying and managing servers. and manage servers throughout their life cycle. Altiris® Deployment Solution 6.

Like other computer icons in the console. The Deployment consoles display icons to identify servers across the network. Halt the Initial Deployment of Servers When a server boots from the PXE server or from BootDisk (if the option is set). Indicates a server is disconnected from the console. See Scripted OS Install on page 168. Deployment Server also lets you view and debug each step in the deployment script. Enhanced scripting capabilities. Deployment Agents include an option to disable this feature (it is off by default). If you are using Initial Deployment to automatically re-image new servers or run installation scripts. Follow steps to create answer files and set up the operating system install files using a wizard. Support for multiple network adapter cards. you must change the default settings in the PXE Configuration Utility. 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. and track each job to provide a history of tasks for redeploying a server. Synchronized server date and time. Run Scripted Installs. These contrasting settings are based on polices 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. or (2) run automatically for every server not identified as a managed computer in the database. You can deploy multiple tasks per deployment job and boot to DOS multiple times when configuring and deploying a clean server. Execute scripted. if you want to ensure that the server waits before being deployed (or waits a set time before proceeding) to avoid erroneous redeployment. Indicates a server is in a waiting state.8 SP2 244 . Server Deployment Options Deployment Server includes features to automatically reconfigure and redeploy new servers. Because servers may require more than one network interface card. Deployment Server automatically sets the server’s date and time after installing or imaging (as part of the configuration process).Server icons. Deployment Server provides property pages to access and configure multiple network adapters remotely from the console. unattended installs across the network for both Microsoft Windows and Linux servers. you can (1) safeguard against mistaken disk overwrites. you need to set the options in the Advanced section of Initial Deployment. See TCP/IP Configuration Settings on page 107. Deployment Server recognizes it as a new computer and will attempt to configure the Altiris® Deployment Solution 6. In contrast.

The message will stay open until the user clicks OK on the message dialog. 1. It will wait until a boot option is selected from the client computer. 4. You can change the default setting in the PXE Configuration Utility to allow Initial Deployment to run automatically and not sit at the prompt. Managing Server Blades Deployment Solution allows you to manage high-density server blades with Rack/ Enclosure/Bay (R/E/B) hardware and properties. Following these steps will assure that the BootWorks message will not come up and things will move forward when a job is scheduled. To fix this delay: 1. 2. a message will appear stating that no BootWorks partition or PXE stamp is found. which delays executing the scheduled job as part of an automated redeployment process. Select Execute Immediately. Clear BootWorks Prompt for Remote Install When you run a deployment job on a computer where the Deployment Agent has been remotely installed. Select the BootWorks tab. or Bay level of the server cluster. Click OK. 2. Enclosure. In the lower section. 3. Click the Servers check box and click OK. 2. or you can manage each server blade directly from the logical view. 3.computer with Sample Jobs in Deployment Solution.8 SP2 245 . Select Change Default Settings. Click on Start > Programs > Altiris > PXE Services > PXE Configuration Utility. Initial Deployment will run automatically for every identified server. See Bay on page 126 for properties and rules to deploy Rack/Enclosure/Bay servers. Click the Advanced tab. Altiris® Deployment Solution 6. 6. Click Initial Deployment and select Properties. Click OK. Change PXE Options for Initial Deployment If installing a server using a PXE Server. 4. 1. Select Tools > Options. 3. Click Altiris BootWorks (Initial Deployment). select Never prompt me from the list. Initial Deployment includes a feature to prohibit servers from being deployed automatically. 5. Initial Deployment will not run for any computer identified in the console as a server.The Altiris Program Options dialog appears. the server will attempt to install but will not run automatically using default settings. Select the Agent Settings tab. Click Edit. From the Deployment Console you can deploy and manage these space-efficient server blades using the physical view to assign jobs to the Rack.

com/ servers/rdp). 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. including the Virtual Blade Server feature. the Create Virtual Bay feature will execute and Initial Deployment will not execute.Using Deployment Solution. Altiris® Deployment Solution 6. both Sample Jobs in Deployment Solution and Server Deployment Rules can be set up.hp. Managing New Server Blades Deployment Solution allows you to automatically deploy. the Bay object will be identified in the physical view). Initial Deployment set up: Clear the Servers check box in the Advanced dialog. 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. when both are set up. allowing you to replace any downed server and get it back on line quickly. data. both the Sample Jobs in Deployment Solution and Virtual Bays features can be set up to automatically run configuration tasks and deployment jobs. the Server Deployment Rules execute and Initial Deployment does not execute. The name of each Rack for an HP Server is displayed along with the assigned name for the Enclosure and Bay.8 SP2 246 . 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. and patches are applied to the new server from the history of jobs assigned to the previous server blade. To Create Virtual Bays: Set up Virtual Rack/Enclosure/Bays for Hewlett-Packard Rapid Deployment Pack installations of Deployment Solution. Altiris provides fail-safe features to ensure that no server is mistakenly overwritten and ensures that all disk images. Virtual Bays. Hewlett-Packard Server Blades Hewlett-Packard high-density blade servers can be deployed and managed from the Deployment console. 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. However. software. The following HP server blades are supported: HP Proliant™ BL e-Class Proliant™ BL 10e Proliant™ BL 10e G2 HP Proliant™ BL p-class Proliant™ BL 20p 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. including Sample Jobs in Deployment Solution. and Server Deployment Rules. configure and provision new server blades using a variety of features. 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).

Initial Job. All subordinate Enclosures and Bays are identified with custom names under the Dell rack name. Select an existing job to run when the virtual computer is associated with a new server blade. Dell Server Blades Dell high-density blade servers can be deployed and managed from the Deployment console. Any blade server can have predefined deployment jobs and configuration tasks associated with it to execute automatically upon installation.For HP blade servers in the physical view the Rack name can be a custom name in the console. if you create Virtual Bays with fewer bays (8) and install an enclosure with additional bays (20). All Dell Rack Servers are supported by Deployment Solution. Enclosure type. the excess virtual bays will be truncated automatically. Enter or edit the name of the Rack. 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. Note If you create Virtual Bays for an enclosure (such as the BLe-class with 20 bays) and if another model of server blade with an enclosure containing fewer bays is connected (such as the BLp-class with 8 bays). or to a specific server blade in the bay. the enclosure. 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). but the server blades can also be managed from the physical view in the Rack/Enclosure/Bay view. See also Managing New Server Blades on page 246. Select the type of HP server blade from the list. Enter or edit the name of the Enclosure. Example: Altiris® Deployment Solution 6. Virtual Bays Blade servers now have a Virtual Bay feature that allows you to pre-assign deployment jobs to the rack. Rack name. the Rack name will always be Dell. Conversely. Select the Server Deployment Rules to run on the Bay when a new server blade is installed. The following servers are supported: Dell Rack Servers All PowerEdge™ rack servers Dell Server Blades PowerEdge™ 1655MC For Dell blade servers in the physical view. Enclosure name. Server Change rule.8 SP2 247 . Example: <rackName> <enclosureName> <bayNumber> See also Server Management Features on page 243 and Server Deployment Options on page 244. with all subordinate Enclosures and Bays also identified.

Fujitsu-Siemens Server Blades Fujitsu-Siemens high-density blade servers can be deployed and managed from the Deployment console. All IBM blade servers are supported by Deployment Solution. IBM Server Blades IBM high-density Blade Centers can be deployed and managed from the Deployment console.8 SP2 248 . Altiris® Deployment Solution 6. For IBM blade servers in the physical view. the Rack name will always be Fujitsu-Siemens. Example: IBM <enclosureName> <baynumber> See also Server Management Features on page 243 and Server Deployment Options on page 244. The following servers are supported: Fujitsu-Siemens Rack Servers All Primergy™ rack servers Fujitsu-Siemens Server Blades Primergy™ BX300 blade servers For Fujitsu-Siemens blade servers in the physical view. but the server blades can also be managed from the physical view in the Rack/Enclosure/Bay view. Example: Fujitsu-Siemens <enclosureName> <bayName> See also Server Management Features on page 243 and Server Deployment Options on page 244.Dell <enclosureName> <bayName> See also Server Management Features on page 243 and Server Deployment Options on page 244. but the server blades can also be managed from the physical view in the Rack/ Enclosure/Bay view. All subordinate Enclosures and Bays are identified with custom names under the Fujitsu-Siemens rack name. All Fujitsu-Siemens Rack Servers are supported by Deployment Solution. 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.

8 SP2 249 .Part V Operating System and Platform Reference This section contains operating system and platform-specific information you need to consider when managing computers. Altiris® Deployment Solution 6.

Example: if you have x86 and x64 versions of the Linux preboot environment selected for a configuration.8 SP2 250 . PXE automatically detects the architecture and sends the correct boot image. you can have 32.and 64-bit comptuters in the same group and use conditions to ensure each receives a different version. An Itanium will attempt to boot only an Itanium boot image. and you add an executable. Boot Disk Creator checks the file header to see which architectures the executable supports. this screen appears prompting you to add additional files or ignore the warning.5. Example: when distributing software. Boot Disk Creator configurations are independent of architecture. There are two differences for 64-bit: When you create a PXE boot configuration (example: an item on the PXE boot screen). 64-bit PXE Boot Images & Configurations Deployment Server 6. you select the architectures you want to include when you create the configuration. Altiris® Deployment Solution 6. it will use the x86 version. if you manually add executables to a configuration which supports multiple processor types.Chapter 21 64-bit Platforms Deployment Solution has been designed to make managing different platforms as seemless as possible. and includes tips to more effectively manage these computers. you are asked which architecture you want to use.8 uses the same process to create automation boot configurations as Deployment Server 6. If not all architectures you have installed are supported by the file you added. This section walks you through the enhancements added to support 64-bit. When you create an automation partition or boot disk from a Boot Disk Creator configuration. If you attempt to boot an x64 computer without an x64 boot image. you need to ensure you provide a version of the file for each architecture you have included. Adding Files to a Boot Disk Creator Configuration for 64-bit For the most part. When a managed computer boots this configuration. 64-bit Job Conditions and Filters Functionality has been added to let you set conditions and filters based on the computer architecture. These conditions and filters let you set up your jobs to make decisions based on the architecture so you don’t have to re-organize your tree around architecture. Boot Disk Creator automatically gathers the correct files for that architecture. However.

called ADLAgent. If you have software which requires configuration beyond this. Installing and Configuring ADLAgent For basic instructions on installing ADLAgent. the file is copied to the system. Altiris® Deployment Solution 6. in the Linux production and automation environments./configure) and the make install command is executed. or adding a line to a standard script. You can configure the agent using the configuration script. and Solaris. you can copy the installation files to an NFS or other share on your network. use a file copy task along with a shell script to install the software. see Installing Deployment Agent on Linux on page 350. Fedora Linux automation environment Support for deploying KickStart scripted installs Native imaging support for ext 2 and 3 filesystems Native imaging support for LVM This section contains considerations you must be aware of when managing Linux and Unix systems. If you need to install ADLAgent on multiple computers. or if you are using a package management system. use standard remote access tools to run the installer. or by modifying the configuration directly in the Deployment Console. You might also modify the ADLAgent configuration file once and copy it to each computer. extracted. including: A native Linux and Unix agent. This might involve using ssh to log in remotely. Unix. When using this task with these formats. and contains the following topics: ADLAgent ADLAgent is the client software which provides connectivity to Deployment Server from Linux.Chapter 22 Linux and Unix Systems Altiris Deployment Solution has several tools to effectively manage Linux and Unix computers.8 SP2 251 . modifying the configuration file directly. Installing ADLAgent on your Linux and Unix computers involves copying the necessary binaries to the client and running the installation script. Distributing Software The software distribution task now supports a number of Linux and Unix file types. A large number of software packages can be installed using this process. The configure script is executed (.

your MBR is modified to boot this partition.Imaging Linux and Unix Filesystems RapiDeploy provides native imaging support for EXT2 and EXT3 file systems. To prevent this. Second. do not update any software which modifies your MBR without uninstalling the automation partition first. if you are using an automation partition.8 SP2 252 . The automation partition can be reinstalled after the software update. your MBR is modified and you might not be able to access your automation partition. If this occurs. but you need to use the -raw switch. Altiris® Deployment Solution 6. Other file systems can be imaged. First. if your bootloader is located on a reiserfs partition. If you install a new version of a bootloader. Linux Bootloaders There are a few considerations you must use to preserve the functionality of Linux bootloaders. you must use the -raw switch when imaging this partition to preserve the structure. you can reinstall the automation partition.

low maintenance solution for organizations that want to perform tasks or access programs such as: Web browsing. The following is a list of the supported functions for thin clients running CE . you must install the Deployment Agent on the thin clients (“pull”) directly.8 SP2 253 . The Automation Agent boots thin clients to automation mode so they can run deployment jobs. Deployment Agents (page 112). security. and reliability. See Automation Agent Settings (page 379). However the there is limited functionality for thin clients running CE . or the proprietary version of Linux from HP or Neoware. Thin client computers come pre-installed with the Deployment Agent so when they are added to a Deployment Server system. which increases their manageability. Production versus Automation Agent Deployment Solution requires that a Production Agent be installed to each thin client you want to manage from the Deployment Console. such as run script. instead of installing an embedded automation partition. which lets you begin managing the device. The client computer’s MAC and IP addresses are added to the Deployment database. Java-based applications and terminal emulation. NET.Chapter 23 Managing Thin Clients Thin clients are a low cost. if you have thin clients running either CE. create and distribute disk images. Rather. Example: users can range from receptionists and data entry workers to users accessing systems from kiosk locations commonly found in call centers or health care environments. communications between the server and client are established right away. Thin clients connect to any current or legacy network and can be managed from a centralized location.NET. See Thin Client Operating Systems (page 254).NET. Thin client operating systems The Deployment Agent is the Production Agent and can be installed to thin clients running Windows XP Embedded from the Deployment Console. Altiris recommends using a PXE Server to boot thin clients to automation. Thin clients do not contain any moving parts and data is stored in RAM. Modify Computer Configuration (the computer name and TCP/IP Setting only) Distribute software (“. However. or line of business (LOB) applications. you cannot remote install (“push”) the Deployment Agent from the Deployment Console.CAB” and “. Thin clients provide users a reliable server-based environment without the complexity or maintenance of a PC. See Installing Deployment Solution Agents (page 344). Supported Deployment Solution Functionality Deployment Solution supports full functionality for thin client running XPe and Linux.EXE” files) Execute and run scripts (DOS and WIN batch files) *no VBS support Copy files and directories Create disk images Altiris® Deployment Solution 6. and more.

Manufacturer Fujitsu-Siemens Model Futro B. Altiris® Deployment Solution 6. CapioOne G150 and Eon E100 series thin client models. Futro S series thin clients come pre-installed with the Deployment Agent and a license for Deployment Solution. CE. See Windows XP Embedded (XPe) (page 254). See Managing Licenses (page 352)or the Altiris Getting Started Guide for more information. t5500.NET (page 257). and t5700 clients. with full Win32 Application Program Interface (API) capabilities. The thin clients come pre-installed with Windows XP Embedded.Distribute disk images Remote Control clients (24 bit color depth only. Net 4.NET. Windows XP Embedded is a componentized technology based on the Windows XP Professional operating system. Windows XP Embedded (XPe) Microsoft Windows XP Embedded (XPe) is a powerful. However. S.0.8 SP2 254 . HP. Altiris supports Fujitsu-Siemens. and reliable operating system that runs on PC architecture hardware with x86 processors. All HP thin clients come pre-installed with the Deployment Agent. and C series thin clients running the Windows XP Embedded operating system. and Linux (page 257). depending on the model of the device. This lets you easily add new devices to the network and establish communications with the Deployment Server. 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 Supported Thin Client Manufacturers Currently.2 or 5. Windows CE . Deployment Solution does not support Futro thin clients running Linux. but if your device is missing the agent. HP HP t5000 thin client series. rapid. the Futro B series requires that you install the Deployment Agent before obtaining a Deployment Solution license from Altiris. or NeoLinux. and Neoware thin clients. Windows CE . or Linux. which includes the t5300. Neoware Thin Client Operating Systems Thin clients come pre-installed with an operating system and the Altiris Deployment Agent. Thin clients come pre-installed with Windows XP Embedded. contact Neoware for a Snap-In. Currently. All Neoware thin clients come pre-installed with the Deployment Agent.

and modifying the configuration (computer name or IP address) already have scripts to handle EWF.Because application developers can choose from over 10. Example: from the Deployment Console in the Jobs pane. These jobs disable EWF first. The data stored in the overlay gives user’s the appearance that files. Other tasks such as. you must turn off The Enhanced Write Filter on the thin client before installing the Deployment Agent. and the second line item checks to verify that EWF is disabled. Because this script handles EWF automatically. and installing the Deployment Agent for Windows. the Enhanced Write Filter is re-enabled. With EWF enabled. the image footprint is smaller and can boot basic images as small as 8MB. There are no limitations when installing the Deployment Agent to thin clients from the Deployment Console. and re-enable EWF as the last step of the deployment job. When creating your own Deployment jobs. See also: Installing Deployment Solution Agents (page 344)and Deployment Agents (page 112). all data written to the overlay storage area will be deleted when the thin client reboots. so that the agent will be saved to the client’s memory. or any other data installed to the thin client. any data writes will be redirected to an alternate storage area called an overlay.8 SP2 255 . The Deployment Agent used for computers running 2003\XP000 is the same agent that is installed on thin clients running the Windows XP Embedded operating system. Some of the tasks Deployment Solution tasks that are impacted by the Enhanced Write Filter are certain deployment jobs. run other scripts or tasks.000 individual feature components. However. The Create Image task creates a copy of the thin client’s image and stores it in the Images folder on the Deployment Share. thin clients can be managed from the Deployment Console without concern that data tasks will not be saved to managed thin clients. creating and distributing images. is a job called Create Disk Image. When the image task completes. programs. The Enhanced Write Filter The Enhanced Write Filter (EWF) is a unique feature of the Windows XP Embedded operating system that protects data from being written to the Hard Disk (RAM) storage area on a thin client. located in Samples > Windows XP Embedded. The script reads as follow: Notice that the first line item disables the Enhanced Write Filter. will be permanently saved. If Altiris® Deployment Solution 6. However. and the thin client reboots. This ensures that data written to thin clients during the deployment job will not be lost when clients reboots. use the Samples in the Job pane of the Deployment Console to help you create your own scripts to handle EWF automatically. The Enhanced Write Filter is an IT managing feature that helps control the data stored on a thin client’s hard drive.

exe program. Deployment Agents (page 112). See the Sample Jobs folder in the Jobs pane in the Deployment Console for examples. Using the EWFMGR Utility HP and Fujitsu-Siemens thin clients can enable or disable the Enhanced Write Filter. using a Windows XP Embedded utility named ewfmgr. data will be lost. See also: Building and Scheduling Jobs (page 147). Altiris® Deployment Solution 6.8 SP2 256 . the next time a thin client reboots. The following are a few examples of how to use the ewfmgr. -disable -enable Enables the write filter so that data written to the protected media is cached in the overlays.EWF is not disabled and enabled properly. or contact Neoware. you typically will only use the following three or four. The current overlay level becomes 1 as soon as EWF is started. Note Neoware thin clients use a different method of enabling and disabling the Enhanced Write Filter. The default command is to display protected volume information. however. after you run a Deployment job. and a new overlay is created at level 1.exe. Switch -all Description Performs a specified command (such as disable or enable) on all protected volumes. which is stored in the C:\Windows\System32 folder. Disables the overlay on the specified protected volume. Although there are many switches that can be used with this utility. -commitanddisable Commits all current level data in the overlay to the protected volume and disables the overlay.

Although the enhanced Write Filter manager can be run from a thin client.NET is designed for a broad range of intelligent hardware devices that require a small-sized operating system. but the Deployment Agent for Windows CE .NET operating system.NET can run on multiple processors. supports Win32 Application Program Interface (API). Windows CE . it is more efficient to include it as part of your Deployment Job. Rather. Altiris® Deployment Solution 6. This enables the Enhanced Write Filter on the C: volume. Window CE . Application developers can choose from a wide range of modules and components. you cannot push the Deployment Agent for CE . Contact the manufacturer for more information. but Neoware thin clients must purchase a standard license.NET Microsoft Windows CE . Licensing Thin Clients HP and Fujitsu-Siemens thin clients do not require a license. See Deployment Agent for CE .Example ewfmgr -all Description This displays the current Enhanced Write Filter settings. Deployment Solution lets you mange thin clients running Windows CE .8 SP2 257 .NET (page 122). However.NET must be installed on each device. Linux HP and Fujitsu-Siemens distribute their own proprietary versions of Linux for thin clients supported by Altiris.NET to thin clients running the Windows CE . Many of the thin clients supported by Deployment Solution come preinstalled with the Deployment Agent and can be managed after they are connected to the network. See Managing Licenses (page 352). creating small image footprints booting the basic image from 350KB. you must run the Deployment Agent installation from the thin client directly. ewfmgr c: -disable ewfmgr c: -enable This disables the Enhanced Write Filter on the C: volume.NET from a centralized location. and runs in Realtime right out of the box. and usually run disconnected from other computers. due to limitations of the Deployment Console.

use a command similar to the following: DAgent." or you have provided appropriate domain credentials to perform a remote installation. Vista Software Distribution Due to increased security in Vista. the "copy all directory files" and/or "copy all subdirectories" options are selected to provide these files. launch the installation MSI on the computer using and admininstrator account and complete the prompts. scripts executed by Deployment Solution cannot display anything to the user.8 SP2 258 . The installation is set to run as completely silent.17. including pause statements. To install. To perform a silent installation. If you are attempting an installation from a remote location or UNC path. Vista Run Script Tasks Due to increased restrictions placed on services in Vista. To remotely install combine the above instructions for a silent installation with a login script or group policy object.msi -qn server_tcp_addr= 172.180 server_tcp_port=402. you have left the advanced option on the default selection.19. Scripts requiring user interaction. Altiris® Deployment Solution 6. software must meet the following criteria before it can be distributed using Deployment Solution: The software you are distributing must be Vista compliant. only one setup executable is required to complete the installation. will not execute correctly. See the release notes for additional information. No user input is required by the installation prcess. In the Distribute Software Task. "Copy files using Deployment Server then Execute. If the package requires additional files. Vista Remote Control Deployment Solution uses the Remote Desktop feature of Vista to perform remote control.Chapter 24 Windows Vista Installing the Deployment Agent on Vista The installation program is contained in the Agents folder on the Deployment Share. Remote Desktop must be enabled on the remote computer and you must have the required credentials to use remote control.

This interface is similar to the configuration interface for the Deployment Agent on other Windows operating systems. The configuration utility is launched by selecting Start > Altiris > Deployment Solution > DAgent Configuration. Additionally. To install. support is provided for the WIM format using ImageX. Altiris® Deployment Solution 6. Vista Imaging RDeploy fully supports imaging Vista computers similar to other Windows operating systems.Deployment Agent UI on Vista When installing the Deployment Agent on Vista computers.8 SP2 259 . select the Control panel applet & UI component option during the DAgent installation. See ImageX Imaging (page 218). you now have the option of installing a client-side agent configuration utility.

2. Removing the Mac Deployment Agent An uninstall script is contained in the /opt/altiris/deployment/adlagent/bin folder. When the installation completes the computer appears in the Deployment Console. providing the IP address of your Deployment Server and the IP address of your NetBoot Server.Chapter 25 Power Mac Installing The Mac Deployment Agent 1.zip. Complete the prompts. 3. Altiris® Deployment Solution 6.8 SP2 260 . Connect to the Deployment Share using Finder > Go > Network > domain > Express. 4. Browse to the Agents/ADLAgent folder. replacing domain with the domain containing your Deployment Server. Extract and run the program contained in altiris-adlagent-x-darwin.

Part VI Reference: Deployment Solution Help Files This section contains the help files that are launched from the Deployment Console.8 SP2 261 . and other Deployment Solution utilities. Translated versions of these help files are available in the product. Web Console. Altiris® Deployment Solution 6.

Open the Deployment Server Configuration Utility by clicking Start > Programs > Altiris > Deployment Server > Configuration. View server activity and statistics.8 SP2 262 . access Deployment Server configuration options. Connections Option (page 268). and restart Deployment Server. you can view Deployment Server statistics. Log in to the Deployment Server you want to manage. Set the communications protocol (multicast or TCP) and set the imaging multicast threshold. See Logon Account (page 263). Item Server activity and statistics Start Stop Restart Description Lists the number of Deployment Server sessions (clients) and Deployment Server Consoles currently running on the network. See Drive Mappings Option (page 264). and more. Stops the Deployment Server on the local computer. start and stop the Deployment Server.Deployment Server Configuration Utility The Altiris® Deployment Server™ Configuration Utility provides general preferences for the Deployment Server. Filter connections from the Deployment Server by IP addresses or network adapter interface. You can use the Deployment Server Configuration Utility to: Set up an account for Deployment Server. Altiris® Deployment Solution 6. Map drives to file servers in your Deployment Server system (if you have images stored in more than one place). Starts the Deployment Server on the local computer. From the main view of the Deployment Server Configuration Utility. See Transport Option (page 265). start. Set debug and log file options in the Debug Option (page 269). Stop. Restarts the Deployment Server on the local computer.

you must enter the username and password. Choose whether you want to use the LocalSystem account or a user-defined account. The default setting is to provide a user name and password during installation. Click Account. Options Opens the Deployment Server Options dialog. Open the Deployment Server Configuration Utility in the Control Panel of the Deployment Server computer. If you choose a user-defined account. Altiris® Deployment Solution 6. 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. The LocalSystem account requires a simple install that runs Deployment Server services on the local computer.Account Opens the Server Login Account dialog. The account must have Administrator equivalent rights on the Deployment Server computer. 4. which lets you specify the account used by the Deployment Server service. prohibiting access to network shares or components. Item Use the Local System account Description Specifies that the LocalSystem account should be used by the Deployment Server service. Click OK. which lets you specify Deployment Server options. Specifies that a user-defined account should be used by the Deployment Server service. With this option you can install the service on different computers and access components across the network. 2. 3. Use the following account and password To specify or change the Deployment Server service account 1. If this option is selected. Logon Account This Service Logon Account dialog is used to set up the user account used by Deployment Server. you can click the Allow service to interact with desktop box to place an icon in your system tray.8 SP2 263 . This icon lets you 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). With the LocalSystem account selected. you must supply the appropriate username and password. You must use this option if your Deployment Server directory is located on a different server than the Deployment Server.

Select this option to send a Wake on LAN request to the client computer. The Deployment Server sends a CACK (Client Acknowledgement) request to client computers. it terminates the connection. It waits for a response from the client for a specified timeout value. Click Schedule to schedule the resetting of the inactive client connections. whereas the client is active. you need to create a G: drive mapping on the Deployment Server using this dialog. and delete drive mappings used by the Deployment Server. Reset inactive client connections. which lets you create a drive mapping. Due to network glitches. Update active client connections. inactive client connections are reset according to a specified schedule. Drive letter to which the drive mapping is mapped. UNC path. Example: if you create a job that distributes software packages from a drive on another file server using a mapped G: drive. Drive Mappings Option The Drive Mappings tab is used to add. Inventory provides software and hardware information about a client computer. If this option is selected. Driver Letter. Any drive mappings used to reference files need to be duplicated here. If it does not receive a response from the client within that specified time.General Option Update Inventory on active computers. Click Schedule to schedule updated inventory. Send Wake on LAN to inactive computers when scheduling.8 SP2 264 . which lets you edit the drive letter or UNC path of the selected drive mapping. Removes the selected drive mapping. Item Drive Letter and UNC Path Add Description Displays the drive mappings with the mapped drive letters and the corresponding UNC paths. UNC path to which the mapped drive points. Select this option to encrypt all communication between IIS and the Data Manager. Modify Remove Opens the Map Drive dialog. the console may show the client active. You can retry sending this request through the Retry every _______ minutes option. when it is inactive. Click Schedule to schedule updated active client connections. edit. Altiris® Deployment Solution 6. It also updates the inventory according to a specified schedule. The Deployment Agent or any other agent sends the inventory when it connects to the server for the first time. Due to network glitches. Encrypt communication between IIS and Data Manager. the console may show the client inactive. You can update inventory on active computers at specified intervals. Opens the Map Drive dialog.

The default path is C:\Program files\Altiris\express\Deployment Server. 6. 3. Click Yes to restart the service. Modifying this setting does not automatically let you use another shared directory other than the express share. run a Custom install to establish another location for the Client Access Point. 5. 2. Click Options and click the Drive Mappings tab. Modify the Drive Letter and UNC Path as desired. Open the Deployment Server Configuration Utility in the Control Panel of the Deployment Server computer.8 SP2 265 . Click Add. Altiris® Deployment Solution 6. 2. Click OK. Specify the Drive Letter and UNC Path. To remove a drive mapping 1. 4. 2. 4. Select the drive mapping you want to remove and click Remove. 3. 5. Note Do not use this setting to change the path to the Client Access Point. To create a drive mapping 1. Select the drive mapping you want to edit and click Edit. To edit a drive mapping 1.Click OK. Click Options and click the Drive Mappings tab. Click OK. Open the Deployment Server Configuration Utility in the Control Panel of the Deployment Server computer. Click Yes to restart the service. 3. Click OK. Open the Deployment Server Configuration Utility in the Control Panel of the Deployment Server computer. Transport Option The Transport tab lets you specify settings for the Deployment Server transport protocols. Click Yes to confirm your decision. 5. To change the Client Access Point shared directory. 4. Click Yes to restart the service. 6.Click OK.Data store path Specifies the path to stored packages and files and other DS functions (such as license verification). Click Options and click the Drive Mappings tab.

Open the Deployment Server Configuration Utility in the Control Panel of the Deployment Server computer. this agent does not downgrade automatically if it connects to a Deployment Server of an earlier version. TCP Port Automatically update clients Allow Encrypted Sessions Allows encrypted sessions between the Deployment Agent and Deployment Server. 3. 4. Click OK. This is used only if multicast is not disabled.Item Disable multicast support (agents must connect using TCP) Multicast Address Multicast Port Multicast TTL Description Disables multicast support. Do one of the following. Port used for the multicast.8 SP2 266 . which means clients must connect to the Deployment Server using TCP. and click the Transport tab. Click Options. This is used whether multicast is enabled or disabled. select Disable multicast support and supply the Multicast Address. do not select the Disable multicast support check box. If you want to use TCP. If the Deployment Agent data encryption is turned on. and TCP Port. depending on the transport you want to use: If you want to use multicast. 2. This is used only if multicast is enabled. install the older version of the agent manually. Multicast Port. The multicast address. To specify the Deployment Server transport 1. 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. Multicast TTL. To downgrade any agent. this Deployment Server option must also be turned on to pass encrypted data between client and server. Specifies the number of "hops" or hubs that the client can go through to multicast.8 version. Note If any agent is upgraded to the Deployment Solution 6. Altiris® Deployment Solution 6. This is used only if multicast is not disabled. The TCP port.

Disk Imaging Option The Disk Imaging tab lets you specify when image multicasting is used and how much bandwidth is used during multicasting. multicasting is disabled and all computers are imaged using direct connections. multicasting is not used. This option can be used if your clients can read an image file from the server faster than trying to coordinate masters and clients. Altiris® Deployment Solution 6. select the Use disk image multicast threshold of n clients check box and set n to 0. so other network traffic can take place at a reasonable rate. If this option is not selected.8 SP2 267 . Note When multicasting a disk image using the PXE Server. 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. all clients become Masters and read from the image server independently. The multicasting feature is disabled for multicasting because of continued data corruption problems inherent with the Intel Universal NIC driver. Set this value to 0 to disable multicasting. When multicasting is not used. 3. Open the Deployment Server Configuration Utility in the Control Panel of the Deployment Server computer. If the number of clients is less than or equal to the number specified. This option prevents the multicasting operation from using all available bandwidth on a network. If you want to use multicasting only when there are more than a specific number of clients. 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 check box and set n to the number of clients there must be more than before multicasting is used. If you want to use multicasting whenever there is more than one client. multicasting is used whenever there are two or more clients. As a result. 4. do NOT select the Use disk image multicast threshold of n clients check box. Item Use disk image multicast threshold of n clients Description Specifies the number of clients that must be involved in a job before image multicasting is used. Click OK. the boot disk on the PXE Server cannot be configured with an Intel Universal NIC driver (also known as an UNDI driver). if the computers being imaged are booting to PXE boot files configured with an Intel universal driver. 2. Limit each disk image multicast to n Mbps To set when multicasting is used 1. Click Options and click the Disk Imaging tab. Limits the bandwidth used in a multicasting session to a user-defined number of Mbps.

4. 2. Click the Use SQL Server account authentication check box. 3. 2. Open the Deployment Server Configuration Utility in the Control Panel of the Deployment Server computer. Define Subnets Select the Allow/reject agents based on their IP subnet box and click Define Subnets. NetWare Server Authentication To access and authenticate to a Novell NetWare Server 1. Enter the username for the selected server.8 SP2 268 . Database Authentication To access and authenticate to a specified Microsoft SQL Server database 1. You can add a security key for the server to which you want to connect. 2. Click Options and click the Disk Imaging tab. Select the Limit each disk image multicast to n Mbps check box and set n to the maximum bandwidth you want a multicasting operation to use. Connections Option The Connections tab lets you allow or reject connections from the Deployment Agents based on the IP subnet. Click OK. 2. You can export and save the security key for your Deployment Server to a file. 3. Click Add Key. IP address. 3. Click Delete Key. Enter the password. Click Export Key. You can delete the security key for a Deployment Server. Authentication Option The Authentications tab lets you authenticate to an existing SQL Server database.To set the maximum bandwidth used during multicasting 1. Enter the password. to the NetWare Server as a file access point. Enter the username for the specified database. Altiris® Deployment Solution 6. Click Add or Modify to enter or edit a network IP address and the corresponding mask. DS Authentication To access and authenticate to Deployment Solution 1. and to Deployment Solution. and local interfaces.

Altiris support can instruct you on the required logging level for your issue. with nine the deepest logging level and one the most cursory logging level. Select the directory path and name to log error messages between managed computers and the Deployment Server. Click Add or Modify to enter or edit a specific a range of IP addresses to connect to the Deployment Server. This number can be from 1 to 9. Click either the Allow or Reject option. Log File Name: Set the path and name for the log text file. Logging Level: Enter the logging level. Altiris® Deployment Solution 6. Select from the list of network adapter cards to allow or reject when connecting to Deployment Server.log. Debug Option The Debug tab lets you set debug options for Deployment Server and communication between managed computers.Define IP Addresses Select the Allow/reject agents based on their IP address box and click Define IP Addresses. Max File Size: Set the size of the text file by entering the maximum file size allowed. The default name is axengine.8 SP2 269 . Select this option to set the name and location of the logging report and the logging level for Deployment Server.log in the Deployment Server shared directory. Log Directory. Each managed computer has its own log file in this directory named <the computer ID of the managed computer>. Set the size of each log file by entering the maximum file size allowed. Engine Debug Logging. Set the path of the folder to collect the client error messages. Max File Size. Log Agent Communication with Engine. Define Interfaces Select the Allow/reject agents based on their IP address box and click Define IP Addresses. The Engine Debug Log is a single report that captures debug information for Altiris support personnel.

you must first install the pre-boot operating system files for the types of pre-boot configurations you want to create. The base pre-boot operating system files. When the Deployment Solution gets installed. the appropriate Automation Agent is also added. 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. Network and Automation Boot Disks (page 280). 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. Altiris® Deployment Solution 6. or with network connectivity to retrieve an image from the Deployment Server USB flash drives Windows installation packages See Create Boot Disk (page 280). You can create DOS. This feature lets you create a single deployment job with multiple tasks that boots to the automation environment you want when each task runs. Before creating configurations.8 SP2 270 .Introduction to Altiris® Boot Disk Creator Altiris® Boot Disk Creator (BDC) is a utility that comes with Deployment Solution and lets you create configurations for pre-boot environments. The Boot Disk Creator Utility gathers data as you create new configurations. you have the option to install the pre-boot operating system files at that time. disk drivers. Based on the type of preboot environment you are creating. Boot Disk Creator creates the type of bootable media you want to use when booting client computers to automation. and Windows Preinstallation Environment (Windows PE) configurations. Linux. you can use the Install Pre-boot Operating System Files feature within Boot Disk Creator to install the necessary pre-boot operating system files. which gives you greater flexibility in managing client computers. The configurations you create can be assigned to automation tasks within deployment jobs that boots client computers to the automation environments. Automation Partitions. The client computer 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. Boot Disk Creator supports the following bootable media: Floppy disks Bootable CDs and DVDs with an ISO image. If there are no files installed.

Or. but you cannot edit the boot images after they have been imported. The colors on the display change when you select a configuration in the treeview of the utility. Network and automation boot disks can create ISO images. This is how you select the type of pre-boot environment configuration you want to create.Example: You can install DOS. See Install Pre-boot Operating System Files (page 285). so that you can create boot menu options using the New Configuration Wizard. You can also create a Windows Installation package to run in a Windows production environment. The colors indicate the following: Black: No configuration has been selected or there are no configurations to select. If you create an Automation boot disk. If you select Network boot disk. along with other settings such as. You can only create configurations for the type of pre-boot operating system files you have installed. See New Configuration Wizard (page 272). You can create floppy boot disks. See PXE Configuration Utility Help. the Create Boot Disk Wizard automatically appears. Boot Disk Creator uses colors to inform you which type of pre-boot configuration you are editing. or Windows PE operating system files so you can create any type of configuration any time you want. displaying only a user’s prompt. After the wizard completes. 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. Boot Disk Creator can also be accessed from the PXE Configuration Utility. they try to connect to the Deployment Server. and more. The New Configuration Wizard is the main process of Boot Disk Creator. which are use for DOS configurations since Linux and Windows PE system files are too large to fit on a floppy. which installs an embedded (recommended) or hidden automation partition on the client computer’s hard drive. The PXE Configuration Import feature lets you import images that have been created by Boot Disk Creator or any other third party imaging software. the Automation Agent is added to the configuration so that when you boot client computers. Altiris® Deployment Solution 6. which you can save to bootable CDs using your own third party CD burning software. client computers boot to the network server you specified in the New Configuration Wizard. 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. Blue: DOS configuration Green: Linux configuration Red: Windows PE configuration See Edit Configurations (page 278). Linux. TCP/IP information. 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. See Automation Partitions. and import the boot images into the PXE Configuration Utility. you can install only DOS and Windows PE system files and install Linux later. or you can select a flash drive from the Bootable drive drop-down list. To help you manage the configurations you create. the type of network adapter.8 SP2 271 . Network and Automation Boot Disks (page 280). You can also create boot configurations directly from Boot Disk Creator. network server information.

You must enter a name of for the configuration to make the Pre-boot Operating System for this Configuration fields active. To start the New Configuration Wizard. Linux. or click Tools > Boot Disk Creator. using an installer package. such as the file server type. New Configuration Wizard You can create as many configurations as needed to support varying types of computer environments. which is the same for DOS. Create an Automation Install Package (page 281): Creates and installs an embedded automation partition to a client computer’s hard disk. or Windows PE. click Ctrl+N. Remove Automation Partition (page 283): Removes an automation partition from a client computer’s hard disk. Before you begin. you must install the pre-boot operating system files that Boot Disk Creator uses to create new configurations. The options are: Buttons Description New Configuration Wizard (page 272): Creates new configurations that is used when booting client computers to automation or a network prompt. The description field is optional but helps you to know what the configuration contains.8 SP2 272 . See Install Pre-boot Operating System Files (page 285). open the Deployment Console and click the icon on the toolbar. Create Automation Boot Disk (page 282): Creates automation boot disks to manually boot client computers to automation. Configuration Name This is the first page of the New Configuration Wizard. NIC drivers. or click File > New Configuration. click the icon on the toolbar of the Boot Disk Creator tool. and any additional files you want to add. Toolbar Description The icons on the toolbar help you navigate to the tasks you want to perform within Boot Disk Creator in one click. Create Network Boot Disk (page 283): Creates network boot disks to manually boot client computers to a specified network server. Altiris® Deployment Solution 6.To start the Boot Disk Creator tool.

You can select Multi-NIC drivers to be included in the configuration by pressing Shift-Click or Ctrl-Click. Novell NetWare (VLM): Select this option to store images on a NetWare server with VLM clients. Linux. a list of supported drivers appears. depending on the whether you selected a Simple or Custom Deployment Solution installation.Field Definitions Name: The configuration name you enter appears in the Configurations treeview after the wizard is completed. operating system. However. this option can save you time and effort in booting different computers. and any other characteristics that help you identify this particular configuration. (Example: enter the type of computer. using IPX network communications. This feature lets you build configuration files to boot multiple computers that contain different types of network adapter cards. Pre-boot Operating System for this Configuration: Boot Disk Creator supports DOS. the description you entered for this field appears at the top of the right pane. By default. if you select the configuration from the treeview. After a client computer boots using a multi-network adapter configuration. the first NIC card is detected and can potentially be the wrong network adapter required to connect to the Deployment Server. Field Definitions Microsoft Windows: Select this option to store images on a Microsoft server using TCP/IP network communications (recommended).8 SP2 273 . select the IPX check box at the bottom of the page. if you use IPX to communicate with a Microsoft server. but it can be on another server. However. Select the pre-boot operating system and click Install Pre-boot Operating System Files (page 285) to install pre-boot operating system files. Multi-Network Adapter Configurations If you are creating a DOS configuration. Novell NetWare (Client32): Select this option to store images on a NetWare server with 32-bit clients.) After the Create Configuration and Create Boot Disk wizards complete. and Windows PE operating systems to create pre-boot environments. File Server Type (DOS) The Deployment Share stores image files. packages. Boot Disk Creator applies the driver that matches the first network adapter card that it detects. network adapter. Use IPX to communicate with Netware: Select this check box if IPX is the network protocol for the Novel NetWare (Client32) server. the Deployment Share is installed to the Deployment Server. and data files. when you select Multi-NIC configurations. Altiris® Deployment Solution 6. See Multi-Network Adapter Configurations (page 273). Create multi-network adapter configuration: Select this option to add multiple network adapter drivers to a single PXE boot file configuration. Example: If you are going to use the multi-network adapter configuration for several different client computers. Description: Enter a description for the configuration. if a client computer has 2 NIC cards and you use the multinetwork adapter configuration to boot the computer.

See Multi-Network Adapter Configurations (page 273). Example: If most client computers have a Broadcom Ethernet adapter. Select a driver from the network adapters driver list. Have Disk You can add network adapter drivers by using any disk media or navigating to a folder. or network folder. CD. or network or automation boot disks. Advanced (page 275). you can use Up and Down to move the Broadcom Ethernet adapter to the top of the list. Linux. The Internet (page 275) button lets you connects to an Altiris supported Web site to download and install network adapter drivers. depending on whether you create automation partitions. See Have Disk (page 274). the Windows NIC drivers that are available to create a Windows PE configuration appear. If the network adapter you want. 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. This lets you specify which order the physical network adapters can be detected when the client computer boots. See Also: Network Adapter (page 274) 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. Internet (page 275). Network adapters can be downloaded from the manufacturer’s Web site and saved to a folder or a disk to be installed later. IRQ. See Install Pre-boot Operating System Files (page 285). and PCMCIA for DOS configurations) click Advanced. If you want to add or change adapter settings (such as I/O Memory. Internet.8 SP2 274 . Multiple Network Adapters Load Order This option is for DOS and Windows PE configurations only. or Windows PE so that client computers can connect to a network or Deployment Server. Altiris® Deployment Solution 6. If you select Auto-detect network adapter. you can click Have Disk. but some computers have a 3Com10/100 LAN PC Card Fast Ethernet card. Field Definitions Auto-detect network adapter: Select this to have Windows PE auto-detect the type of adapter that is in a client computers when the boot image runs. Windows PE determines which network adapter driver to use. The Advanced (page 275) button lets you further define network adapters and their drivers. See Advanced (page 275). or Windows Preinstallation Environment (Windows PE). New network adapters come with a floppy disk or CD to install the appropriate drivers. Linux.Advanced Features The network adapters you select must support DOS. or Advanced (if they are available for the type of configuration you are creating) to add additional drivers. The Have Disk (page 274) button lets you install network adapter drivers from a disk. and are automatically added to the new configuration. does not appear in the list. Example: After installing the pre-boot operating system files for Windows PE.

If you are using the IPX protocol. Microsoft clients EMM386 Memory (config.altiris. Advanced This options lets you add or change settings for network adapter cards so they work correctly when using DOS configurations. IRQ (protocol. and default gateway.Internet Altiris supports many manufacturer network adapters and supports a Web site for you to download the latest NIC drivers. using this configuration.sys): Append memory address information to this line in the config.ini file. click Advanced. Advanced settings (protocol.sys): Append memory address information to this line in the config. Memory (protocol.ini file. Use a static IP address: Select this option if you want a client computer. TCP/IP Protocol Settings This page lets you set up TCP/IP protocol settings for boot configurations. Refer to the following properties and values. Click Add Driver and the driver you downloaded is added to the Network Adapters list. Novell VLM clients Emm386 memory (config.sys file. Enter an IP address.ini): Add parameters to the NIC section of the protocol.com/support/NIC_drivers/. click Internet to launch the Web browser and connect to ftp://support.8 SP2 275 .sys): Append memory address information to this line in the config. Novell Client 32 Emm386 Memory (config. Subnet mask. If you are creating a Linux or Windows PE configuration. TCP/IP is the default protocol when client computers boot to automation on a Windows network.ini): Add parameters to the network setup section of the protocol.cfg file.sys file. From the Network Adapter page.ini file. 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. Advanced settings (driver command line): Add driver command-line entries to the landrv.sys): Add parameters to the NIC section of the net.sys file. this option is not available. Advanced settings (config. Download the driver you want and unzip the files it to a folder on the hard drive.ini): Add parameters to the network setup section of the protocol.bat file. Deployment Server uses its own IP stack to work on IPX networks. to be assigned a specific IP address. From the Network Adapter page. You can also enter a primary and secondary WINS address if you Altiris® Deployment Solution 6.

and more. This option also requires that you create a configuration for each client computer. Enter the TCP port number. The Deployment Server IP address. because the port numbers do not match. To set the TCP port on the Deployment Server 1. a multicast packet is broadcast across the network to find where the Deployment Server is located. change the Port field in the Boot Disk configuration to 402. you can ignore this page by clicking Next. Altiris® Deployment Solution 6. Click OK.8 SP2 276 . From the Deployment Server. 3. See your network adapter documentation or call the manufacturer or consult with your IT department for information. Use TCP/IP multicasting to find the Altiris Deployment Server: Select this option to use TCP/IP multicasting to find the Deployment Server. the IP address is required. Use TCP/IP to connect to the Altiris Deployment Server: Select this option to connect to a specific Deployment Server. sends job commands to the Deployment Agent. Altiris Deployment Server Communication This option lets you set communication properties for the Deployment Server. When client computers boot to automation using this configuration. 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. click Start > Control Panel > Deployment Solution Configuration applet > Options > Transport tab. If you intend to create a network boot disk. 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. so that the IP address is not the same for all computers. If you leave this field blank. as none of the properties are used to create a network boot image. Server name: When you select Use TCP/IP multicasting to find the Altiris Deployment Server. 2. To establish communications between client computers and the Deployment Server.need to resolve IP addresses and naming conventions. Server IP address: Enter the IP address of the Deployment Server to access information stored in the Deployment Share. a multicast packet is broadcast to the server you specify. This would result in client computers not being able to communicate with the Deployment Server. You must select this option if your network adapter or network does not support multicasting. the client computer connects to any server responding to the multicast packet. which manages the Deployment Database. and Port fields are critical because they define how client computers establish communications with the Deployment Server. Port: This option defines which port client computers can use to communicate with the Deployment Server Engine. If you are using the Intel Universal NIC driver (UNDI). Multicast IP address: Enter a multicast IP address for client computers to send a broadcast packet across the network to find the Deployment Server.

Path: Enter the path for the Deployment Share. leave this and the Password field blank.Port: This option defines which port client computers can use to communicate with the Deployment Server Engine. if you are creating a DOS configuration. the first mapped drive you specify must connect to the Deployment Share. Confirm password: Enter the password for the user name as confirmation that you entered the proper password in the Password field. they connect to the appropriate server.2. Window Workgroup: Enter the workgroup for the Deployment Share or file server. 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. which manages the Deployment Database. You can create multiple drive mappings or mount points. the mapped drive that appears is F: \<Deployment Share server>\eXpress.8 SP2 277 . Password: Enter the password for the user name. Field Definitions Manually create drive mapping: Select this option if you want the drive mappings to be included in the autoexec. Drive: By default. The path you enter maps to the drive letter you selected in the Drive 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. Lock Keyboard Select this option for additional security. Click Advanced to enter a NetWare context for the server and select a Frame type if it is different than the default value of 802. Click the drop-down arrow and select a different drive letter if F: is already in use. Example: Windows users: \server\share Altiris® Deployment Solution 6. and more. This prevents someone on the remote computer from ending the automation session and possibly accessing your network. If you did not assign a User name and Password when for the Deployment Share or file server was created. sends job commands to the Deployment Agent.bat file when client computers boot to automation. User name: Enter the authorized user name that was set up when the Deployment Share directory was created. Network Configuration This option lets you define how client computers connect to the Deployment Share or a file server where image files are stored. NetWare Server name: Enter the server name for the Deployment Share or file server. However.

Red: The configuration you selected or created is based on the Windows PE pre-boot environment. If you find a setting mis-entered or not what you want. Network and Automation Boot Disks (page 280) and Edit Configurations (page 278). running HTML applications. select the necessary components. See Automation Partitions. this page appears at the end of the New Configuration Wizard. WinPE Boot Option Settings Select the boot model and optional components to include with this configuration. Enter a Server name and IP address so that client computers can find the Deployment Share where image files are stored. You can also make text edits to files (selected from the treeview) in the right pane. Edit Configurations This is the main Boot Disk Creator page that appears when you start the utility. and click Back until you find the page for the options you want to change. the Edit Configuration page appears. To change configuration settings. Altiris® Deployment Solution 6. or delete. you can use the default boot model unless you are experiencing driver detection problems. right-click on a configuration folder and select Edit Configuration. the configuration information appears in the right pane. Blue: The configuration you selected or created is based on the DOS pre-boot environment. If you are using Boot Disk Creator from within the PXE Configuration Utility. See Edit Configurations (page 278).NetWare users: server\volume:directory Linux users: //server/mount point 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. edit. The colors displayed are: Black: You have not selected or created any configurations. As you select files and folders from the treeview in the left pane.8 SP2 278 . or connecting to an SQL Server database using ActiveX. If you are using Boot Disk Creator from within the PXE Configuration Utility. click Back to re-select the option. The display color changes to help you know the type of configuration you selected to view. Typically. the Create Boot Disk Wizard automatically appears for the next process to begin. When you click Finish. If you plan on executing VB scripts. This feature lets you modify configurations that have already been created. Configuration Summary This page lets you review all the options you selected throughout the New Configuration Wizard. Green: The configuration you selected or created is based on the Linux preboot environment. Use NetWare login scripts to create drive mappings: Select this option if you use NetWare and you want login scripts to create the drive mappings.

However. you can add tracert.bat. 3. it is overwritten. Install Pre-boot Operating System Files (page 285) Additional Files Boot Disk Creator lets you add additional files to folders that either apply to a specific configuration or to all configurations of the same type of pre-boot operating system.mounts. and the same file 5684_Drivers exists in a specific configuration folder. Right-click a configuration in the treeview and select New > Folder. Altiris® Deployment Solution 6. Example: using the Windows Copy and Paste command. the file in the configuration folder overwrites the file in the DOS additional files folder. To add files to the <OS> additional files folder. These folders are considered global. when the files are written to a boot image. any files you add to the global <OS> additional files folders are written to the boot image before the specific configuration files. unmapdrv.bat Linux .local WinPE . Add files to all configuration When you install a pre-boot operating system.mapdrv. 2.mapdrv. after you edit a configuration. press F5 to refresh Boot Disk Creator. A new subfolder is created in the treeview. do the following: 1. Example: if a file named 5684_Drivers resides in the DOS additional files folder.exe to the WinPE additional files folder. However. This may cause unexpected results. If you edit text files in a <OS> additional files folder. If you install pre-boot operating system files and the <OS> additional files folders do not appear.8 SP2 279 . yet the specific configuration file is the one that is written to the boot image.All other files within a configuration can be edited as needed. If a file in the <OS> additional files folder is the same name as a file in a specific configuration folder. since they can affect configurations of the same type. do one of the following methods: Copy files from a network folder and Paste them into the configuration folder. The folders that appear are as follows: DOS additional files Linux additional files WinPE additional files Boot Disk Creator copies the files from the <OS> additional files folders to all corresponding operating system configurations and is added to the boot images. Boot Disk Creator rewrites certain files within the configuration so that drive mappings and mount points are always updated.bat See also: New Configuration Wizard (page 272). the result is not as you expected. Add files to a specific configuration If you want to add files to a specific configuration only. Enter a name for the folder so that you know they are added files. The following files are rewritten after editing configurations: DOS . Each WinPE configuration you create adds the files in the WinPE additional files folder to the boot image. a new folder is added to the bottom of the treeview on the main page of Boot Disk Creator. and do not want to use the global feature of the <OS> additional files folders.

When client computers boot with this image file.Right-click a configuration and select Add File. Automation Partitions.8 SP2 280 . Field Definitions Automation PXE image: The automation agent for the type of pre-boot operating system configuration you created is added to the settings you selected throughout the New Configuration Wizard. Force 2. automation boot disks. after you select all the properties for a New Configuration. you can create bootable media to manually boot client computers to automation. Each type of bootable media guides you through a wizard to gather specific information required for the type of media you want to create. or network boot disks.88 MB PXE image: Select this option to increase the size of PXE boot images. When you click Finish. Enter a name for the file and write text as needed in the left pane. Create Boot Disk This dialog lets you create 3 different types of bootable media: an automation partition install package. the Create Boot Disk (page 280) dialog automatically appears. The Create Boot Disk step numbers appearing at the top of the dialog page vary depending on: How the Create Boot Disk dialog was started The type of media you selected to create Altiris® Deployment Solution 6. However. Create PXE Boot Image Files (PXE) This option is for Boot Disk Creator configurations created from within the PXE Configuration Utility. This process lets you select and create the method of booting a client computer to the automation environment. Network PXE image: The configuration you created does not contain an automation agent. and run deployment jobs as needed. they are mapped to a network server and are at a user’s prompt. the boot menu option appears in the Boot Menu tab. If you install an automation partition on a client computer’s hard disk. Right-click on a configuration and select File > Text file. PXE Boot Image Creation Complete This page lets you know when the PXE boot image file is completed. Because PXE Servers download boot image files to client computers. Click Back to change the new configuration settings for the boot menu option. A browser dialog appears to navigate to the file you want to add. See New Configuration Wizard (page 272). Boot Disk Creator must know what type of image file to create. Network and Automation Boot Disks After you create a New Configuration. A new empty text file is added to the treeview. deployment jobs can run automatically.

Boot Disk Creator shows the appropriate dialog pages when creating bootable media. The installer package runs in a production environment even though the New Configuration is based on the different pre-boot operating system. Both options achieve the same result even though the dialog steps may be different. Create an embedded DOS automation partition (recommended): Select this option to install an embedded partition to a client computer’s hard disk. Create an automation boot disk: Select this option to create automation boot disks so you can manually boot a client computer to automation.NET setup package: Select this option to install the automation partition using an installation setup package that runs in a Windows CE . from this page. depending on the type of operating system you selected. See Create Automation Boot Disk (page 282). See Create an Automation Install Package (page 281). You can select any of these options from the Boot Disk Creator toolbar or from the File menu.8 SP2 281 . Create an Automation Install Package This feature lets you create an automation installation setup package that installs an embedded automation partition on a client computer when it executes. Create a hidden DOS automation partition (for partitions greater than 50 MB): Select this option to install a hidden automation partition. 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. Create an automation partition install package: Select this option to create an automation install package that installs an embedded automation partition to any client computer on the network.The pre-boot environment you specified in the configuration you created However. installer package. Partition size in MB: The default partition size value changes. See Create Network Boot Disk (page 283). Create an automation partition install package. Example: if you right-click on a configuration in the treeview and select Install automation partition. or network boot disk. Windows CE . Field Definitions DOS bootable disk: Select this option to install the automation partition using a DOS bootable disk.NET production environment. 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. Linux bootable disk: Select this option to install the automation partition using a Linux bootable disk. Choose this dialog and return to the editor: Select this option to close the Create Boot Disk dialog without creating an automation boot disk. the number of dialog pages thereafter are different than if you select the option. Example: If you are creating an automation partition Altiris® Deployment Solution 6. based on your selections. Windows setup package: Select this option to install the automation partition using an installation setup package that runs in a Windows production environment.

the Boot Disk Creation Complete page appears. it is possible that the flash drive you are using appears in Windows as Fixed instead of Removable. so long as the client computer can connect to the Deployment Server. Rescan drives: If you attach a USB flash drive to the server. Install the Altiris Deployment Agent for Windows (Aclient): Select this option to install the Deployment Agent on client computers in the production environment after the automation partition is installed. Field Definitions Bootable ISO CD Image: Select this option to create an ISO CD boot image. click this button to set limited properties for the Deployment Agent.for a Windows PE configuration. Click the drop-down arrow to select bootable media from the list. 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. Show fixed drives: If you try to select a USB flash drive from the Bootable disk dropdown list. the partition size is 150-200 MB. You must use third party software to burn the ISO image to a CD. Preparing install environment. Automation boot disks give you greater flexibility because you can physically go to any client computer on the network and boot to automation. but you cannot find it even after clicking Rescan drives. Altiris® Deployment Solution 6. Run silent install: Select this option to install the automation partition without user input. The setup package is located at: After the automation partition installation package is created. Advanced: If you selected to install the Deployment Agent (above). Creating the FRM files.8 SP2 282 . ISO image file path: Enter the path to the folder where ISO images are stored. However. 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. Click Browse to navigate to the folder where you want the setup package stored. Inserting into the installer package. The process does the following: Copying files to production area. 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. and confirms where the installer package is located. Creating automation partition installer: This is a progress page to display the automation installation package process. you can click this button to rescan the physical drives that are attached to the server. Select this option to view all drives attached to the server. All the drives listed display the physical drive number instead of the logical drive letter. A list of available drives is updated in the drop-down list. the partition size for a DOS configuration would range is only 5-50 MB. installation packages are stored in the Deployment Share bwpkgs folder. Installer package file path: By default. but it does not appear in the Bootable disk drop-down list.

The list of available drives is updated in the dropdown list.8 SP2 283 . ISO image file path: Enter the path to the folder where ISO images are stored.Create Network Boot Disk This feature lets you create a network boot disk you can use at any client computer on the network. Windows CE . Select this option to view all drives attached to the server. or you can create a Windows uninstall package that can be distributed to a client computer through a deployment job. You have access to the network server’s system to execute and manipulate files manually.NET setup package: Select this option to remove an automation partition using an installation setup package that runs in a Windows CE . Windows setup package: Select this option to remove an automation partition using an installation setup package that runs in a Windows production environment. you can click this button to re-scan the physical drives that are attached to the server. 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. but you cannot find it even after clicking Rescan drives. You can create bootable CDs. You must use third party software to burn the ISO image to a CD. All the drives listed display the physical drive number instead of the logical drive letter. flash drives. Linux bootable disk: Select this option to remove an automation partition using a Linux bootable disk. Click the drop-down arrow to select bootable media from the list. Altiris® Deployment Solution 6. ISO image file path: Enter the path to the folder where ISO images are stored. and floppy disks to use manually at the client computers. Field Definitions DOS bootable disk: Select this option to remove an automation partition using a DOS bootable disk. Remove Automation Partition This feature lets you remove an automation partition on a client computer’s hard disk. but it does not appear in the Bootable disk drop-down list. Field Definitions Bootable ISO CD Image: Select this option to create an ISO CD boot image. Show fixed drives: If you try to select a USB flash drive from the Bootable disk dropdown list. The properties you defined when creating the New Configuration map a drive to a specified server when a client computer uses a network boot disk. You could also create a network boot disk. Rescan drives: If you attach a USB flash drive to the server. connect to a specific server where the Windows uninstall package is stored and run the executable from the client computer.NET production environment. Bootable ISO CD Image: Select this option to create an ISO CD boot image that removes an automation partition. it is possible that the flash drive you are using appears in Windows as Fixed instead of Removable.

but it does not appear in the Bootable disk drop-down list. Missing Files for Processor Types For the most part. Open the Boot Disk Creator Utility. Boot Disk Creator configurations are independent of architecture. Select this option to view all drives attached to the server. Files that do not import successfully must be recreated configurations using the New Configuration Wizard in this version of Boot Disk Creator. you can save previously created configurations by using the Import Previous Version Configuration Files dialog to convert the configuration’s format to this release. Rescan drives: If you attach a USB flash drive to the server. However. Configuration files that are successfully imported can be used to support automation and imaging on client computers. but you cannot find it even after clicking Rescan drives. if you manually add executables to a configuration which supports multiple processor types. Click the drop-down arrow to select bootable media from the list. Browse: Click to navigate to the directory path where configuration files are located. and you add an executable. If not all architectures you have Altiris® Deployment Solution 6. Example: If you have x86 and x64 versions of the Linux preboot environment selected for a configuration. All the drives listed display the physical drive number instead of the logical drive letter. it is possible that the flash drive you are using appears in Windows as Fixed instead of Removable. Field Definitions Directory: Enter a path to where the configuration files you want to convert are located. However.8 SP2 284 . Description: This is the description for the old configuration files. Show fixed drives: If you try to select a USB flash drive from the Bootable disk dropdown list. To import configuration files 1.Bootable disk: Select this option to create a boot disk that removes an automation partition from a client computer. you need to ensure you provide a version of the file for each architecture you have included. you can click this button to re-scan the physical drives that are attached to the server. Click File > Import. This is because of increased support and functionality that Boot Disk Creator now provides. The list of available drives is updated in the dropdown list. Import Configuration Files The configuration format has changed from all previous versions of Boot Disk Creator. 2. Config File Name: This is the name of the old configuration files you have selected to convert and import into this release of Boot Disk Creator. Boot Disk Creator checks the file header to see which architectures the executable supports. Note There may be some instances when older configuration files cannot be converted to the new file format.

which currently does not have a need for Linux boot images. Linux (page 286). MS-DOS (page 286) or both. You can install all supported pre-boot operating system files at the same time. You can install FreeDOS and MS-DOS. this screen appears prompting you to add additional files or ignore the warning. You can open the Install Pre-boot Operating System Files dialog at any time to install the Linux system files.frm file can be downloaded from the Altiris Solution Center Web site and saved to any location on the network. To install pre-boot operating system files Click Install next to the pre-boot operating system you want to install. click Update to install the new files.installed are supported by the file you added. All existing Windows PE files are deleted from the hard disk before the new files are installed. or of the other pre-boot operating system files. FreeDOS Deployment Solution provides FreeDOS in a file named BDCgpl. any existing operating system files are deleted before the newer files are installed. The operating system version number appears (except for MS-DOS). a checkmark next to the operating system name indicates that the files have been successfully installed. The BDCgpl. or you can select to install only those pre-boot environments you want to use. you decide you want to create Linux configurations and Linux boot images. and the Install option changes to Update. you can only run one version of DOS at a time. but you must select which DOS version you want to run since you cannot run both versions at the same time. and Altiris supports a newer version that becomes available. If you experience any problems with the new version of Windows PE. When you install the pre-boot operating system files for DOS (page 285). However. click Update to install the new files.frm file is available online through Deployment Solution Hot Fixes or Service Pack releases. Install Pre-boot Operating System Files Boot Disk Creator requires that you install the pre-boot operating system files for at least one pre-boot environment before you can create new configurations. Boot Disk Creator uses these files when creating configurations and boot images. When newer versions of FreeDOS become available. click either FreeDOS or MS-DOS to select the version you want to run as the default for creating configurations. After working with Deployment Server and Boot Disk Creator. Example: You can install the DOS and Windows PE pre-boot operating system files to start creating configurations to support your infrastructure. you must install the older version to restore Boot Disk Creator functionality for Windows PE. If you acquire a newer version of DOS. However. an updated . DOS You can install FreeDOS (page 285).frm. Example: If you installed Windows PE.8 SP2 285 . Linux or Windows PE. or Windows PE (page 286). Altiris® Deployment Solution 6. If both versions of DOS are installed.

EXE MODE.SYS EMM386. Required HIMEM. Boot Disk Creator requires the following MS-DOS files. When newer versions of Linux become available.frm file is available online through Deployment Solution Hot Fixes or Service Pack releases. Use Microsoft Windows 98 installation CD: Select to install MS-DOS from an original Microsoft Windows 98 installation CD. copy the appropriate files to a system formatted floppy disk. Windows PE Altiris supports Windows PE 2005 as a pre-boot environment for Boot Disk Creator. If you select BFloppy Drive from the drop-down list. Linux Deployment Solution provides Linux RedHat Fedora in a file named BDCgpl.frm. Boot disk creator only installs DOS files from the A drive. you are asked to supply 2 CDs: Windows PE 2005 and Windows Server 2003 SP1.EXE ATTRIB. Copy the required files listed below from an original Microsoft Windows 98 installation CD to the floppy disk. When you install Windows PE.8 SP2 286 .EXE Note The SMARTDRV.COM MEM.COM FORMAT. a folder that can be accessed from Boot Disk Creator. or use the CD directly.Note FreeDOS may not support newer motherboard chip-sets.EXE SMARTDRV. Altiris® Deployment Solution 6. Folder: Select to copy the required files to a folder that can be access from within Boot Disk Creator.COM FDISK. Floppy Disk: Select to format a disk using the Format a: /s command.COM XCOPY32.MOD Optional EDIT.frm file can be downloaded from the Altiris Solution Center Web site and saved to any location on the network.EXE SYS. an updated . Boot Disk Creator still tries to read data from the A-Floppy Drive. MS-DOS Using an original Microsoft Windows 98 installation CD.EXE file is required for all computers running a scripted install in Windows 2003\XP. The BDCgpl.

SP1) appears. Example: On the Windows PE CD page. There are two dialog pages to complete the Windows PE installation.8 SP2 287 . You first are asked to provide the Windows PE CD. the text Windows PE 2005 (Windows Server 2003. Click Exit to avoid installing the full version of Windows Server. The first operating system listed on each page is the CD you want to use. Altiris® Deployment Solution 6. the Welcome to Microsoft Windows Server* 2003 page appears after inserting the Windows Server 2003 CD. The text on the page lists the operating system CD you need to enter for each of these pages. while the Windows CD page displays Windows Server 2003SP1 (Windows PE 2005).In most instances. followed by the Windows CD.

You can still perform an Initial Deployment. Linux. If you select Deployment Solution Simple Install and Install PXE Server.ini file for each PXE Server on the network. By default.ini file when you click Save. However. you can select which properties you want to set. When you select a specific PXE Server from the File menu. Then. PXE Configuration always starts in the Use Shared properties mode. but now you can select DOS. regardless of the PXE install options you select. If you select Custom Install and Install PXE Server.ini file. The boot menu options you create appear as a menu list on client computers when a PXE boot operation is performed. Previous users of Altiris PXE Server notice that Initial Deployment and ManagedPC are no longer boot menu options. the changes you make to the properties settings are saved to the PXE Manager. they both install to the same server. PXE Manager creates and distributes the appropriate PXE. Shared or Local boot menu options When you start the PXE Configuration Utility. See PXE Manager (page 309). 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. PXE Manager also gathers data from all PXE Servers and stores the information in the PXE Manager. It keeps track of all PXE Server boot menu options. PXE Manager PXE Manager is a service that synchronizes Deployment Server and all PXE Servers installed and configured across the network. See the Deployment Solution Product Guide. PXE Manager always installs on the Deployment Server. The Use Shared properties option lets you create Shared boot menu options that can be used by all PXE Servers on the network. you can select the Customize PXE Server (Shared Configuration) option that lets you change any of the shared properties for that specific server. when you close the PXE Configuration Utility. which allows administrators greater flexibility when performing the following tasks: Creating boot menu options Installing BIS Certificates Creating boot disks. Whether you are in Use Shared properties or select a server to Customize PXE Server (Shared Configuration).PXE Configuration Utility Altiris PXE Configuration Utility integrates with Altiris Deployment Solution and lets you manage all PXE Servers across the network. and whether they are Shared or Local. You can set the order of the boot menu options and select which menu option you want as the default. PXE Configuration has been completely rewritten to give you more capability in working with Deployment Server. you can choose to install them to separate servers. See Boot Menu Tab (page 290). or Microsoft Windows Preinstallation Environment (Windows PE) as the pre-boot automation Altiris® Deployment Solution 6.8 SP2 288 .

the client computer boots to automation and performs the deployment jobs that have been assigned. there is a boot image stored on the Altiris PXE Server. click the PXE Configuration icon on the toolbar. the Summary page displays the MenuOption<number>. so you always know which boot menu option you are working with. Example: if a deployment job contains the task Create Disk Image.Broadcom. When a client computer performs a PXE boot. the Deployment Agent verifies if there is work to complete. which is for more advanced users. and the Automation . BIS Tab (page 310). the pre-boot operating system selected at install time is set for Initial Deployment. the Local Boot menu option is automatically selected.environment. a menu list appears for users to select a boot menu option. it uses DOS .8 SP2 289 . edit. For each boot menu option created. The tasks the can run in automation are: Run script Create Disk Image Distribute Disk Image Scripted OS Install Backup Registry Restore Registry. If so. When client computers perform a PXE boot. See New Shared Menu Option (page 292). Boot Disk Creator and PXE Configuration Boot Disk Creator is now integrated with the PXE Configuration Utility. yet each task executes in the automation environment you want. Remote PXE Installation (page 311). so that you can keep track of the boot menu options you create. A boot image consists of a file or set of files. importing Direct from floppy. See Boot Menu Tab (page 290) and Edit Shared Menu Option (page 293). By default. See DS Tab (page 306). when the client computer executes the task. Additional tasks within the same job can be assigned a different boot menu option. To open PXE Configuration Option 1: From the Deployment Console. MAC Filter Tab (page 307). Data Logs Tab (page 310).Broadband as the automation environment. You can also click Tools > PXE Configuration. Multicast Tab (page 308). Altiris PXE Server provides three different methods of creating boot menu options: the New Configuration Wizard from Boot Disk Creator. When you select a boot menu option to edit or delete using the Boot Disk Creator method. Option 2: Altiris® Deployment Solution 6. PXE Server Tab (page 304). See also: Boot Menu Tab (page 290). Automation Tasks Only Shared boot menu options can be assigned to a task in a deployment job. The Altiris PXE Server downloads the boot image that corresponds with the boot menu option that the user selects. DS Tab (page 306).PXE or Bootworks environment (DOS/Windows PE/Linux) field is assigned to DOS . See the Deployment Solution Product Guide. and User supplied. and delete. If there are no deployment jobs for the client computer.

Boot Menu Option for PXE Server: (Shared Configuration) appears at the top of the page and above the list of configurations. The Create Disk Image dialog opens. set the boot menu order. which could be either Shared Configuration or Custom PXE Server mode. edit. Double-click a task in the job. To delete an item. append the server name to the prompt. and you can delete the boot menu item. PXE Configuration Utility opens to the last saved action. you have to disable the boot menu item from the DS job. and delete boot menu options. Click Start > Programs > Altiris > PXE Services > PXE Configuration Utility. define the prompt for users. The operating system field is the same as in the Shared mode. After the boot menu item is disabled. 2. If a PXE boot menu item is used by the job. The operating system field indicates the type of pre-boot operating system files used to create the boot menu option. View Area When you are in Shared Configuration mode. You can delete an item only when it is not in use by the Deployment Server.8 SP2 290 . By default. depending on whether you select Use Shared properties or Customize PXE Server. 2. so the Scope is always Shared. The Scope field displays both Shared and any new boot menu options you create displays Local. only configurations you create for all Altiris PXE Servers appear in the view area. The following colors are used to denote which automation operating system is used by each configuration: Blue: DOS configuration Green: Linux configuration Red: Windows PE configuration Note: When an item is in use by the Deployment Server. In the In use by DS field Yes does not appear. If you select an Altiris PXE Server from the File menu. You can perform the steps given above to view if the other boot menu items are used by the other jobs. Click the Automation pre-boot environment (DOS/Windows PE/Linux) dropdown list. When you are in Customize PXE Server <server Altiris® Deployment Solution 6. Boot Menu Option for PXE Server: (name of Server) appears. When you select a specific server (Local) from the File menu. it appears in the drop-down list. a window displays the boot menu option for the selected Altiris PXE Server. PXE boot menu options can be either local or shared. When you manage all PXE Servers (Shared) across the network.1. If an existing DS job uses a boot menu item. To identify the boot menu items used in the jobs 1. Boot Menu Tab This lets you create. you cannot delete the item from the PXE Configuration Utility. and set the user’s time-out response when the boot menu list appears on client computers. Example: Create Disk Image. restart the PXE Config Utility. Click each tab to set the category in the PXE Server properties. This helps you identify which mode you are working in. Yes appears in the In use by DS field. The boot menu options listed are for all Altiris PXE Servers.

See New Shared Menu Option (page 292). You can change the text message but not the <F8> command. the default boot option runs. Altiris® Deployment Solution 6. New: Click to open a dialog to add a new boot menu option.PXE or Bootworks environment (DOS/Windows PE/ Linux) field before you delete the boot menu option. When you change back to Customize PXE Server <server name> mode. You cannot change this selection on the other pages if you are setting the properties for the Shared Configuration. Scope: Shared indicates that the configuration is available on multiple Altiris PXE Servers in an environment where they are all serviced by a single Deployment Server. You can create a Local configuration named DOS Clients since there are no other configurations with the same name. Up and Down: Select to order boot options. You can keep the settings on the page or customize the properties for the Altiris PXE Server you selected. Boot Menu Properties Use Shared properties: You can select this option to set the properties for a Shared Configuration. This helps users know which Altiris PXE Server is servicing their client computer. you can view both Shared and Local configuration. Go to the Deployment Console. Time-out: This is the length of time the prompt appears before the boot process starts. Append server name: Select this option to have the Altiris PXE Server name listed following the prompt on client computers when the boot menu list appears. as it is still required to perform a PXE boot option. both DOS Clients configurations appear in the view area. Prompt: This is the user prompt for the PXE boot menu list when it appears on client computers. The top boot option is the default that runs automatically if no other option is selected from the Altiris PXE Server menu. When client computers perform a PXE boot. and delete the task or change the Automation .8 SP2 291 . open the appropriate deployment job. both Shared and Local configurations appear. Boot Menu Options for PXE Server: <Shared Configuration> Name: This is the name of the PXE item that appears on client computers after a PXE boot operation is performed. Example: if you are in Customize PXE Server <server name> mode. See Edit Shared Menu Option (page 293).name> mode. You cannot create a configuration named the same as any other configuration in the view area. Now. Delete: Select a boot menu option from the list and click Delete. regardless of the mode you are in. Edit: Click to modify properties for boot menu options. both configurations appear and user’s cannot know which boot menu option to select. If the user does not press the <F8> key within the time-out period. OS: The operating system that the configuration uses to boot on client computers. Local indicates the configuration was created for a specific Altiris PXE Server. change to Shared Configuration mode and create a configuration named DOS Clients because the Local configuration of the same name does not appear in the view area. You cannot delete boot menu options if they are assigned to a task within a deployment job. Customize PXE Server (Shared Configuration): This option is available when you select a specific server from the File menu. See Redirect Shared Boot Menu Option (page 293).

Pre-boot Image Properties: Select the operating system and processor type for the configuration you are creating and select the method you want to use to create the configuration. User supplied: This is for advanced users. The MenuOption number increments each time you create a new configuration. Any configurations you create or edit using this method are for PXE boot menu items only. Create Boot Image: You must enter a descriptive name for the PXE configuration in the Name field before this option is enabled. See Install Pre-boot Operating System Files (page 294). See Import Boot Menu Options (page 294). the Up 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. Direct from floppy: Select this option if you want the Altiris PXE Server to read a configuration file from a floppy. are meant for the Altiris PXE Servers and the client computers that use PXE as their primary boot option. New Configuration Wizard (page 296). New Shared Menu Option The PXE Configuration Utility lets you create up to 23 boot menu options that can be selected from client computers. The Location field shows the path where the new configuration is stored. all the configurations you create from this dialog. See Import Boot Menu Options (page 294). When a PXE-enabled client computer makes a request to an Altiris PXE Server.ini file. The Install Pre-boot Operating System Files dialog appears before the New Configuration Wizard starts if you need to install the Altiris® Deployment Solution 6. The folder MenuOption<Number> is created as a subfolder of MasterImages. However. so that it becomes the default boot option on client computers. Menu Item Properties Name: This is the name of the PXE configuration that appears as a boot item when the PXE menu downloads to client computers after a PXE boot operation is performed. When you close the PXE Configuration Utility. Image creation method Boot Disk Creator: This lets you start the New Configuration Wizard from Boot Disk Creator. Final Location on PXE Server: This field can help you identify which PXE item you are configuring. but no configuration files are stored there until advanced users add the configuration files manually. 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. If an operating system has an asterisk next to it. This dialog also integrates with Boot Disk Creator as it lets you create new automation configurations from within the PXE Configuration Utility. the Altiris PXE Server downloads a boot menu list for users to select a boot option. If you select this option. You can view the status of these updates on the Status tab. PXE Manager creates and sends PXE.ini files to each Altiris PXE Server on the network. the pre-boot operating system files must be installed before Boot Disk Creator starts the New Configuration Wizard.Save: Click to save all changes you made to the PXE Manager. Allow as default PXE boot option: Select this option to move the configuration you are creating to the top of the boot menu. PXE configurations are stored in the default directory of C:\Program Files\Altiris\eXpress\Deployment Server\PXE\Images\MenuOption<number>.8 SP2 292 . If you do not select this option. you must select Other in the Operating System area.

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. See Redirect Shared Boot Menu Option (page 293). However. which gives you greater flexibility in managing all deployment jobs.8 SP2 293 .) Click on a Shared configuration. or click Edit on the Edit Configuration page until you find the options you want to change. However. Click the drop-down arrow and select a Local configuration from the list.pre-boot operating system files. the Deployment Agent receives a message that it must boot to automation. Example: your main office is in Utah and there are 2 satellite offices. but the Redirect option is enabled when you select a Shared boot menu option. right-click the MenuOption<number> and select Edit Configuration. From the PXE Configuration Utility. and click Edit. one in Los Angeles and the other in New York. The Edit option is enabled when you select any of the Shared boot menu options. (This is the Customize PXE Server <server name> mode. Altiris® Deployment Solution 6. When the Deployment Server sends the job to client computers. 3. can point to a Local configuration so that when client computers are booting to automation. only Shared configurations appear in the list. Client computers that are PXEenabled find the nearest Altiris PXE Server and receive the boot image files needed to boot to automation.PXE or Bootworks environment (DOS/Windows PE/ Linux) configuration from the drop-down list when setting up imaging jobs. The Edit Configuration page from the New Configuration Wizard only displays the MenuOption<number> you selected from the Boot Menu page. the Shared configuration selected for the automation task within the deployment job. Deployment Server lets you select the Automation . 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. if you are in Customize PXE Server: <server name> mode the Edit option is enabled when you select any Local boot menu options. click Edit Boot Image. To make changes. 4. only Shared configuration appears in the view area of on the Boot Menu tab. Edit Shared Menu Option When you are in Shared Configuration mode. and click Redirect. Select a PXE Server. 2. If you selected Boot Disk Creator as the Image Creation Method. To edit Shared or Local boot menu options Select a boot menu option from the view area on the Boot Menu page. See also: Edit Configurations (page 302) and Boot Menu Tab (page 290). click File. When Redirect is used. See Install Pre-boot Operating System Files (page 294) and New Configuration Wizard (page 296). To redirect a Shared boot menu option 1. the Local configuration is used to access local network servers and images.

5. Click OK. 4. Import Boot Menu Options This option lets you import boot menu options that were created using Third Party imaging software. From the New Shared Menu Option dialog. a checkmark next to the operating system name indicates that the files have been successfully installed. You can install all supported pre-boot operating system files at the same time. 3. select User Supplied. Linux (page 296). The path and name of the new MenuOption<number> appears. 3. Option 2: 1. A progress bar displays the PXE boot file image being read as it is imported. You can open the Install Pre-boot Operating System Files dialog any time to install the Linux system files. Copy the PXE files you want in the MenuOption<number> folder. which currently does not have a need for Linux boot images. The Shared configuration displays the redirected configuration in the list. When you install the pre-boot operating system files for DOS (page 295). you decide you want to create Linux configurations and Linux boot images. or previous versions of Altiris PXE Server. or of the other pre-boot operating system files. Boot Disk Creator uses these files when creating configurations and boot images. From the New Shared Menu Option dialog.8 SP2 294 . Example: you can install the DOS and Windows PE pre-boot operating system files to start creating configurations to support your infrastructure. but you must select which DOS version you want to run since you cannot run both versions at the same time. Install Pre-boot Operating System Files Boot Disk Creator requires that you install the pre-boot operating system files for at least one pre-boot environment before you can create new configurations. After working with Deployment Server and Boot Disk Creator. Click Finish. select Direct from floppy and click Import Boot Image. or you can select to install only those pre-boot environments you want to use. and the Install option changes to Update. You can install FreeDOS and MS-DOS. If you make updates to the core automation operating system. this lets you apply those updates without re-creating the affected configurations. 2. such as installing a new version of Linux. The operating system version number appears (except for MS-DOS). Click Next. Altiris® Deployment Solution 6. or Windows PE (page 296). Option 1: 1. 2. Insert a floppy disk. Regenerate Boot Images This lets you regenerate all PXE configurations which are using the selected operating system. Click OK.

click Update to install the new files. click New. click Update to install the new files. Boot disk creator only installs DOS files from the A drive.8 SP2 295 . If you experience any problems with the new version of Windows PE. FreeDOS Deployment Solution provides FreeDOS in a file named BDCgpl. If you select BFloppy Drive from the drop-down list. use the regenerate Boot Images option on the Boot Menu to apply the new version to your existing configurations.If you acquire a newer version of DOS. MS-DOS (page 295) or both. To install pre-boot operating system files 1. DOS You can install FreeDOS (page 295). Use Microsoft Windows 98 installation CD: Select to install MS-DOS from an original Microsoft Windows 98 installation CD. and Altiris supports a newer version that is available. Linux or Windows PE. When newer versions of FreeDOS become available. or use the CD directly. click either FreeDOS or MS-DOS to select the version you want to run as the default for creating configurations. you must install the older version to restore Boot Disk Creator functionality for Windows PE. any existing operating system files are deleted before the newer files are installed. Example: if you installed Windows PE. However. All existing Windows PE files are deleted from the hard disk before the new files are installed. However.FRM file is available online through Deployment Solution Hot Fixes or Service Pack releases. When you install a new version. use the regenerate Boot Images option on the Boot Menu to apply the new version to your existing configurations. Folder: Select to copy the required files to a folder that can be access from within Boot Disk Creator.frm file can be downloaded from the Deployment Solution download site on altiris. MS-DOS Using an original Microsoft Windows 98 installation CD. copy the appropriate files to a system formatted floppy disk. When you install a new version. Altiris® Deployment Solution 6.frm. 2. From the Boot Menu tab. Copy the required files listed below from an original Microsoft Windows 98 installation CD to the floppy disk. The BDCgpl. a folder that can be accessed from Boot Disk Creator. an updated . Note: FreeDOS may not support newer motherboard chip-sets. Boot Disk Creator still tries to read data from the A-Floppy Drive. If both versions of DOS are installed. Floppy Disk: Select to format a disk using the Format a: /s command.com and saved to any location on the network. Click Add pre-boot and follow the prompts. you can only run one version of DOS at a time.

Example: on the Windows PE CD page. New Configuration Wizard You can create as many configurations as needed to support varying types of computer environments.com and saved to any location on the network. Altiris® Deployment Solution 6.frm file can be downloaded from the Deployment Solution download site on altiris. you are asked to supply 2 CDs: Windows PE 2005 and Windows Server 2003 SP1. When you install Windows PE. an updated .COM MEM.EXE SYS. followed by the Windows CD. In most instances. When newer versions of Linux become available. When you install a new version.COM FDISK.frm. use the regenerate Boot Images option on the Boot Menu to apply the new version to your existing configurations.EXE SMARTDRV. Click Exit to avoid installing the full version of Windows Server.EXE ATTRIB. you must install the pre-boot operating system files that Boot Disk Creator uses to create new configurations. Required HIMEM. There are two dialog pages to complete the Windows PE installation.EXE MODE. Before you begin. The first operating system listed on each page is the CD you want to use. You are first asked to provide the Windows PE CD. When you install a new version.MOD Optional EDIT.EXE file is required for all computers running a scripted install in Windows 2003\XP.SP1) appears.COM XCOPY32.EXE Important: The SMARTDRV. See Install Pre-boot Operating System Files (page 294). while on the Windows CD page Windows Server 2003-SP1 (Windows PE 2005) appears. the Welcome to Microsoft® Windows® Server 2003 page appears after inserting the Windows Server 2003 CD. The BDCgpl. use the regenerate Boot Images option on the Boot Menu to apply the new version to your existing configurations. the text Windows PE 2005 (Windows Server 2003.frm file is 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.COM FORMAT. The text on the page lists the operating system CD you need to enter for each of these pages.Boot Disk Creator requires the following MS-DOS files. Linux Deployment Solution provides Linux RedHat Fedora in a file named BDCgpl.8 SP2 296 .SYS EMM386.

Linux. if you use IPX to communicate with a Microsoft server. if you select the configuration from the treeview.To start the New Configuration Wizard. (Example: enter the type of computer. and data files. or click File > New Configuration. Configuration Name This is the first page of the New Configuration Wizard. Description: Enter a description for the configuration. Create multi-network adapter configuration: Select this option to add multiple network adapter drivers to a single PXE boot file configuration. which is the same for DOS. The description field is optional but helps you to know what the configuration contains. Novell NetWare (VLM): Select this option to store images on a NetWare server with VLM clients. However. You must enter a name for the configuration to make the Pre-boot Operating System for this Configuration fields active. and Windows PE operating systems to create pre-boot environments. File Server Type (DOS) The Deployment Share stores image files. NIC drivers. select the IPX check box at the bottom of the page. Field Definitions Name: The configuration name you enter appears in the Configurations pane after the wizard is completed. See Multi-Network Adapter Configurations (page 298). the Deployment Share is installed to the Deployment Server. packages. using IPX network communications. This feature lets you build configuration files to boot multiple computers that contain different types of network adapter cards. the description you entered for this field appears at the top of the right pane. Field Definitions Microsoft Windows: Select this option to store images on a Microsoft server using TCP/IP network communications (recommended). Use IPX to communicate with Netware: Select this check box if IPX is the network protocol for the Novel NetWare (Client32) server. Altiris® Deployment Solution 6. Select the pre-boot operating system and click Install Pre-boot Operating System Files (page 294) to install pre-boot operating system files. and any additional files you want to add. Pre-boot Operating System for this Configuration: Boot Disk Creator supports DOS. By default. Linux. Novell NetWare (Client32): Select this option to store images on a NetWare server with 32-bit clients. and any other characteristics that can help you identify this particular configuration.8 SP2 297 . such as the file server type. network adapter. or Windows PE. click Ctrl+N.) After the Create Configuration and Create Boot Disk wizards complete. depending on whether you selected a Simple or Custom Deployment Solution installation. click the icon on the toolbar of the Boot Disk Creator tool. but it can be on another server. operating system.

or network or automation boot disks. CD. See Advanced (page 299). a list of supported drivers appears. The Advanced (page 299) button lets you further define network adapters and their drivers. Boot Disk Creator applies the driver that matches the first network adapter card that it detects. After a client computer boots using a multi-network adapter configuration. If you want to add or change adapter settings (such as I/O Memory. Example: if you are going to use the multi-network adapter configuration for several different client computers. or Windows PE so that client computers can connect to a network or Deployment Server. the first NIC card is detected and can potentially be the wrong network adapter required to connect to the Deployment Server. See Also: Network Adapter (page 298) Network Adapter The drivers listed in the Network Adapters window vary depending on the type of configuration you are creating. See Install Pre-boot Operating System Files (page 294). Multiple Network Adapters Load Order This option is for DOS and Windows PE configurations only. and are automatically added to the new configuration. You can select Multi-NIC drivers to be included in the configuration by pressing Shift-Click or Ctrl-Click. If you select Auto-detect network adapter. The Have Disk (page 299) button lets you install network adapter drivers from a disk.Multi-Network Adapter Configurations If you are creating a DOS configuration. or network folder. or Advanced (if they are available for the type of configuration you are Altiris® Deployment Solution 6. depending on whether you create automation partitions. Internet. Windows PE determines which network adapter driver to use. Select a driver from the network adapters driver list. The Internet (page 299) button lets you connects to an Altiris supported Web site to download and install network adapter drivers. IRQ. when you select Multi-NIC configurations. See Multi-Network Adapter Configurations (page 298). the Windows NIC drivers that are available to create a Windows PE configuration appear. You can install pre-boot operating system files for DOS. If the network adapter you want does not appear in the list. if a client computer has 2 NIC cards and you use the multinetwork adapter configuration to boot the computer. Advanced Features The network adapters you select must support DOS. Example: if most client computers have a Broadcom Ethernet adapter. this option can save you time and effort in booting different computers. but some computers have a 3Com10/100 LAN PC Card Fast Ethernet card. This lets you specify which order the physical network adapters will be detected when the client computer boots. Linux. Example: after installing the pre-boot operating system files for Windows PE. You must create a new configuration for each type of network adapter that is installed on client computers. or Windows Preinstallation Environment (Windows PE). unless you want to create a Multi-NIC configuration. However. Linux. and PCMCIA for DOS configurations) click Advanced. you can use Up and Down to move the Broadcom Ethernet adapter to the top of the list. you can click Have Disk.8 SP2 298 .

Network adapters can be downloaded from the manufacturer’s Web site and saved to a folder or a disk to be installed later. Have Disk You can add network adapter drivers by using any disk media or navigating to a folder.sys): Append memory address information to this line in the config.ini): Add parameters to the network setup section of the protocol. If you are creating a Linux or Windows PE configuration. this option is not available. Memory (protocol.cfg file. See Have Disk (page 299).sys): Append memory address information to this line in the config. From the Network Adapter page. Novell VLM clients Emm386 memory (config.sys file.sys): Append memory address information to this line in the config. Microsoft clients EMM386 Memory (config. Internet Altiris supports many manufacturer network adapters and supports a Web site for you to download the latest NIC drivers. New network adapters come with a floppy disk or CD to install the appropriate drivers.altiris.creating) to add additional drivers. click Internet to launch the Web browser and connect to ftp://support.ini file. Advanced settings (protocol.ini): Add parameters to the NIC section of the protocol. click Advanced.com/support/NIC_drivers/. Advanced This options lets you add or change settings for network adapter cards so they work correctly when using DOS configurations. Refer to the following properties and values. Altiris® Deployment Solution 6. From the Network Adapter page.ini file. IRQ (protocol.sys): Add parameters to the NIC section of the net. Download the driver you want and unzip the files it to a folder on the hard drive. Internet (page 299). Advanced (page 299).sys file.ini): Add parameters to the network setup section of the protocol. Field Definitions Auto-detect network adapter: Select this option to have Windows PE auto-detect the type of adapter that is in a client computers when the boot image runs. Novell Client 32 Emm386 Memory (config. Click Add Driver and the driver you downloaded is added to the Network Adapters list.ini file. Advanced settings (config.8 SP2 299 .sys file.

using this configuration. TCP/IP Protocol Settings This page lets you set up TCP/IP protocol settings for boot configurations. 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. Use TCP/IP multicasting to find the Altiris Deployment Server: Select this option to use TCP/IP multicasting to find the Deployment Server. Multicast IP address: Enter a multicast IP address for client computers to send a broadcast packet across the network to find the Deployment Server. To set the TCP port on the Deployment Server 1. you can ignore this page by clicking Next.bat file. You can also enter a primary and secondary WINS address if you need to resolve IP addresses and naming conventions. as none of the properties are used to create a network boot image. This would result in client computers not being able to communicate with the Deployment Server. Enter the TCP port number. When client computers boot to automation using this configuration. Subnet mask. 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. click Start > Control Panel > Deployment Solution Configuration applet > Options > Transport tab. The Deployment Server IP address. TCP/IP is the default protocol when client computers boot to automation on a Windows network. Click OK. Altiris® Deployment Solution 6. and Port fields are critical because they define how client computers establish communications with the Deployment Server. Use a static IP address: Select this option if you want a client computer. If you are using the IPX protocol. so that the IP address is not the same for all computers. because the port numbers do not match. 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. This option also requires that you create a configuration for each client computer. If you intend to create a network boot disk. 2. To establish communications between client computers and the Deployment Server. change the Port field in the Boot Disk configuration to 402. Deployment Server uses its own IP stack to work on IPX networks. and default gateway. a multicast packet broadcasts across the network to find where the Deployment Server is located. 3. From the Deployment Server. Altiris Deployment Server Communication This option lets you set communication properties for the Deployment Server.Advanced settings (driver command line): Add driver command-line entries to the landrv. Enter an IP address.8 SP2 300 . to be assigned a specific IP address.

You can create multiple drive mappings or mount points. a multicast packet broadcasts to the server you specify. which manages the Deployment Database. NetWare Server name: Enter the server name for the Deployment Share or file server. Server name: When you select Use TCP/IP multicasting to find the Altiris Deployment Server. User name: Enter the authorized user name that was set up when the Deployment Share directory was created. Network Configuration This option lets you define how client computers connect to the Deployment Share or a file server where image files are stored.2. they connect to the appropriate server. You must select this option if your network adapter or network does not support multicasting. if you are creating a DOS configuration. However. Use TCP/IP to connect to the Altiris Deployment Server: Select this option to connect to a specific Deployment Server. the client computer connects to any server responding to the multicast packet. 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. Port: This option defines which port client computers will use to communicate with the Deployment Server Engine.8 SP2 301 . which manages the Deployment Database. sends job commands to the Deployment Agent. the IP address is required.Port: This option defines which port client computers use to communicate with the Deployment Server Engine. If you leave this field blank. See your network adapter documentation or call the manufacturer or consult with your IT department for information. and more. leave this and the Password fields blank. If you are using the Intel Universal NIC driver (UNDI). and more. If you did not assign a User name and Password when the Deployment Share or file server was created. Click Advanced to enter a NetWare context for the server and select a Frame type if it is different from the default value of 802. Server IP address: Enter the IP address of the Deployment Server to access information stored in the Deployment Share. sends job commands to the Deployment Agent. the first mapped drive you specify must connect to the Deployment Share. Confirm password: Enter the password for the user name as confirmation that you entered the proper password in the Password field. Altiris® Deployment Solution 6. Window Workgroup: Enter the workgroup for the Deployment Share or file server. Password: Enter the password for the user name.

The colors displayed are: Blue: The configuration you selected or created is based on the DOS pre-boot environment. If you find a setting mis-entered or not what you want. Example: Windows users: \server\share NetWare users: server\volume:directory Linux users: //server/mount point 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. Drive: By default. 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.8 SP2 302 . Altiris® Deployment Solution 6. the mapped drive that appears is F: \<Deployment Share server>\eXpress. The path you enter maps to the drive letter you selected in the Drive field. Red: The configuration you selected or created is based on the Windows PE preboot environment.bat file when client computers boot to automation. The display color changes to help you know the type of configuration you selected to view. Green: The configuration you selected or created is based on the Linux pre-boot environment. or delete. click Back to re-select the option. As you select files and folders from the left pane. Path: Enter the path for the Deployment Share.Field Definitions Manually create drive mapping: Select this option if you want the drive mappings to be included in the autoexec. edit. See Edit Configurations (page 302). Configuration Summary This page lets you review all the options you selected throughout the New Configuration Wizard. If you are using Boot Disk Creator from within the PXE Configuration Utility. Use NetWare login scripts to create drive mappings: Select this option if you use NetWare and you want login scripts to create the drive mappings. Click the drop-down arrow and select a different drive letter if F: is already in use. Edit Configurations This is the main Boot Disk Creator page that appears when you start the utility. This feature lets you modify configurations that have already been created. the Create Boot Disk Wizard automatically appears for the next process to begin. this page appears at the end of the New Configuration Wizard. If you are using Boot Disk Creator from within the PXE Configuration Utility. Enter a Server name and IP address so that client computers can find the Deployment Share where image files are stored. the Edit Configuration page appears. When you click Finish. the configuration information appears in the right pane.

yet the specific configuration file is the one that is written to the boot image. unmapdrv.local WinPE . The folders that appear are as follows: DOS additional files Linux additional files WinPE additional files Boot Disk Creator copies the files from the <OS> additional files folders to all corresponding operating system configurations and are added to the boot images.bat. after you edit a configuration. you can add tracert. Example: using the Windows Copy and Paste command. If a file in the <OS> additional files folder is the same name as a file in a specific configuration folder. These folders are considered global. the result is not as you expected. press F5 to refresh Boot Disk Creator. right-click a configuration folder and select Edit Configuration and click Edit until you find the page for the options you want to change. when the files are written to a boot image. The PXE Server is updated in the background.mapdrv. go to the PXE Status Screen tab. Altiris® Deployment Solution 6. Boot Disk Creator rewrites certain files within the configuration so that drive mappings and mount points are always updated. the file in the configuration folder overwrites the file in the DOS additional files folder. You can also make text edits to files (selected from the treeview) in the right pane.bat The edited configuration settings are saved to the PXE Manager database. However. Add files to all configuration When you install a pre-boot operating system. Install Pre-boot Operating System Files (page 294) Additional Files Boot Disk Creator lets you add additional files to folders that either apply to a specific configuration or to all configurations that are of the same type of pre-boot operating system. This may cause unexpected results. If you install pre-boot operating system files and the <OS> additional files folders do not appear.8 SP2 303 .mounts.bat Linux . Each WinPE configuration you create adds the files in the WinPE additional files folder to the boot image. no updates are made to the Altiris PXE Server. If PXE Config is launched and exited without any changes. a new folder is added to the bottom of the left pane on the main page of Boot Disk Creator. any files you add to the global <OS> additional files folders are written to the boot image before the specific configuration files.To change the configuration settings.mapdrv. However. All other configuration files can be edited as needed. To view the updated status of the Altiris PXE Server. See also: New Configuration Wizard (page 296). it is overwritten. The following files are rewritten after editing configurations: DOS . If you edit text files in a <OS> additional files folder.exe to the WinPE additional files folder. since they can affect configurations of the same type. 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.

Create PXE Boot Image Files (PXE) This option is for Boot Disk Creator configurations created from within the PXE Configuration Utility. 3. Click Back to change the new configuration settings for the boot menu option. PXE Server Tab This lets you set response times for the Altiris PXE Servers and specifies how the DHCP Server will be discovered. Right-click on a configuration and select File > Text file. Right-click a configuration in the left pane and select New > Folder. By default. Network PXE image: The configuration you created does not contain an automation agent. (This option is not available in Shared Configuration mode. Boot Disk Creator must know what type of image file to create. When you click Finish. A new empty text file is added to the left pane. Altiris PXE Server properties PXE Server IP address: By default. Field Definitions Automation PXE image: The automation agent for the type of pre-boot operating system configuration you created is added to the settings you selected throughout the New Configuration Wizard. for some reason.) Force 2.Add files to a specific configuration If you want to add files to a specific configuration only. Altiris PXE Servers inherit the shared properties from the Shared Configurations mode. Right-click a configuration and select Add File. When client computers boot with this image file. Enter a name for the folder so that you know they are added files. 2. PXE Boot Image Creation Complete This page lets you know when the PXE boot image file is completed. Enter a name for the file and write text as needed in the left pane. Altiris® Deployment Solution 6. do one of the following methods: Copy files from a network folder and Paste them into the configuration folder. you need to change the IP address on a PXE Server. If. Because Altiris PXE Servers download boot image files to client computers. the IP address for both Shared Configuration and Customize PXE Server modes are already entered. do the following: 1. enter the same IP address in this field. after you select all the properties for a New Configuration. To add files to the <OS> additional files folder. and do not want to use the global feature of the <OS> additional files folders.88 MB PXE image: Select this option to increase the size of PXE boot images. the boot menu option appears in the Boot Menu tab. Client computers use the information defined on this page to locate the Altiris PXE Server that provides their services. A new subfolder is created in the left pane. A browser dialog appears to navigate to the file you want to add.8 SP2 304 . they map to a network server and be at a user’s prompt.

8 SP2 305 . the Altiris PXE Server sets option 60. Enable Automation Only: This lets you send a selected PXE boot image to the managed computer that has a job actively assigned. Select the No DHCP Server installed on PXE Server (Use DHCP port) instead. the second Altiris PXE Server would respond to client computers before the first server. You cannot change this selection on the other pages if you are setting properties for the Shared Configuration. If all 1000 computers are restarted. Response Time: This lets you set the Altiris PXE Server response time for when client computers request a PXE boot. PXE Server image update: This lets you control options for how updated PXE boot images are distributed to your Altiris PXE servers. Altiris® Deployment Solution 6. Scenario: There are 1000 computers known to Deployment Solution as managed computers and only one of those computers has an active job assigned. This helps control which Altiris PXE Servers will respond to client computers when they perform a PXE boot. No DHCP Server installed on PXE Server (Use DHCP port): Select this option if DHCP is installed to a different server than the one where Altiris PXE Server is installed.Enter the IP address for the specific Altiris PXE Server you selected from the File menu. In this example. You can do this by selecting the Only managed computers with active assignments will be processed check box. DHCP Server discovery: Auto detect Microsoft DHCP Server and configure for PXE: Select this option for an Altiris PXE Server to auto detect the ports used for DHCP when Deployment Server and the Altiris PXE Server are installed to the same server. 999 computers are not given any PXE boot instructions from the Altiris PXE Server. You can keep the settings on the page or customize the properties for the Altiris PXE Server you selected. Only that specific MAC address PXE booting client is processed. the second to Immediate response. you can set the first Altiris PXE Server to Short delayed response (1/2 second). but might result in your images taking longer to update. Note: If Microsoft DHCP Server is installed on the Altiris PXE server. They are ignored and the one computer that has a job actively assigned is sent the selected PXE boot image. Use Shared properties: This is selected when you are setting the properties for a Shared Configuration. but is not active and non-functioning. This can cause conflict with client computers. the IP address helps them communicate with the Altiris PXE Server. When client computers perform a PXE boot. Customize PXE Server (Shared Configuration): This option is available when you select a specific Server from the File menu. The Altiris PXE Server uses only one port for DHCP. Enable checkpoint restart enables the Altiris PXE server to resume a transfer if connectivity is lost. Third party DHCP Server installed on PXE server (Do NOT use DHCP port): Select this option if you are not using a version of Microsoft DHCP Server. Deployment Solution relays this information to the Altiris PXE Server. Example: if you have three Altiris PXE Servers. and the third to a Delayed response of your choice. and Deployment Solution has reported to the Altiris PXE Server that a specific MAC address (a selected managed computer) should be put into Automation mode with a specific PXE Menu Option image. Limit bandwidth throttles the amount of network bandwidth consumed by the transfer. If this check box is selected.

To establish communication between the two servers.8 SP2 306 . If no boot menu items were created. Click OK. Enter the TCP port number. because the Deployment Server IP address can change. change the Engine port field on the Altiris PXE Server to 402. scripted OS installs. To set the TCP port on the Deployment Server 1. Altiris PXE Servers and the Deployment Server work together to perform tasks. The Altiris PXE Server must access the Deployment Server and the Deployment Database to retrieve the information required to carry out these tasks on client computers. even if the boot option is not at the top of the list on the Boot Menu Options for PXE Server: (Shared Configuration) page. you have the option to edit this field. Disable Initial Deployment: By default. From the Deployment Console. Default boot option: This is the default boot menu item that Deployment Server uses to execute jobs. and more. such as creating and distributing an image. the default boot option you select for Initial Deployment moves to the top of the boot menu. which manages the Deployment Database. in the Initial Deployment Advanced properties. This would result in the Altiris PXE Server not communicating with the Deployment Server because the port numbers do not match. However. this option is enabled. Data Manager port: This is the port that PXE Manager uses to communicate with the Deployment Server. This value is automatically entered when Deployment Solution is installed. click Start > Control Panel > Deployment Solution Configuration applet > Options > Transport tab. there is a default time-out value Altiris® Deployment Solution 6. sends job commands to the Deployment Agent. The Deployment Server IP address. Example: the TCP port on the Deployment Server is set to 402 and the Engine port on the Altiris PXE Server is set to 502. Engine port: This option defines which port the Altiris PXE Servers use to communicate with the Deployment Server Engine. Execute immediately: Select this option for Initial Deployment to run on new client computers without any user interaction following a PXE boot. Clear the check box if you do not want to use Initial Deployment. the first boot menu item (shared) is selected. and the Data Manager Port are critical fields because they define how the Altiris PXE Server establishes communication with the Deployment Server. Initial Deploy boot option: The boot menu item that was set as the default pre-boot operating system at install time is selected. From the Deployment Server. Go to the Boot Menu Tab (page 290) and create a Shared Configuration if there are no items in the list. 2. When the boot menu appears on client computers.DS Tab This lets you set properties so that all Altiris PXE Servers can communicate with the Deployment Server. 3. Deployment Server properties Deployment Server IP address: This is the IP address of the Deployment Server that controls the Altiris PXE Servers. the Engine Port. and more.

Timeout: Select this option to enter a time-out value of your choice.8 SP2 307 . New: This lets you enter MAC addresses. See Define MAC Addresses (page 308). You can also select to not service the list of client computers. Customize PXE Server (Shared Configuration): This option is available when you select a specific server from the File menu. When you click this button. Wait indefinitely: Select this option so that a user must press <F8> to start the Initial deployment job. Use MAC Address Filtering: Select this option to use MAC filtering. Add. you could create a list of MAC addresses for a specific Altiris PXE Server configuration. select Do NOT service addresses so that the Altiris PXE Server you selected would not download a boot menu to any of the client computers listed. MAC address patterns MAC addresses are listed in this view box. When you click this button. Edit: This lets you modify addresses previously added to the MAC address list. MAC addresses filter properties mode Use Shared properties: This is selected when you are setting the properties for a Shared Configuration. Altiris® Deployment Solution 6. PXE responds immediately but Initial Deployment still waits 5 minutes before running. edit. the Define MAC Addresses dialog appears. Or. Do NOT service addresses: Select this option if you do not want the Altiris PXE Server to service the list of MAC addresses in the MAC Address Patterns area. Use default timeout: Select this option to use the time-out value set in the Initial Deployment Advanced properties from the Deployment Console. If this check box is not selected. The boot menu appears on new client computers for the length of time you set before booting to Initial Deployment. See Define MAC Addresses (page 308). You can also import or export MAC address text files.of 5 minutes. If you select this option. Example: if you had three Altiris PXE Servers that Deployment Server integrated with and you were setting properties for a Shared Configuration. Service listed addresses: Select this option if you want the Altiris PXE Server to service the list of MAC addresses in the MAC Address Patterns area. MAC Filter Tab This feature lets you control the service load of the Altiris PXE Servers by creating a list of MAC addresses you want to be serviced by either a specific Altiris PXE Server or by all Altiris PXE Servers associated to a Deployment Server. select Service listed addresses so that all three Altiris PXE Servers would respond to the listed client computers. You cannot change this selection on the other pages if you are setting properties for the Shared Configuration. you could create a list of MAC addresses. This allows you flexibility to select the Altiris PXE Servers that provide services for specific client computers across the network. the entries in the MAC Address Patterns area are ignored. or delete the addresses. You can keep the settings on the page or customize the properties for the Altiris PXE Server you selected. the Define MAC Addresses dialog appears.

and the MenuOption<number>.1.ini file consists of information gathered by PXE Manager and includes a section called MTFTP\Files. When the Windows navigation dialog appears. Example: the PXE. Enter a MAC address to start the range in the From box and an end range MAC address in the To box. You can create the import text file manually.1. go to the folder or disk drive where you want to save the text file and click OK.0=”224.1. A PXE boot menu option consists of two files. This address appears in the MAC Address Pattern area. A multicast address is automatically assigned to the files an Altiris PXE Server uses to download the boot menu to client computers. and the number of addresses available for a single Altiris PXE Server. Address range: Select this option to enter a range of MAC addresses. Define MAC Addresses Add or edit MAC addresses to the MAC address patterns area of the MAC Filter tab. Single address: Select this option and enter a single MAC address. See MAC Filter Tab (page 307).3” MenuOption129\x86pc\MenuOption129. go to the folder or disk drive where the text file is located and click OK.0=”224. Import: This option lets you import comma-separated text file MAC address list. Multicast Tab This option lets you set properties for the way Altiris PXE Servers download the boot image to client computers. You can use the export feature to save a large MAC address list and import the file to another Altiris PXE Server or to the same Altiris PXE Server in the event you need to uninstall and install Altiris PXE Server. [MTFTPD\FILES] BStrap\x86pc\BStrap.2” MenuOption128\x86pc\MenuOption128.1.0.8 SP2 308 .1. Export: This option lets you export the MAC address list to a comma-separated text file.4” Altiris® Deployment Solution 6.0” MenuOption128\x86pc\MenuOption128. When the Windows navigation dialog appears.0 file is the boot menu. or you can import a file that has previously been exported from any Altiris PXE Server on your network.1” MenuOption128\x86pc\MenuOption128. You can export all or part of the list by selecting the MAC addresses.1 file is the additional file needed to execute whichever menu item is selected by the user.1.Delete: Select a MAC address from the list and click this button.1. the number of multicast addresses available. The PXE Manager multicast properties lets you set a beginning multicast address. The MenuOption<number>.1.0=”224. This section lists the MenuOption files and their assigned multicast addresses.1=”224.1. Altiris PXE Servers communicate with client computers using the Multicast Trivial File Transport Protocol (MTFTP) and support larger transport packets. This determines whether Altiris PXE Servers will include or exclude the client computers listed.1.cr-1005309736=”224. which reduces the time it takes to download files.

TFTP is used to communicate. If the router is not configured to pass a multicast packet. an error message appears on client computers. The PXE Manager.1.ini or PXE. Altiris® Deployment Solution 6. You cannot change this selection on the other pages if you are setting properties for the Shared Configuration. the Altiris PXE Server tries to communicate with clients using MTFTP. IP fragmentation allows larger packets to be broken up into smaller packets during transport.0.ini files. This is helpful if you have a narrow bandwidth on the network and want to Enable Larger packets for TFTP/MTFTP when downloading files from the Altiris PXE Server to client computers. If you disable MTFTP. If an Altiris PXE Server is going to service client computers across subnets and this option is enabled.ini file specific to each Altiris PXE Server. Enable MTFTP: Clear this option if you do not want to use MTFTP to download the boot menu from the Altiris PXE Server to client computers. These are the files that an Altiris PXE Server downloads when a user selects a boot menu option from the menu list on a client computer. which gathers data from all Altiris PXE Servers on the network. If these files are edited. Important: Do not edit the PXE Manager.1.MenuOption129\x86pc\MenuOption129. you lose the ability to access the boot images stored on all Altiris PXE Servers.6” Notice that the multicast address increments by 1 for each file that is created when a new PXE configuration is added and the boot image is created. stating that MTFTP is unavailable.1=”224.1. See PXE Manager in the Automation & Imaging section of the Deployment Solution Product Guide.1. TFTP/MTFTP properties Use Shared properties: This is selected when you are setting the properties for a Shared Configuration. However. PXE-enabled client computers listen for broadcast messages sent by the Altiris PXE Server through MTFTP.ini are both used by the PXE Manager service to synchronize the boot images across all Altiris PXE Servers and Deployment Servers on the network.8 SP2 309 .ini file creates and sends a PXE. you must use a Third Party application to reassemble the smaller packets into the original packet size. Do not allow IP fragmentation: Clear this option to use IP fragmentation. You can keep the settings on the page or customize the properties for the Altiris PXE Server you selected. PXE Manager. you can select this option to communicate.ini and PXE. Packet size: Enter the transport packet size if your infrastructure does not have the capability of handling the default packet size of 768. PXE Manager PXE Manager creates a PXE Manager.5” MenuOption129\x86pc\MenuOption129. The Altiris PXE Server tries to connect to client computers using TFTP. and the PXE Manager service does not function properly. Customize PXE Server (Shared Configuration): This option is available when you select a specific server from the File menu. Enable larger packets for TFTP/MTFTP: Select this option to increase the packet size transport.ini file.cr-1005309736=”224. If an Altiris PXE Server is going to service client computers on the same subnet.

the Altiris PXE Server. Number of Multicast Addresses Available: Enter the number of addresses available for the Altiris PXE Server. warnings. information. and you can enter a directory path where you want the log files stored.8.8 SP2 310 .PXE Manager multicast properties Beginning Multicast address: Enter a multicast address between the range of 224.1. Boot Integrity Services (BIS) properties Enable BIS: Select this option to use BIS Certificates. such as errors. debug.225.000. With Boot Integrity Services (BIS). which are an open source on the network when PXE downloads these boot items to client computers.255.1. you must remove all BIS certificates before upgrading to Deployment Server 6. The client computers receive their certificate from the Altiris PXE Server. You can use BIS Certificates if you meet the following requirements: Client computers must be PXE and BIS compliant. This is a valuable tool that should be used only for troubleshooting purposes as it could impact the network in a production environment due to the amount of data being written to the logs. New certificate password: Enter a password. Data Logs Tab This option lets you enable data logs to help you troubleshoot incidents on the Altiris PXE Servers. Altiris® Deployment Solution 6.0 and .255. communication protocol. You must Enable BIS on this page first. Certificate owner: The default owner is Altiris. and more. Confirm certificate password: Re-enter the password. or all. The next time BIS installed client computers try to boot to the Altiris PXE Server. You can enable log files to help isolate issues with the network traffic.1. BIS Tab PXE configurations always create a . you can encrypt the files to ensure that the Altiris PXE Servers communicating with the client computers are secure.255. go to the Deployment Console and right-click on a computer or group of computers. You can specify a filename for each of the logs. PXE must be installed on your Deployment Server system.0 -. and select Advanced > Install BIS Certificate. Maximum Addresses Available to Single PXE Server: Enter the maximum addresses available on a single Altiris PXE Server. Limit: 128. Each log file lets you select a log level.1 file. the BIS Certificates must validate before any files can be downloaded. Note: If you have BIS enabled in Deployment Server 6.

Log Files: These log files are specific to Altiris PXE Servers and if enabled.Data Log properties Use Shared properties: This is selected when you are setting the properties for a Shared Configuration. Log File Location: This is the folder where all log files are stored. Note: DHCP services is required on the network to make the Altiris PXE Server function correctly. To install a remote Altiris PXE Server 1. Status Tab View the status of the Altiris PXE servers in your environment and track whether updates have been applied to each Altiris PXE server. Filename: Enter a name for the log file you enabled if you do not want to use the default name. Altiris® Deployment Solution 6. all remote installs must be “pushed” from the Deployment Server. The default location is C:\DSSetup.exe is installed. You can keep the settings on the page or customize the properties for the Altiris PXE Server you selected. You can install an Altiris PXE Server to both locations from the Deployment Server in Washington using the Remote PXE Installation Wizard. Browse to the location where axInstall. However. log information to the filename you specify and store it in the PXE folder on each Altiris PXE Server across the network. PXE Server Log PXE MTFTP Log Packet Parser Log DS Traffic Log Config Service Log The PXE Manager Log writes data to the filename you specify and stores it in the PXE folder on the Deployment Server. Level: Select the type of data you want to write to the log files. Remote PXE Installation You can install an Altiris PXE Server to any remote location on your network using this feature. Customize PXE Server (Shared Configuration): This option is available when you select a specific server from the File menu. If no directory path is entered. Each level in the list writes out more details to the log files the previous level. You cannot change this selection on the other pages if you are setting properties for the Shared Configuration.8 SP2 311 . Example: your business home office is in Washington and you have two smaller offices in Los Angeles and Australia. log files are stored in the default Deployment Share folder of C:\Program Files\Altiris\express\Deployment Server\PXE.

9. 3. 7. Run axInstall. Altiris® Deployment Solution 6. and click Next. Click Yes to accept the licensing agreement. Enter the computer name or Browse the network to select a remote Altiris PXE Server. 8. Enter the Altiris PXE Server install path. Select Yes. 4. 5.2. I want to install PXE Server on a remote computer. 10. Click Install. Select Install an additional Altiris PXE Server. and click Install.8 SP2 312 . 6. Select Component Install. Enter or Browse to the Deployment Share folder.exe. Enter the PXE Server IP address. 11.

and files from being restored Find files in an image Open a file with its associated program and edit Make self-extracting images Print image tree structure of files. This opens the ImgExpl. folders.IMG file type or image files with packaged rdeploy. Image files are created using the RapiDeploy utility. Altiris® Deployment Solution 6. add. an . and volumes Replace files Revert back to original image file contents Split images View.IMG or .EXE file type.exe runtime versions in an . such as extracting and saving files to another destination volume. folders and applications—before distributing and restoring its contents to a client computer. You can view properties and perform operations. folders. and volumes in an image ImageExplorer User Interface Click the ImageExplorer icon on the toolbar or select Tools > ImageExplorer.Altiris® ImageExplorer Altiris® ImageExplorer provides features to view and edit image files. You can open and edit image files in the native . or excluding files from being restored when distributing the image file to a client computer. folders.EXE file containing a replication of the source computer’s hard disk.8 SP2 313 . You can also print the contents of a folder or edit a file using its associated application.exe program located in the Deployment Share. a tool used most commonly in Deployment Solution to create and distribute hard disk image files. See also: Using ImageExplorer (page 318) ImageExplorer Features Add new files and folders Command line mode Convert images Create image indexes Extract files and folders Exclude (or include) volumes. or change the image description View properties of files. you can modify an image file—add or delete data files. Using ImageExplorer.

the new file is added to the same folder. Option 2: Select File > Create Image Index Altiris® Deployment Solution 6. Option 1: Ctrl-T Option 2: Select File > Convert Image Option 1: Ctrl-C Copy Copies a file or folder from one location and lets you paste it to a destination image file. folder. Button Access Option 1: Ctrl-A Option 2: Select Edit > Add File Option 3: Rightclick an item and select Add File Option 1: Ctrl-D Add Folder Adds a new folder to the image file. folder. Click any item to add a folder to the container object. Add File is available when you rightclick a volume. manage.Altiris ImageExplorer provides the following features to view. and file elements of an image file. Add Folder is available when you right-click a volume. or a file in the treeview. or a file in the treeview. Note Copying large amounts of data and large numbers of files between image files can take several minutes. See Add New Files (page 320). When you right-click a file and select Add File. See Convert an Image (page 320). Feature Add File Description Adds a new file to the image file. Option 2: Select Edit > Copy Option 3: Rightclick an item and select Copy Option 1: Ctrl-I Create Image Index Creates an image index to make the process of restoring images easier. folder.8 SP2 314 . Option 2: Select Edit > Add Folder Option 3: Rightclick an item and select Add Folder Convert Image Converts image files from file format 4 to the format most currently used by RapiDeploy. and modify the volume. See Create an Image Index (page 321).

or a file from the image file. Option 2: Select Edit > Find Option 3: Rightclick a container object and select Find Include Allows volumes.Feature Exclude Description Marks volumes. The the check box. Note You can also include a previously excluded file by clicking the next to the file in the Details pane. See Find Files (page 322). Option 1: Insert key Option 2: Select Edit > Include Option 3: Rightclick an excluded item and select Include Altiris® Deployment Solution 6. icon replaces Button Access Option 1: Del key Option 2: Select Edit > Exclude Option 3: Rightclick a file and select Exclude File(s) Option 1: Ctrl-E Extract Extracts a complete volume. Option 2: Select Edit > Extract Option 3: Rightclick an item and select Extract File(s) Option 1: Ctrl-F Find Search for files or folders within an image file using specific names or wildcard characters.8 SP2 315 . You can use ? as a variable for a single character or * (asterisk) for multiple characters. folders. and files not to be included when deploying the image file to client computers. A check box will reappear. and files that were previously marked Excluded to be included in the image file when it is deployed to a client computer. Note You can also exclude a file by clicking the check box next to the file in the Details pane. See Extract a Folder (page 322). It lets you select a destination volume or directory to save the folders or files. a folder (with its sub-folders). Note Extracting large amounts of data and large numbers of files can take several minutes. folders.

Feature Make SelfExtracting Description Creates a self-extracting file from an existing image file.exe or IBMaster.5 do not open. Option 1: Doubleclick (if not associated) Option 2: Select Edit > Open with Option 3: Rightclick the file and select Open with Option 1: Ctrl-O Option 2: Select File > Open Paste Option 1: Ctrl-V Option 2: Select Edit > Paste Option 3: Rightclick an item and select Paste Altiris® Deployment Solution 6. Note Image files created with IBMaster 4.exe. If the file is already associated with a program you can simply double-click to open. however these files can be viewed and extracted. However. Open Image File Opens image files created with RDeploy. You need an older version of ImageExplorer (Deployment Solution 5. Places a file or folder from one location to another. Files created with IBMaster are Read-only.5 or earlier) to edit files created with IBMaster. Button Access Option 1: Ctrl-M Option 2: Select File > Make Self-Extracting Open File (available for files) Opens a file using its associated application. See Make SelfExtracting Images (page 323).exe.8 SP2 316 . if the application exists on the computer where ImageExplorer is being run. Option 1: Doubleclick Option 2: Select Edit > Open Option 3: Rightclick the file and select Open Open File with Lets you open a file with a selected program. you can use the Convert an Image (page 320) feature to convert image files to the current RapiDeploy file format. Use Open file with to change the program or select the default Quick Open feature.5 or earlier. or RapiDeploy 4.

Includes sub-folders and files with their modification date. Option 1: Ctrl-R Option 2: Select Edit > Revert Option 3: Rightclick an item and select Revert File(s) Altiris® Deployment Solution 6. volumes. Properties appear differently for images. Option 1: Ctrl-L Option 2: Select Edit > Replace Option 3: Rightclick a file and select Replace File(s) Revert (available for files) An undo feature for the Replace File option. folders.8 SP2 317 . modification dates. Button Access Option 1: Ctrl-P Option 2: Select File > Print Option 3: Rightclick an item and select Print Properties Provides general information about the folder or file. You must have the associated application program installed to print the file (example: MS Word to print DOC files). Option 1: AltEnter Option 2: Select File > Properties Option 3: Rightclick an item and select Properties Replace Files (available for files) Provides a way to update a file in the image with a file from another source. and attributes. such as size. See Print Folder Contents (page 324) and Print a File (page 325).Feature Print Description Folders: Prints the folder structure. and size. time. Files: Prints the actual file. or files. See View Properties (page 318). This reverts a previously changed file to its original file. Both files must have the same name.

See also: View Properties (page 318). After selecting Properties for a selected folder in an image file. image files created with IBMaster can be viewed and files can be extracted. After selecting Properties for a selected image. or typing AltEnter. The Size on disk field displays the actual size of the compressed image file before it is deployed.6 or higher. You can open the properties page for an image file. click the General tab to view its property data. and attributes. such as size. location. volume. However. To modify older image files you will need to use the version of Altiris ImageExplorer that ships with the earlier versions of Deployment Solution. or file by right-clicking and selecting Properties. such as size. open the image file you want to view or modify by selecting Files > Open from the program menu bar.exe instead of the current RDeploy. Note Older image files created with IBMaster. click the General tab to view the image items and additional property data. Example: the Size field displays the amount of room that the image used on the hard drive of the source computer. and Extract a Folder (page 322).Feature Split Image Description Splits an image file of one size to be the segment size of another. a property page opens with the appropriate tabs: General Properties for an Image File This page displays data for image files. General Properties for a Volume This page displays data for a volume.8 SP2 318 . Depending on the type of image element. View Properties After opening an image file with ImageExplorer. You can modify the password of the image file in this dialog. and attributes. The ImageExplorer always displays the files created with IBMaster as Readonly even when the file attributes are Read-write. clicking File > Properties. Add New Files (page 320). See Convert an Image (page 320). The Image property page includes the name of the image file and its associated image data. Button Access Option 1: Ctrl-S Option 2: Select File > Split Image Using ImageExplorer With the ImageExplorer running. basic information about the image file and its elements can be viewed by selecting a file or volume (partition) name and clicking Properties.exe cannot be modified with the version of ImageExplorer that ships with Deployment Solution 5. Altiris® Deployment Solution 6. location.

If no associated program is located. an Open with dialog appears. such as size. ImageExplorer keeps track of these split image files and prompts you to locate any additional linked image files not stored in the same directory. See also: Print a File (page 325) and Settings (page 326). After selecting Properties for a selected file in an image. Note You can also associate a file with a program by right-clicking the file and selecting the Open with command. After selecting Properties for a selected folder in an image file.8 SP2 319 . Enter a path in the field Altiris® Deployment Solution 6. you can use the features in RapiDeploy to split the image file into multiple files. Find Missing Split Image Files If multiple files from a split image are kept in different folders or on separate CDs. allowing the user to select and associate a program for the file. General Properties for Files This page displays data for files. including data imported from the partition table.General Properties for a Folder This page displays data for a folder. It provides a count of the volumes in the image and lists the name of each volume in the Volumes pane. Description Properties for an Image This page displays the constituent volumes within the image file. It includes volume data and statistics. You can change the default program for the Quick Open feature by clicking View > Settings and editing the Open with program box. The Quick open feature lets you select a default program to open files without associated programs (Microsoft Notepad is the default program). If the image file has Read-write access. The file opens with its associated program. Open a File To open a file in an image. location. and attributes. double-click the file in the Details pane of the ImageExplorer or right-click and select Open. Disk Partition Properties The Miscellaneous property page provides a comprehensive list of system attributes for each volume in the image file. this dialog appears to help you locate the missing split image files. and attributes. location. Opening Split Image Files If an image is too large or if you are trying to meet size restrictions to store an image (such as dividing image files to 600 MB to fit on multiple CDs). you can modify the image description. click the General tab to view its included files and additional property data. When editing. such as size. click the General tab to view its included files and additional property data.

to file format 6 in Deployment Server 5. Option 1: Locate a file and click OK. this process takes longer. You do not receive a message warning that the embedded self-extracting code was removed. ImageExplore keeps track of all files in a split image and prompts you for any missing split image files if they are not located in the same folder. Select File > Open.or browse to the missing files. be aware of the following: If an old image has an image index (. The Select Files to add dialog appears.IMG file. a message appears confirming your decision to copy a file to the image file. the embedded RapiDeploy code is removed and the image is restored to a . the user receives a message indicating that the password has been removed. Right-click the preferred volume or folder in the image and select Add File. Open Altiris ImageExplorer. If an old image file is a self-extracting image. If an old image has a password.IMX) file.5 and earlier. Option 2: Drag a file from Windows Explorer to the selected folder or volume in an image file displayed in ImageExplorer. If you have large files with many segments. Altiris® Deployment Solution 6. Note You can access and edit text files by double-clicking the file in the Details pane of the ImageExplorer dialog. Add New Files 1.8 SP2 320 . or copy and paste the file. If the option is selected (see the Paste / Drop operations in the Settings (page 326) dialog). Convert an Image The internal file format for images changed from file format 4 in Deployment Server version 5. the new image file created does not have a password. Click OK. 2. However. but minor changes have been made to improve the overall format structure. Field Definitions Image File to Convert: Select the image file you want to convert. This feature lets you select any previously created image file and convert it to the current file format that RapiDeploy uses today. Select an image file. 4. 3. a new image index file is created. The new file appears in the image.6 or later. If the file format changes in future releases of Deployment Server. when you convert an image file. it will always be to the most current file format. File conversions may vary in length of time because ImageExplorer reads each segment in the image before converting it to the new image file. File format 6 has remained the same since its release. When converting image files.

New Output Image File: Select a folder and filename for the image file you want to convert. zip drives. The list of options includes default sizes for CDs.003. Click the drop-down arrow and select a segment size from the list.IMG to be on the same CD. and select an image file.IMX file is created in the same folder as the image you selected to index. . such as . and select an image file to convert. 5. and more.IMX files give RapiDeploy the information needed to restore the image. back to the first CD just for RapiDeploy to restore the image. Estimated segment count: The estimated number of segments in the file you selected to convert. You can also index images as you create them by selecting the Make an image index (. Output Folder for Index (optional): If you do not select a folder for the index output. Altiris® Deployment Solution 6.Current segment size: By default.IMG and .003. Click File. can give the file information to RapiDeploy when restoring the image file. Click Browse to navigate to a folder.002. 3.004. . .002. To create an index image 1. and . 2. Click File. 4. Click Browse to navigate to a folder. This makes restoring images easier because you are not required to insert the first CD.004. ImageExplorer creates a table of contents at the end of segment .8 SP2 321 . a new segment is created until the entire image is converted. New segment size (MB): Select a size for image segments from the drop-down list. and select Convert Image File. which identifies the file information for each segment of the image. and select Create Image Index. To convert an image file 1. Example: if you have an image with multiple segments.IMG and . Enter a new filename for the converted image. With this feature. can be copied to additional CDs as needed.imx) file option in RapiDeploy. along with the first segment of the image. based on the new segment size. Create an Image Index This feature lets you create an index file for image files so that when you copy the images to CDs. The other segments. and . Click OK. Current segment count: The number of segments in the image file. the first CD that contains the . the index file. When a file segment reaches this limit. Click Browse to navigate to a folder. Field Definitions Image File to Index: Select the image file you want to index. you can select . the segment size for RapiDeploy images is 2 GB. 3.IMG. Click Browse to navigate to a folder for the index file output. . 2. as you copy the segments to CDs.004. a new index file named . When you use the CDs to restore an image. the . See the RapiDeploy Reference Guide. Then.IMX is created. the last CD.

You can change the search domain before clicking Find. volume name.4. The following attributes use three-way check boxes with these features: Altiris® Deployment Solution 6. Select a folder on your local disk or on the network to place the extracted folder. Select File > Open. Replaced). organized by File Name and Location. You can use the ? (question mark) as a variable for a single character. Click OK. Click OK. 3. right-click. To search for a file. or use the * (asterisk) for multiple characters. Extract a Folder Use this feature to save a folder or file from an image to an external destination folder: 1. or folder name from the treeview to set a search domain. select that directory in the treeview pane and open the Find dialog. 4. The Browse dialog appears. Field Definitions Include folders: Select this option to include matching folders in the search results. 5. enter a string or characters (alpha and numeric) in the Find what box.8 SP2 322 . select the image file. 2. Note Extracting large amounts of data and large numbers of files can take several minutes. 6. Files and folders meeting specified search criteria are listed in the results box. Open Altiris ImageExplorer. Hidden. Note To search in a specific directory. and select Extract Folder. Click Include matching files to select files. Excluded. Select a folder in the image. Click Include matching folders to select folders. Filter Results Click Filter on the Find Files dialog to open an advanced search for files based on associated system attributes (Read-only. Select an image file. Click OK. System) and ImageExplorer attributes (Added. Find Files To search for files or folders in an image file. Include files: Select this option to include matching files in the search results. Field Definitions Find What: Enter the string or characters to find a file based on system attributes or ImageExplorer attributes of the file or folder.

Attributes: These are the system attributes of the files assigned by the operating system when the image was created. the file will take more time than if the . Note If you clear this check box and the Make Self-extracting process fails.IMG) are combined together to create the executable that restores images. which was used to create images beginning with Deployment Server 5.A solid checkmark means the item must contain the attribute. which is embedded into the executable. Field Definitions Current self-extractor type: The image file you selected is of this operating system type.8 SP2 323 . You can use the Convert an Image (page 320) feature to convert the image to the latest RapiDeploy file format. Altiris® Deployment Solution 6. When new versions of RapiDeploy become available through Deployment Server upgrades. This is helpful when you need to restore an image to a computer that does not have access to the Deployment Server and RapiDeploy for imaging through the network. Flags: These are the attributes assigned by ImageExplorer.IMG files appear. A dimmed checkmark means the value is NULL and the item can either have the value or not. However. See also: See Create an Image Index (page 321). However. you can re-make any self-extracting file by re-running Make Self-Extracting.6 or later. You can copy the self-extracting file to a folder or removable media and manually run it on any computer. including the index (. RapiDeploy and only the first segment of the image file (. you cannot use this feature. the original image file may become damaged or corrupted. If your file is 2 GB. all other segments that make up the entire image.IMG segment. or you can create a deployment job on the Deployment Server and distribute the self-extracting file to multiple computers. Keep original image file: Select this check box for ImageExplorer to make a selfextracting image file without affecting the original image file.IMX) are required when restoring an image. when you navigate to a folder to select an image. and you can no longer use the original image file to create a self-extracting file. If you have images that were created with Altiris IBMaster 4. You can select image files that have been created with RapiDeploy. An empty box means the item must not contain the attribute. Make Self-Extracting Images This lets you create a self-extracting file for an existing image file so you can run the executable at a client computer. This process may vary in length of time because ImageExplorer reads only the .IMG segment is 700 MB.5 or earlier. The image file’s embedded RapiDeploy code is replaced with the latest version of RapiDeploy. The self-extracting file is comprised of a valid image file and RapiDeploy. all .

volume. DOS: This mode uses the RapiDeploy graphical user interface to display the image file’s progress while it is running. You can view the progress bar at the bottom of the client computer’s display while the image file is running. Select Change self-extractor type. Click OK. To create a self-extracting image file 1.WIM files. 4. Click OK. This option is available only if the image file has self-extracting code. Not Enough Free Space The image file you selected to make into a self-extracting file cannot be created because there is not enough free disk space. See Field Definitions (page 323). Enter a directory path or click Browse to navigate to a location with more disk space. and other attributes for each file. You can open the sample job and specify the location of the .EXE code from a self extracting image. 3. or folder. click OK to view a Print Preview (page 325) of the report file. you can print a report that includes the constituent files and subfolders and includes fields with the modified date. 5. this option is unavailable. a volume (partition). DOS text mode: This is a text version user interface. and select Make Self-Extracting. Remove existing self-extractor: Use this option to remove the . otherwise. Click File. Depending on the options selected. which launches the ImageX utility and captures an image of the target computer. Clear Keep original image file if you want to make the original image file a selfextracting image file. time. ImageX Sample Scripts These are sample scripts that let Deployment Solution run ImageX imaging jobs from the Deployment Console.WIM file. Field Definitions Title: Enter a title for the top of the report page. The self-extracting file is created in the same directory as the original image file. The image file will return to its original state with a .8 SP2 324 . Click Browse to navigate to the location of the image file. or a folder. You can use ImageX to capture several different images into a single . The Not enough free space dialog lets you select an alternate location to create the self-extracting file. size. 2. see Not Enough Free Space (page 324). Altiris® Deployment Solution 6. If the Not enough free space dialog appears. These sample scripts include documentation so you can put the name and location of the . When printing the contents of an image file.Image file size: The size of the current image selected. You can run the job against the server.IMG file extension. Print Folder Contents You can print a list of the files and sub-folders within an image file.WIM file with the correct passwords and network locations.

volumes. Lines: View the number of lines in the report. Fields to Print Include modified date and time: Print the date and time that the file or folder was modified. volume. See also: Print a File (page 325).What to print Just this folder: Print only the files in the selected image.8 SP2 325 . Replaced). Print < . Attributes and date/time properties will be saved for this hidden folder in the image file. volume. you can select and print an actual file using its associated program. Field Definitions Quick print: Click this button to run a default program to open and print the selected file. You can also attempt a Quick print to open the file using a standard program. Include file number: Print the file number associated with each file. System. Include size: Print the size of the file. Include attributes: Print the Read-only. Hidden. > entries: Print an entry in each folder identified as < . such as Microsoft Notepad. Print: Click to print the report. The default program is Microsoft Notepad. Archive. Print Preview View an online display of the print report for image files. The name of the report will appear at the top of the page with details in a table that were selected in the Print Folder Contents dialog. This folder and subtree: Print the files in the image. Altiris® Deployment Solution 6. See also: Print Folder Contents (page 324)and Open a File (page 319). or Compressed system attributes (Read-only. or folders. Print excluded items: Print the files that were marked previously as Excluded. > (a dot notation). Excluded. or folder. Field Definitions Save: Click to save the report to a text file. Hidden) and the ImageExplorer attributes (Added. System. If your file is not associated with a program. You can change the default program to print files using the Print With program box in the Settings dialog. or folder and all the subfolders and files. Print a File From the ImageExplorer dialog. you can associate it by selecting from a provided list of installed programs on the computer. This will not print the subfolders.

The Settings dialog appears to set options to confirm specific operations using message boxes in the user interface. Paste & Drop operations: Present a confirmation message when dragging a file to a new folder in an image file. File Overwrite operations: Present a confirmation message to the user when extracting a file from an image file and overwriting an existing file on a destination drive. or when using the Add New Files command. Confirm password: Type the password again to confirm that is was correctly typed in. The Set / Change Password dialog appears. Show file numbers: View the associated file numbers in the image. it is Read-only and any operation performed cannot be saved. In the Attributes section. EXT3. when opening this file a confirmation box appears reminding the user that the file cannot be saved. This lets you view the help side-by-side with the program rather than allowing it to be sent behind the ImageExplorer user interface. Example: if an image file created in RapiDeploy 4. and as a result any changes cannot be saved. Field Definitions Current password: Enter current password. Altiris® Deployment Solution 6. In NTFS the files are numbered automatically. In FAT.Setting a Password on an Image File Right-click an image file and select Properties. EXT2.5 or earlier is opened. File Revert operations: Present a confirmation message when executing a Revert operation that returns the image file to its original file structure and content after replacing files. Settings You can set preferences for the Altiris ImageExplorer by clicking View > Settings. As a result.8 SP2 326 . This message appears when clicking the check box on the file or folder or selecting the Exclude operation. to set options for displaying items or excluding items. New password: Enter new password. or to select default programs when using the Quick print (see Print a File (page 325)) or Quick open (see Open a File (page 319)) options. Display Settings Keep help on top: Select to keep open help file on top of the ImageExplorer user interface. Folder Overwrite operations: Present a confirmation message to the user when extracting a folder from an image file and overwriting an existing folder on a destination drive. Exclude operations: Present a confirmation message to the user when assigning the Exclude option to a file (to not distribute the selected file as part of the image). and other file systems the files are numbered by RapiDeploy when creating the image file. when using the copy and paste operation to move files to another folder. select Password. Confirmations Read-only Open operations: Present a confirmation message to the user when opening a file in a Read-only state.

You could copy the segments to CDs and use them to restore the image file at client computers. if the old image is an old format image (IBMaster 4. Color replaced items: Select this option to mark files/folders replaced to the image with magenta text. However. and you wanted to split the image so it could fit on CDs. Color excluded items: Select this option to mark files and folders added to the image with red text. Use to associate files to a common program. the self-extracting code is removed. Color added items: Select this option to mark files/folders added to the image with blue text. See Open a File (page 319). the image cannot be split but is converted instead.IMX) file. The default program is Microsoft Notepad. Open with program: Set the default program to run with a selected file. the embedded RapiDeploy code remains. all the principles of Convert and Image apply. Split Image This feature lets you select an image file to split (rewrite) into a new image file based on the segment size you select. you could select 650 MB or 700 MB as the new segment size and the result would be one image file with multiple segments. If an old image has a password. the image cannot be split but is converted instead. a new image index file is created. See Exclude (page 315). See Replace Files (available for files) (page 317). If you proceed. a message appears to verify if this is what you want to do. See Add File (page 314) and Add Folder (page 314).5 or earlier). The default program is Microsoft Notepad. If an old image file is a self-extracting image. If an old image has an image index (. Altiris® Deployment Solution 6.Show excluded items: View the files marked as Excluded in the image.5 or earlier). Default Programs to Open and Print Files These settings are default settings for the Quick Open and Quick Print options that appear with the Open with and Open features. However. If you proceed. such as Microsoft Notepad. the new image file has the same password. This setting lets you include all files previously marked as Excluded to be saved to an external destination folder when running the Extract command. Print with program: Set the default program to print a selected file. Example: if you have a 2 GB image file. be aware of the following: If the old image is an old format image (IBMaster 4. the image cannot be split but is converted instead. if the image is an old format image (IBMaster 4. Extract excluded items: Allow the Excluded files and folders to be extracted from the image file to a destination folder. While Convert an Image (page 320) changes the file format of an image to be the current format used by RapiDeploy. If this occurs.5 or earlier). If you proceed. split an image keeps the format of the original image but changes the size of its segments. the password is removed. When splitting image files.8 SP2 327 . and the new image contains the same version of RapiDeploy as when it was originally created. Files will be shown after refreshing the screen. See Find Files (page 322).

xp. 2. and select an image file to split. Click File. To split an image file 1. When a file segment reaches this limit. To access the online command line options 1.img. Click Browse to navigate to a folder. the segment size for RapiDeploy images is 2 GB. Altiris® Deployment Solution 6. 4.8 SP2 328 . and enter a new filename for the image. Enter C:\Program Files\Altiris\eXpress\Deployment Server\ (default installation path). zip drives. 3. Command Line Switches This feature can be use to create Deployment Server Run Scripts or batch jobs to help you manage images from the command line. New Output Image File: Select a folder and filename for the image file you want to split. In the Open field. and select Split Image File. Current segment size: By default. At the end of some switches. Enter imgexpl /? to view the command-line switches page. Click Browse to navigate to a folder. select Start > Run. 4. 2. such as w2k. and select a segment size from the list. 5. based on the new segment size. 3. Click the drop-down arrow. a new segment is created until the entire image is split. From the Windows environment. Click OK.Field Definitions Image File to Split: Select the image file you want to split. and more. New segment size (MB): Select a size for image segments from the drop-down list. enter the command CMD. Current segment count: The number of segments in the image file. Command line Parameters Description Image files to open or operate (can be repeated. Estimated segment count: The estimated number of segments in the file you selected to split.img). select options are listed to indicate that the additional commands are allowed. The list of options includes default sizes for CDs.

Command line Switches Description -register: register file types in the Windows Registry. or an error occurred option the source. C:\Program Files\Altiris\eXpress\Deployment Server\imgexpl f:\w2k. or volume to an image. folder. Accepts the <-overwrite> and <-size> options. 12 Error performing an operation. 16 The Source was not found. -overwrite: when in silent mode. 14 The Image file was not found or an error occurred opening an image. -silent: *do not display confirmation or errors. folder. 18 The destination was not found or an error occurred opening the destination. * Indicates the options that can be used with any command. 10 Invalid password. Accepts the <-overwrite> option. Error registering or unregistering file types. ‘password’ and ‘sales’. Accepts <-overwrite> and <-size> options.img that requires the password ‘develop’. -add <src> <dst>: add file. Process exit codes 0 2 4 6 8 Success. -convert <dst>: convert an old format image to the current image format used by RapiDeploy. Command line syntax error.img -password develop Open two image files that each have different passwords. Attempted to write to a Read-only image. or volume from an image. You can use wildcards when entering the source (src). Operation cancelled by the user. -size <size in MB>: size of the new image segment in MB. Examples: Open a W2k. Accepts the <-overwrite> and <-size> options. -unregister: unregister file types in the Windows Registry. -split <dst>: split an image into new size file segments. Options -lang <lang code>: *specify the Language code for the user interface. -extract <scr> <dst>: extract a file. -password <pwd>: *passwords for image files being opened. do not confirm actions. Altiris® Deployment Solution 6.8 SP2 329 .

img -password develop -add e:\*.img.txt 1:\temp Convert the old format image file.img -size 650 Altiris® Deployment Solution 6.img.8 SP2 330 . C:\Program Files\Altiris\eXpress\Deployment Server\imgexpl f:\w2k. to the new image.img -password develop f:\w2k.img to e:\dump.img -convert f:\new2k.txt 1:\temp Extract kernal.C:\Program Files\Altiris\eXpress\Deployment Server\imgexpl f:\w2k. in 650 MB segments.img -password sales Add all *.img -password develop -add e:\*. C:\Program Files\Altiris\eXpress\Deployment Server\imgexpl f:\w2k.img. new2k.dll from the ‘Windows’ folder of the volume ‘sys’ in w2k. w2k.txt files in e:\to the ‘temp’ folder of the volume in slot 1 of w2k. C:\Program Files\Altiris\eXpress\Deployment Server\imgexpl f:\w2k.

Select one of the following methods for installing a Deployment Server system: Simple Install for Deployment Server on page 337 Custom Install for Deployment Server on page 340 Thin Client Install for Deployment Server on page 343 Component Install for Deployment Server on page 343 To install Deployment Agents on the client computer. Windows computers. The Deployment Web Console can be installed as part of the Deployment Server installation on any computer running Microsoft IIS. LAN and Web servers. with each client communicating through its own Deployment agent to update inventory data and react to Deployment Server commands and deployment tasks. or installed across several computers to distribute processing for large enterprise environments. Note You can also install the Deployment Server components remotely from the Altiris Console. Linux computers. scalable computer deployment and management system that can be installed and configured on a single computer.8 SP2 331 . 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. After installing Deployment Server components. see Installing Deployment Solution Agents on page 344. you can remotely install Deployment Agents on all types of computer resources across your organization: laptops and handhelds. and handhelds can be managed as a unified environment.Installing Deployment Server Deployment Server is a flexible. network switches. Deployment Server Components The Deployment Server system includes the following components: Deployment Console on page 332 Deployment Server on page 332 Deployment Database on page 333 Deployment Share on page 334 Altiris PXE Server on page 334 DHCP Server (not an Altiris product) Deployment Web Console on page 335 Installing Deployment Solution Agents on page 344 Sysprep on page 365 Altiris® Deployment Solution 6. and so on.

All these components can be installed on the same computer or distributed across multiple computers as per your environment. Managed computers require access to the Deployment Server at all times. Deployment Server Deployment Server controls the flow of the work and information between the managed computers and the other Deployment Server components (Deployment Console. you can access the Deployment Database on other Deployment Server systems to manage sites across the enterprise. Assign a static IP address to the Deployment Server computer. To install the Deployment Server on a remote computer. requiring that you have administrative rights on the computer running the Deployment Server. Create a user account to run the Deployment Server. Other components cannot connect to the Deployment Server if you use DHCP and dynamically change the IP address. Deployment Database. You must create this account on all Deployment Server computers. and the Deployment Share). The account must have a non-expiring password. See also Deployment Web Console on page 335. go to the Altiris Server services in your Windows Manager. not as a system account. See Connecting to Another Deployment Server on page 95. start. In a Simple Install for Deployment Server. the default administration shares must be present. you must ensure that a connection is available to these computers and security rights are set. Deployment Console communicates with the Deployment Database and Deployment Server services. Altiris® Deployment Solution 6. Deployment Console The Deployment Console is the Win32 user interface for Deployment Solution. Restore any shares that have been removed before you install the Deployment Server. or stop Deployment Server. The service runs as a logged-onuser. from this console. You can install this Windows console on computers across the network to view and manage resources from different locations. Managing from the Deployment Console on page 72.8 SP2 332 . In addition. and Deployment Server Components on page 331. In a Custom Install for Deployment Server. the Deployment Console is installed on the same computer as all other components. Note To view. The account must have full rights to 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. The computer and deployment data for each managed computer is stored in the Deployment Database. You must have administrative rights on any computer running the Deployment Console.

keyboard. Deployment Database The Deployment Database can be installed on Microsoft SQL Server™ 2000 or Microsoft Desktop Engine (MSDE) 2000. If the computer you are installing the database to has an existing Microsoft SQL Server™. Note You can install a single Deployment Database per Deployment Server system—you cannot have two databases storing data for a single computer. Microsoft Networking. Asset tag. Windows services installed Devices. and Serial numbers General Information.Note Creating an administrative account using the same name and password on each computer is easier to remember than using the names and passwords of existing accounts. you can identify a specific instance using this format: <database instance>\express. if you have multiple instances of the Microsoft SQL Server already set up. Altiris® Deployment Solution 6. E-mail. Windows devices installed such as network adapter. RAM. Personality Packages. The applications installed and information about these applications. you can enter the name SQLClusterSvr\salesSegment or SQLClusterSvr\marketingSegment during the Deployment Server setup depending on the previously established database instance. such as: Hardware. phone. TCP/IP. See also Deployment Server Components on page 331. Image files. such as the name of the application.MSI files) are passed through the Deployment Server. however. See Deployment Server System Requirements on page 336. and User information Applications. and Site The Deployment Server Database also contains jobs and other data used to manage your computers. the Deployment Database is added to that instance of the database engine. Example: if you have a clustered Microsoft SQL Server named SQLClusterSvr to manage multiple Deployment Solution systems on different network segments. Computer name and MAC address Configuration.8 SP2 333 . Therefore storing these files on the same computer as the Deployment Server can speed up the deployment of these packages. Publisher. Mail Stop. This feature is supported in the silent install . Department. Note In Deployment Solution 6. and monitors Location information.0 and later. and Product ID Services.RIP. are sent directly from the Deployment Share to the client computer when executing an imaging task. Most packages (.INI file and the GUI install executable. and . The database maintains the information about the managed computers. Contact name.

See also Deployment Server Components on page 331. Deployment Share is where you store image files. registry files. script files. This share must be created before you begin installing. If you are installing Deployment Solution on a remote file server (not the computer where you are running the install program). other computers can be used as additional.MSI packages. The 6. Note You can install only one Deployment Share per Deployment Server system.8 release of Deployment Solution also supports a different name for the Deployment database other than the default “eXpress”. In some cases.INI file and the GUI install executable. you can select the option to create the share during install. backup storage points. Deployment Share Deployment Share is a file server or shared directory where Altiris program files and packages are stored. However. This feature lets you identify and run multiple databases from one clustered Microsoft SQL Server to manage multiple sites or network segments. 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). If you are not installing to a remote computer. The share must allow access to all other components.8 SP2 334 . Note for NetWare users: If you have trouble using the Novell NetWare server as a Deployment Share. you can identify a named instance of the Microsoft SQL Server when installing Deployment Solution. When a computer is being deployed or managed. the client computer receives a request to boot to automation and the PXE-enabled computers connect to the first Altiris PXE Altiris® Deployment Solution 6. When the Deployment Server sends a deployment job. See Custom Install for Deployment Server on page 340. install the Novell Client rather than the Microsoft NetWare Client. Altiris PXE Server The Altiris PXE Server provides service to client computers on a subnet.Support for Multiple Database Instances In Deployment Solution 6. other systems emulating a Microsoft or NetWare environment can be used as the Deployment Share. See also Deployment Server Components on page 331. including managed computers and the user account that runs the Deployment Server. You can now identify other named instances of Microsoft SQL Servers rather than accessing only the default instance. This feature is supported in the silent install . Deployment Server stores and retrieves these packages from the Deployment Share as needed. and more. Personality Packages.0 and later. . if the Deployment Share's hard drive gets full. create a share (or give Read/Write rights for NetWare) on the file server where Deployment Server can be installed.

You can install an Altiris PXE Server on a Microsoft Server 2003. The client computer always boots according to the request and reply communications taking place between the Deployment and Altiris PXE Servers. Install Automation Partition on page 137. DHCP Server The DHCP (Dynamic Host Configuration Protocol) server is a server set up to assign TCP/ IP address to the client computers. or a remote computer running only Microsoft IIS. and Windows PreInstallation Environment (Windows PE) as pre-boot environments.8 SP2 335 . The Altiris PXE Server sends a boot menu option list to the client when the computer performs a PXE boot. See also Pre-boot Operating System (Simple) on page 361. This server is not an Altiris product. which communicates with the Deployment Server and the client computers. The default automation environment (the first pre-boot operating system files installed during the Deployment Solution installation) is used for Initial Deployment. uses the default automation environment or the environment specified by a user who has the persmissions to create a deployment job. Using an Altiris PXE Server to boot client computers to automation. 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. Windows 2000 Server and Advanced Server. Altiris supports DOS. Notification Server. The deployment job.Server they discover. These options let you create a single job. including a computer running Deployment Server. The Deployment Web Console can be installed on any computer running the Microsoft IIS Server. but it is required if you intend to use the Altiris PXE Server. Note If Microsoft IIS is running. Altiris® Deployment Solution 6. saves you from having to install an automation partition on each client computer’s hard disk. See also Deployment Server Components on page 331. We recommend that you use DHCP to manage the TCP/IP address in your network regardless of whether you use PXE or not. The Altiris PXE Server also functions on the same protocols as a standard DHCP Server so you can place the Altiris PXE Server anywhere you would place a DHCP server. and PXE Configuration Utility Help. See Boot Disk Creator Help. the Deployment Web Console is installed automatically during the Windows installation. Deployment Web Console The Deployment Web Console remotely administrates a Deployment Server installation from a Web browser. This greatly reduces the amount of time it takes to set up and manage your computers. but you must also install a DHCP Server. which contains at least one automation task. Linux. The boot menu options the request boot menu files from the Altiris PXE Server and are downloaded from the Altiris PXE Server to the client computer’s RAM storage. but may contain multiple automation tasks. or manually start computers using Altiris supported bootable media. You can also install as many Altiris PXE Servers as required in your system. unless you specify otherwise.

Deployment Server System Requirements The following are the system requirements for Deployment Server components and the network environment. See also Deployment Console on page 332 and Deployment Server Components on page 331. Open a DOS prompt to add the group Everyone by typing the following: net localgroup “Pre-Windows 2000 Compatible Access” Everyone / add Restart all domain controllers for the change to take effect. If you have a NetWare file server for your Deployment Share.71 or later to install.Note The DS Installer does not detect the version of MDAC that is installed. change them to the pre-2000 option from the Windows Start menu.8 SP2 336 . Deployment Server RAM: 256 MB Disk Space: 200 MB Component Hardware Software All components require Pentium III processors Deployment Server RAM: 256 MB Disk Space: 200 MB RAM: 128 MB Disk Space: 3. Server and Advanced Server Windows XP Professional Windows Server 2003 (SP1) Altiris® Deployment Solution 6. you must set up Active Directory with the Permissions compatible with pre-Windows 2000 option. IPX can also be used to communicate with this component. If the version of MDAC is earlier than 2. The Deployment Web Console requires MDAC version 2.71. For Windows 2000 systems. the Web console displays a target of invocation error. If you select the Permissions compatible only with Windows 2000 servers option the Deployment Server cannot manage domain accounts for you.5 MB Windows 2000 Server and Advanced Server Windows Server 2003 (SP1) Deployment Console Windows 2000 Professional. If you are using Windows 2000 only permissions. Network TCP/IP is used for communication between all Deployment Server components.

Windows 2000 Professional. . Deployment Web Console Deployment Agents Deployment Agent requirements are the same as the target operating system. Cannot be used for any other components).71 or later.8 SP2 337 .RIP.5 MDAC 2. plus space for data. Altiris® Deployment Solution 6. Deployment Console. boot. Server or Advanced Server Windows XP Professional Windows Server 2003 (SP1) MS IIS 5. The Deployment Agent requires around 5 MB disk space. Memory: 128 MB Disk Space: 100 MB for Deployment Server program files plus space for storing files (image. but does not have to be on the same computer as an Altiris PXE server) Windows 2000 Server or Advanced Server Windows Server 2003 (SP1) Deployment Database Memory: 128 MB Disk Space: 55 MB (for program files).NET frameworks are running on the selected computer. and so on) Memory: 128 MB (Microsoft SQL ServerTM 2000 (SP3) or MSDE 2000 (SP3) Deployment Share (File server for storage) Windows 2000 Server or Advanced Server Windows Server 2003 (SP1) NetWare (File server only. Deployment Share. and Deployment Database—on the same computer. You can install the Deployment Server with a Microsoft Desktop Engine (MSDE) from the Simple Install.Component Altiris PXE Server Hardware Memory: 128 MB Disk Space: 25 MB (for boot files) Software DHCP server (must be on the network. See the following sections for additional information: Installing the Deployment Agent on page 346 Installing Deployment Agent on Linux on page 350 Installing the Automation Agent on page 352 Managing Licenses on page 352 Simple Install for Deployment Server The Simple Install places all Deployment Server Components — Deployment Server. The Deployment Web Console is installed during a Simple Install (and during a silent install) if the Microsoft IIS services and .

Launch the appropriate Altiris Deployment Server installation file and follow the setup steps.altiris. Start the server and log on using the administrator account you created for the Deployment Server. 4. Altiris® Deployment Solution 6. you can install MSDE 2000 on a local computer if a database is not already installed. Select Include PXE Server. Click Yes to the Software License Agreement. Click Upgrade using existing license to upgrade the installation using an existing license. Click License File and browse to locate a license file (. click Free 7 day license. 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. See Altiris PXE Server on page 334. b. If you do not have a license file. 3. 5. Click Install. To run a simple install 1. 6. This option installs the Altiris PXE Server. In File Server path. This is optional. Click Extract and Execute App to extract and execute the application immediately. enter the drive letter and the path to install the Deployment Server program files. See the Altiris Getting Started Guide for further licensing information.LIC file).You can download the Altiris Deployment Solution either from the Altiris product CD or from www. 7. Enter the following information in the Install Information screen: a. AltirisDeploymentSolutionWin_6_8 installs all Windows components of Deployment Solution. See Deployment Server System Requirements on page 336. SQL 2005. Using the Simple Install option. The Deployment Server self-extracting install dialog appears. Note Simple installation works only with a default Microsoft SQL 2000. The Deployment Share lets you store files on the computer and run Deployment Server system applications.com.) Select Create eXpress share to create a Deployment Share on the computer. Click Simple Install. c. The installation continues and lets you use a free evaluation license file. See Deployment Share on page 334.8 SP2 338 . (The default path is C:\Program Files\Altiris\eXpress\Deployment Server. 2. or MSDE install. Note The default installation directory is DSSetup on C drive. This is the activation key you received when you registered your Altiris software.

See Custom Install for Deployment Server on page 340. Provide the location of the Microsoft Sysprep files. 9. This account must already exist. enter the domain and the user name (Example: Domain1\administrator). Install add-ons to provision server hardware. Select this option if you want to push the Deployment Agent to computers running the Windows 2000. the name you are currently logged on as appears. and Windows Server 2003 operating systems.EXE files or can disable services. If you click No. Note Antivirus applications can delete service . or click Back to modify settings before starting the installation. 10. This occurs because the service files are deleted by the antivirus application during scanning. Remote Install Clients. By default. Enter an administrator user name and password for the Deployment Server system. Click Next. Please ensure this service is started and running currently. stating that the share is already in use and you need to manually set the share to point to the correct directory. a message appears.” error appears.Note You do not need to apply a license key to activate the HP Thin Client t5000 Series. click Finish. Select this option to install the add-ons for Dell computers. Select this option to enable Sysprep support. Altiris® Deployment Solution 6.8 SP2 339 . 8. e. Click Yes and continue. You have successfully completed a Simple install for a Deployment Server system. Click Install to install the components listed on the summary screen. The Installation Information dialog displays the selected Deployment Server components to be installed. Note If you are upgrading your installation. The Installation Information dialog appears asking if you want to install clients. After the installation is complete. d. Note This option is enabled on Dell computers ony when add-ons are present in the oeminstall-addons section of the oeminstall. the “Unable to connect to the Altiris Deployment Server DS Management Server. This managed client computer automatically receives a non-expiring license when connected to the console. disable the antivirus software and reinstall Deployment Server. For example: when you run the Deployment Server Win32 Console. Enable Sysprep Support. Click the Deployment Console icon on your desktop to view all computer resources running Deployment Agents configured for your Deployment Server. If you use a domain account. the message Do you want to replace the share? appears. Click OK to this message.ini file located in the eXpress directory. XP. To resolve this issue. The installation process begins and can take several minutes to complete.

AltirisDeploymentSolutionWin_6_8 installs all Windows components of Deployment Solution. The default path is C:\Program Files\Altiris\eXpress\Deployment Server. 5. Click the Custom Install option if any of the following conditions exist: You are using the NetWare file server as a Deployment Share. enter the drive letter and the path to install the Deployment Server program files. This is the activation key you received when you registered your Altiris software. 3. If you do not have a license file. The default path is the DSSetup directory in the C drive.LIC file). Click Yes to the Software License Agreement. You can install Deployment Server with Microsoft Data Engine (MSDE) or install it to an existing SQL Server. The Deployment Share lets you store files on the computer and run Deployment Server system applications. You can download the Altiris Deployment Solution either from the Altiris product CD or from www. Click License File and browse to locate the license file (. You are managing many computers and require a distributed architecture to meet bandwidth restrictions and other design requirements. Select the Custom install option to add new components or to install Deployment Solution to an existing database. See Deployment Server System Requirements on page 336. To run a custom install 1. Select Create Deployment Share to create a Deployment Share in the system. the Deployment Share. or click the Extract to a specific folder option to set a path to an existing folder to download installation files. the Novell share should already be set up. Click Install. click Free 7 day license. Install the Deployment Share and enter the license file location: In File Server path. Click Extract and Execute App to extract and execute the application immediately. Deployment Console.com. 2. and the Deployment Database—on different computers.8 SP2 340 . (You can only create the share if it is on a Microsoft Windows Server.Custom Install for Deployment Server The Custom Install lets you distribute all Deployment Server Components— Deployment Server. The Deployment Share can be on a Microsoft Windows server or Novell NetWare server. 6.altiris.) See Deployment Share on page 334. Launch the appropriate Altiris Deployment Server installation file and follow the setup steps. Altiris® Deployment Solution 6. Start the server and log on as the administrator account you created to run Deployment Server. Click the Use current temp folder option to use the current temporary folder to download installation files. Click Upgrade using existing license to upgrade the installation using an existing license. The 4. The Deployment Server self-extracting install dialog appears.

Enter the Pre-boot Operating Systems information required for Boot Disk Creator. Type the port information in the Port field. Type the alternate name in the Database Name field and click Next. Install the Deployment Server on this computer or on a remote computer. Click Browse to select the FIRM file (for FreeDos and Linux operating systems) or enter the path for the location of the operating system files (for MS-DOS and Windows PE). You can edit the port number if you have manually entered the SQL Server name or if the port number does not appear automatically due to some firewall restriction. Altiris® Deployment Solution 6. the services that controls the flow of the work and information between the managed computers and Deployment Server components. If a previous installation of the Deployment Database is detected. Note If you have multiple instances of the Microsoft SQL Server already set up. Click Next. You can select a different name other than eXpress for your Deployment Database. Enter the Deployment Server information. Identify the type of Deployment Database authentication to be used. See Deployment Database on page 333. 7. Note You cannot use the remote SQL database with NT authentication on a remote computer if you don't have administrative rights on the computer. 9. See the Altiris Getting Started Guide for further licensing information. and Windows PE. Depending upon the selection of SQL Server instance. Identify where you want to install the database. Select the computer to install Deployment Server. See Deployment Server on page 332. Click Next. Enter a static IP address for the Deployment Server computer to ensure that the IP address remains constant.8 SP2 341 . Provide the account information that already exists on the Deployment Share and the Deployment Server. Click Next. Enter the path where the Deployment Server should be installed. you can identify a specific database instance in this field using the format: <SQL Server Name>###BOT_TEXT###lt;database instance>. Note You do not need to apply a license key to activate the HP Thin Client t5000 Series. Enter the user name and password if SQL Server authentication is used. Enter the Deployment Database information. Linux. 10. This managed client computer automatically receives a non-expiring license when connected to the console. MS-DOS. Select any one of the four options from FreeDos. Note If you are using a free evaluation license you cannot use the WinPE Add On Packages.installation continues and lets you use a free evaluation license file. a message appears asking whether you want to preserve or overwrite the existing database. the default port at which the selected instance is listening appears in the SQL Port Number field. or select an existing Microsoft SQL Server from the list of computers. 8.

Altiris® Deployment Solution 6. Remote Install Deployment Agent. You can select DOS. If you want to use the previously installed pre-boot operating system. Enter Deployment Console information. Note If you are upgrading your installation. The Installation Information dialog displays the selected Deployment Server components to be installed. Click OK. 16. 15. Enable Sysprep Support. 12. The installation process begins. 14. See Deployment Web Console Information on page 364. Select this option to enable Sysprep support. XP. See Altiris PXE Server on page 334. or click Back to modify settings before starting the installation. If you click No. the message Do you want to replace the share? appears. You must provide information about the path where you want to install the Deployment Web Console and also valid user credentials. Select this option to install the add-ons for Dell computers. Provide the location of the Microsoft Sysprep files. Select whether you want to install the Deployment Console on the computer you are working or on a remote computer. Enter PXE Server information. Install Deployment Agent to the client computers. This computer must be running Microsoft IIS . 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 the Server name. Provide information for installing the Deployment Web Console on the computer you are currently installing from. 17.NET framework. Note This option is enabled on Dell computers ony when add-ons are present in the oeminstall-addons section of the oeminstall. click Finish. If the Server name field is left blank it finds the first Deployment Server that responds. Note This option is disabled if Microsoft IIS is not detected. 13. Enter information on how you want to connect your managed computer to the Deployment Server. Click Next. Select this option if you want to push the Deployment Agent to computers running the Windows 2000. Click Next. Click Yes and continue.8 SP2 342 . select the Keep Default option.ini file located in the eXpress directory.11. Click Install to install the components listed on the summary screen. After the installation is complete. or Windows PE. Select the pre-boot operating system to use as the default PXE boot menu item. and can take several minutes. and Windows Server 2003 operating systems. a message appears stating that the share is already in use and you need to manually set the share to point to the correct directory. Linux. 18. The Installation Information dialog appears asking whether you want to install clients. Install add-ons to provision server hardware.

Click Install. 6. See Altiris PXE Server on page 334. 4. Select the Components to install. Deployment Web Console. Select the Thin Client Install option on the Deployment Server Install Configuration dialog and click Next. Altiris® Deployment Solution 6.exe. Click Extract and Execute App. Click this option to install another Deployment Console (a Windows executable) on another computer. Additionally. Start the server and log on with the administrator account you created to run Deployment Server. Select a default pre-boot operating system or select None and click Next. 6. The Thin Client is installed.8 SP2 343 . Altiris PXE Server. Click Next. This option installs the Altiris PXE Server. Click Yes to the Software License Agreement. To install Thin Client 1. 3. 2. Click Install on the Installation Information screen. Click Add Component. See Simple Install for Deployment Server on page 337. The Deployment Server self-extracting install dialog appears. See Deployment Server System Requirements on page 336. and Deployment Agents to the existing Deployment Share. Install an additional Deployment Console. 3. Enter a path for the Deployment Share. (Optional) Select Include PXE Server. 5. you can also add Microsoft Sysprep files. Enter the user name and password of the Deployment Server service on the Deployment Share Information dialog and click Next. To install components 1. You can add as many Deployment Consoles as required to manage from multiple consoles across your system. Launch the appropriate Altiris Deployment Server installation file and follow the setup steps. but you can install only one at a time. Component Install for Deployment Server The Component installation option lets you add selected Deployment Server Components— Deployment Console. Thin Client Install for Deployment Server The Thin Client installation option lets you install the Thin Client view of the Deployment Console on your computer. 4. 7. Click the Deployment Console icon on your desktop to view all the computer resources running Deployment Agents configured for your Deployment Server. Double-click axinstall.You have successfully completed a Custom install for a Deployment Server system. 5. 2.

but it also allocates additional blocks of IP addresses to other Altiris PXE Servers in the system. 9. See Sysprep on page 365. Note Install add-ons to provision server hardware is the only option available on the Installation Information Summary dialog when you select Component Install. The Master PXE Server works concurrently with any additional Altiris PXE Server to handle boot requests across the network segment. Install add-ons to provision server hardware. Master PXE Server. 11. Note If you select the On a remote computer option. Click Install to install the components listed on the summary screen. Click this option to install the Microsoft Sysprep files. When you add another Altiris PXE Server. Installing Deployment Solution Agents Each client computer requires the Deployment Agent to run as the Production Agent on a local hard disk. setting up managed computers in the Deployment Server system.Install an additional Deployment Web Console. Use this option to add additional Altiris PXE Servers across a network segment to handle boot requests for large environments. The Web console is installed on the local computer if the computer is running Microsoft IIS. the Altiris PXE Server installed initially is designated as the Master PXE Server. Select this option to install the add-ons for Dell computers. Note This option is enabled on Dell computers ony when add-ons are present in the oeminstall-addons section of the oeminstall. The Installation Information dialog appears specifying that the installation has been successful. Click Finish. and can take several minutes. See Deployment Web Console Information on page 364. see Altiris PXE Server Install on page 363.ini file located in the eXpress directory.8 SP2 344 . 8. you have to browse and select the remote computer. Click this option to install an additional Deployment Web Console on the local computer. Install an additional Altiris PXE Server. For all the available options for installing Altiris PXE Server. The installation process begins. The Deployment Console Information dialog appears. Select the computer to install the component and click Next. Click this option to install additional Deployment Agents on client computers. 10. which communicates with the Deployment Server and registers in the Altiris® Deployment Solution 6. Add Microsoft Sysprep files. Click Next. or click Back to modify settings before starting the installation. Install additional Deployment Agents. if you did not install them earlier.

DOS (If this line is missing. Install on handheld computers running the Pocket PC operating system. notebook. Install a Production Agent to a Windows desktop. or you can “pull” the Deployment agent from the client computer from the Deployment Web Console (or pull it from the Deployment Share). Install on any Windows desktop. Installing Deployment Agent for Pocket PC. you may have to move the files to a different location. The Deployment agents for handhelds are also easily installed from the console using prebuilt jobs.ini that comes with your driver (protocol. See Installing the Deployment Agent on page 346.NGRPCI_NIF [NGRPCI] (This header must be the sixth item listed in the line above) Device=NGRPCI.inf) Example: The OEM setup file may contain lines similar to the following: [netcard] NGRPCI=”NETGEAR FA310TX Fast Ethernet PCI Adapter”.ndis. Because not all NIC drivers follow that standard. See Installing the Automation Agent on page 352. or multicasting) Microsoft Client Drivers The Boot Disk Creator is set up to work with drivers that follow a certain standard. add it. See Installing Deployment Agent on Linux on page 350. sometimes outdated drivers (including default drivers that come with the hardware) cause problems when clients are in automation mode. Automation Agent. For Windows and Linux client computers. See Managing Licenses on page 352.NGRPCI.Deployment Database. Client Connectivity and Network Adapters Altiris supports all standard network adapter cards and includes many drivers with the installation of Deployment Solution. Deployment Agent. or server. you should check the manufacturer’s Web site for your network adapter to ensure you use their latest driver in your pre-boot operating system configuration file. However. Deployment Solution lets you “push” agent software to a client computer from a Deployment console. See Install Automation Partition on page 137.dos) The sample protocol. You can install an embedded (recommended) or hidden automation partition. The syntax is device=drivername.0. The following three files must be in the same directory: The DOS driver for your card (drivername. notebook. You can also install this agent to any supported Linux workstation or server. uploading.ethernet.real. 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.) Altiris® Deployment Solution 6. computer. To avoid these problems.8 SP2 345 . 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. Deployment Agent on Linux. or server computer. Install on any supported Linux workstation or server.ini) The OEM setup file that specifies the DOS driver (oemsetup.

) The .ins. The following are the requirements to install Deployment Agents to set up managed computers for each Deployment Server system. or click Tool > Remote Agent Installer to open the utility program. 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. For Windows 98 clients. you can successfully install the Deployment Agent using the Remote Agent Installer. This line must have at least two values listed.com. each user must have an account password.cfg files.8 SP2 346 . The two values needed are the description of the card (value1). Altiris® Deployment Solution 6. you have to install manually by running the aclient. Or. Windows XP. or you can e-mail the executable or a shortcut to users and run the install program from the client computer.ini file. Deployment Solution lets you install agent software using Remote Agent Installer to “push” the agent to a client computer from a Deployment console. You must have administrative rights to the client computers and File and Print Sharing must be enabled to install the agent software. Remote Agent Installer returns an error message if it is unable to get to the Administrative share on the remote XP computer for each user. run it on the local computer to install. Click Remote Agent Installer on the Deployment Console toolbar. and net.exe from the network share or Deployment Web Console to install a Deployment agent.If there is no protocol.com driver file name (value2). (These files must be in the same directory.exe downloaded from the network share or from the Deployment Web Console. When remotely installing the Deployment Agent on a Windows XP computer. and the . create a text file that contains the following command: DriverName=drivername Novell Client Drivers The Boot Disk Creator performs the following functions: Searches all subdirectories for a directory that contains *. You can also download aclient. Remote Agent Installer You can use the Remote Agent Installer utility program to install the Deployment Agent on Windows 2003/XP/2000 operating systems. you can “pull” the Deployment agent from the client computer by accessing the Windows share or downloading the install package from the Deployment Web Console. Searches the file for a line starting with a carat (^). Installing the Deployment Agent For client computers running a Windows operating system. Windows XP does not allow access to any Administrative shares if the user on that computer does not have an assigned password (including the guest account). you must install the agent software locally. When all users have passwords and the network setup wizard has been run. After downloading the install executable.INS file is opened to get information about the network card. Windows 9x. *. separated by a comma. For Windows 98 computers.

Add clients to a specific group. Add.Enter administrator account information Enter common administrator credentials for all client computers. Click Next. Specify another group to add new computers. Automatically Add to a Group You can add new computers to the All Computers group automatically. Use this username and password for all clients. Click Change Settings to set the Deployment Agent Settings on page 113 for the Deployment Agent. Enter the path where the Deployment Agent is to be installed on the client computer. you have to locate and download the program install files. The parameters must be entered in this order. 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. This file has the following parameters: -c:[computer] –u:[username] – p:[password] –i:[input file]. Import. You can also change SID and Agent settings from this Agent Properties dialog. Select the computers by the name in the list. View agent settings in the summary box. Let me specify a user name and password for each computer as its installed. Enter the name of a computer on the network or its IP address. Use back slashes to separate subgroups. or keep the default credentials to be prompted for each client computer. Enable this agent to use Microsoft Sysprep. or specify another computer group.RCI file and import new computers from a file previously created file in a DOS text file. Install directory. Enter credentials for an administrator account that has rights to all client computers added to the remote install list. Specify install directory Enter a location to install the Deployment Agent. Add clients to default group. The password parameter is not required if the administrator account does not have one Altiris® Deployment Solution 6. This is the default option. Properties. Select to set the security on the client computer. Find a . Prompts for an administrative user name password for each computer in the remote install list. If you enable this option. Select a computer and view agent install settings. Computer Name. or enter a computer name or IP address. Add new computers to the All Computers group.8 SP2 347 .

cab) We recommend installing these files from a Windows 2003 server CD.assigned. You can export the computers listed into an export file for future use. Enter the security key file path for the Deployment Server or browse and select a file containing the security key file path. This takes a long time to convert the SIDs.RCI. Select to download and install the Microsoft Sysprep files. Download Microsoft Sysprep If you selected Enable this agent to use Microsoft Sysprep on the previous dialog. Altiris® Deployment Solution 6. Windows 2000/XP/2003 (deploy. When the computers appear in the installer list and the properties have been set. Click to automatically update file system permissions to maintain the individual file permissions that may have been set. do not select this option. you do not need to specify an input filename. but any DOS text file can be used. Update file system permissions when changing SIDs. Remote Agent Installer first looks for an RCI file extension. Altiris recommends using Microsoft Sysprep in situations where SID replacement is required. Export. security and other settings on the Deployment Agent to be installed. click Finish. it connects to Deployment Server automatically and appears in the Computers pane of the Deployment console.8 SP2 348 . Get Server Security Key This page appears only if you select the Enable key-based authentication to Deployment Server option in the Change Agent Settings. Each computer entry must be on a separate line. you need to download the install files required for the Windows operating systems running on the client computer. Click Next. Note SIDgen is no longer supported and should not be used. To install Microsoft Sysprep. After the Deployment Agent is installed. If you are using the default settings. The default extension is *. the Remote Agent Installer dialog assists in finding the required install files for the specific versions of Sysprep. Change Settings Click Change Settings to modify access. This also includes the individual network shares that may exist on this client. See Deployment Agent Settings on page 113. The status of the agent install appears on screen. Checking this option also includes those individual permissions. To make the SID utility run faster.

However. this requires that you manually complete the installation at each client computer. Automating the Installation of Deployment Agent If you do not select Remote Agent Installer to install Deployment Agent. Enable changing of Security ID. it connects to the Deployment Server and appears in the Computers pane of the Deployment console. Click Next. Creating a Template File using Remote Agent Installer A template file can be created when running Remote Agent Installer. 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. After the Deployment agent is installed. Click to open the Computer Configuration Properties dialog and enter the settings for the Deployment agent you are installing. Advanced. This is optional. remove the semicolon.inp file or using the Remote Agent Installer. Select the utilities you want to use and enter the path where the utilities are stored. The template file can be created using two methods: editing the sample. 3. a screen listing the options for managing the SIDs appears. If you have enabled the security IDs. login script. Select to prohibit users from changing any agent settings.inp file Deployment Solution ships with a sample template file named sample. See Installing Deployment Solution Agents on page 344. After modifying agent properties and adding computers to the Selecting Clients window. To enable an option.Installing Deployment Agent for Windows Run AClient.8 SP2 349 . enter a location to install the Deployment agent. Select to manage the security IDs to run a SID utility as part of an imaging job. This file is located in Program Files\Altiris\eXpress\Deployment Server. if required: Secure modification of server properties. click Export Altiris® Deployment Solution 6.inp. Select a group in Deployment Console to add the client to. you can use a template file to set applicable options and properties. On the Altiris Client Service dialog. 2. Editing the Sample. Example: to specify a specific IP address and port number for the client to locate the Deployment Server. Instead. install the Deployment Agent using log-on scripts or batch flies. or manually from a client computer. Select one of these options. Click Next to install the Deployment Agent. Most of the parameters have been disabled in this file.exe from the Deployment Share (shared folder) or download the install file from the Deployment Web Console. which contains the commands to configure installation options and properties. 1. remove the semicolon from the TcpAddr and TcpPort lines and change the address and port number to the correct values.You can also leave it at the default group.

the following two template files are created: Export_PC-1.inp -install The following command-line options are available: Option -install -remove -silent -stop Definition AClient. Starts the Deployment Agent. Permanently removes Deployment Agent from the computer where it was installed. 8.to create the template file to import computers (*. Lets you use the options without being prompted for further input. 7. After downloading the .BIN file) on the client computer.2.0 RAM 32 MB Installing the Deployment Agent for Linux 1. Example: if you have computers named PC-1 and PC-2 listed in the Selecting Clients window and export these computers using the file name Export. you can install from the command line. -start 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 . 8.3.exe aclient. Example: \FX1\eXpress\AClient.8 SP2 350 .0. but does not remove it.rci.inp).1 United Linux 1.inp Using the Template File To use the template file you created. The Deployment Agent is updated automatically on Linux computers when upgrading to a new version of Deployment Solution.inp Export_PC-2. Processors Disk space Operating systems: Pentium 5 MB contiguous RedHat 7. Altiris® Deployment Solution 6.1 RedHat Advanced Server 2. run the AClient. the Deployment Agent runs in production mode.BIN file to a local directory.exe runs and installs the Deployment Agent on the computer as opposed to just running it in memory. The next time the computer is booted.exe installation program specifying the template file and using the -install switch. The creation date of the Deployment Agent is checked and updated when a new agent is available. This option works only when Deployment Agent is installed on the computer.rci) as well as the template file (*. Stops the Deployment Agent from running.

See Installing Deployment Solution Agents on page 344. open the adlagent. browse to the /opt/altiris/deployment/adlagent/bin directory from the shell and type the following: . the service updates the changes made in the adlagent configuration file. Altiris® Deployment Solution 6.conf file. switch to the root user (su) and change the directory to the location of the . To start and stop the Deployment Agent for Linux. type chmod 544 <filename> Type: .BIN file.To install from the command line. By stopping and starting the Deployment Agent for Linux. to obtain the permission. browse to the directory where you saved the .BIN file by typing (cd < directory>) after changing the directory. or the adlagent restart command. Change UseMcast=true to UseMcast=false.conf file located in the /opt/altiris/deployment/adlagent/conf directory and make setting changes to the configuration document. restart the Deployment Agent for Linux./configure You are prompted to select Multicast options to identify a Deployment Server to manage the current client computer.BIN file. You can also change the adlagent configuration file settings by executing the configure script from the /opt/altiris/ deployment/adlagent/bin directory. To run the script to change settings for the adlagent configuration file. This file is located in the /opt/altiris/deployment/ adlagent/conf directory.conf file in an editor and scroll to the [Transport] section and the UseMcast line. you can edit the configuration file to change the functionality or properties. In many cases. 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.d directory (with administrator/root rights) and use the adlagent stop and adlagent start commands.d/init. you must enter the full path or browse to the /etc/rc. You can also use the Package Manager installed with Linux to restart the Deployment Agent for Linux. 3. You can change the adlagent configuration file settings by updating the adlagent./<file name> The Deployment Agent for Linux is installed in the /opt/altiris/deployment/ adlagent directory. Additional configuration settings can also be identified and edited in the configuration file. After editing the configuration file. Type the IP address of the specific Deployment Server you want to manage the client computer into the TCPAddr=<IP address> line. You can now view the Linux managed computer from a Deployment console. 2. you must have the permission to execute the . To edit the configure file directly. Example: you can open the adlagent.8 SP2 351 .

install a new license. This utility shows the license status. create boot menu options from the PXE Configuration Utility. you can create a Microsoft Install Package (MSI) and deploy it using a job from the console. but licensing is based on the number of managed client computers. or bootable USB devices. using one of the following methods: Boot Disk Creator. or add licenses to computers installed with Deployment Solution. Altiris® Deployment Solution 6. Processors Disk space Operating systems RAM Pentium 5 MB contiguous MS DOS and Linux 32 MB Here are some other ways to create and install an Automation Agent.Installing the Automation Agent After Deployment Server has detected a managed computer through the Deployment Agent in a production environment. To install an Automation Partition on Windows 2003/XP/2000 computers. create boot disks to install locally. Direct from floppy. and add additional licenses. For Windows 98 computers. See PXE Configuration Utility Help.8 SP2 352 . or User Specified. or apply a license to a client computer. Although you can install multiple Deployment Servers. For Deployment Solution systems running the Altiris PXE Server. Managing Licenses From the Deployment Console you can find the number of licenses used. you can install an Automation Partition from the Computers pane. You can use this feature on Windows 2003/XP/2000. See Distributing Software on page 175. The Deployment Server system also provides the license utility to install or update regular licenses. which is saved in an embedded (recommended) or hidden partition on the client computer’s hard disk. See Boot Disk Creator Help To install an Automation Partition See Install Automation Partition on page 137. You can also create floppy disks. detect an expired license. bootable CDs with an ISO image.

Altiris® Deployment Solution 6. Expired License See also: Using the License Utility on page 353. When you open the License Utility. Rapid Deployment Pack Licensing on page 356. Computers Not Using a Regular License on page 357. The total number of client and server computers that a Deployment Server is licensed for. As long as this date is not expired you can use that license to register any version of Deployment Server. Regular production licenses never have a license expiration date. Each client computer that has an agent and that communicates actively with the Deployment Server uses a single license node. Detecting an Expired License on page 357. After the expiry date those trial or evaluation licenses no longer function.lic file) after Altiris products are installed. Adding a License from the Deployment Console on page 356. Licensed Nodes DS and PCT These are common abbreviations for Deployment Server and PC Transplant. This detail appears in the License Details when you apply a license with the Product Licensing Utility. which overwrites the current Activation Key with the one you are installing. Evaluation licenses however do have an expiration date.8 SP2 353 . but always have an AUP date. although some licenses apply only to PC Transplant. All regular licenses (that are purchased) never expire. and Expired Licenses on page 358. Using the License Utility The Deployment Server system provides a license utility to update or add licenses to installed sites. Finding the Number of Licenses Used on page 357. Both of these products are licensed with the same licensing model. which lets you apply the license activation key file (. you can select the Replace all existing license Activation Keys with this new Activation Key check box.Annual Upgrade Protection Description Altiris Annual Upgrade Protection or AUP lets registered Altiris software users upgrade to any version of the registered product that is released during the coverage period without paying an upgrade charge. and very often a single license applies to both products at once. and need to be replaced with a regular license. and select a license file.Licensing Terms Term AUP . You can view this information on the About Deployment Console box. This utility is installed to the Deployment Share during the Deployment Server installation. the Altiris Activation Key Wizard appears. On the Select Altiris Program Files to Activate page.

The Altiris Activation Key Wizard displays the activation key information. install new or updated licenses for installed software. because you will need it when future product updates are released. 3. Install a Regular License for Altiris Products When a product is installed from the Altiris CD or the Altiris Web site. To apply a regular license file 1.LIC).LIC file. Click Cancel. Enter the directory path to the new . 4. as long as the file names are different. Run license. You can also store multiple license activation key files in the same folder. A list displays the Altiris products that are installed on the Deployment Server. 2. and additional licenses for installed software. 2. Enter the directory path to the new . Multiple license activation key files can be stored in individual folders on a single disk. Each program file uses license activation key files. Click Next. Click Next. you can apply a 30-day evaluation license or a purchased regular license to installed products that use a license activation key file (. a 7-day trial license is automatically applied. Open the License Utility.exe. To open the Altiris License Utility Option 1: Click Start > Programs > Altiris > Deployment Solution > Product Licensing Utility.The License Utility shows the license status. Browse to the location where you installed the Deployment Share. Option 2: 1. Select one of the following: Option 1: Altiris® Deployment Solution 6. Note Save the license activation key file.8 SP2 354 . 4.LIC file and click Next. install a specific product. However. 2. store it in a safe place (such as a floppy disk) for future reference. 3. To view license status 1. Open the License Utility. After you receive the key. A summary screen displays the activation key information.

Click the Apply regular license check box. right-click the HP client computer and select Properties. Click Add to browse to the location of an Altiris product folder. Select the program filename and click Open. 2. The Altiris Activation Key Wizard displays the activation key information. Rapid Deployment Pack Licensing on page 356. b.LIC file and click Next.8 SP2 355 . Install Multiple Licenses Some Altiris utilities can combine multiple licenses together for the total number of nodes. Option 3: f. Note You do not need to apply a license key to activate the HP Thin Client t5000 Series. e. The product is added to the license list. Click Next. From the Deployment Console. HP client computers and licensing HP client computers automatically connect to the Deployment Server with a 30-day trial license. 4. Click Finish. This managed client computer automatically receives a non-expiring license when connected to the console. Click Remove. See also: Managing Licenses on page 352. HP client computers display a clock icon to indicate that the trial license is limited. 3. Select the products you do not want to apply a license to. A list displays the Altiris products you have licensed. Open the License Utility. d. Example: two 50-node licenses can be combined to a single 100-node license. See Installing Deployment Solution Agents on page 344. Enter the directory path to the new . Select the products to license and click Finish. Click OK. Click Finish to apply the license to the selected products. This option lets you apply an “add-on” license to the Altiris products you have installed on the Deployment Server. and has an expiration date. Option 2: c. h. Adding a License from the Deployment Console on page 356. Finding the Altiris® Deployment Solution 6. Select the products to license and click Finish. g. Following are the steps to upgrade the trial license: 1. In the Deployment Console. The license is automatically upgraded to a purchased license.a. Use the Shift key to select multiple products. 1. Select the product you want to license. 2. 3.

From the Deployment Console. 3. Select Properties. and Expired Licenses on page 358. Using the License Utility on page 353. Select Advanced. Those installation files use a slightly different version of the Product Licensing Utility. However. The easiest way to resolve this issue is to use the install files from the HP Web site. Using the License Utility on page 353. The only major difference is that due to the HP policy. Select Apply Regular License. right-click the computer group to which you want to apply the license. Adding a License from the Deployment Console on page 356.com Web site. Detecting an Expired License on page 357. To install a regular license to a single computer 1. and you download Deployment Server from the Altiris. you must install a regular license on the Deployment Server before you can install and manage licenses for client computers from the Deployment Console. Computers Not Using a Regular License on page 357. Altiris® Deployment Solution 6. You cannot install a license directly to a client ccomputer. AUP for their customers is much longer than normal. Detecting an Expired License on page 357. 4. 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. Computers Not Using a Regular License on page 357. It functions and behaves almost in a similar manner in regards to licensing. Because of this. Select Apply regular license. 2. To install a regular license to multiple computers 1. See also: Managing Licenses on page 352. Click OK.8 SP2 356 . Detecting an Expired License on page 357. right-click the computer to which you want to apply the license.Number of Licenses Used on page 357. and Expired Licenses on page 358. and Expired Licenses on page 358. Rapid Deployment Pack Licensing Rapid Deployment Pack (RDP) is a version of Deployment Server released to HP customers. From the Deployment Console. you cannot apply the licenses. 3. Finding the Number of Licenses Used on page 357. Finding the Number of Licenses Used on page 357. Computers Not Using a Regular License on page 357. You must apply a regular (permanent) license to continue managing client computers. if you have licenses for RDP. Deployment Server does not apply licenses correctly if they have AUP longer than 3 years. 2. Rapid Deployment Pack Licensing on page 356. See also: Managing Licenses on page 352. and they let licenses with long AUP dates.

You can see the total number of licenses you have purchased. Using the License Utility on page 353. Detecting an Expired License on page 357. this is an HP computer that still has the free 30-day license. Clients that are expired cannot be managed until a license is purchased for them and they have been flagged in the Computer Properties dialog to accept a regular license. 2. Double-click on the Deployment Agent icon on the client computer. However. Adding a License from the Deployment Console on page 356. Rapid Deployment Pack Licensing on page 356. Select Properties. a clock icon in the lower left corner implies that the computer still has a free license. Adding a License from the Deployment Console on page 356.8 SP2 357 . See also: Managing Licenses on page 352. You can view the information in the Computers pane to understand for which computers regular licenses have been applied. See also: Managing Licenses on page 352. 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. Note If you place a job on a computer with an expired license. Altiris® Deployment Solution 6. Using the License Utility on page 353. To verify that a client computer is associated with the Deployment Server you want. A computer with an expired license states Client license expired . Computers Not Using a Regular License From the Deployment Console. If you try to view the properties of a computer with an expired license. the following error message appears: Error: You have chosen a computer that has expired. In the Computers pane. 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 them. it can be that the computer was moved from one Deployment Server to the other. this may not always mean that the license has expired so check the other options listed below. do the following: 1. Computers Not Using a Regular License on page 357. the same error message appears. Finding the Number of Licenses Used on page 357. and Expired Licenses on page 358. the total licenses you have used. and Expired Licenses on page 358. and the former server had an expired licence. you can understand which computers do not have a regular license. and the total licenses available. Detecting an Expired License on page 357. If the icon has a clock in the lower left corner of the Computers pane.see computer properties when selected. Rapid Deployment Pack Licensing on page 356.Finding the Number of Licenses Used Open the Deployment console and select Help > About from the main menu bar.

Click the Global tab. This makes all computer nodes in that group release the license node they were using and take a regular license node. This can cause problems if the trial licenses are still being used and they expire even after you apply a regular license. Altiris® Deployment Solution 6. the computer stops accepting jobs or any type of remote management. In the Deployment Console. go to Tools > Options. If this node is a temporary license. 2. 1. however the 7-day trial license. When a license is first installed on the Deployment Server. This is helpful if you want to see an immediate resolution to a license issue. Computers Not Using a Regular License on page 357. See also: Managing Licenses on page 352. Rapid Deployment Pack Licensing on page 356.8 SP2 358 . Using the License Utility on page 353. Finding the Number of Licenses Used on page 357. 5. and Detecting an Expired License on page 357. See also: Managing Licenses on page 352. If that license is not replaced before the time limit. 4. This is a long term and preventative solution to expired license issues. DS Installation Help The following are the help file topics for the Deployment Server installation program that you can access by clicking Help or pressing the <F1> key. Select Advanced > Apply Regular License. These topics identify and explain the screen elements on the dialogs used in the installation process. Rapid Deployment Pack Licensing on page 356. and Expired Licenses on page 358. In the Deployment Console.3. Finding the Number of Licenses Used on page 357. Enter the IP address of the correct Deployment Server in the Address/Hostname field. When the Deployment Server receives new regular licenses. right-click the All Computers computer group (or any other computer group you need to do this to). This resolves the computer node licenses expiry issue. Adding a License from the Deployment Console on page 356. Using the License Utility on page 353. Adding a License from the Deployment Console on page 356. or the 30-day evaluation licenses do expire. Expired Licenses Regular Deployment Server licenses do not expire. and can cause some problems if not replaced properly after adding regular licenses. 4. First you can set up a global option that automatically replaces any trial license with a regular license as soon as they become available. 3. Select the Automatically replace expired trial licenses with available regular licenses check box. it does not by default release the trial license nodes that it was using before. The second way you can deal with expired licenses is reapply all regular licenses to the computer nodes. Computers Not Using a Regular License on page 357. Click OK. Computers with expired licenses become dead nodes and can no longer be managed by the Deployment Console. each computer in the database takes a license node. that computer has a tag in the database that says it is a trial node. There are 2 ways to deal with this lingering expired license issue.

Click this option to install all Deployment Server components on a single computer. If not. 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. Altiris® Deployment Solution 6. A Simple installation lets you install all components on a single computer.Install Configuration The Deployment Server system supports a Simple Install and as well as a Custom Install option. See Component Install for Deployment Server on page 343. Select this feature to install the Altiris Altiris PXE Server when running the Simple install option. a secondary dialog appears asking you to select the IP address for the Deployment Server interface. The Custom installation lets you distribute individual components of a Deployment Server system on multiple computers. This configuration is recommended for managing computers on a single LAN or across a site with few subnets. Note If you are running Deployment Server on a MS Windows Server 2003 Domain Controller with SMB Signing enabled you cannot execute any imaging and DOS jobs. Click this option to install additional Deployment Server components to your system. the installation program prompts you to automatically install MSDE 2000 from an Altiris download Web site. Click this option to check for an installation of Microsoft SQL Server for a Simple install. See also Deployment Server System Requirements on page 336. You do not require a license file to install this view. The PXE Server requires a DHCP server also installed on your network. Pre-Installation Simple Install Helper. Include PXE Server.8 SP2 359 . the installation program continues. The Thin Client Install lets you install the Thin Client view of the Deployment Console on your computer. Example: use this option if you want to add an Altiris PXE Server to your Simple or Custom installation. Click this option to install the Thin Client view of the Deployment Console on your computer. A Custom install lets you balance network activity for large enterprises with multiple subnets. The PXE Server requires a DHCP server also installed on your network. Thin Client Install. See Simple Install for Deployment Server on page 337. See Custom Install for Deployment Server on page 340. Include PXE Server. Select this feature to install the Altiris Altiris PXE Server when running the Simple install option. or if you need multiple Deployment consoles. If Microsoft SQL Server or MSDE is located. When running jobs on MS Windows Server 2003. If you have multiple network adapter cards. you must change the SMB Signing Registry Key to execute DOS-based deployment jobs. Custom Install. Installation Type Simple Install. See Thin Client Install for Deployment Server on page 343. Click this option to install Deployment Server components on multiple computers across your system. Use the Component Install option to install additional components on your system. Component Install.

Installing Deployment Server. Upgrade the Deployment Solution install by using an existing license file. Select the drive letter and directory path where Deployment Server can be installed. If you are installing the Deployment Server to a local Windows computer. RIPs. Open the Default Domain Controller Security settings dialog by clicking Start > Settings > Control Panel > Administrative Tools > Domain Controller Security Policy >Local Policies >Security Options. Type the path or browse to the license (. See also Deployment Server Components on page 331. Click to use an evaluation license for a new Deployment Server installation. and Managing Licenses on page 352. Altiris® Deployment Solution 6. If running a Simple Install.8 SP2 360 .To disable SMB signing on the Windows 2003 Server 1. Service user name and Service password. Installing Deployment Server using Component Install Specify the Deployment Share (shared directory) where image files. The service is identified in the Services section of the Windows Computer Management as Altiris eXpress Server. For domain accounts include the domain name (example: orgDomain\admin). Ensure you create the administrator domain account before starting the installation. For Windows XP. Ensure you have a shared Windows or NetWare directory with available disk space and security rights before installing. you must run the Network Setup Wizard accessed from My Network Places to enable sharing. Create Deployment Share. If you are installing to a remote file server or if you select an invalid path. File server path. Note If you are installing the Deployment Server to a remote file server. and other package files are to be stored. create a share or grant access rights to the Deployment Server directory on the file server before you start the installation.LIC) file received when you registered on the Altiris Web site. and other package files are stored. right-click it and select Properties > Disabled. Locate the Microsoft network server: Digitally sign communications (always) policy setting. The default path is the Program Files directory on the local computer. . License file. this option is unavailable. Deployment Server Install Install the Deployment Server on a computer. select the Create Deployment Share check box to create a shared directory as your Deployment Share. 2. This is Enabled by default. Upgrade using existing license. Ensure you have a shared Windows or NetWare directory with free disk space and appropriate security rights before installing. Installing Deployment Server Specify the Deployment Share (shared directory) where the image files. Disable the Microsoft network server: Digitally sign communications (if client agrees) policy setting as well. Free 7 day license. type the user name and password of the Deployment Server service and the Deployment Share. 3.RIPs.

Linux Managed. The exact location of the folder varies. Create the administrator domain account before starting the installation. Click On this computer. However. Browse to the BDCgpl. Linux. Type the user name and password of an administrator account for the Deployment Server computer.FRM file is an open source code and is not owned by Altiris. Type the user name and password of the Deployment Server. Type the Deployment Server IP address and port information.FRM file is an open source code and is not owned by Altiris. However. DOS requires an original Microsoft Windows 98 installation disk. depending on the installation path. or browse to the system formatted files. 3. 2. However. the first pre-boot operating system you install becomes the default boot menu option for Initial Deployment. Select this option if you do not want to provide a default automation operating system. which Deployment Server can use as the default when creating a deployment job with an automation task. this file is available to all customers by downloading the file from the Altiris Solutions Center. None. 2. this file is available to all customers by downloading the file from the Altiris® Deployment Solution 6. Type the name of the computer or browse to where you want to install. The exact location of the folder varies. For domain accounts include the domain name (example: orgDomain\admin). MS-DOS. This .frm file. Browse to the BDCgpl. The user account must have rights to the Deployment Share. This . This flexibility lets you run several automation tasks within a single job. 4. and each task can boot to the automation environment you want.frm file. See Deployment Server Components on page 331 and Installing Deployment Server on page 331. or Windows Managed. which is located in the GPL folder on the Deployment Server. type the domain and user name. To install service on a remote computer 1. Pre-boot Operating System (Simple) Select a default pre-boot operating system.8 SP2 361 . 3. For a domain account. you can also install additional pre-boot operating system files through Boot Disk Creator later. Create this account before starting the installation. You can also select this later through the Boot Disk Creator utility. If you are running an Altiris PXE Server in your system environment. depending on the installation path. Enter the path to install the Deployment Server.To install service on a local computer 1. The destination path and IP address of the computer appear automatically. which is located in the GPL folder on the Deployment Server. Click On a remote computer. You can assign an automation pre-boot operating system to an automation task when it is added to a deployment job. The menu options display DOS Managed. DOS FreeDOS.

and each task can boot to the automation environment you want. Browse to the Windows PE files and the Microsoft Windows operating system path. which Deployment Server can use as the default when creating a deployment job with an automation task. and PXE Configuration Help. DOS requires an original Microsoft Windows 98 installation disk. and Microsoft Windows 2003 SP1. this file is available to all customers by downloading the file from the Altiris Solutions Center. x86 x64 ia64 See Boot Disk Creator Help. depending on the installation path. Browse to the Windows PE files and the Microsoft Windows operating system path.frm file is open source code and is not owned by Altiris. You can select the Altiris FIRM file for the following operating systems. you can also install additional pre-boot operating system files through Boot Disk Creator later. the first pre-boot operating system you install becomes the default boot menu option for Initial Deployment.frm file. Pre-boot Operating System (Custom) Select a default pre-boot operating system. Linux Managed. Altiris supports Microsoft Windows PE 2005. The exact location of the folder varies. Altiris supports Microsoft Windows PE 2005. You can select the WinPE files for the following operating systems. x86 x64 ia64 Windows PE. Browse to the BDCgpl.frm file. and Microsoft Windows 2003 SP1. If you are running an Altiris PXE Server in your system environment. or browse to the system formatted files. This . However. FreeDOS. which is located in the GPL folder on the Deployment Server. You can assign an automation pre-boot operating system to an automation task when it is added to a deployment job. The exact location of the folder varies. Browse to the BDCgpl. The menu options display DOS Managed. this file is available to all customers by downloading the file from the Altiris Solutions Center. See Boot Disk Creator Help. This flexibility lets you run several automation tasks within a single job. However.frm file is open source code and is not owned by Altiris.8 SP2 362 . Altiris® Deployment Solution 6. depending on the installation path.Altiris Solutions Center. and PXE Configuration Help. Linux. MS-DOS. Windows PE. However. This . or Windows Managed. which is located in the GPL folder on the Deployment Server.

However. The Universal Network Device Interface (UNDI) default driver is not supported by Novell NetWare. if you do not use PXE and prefer using embedded (preferred) or hidden partitions. Click Yes. if you have multiple instances of the Microsoft SQL Server already set up. this does not alter the Deployment Share name. or bootable media to run tasks. The instance of the database can vary. Note In Deployment Solution 6. You can also change the default SQL Port number. Altiris PXE Server Install Select the 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). To name the Deployment Database differently from the default name eXpress. Altiris® Deployment Solution 6. I want to install PXE Server on a remote computer to install the Altiris PXE Server on a remote computer. you must set up the Altiris PXE Server after installing Deployment Server. See also Deployment Server Components on page 331. Click No I will be using an Altiris automation partition on each client computer. you can type a different name in the Database Name: box. 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.0 and later. Example: if you have a clustered Microsoft SQL Server to manage multiple Deployment Solution systems on different network segments. Note This option is unavailable for installing the Altiris PXE Servers using Add Components. Type the name of the computer and the path. Install the Deployment Database using these options: Select the Microsoft SQL Server instance where you want to install your Deployment database. Note If you have a Novell NetWare file server. To install the database you must have administration rights to the selected server. you can identify a specific instance using this format: <SQL Server Name>###BOT_TEXT###lt;database instance>.8 SP2 363 . Click Yes.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. you can enter the name salesSegment\express or marketingSegment\express depending on the previously established database instance.

To Install Deployment Web Console 1. DS Web Console installs to the same computer running the installer. If you want to change the default values. Client Connection to Server Select the protocol your managed computers can use to connect to the Deployment Server. Lets managed computers connect to any Deployment Server. Discover Deployment Server using TCP/IP multicast. you have to change the client configurations. If managed computers are on a different segment or if you are using the Altiris PXE Server with an UNDI driver.8 SP2 364 . You can use this without PXE for faster access. Pre-boot Operating System (Simple) on page 361. as it goes directly to the IP address without searching. 3. If you want to use different drivers on the Altiris PXE Server. Note If you change the port number. See also Installing the Automation Agent on page 352. Example: if you select Linux in the Pre-boot Operating Systems page. 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. Do not change the port number unless the default is already being used. the Linux option is enabled as the default PXE boot menu item. and PXE Configuration Utility Help. 2. you can create multiple PXE boot files after installing. enter the Console port and Deployment Web Console path for the installation. click Connect directly to Deployment Server and enter the IP address of the Deployment Server that the managed computers can connect to. enter the name of the Deployment Server computer.Type the IP address for the Altiris PXE Server and the Deployment Server. and click Browse to navigate to a computer where you want the installation to occur. 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. Deployment Web Console Information This feature lets you remotely manage Deployment installations. Installs the Altiris PXE Server using the Intel Pre-boot eXecution Environment (for PXE-compliant computers only). Altiris® Deployment Solution 6. Multicasting cannot be used with the UNDI driver. The Service user name and Service password must be an existing account on the Deployment Share and the destination computer where the Web Console can be installed. Click On a remote computer. To use multicasting and connect to a specific Deployment Server. See also Deployment Agents on page 112. By default. Select the pre-boot operating system that can be used as the default PXE boot menu item. You can also select to not install Deployment Web Console by clicking the Do not install option. Type the path on the computer to install the Altiris PXE Server. Connect directly to Deployment Server.

Note This option is enabled on Dell computers ony when add-ons are present in the oeminstall-addons section of the oeminstall. and download Adobe Acrobat for documentation. access the Deploy. Select this option to install the addons for Dell computers.8 SP2 365 . If you install the Itanium Windows operating system to a computer that is not an Itanium box. or click Back to change settings. and Windows Server 2003 operating systems. Installing Components Click Install. Provide the location of the Microsoft Sysprep files. Altiris® Deployment Solution 6. See also Deployment Console on page 332 and Deployment Server Components on page 331. Note Install add-ons to provision server hardware is the only option available on the Installation Information Summary dialog when you select Component Install. You can remotely install Deployment Agents.ini file located in the eXpress directory. enable Sysprep support. Sysprep Enter the location of the Microsoft Sysprep files according to the operating system. the Do not Install option is disabled. Select this option to enable Sysprep support. Remotely Install Deployment Agent (Windows 2000 or later only). To resolve this issue. See also Deployment Server Components on page 331. Type the location or click Browse and select the required files. Select this option to push the Deployment Agent to computers running the Windows 2000. Add Components Summary The components in the list are installed. Install add-ons to provision server hardware. Enable Microsoft Sysprep Support. Click Finish. Installation Information Summary The components are installed.cab file from an Itanium box and save it on the server before you install Deployment Solution.Note If you are installing an additional Deployment Web Console using Add Component. See also Deployment Server Components on page 331. but is of the wrong type for the computer. an error message appears that the file is valid. XP.

If you select SQL authentication. you can add components to the existing system. Use SQL Server authentication. Use Windows NT authentication. See also Deployment Server Components on page 331 and Installing Deployment Server on page 331.Download Adobe Acrobat. See also Deployment Server Components on page 331. Select the type of component you want to add.PDF format. See also Deployment Server Components on page 331. Enter the user name and password set for the Microsoft SQL Server. enter the user credentials with administrative rights for the SQL database.8 SP2 366 . See also Deployment Server Components on page 331 and Installing Deployment Server on page 331. You can select Windows authentication or SQL Server authentication. the default “sa” user name is used with no password is required. see the Error Messages in Deployment Solution chapter in the Reference Guide. Console Install You can install the Deployment Console on either the local computer or multiple remote computers. Click to use the Windows network or Active Directory authentication. Type the computer name or browse and select a computer. If using MSDE. Select this option to download the Adobe Acrobat Reader to read the documentation in the . Installer Return Codes For a list of return codes for the installation program. Click On a remote computer to install the Deployment Console to a remote computer. Add Components If you have already installed Deployment Server. Deployment Database Authentication Specify the type of authentication the Deployment Database will use. Click On this computer to install the Deployment Console to the local computer. Installing the Deployment Console to remote computers lets you manage computers from multiple Deployment Consoles across the Deployment Server installation. Altiris® Deployment Solution 6. Click Finish.

the Deployment Web Console loads into the Altiris Console to provide comprehensive reports and integrate additional management solutions. Altiris® Deployment Solution 6. and collections — with standard Deployment Solution management features. security. Deployment from the Altiris Console allows you to use the built-in features of Notification Server — such as Package Servers.Part VII Deployment Web Console The Deployment Web Console allows you to manage and deploy computer resources in real-time from a web browser to manage multiple Deployment Server sites. In addition.8 SP2 367 .

double-click the icon on the desktop or click Programs > Altiris > Deployment Solution > Console. See Deployment from the Altiris Console (page 386). double-click the icon on the desktop. perform remote operations. you can manage all types of computer devices and servers from the Deployment Web Console using all features available in the Windows console. See the Deployment Server Help and Deployment Product Guide for additional information. and Details panes to view computer icons and properties. Notification Server also provides collection features to group computers by defined criteria. Deployment from the Altiris Console lets you generate enterprise-wide reports that track deployment resources and integrate features such as Package Servers for location-sensitive software distribution. HelpDesk. Altiris® Deployment Solution 6. The Web console for Deployment Solution provides standard Computers. build and schedule jobs. and other deployment utilities and features. Deployment from the Altiris Console lets you manage and generate reports across multiple Deployment Server systems and integrate additional Web applications available in the client and server management suites. As an IT administrator. See Deployment Web Console Basics (page 369). Jobs. including the ability to remotely access and manage computer devices. Recovery. The Web console reads and writes directly to the Deployment Database and can be accessed as a standalone Web application or integrated within the Altiris console: The Deployment Web Console provides basic deployment and management functionality from a Web browser. including Inventory. and identify the state and status of computers in your system. including remote control. and Application Metering solutions. PXE server configuration. The Deployment Console is a Windows-based console with complete deployment and management features. or click Programs > Altiris > Deployment Solution > Deployment Web Console. and view multiple Deployment sites. security. To launch the Deployment Web Console.Managing from the Deployment Web Console Deployment Solution provides both Windows and Web user interface consoles to deploy and manage computer devices across local or wide area networks.8 SP2 368 . schedule deployment jobs. Software Delivery. To launch the Deployment Server Console. image editing.

Click to apply settings. Deployment Web Console Basics The Deployment Web Console is a feature-rich Web application that uses Microsoft . New Computer. From the Deployment Web Console you can build simple or complex deployment jobs to migrate users. Up/Down arrows. Distribute Software. Find. Expand. You remain on the current page after clicking Cancel. Click to expand or contract feature sections within the Web page. New Job.The Deployment Web Console also provides features and functionality to integrate with Microsoft’s Automated Deployment Services (ADS). Refresh. deployment job or other system components. Click to change the order of items in a list. You can also filter computers by operating system or jobs by task types. Click to add new items or objects within a group. New. Click to update console information after adding or deleting items.8 SP2 369 . groups. Run Script. Distribute Personality. Altiris® Deployment Solution 6. The Deployment Web Console includes a graphical user interface with distinct icons to identify type and status of the computer. See Automated Deployment Services (ADS) (page 385). Click to cancel out of an action or delete a property or name. Cancel. See Basic Tasks from the Deployment Web Console (page 372) for steps to manage and deploy computer devices from the Deployment Web Console. The Deployment Web Console also loads from the Deployment tab in the Altiris Console for integration with the Client Management Suite and Server Management Suite. creating groups. install software and image hard disks — all from a Web browser. Example: the order of tasks in a deployment job. Click when Adding New Computers. set up new users. Click to create a new job. Click to change the user’s task password on multiple Deployment servers. Click to find or filter selected computers in a group or jobs in a folder. such as new computer accounts or conditions sets. You remain on the current page after clicking Apply. deployment jobs. properties or names. and Capture personality. and package files. or making other screen changes.NET and other built-in services to provide real-time access to computer resources. Task User Passwords. Users have access to the job tasks: Copy file to. Apply.

Click to set these features set properties for the Deployment Web Console and the ADS features. run Remote Operations. Click to delete an item. When running Deployment from the Altiris Console. you can view the computer status in the Details pane. You can now manage computers by defined groups or filtered by client type. When a computer or group is selected. you can also identify managed computers within the Altiris Console Collections created by Notification Server. licensing information for each system. computer model. or other properties. the Details pane shows a list of computers in the group and gives basic information about each computer. Click to run a process or actuate a feature.Go. Computers pane From the Computers pane. The Find detail bar appears in the Details pane to filter computers by a set criteria. Elements of each group appear in the Details pane with features to view properties and run management tasks. Deployment Web Console options. It gives you a graphical view of your network and provides features to build jobs.8 SP2 370 . type. software packages and scripts. These collections identify only managed computers with the Deployment Agent installed. Help. Like all Deployment consoles. Click to view supported Deployment Servers. the Deployment Web Console is divided into several panes to organize computers. About Deployment Web Console. you can traverse multiple Deployment Server systems and navigate the treeview of each system to select computers or computer groups. displaying computers by operating system. deployment jobs. or Assigning and Scheduling Jobs for each selected computer or group. and general information. See Managing Altiris® Deployment Solution 6. you can view and select New Computers and other computer groups defined for your organization. Delete. Click to open help documentation for the Deployment Web Console. and report the status and state of all of your computer resources. When a computer is selected. store and access jobs and packages. including a list of jobs that have run or are scheduled to run on the computer and the status of each job. You can view Computer Details. By drilling down into a selected Deployment Server system.

See Scheduling Jobs from the Deployment Web Console (page 419) for complete information about setting up. deploying computers. or saved for a later time. where they are replicated to the source Deployment Server. order tasks. and task list. Jobs are organized by Deployment Servers. Jobs can be run immediately. You can organize the job objects using the New job folder command from the Select Action list. Once a job is created.8 SP2 371 . or remove tasks. or deleting tasks. Jobs pane Use the Jobs pane to create and build jobs with specified deployment tasks. modifying. listing all job folders and individual jobs for a specific site under the name of the managing Deployment Server. It also shows the computers or computer groups to which the job is assigned. the computer groups and managed computers for that system appear. When you select a Deployment Server in the list. importing. the Details pane displays a list of jobs in the folder and provides basic information about each job object. changing configurations. all computers and computer groups for that system appear. From the Jobs pane you can schedule and execute deployment jobs such as creating images. the Details pane displays information about the job to set up conditions. you can change it by adding. and viewing properties from the Computers pane. or installing software. It extends the user interface features when working in the Computers or Jobs panes. When a job is selected. running remote operations. status. When you select Deployment Servers in the Computers pane. Details pane The Details pane is the right-hand pane in the Deployment Web Console. When you select a job icon in the Jobs pane. such as its state. and managing computers from the Jobs pane. Jobs in one Deployment Server group can be scheduled to computers in another Deployment group. scheduled to run a particular time.Computers from the Deployment Web Console (page 398) for complete information about organizing computers. Altiris® Deployment Solution 6. and add. Jobs can also be replicated directly to another system using the Move job command in the Details pane. When you select a specific Deployment Server. modify. the Details pane lists all associated Deployment Server in your organization and displays links to access the computers and jobs for that site.

the computers and computer groups are listed. The selected operation runs on the managed computers. Basic Tasks from the Deployment Web Console The following are basic tasks you can perform using the Deployment Web Console as a stand-alone console or from the Altiris Console. See Automated Deployment Services (ADS) (page 385). Show physical devices. a secondary page may open to run the operation.Deployment Web Console Options Click the Console Options icon in the toolbar of the Deployment Web Console. The Deployment Web Console appears with the following console options. the MAC address cannot be found and the client-server connection is rejected. Altiris® Deployment Solution 6. Remote Computer Operations (page 372) Assigning and Scheduling Jobs (page 373) Finding and Filtering Computers and Jobs (page 373) Remote Computer Operations From the Deployment Web Console. See Remote Operations (page 415) for a list of provided management actions. Depending on the selected action. 2. Reject Client Computer Connections To manage unwanted client computers from attaching to the Deployment Server. The computers appear as a Selected Computer. Clear the computer and job selections after scheduling. Show blade servers as Rack/Enclosure/Bay objects in the Computer pane. Click a Deployment Server or other computer group in the Computers pane. From the Selected Computers list. 3. Set the appropriate values and click OK. If the client tries to connect to the server. Select the managed computers to select the check box for specific computers. Verify actions to the user before scheduling jobs or performing other operations. select an action to perform on the managed computer. Deploy and manage using the Microsoft ADS features.8 SP2 372 . Select this option to clear selected computers or computer groups and the associated jobs assigned to them. use the Reject Connection Computer Action to remove the client’s MAC address and other information from the Deployment database. Microsoft Automated Deployment Services (ADS) Enable ADS. 1. you can quickly deploy and manage computers onthe-fly using remote operation features. In the Details pane. Prompt before performing operations.

you can enter a search string for a computer name in the Find field and filter by operating system.8 SP2 373 . Click a Deployment Server or another computer group in the Computers pane. The jobs appears as a Selected Job. click the clear icon. . See Find a Computer in the Database (page 417) and Creating a Computer Group Filter (page 417). Select the check box for one or more jobs in the Details pane. Click the Deployment Servers link in the Computers pane to view a list of all available Deployment servers Altiris® Deployment Solution 6. Scheduling Jobs After selecting computers or computer groups and assigning jobs. If you select a computer group in the Computer pane. The computer appears as a Selected Computer.Note Virtual client computers cannot be rejected. 2. From the Deployment Web Console. Assigning and Scheduling Jobs From the Deployment Web Console. 3. you can enter a search string for a job name in the Find field and filter by task types. To reject client computers 1. Deployment Server Configuration You can configure all the options for a single Deployment Server from the Deployment Server Options page from the Deployment Web Console. Click the Computer actions drop-down list. Finding and Filtering Computers and Jobs You can search for or filter computers or jobs within a selected group or job folder. See Scheduling Jobs on page 373. Select the check box for specific computers or computer groups in the Details pane. To clear the computers or jobs and reselect. If you select a job folder in the Jobs pane. and select Reject Connection. Click Run Now or Schedule to run the selected jobs on the selected computers. 1. Select the check box next to the computer whose connection you want to reject. 2. 3. Click a job folder in the Jobs pane. in the Computers pane. you can now select to run the job immediately or schedule it for another time. Secondary pages appear to set scheduling values. you can assign jobs to computers and schedule them to run immediately or at a later time. click a Deployment Server name. A list of client computers and groups appears in the Details pane.

appears in the Details pane. Select a transfer rate from the Speed list. Specify a static TCP port for file transfers to the clients or choose to assign it dynamically. The default value for static port is 0 and causes the server to use a dynamic port. Deployment Agent/Deployment Server file transfer port. double-click a particular Deployment Server in the Details pane to view the Deployment Server Options page. Then. This is the file transfer speed between the Deployment Server and client computers. in percentage. Change Sysprep Settings. click Add product key to enter product key (up to 29 characters) information. The options are Serial Number (SMBIOS). Key. Remote control ports. Asset Tag (SMBIOS). UUID (SMBIOS). changes to computer names is not reflected in the Web console. for the scheduled imaging job. Synchronize display names with windows computer names. or MAC Address (SMBIOS). If the Port 1 is already in use. Enter the global Sysprep values you want to use when creating or distributing disk images. The transfer port range is 1 to 2147483647. Display imaging status on console (percent complete). Port 2 is used for remote control. Add as many product keys as needed and select a product key from one of the keys listed. To modify a product key. Speed. Specifies the primary lookup key type used to associate a new computer with a managed computer. select the product key and click Modify product Altiris® Deployment Solution 6. This setting is useful if you have a firewall and need to use a specific port rather than a dynamically assigned port. Shows the status. Port 1 and Port 2 by selecting the Remote control ports check box. You can change the following options: Global (page 374) Maintenance (page 375) Agent Settings (page 375) Security (page 380) Logon (page 385) Global Set global options for the selected Deployment Server. Automatically updates the display name of the managed computer names in the Web console when the managed computer name changes. Then. You can specify the two ports. SysPrep Settings OS Product Key tab Click the drop-down arrow and select an Operating System from the list. Synchronization option is off by default. If this option is not selected. The remote control port ranges from 0 to 65535. By default the check box for Remote control ports is not selected and dynamic port is used while remote controlling. The computer names do not have to be synchronized for the Deployment Server to manage the computer.8 SP2 374 . Click Change Sysprep Settings to view the Sysprep Settings dialog.

Click this link to change Automation Agents Settings. 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.key. Remove inactive computers after _____ days. The program continues to retry until the job succeeds or until the job is cancelled. To delete a product key from the list. Maintenance Retry failed imaging jobs immediately. Automatically replace expired trial licenses. Altiris® Deployment Solution 6.000 is valid. Select this option to force these settings when adding a new computer. Modify default settings. Immediately retry a failed image deployment job. log entries remain in the history. select the product key and click Delete product key. Note If a product key is being used by another task. Agent Settings Use the Agent Settings tab to control the default agent settings for new computers. Modify default settings. Production Agent Settings The description below is for client computers running the Windows or Linux operating systems. Automation Agent Settings. Select this option to force these settings to effect new client computers until you can change the settings using the Deployment Console. but any number between 1 and 10. See Automation Agent Settings (page 379). Allows Deployment Server to automatically assign a permanent license to the managed computers after the trial license expires. Force new Automation agents to take these settings. Delete History older than _____ days. See Production Agent Settings (page 375). a message prompt appears that the product key is currently in use and you cannot delete the product key until the task completes. no entries are kept in the history. Production Agent Settings Force new Production agents to take these default settings. Click this link to change Deployment Agent Settings for Windows and Linux systems. The default value is 30 days. Specify the number of days you want to keep inactive computers in the Deployment database before they are deleted. If this option is not selected. This option is only available if you select Force new agents to take these default settings.8 SP2 375 . Specify the number of days an entry is kept in the history until it is deleted. If the number of days is set to 0.

which saves bandwidth when running deployment tasks on slower connections.Click the Modify default settings link to set or modify Deployment Agent for Windows and Deployment Agent for Linux properties from the same dialog. Otherwise. This helps keep rogue computers from connecting to unauthorized Deployment Servers. Try using defaults on both the client and Deployment Server if you are having problems connecting. This forces clients to realize the network is down. 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. your clients cannot connect. the client connection is allowed. Refresh connection after idle. Key file. The Deployment Server closes the connection after the specified time and immediately tries to re-open the connection. Altiris® Deployment Solution 6. 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. Server Name. Enter the IP address or NetBIOS name of the Deployment Server computer. Enter the group multicast address. 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. Port. Specifies the number of routers the multicast request is can pass through. Multicast Address. Enter the port number distributing the multicast address. Select this option to valid the client computers that are trying to connect to the Deployment Server.8 SP2 376 . Discover Deployment Server using TCP/IP multicast. Server Connection Connect directly to this Deployment Sever. The Production Agent Settings dialog appears. The client computer checks the Deployment Server authentication key and if a match is made. Enter or browse to an authorized key. 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. making it easier to find the closest Deployment Server. The default checking is of 28800 seconds or 8 hours. Enter the port number communicating with the Deployment Server. Select the Refresh connection after idle check box and set the refresh time by seconds. The port number must match the number set on the Deployment Server. minutes. Port. Abort files transfers if the rate is slower than. Address/Hostname. It is recommend keeping this setting above 28800. TTL. Enable key-based authentication to Deployment Server. Enter the NetBIOS name of the computer running the Deployment Server. hours. Ensure that the multicast address and port match those set up on the Deployment Server. Preserve bandwidth on slower connections by selecting this option. or days. Select this option so that the client receiving the Deployment Agent connects to the Deployment Server you selected to configure.

This feature overrides the Power Control option from the Deployment Server to Force applications to shut down without a message. 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 for the user to be prompted before running a program or executing file copy commands Remote Control. Select to allow encryption from this managed client computer to the Deployment Server. Altiris® Deployment Solution 6. Click to not continue without receiving a response from the user. you need to decide whether to continue or abort. Select the days and set the start and end times when access to the Deployment Agent is denied.8 SP2 377 . Abort the operation. The default setting is to NOT allow the computer to be remote controlled. You can set a default time before running or aborting the commands. Select for the user to be prompted before running the Remote Control commands. the Deployment Server does not communicate with the Altiris Client on the managed client computer. Allow this computer to be remotely controlled. Require encrypted sessions with the servers. the client computer can connect (but is not required to connect) using encryption. Copy file and Run command. the administrator can remote control the selected computer. This allows encrypted data transmissions between the Deployment Server and the Deployment Agent on the client computer. Select when the Deployment Server is denied access to the Deployment Agent. If this option is selected and the option to allow encryption in the Deployment Configuration tool is not selected. Security This page lets you secure data between the Deployment Server and the Deployment Agent. Click to continue without receiving a response from the user. Select the Allow encrypted sessions with the servers check box to allow Deployment Server to transmit using encryption protocols. you must open the Deployment Configuration tool (Start > Programs > Altiris > Deployment Server > Deployment Configuration tool). Select the time for the user to respond and either continue with the operation or abort the operation. Select the amount of time you want to wait for a response. To enable encryption protocols. and select one of the following: Continue the operation. Select to require encryption between the managed client computer and the Deployment Server. Time to wait for response. If selected. If one of the Prompt the user before performing actions is selected and the user is not at the computer to respond. Prompt the user before performing actions Shut down and Restart. Encrypt session communication with Deployment Server.Access Set these commands to control how the client handles requests from the server. and select the Transport tab. Select for the user to be prompted before shutting down or restarting the computer. If you select this option.

Select to hide the Altiris Client icon in the system tray of the managed computer. Select it to enter a file name for the log and the maximum size for the log file. Click to save information to a log file. Maximum size. which includes only the User Prompts and Remote Control tabs on the Altiris Client Settings dialog. Use this tab to save the Deployment Agent for Windows log file. By default. File name. Enter the maximum number of bytes for each log file. allowing you to save different types and levels of information to the log files. If the option is selected and the user does not know the password. The default is to save the log file to the \Program Files\Altiris\AClient\AClient. older data is dropped from the files. Hide client tray icon. so it is recommended to provide maximum file size. Log errors. Proxy Typically. older data is dropped from the files. the option Save log information to a text file is cleared. and debugging data using this dialog. Note If the log exceeds the specified size.Note Selecting encryption options slows down the communication path between Deployment Agent for Windows and the Deployment Server. informational errors. Log File The Log File property page controls how data is logged and saved in a Deployment Server system.log file. Select this option to list comprehensive debugging information in the text file. Click Edit Password to change the password settings for users trying to access the Admin properties. Log debugging information. 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. If you hide the icon you are required to run AClient. Save log information to a text file. A Altiris® Deployment Solution 6. You can save a text file with log errors.8 SP2 378 . Password protect Admin properties. You can maximize the size of the log file to save all selected data. so do not use encryption unless it is necessary for high security environments.exe -admin to view and modify the complete administration properties from the managed client computer. 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 forwards or re-creates the multicast packets. If the log exceeds the specified size. they have rights only to open the User Properties. Select to allow users on the managed computer to access the Admin properties only if they enter the set password. Enter the name and path of the log file. Select this option to save a list of procedural steps run on the client computer.

or days for managed computers send multicast advertisement. Linux. Select this option to disable the direct disk access for automation communications. Automation Agent Settings You can configure property settings for the Automation Agents (DOS. The default is C: Force all programs to close when shutting down.8 SP2 379 . and Windows PE Automation Agents. Linux. minutes. Specify the Windows boot drive. it receives the default agent settings from Deployment Server for drive mappings. Set these options to control how the managed computer can act as a proxy agent. 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. When a new client computer connects. You can remotely maintain important agent settings and update settings as required from the console. and LMHost entries. Set the time by seconds. or days for managed computers to delay jobs until after system startup. Prompt for a boot disk when performing automation jobs. Forward Wake-On-LAN packets. authentication. It is required that the F Drive be Altiris® Deployment Solution 6. Select the Force new Automation agents to take these settings check box. Each client computer still has the capability to maintain its unique settings for the Deployment Agent for DOS as set in the Boot Disk Creator. Select if you want the managed computer to forward Wake on LAN packages. Synchronize date/time with Deployment Server. hours. Advanced Disabled direct disk access for Deployment Agent for DOS (BootWorks) communication. Send multicast advertisement every. Startup/Shutdown Delay starting jobs after system startup.managed client computer set up as a multicast proxy simply acts as a Deployment Server and advertises the server’s name and IP address through multicasting. Select this option to shut down applications when using Power Control features. and click the Modify default settings link to view the default settings for the DOS. Forward Deployment Server multicast packets. The user is still prompted to Abort or Continue the shutdown. Select this option to synchronize the system clock of managed computers with the time of the Deployment Server. and Windows PE) for specified computers or computer groups. Drive Mappings Set drive mappings used by the Automation Agents to access hard disk image files and other packages from a specified network drive. Or you can set the managed computer as a proxy to send Wake On LAN packets. minutes. Select this option to prompt for a boot disk while doing any automation jobs. Set the time by seconds. hours. Specify the drive that the client computer can boot from. identifying the type of traffic this managed computer can forward from the server.

Enter the name of the Domain or Workgroup of the user that the Automation Agents can log on to map the network drives. 2. Note You must select a shared folder in this field. You can create users and groups and set scope-based rights. Domain/Workgroup. import both Active Directory users and groups. Click the Add LM Hosts icon.mapped to the Deployment Share. The associated credentials for each network drive must have the appropriate rights for the Automation Agents to access files. You can also add local users and local groups. Network These settings allow you to match the IP address with the computer name. as maintained in the LMHosts file in automation partition. 4. 1. Enter a UNC path. Drive. Enter the password. Enter the IP Address.8 SP2 380 . User name. Example: F: \WebDeploy\Image files. Security This features lets you enable or disable security for the Deployment Server. 3. Enabling Security (page 381) Rights (page 382) Setting Permissions (page 383) Altiris® Deployment Solution 6. Use the Security tab to provide enable/disable security and to add local users and local groups. Select the drive letter of a shared folder. Enter the Computer Name to associate with an IP address. Path. Authentication Enter the login credentials that Automation requires to map network drives. and assign rights for users to perform Deployment Solution operations. Enter the user name that the Automation Agents can use to log on so they can map to the specified network drives. Password. You can also import both Active Directory users and groups and assign rights to all of them. but the Automation Agents can only map and access files from a shared folder. Click Apply. You can also map other file server directories when storing large numbers of image files or deployment packages. From the browse window you are allowed to select any type of folder. You can click Lookup IP and the IP address field automatically fills in the IP address of the computer you entered in the Computer Name field.

A list of all available Deployment servers appears in the Details pane. 3. See Importing user groups from Active Directory (page 382). 1. Click New Group from the toolbar. 4. 8. Security is now enabled. Membership Groups Assign the user to previously created groups. Add users from Active Directory (not groups) by providing the user names and domain to which they belong. 2. Click the Security tab.com. If enabling security. you can assign the user to a group with Administrative rights. Altiris® Deployment Solution 6. such as sam@abc. select the Enable Security check box. and click Apply. Deployment Web Console accesses the Windows Active Directory server to validate the user password. The users are added to the Deployment Database. 2. Any subsequent users do not have rights and cannot be added to any group by default. 1. Notes If you add Active Directory Syntax name. Click Membership to view the membership groups and all available groups. Click the Deployment Servers link in the Computers pane. Click Import User on the toolbar to view the Import Active Directory User page. When logging on with the imported AD account. To enable security 1. Click Rights to view the available rights. Click Apply to add the user. However. Importing users from Active Directory You can import users from Active Directory. Click New User to add new user information. the field Domain name becomes disabled. 6.Enabling Security You can enable security by first creating a user with Administrative rights or selecting a user who belongs to a group having Administrative rights and selecting Enable Security. No default group membership is applied nor any default rights are applied unless this is the first user you have imported. Type the user details. You can also import new users from the Active Directory. Enter a name for the group and a description. 5. 7. you still need to assign the users to security groups with appropriate rights and permissions. You can now create users and groups and assign permissions to computer groups and job folders. Select or click the specific Deployment server in the Details pane to view the Deployment Server Options page.8 SP2 381 . Note The first user automatically gets the administrative rights. Now that you are an administrator. 2.

and upon matching doesn't prompt for user credentials. A brief explanation of each deployment server right that can be assigned is detailed below: Administrator Lets you access all available features from Deployment Web Console.Importing user groups from Active Directory You can also import user groups from Active Directory. Lets you view and set RapiDeploy options. Lets you create custom data sources options. and it tries to access the Deployment Server Console. by default you have the rights to schedule job on all computers. click a user and click Rights. Click Import Group on the toolbar to view the Import AD Group page. This method of authentication is the same for AD user and AD group also. Lets you view rejected computers in Deployment Solution and change their status. Click Apply to save the changes. DS checks the authentication with the logged on user. Options Console Options Global Options Domain Accounts Options RapiDeploy Options Agent Settings Options Database Tokens Manage Rejected Computers Refresh Clients Allow scheduling on All Computers Groups Altiris® Deployment Solution 6.8 SP2 382 . Lets you view and set console options. and any user who is a part of the group tries to access the Deployment Server Console. If you have Administrator rights. Lets you view and set global options Lets you view and set domain accounts options. Lets you view and set agent settings options. To verify. and set database tokens. DS Authentication If the user is already in the DS database. From the Security tab. DS doesn't prompt for credentials. Add groups from Active Directory by providing the group names and domain to which they belong. 2. Lets you schedule jobs on all computers. 2. After selecting all applicable rights. Similarly. Select the check box for every right you want to grant. 1. Rights Rights allow you to set general rights for a user or group. You can view. add or change the rights assigned to each console user. irrespective of the state of the Allow scheduling on All Computers check box. if a group has already been added in the DS database. 3. You must have Administrator rights to enable security. Lets you Refresh Deployment Solution clients. The groups are added to the Deployment Database. create. You can grant this right to a specific user or a group. 3. click Apply to save your changes. use the following steps: 1.

Select or click a specific Deployment server in the Details pane to view the Deployment Server Options page. 7. You cannot explicitly deny permissions to computer or job objects for users with administrator rights. Notes If you do not have administrator privileges. computer groups. Click a specific computer to view its property. The description of each permission group appears under Description column. inventory. 1. 2. Distribute Software. Log on as a user with administrative privileges. Select Permissions from the Computer actions drop-down list. Click the Deployment Servers link in the Computers pane. 5. 4. Distribute Personality. and Capture Personality when creating or modifying jobs. Import/Export Option Task Password Use PXE Configuration Utility Setting Permissions Set permissions for jobs. Altiris® Deployment Solution 6. Click Advanced to view the advanced options associated with the selected permission group. A list of users or user groups appears. and scheduled jobs status. see Evaluate Permissions (page 384). Run Script. 8. Notes Administrators have access to all objects with unrestricted rights and permissions. 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. you cannot view Permissions option. This page contains Allow as well as Deny check boxes. 9. Click the Security tab. You must have Administrator rights to enable security. A list of all computers belonging to the selected Deployment Server appears. computers. Select the check box for the permission group to allow the permissions you want to grant for the selected user or user group. job folders. 6. You can select a user or a group and grant permissions accordingly. You must have administrative rights to access this option. and physical devices. 3. For information on evaluating permissions. Lets you centrally update passwords for users and groups so they can access the tasks: Copy File to. Lets you set up and modify PXE Configurations. Lets you import and export any jobs/computers.Administrator Lets you access all available features from Deployment Web Console.8 SP2 383 .

Altiris® Deployment Solution 6. If a Web Console user does not have permissions to run all tasks the job contains. You can evaluate permissions in three ways: If none of the Allow or Deny options are selected for a permission associated with a subfolder. the permission to deny the privilege is the one enforced. which is the one it uses. but not all permissions in the selected group are allowed. and not after the execution of the job. This is irrespective of any other privileges. the object in question looks in the current location and up the tree for the first permission it can find.8 SP2 384 . This type of inheritance can be confirmed with the message that appears for the subfolder. If a user has “Schedule this task” permission for a certain task and the user schedules the job and the user modifies the job by adding another task. This is true only if none of the 'Allow' or 'Deny' options are specified for a permission for that user. Evaluate Permissions Identify the combined permissions of groups and containers with contrasting permissions. for which the schedule task permission is not allowed. It displays a partial check mark (check mark with a grey background) when at least one. When a user is associated with multiple groups. which is called tri-state check box. Permission Rules Permissions received through different sources may conflict with each other. You can identify effective permissions for each object by resolving any possible conflicts. the users belonging to that group inherits the same permissions as that of the group. it displays no check mark if none of the permissions in the selected group are allowed. and click Apply. Deny overrides Allow. And finally. If a user group is associated with some permission. In this scenario. the user cannot schedule it. This is because the Web console checks the permissions only before scheduling the job. it inherits the options specified for the permission associated with its parent group. click Apply permissions recursively to all child objects to assign the permissions. The following permission rules determine which permissions are to be enforced: Permissions cannot be used to deny the user with Administrator console rights access to use any console objects or features. one group could be allowed permission at a particular level while the other group is denied the same permission. This tri-state displays a full check mark when all permissions in the selected group are allowed. Permissions are represented in three different stages according to the state of the check box. the second task also gets executed. Permissions do not flow down an object tree. Instead. Give permissions as per your requirements. To assign permissions to multiple groups.10. the user is not allowed to run the job. 11. User permissions take precedence over Group permissions. Notes If a user does not have the “Schedule this job” permission for a particular job.

All specified ADS controllers are listed. Automated Deployment Services (ADS) From the Deployment Web Console. select the servers from the Details pane and click the Task Password icon on the toolbar. devices and job templates appear. Enter the name of the user. 2. 5. you can utilize and extend features of Microsoft’s Automated Deployment Services (ADS). click the Add icon to enter the computer name where the ADS controller is installed. in the toolbar of the Deployment Web An ADS Controllers collection appears in the Computer and Jobs pane. 4. and click Advanced to view the individual permissions related to the selected permission group.The Deployment Web Console displays the simple as well as advanced options of granting permissions. In the Computers pane. Username. The simple option displays only the Allow column. Logon This option lets you set user credentials for the Deployment Server. Enter the domain name for the specified user. Example: a Modify permission for a job folder can contain different security permissions than a Modify permission for a computer group. click Advanced to view the individual permissions related to the selected permission group.8 SP2 385 . Confirm Password. A list of all permission with Allow and Deny check boxes appears. Click the Console Options icon Console. Enter the login credentials and access paths on this page. select the check box for a specific permission. Enter the password to confirm the entry. Altiris® Deployment Solution 6. but only if Role Base Security is enabled for the server you selected. You can now manage computer devices using standard ADS features. All ADS controllers. Security permissions are grouped together and appear as a single Permission group under Simple option. If you want to change the Task Password for multiple Deployment Servers. Password. and click Apply. click ADS Controllers. Select the Deny check box or clear the Allow check box for the specific security permission. Enter a password for the specified user. Enter credentials and ADS paths as in step 4. click ADS Controllers. Domain. 1. In the Jobs pane. To view all the permissions related to a specific permission group. The user can access the server through the Deployment Web Console. whereas the Advanced option displays both the Allow and Deny column. From the Details page. You can use the Advanced option to view all the individual permissions that together form the Permission Group. 3. If you want to exclude a specific security permission. This grouping of permissions varies from object to object. Select the Enable ADS option.

Organize using Deployment Collections.8 SP2 386 . Deploy and manage computers from the Deployment tab while managing other aspects of your organization such as inventory reports. From the Configuration tab. assign jobs. while providing additional collections. you can transmit data from the Deployment Database to the Notification Database from which you can generate reports. Employ the Schedule Wizard. Altiris® Deployment Solution 6. See Installing Deployment Solution from the Altiris Console (page 14). By setting polling intervals on the Altiris Agent and the Deployment Server Agent. From the Reports tab. application management. In use. create reports for all Deployment Servers computers devices and deployment tasks across all sites. Computer devices can now be grouped on criteria such as operating system. reports and other basic Notification Server features from the Altiris Console. software delivery.Deployment from the Altiris Console Deployment from the Altiris Console provides additional features and functionality for managing and deploying computer resources using Deployment Solution. workstation or server. Set Security. Using Deployment Solution from the Altiris Console Integrate with other IT solutions. All other Deployment security is set from the Deployment Server Console (the Windows console). and other groupings. patch management and other administration tasks. set NS security to limit users from using the Deployment tab. open the Schedule Wizard to select computer groups. mobile computers. and schedule jobs to run immediately or at a specified time. Generate Reports. computer type. remote control. From the Tasks tab. the Altiris Console opens and displays the Deployment Web Console.

However. See Creating Deployment Server AClient Packages (page 388). Click Speed. Click Deployment Servers in the Computers pane. Click Apply. The available Deployment Servers appear in the Details pane. and Domain name.8 SP2 387 . 4. Click Change Task User Password icon on the toolbar. This is the computer name of the Deployment Server. See Installing AClient to a Notification Server Client (page 388). you can identify and add existing Deployment Servers to appear in the Computers and Jobs pane from the Deployment Web Console. password. type the name of an existing Deployment Server. in most cases. Enter the user information for all 4 fields on the page. To change task passwords 1. You can create a package to install AClient to the existing Notification Server clients. or click the New Server icon. Note You can also remotely install Deployment Servers from the Deployment Web Console. Select the speed of the network connection for the Deployment Server from the drop-down list. enter a username. Click Add Deployment Server in the Computers or Jobs action list. 3. You can also assign the Deployment Server AClient package to computers. If Deployment Solution security is enabled for the Deployment Server. See Viewing Notification Server Clients without AClient (page 388). and Capture Personality when creating Jobs. 4. Distribute Software. 3. Run Script. Distribute Personality. To consolidate multiple Deployment Server sites. 5. From the Deployment Servers page. 2. 1. See Installing Deployment Solution from the Altiris Console (page 23). Click one or more Deployment Servers you want to change the task user passwords. 2. Altiris® Deployment Solution 6. this tab is only visible to administrators and users who have been granted the appropriate rights to modify task passwords.Adding Deployment Servers You can manage multiple Deployment Servers from the Deployment Web Console. Task Password options This feature lets you centrally set or change user passwords for multiple Deployment Servers to they can access the tasks: Copy File to. Click Credentials. Configuring the Deployment Server AClient The Deployment Server AClient option lets you view the Notification Server clients that do not have AClient installed. Enter the Deployment server’s port number if it is different than the default value.

In the left pane. The task is enabled. To select the computer collections. In the Altiris Console. 9. select the Enable check box. For more information. click All NS Clients without AClient. select Configuration > Solutions Settings > Deploy and Migrate > Deploy > Deployment Server AClient Configuration > Deployment Server AClient Install. The Collection Selector dialog box opens. Creating Deployment Server AClient Packages You can create the Deployment Server AClient package that is used in the Installing AClient to a Notification Server Client (page 388) task. 6. In the Altiris Console. 2. the All NS Clients without AClient page appears with a list of all Notification Server clients that do not have AClient installed. 3. make the required changes. In the right pane. Installing AClient to a Notification Server Client You can install an AClient to the Notification Server client by creating a task to install the AClient. To create a task to install AClients to Notification Server clients 1. To view the Notification Server clients without AClient 1. click the Configuration tab. In the Altiris Console. click the Configuration tab. The task that you create uses the package that was created on the Creating Deployment Server AClient Packages page. 5. see Creating Deployment Server AClient Packages (page 388). Altiris® Deployment Solution 6. To enable the task. OS Version. You can also double-click a client to view more details. click the Configuration tab. User. Click Apply. you can view the Notification Server Clients that do not have AClient installed. 7. You can view details such as Name. In the left pane. OS Name. The AClient installation task is saved. select Configuration > Solutions Settings > Deploy and Migrate > Deploy > Deployment Server AClient Configuration > All NS Clients without AClient.Viewing Notification Server Clients without AClient In the Altiris Console. 2.8 SP2 388 . Click Apply. Domain. In the right pane. and so on for each client. Select the computer collections and click Apply. 4. Select the required scheduling options. To create the Deployment Server AClient Package 1. 8.

Configuring the Deployment Server Agent To update Notification Server collections and generate reports from the Altiris Console. 2. For large Deployment Server systems. 5. Click the Programs tab. Resynchronize all Deployment Server computers/tasks for this configuration. select Configuration > Solutions Settings > Deploy and Migrate > Deploy > Deployment Server AClient Configuration > Deployment Server AClient Package. 2. To run deployment reports. set the polling intervals from the Configuration tab. You can select all Deployment Servers or identify an individual Deployment Server. Enter credentials for the Deployment Database selected in the list. On the Package tabview. Click to completely transmit all Deployment Server data to the Notification Database. Select a Deployment Server. The new agent configuration appears in the list. A list of Deployment Servers is listed. 6. specify the Name and Description for the package. Role-based user name.8 SP2 389 . Enter credentials if Deployment Solution security has been enabled using the Deployment Server Console. Altiris® Deployment Solution 6. Check the command line and the specified parameters in the Command line field. 3. Click the Reports tab on the Altiris Console. Database Login ID. 4. Click Apply. Select a polling interval for that Deployment Server from the list in the Computer/Job Polling Interval box. 7. Set polling intervals for Deployment Servers 1. In the left pane. The Deployment Server AClient package is created. Click Add. Enable. this process can take several minutes and require large amounts of bandwidth. Select the Deployment Server to configure.2. you must configure the Deployment Server Agent (see Configuring the Deployment Server Agent on page 389) to transmit data between the Deployment Database to the Notification Database. Click Update Distribution Points. see Exporting and Importing Deployment Jobs (page 393). The Deployment Solution reports are generated from the Altiris Console from data stored in the Notification Database. Select to enable communication between the Deployment Database and the Notification Database. Generating Deployment Reports from the Altiris Console Deployment from the Altiris Console furnishes features to generate comprehensive reports detailing computer information and deployment jobs for all Deployment Server sites. 3. Click Reports > Deploy and Migrate > Deployment. Use this feature carefully. For more information. 1.

Select reports specific to Client Information. See Configuring the Deployment Server Agent (page 389). Note Package Servers can only replicate packages on Deployment Server installations set up as a simple install. package files are accessed quickly from local package libraries. Windows Workstations.3. and other package files for building deployment tasks for use across multiple Deployment Server installations. or schedule a report to run. Overview of Package Servers Package Servers are a basic feature of Notification Server and are used to reduce network traffic and HTTP download times when deploying packages across your system. software packages. Click a report option to run. A description of each report appears in the Details pane after it is selected. Package Servers replicate and transmit packages from a central computer to local computers during off-peak hours. From a central Deployment Server installation. Notification Server lets you identify managed computers running the Altiris Agent as a Package Server. where all Deployment Server components are on a single computer. 4. These collections identify computers running the Deployment Agent and meeting the criteria for each collection. Job Status. Server Information. scripts. When deployment tasks are executed. and so on. At each polling interval the new data is transmitted between the databases and updated in the Deployment Web Console. packages can be built and saved to a local Library structure. Altiris Console Collections From the Deployment Web Console you can view and order computers based on Altiris Console Collections created automatically in Notification Server and viewed from the Altiris Console. You can assign jobs and perform operations to these collections from the Deployment Web Console.8 SP2 390 . view. or Software Deliver Execution Status. Altiris® Deployment Solution 6. Windows Servers. such as Mobile Computers. Collections are updated between the Notification Database and Deployment Database. Job Information. where they are replicated to other Deployment Servers and used in deployment jobs for each Deployment Server system. Using Package Servers to Replicate Deployment Jobs Deployment Solution takes advantage of Package Servers (a basic component of Notification Server) to automatically copy images.

When the Deployment is installed and enabled on the Altiris Console (on Notification Server). all items to be replicated must reside under this substructure. additional configuration steps are required. There is a global configuration variable that says not to allow any package downloads from the server. leaving the DS Install in a state where there is no way to access the package. 1. or files are set manually to be copied down to other destinations again. check the Package Server settings and the package settings to ensure that the package can be delivered. and any other package files needed for a Deployment Server Task. Go to your Central Deployment Server directory (default is c:\Program Files\Altiris\eXpress\Deployment Server). you can set up the Deployment Server Library directory structure. and policies are created to take advantage of Package Server technology. RIPs. Setting Up a Central Deployment Server Library Before setting up Package Server in a Altiris Console. After the package files have been copied once (per each package server). 2. Because the package used to replicate files only points to one location. you need to select a central Deployment Server to copy and store all packages to be replicated to other Deployment Server installations.Replication of packages from a central Deployment Server to other Deployment Servers is a one-way process: You can build and copy packages from the Library of a central Deployment Server to replicate to other Deployment Servers. Altiris® Deployment Solution 6. new files are added to the package. however. any changes made to a destination Deployment Server cannot be replicated back to the central Deployment Server. The DS install package by default is not set to use any Package Servers. 3. collections. After selecting a Deployment Server in your system. they can never be copied again unless the files are updated. however. You need to manually create the Library directory and any other subdirectories on the central Deployment Server. default packages. To complete the setup process.8 SP2 391 . Setting up Package Servers requires three basic steps: 1. The Library is a directory structure that contains your images. Setting Up a Central Deployment Server Library (page 391) Setting Up Package Servers (page 392) Exporting and Importing Deployment Jobs (page 393) Note Before delivering packages.

3. 5. The Package Servers that can receive the files to be replicated. Remember that only the files under this structure are replicated to the other Deployment Server installations. you have two packages and one policy created to help facilitate replication. 4. create subdirectories to use for images. From the left pane. the task creates a CFG file in the temp directory located in the Deployment Server directory. Select Add Package Server from the bottom of the page. RIPs. Altiris® Deployment Solution 6. From the Altiris Console. To set up a Package Server 1. you must copy the file into a temp directory under the Library structure and edit the task to point to the file in the Library\temp directory. Under the Library directory. 2. including: The source of the files and programs to be replicated. Modify the DS Library Package To replicate files stored in the central Deployment Server Library directory. select the Package Source option to configure the path to the files that are included in this package. you can set up Package Servers on other Deployment Server installations. select Server Settings > Notification Server Infrastructure > Package Servers. Copy into this structure any required files accessed during execution of the jobs. Follow these steps to modify the DS Library package: 1. Create a Temp directory for deployment tasks that require a temp directory. The destination directory for the files being replicated. select the Configuration tab. From the right pane. Use the search feature if required. For this task to replicate correctly. Note Any job that is automatically created needs to be modified before running or the default directories cannot be correct. the DS Library package installed with the Deployment Solution (on Notification Server) must be edited with configuration information. or other package files. You can manually modify the packages and enable the policy. Locate and select the Deployment Server computer (or the Deployment Share for each installation) and click Add.2. 4. Select the Tasks tab and select Deploy and Migrate > Deployment > Deployment Server Replication > DS Library. The programs that will run after the files are copied to the Package Servers.8 SP2 392 . 2. Setting Up Package Servers After setting up a Library directory structure on the central Deployment Server computer. Create a Library directory. Example: if you choose to change the configuration of a computer by choosing the Configure option in the Deployment on the Notification Server. 3. After installing Deployment from the Altiris Console.

Enable all applicable Package Servers by clicking the Enabled check box. 4.\Library\Images\NT4. Fill in the Package Location box with the correct path for the Library. As soon as the Notification Server Client’s Configuration request interval time (on the destination Deployment Servers) has elapsed. Example: a deployment task that deploys an image named NT4. Altiris® Deployment Solution 6. Select Apply to save the changes. Choose from one of the following options: Access Package from a local directory on the Notification Server computer Use this option when the central Deployment Server is installed on the same computer as the Notification Server. Select the applicable Package Source method and enter the correct path to the Central Deployment Server Library. 6. enter the destination path: \%COMPUTERNAME%\eXpress\Library 8. When using this option. Exporting and Importing Deployment Jobs After creating a Library directory on the central Deployment Server and setting up Package Servers. you need to create the jobs to copy and run the packages on the managed computers.img instead of the standard . read and follow the instruction on this page.\images\Nt4. 7. the files in the central Deployment Server are sent to the Package Servers on other Deployment Servers.img path. This option lets you specify to which Package Servers you would like this package to be replicated to. These tasks need to be exported from the central Deployment Server to the destination Deployment Servers by configuring the DS Task Import Utility package and modifying the DS Task Import Utility policy on the central Deployment Server. a message warning you about the size of the files in the Package can appear. 5. Select Package Servers. This message is to remind you that all files in this directory will be sent when this package is used. Note Replicated deployment tasks need to reference files created in the Library directory structure.8 SP2 393 . Note Depending on the amount of data in the Central Deployment Server Library. Access Package from Existing UNC Use this option when the Deployment Server that has been configured as the Central Deployment Server Library is not installed on the same computer as the Notification Server. To identify the destination directory (where the package files will be sent) on the destination Deployment Server. At the package destination location.img would use the file path of . select the Advanced tab.3.

bin file from the central Deployment Server. Right-click the jobs you want to export. 2. you can create a job export file. you must edit the program command-line in the task replication package. Browse to the \Notification Server\nscap\bin\win32\x86\DSUtil directory and enter a name for the export file. The method of handling duplicate job names on the destination Deployment Server needs to be changed. choose the Export subfolders check box. By default. Modifications to this package are required when any of these alterations are made: The Deployment Server jobs exported are not saved in a file called Task. Configure the DS Task Import Utility Package After creating deployment tasks and exporting them to the DSUtil directory. To configure or modify how the DS Task Import Utility package is configured.exe program to import deployment jobs.bin. Select Export (or click File > Import/ Export > Export Jobs). When all steps are completed. The Export Jobs dialog appears. If you want to export the task subfolders. (The default file name used in the task replication package is task. Open a Notification Server Administration console and select the Tasks tab. In the right pane. If needed.exe program file is copied to the \Notification Server\nscap\bin\win32\x86\DSUtil directory. select the Programs link. Altiris® Deployment Solution 6. 2. complete the following steps: 1. Security for the Deployment view on Notification Server is enabled on the destination Deployment Server. 3. 1.) The DSUtil directory is added when you install the Deployment view on Notification Server. 3. no changes are required for this package. Click OK to start the export. The DS Task Import Utility package runs the aximport. Note If you use an export file name other than task. This is the same directory where you saved your exported tasks. the aximport.8 SP2 394 .bin. When the Deployment view on Notification Server is installed.To create a job export file After creating deployment jobs to use with the replicated packages.bin. change the name of the file on the command line to match the name of the export file created when the Deployment Server tasks from the central Deployment Server were exported. Select Deploy and Migrate > Deployment > Deployment Server Replication > DS Task Import Utility. the Identification section expands to view settings. you need to configure (or verify) settings in the DS Task Import Utility package.

Select Apply. When the Altiris Agent checks for new policies. Select Deployment and Migration > Deployment > Deployment Server Replication > DS Task Import Utility.bin file. Synchronize Deployment Server Tasks You can update deployment tasks by creating a new task. The next time the Notification Server Client’s configuration timer elapses on the Deployment Servers with Package Server installed.bin file has been created and saved in the \Notification Server\nscap\bin\win32\x86\DSUtil directory. On the destination Deployment Servers. 1. This collection is selected by default. the policy is executed. change the command-line options. To avoid waiting for Notification Server to detect that the file has been modified. If you have Console Security enabled. The policy is now enabled. Open a Notification Server Administration console and select the Tasks tab. Verify that the Applies to Collection option has been configured to use the DS Package Servers collection. The Identification section of the Advertisement page appears by default.bin file and placing it in the DSUtil directory. the default command-line parameters for the aximport. If this is not the desired result.exe. 3.exe task. Modify and Enable the DS Task Import Utility Policy You must enable the DS Task Import Utility policy to allow the Deployment Server tasks to be replicated to the destination Deployment Servers. After all timers elapse. a DOS box appears on this computer and aximport. the username (/u) and password (/p) command line options need to be included for this process to work correctly. 2.exe is run. Before enabling the DS Task Import Utility policy. You can choose to force an update of the package to ensure that the task export file is in the package. 4. Select Apply.8 SP2 395 .exe program are configured to use the Task. /u Database user name /p Database user password Example: aximport. Notification Server compares and detects the new export file by its time stamp.As can be seen in the figure above.bin /o /u administrator /p yourpw See the command-line chapter in the Altiris eXpress Deployment Solution User Guide for additional command-line options for aximport. the package can be refreshed manually by selecting the DS Task Import Utility package Altiris® Deployment Solution 6. 4. ensure that the task. this policy runs on the destination Deployment Servers. This file contains the exported Deployment Server deployment tasks (jobs). Note The /o switch causes the import to replace any tasks with the same name as those being imported. Click the Enabled check box.

your network traffic is light--and you can plan the polling updates for off-hours--but report data is more static and out-of-date. updated collection data created in Notification Server is transmitted using the Altiris Agent to update the Deployment Database. Setting polling intervals and configuration request intervals requires that you plan how often you want to refresh console and deployment information based on network traffic requirements. set the polling interval in the Altiris Console.8 SP2 396 . See Setting the Altiris Agent Configuration Request (page 397).(from the Solutions tab of the Notification Server Administration Console) and selecting the Update Distribution Point option. new computers and deployment tasks created in a Deployment console and saved to the Deployment Database are transmitted using the DS Agent to update the Notification Database. the policy to import the Deployment Server jobs can be forced to run again by manually scheduling the policy. Setting the DS Agent Polling Interval To refresh data to the Notification Database. See Setting the DS Agent Polling Interval (page 396). (2) Conversely. Select Solution Settings > Deploy and Migrate > Deployment > Deployment Server Agent Configuration > Deployment Server Agent Configuration. 2. (1) To update the Notification Database. but network traffic is heavy because data is extracted and transmitted every minute from every Deployment Database to update the Notification Database. Altiris® Deployment Solution 6. if you set polling intervals and configuration requests for a larger polling interval (such as one day). The balance between timely deployment information appearing in the Deployment view on the Notification Server and the level of network traffic should meet your IT policies. In contrast. and network design. From a destination Deployment Server. your console information is relatively up-to-date. 1. organizational requirements. Deployment Solution uses two separate interval settings to synchronize data between the Deployment Database and the Notification Database. Select the Configuration tab. Setting Polling Intervals in Deployment Solution You can set polling intervals to transmit data from the Deployment Database to the Notification Database when generating reports from multiple Deployment Server systems. If you set frequent updates (such as setting a polling interval to 1 minute).

Notification Server identifies that the DS Agent needs to be installed. 4. Click Apply. you must set the interval request information in the Altiris Console. You can also set inventory updates. Altiris® Deployment Solution 6. In Agent Basic Settings. 5. 2. select new values in the Request new configuration field. Setting the Altiris Agent Configuration Request To download collection data from Notification Server for each Deployment Server installation. This feature sends a request to Notification Server to flag all new scheduling records in the Notification Database. This field is only used by Deployment Server when first installing the Deployment from the Altiris Console. To update scheduling and configuration information for each Deployment Server installation. Click the Configuration tab. Set the Computer/Job Polling Interval. You can also select settings for each Deployment Server installation. This transmits data to the Deployment Database to update data. Select Altiris Agent > Altiris Agent Configuration > All Windows Servers. 3. Select the Deployment Server Agent for all Deployment Servers. This feature transmits all inventory data from the computer running Deployment Server. 4. the Notification Database must update the Deployment Database. 1. Click Apply.Multiple policies to configure or install Deployment Server Agents are provided. This updated data is transmitted automatically through the Altiris Agent at defined configuration request intervals. if required. By sending basic inventory (including information that Deployment Server is installed on the computer). 3. Request new configuration information every: _______. Send basic inventory every: ______.8 SP2 397 .

Each Deployment Server site is identified in the Computers pane under Deployment Server. 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. and manage all computer resources across your organization. or can be associated with virtual computers. network container. Manage with Computer icons. To filter computers in a computer group to schedule jobs only to the appropriate computer types. you can identify. See Adding New Computers (page 403). handhelds. Manage multiple Deployment Server sites. or other criteria. or set filters to sort computers by type. or any other structure to meet your needs.Managing Computers from the Deployment Web Console From the Computers pane of a Deployment Solution console. with a listing of scheduled jobs and operations associated with each computer.8 SP2 398 . Deployment Solution lets you add new computer accounts and set configuration properties for new computers before they are recognized by the Deployment Server system. hardware configuration. and network switches. network and Web servers. Organize computers by department. You can deploy and provision computers on a mass scale. Add new computers. software requirements. You can use search features to locate a specific computer in the Deployment Database. Altiris® Deployment Solution 6. Preset computer accounts automatically associate with new computers when they start up. notebooks. you can now access different Deployment Server systems and manage all sites or network segments across your organization. You first select a Deployment Server icon and expand the treeview to see the computers and computer groups managed by the selected Deployment Server. To select a computer to run remote operation or schedule a job. deploy. In the Deployment Web Console. See Viewing Computer Details (page 402). including desktop computers. select a Deployment Server group icon from the Computers pane and select the computer or computer group in the Details pane. See Managing Multiple Deployment Server Systems (page 399). Major computer types are identified by a computer icon in the console. From the Deployment Web Console. Deploy to groups of computers. see Creating a Computer Group Filter (page 417). you assign and schedule deployment jobs to computers or groups with easy-to-use Web features. OS. Select a job and click Run Now or Schedule. configuration.

Enter the computer name for the computer running Deployment Server. if required. Jobs can be organized and assigned for daily tasks or to handle major IT upgrades. View and configure computer properties. select Add Deployment Servers from the drop-down list. Or you can view the Computer Properties page for detailed access to a computer’s hardware. Adding Deployment Servers You can identify and add existing Deployment Servers to the Deployment Web Console. 2. and network property settings. 3. Run remote operations from the console. Altiris® Deployment Solution 6. Build deployment jobs with one or more management tasks to run on selected computers. The Deployment Server appears in the Computers pane with its job folders listed in the Jobs pane. Use Logon tab to set security options. Build and schedule jobs. Individual Deployment Servers. You can modify computer settings for each computer from the console.8 SP2 399 . Note To push down a new installation of Deployment Server using Deployment from the Altiris Console. Expand the Deployment Server group icon to view all computers for a specific site or network segment. Configure property settings. Create jobs. assign the job to computer groups. See Remote Operations (page 415). This icon identifies an individual Deployment Server system with its managed computer devices. run deployment jobs or select from additional management commands. See the property pages for modifying Deployment Agent settings. Managing Multiple Deployment Server Systems From the Computers pane of the Deployment Web Console. See Computer Details (page 412). send a file. or click the on the Details page. Expand the Deployment Server system to view all managed client computers and groups for the selected Deployment Server. See “Building and Scheduling Jobs” on page 102. See Computer Configuration Properties (page 406). All Deployment Servers are listed under this collection. 1.Configure Computer Agents. This lets you authenticate to a role if security has been set up in the Deployment Server Console. In the Computers pane. you can access multiple Deployment Servers and drill down to view all client computers attached to each Deployment Server system. Enter the port number if it is different from the provided default. software. This lets you manage computers and use jobs created at various sites managed by different Deployment Server systems. see Installing Deployment Solution from the Altiris Console on page 14. add tasks. Deployment Servers collection. Perform operations quickly in real-time from a Deployment console. See Deployment Agents (page 410).

4. and Capture Personality tasks. Altiris® Deployment Solution 6. The job from the original Deployment Server appears in the Deployment Share of the targeted Deployment Server. Distribute Personality.Changing Task User Password options Change Task User Password option lets you update the user credentials to be used for the execution of Copy File to. If the job includes associated files. a linked icon appears with the job identifying that the associated files are referenced from the original Deployment Server system. Select Deployment Servers for which you want to perform Change Task User Password operation. software packages. and Capture Personality tasks. Distribute Personality. 3. 4. Select a job in the Jobs pane of the Deployment Web Console. 5. 2. This lets you easily replicate jobs from one site to another site quickly and efficiently. Select the check box for each computer or computer group you want to run the job. Task password option facilitates to update user credentials for multiple Deployment Servers at one time. The Task Password page appears.8 SP2 400 . Click Schedule in the toolbar of the Details page. and click Apply. Distribute Software. Click Deployment Servers link in the Computers pane. select another Deployment Server system. Computers and computer groups of the selected Deployment Server site appear in the Details pane. Distribute Software. 6. Type the user credentials. 1. scripts) associated with a specific job are linked from the Deployment Server Deployment Share of the originating job. Note This feature is valid only for the Copy File To. Run Script. Click Change Task User Password from the toolbar. Scheduling Jobs from Other Deployment Server Systems From the Deployment Web Console. 5. 1. 3. you can schedule jobs from one Deployment Server to computers in another Deployment Server. Replicating Jobs to Other Deployment Server Systems 1. Click Yes to the summary message to update the password of specified user. The available Deployment Servers appear in the Details pane. 2. Select a job in the Jobs pane of the Deployment Web Console. Click Schedule job in the Jobs Action list. Select scheduling options and click OK. Files (image files. Run Script. Note This tab is visible only to the administrators and those users who have the rights to modify password. From the Computers pane.

such as files are also copied. Otherwise. The Job/Folder Selection page appears with all Deployment Server systems and their job folders. the Console Manager proceeds. However. Select a folder in another Deployment Server system from this page and click OK. Select Copy job/folder in the Select Action list.8 SP2 401 . and an error appears in the Altiris Console Manager log in the Event Viewer. any Deployment Server-specific flags take precedence. replication targeting Timpanogos does not copy collateral files. When this value is set to 1. The path of this registry key is HKEY_LOCAL_MACHINE > SOFTWARE > Altiris > eXpress > Deployment Web Console > Deployment Console Manager > Job Replication. Note If the key value name does not exist or if the key value is not equal to 1. overrides all Deployment Serverspecific flags regardless of their respective settings. the associated collateral. the Console Manager must be restarted for the changes to be implemented. The path of this registry key is HKEY_LOCAL_MACHINE > SOFTWARE > Altiris > eXpress > Deployment Web Console > Deployment Console Manger > Job Replication > Exclude Targets. The ExcludeAllTargets global value when set to 1. set the key value in the ExcludeAllTargets registry key as dsword:00000001. the files are replicated. The Console Manager logs a warning in the event log stating that Console Manager is waiting for the file to exist. 3. Replicating Jobs without Copying the Collateral When copying jobs from one Deployment Server to another. both Create and Modify Permissions are required for the Job objects if security is enabled. To enable the Do not copy value for an individual target (destination) Deployment Server. a linked icon appears with the job identifying that the associated files are referenced from the original Deployment Server system. When the ExcludeAllTargets value does not exist or is not set to a value of 1. However. To enable the Do not copy value of an individual Deployment Server. If the job includes associated files. such as Package Servers. Note When the ExcludeAllTargets value is changed or set. you can also copy dependent files to the destination server using a different mechanism. the job does not appear in the target Deployment Server Console. The job is replicated from the original Deployment Server system to the targeted Deployment Server system. In the above example. To enable a Do not copy value for all replication. When the key value is set. it must be equal to 1. Note To successfully replicate a job from one Deployment Server to another Deployment Server. Once the file exists. changing the value for an individual Deployment Server does not require a restart of the Console Manager service. Altiris® Deployment Solution 6. the Console Manager waits until the file exists on the destination Deployment Server before copying the job data and scheduling data. set the key value in the Exclude Targets registry key as Timpanogos = dword:00000001. The Console Manager follows the same procedure for an individual Deployment Server that it follows when the ExcludeAllTargets value is set. Timpanogos is the name of the target Deployment Server.2.

Viewing Computer Details In Deployment Solution. server. a computer resource is identified in the console with a distinctive icon to display the computer type — Windows desktop or notebook. Altiris® Deployment Solution 6. The following is a sample list of computer icons appearing in each Deployment console identifying the computer type and state. Additional icons identify different states of server deployment. This icon appears if the Workstations check box is selected on the Advanced tab of Initial Deployment. Computer connected to Deployment Server but the user is not logged on. such as the log on status. or Linux operating system — and its current status. The computer is designated as a master computer and is used to broadcast images to other client computers. A managed server connected to the Deployment Server with a user logged on. Computer with a time-limited user license and a user logged on. As soon as the computer connects and the Deployment Server recognizes the new computer and changes the icon. You can also view the status of the jobs assigned to the selected computer in the Details pane of a Deployment console. Computer not currently connected to the Deployment Server but known to the Deployment Database. See “Advanced” on page 131. handheld. A managed Linux computer connected to the Deployment Server with a user logged on. Additional icons identify different states of Linux computer deployment. A connected handheld computer. or user with a timed license status. A client computer waiting for user interaction before running deployment tasks. server waiting status.8 SP2 402 . See “Adding New Computers” on page 63. A virtual computer with values defined in advance using the New Computer feature. Computer connected to the Deployment Server with a user logged in. These computer icons change to convey the state of the computer.

Create or import computer accounts from the Deployment console. New computers with the Deployment Agent installed are added to the All Computers groups (unless otherwise specified in the Deployment Agent configuration). These icons appear as physical representations to allow management of different levels of the server structure.View the Physical Devices by clicking the drop list in the Computers pane and selecting Show Physical Devices. assign IP and network settings. Use Initial Deployment to configure and deploy new computers booting to automation. server icons identify logical server partitions. See Initial Deployment (page 442).8 SP2 403 . Starting up a new computer in automation lets you image the hard drive. Adding New Computers Computers can be added to the Deployment Database using three methods: Install the Deployment Agent on a Windows or Linux system. See Creating a New Computer Account (page 404). Click New Group or select New > Computer Group to create a new group. You can add new computers using the New Computer feature or import computers using a delimited text file. See “Bay” on page 70 for properties and rules to deploy Rack/ Enclosure/Bay servers. If you install the Production Agent (Deployment Agent) to a computer with the operating system already installed. You can move the computer to another group listed in the Computers pane. Using Initial Deployment you can associate new computers with pre-configured virtual computer accounts. These newly configured computers appear in the New Computers group. Altiris® Deployment Solution 6. In addition. 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. Physical view of Rack/ Enclosure/Bay components for high-density server systems. distribute personal settings and software. and install the Deployment Agent for new computers. You can pre configure computer accounts by adding names and network settings from the console. the computer is added automatically to the Deployment Database at startup. See also “Deployment Agents” on page 67.

You can set up as much configuration information (computer name. Creating a New Computer Account You can create computer accounts for individual computers or for computer groups. To create a new computer account Create new computer accounts in the Deployment Database for one or more computers. you are ready to deploy it because have done all the work ahead of time. you can automatically assign new names and associate them with existing computer groups or the New Computer group. The virtual computer you created now turns into a managed computer in the console. At startup. 1. Virtual Computers Deployment Solution provides features to create a virtual computer to pre-define a computer’s configuration settings and assign customized jobs to that computer even if you do not know that computer's MAC address.About New Computers When a new computer starts up. When the new computer finally arrives.8 SP2 404 . especially when you need to deploy several computers to individual users with specific needs. if Deployment Server recognizes the MAC address provided in a New Computer account or import file. Virtual computers offer a great deal of power and flexibility. To add one or more new managed computers. it automatically associates the user account at startup with the New Computer icon. A virtual computer icon appears if specific hardware data (MAC Address) is not known. You can also prepare jobs prior to the arrival of the new computer to deploy the computer using customized images. for example) you know about the computer and apply it to the new computer as it comes online. the computer appears as a virtual computer. MSIs and RIPs based on a user's specific needs. and IP address. The New Computer icon appears for a new computer if the MAC Address is provided when creating a new computer account using any import or new computer account feature. When creating new accounts for computer groups. A virtual computer account can be associated with a new computer using the Initial Deployment feature. The virtual computer saves time because you can configure the computer before it arrives on site. workgroup name. This type of computer is known as a virtual computer. the configuration settings and jobs assigned to the virtual computer can be associated with the new computer. Just set the managed computer option in PXE or automation and the new computer can connect to the server as a managed computer. You can create multiple virtual computer accounts and associate the account with a new computer when it boots to automation. Deployment Server recognizes the new computer and the icon changes. As soon as the computer starts up and is associated with a virtual computer account. If this value is not provided. letting you to associate it to a new computer. first select the desired Deployment Server system in the Computers pane and select New computer(s) from the Altiris® Deployment Solution 6.

or . Importing New Computers from a Text File You can import computer configuration data using delimited text files (. You can import: . a message appears. Note Jobs can be added to the import file. Click Open. The imported computers appear in the Computers pane of the Deployment Web Console. Enter the number of computers to be placed in the name range. The Computer Configuration Properties appears. Click OK. 2. 2. This file contains all configuration data for a new computer. allowing you to select files from the Deployment Share. including all settings in the Computer Configuration Properties of a selected computer. a warning appears stating that the computer import file is incorrect. 1.imp type of files. They can be created and associated with the new computers. To create multiple computer accounts Define a name range and create accounts in the Deployment Database for multiple new computers. 4. When a new computer starts up. the numeral is added to beginning of the name.csv. . Select Append to incrementally add the numeral to the end of the Fixed text.txt. If a correctly formatted computer import file is selected. Click the Action drop-down list in the Computers pane and select Import Computers. Select the import file. Altiris® Deployment Solution 6. click to open the Define name range section. 3.csv. informing you that the computer import is complete and identifies the number of computers added.txt. . 2. To import new computers from a text file 1. Enter the core name in Fixed text and a numeral for the range start. A virtual computer icon appears in the selected group. or . If the computer import file is incorrectly formatted.imp files) to establish multiple computer accounts in the Deployment Server database.Computer actions drop-down list or click the new computer icon in the Details pane. On the Networking tab. Type the name of the new computer (up to 15 characters) and configure settings.8 SP2 405 . 3. If you clear this box. A dialog appears. you can assign it to this preset account.

Altiris® Deployment Solution 6. Computer Name box is disabled for multiple computer configurations. Set the TCP/IP addresses for one or more network adapters. Modifying Configuration. This can be done by manually using these utilities or when installing the Deployment Agent. Networking Settings Use the Sysprep utility to generate unique SIDs. Set the local Windows user account values. Computer name This is the NetBIOS name for the computer. Set Novell Directory Services client logon options. set. The name must be unique in the network and is limited to 15 characters. Networking Settings TCP/IP Settings NetWare Client Settings Operating System Licensing Settings User Account Settings Set the Windows name of the computer and the Workgroup or Domain settings.8 SP2 406 .Computer Configuration Properties Computer property settings can be viewed. and modified when Adding New Computers. Set the registered name and view the hashed installation license key for the installed operating system. or setting up Initial Deployment.

myServer. Use Token Select the check box to specify the computer name using tokens. Selecting this option enables Fixed text combo box and disables the Range start. Enter the text portion of the name you want associated with each computer. and specify the organizational unit (OU) using this format: OU/ newOU/users. the number is added as a prefix to the fixed text. the DNS domain name. for example: Marketing1. Append Select to add the range after the fixed text in the computer name. %NAME%. Enter a numeral to add to the fixed text. You can identify a root name and automatically increment its associated number. Enter the number of computers to be automatically named. Enter either the fully qualified domain name. Altiris® Deployment Solution 6. %SERIALNUM%. %NICyMACADDR%. Range start. Microsoft networking Click Workgroup or Domain and enter the name. This option is available when selecting groups of computers. If you clear this box.yourcompany.First 8 characters of actual computer name. set a range of names for multiple new computers: Number of computers.Complete computer name. %NODENAME%. or the WINS domain name. Label.Fixed Text: You can select one of the six tokens from the drop-down list.Define name range Create a sequential range of computer names. You can enter the fully qualified domain name (example: mjones. The complete entry to place the computer in the users OU is the following: mjones.yourcompany. Fixed text.com/OU/newOU/users internal.org/New Corporate Computer OU/ Mail Room/Express Mail Servers.Serial number from SMBIOS.8 SP2 407 . Note This option is applicable for multiple computers and not for single computer. Selecting this option enables the NIC Number option where you need to specify the NIC number which can range from 1-8. Note The default value for NIC number is 1. for example: Marketing. For new computers. and Append options.com).MAC address of the computer with NIC specific number.

The network adapter with the lowest bus. Add. device. Click to obtain an address from a DHCP server. Assign a static IP address. MAC. Domain suffix. and function number is the first listed (NIC0 . If the bus. Click the Add icon for additional network adapters installed on the client computer.8 SP2 408 .zero based). If IP settings are provided for additional network adapters not present in the computer. A list of all network adapters installed in the selected computer. your computer appears twice in the console. Enter this to add domain suffixes to the root address. it is enumerated in the order it is detected. they are disregarded. ensure that one network adapter is not using an Intel Universal NIC driver (commonly called UNDI driver) to connect to Deployment Server. device. When configuring multiple network adapters. The MAC address is a unique number assigned to the network adapter by the manufacturer. Click to set static IP address values. If one network adapter uses the native driver and one uses an UNDI driver.TCP/IP Settings Host name Network adapter The Windows name of the managed computer that is hosting Deployment Server. and function information cannot be determined for a network adapter. Use DHCP to obtain IP address. This is read-only. it is configured only with the IP settings listed first. If a computer in the group has only one network adapter. Altiris® Deployment Solution 6.

You can enter DNS Suffix and specify DNS Suffix order search also. for example: \OneServer. Click this tab to add additional WINS settings for this network adapter. Click this tab to enter the router settings information for this IP interface.8 SP2 409 . IP Address. All the fields. Ensure you use the “eth” syntax when naming new interfaces. Append these DNS suffixes (in order): Add the name of the Domain Suffix and use the up and down arrows to set the DNS suffix search order. NetWare Client Settings Set Novell NetWare client values for a new or existing computer. Metric. Enable NetBIOS over TCP/IP. Disable NetBIOS over TCP/IP. Netmask. Select whether you want to log on directly to a NetWare server or to a NetWare tree in Novell Directory Services (NDS). Click and enter the name of the NetWare server. Gateway. for example: eth0:1 or eth0:new interface. server name. You can specify the preferred tree. This is the primary login server for the NetWare client. Interface. Click to set named interfaces for this network adapter. Enter the Broadcast address for the specified IP interface.Show advanced Select Advanced to set multiple IP Interfaces. Gateway. Designation. and Use NetBIOS setting from the DHCP Server. Enter a name for the IP interface. which denotes that the named interface is operating. Click the edit icon to modify settings. Click and enter the name of the NDS tree. WINS. and NDS context. Ignore NetWare settings Preferred tree Preferred server Select to disregard all Novell NetWare client settings for this computer. DNS. Shut down the named interface by selecting Down. Click this tab to enter the gateway address for this IP interface. that is. Enter or modify the IP address common to all interfaces. State. You can select one of the three available options. and Use are mandatory. DNS Suffix. Broadcast Address. Enter the appropriate subnet mask. The default value of the interface state is Up. Flag. Click this tab to add additional Domain Naming Servers (DNS) for this network adapter. Altiris® Deployment Solution 6. Name. Ref. Static Routes. Netmask.

Select this option to run the NetWare client login scripts. Deployment Agents are Altiris® Deployment Solution 6. Enter the alpha-numeric license key. Management User must change password at next logon User cannot change password. and 2003 Servers). XP. Registered user Organization License key Enter the name of the registered user. Marketing. Prohibit the user from changing their password at any time. User Account Settings Set up local user accounts for the newly imaged computer or when running a configuration task. full name.NDS User name NDS Context Run login scripts Click and enter the name of the user object for the NetWare client. Select to maintain the user password. Password never expires. 2000. Click and enter the organizational unit context for the user. The full name for this local Windows user account. and password. Retype the password for confirmation. Specify the Windows groups that this user can belong to as a comma-delimited list. Operating System Licensing Settings Enter or view the license information for your Windows operating system software (Windows 98. Enter a user name. The password for this local Windows user account. set standard Windows login options. Deployment Agents To remotely manage computers from a Deployment console. This is the hash value rendered from the OEM key or 25-digit license key required when installing the operating system.8 SP2 410 . Enter the name of the Organization. a Deployment Agent is installed on each computer in the Deployment Server system. Select to force the user to change the password after setting the configuration properties. for example: Administrators. User name Full name Password Confirm Password Groups The user name for this local Windows user account.

including desktops.provided for various computer types.NET 4. the user sees a small icon in the system tray. the client computer running the Deployment Agent is connected to the Deployment Solution system. the managed computers automatically update the Deployment Agent. Altiris® Deployment Solution 6. it shows that the client computer is not connected to the Deployment Solution system. and Windows PE preboot operating systems.NET Notification Server Client Deployment Server Agent Install Deployment Agent to add a managed computer When Deployment Agent is installed on a computer. When a Deployment Server is located by the Deployment Agent. and PPC Handhelds. Deployment Agent for CE . the Deployment Server is down. When a new version of the Deployment Agent is saved to the Deployment Share file server. For best performance. notebooks. The agent may be configured incorrectly. the client computer is added as a record to the Deployment Database. DOS. and servers. 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 on Notification Server. The Automation Agents boot client computers when the Deployment Server sends a deployment job. Automatically update to newer version of Deployment Agent At times. When the Deployment Agent is running on a computer. including Windows. When the icon is blue. This agent runs on the HP T5000 computer devices running the CE . Altiris supports DOS. it is suggested that all managed computers run the latest version of the Deployment Agent. Deployment Agent on Windows Deployment Agent on Linux Automation Agents The Deployment Agent runs on Windows computers. This agent runs on the Deployment Server computer when running Deployment Solution on Notification Server. it searches across the network for a Deployment Server to attach to. Linux.2 operating system. When the Deployment Agent icon is clear. Altiris may update versions of the Deployment Agent to enhance features. or other network problems exist.8 SP2 411 . Linux. This Deployment Agent runs on Linux workstations and server. The following Deployment Agents reside on the client computer and communicates with the Deployment Server. Managing Agent Connections The following utilities are provided for managing transmissions between the Deployment Server and Deployment Agents running on the managed client computers.

Reject or Retrieve a Rejected Computer If a computer you do not want to manage connects to your Deployment Server. and clicking Accept Computer(s) icon from the toolbar. 2. Click OK. The rejected computers are prohibited from being active in the Deployment Database. View Rejected Computers You can view the rejected computers by clicking on a Deployment Server. right-click a computer and click Advanced > Reset connection. They are identified and rejected by their MAC address. General (page 413) Network (page 413) TCP/IP (page 413) Location (page 413) Bay (page 413) Lights-Out (page 414) Altiris® Deployment Solution 6. The computer should reconnect and its icon color returns to its original active status color. See Properties (page 412) and Inventory (page 414). 3. This removes the unwanted computer from the Computers pane in the Web Console. Although the computer is not deleted. Click the computer you want to reject from connecting to the Deployment Server. This is useful for troubleshooting or if you suspect there is a bad connection. you can reject it. Further attempts by the computer to connect are denied. and selecting View Rejected Computers from the Select action drop-down list. Select Reject Connection from the Select action drop-down list. You can remove computers from the Rejected Computers list by selecting it.Reset a Client Connection Resetting the connection that a managed computer has with the Server simply disconnects and reconnects the computer.8 SP2 412 . When the computer disconnects. 1. To reset a client connection. Computer Details View and edit the computer properties and inventory for each managed computer. Properties The following are the general properties of the selected managed computer. any history or schedule information associated with the computer is deleted. This allows the computer to attach again and be managed by the Deployment Solution system. its icon turns gray.

Network View Microsoft Networking. This lets you replace new blades in the bay and automatically run deployment tasks from its deployment history. you can enter this information manually or you can let the user populate this screen using Prompt User for Properties. and user information for the selected managed client computer. Location View and edit user-specific properties such as contact name. Click Change to open the configuration window allowing you to modify settings. View logged in user name. department. Altiris® Deployment Solution 6. phone number. operating system installed. Run Predefined Job The server processes any specified job. or from any script (in a Run Script task) with this command: rem deployment start. name of the Deployment Server. 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. Novell Netware settings.See “Restoring a Computer from its Deployment History” on page 88 All deployment tasks in the bay's history are executed starting from the last Distributing Disk Image task or Scripted OS Install task. Select a job to run automatically when a new server is detected in the bay. These rules are described below: Rule Re-Deploy Computer Action Restore a blade server using deployment tasks and configuration settings saved from the previous server blade in the bay.General View or change the name of the computer as it appears in the console. TCP/IP View TCP/IP information.8 SP2 413 . Bay View location information and other properties for Rack / Enclosure / Bay components for high-density and blade servers. including a list of all installed network adapter cards (up to eight) for the selected computer. version of the Deployment Agent. As the administrator. whether or not an automation partition is installed. e-mail address. Set rules for automatic re-deployment of blade servers based on physical location changes. and site name. and other client information. mail stop.

Applications View the applications that are installed on the computer. If the server blade is a new server (never before identified). 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. If the server existed in a previous bay. asset tag. power down and restart the computer remotely. Hardware (page 414) Drives (page 414) Applications (page 414) Services (page 415) Devices (page 415) Hardware View processor make and type. or to check server status.8 SP2 414 . product name.Rule Ignore the Change Action This option lets you move blades to different bays without automatically running jobs. processor count. and number of drives installed. If you have multiple drives. including description. RAM installed on the computer. The icon on the console changes to reflect that the server is waiting. Altiris® Deployment Solution 6. version number. file system. volume label. The server blade placed in the bay is not identified as a new server and no jobs are initiated. publisher. the established process for managing new computers is executed. Drives View information about each drive on the computer. serial number. model. serial number. (default) No job or tasks are performed (the Deployment Agent on the server blade is instructed to wait). display configuration. you can select a drive from the list box to view its settings. and whether or not Wake On LAN and PXE are installed and configured. such as capacity. Inventory The following are the inventory details of the selected managed computer. UUID. the history and parameters for the server are moved or associated with the new bay. product ID. MAC address of each network adapter installed. Wait for User Interaction Lights-Out View information about the remote management hardware installed on the selected computer (most often a server) used to power up. manufacturer. and systems components.

a new job appears in the Jobs pane of the Deployment console under the System Jobs > Image Jobs folder. ports. To manage unwanted client computers from attaching to the Deployment Server.8 SP2 415 . Devices View the devices installed on the computer. directories. keyboards. disk drives.Services View the services installed on the computer as well a description. This menu provides a variety of commands to remotely manage all computers in your site or network segment. including display adapters. This creates and stores the image to distribute now or later. See Copy File (page 437). click the Computer actions drop-down list and select a remote operation to perform on the selected computer. View a history of deployment tasks. Quick Disk Image Run command History Reject Connection Altiris® Deployment Solution 6. IP address. Active Directory context. The job name has a generic format of Create Image: <computer name>. See Reject Client Computer Connections (page 372). You can also manually boot a client computer using bootable media created in Boot Disk Creator. To run a disk image job you must have have an Automation Partition installed on the client computer. If the client tries to connect to the server. Type and run commands remotely. Send a command from the Deployment console as if you were entering a command from the command-line prompt. Select a computer and image its hard disk. use the Reject Connection computer action to remove the client's MAC address and other information from the Deployment database. the MAC address cannot be found and the client-server connection is rejected. Configure Set network and local configuration properties for each computer. or create a boot menu option in PXE Server. including computer name. Click Save to save the deployment history to a file or click Delete to delete the history. storage volumes. Copy File to Copy selected files. Remote Operations After selecting a specific computer device. start type. and path for each service. or entire directory structures and send them to the selected computer(s). See Computer Configuration Properties (page 406). domains. When you finish this computer operation. and other system devices.

Apply a permanent license if a client computer is using a timelimited license or requires an updated license. Click to log off of the selected managed computer. Select it to ensure you have the latest inventory of the computer. See Production Agent Settings (page 375). Upda