Symantec ALTIRIS DEPLOYMENT SOLUTION 6.9 SP4 - V1.0 Manual

Table of Contents

Quick Links

Altiris Deployment Solution™ 6.9 SP4

from Symantec Admin Guide

Table of Contents

Summary of Contents for Symantec ALTIRIS DEPLOYMENT SOLUTION 6.9 SP4 - V1.0

Page 1 Altiris Deployment Solution™ 6.9 SP4 from Symantec Admin Guide...
Page 2 Copyright © 2008, 2009, 2010 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, Altiris and any Altiris or Symantec trademarks used in the product are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries.
Page 3: Table Of Contents
Contents Chapter 1: About Altiris® Deployment Solution™......19 Deployment Solution Architecture ..........20 Deployment Server .
Page 4 Using the Remote Agent Installer (Windows-only) ....... . 35 Windows XP ............35 Step 1: Disable Simple File Sharing on Windows XP .
Page 5 Number of Client Connections ......... . . 58 Network Speed.
Page 6 RapiDeploy options ........... . . 85 Agent settings options .
Page 7 Network configuration ........... 120 TCP/IP .
Page 8 Deployment tasks............155 Task names in a mixed-language environment.
Page 9 Upgrading AClient to DAgent ..........197 Symantec Backup Exec System Recovery (BESR) sample jobs ......197 Initial deployment .
Page 10 Chapter 20: Symantec® Ghost® Imaging........226...
Page 11 What if I Am Not Using PXE? ......... . . 242 Tools .
Page 12 Vista Software Distribution ..........261 Vista Run Script Tasks.
Page 13 WinPE ............. . 290 Set Default Pre-boot Operating System .
Page 14 Add New Files ............322 Convert an Image .
Page 15 Install multiple licenses ..........361 Adding a license from the Deployment Console .
Page 16 Appendix B: RapiDeploy Technical Reference....... . 416 RapiDeploy Executable Files..........416 Running RapiDeploy from the Command-line .
Page 17 Uninstall Office XP ........... . . 463 Wake up Computer .
Page 18 Discovering a Device..........498 Deleting a Device .
Page 19: Chapter 1: About Altiris® Deployment Solution
Chapter 1 About Altiris® Deployment Solution™ Altiris® Deployment Solution™ software provides a suite of tools to quickly install operating systems and software. Deployment Solution leverages a number of Altiris technologies to provide extensive management capabilities: Altiris Technology Description RapiDeploy® Imaging Capture and deploy computer images using PXE, DVDs, CDs, or USB drives.
Page 20: Deployment Solution Architecture
About Altiris® Deployment Solution™ Deployment Server Feature Description Extensive supported platforms Support for 32- and 64-bit architecture, servers, blades, thin clients, and Itanium, running Windows and Linux operating systems. Power control, Wake on LAN Managed computers can be started or shutdown remotely.
Page 21: Deployment Server
About Altiris® Deployment Solution™ Deployment Server The Deployment Server is the central component of a Deployment System and manages the Deployment Database, the communication between the different components, and schedules jobs to run on managed computers. Deployment Database The Deployment Database provides the back-end datastore and stores details about the computers, groups, and jobs in your Deployment System.
Page 22: Automation Tools
About Altiris® Deployment Solution™ Deployment Web Console: A Web application that provides browser-based administration. This console can be executed remotely using any Web browser, and has built-in tools to manage multiple Deployment Servers. Deployment Tab in the Altiris Console: This interface is integrated into the Altiris Console to provide integrated management with other Altiris Solutions.
Page 23: Part I: Planning And Installing Your Deployment System
Part I Planning and Installing Your Deployment System Deployment Solution is designed to meet deployment, management, and migration needs for small, medium and large organizations with diverse topologies and varying computer management requirements. This section provides steps for installing Deployment Solution components, but also includes system architecture details and discusses planning strategies to install and optimize your Deployment Solution system.
Page 24: Chapter 2: Preparing To Install
Chapter 2 Preparing To Install This sections lists the tasks you need to complete before you install Deployment Solution. Step 1: Log on to Your Deployment Server Computer as an Administrator (page 24) Step 2: Create a Services Account (page 25) Step 3: Gather Automation Operating System Install Files (page 26) Step 4: Obtain a License File...
Page 25: Step 2: Create A Services Account
Preparing To Install Select the Administrator account you are using to install Deployment Solution. If it does not exist, add it. Click the Server Roles tab, and enable System Administrators: Click OK and verify that the role was added. MSDE Database Engine Optionally, in smaller installations, you can use the MSDE database engine instead of SQL Server.
Page 26: Step 3: Gather Automation Operating System Install Files
Preparing To Install To create a services account On each computer where you host a Deployment System component, click Start > Administrative Tools > Computer Management. Browse to Local Users and Groups, and add a new user: The process for creating domain-level accounts is similar. This is the only account that needs to be created before you install.
Page 27: Chapter 3 Installing
Chapter 3 Installing Simple or Custom Install? If you plan to install your Deployment Server, Database, and Share on the C drive of the same computer, select the Simple install. Otherwise, select Custom. Simple Install Installs to the C drive. Installs each of the Deployment System components (with the exception of the Deployment Agent) on the computer where the install was launched.
Page 28: Enable Microsoft Windows Vista Sysprep Support
Installing This can be installed later by running setup.exe and selecting Component Install. Enable Microsoft Windows Vista Sysprep Support Microsoft Windows Vista Sysprep lets Sysprep run on a Vista Client after an Imaging event. 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.
Page 29: Chapter 4: Post-Installation Configuration
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 29) Step 2: Create Domain Join and Deployment Share Accounts (page 29) Step 3: Grant Services Account the db_owner Role to Your Deployment Database (page 30)
Page 30: Deployment Share Read/Write Account
Post-Installation Configuration Deployment Share Read/Write Account Create this account on the computer hosting your Deployment Share, granting the rights in the following table: Rights Description File System Grant read/write privileges to your Deployment Share. Step 3: Grant Services Account the db_owner Role to Your Deployment Database Open Enterprise Manager and connect to your SQL Server.
Page 31: Step 4: Configure Your Deployment System
Post-Installation Configuration Click OK and verify that the change was successful. Step 4: Configure Your Deployment System The majority of tasks you perform in your Deployment System use the Deployment Console. To open the Deployment Console Click Start > Programs > Altiris > Deployment Solution > Console. Add Your Domain Join Accounts If you are using accounts to join computers to a domain you need to provide the account credentials.
Page 32: Grant Console Rights To Administrators
Post-Installation Configuration In the Deployment Console, click Tools > Security. Add a new user or group. We recommend clicking AD Import and importing Active Directory groups, as this simplifies rights management. The first user or group added is granted administrator rights. Each additional user or group after the first are granted no rights and must be assigned rights explicitly.
Page 33: Configure Deployment Server
Post-Installation Configuration Configure Deployment Server The Deployment Server Configuration Utility lets you configure advanced settings for the Deployment Server component. You can stop, start, or restart the Deployment Server services, update the services account, and configure additional options. You do not need to perform any configuration at this time, though you should become aware of the configuration options provided.
Page 34: Chapter 5: Deployment Agent Installation
Chapter 5 Deployment Agent Installation The Deployment Agent runs on managed computers to perform local management tasks as directed by Deployment Server. 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, you should install the Deployment Agent on managed computers.
Page 35: Using The Remote Agent Installer (Windows-Only)
Deployment Agent Installation Using the Remote Agent Installer (Windows-only) Advantage: Browse your network to quickly select computers, monitor installation status in real time, and retry failed installations. Disadvantage: Requires Local User rights on each computer. Does not work with simple file sharing in Windows XP. Windows XP Step 1: Disable Simple File Sharing on Windows XP In Windows Explorer, click Tools >...
Page 36: Step 1: Provide Users Access To The Agent Installation Program
Deployment Agent Installation Step 1: Provide Users Access to the Agent Installation Program The agent installation programs are stored in the Agents folder on your Deployment Share. Copy this file to a location that your users can have access. For security purposes, we do not recommend granting any users direct rights to your Deployment Share, especially if you are storing software or computer images on this share.
Page 37: Agent Auto Update
Deployment Agent Installation Agent Auto Update The Deployment Agent has the ability to update itself to a newer version automatically, and is set to update computers in batches to prevent network overload. This greatly reduces the effort required when upgrading. See the release notes on the Altiris Knowledgebase for specific information on Agent upgrades.
Page 38: Part Ii: Booting Computers To Automation
Part II Booting Computers to Automation Deployment Solution has the ability to perform work on computers before the normal operating system loads. To do this, a managed computer is booted into an environment where it can communicate with your Deployment Server to perform tasks. This preboot environment is called automation.
Page 39: Chapter 6 What Is Automation
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. If you have ever used a disk imaging utility, or booted a computer using an installation CD, you are probably familiar with running computers in a similar environment.
Page 40 What is Automation? Which Automation Operating System Should I Use? (page 44) Deployment Solution...
Page 41: Chapter 7: Automation Boot Methods
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, automation partitions, or boot media (CD/DVD, USB device, or floppy). This section provides an overview of the available boot methods to help you select the method that works best for your environment, and contains the following: (page 41) Automation Partitions...
Page 42: Automation Partitions
Automation Boot Methods This configuration does not require PXE in your general network environment, but still provides access to the automation environment without physical access. When using the DOS automation environment, PXE provides an additional advantage: multicast boot. This enables your PXE server to simultaneously boot up to 100 computers in a single session to perform automation work.
Page 43 Automation Boot Methods requires booting into automation mode, the boot disk must be present at the right time to boot automation. If a complex job requires access to the production environment during this time, the BIOS will most likely continue to boot to automation until the boot media is removed.
Page 44: Chapter 8: Automation Operating Systems
Chapter 8 Automation Operating Systems Which Automation Operating System Should I Use? After you have selected a method to boot computers into automation, you need to decide which operating system you want to use. In the past, MS DOS was the only supported option.
Page 45: Winpe
Automation Operating Systems WinPE WinPE (Windows Pre-boot Environment) is the next generation boot environment for Windows computers. WinPE provides several advantages over DOS, including better driver support (WinPE uses the same drivers used by the other modern versions of Windows), increased speed, and generally more functionality. The biggest drawbacks are its size, which causes increased boot time, especially when booting over the network using PXE.
Page 46: Chapter 9: Installing And Configuring Automation
Chapter 9 Installing and Configuring Automation This section explains: Configuring Automation Operating Systems (page 46) Configuring Automation Boot Methods (page 49) Deploying Automation to Managed Computers (page 50) Configuring Automation Operating Systems The following sections guide you through installing and configuring the automation operating systems supported by Deployment Solution.
Page 47: Adding Additional Files
Installing and Configuring Automation Click Install and complete the wizard, providing the files listed in the previous table when prompted. For complete details on this process see the Boot Disk Creator help. Adding Additional Files Occasionally, you might need to make additional files available within an automation environment, such as utilities or mass storage drivers.
Page 48: Adding Mass Storage Drivers For Winpe
Installing and Configuring Automation The following example provides an overview of this process. Adding Mass Storage Drivers for WinPE Select either the WinPE Additional Files folder, or a specific Boot Disk Creator configuration. Right-click and select add > Folder. Using this add folder command, create the following path: i386\system32\diskdrivers Within the diskdrivers folder, create the necessary folders to contain your drivers.
Page 49: Configuring Automation Boot Methods
Installing and Configuring Automation Files placed in this folder are mounted in Linux automation at /mnt/atrsboot Example You can place a disk image and the rdeployt executable in this folder, create a boot DVD, and restore the included image without network access, using a command similar to the following: /mnt/atrsboot/rdeployt -md -f/mnt/atrsboot/[imagename].img Configuring Automation Boot Methods...
Page 50: Configuring Boot Media (Dvd/Cd, Usb Device, Floppy)
Installing and Configuring Automation An embedded partition doesn’t create an actual disk partition, it reserves space on an existing partition by marking the sectors on the disk as unusable. The target drive must have an existing partition before an embedded partition can be installed. A hidden partition creates an actual disk partition, but this partition is hidden from normal view within the production system, though it is still viewable by FDISK or by an administrator.
Page 51: Using Pxe
Installing and Configuring Automation This configuration contains the automation operating system files, network drivers, IP address of your server, and other settings which control how the managed computer communicates with your Deployment Server. This configuration does not specify how this automation configuration is installed. This is done using the Create Boot Disk wizard, which is launched automatically after you create a configuration.
Page 52 Installing and Configuring Automation Click Create Boot Image to launch the configuration wizard. This wizard is identical to the wizard used when creating configurations for automation Partitions or boot media. When this option is selected from the PXE menu, the necessary files are loaded, the job is performed, the computer boots to the production operating system.
Page 53: Chapter 10: Setting Up The Altiris Pxe Server
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. PXE uses standard network protocols to establish a communication channel between a computer and an Altiris PXE server during the boot process.
Page 54: Pxe Services And Architecture
Setting Up the Altiris PXE Server Regardless of how broadly you implement PXE, Deployment Solution provides tools and services to simplify management of PXE in your environment. 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...
Page 55: How Pxe Works
Setting Up the Altiris PXE Server On each individual Altiris PXE Server, the Altiris PXE Server service and the MTFTP service are installed to perform the work of an Altiris PXE Server. These services are configured, started and stopped by the PXE Config Helper service. Clients connect directly to these services during the PXE boot process: How PXE Works Before a computer can boot over a network, it needs two things: an IP address to...
Page 56: Part 1: Dhcp Request And Pxe Discovery
Setting Up the Altiris PXE Server Part 1: DHCP Request and PXE Discovery Request and Receive an IP Address Initially, the boot agent directs the execution of normal DHCP operations by broadcasting a DHCPDISCOVER packet (255.255.255.255) to port 67 on its local physical subnet to discover a DHCP server.
Page 57: Pxe Planning And Installation
Setting Up the Altiris PXE Server The .1 file is an image of a boot disk floppy with modifications to the autoexec.bat and additional files which ultimately provide the automation environment on the managed computer. The following diagrams contain a basic outline of this process: PXE Planning and Installation This section contains an overview of the PXE deployment process, in the following sections:...
Page 58: Enabling Pxe On Managed Computers
Setting Up the Altiris PXE Server Enabling PXE on Managed Computers Each computer you plan to manage using PXE must have PXE boot enabled (sometimes called network or NIC) and set to the correct sequence in the BIOS. It is also a good idea to apply the latest BIOS updates, especially if your network card is integrated on the motherboard.
Page 59: Pxe Request Routing
Setting Up the Altiris PXE Server PXE Request Routing PXE clients use broadcast packets to find DHCP and PXE services on a network, and multicast packets (MTFTP) to transfer files. These packet types can present challenges when planning a PXE deployment because most default router configurations do not forward broadcast and multicast traffic.
Page 60: Pxe Settings
Setting Up the Altiris PXE Server Boot options. Each boot option corresponds to a specific configuration which includes an operating system, network and other drivers, utilities, mapped drives, and so on. This section contains a brief overview of selected PXE configuration and boot options. For complete details, see the help for the PXE Configuration Utility.
Page 61: Pxe Redirection
Setting Up the Altiris PXE Server PXE Redirection Lets you redirect a global PXE menu option to a local PXE menu option. Redirection settings are not available globally, they are always specific to an individual Altiris PXE Server. This is due to the role redirection plays in your PXE environment. Consider the following example: You manage computers in three locations: Two offices in Ontario, and one office in Alberta.
Page 62: Part Iii: Using Deployment Solution
Part III Using Deployment Solution This section provides feature identification and basic procedures for deploying and managing computers using Altiris® Deployment Solution™ software. Deployment Solution...
Page 63: Chapter 11 Deployment Basics
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.
Page 64: Creating Jobs And Tasks
Deployment Basics 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.
Page 65: Using Lab Builder
Deployment Basics 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. In the Search For field, type all or part of the computer’s property values you would like to search for.
Page 66 Deployment Basics 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.
Page 67: Computer Import File
Deployment Basics 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 ) located in the Samples folder of the Deployment Share. ImportComputers55.xls A semicolon as the first character denotes comment lines.
Page 68 Deployment Basics 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-OEM- 1234567-12345,,,,,,,,John Doe,Engineering,jdoe@altiris.com,111,(801) 805- 1111,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 Deployment Solution...
Page 69: Chapter 12: Managing From The Deployment Console
Deployment Console. However, you can toggle from Full View to Thin Client View. Deployment from the Symantec Management 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.
Page 70: Deployment Console Basics
When a computer is selected, you can view the computer status in the Details pane, including a list of jobs that are running or are scheduled to run on the computer and the status of each job. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 71: Jobs Pane
See on page 145 for complete information about setting up, importing, and managing computers from the Jobs pane. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 72: Details Pane
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. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 73: Thin Client View Of The Deployment Console
To install thin client To install Thin Client, choose one of the following options: On the Deployment Server Install Configuration dialog, select the Thin Client Install option. The Deployment Console Thin Client View appears. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 74: Switching Between Two Views
If you select a deploy option, a list of the available resources appears for the selected type, such as Configurations, Images, or Software Packages. You can select a resource from this list. To create a job You can create a job in one of the following ways: Altiris Deployment Solution™ from Symantec User’s Guide...
Page 75: Resources Pane
Import. Select this option to import a job. See To import a job on page 76. Rename. Select this option to rename a folder. Note You cannot rename the Software Packages pane. You can only rename a folder. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 76: Inventory Pane
This pane displays a table that lists all the thin clients identified by the console. 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 Altiris Deployment Solution™ from Symantec User’s Guide...
Page 77: Toolbars And Utilities
PXE Configuration. After installing the PXE Server, you can create and modify configurations, which make up the boot menu options that appear on client computers. This is another another option to boot computers to automation. See the Altiris PXE Configuration help. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 78: Software Virtualization Solution
78. DeployAnywhere Driver Database Management. Lets you run DeployAnywhere to create hardware independent images. This functionality is provided by Symantec Ghost Imaging Foundation (GIF). To add and manage drivers, on the Tools menu, click the new DeployAnywhere option. To enable this functionality, select the DeployAnywhere option from the deploy image task.
Page 79: Using Svs Admin Utility With Deployment Solution
The ATools.ini file extends the main Tools menu on the console. This sample file contains one submenu, Web Tools, and two additional menu items, Notepad and Netmeeting. The .INI files are located in the Deployment Share. [Submenus] Web Tools=wtools.ini [Notepad] MenuText=Notepad Editor Description=Simple Editor Altiris Deployment Solution™ from Symantec User’s Guide...
Page 80: Computer Filters And Job Conditions
For each job, you can now create task sets that are applicable only to the computers matching those conditions. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 81: Creating A Computer Group Filter
Windows 2008, 256 MB of RAM, and 20 GB hard disks only. By applying the filter, you can view all the computers that meet the specified criteria in the Details pane of the Deployment Console. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 82: General Options
Setting conditions for task sets on page 151. Refresh displayed data every ____ seconds. Refresh the display of data accessed from the Deployment Database. This lets you refresh console data at defined intervals Altiris Deployment Solution™ from Symantec User’s Guide...
Page 83: Global Options
A computer is displayed if the logged-on user has any permission on the computer’s group or if the computer’s group inherits any permissions from a parent folder. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 84: Sysprep Settings
Status field displays the message: Password for 10 tasks updated. Domain accounts options This sign-on feature retrieves the name of the administrator (or the user with administration rights) and the password for each domain. This feature lets you avoid Altiris Deployment Solution™ from Symantec User’s Guide...
Page 85: Rapideploy Options
Deployment Server, and have no information stored in the Deployment Database. These settings are not for the existing managed computers, nor are these settings applied when setting properties using the Remote Agent Installer. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 86: Custom Data Sources Options
Click Add. On the Virtual Center page, enter the Display name, Server hostname, and Username. By default, the port number is displayed. You can also set up a password for the selected user. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 87: Security In Deployment Solution
Additional groups can be created with different rights and permissions depending on the needs and responsibilities in the IT team. If users are assigned to multiple groups, the Evaluate Permissions and Evaluate Rights features are sorted and display effective permissions and rights. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 88: Enabling Security
Administrator rights. Click OK. Note You can assign the user Administrator rights directly, but we recommend you to assign users to groups. See Best practices for Deployment Solution security page 87. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 89: Groups
Manage User Groups dialog and clicking View Members. See also Best practices for Deployment Solution security on page 87 and Enabling security on page 88. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 90: Adding Groups From The Active Directory
Options Console. Lets you set the view and the Console options. See Console options on page 82. Options Global. Lets you set the view and the Global options. See Global options on page 83. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 91: Restricting The Number Of Computers
If checked, lets you modify the master return code list. Allow DeployAnywhere. Lets you run DeployAnywhere to create hardware independent images. This functionality is provided by Symantec Ghost Imaging Foundation (GIF). To add and manage drivers, on the Tools menu, click the new DeployAnywhere option.
Page 92: Setting Permissions
In this scenario, the permission to deny the privilege is enforced. Permissions do not flow down an object tree. Instead, the object in question looks in the current location and up the tree, and uses the first permission it finds. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 93: Connecting To Another Deployment Server
If an entry for your server already exists, select it from the menu. Otherwise, enter the name of the server hosting your remote SQL server in this field. Click Next. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 94: Rejected Computers In Deployment Solution
It also creates additional network traffic when all computers connect and disconnect. By refreshing the managed client computers, you ensure that you are viewing the current status and state of all computers resources in your system. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 95: Chapter 13: Managing Computers
Click New Group on the console to add a new group in the Computers pane of the Deployment Console. You can also click File > New > Computer Group or right-click in the Computers pane and select New Group. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 96: Viewing Computer Details
145. The following is a sample list of computer icons displayed in each Deployment Console, identifying the computer type and state. A computer connected to the Deployment Server with a user logged on. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 97 Click the New Group icon on the toolbar or select File > New > Computer Group to create a new group. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 98: Adding New Computers
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™ from Symantec User’s Guide...
Page 99: Creating A New Computer Account
Importing new computers from a text file on page 100. Click OK. A pre-configured computer account icon appears in the Computers pane. When a new computer starts up, you can assign it to this preset account. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 100: Importing New Computers From A Text File
Jobs can be added to the import file. They can be created and associated with the new computers. If the computer import file is incorrectly formatted, a warning appears, stating that the computer import file is incorrect. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 101: Computer Configuration Properties
Sample jobs on page 196. Click the configuration group icons to set additional computer property values. After you edit these computer property settings, the computer restarts so that the changes can take effect. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 102: General Configuration Settings
The hash value rendered from the OEM key or 25-digit license key required when installing the operating system. User name The user name for the local Windows user account. Full name The full name for the local Windows user account. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 103: Microsoft Networking Configuration Settings
Number option. You need to specify the NIC number, which ranges from 1-8. %SERIALNUM%- Serial number from SMBIOS. %NODENAME%- First 8 characters of actual computer name. The NIC Number textbox is visible for NIC number input; the default value is 1. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 104: Tcp/Ip Configuration Settings
Enter TCP/IP settings for one or more network adapters. Click Advanced to setup IP Interfaces, Gateways, DNS, WINS, and Static Routes. For computer groups, click Associate to assign a range of pre-defined IP addresses. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 105 DAgent do not report limited information for disabled NICs. Deployment Solution tracks any disabled NICs when it rebuilds or reconfigures a computer. Users have the option of enabling, disabling, or keeping the card in its current state. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 106: Tcp/Ip Advanced Options - Ip Interfaces
Add additional WINS settings for this network adapter. Select one of the Enable NetBIOS over TCP/IP, Disable NetBIOS over TCP/IP, or Use NetBIOS settings from DHCP server options for this network adapter. See also Computer configuration properties on page 101. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 107: Tcp/Ip Advanced Options - Static Routes
Select this option and enter the name of the NDS tree. NDS User Enter the name of the user object for the NetWare client. name NDS Context Enter the organizational unit context for the user. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 108: Operating System Licensing Configuration Settings
The password for this local Windows user account. Confirm Confirm the password for the local Windows user account. password Groups Specify the Windows groups that this user belongs to as a comma-delimited list. Example: Administrators, Marketing, Management. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 109: Deployment Agents
This agent runs on ThinClient Windows CE 6.0 ThinClient CE 6.0 operating systems and lets the Deployment Console manage WinCE 6.0 based Thin Clients. Deployment Agent on CE This agent runs on the CE .NET 4.2 operating .NET system. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 110: Deployment Agent Settings
Select the Automatically update clients option and click OK. Deployment agent settings You can set the default agent settings when new client computers are added to the system that the Deployment Server manages. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 111 Deployment Agent communicate with the Deployment Server. Clicking Properties lets you edit the Deployment Agent properties. Passwords protect this option. About. Displays the version and licensing statement for the Deployment Agent. Passwords do not affect this option. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 112: Server Connection
Ensure that the multicast address and port match those set up on the Deployment Server. Try using defaults on both the client and Deployment Server if you have problems while connecting. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 113: Access
Continue the operation. Select to continue if there is no response from the user. Abort the operation. Click to not continue if there is no response from the user. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 114: Security
Save log information to a text file. Select this option to save information to a log file. By default, this option is cleared. Selecting this option enables the File name and Maximum size fields. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 115: Proxy
Deployment Server. Prompt for a boot disk when performing automation jobs. Select this option to prompt for a boot disk while running any automation jobs. Advanced Altiris Deployment Solution™ from Symantec User’s Guide...
Page 116: Deployment Agent For Linux
Deployment Server for drive mappings, authentication, and LMHost entries. 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. Automation Agent Settings include the following property settings: Altiris Deployment Solution™ from Symantec User’s Guide...
Page 117: Drive Mappings
LMHosts file in the Deployment Agent for DOS partition. 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. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 118: Managing Client Connections
Click Yes to confirm the action, click Close. This client computer can now be managed from within the Computers pane. Connection requests from this client computer are now allowed. See also Deployment agents on page 109. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 119: Computer Properties
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™ from Symantec User’s Guide...
Page 120: Network Configuration
See also Computer configuration properties on page 101. Devices View the devices installed on the computer, including display adapters, disk drives, ports, storage volumes, keyboards, and other system devices. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 121: Location
If the server blade is a new server (never before identified), the established process for managing new computers is executed. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 122: Lights-Out
See Restoring a computer from its deployment history on page 124. History View, print, delete, and save to file a history of deployment tasks. See Viewing a computer’s history on page 125. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 123 Remove a BIS certificate from the selected computer. Certificate Uninstall agent Uninstall the agent from the selected computer. Apply Regular Apply a permanent license if a client computer is using a time- License limited license or requires an updated license. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 124: Restoring A Computer From Its Deployment History
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>. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 125: Configuring Computers
Click OK. 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>. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 126: Power Control
Force application to close without a message option to shut down users without a warning. If you do not select this option, the user is prompted to save work before the power operation continues. Click Yes. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 127: Remote Control
The client and Deployment Server Console must be able to communicate to each other through TCP/IP. To remotely control a managed computer Right-click a computer and click Remote Control > DS Remote Control. This opens the Remote Control window displaying the managed computer’s screen. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 128 Color Depth Remote control properties on page 129. Properties Remote control properties on page 129. To end a Remote Control session, click Control > Close Window in the Remote Control window. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 129 (you must access Admin properties). After opening the Deployment Agent property page, select the Remote Control tab. Select Allow this computer to be remote controlled to provide access from the Deployment Server Console. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 130: Remote Desktop Connection
Copy File to feature. See Copying a file page 188. To end a Remote Control session, click Control > Close Window. Remote desktop connection Remote Desktop connection is available for many Windows operating systems. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 131: Additional Remote Control Programs
Execute from the menu, or clicking this icon in the toolbar. Type a command you would like executed on the selected remote computer(s), or select from a list of previously-run commands. Example: Type regedit to open the registry on the computer. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 132: User Account
A dialog appears in the Deployment Server Console with a list of properties. Select the properties to prompt the user. The properties selected in this dialog are active on the property form sent to the user, letting the user enter information for the selected properties. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 133: Install Automation Partition
During the Deployment Server installation, the Pre-boot Operating System page appears for you to select a default pre-boot operating system, which is used by Boot Disk Creator to create the configurations that boot client computers to automation. You can Altiris Deployment Solution™ from Symantec User’s Guide...
Page 134: Change Agent Settings
Features like rules-based deployment, support for remote management cards, and quick server restoration from a deployment history give you new tools to manage all servers throughout your organization. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 135: Server Management Features
Support for multiple network adapter cards. Because servers may require more than one network interface card, Deployment Server provides property pages to access and configure multiple network adapters remotely from the console. See TCP/IP configuration settings on page 104. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 136: Server Deployment Options
Click the DS tab. Select a pre-boot operating system from the Initial Deploy boot option drop- down list. Click Execute Immediately. Initial Deployment runs automatically for every identified server. Click Save. Click OK. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 137: Managing Server Blades
By default, the replay option is checked when you create a new job. This option replays the job during any rip and replace actions. Symantec provides fail-safe features to ensure that no server is mistakenly overwritten and that all disk images, software, data, and patches are applied to the new server from the history of jobs assigned to the previous server blade.
Page 138: Virtual Bays
Hewlett-Packard high-density blade servers can be deployed and managed from the Deployment Console. The following HP server blades are supported: HP Proliant™ BL e-Class HP Proliant™ BL p-class Proliant™ BL 10e Proliant™ BL 20p Proliant™ BL 10e G2 Proliant™ BL 20p G2 Altiris Deployment Solution™ from Symantec User’s Guide...
Page 139: Dell Server Blades
Solution, but the server blades can also be managed from the physical view in the Rack/ Enclosure/Bay view. The following servers are supported: Fujitsu-Siemens Rack Fujitsu-Siemens Server Blades Servers All Primergy™ rack servers Primergy™ BX300 blade servers Altiris Deployment Solution™ from Symantec User’s Guide...
Page 140: Ibm Server Blades
Computers pane when a match is found. Press F3 to find the next computer that matches the search criteria until there are no more results, or the end of the computer list is reached. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 141: Using Lab Builder
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™ from Symantec User’s Guide...
Page 142 This means you don't have to visit each computer to reset the IP addresses and other settings when you deploy an image. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 143 Upload Registries. This job backs up computer registry files to the Deployment Server. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 144 Altiris Deployment Solution™ from Symantec User’s Guide...
Page 145: Chapter 14: Building And Scheduling Jobs
As jobs are assigned, scheduled and executed, it is helpful to know specific details about their status and assignments. The Deployment Console provides job icons to show the state and status of the job in the Details pane: Altiris Deployment Solution™ from Symantec User’s Guide...
Page 146: New Job Wizard
The New Job Wizard provides integrated features to build, assign, and schedule common deployment jobs. It helps you build the most common jobs, and guides you through additional steps to assign and schedule the jobs to selected computers. It lets you Altiris Deployment Solution™ from Symantec User’s Guide...
Page 147 This option is selected by default. This option replays the job during any rip and replace actions. After creating a job, the job appears in the Jobs pane of the Deployment Console with the deployment tasks listed in the Tasks list. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 148: Migrating Computers
Click the option to deploy a disk image and migrate the personality settings to the computer. (Optional) Select Install software packages prior to applying the personality on the destination computer to install software packages on the computer. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 149: Selecting Computers In The New Job Wizard
Select Computers dialog, 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. Right-click a computer in the Destination column to replace it with another Altiris Deployment Solution™ from Symantec User’s Guide...
Page 150: Setting Up Conditions In The New Job Wizard
A new job is added to the Jobs pane in the Deployment Console. You can group and organize jobs, and access and apply them to computers or computer groups from an index of prebuilt jobs. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 151: Job Scheduling Wizard
Setting conditions on a job lets you run selected tasks only on computers that match defined criteria. As a result, you can create a single job with tasks defined for computers with varying properties, including operating system types, network adapters, Altiris Deployment Solution™ from Symantec User’s Guide...
Page 152 Example: When setting conditions based on the NICS table on the nic_device_id and nic_vendor_id columns, you must use decimal values. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 153: Order Condition Sets
Use the up and down arrows to change the order of the scheduled jobs. Click OK. Note The Schedule Job dialog is the same for Rescheduling Jobs, New Job Wizard, and Job Scheduling Wizard. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 154 (or you can drag computers to a file or package in the Resources view). A job is created automatically for each assigned package in the Systems Jobs > Drag-n-Drop folder. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 155: Deployment Tasks
Modifying configuration on page 182. Back up Registry. Copy the registry files of selected computers and save the registry file settings to a selected directory. See Backing up and restoring registry files page 183. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 156: Supported Live Task Types
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 Altiris Deployment Solution™ from Symantec User’s Guide...
Page 157: Creating A Disk Image
This task creates an image of a computer’s hard disk. You can save the disk image as an .IMG, .EXE, .WIM, .DMG, or .GHO file. For more information about Ghost, see the Symantec Ghost Imaging Foundation documentation. Create an image file by using the New Job Wizard or adding the task when building new jobs.
Page 158 When imaging computers where images are stored on the managed computer’s hidden automation partition, use the option to remove the automation partition only when you want to clear all images from the computer. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 159: Creating A Mac Image
By default, all partitions of disk 1 are imaged. To image a different disk, provide the disk number in the Additional Parameters field using the same format. Choose from one of the following options to add the path and file name for the disk image: Altiris Deployment Solution™ from Symantec User’s Guide...
Page 160: Creating A Ghost Image
The Automation pre-boot Environment for Mac Image is the Default Automation when capturing Mac images. Creating a Ghost image Symantec™ Ghost Solution Suite is a corporate imaging and deployment solution. It also provides operating system migration, software distribution, computer personality migration, hardware and software inventory, and secure system retirement.
Page 161: Advanced Sysprep Settings For Creating A Disk Image
You can use the Sysprep advanced settings dialog to specify the settings for any Windows Vista operating system. If you select Windows Vista as the operating system under Sysprep settings on the Create Disk Image dialog and click Advanced Altiris Deployment Solution™ from Symantec User’s Guide...
Page 162: Advanced Sysprep Settings For Creating A Disk Image In Windows Vista
/logPth that specifies the fully qualified path where the DA log files are written. /logID that specifies the ID to prepend to the log file name. For more information about DeployAnywhere or Ghost, see the Symantec Ghost Imaging Foundation documentation.
Page 163 If you clear this option, a warning appears, confirming that you want to remove the configuration step after the image is deployed. As a result, the imaged computer may not reconnect to the network. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 164: Distributing A Mac Image
(Optional) Set Return Codes. See Setting up return codes on page 193. Click Finish. The task appears in the Task list for the job. The Mac image is deployed when you run this task. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 165: Distributing A Ghost Image
NetBoot in the Administration Guide. Distributing a Ghost image You can distribute a Ghost (.GHO) image using the Distribute Disk Image task. For more information about Ghost, see the Symantec Ghost Imaging Foundation documentation. To distribute a Ghost image On the Distribute Disk Image dialog, select the Select a disk image file option.
Page 166: Advanced Sysprep Settings For Distributing A Disk Image
RDeploy options: Graphical Mode[RDeploy]. Click this option to choose RDeploy as the imaging executable. Text Mode[RDeployT]. Click this option to choose RDeployT as the imaging executable. Text Mode or RDeployT is the default choice. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 167: Imaging Computers From Usb Disk On Key (Dok) Devices (Jumpdrives)
Copy HIMEM.SYS to the device. Copy RDeployT.exe from the <InstallPath>\eXpress\Deployment Server\RDeploy\DOS directory to the device. Copy the <Filename>.img file to the device. Create an Autoexec.bat with the script and command-line option, rdeployt -md - fc:\IMAGE.img -d2 Altiris Deployment Solution™ from Symantec User’s Guide...
Page 168: Scripted Os Install
Linux. Run scripted install jobs to remotely install different versions of Linux. You can customize sample scripted install jobs installed with the Deployment Server system and create a kickstart answer file to remotely run a scripted install. See Scripted install for Linux on page 175. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 169: Scripted Install For Windows
171. Note Before running a scripted install, you must install DOS. However, DOS is not required if you are using your own scripts or utilities to partition and format the client computer. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 170: Select Os Version And Language
Automation (Pre-boot Environment). Select the required pre-boot environment from the Automation (Pre-boot Environment) drop-down list. The option reported by the PXE Manager is the default pre-boot environment option. List of supported multiple languages: German French Spanish Japanese Simplified Chinese Altiris Deployment Solution™ from Symantec User’s Guide...
Page 171: Installation Source Files
Deployment Share. The Deployment Server system includes a DR DOS image file that is selected by default. You can create your own MS DOS image from your Windows CD and build a job. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 172: Import An Answer File
Enter a name for the section. If you add a section, this name appears in the new tab in the Answer File setup dialog. Enter a description. Enter comments to describe the new section. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 173: Delete A Section
View or edit Deployment Agent for Windows settings in this dialog. You can change agent settings using this text-edit dialog. See Deployment agent settings on page 110 for a list of the Deployment Agent properties. See also Scripted install for Windows on page 169. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 174: Scripted Install Summary
On the Scripted OS Install Commands page of the Scripted OS Install dialog, set the command-line options for the cmdlines.txt files and enter the Additional commands in the cmdlines.txt file. (See Command-line switches for scripted install on page 173.) Click Finish. The job Altiris Deployment Solution™ from Symantec User’s Guide...
Page 175: Scripted Install For Linux
Select Run in quiet mode to install the package without requiring user interaction. Specify the users to associate with the .RIP or the Personality Package. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 176 (Optional) Set Return Codes. See Setting up return codes on page 193. Click Finish. The task appears in the Task list for the job. The software is distributed when you run this task. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 177: Distribute Software Advanced
For more information on SVS Help, refer to Software Virtualization Solution on page 78. Note This task runs only on Windows computers. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 178 Action drop-down list. The actions are: Action Name Description Activate Activate layer. Activate on Activate layer on startup. startup Activate and Activate layer and activate it whenever the computer starts up. Activate on startup Deactivate Deactivate layer. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 179: Importing Package Advanced
146 and Building new jobs on page 150. Also see Distributing personality settings on page 180 to migrate settings to another user. After creating a job, click Add > Capture Personality. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 180: Capture Personality Advanced Options
The Distribute Personality task lets you save personal display and user interface settings defined in the operating system for each user. You can distribute Personality Packages to migrate personality settings. This task runs Altiris PC Transplant from the console to capture and distribute settings. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 181: Distributing Personality Settings
(Optional) Set Return Codes. See Setting up return codes on page 193. Click Finish. The task appears in the Task list for the job. The personality is distributed when you run this task. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 182: Distribute Personality Advanced
193. Click Finish. The task appears in the Task list for the job. The configuration is modified when you run this task. See also Modifying tasks in a deployment job on page 190. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 183: Backing Up And Restoring Registry Files
Use this task to gather inventory from an individual computer or a group of client computers. This ensures that the Deployment Database is updated with the latest computer properties information, which includes the following information: Applications Devices Drivers Hardware Location Altiris Deployment Solution™ from Symantec User’s Guide...
Page 184: Running A Script
The Deployment Server assumes a return code of zero (0) as a successful script execution. Some programs return a code of one (1) to denote a successful script Altiris Deployment Solution™ from Symantec User’s Guide...
Page 185: Script Information
Deployment Agent installed, which prohibits it from using a network security account. Run script in console user session. For Windows 2008 and Vista, you can see the output of jobs on a local desktop and use that output for debugging Altiris Deployment Solution™ from Symantec User’s Guide...
Page 186: Using Logevent And Wlogevent In Scripts
The following is an example of the file that is modified to return a code of 0 (which is the success code recognized by the Symantec Management Console and utilities). You can make similar changes to your script files as needed.
Page 187 REM Execute WLogEvent.exe from CMD script REM This script requires WLogevent.exe to reside on the client REM in the temp directory .\WLogevent.exe -c:0 -l:1 -ss:“Running Dir on %NAME%" .\WLogevent.exe -c:0 -l:1 -ss:“Finished with the DIR command on %NAME%" Altiris Deployment Solution™ from Symantec User’s Guide...
Page 188: Copying A File
Location variables are being added to the Deployment Server for the Copy Files feature, letting you enter a token variable instead of requiring a complete location path when copying files to a managed computer (a client computer running the Deployment Agent). Altiris Deployment Solution™ from Symantec User’s Guide...
Page 189: Copy File To Advanced
Select Force application to close without a message, if required. Click Next. (Optional) Set Return Codes. See Setting up return codes on page 193. Click Finish. The task appears in the Task list for the job. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 190: Waiting
Right-click in the Details pane and select Paste. The tasks appear at the bottom of the task list, and use the condition settings of the current job. Change the order of the task using the up and down arrows. The tasks run in the order listed. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 191: Modifying Multiple Modify Configuration Tasks
(the current job sends modified configuration files already created). If you click YES, a Modify Job Wizard appears with a list of each managed computer scheduled to change configuration settings. Select one or more computers and click Next. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 192: Creating New Script Files
To copy jobs and job folders In the Jobs pane, right-click a job or job folder you want to copy, and click Copy. In the Jobs pane, right-click the destination job folder and click Paste. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 193: Importing And Exporting Jobs
If no custom code is assigned to the return code, the action set in the default runs. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 194 Select return codes for the current job from the drop-down list. To add master return codes Select a job from the Jobs pane. Click Add in the right pane to add a task. Select the task. The task dialog appears. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 195 Select the Add to Master return code list check box to add the custom code to the master return code list. The code is listed in both the Other return codes and Altiris Deployment Solution™ from Symantec User’s Guide...
Page 196: Sample Jobs
Limit users on the managed computer to access the administrator properties only if they enter the set password. If the password is entered incorrectly three times, a 3- minute lock-out time period begins and an appropriate error message displays. You can also uninstall DAgent. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 197: Uninstalling Dagent
Symantec Backup Exec System Recovery (BESR) sample jobs Deployment Solution includes several BESR sample jobs. For more information on BESR, see http://www.symantec.com and search for Symantec Backup Exec System Recovery. 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.
Page 198: Configurations
Click Add. A configuration set appears in the Configurations menu field. The Configuration page of the New Job Wizard appears. Enter values to set computer and network properties for new computers. See Modifying configuration on page 182 for a list of property categories. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 199: Advanced Configuration
The default setting is 60 seconds. Click OK, or click the Advanced tab to stop servers or workstations from running configuration task sets and jobs automatically. See also Sample jobs on page 196. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 200: Advanced
Identifying a computer as a server by the operating system cannot be accomplished for new computers until the server operating system has been installed. Select Workstations/Clients to force desktop and laptop computers to stop before automatically running Initial Deployment. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 201: Part Iv: Best Practices
Part IV Best Practices This section provides details on many of the management tasks available in Altiris® Deployment Solution™ software. Deployment Solution...
Page 202: Chapter 15: Securing Deployment Solution
Chapter 15 Securing Deployment Solution To effectively manage computers, Altiris® Deployment Solution™ software requires access beyond the files and database owned by the application. Example: Deployment Solution requires rights to install software on managed computers and rights to join computers to a domain during configuration. The broad range of tasks performed by Deployment Solution enables simplified management but also introduces a greater need for strong security policies.
Page 203: Service Account
Securing Deployment Solution Account Description Domain Join Used to join computers to a domain during configuration. Deployment Share Provides access to the Deployment Share in the Read/Write automation environment. These accounts should not be part of any group, and should not posses interactive login privileges.
Page 204: Domain Join Accounts
Securing Deployment Solution Rights Description File System This account requires full control of your Deployment Share, and does not require administrative privileges on the computer hosting your Deployment Share. Database This account requires the db_owner role on your Deployment Database. See Part 3: Database Security (page 207) for more information.
Page 205: Part 2: Deployment Administrator Accounts
Securing Deployment Solution efficient to access the Deployment Share directly rather than accessing it through the Deployment Server. Grant the rights recommended in the following table: Rights Description File System Grant read/write privileges to your Deployment Share. 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.
Page 206: Deployment Console Security
Securing Deployment Solution One major advantage of the Deployment Solution security model is that administrators do not need to be granted explicit rights on any managed computers. All access is filtered through the integrated role-and-scope based security in the Deployment Console.
Page 207: Grant Rights To Administrators
Securing Deployment Solution Grant Rights to Administrators In the Deployment Console, click Tools > Security. Select a user or Group and click Rights. Enable the rights you want granted. Grant Permissions to Administrators Right click a Computer, Computer Group, or Job and select Permissions. Select a user or group and enable or disable the permissions you want granted.
Page 208: Required Database Rights
Securing Deployment Solution Required Database Rights This section contains a list of the database rights that need to be granted to use Deployment Solution, and covers: Rights Required to Install (page 208) Rights Required for the Services Account (page 209) Rights Required for Deployment Administrators (page 209) Rights Required to Install...
Page 209: Rights Required For The Services Account
Securing Deployment Solution Rights Required for the Services Account The account used to run your Deployment Services needs to have database owner rights: Open Enterprise Manager and connect to your SQL Server. Browse to Security > Logins: Double-click the account you are using to run the Deployment services. If the login is not listed, add it.
Page 210: Part 4: Securing Communication
Securing Deployment Solution This prevents you from manually granting this access to individual administrators as they are added or removed from Deployment management responsibilities. Open Enterprise Manager and connect to your SQL Server. Browse to Security > Logins. Add each user or group that will manage computers using Deployment Solution. For each user or group, on the Database Access tab, grant the public role for the eXpress database: Part 4: Securing Communication...
Page 211 Securing Deployment Solution To enable server connection security In the Deployment Console, right-click a computer or group and select Change Agent Settings > Production Agent. Select Connect directly to this Deployment Server and provide the hostname. Select to Enable key based authentication to Deployment Server and provide the path to your server.key file on your Deployment Share: Deployment Solution...
Page 212: Additional Agent Security
Securing Deployment Solution Additional Agent Security The Security tab on the Agent Settings screen provides additional security options, 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. This prevents the session from being broken manually on the managed computer.
Page 213: Appendix A: Remote Agent Installer Rights
Securing Deployment Solution 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, you need an account with Local User rights. You only need access to this account when performing the one-time agent installation, so either use your domain administrator, a domain account with local user rights, or any other account with local rights.
Page 214: Appendix C: Managing Key-Based Agent Authentication
Securing Deployment Solution Click Update. Appendix C: Managing Key-Based Agent Authentication Key authentication is configured and ready to be enabled after installation. This appendix contains information on backing up your authentication keys and enabling redirection to another Deployment Server. Backing up the Server Private Key During installation, a private key is generated on the Deployment Server and stored in the registry at the following location: HKLM\Software\Altiris\Altiris...
Page 215: Chapter 16: Migrating Application Data And User Settings
Chapter 16 Migrating Application Data and User Settings To perform migration, 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). Deployment Solution...
Page 216: Chapter 17: Capturing And Deploying Disk Images
Chapter 17 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, or one or more of the partitions on the hard drive. This file can be used to restore the structure and contents of the imaged hard drive. Imaging in Deployment Solution Deployment Solution provides several tools to simplify the imaging process, including tools to perform hardware independent imaging using sysprep.
Page 217: Partition Size
Capturing and Deploying Disk Images When a computer receives an image, you can select which partitions to download. The default setting is to restore all partitions, which would overwrite any existing partitions. To keep an existing partition, you can specify which partitions to download and which to ignore.
Page 218: Http Imaging
Capturing and Deploying Disk Images group. If a single computer fails, it will drop out of the session and the session will continue. 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...
Page 219: Managing Images
Capturing and Deploying Disk Images Managing Images You can view and make changes to RapiDeploy image files (*.img) using the Altiris ImageExplorer. For more information, see Altiris® ImageExplorer on page 316. Deployment Solution...
Page 220: Chapter 18 Imagex Imaging
Chapter 18 ImageX Imaging Deployment Solution provides native support for imaging computers using ImageX. Obtaining and Installing ImageX Before using ImageX, you must download and install the Microsoft Windows Automated Installation (WAIK) toolkit. This is available as part of the Business Desktop Deployment (BDD) Workbench.
Page 221: Chapter 19: Mac Imaging
Chapter 19 Mac Imaging Deployment Solution supports native imaging of Mac PowerPC and Intel-based computers. Using an OS X Server to provide the boot image, Deployment Solution can capture and deploy images to most Mac computers. Requirements: A Mac computer to provide the source for the automation image. Instructions for creating this image are contained in Creating an Automation Image (page 221).
Page 222: Step 1: Configure A Source Computer
Mac Imaging Step 1: Configure a Source Computer In this step, a basic OS X system is prepared to provide the source for your automation boot image. If your source computer is running OS X 10.5, you must update to 10.5.2 or later. Perform a fresh installation of OS X on the source computer.
Page 223: Step 3: Image The Source Computer
Mac Imaging This computer is ready to be imaged. In Step 3: Image the Source Computer (page 223), we use the imaging utility, hdiutil, to capture and store an image of this computer. Step 3: Image the Source Computer Connect to your NetBoot Server and mount a NetBoot share. Typically, this share would be NetBootSP0.
Page 224 Mac Imaging Run the System Image Utility (Applications > Server > System Image Utility). In the left pane, select the image you mounted in step 1. In the right pane, select NetBoot Image then click Continue. Provide Automation as the image name, then click Create. When the creation completes, provide Automation as the folder name and save it to folder.
Page 225: Step 2: Start The Netboot Service
Mac Imaging Step 2: Start the NetBoot Service On the OS X Server that is hosting the NetBoot service, open the Server Admin utility. Expand the services on the localhost. Start the AFP service (if it is not already started). Start the DHCP service.
Page 226: Chapter 20: Symantec® Ghost® Imaging
Important Deployment Solution 6.9 SP1 and later includes the Ghost executable. You do not have to perform this step to use Symantec Ghost with Deployment Solution versions after 6.9 SP1. 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.
Page 227: Chapter 21 Software Packaging
Chapter 21 Software Packaging Deployment Solution includes the robust Wise Packager for Altiris Deployment Solution. This article presents an overview of the Wise Packager, including a walk-through of the software capture and distribution process. Information for users migrating from RapidInstall to the Wise tools is provided as well. Why Use Software Packaging? Installing and managing software is a major part of successful computer management.
Page 228: Setting Up A Reference Computer
Software Packaging The following sections provide additional details on this process: Step Description Setting up a Reference This computer hosts the capture process. Computer (page 228) Capturing a Software Using Wise Setup Capture to capture changes to the Package (page 228) reference computer.
Page 229: The Capture Process
Software Packaging vendor-supplied MSIs is not recommended since it could introduce incompatibilities with future updates. Hardware drivers, operating systems and updates should not be captured, due to their complexity and Windows File Protection. The Capture Process Before you begin, review the guidelines in Appendix C: SetupCapture Guidelines (page 232).
Page 230: Advantages Of Windows Installer
Software Packaging A set of guidelines. An Application Programming Interface (API). A runtime service that makes application installation and management part of Windows services. Windows Installer is not a installation authoring tool, but rather an installation engine and rule set. The Windows Installer engine resides on the destination computer as part of the operating system.
Page 231 Software Packaging Windows Installer Description Benefits Self-healing With self-healing (also called automatic repair and self- repair), the application repairs missing components. When an application starts, Windows Installer checks a list of key files and registry entries. If it detects any problems, Windows Installer repairs the application using a cached database that contains key paths to application components.
Page 232: Appendix C: Setupcapture Guidelines
Software Packaging Windows Installer Description Benefits Dynamic Source List Provides sources for the MSI to repair from and enable advertising. Multiple possible locations for the MSI package are listed, ensuring access even between different networks. Group Policy and Sets privileges to control the user and application rights, Security and provides a more secure environment.
Page 233 Software Packaging Registry keys that define an environment variable are converted to an environment variable in the repackaged installation. Deployment Solution...
Page 234: Chapter 22 Deploying Scripts
Chapter 22 Deploying Scripts Altiris Deployment Solution provides a number of pre-defined tasks you can combine to create complex management jobs. When you need to perform a management task that isn’t covered effectively by the predefined tasks, DS provides an environment to pre-process, deliver, and execute VBScripts, batch files, and shell scrips.
Page 235: Writing A Script
Deploying Scripts Using the flexibility of tokens and the processing power of the command processor of your OS, you can develop and deploy scripts ranging from a simple file search to a full system customization. This chapter discusses how to effectively create and deploy scripts in your DS environment.
Page 236: Retrieving Database Values Using Tokens
Deploying Scripts The following table contains the predefined server scripting commands: Server Scripting Commands Command Description Unloads BootWorks to provide additional memory for complex scripts. BootWorks BootWorks is unloaded automatically when you specify ScriptedInstall. Unload BootWorks Unload Tokens are replaced automatically in your scripts. This command ReplaceTokens replaces tokens in additional files, such as those used when configuring a computer.
Page 237: Running Scripts On The Server
Deploying Scripts After replacing tokens in the script itself, the server processes the next command in this script: ReplaceTokens. Since the token replacement process already replaced the compname token, the ReplaceTokens command works as expected and creates a unique system.inf file for each computer, containing values unique to that computer. The script is delivered to the client, and the Firm utility finds the correct file on the eXpress share to copy to the production drive.
Page 238: Dos/Cmd Error Handling
Deploying Scripts To provide additional feedback when running scripts, Altiris provides an error logging utility, called logevent, for DOS, Windows, and Linux. This utility lets you send error, warning, and informational messages back to your server from within scripts, and job execution can be stopped based on the messages you return.
Page 239: Visual Basic Error Handling
Deploying Scripts LOGEVENT -c:2 -l:3 -ss:”Bad command or file not found.” GOTO END :ONE LOGEVENT -c:1 -l:1 -ss:”Error 1.” :END Visual Basic Error Handling By including the vbscript server command in a script deployed to a Windows or DOS environment, DS executes the script using Visual Basic. Visual Basic has a powerful, integrated method to handle errors.
Page 240: Linux Shell Error Handling
Deploying Scripts End If Next Next Else WSHShell.Run ".\WLogevent.exe -c:" & ErrNum & " -l:3 - ss:""Error:" & _ Err.Description & """" , 1, true Err.Clear End If Linux Shell Error Handling The logevent command is provided in the Linux agent, so any Linux computer with the agent installed has local access to logevent.
Page 241: Chapter 23: Creating An Image Distribution Framework
Chapter 23 Creating an Image Distribution Framework Why Use an Image Distribution Framework? In distributed networks, your ability to effectively manage computers is often limited by the speed of your network link to remote locations. In Deployment Solution, computer imaging can often require file transfers in excess of several gigabytes, even when multicasting.
Page 242: Pxe Redirection
Creating an Image Distribution Framework PXE Redirection PXE solves this problem by enabling you to redirect a shared PXE configuration to a configuration on a local PXE server. This lets you assign a job across multiple locations, and have computers at each location boot using a local PXE server with configuration specific to this location.
Page 243: Step Two: Replicate Images
Creating an Image Distribution Framework and password on each server. This account should not possess group membership, interactive login privileges, or any additional rights. This account is specified when creating the boot configuration in Boot Disk Creator, and the username and password must be the same for each share. Step Two: Replicate Images Before an image can be used, it must be replicated to the image store file share at each location.
Page 244: Getsrv.exe Parameter Descriptions
Creating an Image Distribution Framework GetSRV.EXE Parameter Descriptions The following table contains descriptions of the getsrv.exe parameters: Parameter Description /s [filename] File containing the list of servers hosting local image stores. This file is typically placed in the deployment share. See Create a Server Lookup File (page 243).
Page 245: Modify Mapdrv.bat To Call Getsrv.bat
Creating an Image Distribution Framework Modify Mapdrv.bat to call Getsrv.bat Mapdrv.bat is called to map drives in the automation environment. This file is modified to call the getsrv.bat file you modified in a previous step. After this executes, the server name variable is available to map the drive to your local image store.
Page 246: Chapter 24: Deploying And Managing Servers
Chapter 24 Deploying and Managing Servers Deployment Solution provides additional features to remotely install, deploy and manage network and web servers. From the Deployment Server Console, you can configure new server hardware, install operating systems and applications, and manage servers throughout their life cycle. And because servers are mission-critical, you can set up a system to quickly deploy new servers or automatically re-deploy servers that have failed.
Page 247: Server Deployment Options
Deploying and Managing Servers Server icons. The Deployment consoles display icons to identify servers across the network. Like other computer icons in the console, server icons can be selected to view server properties or assign specific jobs and management tasks Icon Description Indicates a server is active and a user is logged on.
Page 248: Managing Server Blades
Deploying and Managing Servers computer with Sample jobs. Initial Deployment includes a feature to prohibit servers from being deployed automatically. Click Initial Deployment and select Properties. Click the Advanced tab. Click the Servers check box and click OK. Initial Deployment will not run for any computer identified in the console as a server. Change PXE Options for Initial Deployment If installing a server using a PXE Server, the server will attempt to install but will not run automatically using default settings.
Page 249: Managing New Server Blades
Deploying and Managing Servers Using Deployment Solution, you can employ “rip and replace” technology that allows you to insert a new server blade and automatically configure and deploy it exactly like the previously installed server blade, allowing you to replace any downed server and get it back on line quickly.
Page 250: Virtual Bays
Deploying and Managing Servers For HP blade servers in the physical view the Rack name can be a custom name in the console, with all subordinate Enclosures and Bays also identified. Example: <rackName> <enclosureName> <bayNumber> See also Server Management Features on page 246 and Server Deployment Options page 247.
Page 251: Fujitsu-Siemens Server Blades
Deploying and Managing Servers Dell <enclosureName> <bayName> See also Server Management Features on page 246 and Server Deployment Options page 247. Fujitsu-Siemens Server Blades Fujitsu-Siemens high-density blade servers can be deployed and managed from the Deployment console. All Fujitsu-Siemens Rack Servers are supported by Deployment Solution, but the server blades can also be managed from the physical view in the Rack/ Enclosure/Bay view.
Page 252: Part V: Operating System And Platform Reference
Part V Operating System and Platform Reference This section contains operating system and platform-specific information you need to consider when managing computers. Deployment Solution...
Page 253: Chapter 25: 64-Bit Platforms
Chapter 25 64-bit Platforms Deployment Solution has been designed to make managing different platforms as seemless as possible. This section walks you through the enhancements added to support 64-bit, and includes tips to more effectively manage these computers. 64-bit Job Conditions and Filters Functionality has been added to let you set conditions and filters based on the computer architecture.
Page 254: Chapter 26 Linux And Unix Systems
Chapter 26 Linux and Unix Systems Altiris Deployment Solution has several tools to effectively manage Linux and Unix computers, including: A native Linux and Unix agent, called ADLAgent, in the Linux production and automation environments. 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...
Page 255: Imaging Linux And Unix Filesystems
Linux and Unix Systems Imaging Linux and Unix Filesystems RapiDeploy provides native imaging support for EXT2, EXT3, and LVM file systems. Other file systems can be imaged, but you need to use the -raw switch. Linux Bootloaders There are a few considerations you must use to preserve the functionality of Linux bootloaders.
Page 256: Chapter 27 Managing Thin Clients
Chapter 27 Managing Thin Clients Thin clients are a low cost, low maintenance solution for organizations that want to perform tasks or access programs such as: Web browsing, Java-based applications and terminal emulation, or line of business (LOB) applications. 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.
Page 257: Supported Thin Client Manufacturers
Managing Thin Clients Distribute disk images Remote Control clients (24 bit color depth only. No chat or send file features) Power Control (restart/shutdown/wake up jobs) Set computer properties Create conditions to run jobs and filter computers Modify client properties via Windows and Linux agent settings Supported Thin Client Manufacturers Currently, Altiris supports Fujitsu-Siemens, HP, and Neoware thin clients.
Page 258: The Enhanced Write Filter
Managing Thin Clients Because application developers can choose from over 10,000 individual feature components, the image footprint is smaller and can boot basic images as small as 8MB. The Deployment Agent used for computers running Windows is the same agent that is installed on thin clients running the Windows XP Embedded operating system.
Page 259: Using The Ewfmgr Utility
Managing Thin Clients EWF is not disabled and enabled properly, after you run a Deployment job, the next time a thin client reboots, data will be lost. See also: (page 145), Deployment agents (page 109). 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.exe, which is stored in the C:\Windows\System32 folder.
Page 260: Windows Ce .Net
Managing Thin Clients Example Description ewfmgr -all This displays the current Enhanced Write Filter settings. ewfmgr c: -disable This disables the Enhanced Write Filter on the C: volume. ewfmgr c: -enable This enables the Enhanced Write Filter on the C: volume. Although the enhanced Write Filter manager can be run from a thin client, it is more efficient to include it as part of your Deployment Job.
Page 261: Chapter 28: Windows Vista
Chapter 28 Windows Vista Deployment Solution 6.8 introduced a new Deployment Agent, called DAgent, to support windows Vista. DAgent is used to: Install software Execute scripts Gather inventory and system configuration Integrate Windows Remote Desktop into the Deployment Console Install the Deployment Agent on Vista The DAgent installation program is contained in the Agents\AClient folder on the Deployment Share.
Page 262: Vista Run Script Tasks
Windows Vista The software you are distributing must be Vista compliant. The installation is set to run as completely silent. No user input is required by the installation prcess. If the package requires additional files, the "copy all directory files" and/or "copy all subdirectories"...
Page 263: Chapter 29: Mac Deployment Agent
Chapter 29 Mac Deployment Agent Installing The Mac Deployment Agent Connect to the Deployment Share using Finder > Go > Network > domain > Express, replacing domain with the domain containing your Deployment Server. Browse to the folder. Agents/ADLAgent Extract and run the program contained in altiris-adlagent-x-darwin.zip. Unzip and double-click the secondary configuration application.
Page 264: Part Vi: Reference: Deployment Solution Help Files
Part VI Reference: Deployment Solution Help Files This section contains the help files that are launched from the Deployment Console, Web Console, and other Deployment Solution utilities. Translated versions of these help files are available in the product. Deployment Solution...
Page 265: Chapter 30: Deployment Server Configuration Utility
Chapter 30 Deployment Server Configuration Utility The Altiris® Deployment Server® Configuration Utility provides general configuration preferences for the Deployment Server. You can use the Deployment Server Configuration Utility to: Set up an account for the Deployment Server. See Service Logon Account page 266.
Page 266: Service Logon Account
Deployment Server Configuration Utility Account Opens the Service Logon Account dialog, which lets you specify the logon account used by the Deployment Server service. The LocalSystem account requires a simple installation that runs Deployment Server services on the local computer, prohibiting access to network shares or components.
Page 267: General Options
Deployment Server Configuration Utility Click OK. In the Service Logon Account dialog, select an account option. General Options Update Inventory on active computers. Inventory provides software and hardware information about a client computer. You can update inventory on active computers at specified intervals.
Page 268 Deployment Server Configuration Utility Remove Removes the selected drive mapping. Data store Specifies the path to stored packages and files and other path Deployment Solution functions (such as license verification). The default path is C:\Program files\Altiris\express\Deployment Server. Note Do not use this setting to change the path to the Client Access Point. Modifying this setting does not automatically let you use a shared directory other than the express share.
Page 269: Transport Option
Deployment Server Configuration Utility Transport Option The Transport tab lets you specify settings for the Deployment Server transport protocols. Item Description Disable multicast Disables multicast support, which means that client support (clients computers must connect to the Deployment Server using must connect using TCP.
Page 270: Disk Imaging Option
Deployment Server Configuration Utility Disk Imaging Option The Disk Imaging tab lets you specify the number of client computers for image multicasting and the maximum bandwidth to use during disk image multicasting. Note When multicasting a disk image using the PXE Server, the boot disk on the PXE Server cannot be configured with an Intel Universal NIC driver (also known as an UNDI driver).
Page 271: Authentication Option
Deployment Server Configuration Utility Click OK. To set the maximum bandwidth used during multicasting Open the Deployment Server Configuration Utility in the Control Panel of the Deployment Server computer. 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.
Page 272: Debug Option
Deployment Server Configuration Utility Define IP Addresses Select the Allow/reject agents based on their IP address check box and click Define IP Addresses. The TCP/IP Connection Filters dialog appears. You can add, modify or remove a Start IP address and the corresponding End IP address. You can also specify whether to allow or reject only these IPs to connect.
Page 273: Chapter 31: Introduction To Altiris® Boot Disk Creator
Chapter 31 Introduction to Altiris® Boot Disk Creator Altiris® Boot Disk Creator (BDC) creates and configures the boot images used to start computers in the pre-boot automation environment. These images leverage WinPE, Linux, and DOS operating systems and include native Deployment Agents to run assigned tasks.
Page 274: Toolbar Description
Introduction to Altiris® Boot Disk Creator boot configurations directly from Boot Disk Creator and import the boot images into the PXE Configuration Utility. The PXE Configuration Import feature lets you import images created by Boot Disk Creator or any other third-party imaging software, but you cannot edit the boot images after importing them.
Page 275: New Configuration Wizard
Introduction to Altiris® Boot Disk Creator New Configuration Wizard You can create multiple configurations to support varying types of computer environments. Before you begin, you must install the pre-boot operating system files that Boot Disk Creator uses to create new configurations. See Install Pre-boot Operating System Files on page 288.
Page 276: Multi-Network Adapter Configurations
Introduction to Altiris® Boot Disk Creator Novell NetWare (VLM): Select this option to store images on a NetWare server with VLM client computers by using IPX network communications. Novell NetWare (Client32): Select this option to store images on a NetWare server with 32-bit client computers.
Page 277: Have Disk
Introduction to Altiris® Boot Disk Creator Note This option is available only for WinPE, and is selected by default. Select a driver from the network adapter drivers list. You must create a new configuration for each type of network adapter that is installed on the client computers, unless you want to create a Multi-NIC configuration.
Page 278: Tcp/Ip Protocol Settings
Introduction to Altiris® Boot Disk Creator IRQ (protocol.ini): Add parameters to the network setup section of the protocol.ini file. Novell VLM clients Emm386 memory (config.sys): Append memory address information to this line in the config.sys file. Advanced settings (config.sys): Add parameters to the NIC section of the net.cfg file.
Page 279 Introduction to Altiris® Boot Disk Creator To set the TCP port on the Deployment Server From the Deployment Server, click Start > Control Panel > Altiris Deployment Server > Options > Transport tab. You can also click Start > All Programs > Altiris > Deployment Solution > Configuration >...
Page 280: Network Connection
Introduction to Altiris® Boot Disk Creator Network Connection This option lets you define the way the client computers connect to the Deployment Share or a file server that stores image files. Windows Workgroup: Enter the workgroup for the Deployment Share or file server. NetWare Server name: Enter the server name for the Deployment Share or file server.
Page 281: Winpe Boot Option Settings
Introduction to Altiris® Boot Disk Creator 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. WinPE Boot Option Settings Select the boot model and optional components to include with this configuration. Typically, you can use the default boot model unless you are experiencing driver detection problems.
Page 282: Additional Files
Introduction to Altiris® Boot Disk Creator You can edit all other files within a configuration as needed. However, after you edit a configuration, Boot Disk Creator rewrites certain files within the configuration so that drive mappings and mount points are always updated. The following files are rewritten after editing configurations: DOS - mapdrv.bat, unmapdrv.bat Linux - mounts.local...
Page 283: Create Pxe Boot Image Files (Pxe)
Introduction to Altiris® Boot Disk Creator Copy files from a network folder and paste them into the configuration folder. Right-click a configuration and select Add File. A browser dialog appears to navigate to the file you want to add. Right-click a configuration and select File > Text file. A new empty text file is added to the left pane.
Page 284: Create Automation Partition Install Package
Introduction to Altiris® Boot Disk Creator Where you open the Create Boot Disk dialog from The type of media you selected to create The pre-boot environment you specified in the configuration you created However, based on your selections, Boot Disk Creator shows the appropriate dialog pages when creating bootable media.
Page 285: Create Automation Boot Disk
Introduction to Altiris® Boot Disk Creator Create an embedded ___ automation partition (recommended): Select this option to install an embedded DOS, Linux, or WinPE partition to a client computer’s hard disk. Create a hidden ___ automation partition (for partitions greater than 50 MB): Select this option to install a hidden DOS, Linux, or WinPE automation partition.
Page 286: Create Network Boot Disk
Introduction to Altiris® Boot Disk Creator Show fixed drives: If you try to select a USB flash drive from the Bootable disk drop- down list, but you cannot find it even after clicking Rescan drives, it is possible that the flash drive you are using appears in Windows as fixed instead of removable.
Page 287: Remove Automation Partition
Introduction to Altiris® Boot Disk Creator Remove Automation Partition This feature lets you remove an automation partition from a client computer’s hard disk. You can create bootable CDs, flash drives, and floppy disks to use manually at the client computers, or you can create a Windows uninstall package that can be distributed to a client computer through a deployment job.
Page 288: Missing Files For Processor Types
Introduction to Altiris® Boot Disk Creator Missing Files for Processor Types For the most part, Boot Disk Creator configurations are independent of architecture. However, if you manually add executables to a configuration that supports multiple processor types, you must provide a version of the file for each architecture you include. Example: If you have selected x86 and x64 versions of the Linux pre-boot environment for a configuration, and you add an executable, Boot Disk Creator checks the file header to see which architectures the executable supports.
Page 289: Dos
Introduction to Altiris® Boot Disk Creator You can install FreeDos, MS-DOS, or both. See FreeDOS on page 289 and MS-DOS page 289. However, you can only run one version of DOS at a time. See Set Default Pre- boot Operating System on page 290.
Page 290: Winpe
Introduction to Altiris® Boot Disk Creator WinPE Altiris supports WinPE as a pre-boot environment for Boot Disk Creator. See the release notes for the current list of supported WinPE versions and for specific installation instructions. Set Default Pre-boot Operating System While creating an automation partition, from the Tools menu on the Boot Disk Creator interface, you must select the pre-boot operating system that you want to set as the default, such as FreeDOS or MS-DOS.
Page 291: Chapter 32: Pxe Configuration Utility
Chapter 32 PXE Configuration Utility Altiris® PXE Configuration Utility integrates with Altiris® Deployment Solution and lets you manage all PXE Servers across the network. PXE Configuration has been completely rewritten to give you more capability in working with Deployment Server, which provides administrators greater flexibility when performing the following tasks: Creating boot menu options Installing BIS Certificates...
Page 292 PXE Configuration Utility Initial Deployment, but now you can select DOS, Linux, or Microsoft Windows Preinstallation Environment (WinPE) as the pre-boot automation environment. By default, the pre-boot operating system selected during installation is set for Initial Deployment. See DS Tab on page 309.
Page 293: Boot Menu Tab
PXE Configuration Utility To open PXE Configuration Option 1: From the Deployment Console, click the PXE Configuration icon on the toolbar. You can also select Tools > PXE Configuration. Option 2: Select Start > All Programs > Altiris > PXE Services > PXE Configuration Utility.
Page 294 PXE Configuration Utility From the drop-down list, select the automation pre-boot environment such as DOS, WinPE, or Linux. If a PXE boot menu item is used by the job, it appears in the drop-down list. You can perform these steps to check if the other boot menu items are used by the other jobs.
Page 295: New Shared Menu Option
PXE Configuration Utility Prompt: This is the user prompt for the PXE boot menu list when it appears on client computers. You can only change the text message, but not the <F8> command as it is still required to perform a PXE boot option. Append server name: Select this option to have the PXE Server name listed following the prompt on client computers when the boot menu list appears.
Page 296: Edit Shared Menu Option
PXE Configuration Utility User supplied: This option is for advanced users. If you select this option, you must select Other in the Operating System section. The Final Location on PXE Server field shows the path where the new configuration is stored. The folder MenuOption<Number>...
Page 297: Regenerate Boot Images
PXE Configuration Utility Note You must enter a name in the Name field to enable the Import Boot Image button. Insert a floppy disk. The path and name of the new MenuOption<number> appears. Click Next. A progress bar displays the PXE boot file image being read as it is imported.
Page 298: Dos
PXE Configuration Utility Example: If you have installed WinPE, and Altiris supports a newer version that is available, browse and specify the location of the pre-boot files and click Next to install the new files. All existing WinPE files are deleted from the hard disk before the new files are installed.
Page 299: Linux
PXE Configuration Utility Required Optional SMARTDRV.EXE ATTRIB.EXE SYS.COM MODE.COM XCOPY32.MOD FORMAT.COM FDISK.EXE Note The SMARTDRV.EXE file is required for all computers running a scripted install in Windows 2003\XP. Linux Deployment Solution provides Linux RedHat Fedora in a file named BDCgpl.frm. The BDCgpl.frm file can be downloaded from the Deployment Solution download site on altiris.com and saved to any location on the network.
Page 300: Configuration Name
PXE Configuration Utility To start the New Configuration Wizard, click this icon on the toolbar of the Boot Disk Creator tool and click Ctrl+N or click File > New Configuration. Configuration Name This is the first page of the New Configuration Wizard, which is the same for DOS, Linux, or WinPE.
Page 301: Multi-Network Adapter Configurations
PXE Configuration Utility Multi-Network Adapter Configurations If you are creating a DOS configuration, when you select Multi-NIC configurations, a list of supported drivers appears. You can select Multi-NIC drivers to be included in the configuration by pressing Shift-Click or Ctrl-Click. After a client computer boots using a multi-network adapter configuration, Boot Disk Creator applies the driver that matches the first network adapter card that it detects.
Page 302: Have Disk
PXE Configuration Utility If the network adapter you want does not appear in the list, click Have Disk, Internet, or Advanced to add additional drivers. See Have Disk on page 302, Internet page 302, and Advanced on page 302. Field Definitions Auto-detect network adapter: Select this option to let WinPE auto-detect the type of adapter that is in the client computers when the boot image runs.
Page 303: Tcp/Ip Protocol Settings
PXE Configuration Utility Advanced settings (driver command line): Add driver command-line entries to the landrv.bat file. TCP/IP Protocol Settings This page lets you set up TCP/IP protocol settings for boot configurations. TCP/IP is the default protocol when client computers boot to automation on a Windows network. If you are using the IPX protocol, Deployment Server uses its own IP stack to work on IPX networks.
Page 304: Network Connection
PXE Configuration Utility Use TCP/IP multicasting to find the Altiris Deployment Server: Select this option to use TCP/IP multicasting to find the Deployment Server. When client computers boot to automation using this configuration, a multicast packet is broadcast across the network to find where the Deployment Server location is located.
Page 305: Network Drive Mappings And Mount Points
PXE Configuration Utility User name: Enter the authorized user name that was set up while creating the Deployment Share directory. If you did not assign a User name and Password when the Deployment Share or file server was created, leave these fields blank. Password: Enter the password for the user name.
Page 306: Configuration Summary
PXE Configuration Utility Configuration Summary This page lets you review all the options you selected throughout the New Configuration Wizard. If you want to modify a setting, click Back to re-select the option. When you click Finish, the Create Boot Disk Wizard appears for the next process to begin.
Page 307: Create Pxe Boot Image Files (Pxe)
PXE Configuration Utility system. However, any files that you add to the global <OS> additional files folders are written to the boot image before the specific configuration files. If a file in the <OS> additional files folder has the same name as a file in a specific configuration folder, it is overwritten.
Page 308: Pxe Boot Image Creation Complete
PXE Configuration Utility computers, after you select all the properties for a New Configuration, Boot Disk Creator must know the type of image file to create. Field Definitions Automation PXE image: The automation agent for the type of pre-boot operating system configuration that you created is added to the settings you selected throughout the New Configuration Wizard.
Page 309: Ds Tab
PXE Configuration Utility DHCP Server discovery: Auto detect Microsoft DHCP Server and configure for PXE: Select this option for a PXE Server to auto-detect the ports used for DHCP when Deployment Server and the PXE Server are installed to the same server. 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.
Page 310: Mac Filter Tab
PXE Configuration Utility Engine port: This option defines which port the PXE Servers use to communicate with the Deployment Server Engine, which manages the Deployment Database, sends job commands to the Deployment Agent, and more. Data Manager port: This is the port that PXE Manager uses to communicate with the Deployment Server.
Page 311: Define Mac Addresses
PXE Configuration Utility Customize PXE Server: Shared Configuration: This option is available when you select a specific server from the File menu. You can also customize the properties for the PXE Server you selected. Use MAC Address Filtering: Select this option to use MAC filtering. If you do not select this check box, the entries in the MAC Address Patterns section are ignored.
Page 312 PXE Configuration Utility The PXE Manager multicast properties section lets you set a Beginning Multicast Address, the Number of Multicast Addresses Available, and the Maximum Addresses Available to Single PXE Server. A multicast address is automatically assigned to the files a PXE Server uses to download the boot menu options to client computers.
Page 313: Data Logs Tab
PXE Configuration Utility computers on the same subnet, you can select this option to communicate. If you disable MTFTP, TFTP is used to communicate. PXE-enabled client computers listen for broadcast messages sent by the PXE Server through MTFTP. If a PXE Server is going to service client computers across subnets and this option is enabled, the PXE Server tries to communicate with clients using MTFTP.
Page 314: Status Tab
PXE Configuration Utility Log Files: The following log files are specific to PXE Servers and, if enabled, log the information to the filename you specify and store it in the PXE folder on each PXE Server across the network. PXE Server Log PXE MTFTP Log Packet Parser Log DS Traffic Log...
Page 315 PXE Configuration Utility Enter the Remote computer name or browse the network to select a remote PXE Server. Enter the PXE Server IP address. 10. Enter the PXE Server install path and click Next. 11. On the Gathering Information page, enter a User name and Password with administrative rights on the remote computer.
Page 316: Chapter 33: Altiris® Imageexplorer
Chapter 33 Altiris® ImageExplorer Altiris® ImageExplorer provides features that let you view and edit image files. Image files are created using the RapiDeploy utility, a tool used most commonly in Deployment Solution to create and distribute hard disk image files. These are .IMG or .EXE files containing a replication of the source computer’s hard disk.
Page 317 Altiris® ImageExplorer ImageExplorer provides the following features to view, manage, and modify the volume, folder, and file elements of an image file. Feature Description Button Access Add Files Adds a new file to the image file. See Option 1: Ctrl+A Add New Files on page 322.
Page 318 Altiris® ImageExplorer Feature Description Button Access Extract Extracts a complete volume, folder Option 1: Ctrl+E (with its sub-folders), or file from the Option 2: Select image file. You can select a Edit > Extract destination volume or directory to save the folders or files. See Extract Option 3: Right- a Folder...
Page 319 Altiris® ImageExplorer Feature Description Button Access Open File Lets you open a file with a selected Option 1: Ctrl+W with program. If the file is already Option 2: Double- associated with a program, you can click the file (if simply double-click to open. Use not associated) Open file with to change the program or select the default Quick...
Page 320: Using Imageexplorer
Altiris® ImageExplorer Feature Description Button Access Properties Provides general information about Option 1: the folder or file, such as size, Alt+Enter modification dates, and attributes. Option 2: Select Properties appear differently for File > images, volumes, folders, or files. Properties View Properties on page 320.
Page 321: General Properties For An Image File
Altiris® ImageExplorer Alt+Enter. Depending on the type of image element, a properties page opens with the appropriate tabs. General Properties for an Image File This page displays the data for image files. After selecting Properties for a selected image, click the General tab to view the image items and additional property data, such as size, location, and attributes.
Page 322: Open Split Image Files
Altiris® ImageExplorer default program for the Quick Open feature by clicking View > Settings and editing the Open with program box. See also: Print a File on page 328 and Settings on page 329. Open Split Image Files If an image is too large or you are trying to meet size restrictions to store an image (such as dividing image files to 600 MB segments to fit on multiple CDs), you can use the features in RapiDeploy to split the image file into multiple files.
Page 323: Create An Image Index
Altiris® ImageExplorer releases of Deployment Server, when you convert an image file, it will always be to the most current file format. When converting image files, be aware of the following: If an old image has an image index (.IMX) file, a new image index file is created. If an old image file is a self-extracting image, the embedded RapiDeploy code is removed and the image is restored to an .IMG file.
Page 324: Extract A Folder
Altiris® ImageExplorer This feature creates a new index file named .IMX. As you copy the segments to CDs, you can select .IMX and .IMG to be on the same CD. You can copy the other segments, .002, .003, and .004, to additional CDs as needed. When you use the CDs to restore an image, the first CD that contains the .IMG and .IMX files provides RapiDeploy the information needed to restore the image.
Page 325: Filter Results
Altiris® ImageExplorer You can select one of the following options to change the search domains and click Find. Search all open images: Select this to search for a file or folder in the open images. Search entire image: Select this to search for a file or folder in the entire image. Search only in: Select this to search for a file or folder only in the selected file, volume, or folder.
Page 326 Altiris® ImageExplorer to a computer that does not have access to the Deployment Server and RapiDeploy for imaging through the network. You can select image files created using RapiDeploy, which was used to create images beginning with Deployment Server 5.6 or later. You cannot use this feature if you have images created using Altiris IBMaster 4.5 or earlier.
Page 327: Not Enough Free Space
Altiris® ImageExplorer Processor architecture: These options are available only when you select the corresponding self-extractor type. UI mode: You can select GUI mode or Text mode. To create a self-extracting image file Click File, and select Make Self-Extracting Image. Enter or browse to the location of the image file. Clear Keep original image file if you want to make the original image file a self- extracting image file.
Page 328: Print Preview
Altiris® ImageExplorer Print < . > and < .. > entries: Select this option to print an entry in each folder identified as < . > (a dot notation) and < .. >. Attributes and date/time properties will be saved for this hidden folder in the image file. Print Excluded items: Select this option to print the files previously marked as Excluded.
Page 329: Settings
Altiris® ImageExplorer Field Definitions Current password: Enter the current password. New password: Enter the new password. Confirm password: Enter the new password again to confirm. Settings Click View > Settings to set the preferences for ImageExplorer. The Settings dialog appears, from which you can set options to confirm specific operations using message boxes in the user interface, for displaying items or excluding items, or for selecting default programs when using the Quick print or Quick open options.
Page 330: Split An Image
Altiris® ImageExplorer previously marked as Excluded to be saved to an external destination folder when running the Extract command. Color Excluded items: Select this option to mark with red text the files and folders excluded from the image. See Exclude on page 317.
Page 331: Command-Line Switches
Altiris® ImageExplorer Current segment size: By default, the segment size for RapiDeploy images is 2 GB. Current segment count: By default, the number of segments in the image file is displayed. New Output Image File: This option lets you enter or browse to a folder and filename for the image file you want to split.
Page 332 Altiris® ImageExplorer Command Description line Switches -register: Register file types in the Windows Registry. -unregister: Unregister file types in the Windows Registry. -add <src*> <dst>: Add a file or folder to an image. Accepts the <-overwrite> option. You can use wildcards when entering the source (src).
Page 333 Altiris® ImageExplorer C:\Program Files\Altiris\eXpress\Deployment Server\imgexpl f:\w2k.img -password develop Open two image files that have different passwords, ‘develop’ and ‘sales’. C:\Program Files\Altiris\eXpress\Deployment Server\imgexpl f:\w2k.img -password develop f:\xp.img -password sales Add all *.txt files in e:\to the ‘temp’ folder of the volume in slot 1 of w2k.img. C:\Program Files\Altiris\eXpress\Deployment Server\imgexpl f:\w2k.img -password develop -add e:\*.txt 1:\temp Extract kernel.dll from the ‘Windows’...
Page 334: Chapter 34: Installing Deployment Server
Installing Deployment Solution agents on page 350. Note You can also install the Deployment Server components remotely from the Symantec Management Console. Enabling SQL Server 2008 SQL Server 2008 turns off the network TCP and pipe protocols. Before you install Deployment Server, you need to enable the network TCP protocol.
Page 335: Enabling Sql Server 2008
Deployment Server controls the flow of the work and information between the managed computers and the other Deployment Server components (Deployment Console, Deployment Database, and the Deployment Share). Managed computers connect and communicate with the Deployment Server to register inventory and configuration Altiris Deployment Solution™ from Symantec User’s Guide...
Page 336: Deployment Server
This feature is supported in the silent install .INI file and the GUI install executable. The database maintains the following information about the managed computers: Hardware. RAM, asset tag, and serial numbers General Information. Computer name and MAC address Altiris Deployment Solution™ from Symantec User’s Guide...
Page 337: Deployment Database
Deployment Server. You must create this share before you begin installing. If you are not installing on a remote computer, you can select the option to create the share during the installation. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 338: Deployment Share
We recommend that you use DHCP to manage the TCP/IP address in your network, whether you use PXE or not. This greatly reduces the amount of time required to set up and manage your computers. Deployment Server components on page 335. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 339: Deployment Web Console
Hardware Software All components require Pentium III processors Deployment RAM: 256 MB Windows Server Server Disk Space: 200 MB Deployment RAM: 128 MB Windows XP Professional Console Windows Server Disk Space: 3.5 MB Altiris Deployment Solution™ from Symantec User’s Guide...
Page 340: Deployment Server System Requirements
Deployment Server components on page 335. You can install the Deployment Server with a Microsoft Desktop Engine (MSDE) by using the Simple Install. You can install the Deployment Web Console during a Simple Install Altiris Deployment Solution™ from Symantec User’s Guide...
Page 341: Simple Install For Deployment Server
The Deployment Share lets you store files on the computer and run Deployment Server system applications. See Deployment share page 337. Select one of the following options to configure the licensing information: Altiris Deployment Solution™ from Symantec User’s Guide...
Page 342 Remotely install Deployment Agent. Select this option if you want to push the Deployment Agent to computers running Windows operating systems. Install add-ons to provision server hardware. Select this option to install the add-ons for Dell computers. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 343 Click Extract and Execute App to extract and execute the application immediately. The default installation directory is C:\DSSetup. If the file C:\DSSetup\AppLic.dll already exists, a prompt appears, asking whether you want to overwrite this file. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 344: Custom Install For Deployment Server
Deployment Server on the local computer or on a remote computer. The IP address and the port information for the selected computer are displayed by default. Enter the path where you want to install the Deployment Server. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 345 13. Specify how you want to connect your managed computer to the Deployment Server by selecting one of the following options. Select the Connect directly to Deployment Server option and enter the Deployment Server IP address and port. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 346 You have successfully completed a Custom Install for a Deployment Server system. Click the Deployment Console icon on your desktop to view all the computer resources running Deployment Agents configured for your Deployment Server. Simple install for Deployment Server on page 340. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 347: Thin Client Install
If a previous installation of the Deployment Database is detected, an axinstall prompt appears, asking whether you want to preserve or overwrite the existing database. Click Yes to preserve the data in your Deployment Database. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 348 The component install option lets you add selected Deployment Server Components — Deployment Console, Deployment Web Console, PXE Server, and Deployment Agents to the existing Deployment Share. You can also add Microsoft Sysprep files. Deployment Server components on page 335. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 349: Component Install
IP addresses to other PXE Servers in the system. For all the available options for installing PXE Server, see PXE server install page 367. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 350 You can also install this agent on any supported Linux workstation or server. See Installing the Deployment Agent on page 352. Deployment Agent on Linux. Install on any supported Linux workstation or server. See Installing Deployment Agent on Linux on page 356. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 351: Installing Deployment Solution Agents
Searches the file for a line starting with a carat (^). This line must have at least two values listed, separated by a comma. The two values needed are the description of the card (value1) and the .com driver file name (value2). Altiris Deployment Solution™ from Symantec User’s Guide...
Page 352: Client Connectivity And Network Adapters
Specify install directory Enter a location to install the Deployment Agent. Install directory. Enter the path to install the Deployment Agent on the client computer. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 353: Installing The Deployment Agent
This also includes the individual network shares that may exist on this client. On selecting this option, SID conversion takes a long time. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 354: Specify Install Directory
After the Deployment Agent is installed, it connects to the Deployment Server and appears in the Computers pane of the Deployment Console. Installing Deployment Solution agents on page 350. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 355: Download Microsoft Sysprep
-remove Permanently removes the Deployment Agent from the computer where it is installed. -silent Lets you use the options without being prompted for further input. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 356: Automating The Installation Of Deployment Agent
To run the script to change the settings for the configuration file, adlagent browse to the directory from /opt/altiris/deployment/adlagent/bin the shell and enter ./configure Altiris Deployment Solution™ from Symantec User’s Guide...
Page 357: Installing Deployment Agent On Linux
The Deployment Server system also provides the license utility to install or update regular licenses, or to add licenses to computers installed with Deployment Solution. This utility shows the license status, installs a new license, and adds additional licenses. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 358: Installing The Automation Agent
Select Altiris Program Files to Activate page, you can select the Replace all existing license Activation Keys with this new Activation Key check box, which overwrites the current Activation Key with the one you are installing. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 359: Using The License Utility
A list displays the Altiris products that are installed on the Deployment Server. Each program file uses license activation key files. Select the products that you want to license. Use the Shift key to select multiple products. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 360: Install A Regular License For Products
Select Apply regular license. Click OK. To install a regular license on multiple computers From the Deployment Console, right-click the computer group to which you want to apply the license. Select Advanced. Select Apply Regular License. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 361: Install Multiple Licenses
To verify that the license has expired, use the following options: When you select a computer with an expired license, the following message appears: Client license expired - see computer properties. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 362: Rapid Deployment Pack Licensing
This is a long term and preventative solution to expired license issues. In the Deployment Console, go to Tools > Options. Click the Global tab. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 363: Expired Licenses
Custom install. Select this option to install Deployment Server components on multiple computers across your system. A Custom Install lets you balance network activity for large enterprises with multiple subnets. Example: Use this option to distribute the Altiris Deployment Solution™ from Symantec User’s Guide...
Page 364: Installation Help
Deployment Server directory on the file server before you start the installation. For Windows XP, you must run the Network Setup Wizard accessed from My Network Places to enable sharing. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 365: Installing Deployment Server
Server computer. For domain accounts, include the domain name (Example: orgDomain\admin). The user account must have rights to the Deployment Share. Create the administrator domain account before starting the installation. See Deployment share on page 337. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 366: Deployment Server Install
Linux. Browse to the BDCgpl.frm file. This is available on the Deployment Solution download site. WinPE. Browse to the WinPE files. See Boot Disk Creator Help and PXE Configuration Help. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 367: Pre-Boot Operating System (Simple)
Select the Yes, I want to install PXE Server on this computer option to install the PXE Server on the local computer. Note This option is selected by default for the Component Install. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 368: Deployment Database Install
If you do not want to install the Deployment Web Console, select the Do not install option. If you want to change the default values, enter the Console port and Deployment Web Console path for the installation. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 369: Client Connection To Server
The components in the list are installed. Download Adobe Acrobat. Select this option to download the Adobe Acrobat Reader to read the documentation in the .PDF format. Click Finish. Deployment Server components on page 335. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 370: Sysprep
335 and Installing Deployment Server page 334. Installer return codes For a list of return codes for the installation program, see the Error Messages in Deployment Solution chapter in the Reference Guide. Altiris Deployment Solution™ from Symantec User’s Guide...
Page 371: Deployment Database Authentication
Altiris Deployment Solution™ from Symantec User’s Guide...
Page 372: Part Vii: Technical Reference
Part VII Technical Reference This section technical information for command-line switches, return code values and other detailed information for Deployment Solution components. Deployment Solution...
Page 373: Appendix A Command-Line Switches
Appendix A Command-Line Switches This section provides detailed information about command-line switches for specific executables within Deployment Solution. Job Utilities The Job Utility applications allow you to import, export, create and schedule jobs from the command line. Each action is performed from separate binaries installed in the Deployment Share file directory.
Page 374: Job Import Utility
Command-Line Switches Options /f <folder-name> Job folder to be exported /e <job-name> Job to be exported Process all subfolders also Include the Initial Deployment Job Suppress confirmation prompts /dsn <odbc-dsn-name> ODBC data source name /d <db-server> Database server name /u <db-user> Database user name /db <db-databaseName>...
Page 375: Create Job Utility
Command-Line Switches /d <db-server> Database server name /u <db-user> Database user name /db <db-databaseName> Database name /p <db-password> Database user password /lu <login-user> Deployment Server login user name /lp <login-password> Deployment Server login password Note When new jobs are created in a console, by default, Deployment Server will notify all other consoles that changes have been made so they can refresh and show the newly imported jobs.
Page 376 Command-Line Switches Tasks /tci <filename> Create disk image /tdi <filename> Distribute disk image /tds <filename> Distribute software /tbr <path> Backup registry files /trr <path> Restore registry files /trs <path> Run Script /tcf <source> <dest> Copy file /tgi Get Inventory /tre Restart /tsd Shutdown...
Page 377: Schedule Job Utility
Command-Line Switches axEvent CreateOscar /tci .\Images\oscar.img axSched oscar CreateOscar /t "2009-12-31 08:00" Example 2: Shutdown Oscar's computer right now. axEvent Shutdown /tsd axSched oscar Shutdown /t "2009-12-31 08:00" Example 3: Run a Windows program on all computers right now. (Calc.exe is the only line in script.txt.) axEvent /w /i RunCalc /trs script.txt axSched oscar RunCalc /t "2009-12-31 08:00"...
Page 378: Import Computer Utility
Command-Line Switches If the /t switch is not used, the job is assigned to the computer but not scheduled. As a result, it will not execute. If you would like the job to run immediately, choose a date in the past. If you have a group or computer name which include spaces, put the name in quotes.
Page 379: Deployment Agent For Windows
Command-Line Switches for this service are set in the registry setting rather than in the Start Parameters property of the service. If you want to add start parameters after the install, you can modify the registry settings. The registry key is LOCAL_MACHINE\SYSTEM\ControlSetXXX\Services\Altiris Express Server.
Page 380: Aclient.inp Parameters
Command-Line Switches Aclient.inp Parameters You can use this input file to set installation parameters for , so you can aclient.exe install the client program from a script file. The file is copied to the Deployment Server program directory when you install the product. Command-line parameters are included in the file, but are marked with a REM statement.
Page 381 Command-Line Switches Parameters Details LogSize Function: Sets the maximum log file size (in bytes). Example: To set the log file size limit to 4096 bytes, type LogSize=4096 MCastAddr Function: Specifies the multicast group address to be used to find the Deployment Server. Example: To set the IP address for multicasting, type MCastAddr=225.1.2.3 MCastPort...
Page 382 Command-Line Switches Parameters Details PromptSeconds Function: Specifies the length of time (in seconds) that the client will wait for a response from the user. Example: To wait 30 seconds for user input, type PromptSeconds=30 ShowTrayIcon Function: Specifies whether or not to show the Altiris client icon in the system tray.
Page 383: Adlagent.config Parameters
Command-Line Switches Parameters Details UseRCDrivers Function: Specifies whether or not to install keyboard and mouse filter drivers that enable remote control on Windows client computers. (The default is “ ,” so the drivers are not installed.) Example: To install the drivers for remote control, type UseRCDrivers=Yes UserName Function: Associates a computer with the primary user or users.
Page 384 Command-Line Switches Parameters Details DebugTrace Specifies whether or not to log any messages. Changes to the DebugTrace field may not be recognized until the ADLAgent is stopped and restarted. Example: DebugTrace=True. LogErrors Specifies the types of messages to be written in the log file.
Page 385 Command-Line Switches Parameters Details GetApps Specifies whether or not to get the Applications at a “Get Inventory” request. Example: GetApps=True. GetServices Specifies whether or not to get the Services at a “Get Inventory” request. Example: GetServices=True. GetDevices Specifies whether or not to get the Devices at a “Get Inventory”...
Page 386 Command-Line Switches Parameters Details TcpPort This is the IP port number of the Deployment Server listening for requests (Optional). Specifying this parameter will switch the ADL Agent to use TCP to connect to the Deployment Server. Example: TcpPort=402 WakeOnLANProxy Specifies whether to proxy Wake on LAN packets. Example: WakeOnLANProxy=True.
Page 387: Aclient.config Parameters
Command-Line Switches Parameters Details MAKE_LOWER_CASE Changes the file path and file name to lower case when copying a file from the Deployment Server. Example: MAKE_LOWER_CASE=True. FORCE_NEW This is for the agent in automation mode only. It forces the agent to run the Initial Deployment event, even if it is already in the database.
Page 388 Command-Line Switches Parameters Details SIDgenCount Specifies the number of times SIDGen has run. Example: SIDGenCount=0. Note: This value is set by the AClient and the user need not set it. TaskSequence Specifies the task sequence of the task executed by the AClient.
Page 389 Command-Line Switches Parameters Details DSOrganizationalUnit Specifies the organizational unit for Deployment Solution. Example: DSOrganizationalUnit=myou. ChangeSID Specifies whether to change the SID value. Example: ChangeSID=True. Computer Name Specifies the name of the computer. Example: ComputerName=Altiris. DNSDomain Specifies the DNS domain, which is the name of the Workgroup or Domain that this computer is a member Example: DNSDomain=cybage.com.
Page 390 Command-Line Switches Parameters Details VendorID Specifies the Vendor ID for the NIC. Example: Vendor ID=32902. DeviceID Specifies the device ID for the NIC. Example: Device ID=4153. PCIFunction Specifies the PCI Function for the NIC. Example: PCI Function=0. PCIDevice Specifies the PCI Device for the NIC. Example: PCI device=8.
Page 391 Command-Line Switches Parameters Details Gateway Specifies the Gateway information for TCP/IP. Example: Gateway=172.17.31.2. Netmask Specifies the Netmask value for TCP/IP. Example: Netmask=255.255.255.0. Address Specifies the address for TCP/IP. Example: Address=172.17.31.98. DHCP Specifies the DHCP value for TCP/IP. Example: DHCP=True. SetIPInfo Specifies whether to set the IP information for TCP/IP.
Page 392 Command-Line Switches Parameters Details MACAddress Specifies the MACAddress for NICEntry. Example: MACAddress=00-FF-3C-03-85-C0. Description Specifies the description of the computer for NICEntry. Example: Description=AMD PCNET Family PCI Ethernet Adapter. VendorID Specifies the Vendor ID for NICEntry. Example: Vendor ID=4332. DeviceID Specifies the Device ID for NICEntry. Example: Device ID=33081.
Page 393 Command-Line Switches Parameters Details DNS-Host Specifies the DNS host for NICEntry. Example: DNS-Host=TESTWXP2. DNS-Domain Specifies the DNS domain for NICEntry. Example: DNS-Domain=mydomain.com. DNS-Enabled Specifies whether the DNS is enabled for NICEntry. Example: DNS-Enabled=True. SetDNSInfo Specifies the DNS information for NICEntry. Example: SetDNSInfo=True.
Page 394 Command-Line Switches Parameters Details EncryptedClientID Specifies the encrypted client ID. Example: EncryptedClientID=0 Password Specifies the password. Example: Password=Altiris AllowMod Specifies whether or not to enable or disable security for admin properties. If the value is 0, the security is disabled. if the value is 1, the security is enabled. Example: AllowMod=1 Transport TransportUse...
Page 395 Command-Line Switches Parameters Details PromptReboot Prompt before executing shutdown and restart commands. Example: PromptReboot=Yes. PromptExecute Prompt before executing program execution and file copy commands. Example: PromptExecute=Yes. PromptRemoteControl Prompt before executing remote control commands. Example: PromptRemoteControl=Yes. PromptSeconds Specifies how long the user prompt should appear in seconds.
Page 396 Command-Line Switches Parameters Details SpeedLimit Specifies the minimum speed limit in Kbps to transfer files. If the rate is slower than the rate specified here, do not transfer files. SetSpeedLimit must be enabled for this setting to work. Example: SpeedLimit=10000. Blockout ScheduledBlockStart Specifies the beginning of the period when the client...
Page 397 Command-Line Switches Parameters Details BlockedDaySat Specifies whether to block the client from connecting to the Deployment Server between the times specified in ScheduledBlockStart and ScheduledBlockEnd on Saturdays. Example: BlockedDaysSat=True. Proxy WakeOnLANProxy Forward Wake On LAN packets sent from the Deployment Server. Example: WakeOnLANProxy=Yes.
Page 398: Deployment Agent For Dos Command-Line Switches
Command-Line Switches Parameters Details ForceReboot Specifies whether to force applications to close when shutting down. Example: ForceReboot=Yes. BootDrive Specifies the Windows boot drive. Example: BootDrive=D:\. SyncTimeWithServer Specifies whether to synchronize the client system’s date and time with the Deployment Server. Example: SyncTimeWithServer=Yes.
Page 399: Bootwork.exe
Command-Line Switches Bootwork.exe You can use either a forward slash (/) or a dash (-) with the command-line options. Commands are not case sensitive. Switch Details -dsbios Function: Disables reading of the BIOS for system information. This is typically used for troubleshooting, if a client computer crashes when it first starts running BootWorks.
Page 400 Command-Line Switches Switch Details -mip<IPaddress> Function: Specifies the multicast IP address of the Deployment Server. The default value is 225.1.2.3. If the address is changed on the Server, use this parameter to change the address in BootWorks so the client looks for the correct address. The port number must also be specified if you change this parameter.
Page 401: Deployment Agent For Dos Install (Bwinst.exe) Switches
Command-Line Switches Switch Details -pause Function: Causes the computer to pause for 5 seconds before beginning production boot processes. This allows time to access the bootworks program before the computer boots to production. Example: To add a 5-second pause before a production boot, type bootwork -pause -s<name>...
Page 402 Command-Line Switches Switch Details -s[x] Function: Works with the -old switch to set the partition size (in MB) for hidden BootWorks partitions. The minimum size is 5 MB, which is the default. Note If you install embedded BootWorks (new style for 4.x versions), this switch does not apply.
Page 403: Keyboard And Screen Lock Utility (Kbdsclk) Switches
Command-Line Switches Switch Details Function: Specifies the source path to the BootWorks files. The default is drive a:. Example: To install BootWorks from a directory named “bootfile” on a network drive, type bwinst -f=f:\bootfile Function: Reads the BIOS settings for the hard drive if IDE settings fail or return incorrect values.
Page 404 Command-Line Switches The Altiris client graphic appears. The keyboard and screen are not locked. If options are added to the batch file, they are executed in the order they appear in the file. Option Description p=pwd [b] Function: Sets a password to enable/disable the keyboard and screen lock.
Page 405: Deployment Server Install Switches
Command-Line Switches Use w to specify the name of a wallpaper/graphic file to replace the default. See the table above for details on using graphics files. When x is used, the wallpaper/graphic appears and the KBDSCLK program exits, ignoring all other commands except w and h, regardless of order. KBDSCLK does not remain loaded as a TSR, so the keyboard is not locked.
Page 406: Silent Install Options
Command-Line Switches Switch Details -i - Function: Allows you to create a setup.ini file used for automation or a silent install Example: axinstall -i -t <INI file Function: Allows you to run a silent install (where the install application location> executes without asking for user input) and read setting from an INI file.
Page 407: Simple Install Entries
Command-Line Switches WCRemoteComputerName WCUsername WCPassword WCEncryptedPassword WCConsoleManagerport The Version and InstallType entries are both required in the new SILENT.INI file. If the Version entry is missing, it is assumed that it is an old SILENT.INI file (implicitly assumed to be version 1). If the InstallType entry is missing for a new version of SILENT.INI, an error will be logged to the log file and the installation will be aborted.
Page 408 Command-Line Switches To install FreeDos files, specify the following fields PBFreeDOS=FALSE | TRUE PBFreeDOSFile=c:\DSSetup\BDCgpl_6.8.8271.frm If you install DOS files, the following fields are listed: PBMSDOS=FALSE | TRUE PBMSDOSPath=c:\DOSFiles To install Linux files, specify the following fields For Linux IA64, specify the path of the .FRM file in .
Page 409: Custom Install Entries
Command-Line Switches For WinPE x64, to use an add-on file, specify the path of the add-on file in . The field should be PBWindowsPEX64AddOnPath PBWindowsPEX64AddOn True Example PBWindowsPEX64AddOn=TRUE PBWindowsPEX64AddOnPath=c:\DSSetup\AddonX64.exe To specify the WinPE disk path, specify the path in PBWindowsPEWinPEX64Path the operating system path in .
Page 410 Command-Line Switches DAEncryptedPassword=z%l$qry^w CreateExpressShare=FALSE | TRUE DOSFilesPath=c:\dos SEPath= C:\Program Files\Altiris\eXpress\Deployment Server SELocation=local | remote SERemoteComputerName=DESKPRO1 SEUsername=administrator SEPassword=password SEEncryptedPassword= z%l$qry^w SEIPAddress=172.16.2.123 SEDataManagerPort= 8080 SEDBLocation=local | same | remote | sqlserver SEDBRemoteComputerName=DESKPRO2 SEDBSQLPortNumber=<Enter SQL Port Number here> SEDBEnginePath=c:\mssql7 SEDBDataPath=c:\mssql7\data SQLAuthentication=FALSE | TRUE SQLMachineUsername=administrator SQLMachinePassword=password SQLEncryptedMachinePassword= z%l$qry^w...
Page 411: Add Component Entries
Command-Line Switches PXCreateDefaultPXEBootFiles=FALSE | TRUE SQLAuthentication=FALSE | TRUE SQLUsername=Administrator SQLPassword=password SQLEncryptedPassword=zlq%r*x+y DSConnectionMethod=multicast | tcpip DSConnectionServerName=* | <server name> DSConnectionDSIPAddress=172.16.2.123 DSConnectionDSPort=402 COLocation=local | remote CORemoteComputerName=DESKPRO4 COUsername=Administrator COPassword=password COEncryptedPassword=zlq%r*x+y WCLocation=local | remote | none WCPath= c:\Program Files\Altiris\express\Deployment Server WCRemoteComputerName=DESKPRO5 WCUsername=Administrator WCPassword=password WCEncryptedPassword= zlq%r*x+y WCConsoleManagerPort=8081 Add Component Entries If the InstallType is set to addcomponent, the following entries will be expected in the...
Page 412: Client Bios Settings For Wake-On Lan And Pxe
Command-Line Switches SEDataManagerPort=8080 COLocation=local | remote CORemoteComputerName=DESKPRO4 COUserName=Administrator COPassword=password COEncryptedPassword=zlq%r*x+y PXLocation=dos | local | remote PXRemoteComputerName=DESKPRO3 PXMakeMasterServer=FALSE | TRUE PXIPAddress=172.16.2.123 PXDSIPAddress=172.16.2.123 PXPath=c:\Program Files\Altiris\express\Deployment Server PXCreateDefaultPXEBootFiles=FALSE | TRUE PXUsername=Administrator PXPassword=password PXEncryptedPassword= zlq%r*x+y WCLocation=local | remote | none WCPath= c:\Program Files\Altiris\express\Deployment Server WCRemoteComputerName=DESKPRO5 WCUsername=Administrator WCPassword=password...
Page 413: Command-Line Switches For The Pocket Pc Agent
Command-Line Switches Wake On LAN ON/ENABLED Remote Power Up ON/ENABLED Power Switch/Wake-up ON/ENABLED Command-line Switches for the Pocket PC Agent You can manage the Pocket PC Agent through command-line switches. The default path of the agent executable file is: C:\Altiris\PPCAgent\PPCAgent.exe The following table shows the optional switches and the functions they perform.
Page 414: Command-Line Install Switches For Winpe
Command-Line Switches Switch Details -install -os LINUX -ia64 Installs the Linux agent for ia64 “e:\BDCgpl_6.8.8260.frm” computers. -install -os LINUX -x86 Silently installs the Linux agent for x86 “e:\BDCgpl_6.8.8260.frm” -quiet computers. -install -os LINUX -x64 Silently installs the Linux agent for x64 “e:\BDCgpl_6.8.8260.frm”...
Page 415 Command-Line Switches Switch Details -install -os WINPE -x64 Silently installs the WinPE agent for x64 “e:\Altiris_DS_Preboot_WinPE2005_x64. computers. exe” -quiet -install -os WINPE -ia64 Silently installs the WinPE agent for ia64 “e:\Altiris_DS_Preboot_WinPE2005_ia64 computers. .exe” -quiet Example: To install the WinPE agent for x86 computers, run C:\Program Files\Altiris\eXpress\Deployment Server\Bootwiz\bootwiz.exe –install -os WINPE -x86 "e:\Altiris_DS_Preboot_WinPE2005_x86.exe"...
Page 416: Appendix B: Rapideploy Technical Reference
Appendix B RapiDeploy Technical Reference In Deployment Solution, most imaging tasks can be completed directly from task wizard in the Deployment Console. For advanced imaging operations, you might need the extended functionality provided by the command-line interface of the Deployment Solution imaging tool, RapiDeploy. This section provides details on using the RapiDeploy command-line interface.
Page 417: Rapideploy Command-Line Switches
RapiDeploy Technical Reference Switches can be entered in any order and they are not case sensitive. When using multiple switches, leave a space between each option. You can also get a list of switches at the DOS prompt by typing the following: rdeploy -? If you want to redirect this list to a file, type the following: rdeploy -? -text >...
Page 418 RapiDeploy Technical Reference RapiDeploy Command-line Switches (Continued) Switch [parameters] Details -cfgfile:[filename] Function Sets the configuration filename (default is lastrun.cfg). The configuration file provides information for post configuration. The default configuration file is lastrun.cfg that can be edited in a text editor with the specific information needed for the computer.
Page 419 RapiDeploy Technical Reference RapiDeploy Command-line Switches (Continued) Switch [parameters] Details -d[hard disk number] Function Specifies which hard disk to read from or write to, depending on whether you are uploading or downloading. This switch is used for computers that have more than one hard disk. Examples To download an image to disk 2, combine with the switch...
Page 420 RapiDeploy Technical Reference RapiDeploy Command-line Switches (Continued) Switch [parameters] Details -f[path & file name] Function Used with the switch. In upload mode, it specifies the filename and location for storing an image file. In download mode it specifies which image file to restore. To create (upload) a regular image file, use an .img extension.
Page 421 RapiDeploy Technical Reference RapiDeploy Command-line Switches (Continued) Switch [parameters] Details -forceoem Function Forces the OEM partition to be restored. Use this switch to overwrite an OEM partition on the hard disk with an OEM partition in the image. Example To restore an image and have the OEM partition in the image replace an existing OEM partition on the hard disk, type [filename] rdeploy -md -f...
Page 422 RapiDeploy Technical Reference RapiDeploy Command-line Switches (Continued) Switch [parameters] Details -i[IDnumber] Function Sets session ID when sending an image file to more than one computer. Use this switch with multicast sessions so the Master PC can identify Client PCs in the same session. Example To send an image to 10 Client PCs, type [filename] rdeploy -mdb -f...
Page 423 RapiDeploy Technical Reference RapiDeploy Command-line Switches (Continued) Switch [parameters] Details -m[mode] Function Sets the operating mode. Modes u (Upload image) d (Download image) dd (Disk-to-disk) b (Multicast only) mm (Multicast master) ub (Upload and multicast image) db (Download and multicast image) client (Client mode) Examples To upload an image, type...
Page 424 RapiDeploy Technical Reference RapiDeploy Command-line Switches (Continued) Switch [parameters] Details -mconv Function Used with the switch to convert an existing image file (.img) to a self-extracting .exe file. (Does not upload or download; just converts the file.) Example To convert a file named WINXP.IMG, type rdeploy -mconv -fwinXP.img See also -f[path &...
Page 425 RapiDeploy Technical Reference RapiDeploy Command-line Switches (Continued) Switch [parameters] Details -p[partition] Function Specifies which partition to process. Parameters n Number (1-31) uploads the partition (each partition must be designated separately) b images the BootWorks partition (works for both hidden and embedded types) oem images the oem partition rs images the recovery partition...
Page 426 RapiDeploy Technical Reference RapiDeploy Command-line Switches (Continued) Switch [parameters] Details -restoresig Function Causes RapiDeploy to restore the unique disk signature in the MBR of the hard disk from which the image was created. Normally, RapiDeploy does not transfer the disk signature to the target computer when deploying an image.
Page 427 RapiDeploy Technical Reference RapiDeploy Command-line Switches (Continued) Switch [parameters] Details -szf Function Use this switch to set fixed sizing for all partitions. By using this switch, RapiDeploy will use the original sizes that existed on the computer from which the image was created. Example If the original size of the partition to be downloaded was 250 MB and you want the destination partition to remain 250 MB, use the -szf switch.
Page 428 RapiDeploy Technical Reference RapiDeploy Command-line Switches (Continued) Switch [parameters] Details -threshold:[n] Function This option applies only to the “Restore and Send” (- mdb) mode. We have found that when using a small number of clients, it is faster to perform individual downloads on each client than it is to multicast to all of them.
Page 429: Using Command-Line Switches With Executable Images
RapiDeploy Technical Reference RapiDeploy Command-line Switches (Continued) Switch [parameters] Details -ve:[31.34] Function Set VESA screen resolution. Example To set screen resolution to VESA mode 31 (640x480x256), type rdeploy -ve:31 -w[n] Function When multicasting, specifies the maximum number of minutes to wait for Client PCs to connect. If all Client PCs connect, it will start right away.
Page 430: How Firm Works
RapiDeploy Technical Reference How FIRM Works FIRM identifies two drive types: DOS drives and FIRM drives. DOS drives are those that DOS recognizes, such as local drives and network drives. FIRM recognizes DOS drives in addition to other local partitions that are present but may not be recognized by DOS. FIRM assigns drive letters to partitions in the order they are defined on the hard disk.
Page 431: Firm Command-Line Switches
RapiDeploy Technical Reference FIRM Command-Line Switches Drive designations Because FIRM and DOS recognize drives differently, they might assign different letters to the same drive. So, for some commands you must specify the drive type in addition to the drive letter. Drive types are: OS (operating system drive), and f (FIRM drive).
Page 432 RapiDeploy Technical Reference FIRM Modes and Switches Mode Options drives Function Gets a list of all partitions/drives. Shows the file system and FIRM drive letters. Also shows the percentage of the drive used by the partition. Usage firm drives Example To see a list of all supported drives, including the embedded BootWorks partition, type firm drives type...
Page 433 RapiDeploy Technical Reference FIRM Modes and Switches (Continued) Mode Options Function Displays file and directory lists. Usage [directory] firm dir Option [directory]=directory letter or path Syntax [drive type][drive letter or token] [path] firm dir Do not include a filename or you will get an error. The drive type is optional.
Page 434 RapiDeploy Technical Reference FIRM Modes and Switches (Continued) Mode Options backupreg Function Backs up registry files. Usage dest file][local path] firm backupreg [ Options -noprofile Backs up default registries without the user profiles. [destination file]=destination filename (must be a DOS filename) [local path]=local path to registry files (source) (Default source path for Win NT is c:\winnt\system32\config.
Page 435 RapiDeploy Technical Reference FIRM Modes and Switches (Continued) Mode Options backuplist Function Backs up a set of files. Usage [destination file] [list file] firm backuplist Options [destination file]=destination filename (must be a DOS filename) [list file]=filename containing a list of files to back up (source) Must be in a DOS text/ascii file format.
Page 436: Appendix C: Tokens: Dynamic Database Access
Appendix C Tokens: Dynamic Database Access These are variable tokens that can be inserted in scripts (see Running a script page 184) or answer files (in Scripted OS install on page 168) to extract information from the Deployment Database. Example: the token named %ASSETTAG% contains the asset tag of a computer. Tokens are most commonly used when creating custom scripts (using the Run Script Task) or answer files when doing unattended operating system installations.
Page 437 Tokens: Dynamic Database Access Token Description %IPNAME% Full DNS name of the computer %JOBNAME% The name of the current job. %JOBUSER% The name of the user logged on to the Deployment console %LDAPDOMAINOU% The LDAP format for AD domains. Example: dc=MyCompany, dc=com, OU=MyParentOU, OU=MyOU %MAILSTOP%...
Page 438: Finding The Right Token Value
Tokens: Dynamic Database Access Token Description %NICyPCIFUNCTIONNUMBER% PCI Function number for NIC y. Example: the PCI Function number for the third NIC would be %NIC3PCIFUNCTIONNUMBER%. %NICyUSEDHCP% If you use DHCP, the valid values are Yes or No. %NICyUSEWINS% If you use WINS, the valid values are Yes or No. %NODEFULL% Complete computer name %NODENAME%...
Page 439: Creating Unique Files Using Tokens
Tokens: Dynamic Database Access Explanation of Script FS2 is the alias name. hardware is the table name Ram_Free is the column name to find the value in. If a job using the above script was assigned to the PC-1 computer (with the computer_id of 500001), the values specified are located in the database and appear on the client’s computer.
Page 440: Template File Rules
Tokens: Dynamic Database Access requires a Sysprep.inf file. This file is used, among other things, to set the NetBIOS computer name for a computer and which Domain the computer will belong to (see the sample Sysprep.inf file in the figure to the right.) If the image being deployed to the computers contained this Sysprep.inf file and no other changes were made, all computers would end up with the same computer name and Domain when the Sysprep.inf files was used to configure the computers being...
Page 441: Custom Tokens
Tokens: Dynamic Database Access When the Job is executed the following happens: The template file (Sysprep.inf) is examined and all tokens are located. The unique token values for each computer are located in the Deployment Server database and are used to create a new file for each computer. The tokens in the new files have now been replaced with their applicable values and the files are saved in the Deployment Server directory path specified in the task.
Page 442 Tokens: Dynamic Database Access To return the names of the computers: %#!computer@computer_name% To return the color column from a custom database and table that has the computer_id column in it: %#DBAlias!table@color% To return the color column from the first record from a custom database and table: %#DBAlias^!table@color% Syntax Two %#Alias*”SQL query statement”%...
Page 443: Appendix D: Error Codes
Appendix D Error Codes This section presents some error messages generated by Deployment Solution. They are divided into the following groups: General Error Messages on page 444 Client Error Messages on page 446 Communication Error Messages on page 447 Memory Error Messages on page 449 Partition Error Messages on page 450...
Page 444: General Error Messages
Error Codes General Error Messages Error Message Description "Error reading . . ." Explanation: An error occurred while reading or writing to the disk. "Error writing . . ." Possible causes: Faulty disk hardware. A write-protected disk. The BIOS in some computers has an antivirus capability which attempts to protect the disk from Master Boot Record (MBR) viruses by write-protecting the first sector or track on the hard disk.
Page 445 Error Codes Error Message Description "This program is not licensed Explanation: Multicasting works only when the license count for multicasting (peer-to- is greater than one. peer imaging)." Action: Upgrade your license to support more nodes. Call your authorized reseller for more information. "Exiting with error code .
Page 446: Client Error Messages
Error Codes Client Error Messages Error Message Description "The master PC ended the Explanation: The Master computer sent a "goodbye" packet transfer before we received before the image-transfer was finished. The download didn't all of the data." finish, so the client disk will be in an indeterminate state. Possible cause: The user aborted the download before it was complete.
Page 447: Communication Error Messages
Error Codes Communication Error Messages Error Message Description "Error opening IP socket." Explanation: An error was returned from a call to the network protocol stack. "Error canceling IP listen packets." Possible causes: "IP SendPacket error, code . The IP protocol stack isn't loaded. .
Page 448 Error Codes Error Message Description "Unable to register multicast Explanation: Indicates a failure in the program’s library cleanup function." routines. Action: Isolate the system from the network and try to reproduce the error. This will determine if the error is on the network or in the Altiris program.
Page 449: Memory Error Messages
Error Codes Error Message Description "Out of range index . . . in Explanation: Internal program error. removeItem. ElementCount is . . Action: Please report the error to Altiris. Write down the ." error code and message and a description of what was "Error removing child subtree."...
Page 450: Partition Error Messages
Error Codes Partition Error Messages Error Message Description "Collision in partition-table . Explanation: More than one partition was defined for a ." given partition table slot. It can mean one of two things: "Collision with . . ." Possible cause: The on-disk partition-tables (including partition tables in extended partitions) are corrupt.
Page 451: Installer Return Codes
Error Codes Error Message Description "This image requires that the Explanation: The image being transferred contains a destination drive have the geometry-dependent partition, and the geometry of the same geometry . . ." source disk does not match the geometry of the target disk. This means the disks are not seen as identical drives by the drive controller.
Page 452 Error Codes Return ErrorID Error Description Code 1004 IDS_ERR_INSTALLING_SE This return code is for the Deployment RVER_REG Server component. Thus error occurs while creating some registry entries required for the server to function correctly. If you choose to continue, you will need to set the options manually from the Altiris eXpress Deployment Server Configuration control panel...
Page 453 Error Codes Return ErrorID Error Description Code 1010 IDS_ERR_COPYING_PACKA This return code is for the Deployment Server component. This error occurs while copying the install package to the remote computer. Please ensure the temp directory on the remote computer contains at least 100MB free space. 1011 IDS_ERR_SETUP_INSTALL This return code is for the Deployment...
Page 454 Error Codes Return ErrorID Error Description Code 1017 IDS_ERR_INSTALLING_SE This return code is for the Deployment RVICE Web Console component. This is an unknown error that occurs while installing the Altiris RemoteInstall service. Ensure that the username and password you have supplied has Administrator rights on the remote computer.
Page 455 Error Codes Return ErrorID Error Description Code 1024 IDS_ERR_STARTING_SERV This return code is common for all the components of Deployment Server. This is an unknown error that occurs while starting the Altiris RemoteInstall service. Ensure that the username and password you have supplied has Administrator rights on the remote computer.
Page 456: Appendix E: System Jobs For Deployment Solution
Appendix E System Jobs for Deployment Solution System jobs are shipped and installed in the Deployment Share ( <DS install ) to assist in various path>\Altiris\eXpress\Deployment Server\Samples deployment tasks. During installation, jobs are automatically imported from the file into Deployment Solution where they can be viewed in the System samples.bin Jobs folder in the Jobs area of the console.
Page 457: Imaging
System Jobs for Deployment Solution Imaging Use these sample jobs for basic imaging tasks: Create Disk Image (page 457) Distribute Disk Image (page 457) Create Disk Image Description Creates a disk image. Additional files required None. What this task does This task will create a disk image using the name of the computer as the image filename.
Page 458: Distribute Rapidinstall Package
System Jobs for Deployment Solution What this task does This task runs the DIR command in Windows from a command prompt. Steps to use Assign the job to a computer or computer group. Distribute RapidInstall Package Description Runs the RapidInstall package. shwnm.exe Additional files required: None.
Page 459: Capture User Microsoft Office Settings
System Jobs for Deployment Solution Edit the job. Assign the username and password for use with Windows XP/2003 based systems. Assign the job to a computer or computer group. Capture User Microsoft Office Settings Description Collects the user’s Microsoft Office setting using PC Transplant Additional files required None.
Page 460: Install Office Xp From Mapped Drive
System Jobs for Deployment Solution Shutdown Computer (page 462) Start SQL Server Service (page 463) Stop SQL Server Service (page 463) Uninstall Office XP (page 463) Wake up Computer (page 463) Install Office XP from Mapped Drive Description Installs Microsoft Office XP. Additional files required Microsoft Office XP setup files located on the network share that will be used in the drive mapping.
Page 461: Sql 2000 Unattended Install
System Jobs for Deployment Solution SQL 2000 Unattended Install Description This script will do an unattended install of SQL Server 2000. Additional files required The files from the SQL Server 2000 disk. What this task does This script will copy all files and directories from the SQL setup to the client computer, then execute an unattended install using the specified silent install script ( sqlins.iss...
Page 462: Copy Wlogevent To Client
System Jobs for Deployment Solution Steps to use Assign the job to a computer or computer group. Install MSI 2.0 Runtime Description Installs the Microsoft Installer runtime files. Additional files required None. What this task does This task uses conditions to determine the operating system of the computer and installs the appropriate MSI 2.0 runtime files.
Page 463: Start Sql Server Service
System Jobs for Deployment Solution Assign the job to a computer or computer group. Stop SQL Server Service Description This script will stop the SQL Server service. Additional files required None. What this task does This script will send the NET STOP MSSQLServer NET STOP command to the computer.
Page 464: Distribute Software
System Jobs for Deployment Solution Steps to use Assign the job to the handheld device appearing in the Computers section of the Deployment Server Console. Install Altiris Pocket PC Agent Description Installs Pocket PC Agent on the host computer (the computer with the handheld cradle) for the handheld device.
Page 465 System Jobs for Deployment Solution reboots the client so that DOS will recognize the newly created DOS partition. It then calls to copy the basic RedHat files that facilitate a RedHat Kickstart install. It RH7SETUP then runs to create a disk image of the now populated DOS partition. RDeploy Steps to use Make a copy of the sample job.
Page 466: W2K Scripted Install (Target Hd)
System Jobs for Deployment Solution RH7 Scripted Install (Network) Description This job deploys the RedHat Linux operating system using the Network scripted install model. The network method copies the RedHat files from an FTP server during operating system installation. See the Deployment Solution User Guide for instructions on setting up an FTP server for this purpose.
Page 467: Create Rh7 Install Disk Image (Network)
System Jobs for Deployment Solution What this task does: This job starts a RedHat Kickstart operating system install on a client using the Target HD install method. It downloads the RH71_HD image (or whatever you have named it) to the selected client. This creates a 2 Gig FAT16 DOS bootable partition with the operating system files to do a Kickstart unattended install.
Page 468: Create Rh7 Install Disk Image (Target Hd)
System Jobs for Deployment Solution RH8 Scripted Install (Network) Description This job deploys the RedHat Linux operating system using the Network scripted install model. The network method copies the RedHat files from an FTP, NFS, or HTTP server during the operating system installation. See the Deployment Solution User Guide for instructions on setting up an FTP server for this purpose.
Page 469: Rh7 Scripted Install (Target Hd)
System Jobs for Deployment Solution Server-side Embedded VBScript (Windows) (page 473) WLogevent CMD Script (Windows) (page 473) WLogevent VB Script (Windows) (page 474) Send Email if Disk Space Low (Linux) Description This script will send an email specifying that the computer had less free space than specified threshold.
Page 470: Create Rh8 Install Disk Image (Network)
System Jobs for Deployment Solution This script will not create the computer account in the domain. If it is not already a member of the domain, this event will fail. Assign the job to a computer or computer group. Move Computer to Specific OU (Windows) Description: This script will take the specified computer and move it to the specified domain OU.
Page 471: Scripts
System Jobs for Deployment Solution WLogevent CMD Script (Windows) Description This script shows how to use the utility to send status back to Wlogevent the console while running a Windows CMD script. Additional files required None. What this task does This job will copy the to the Windows client, WLogevent.exe then sends a status message to the console, then executes a...
Page 472: Send Email If Disk Space Low (Linux)
System Jobs for Deployment Solution Distribute RapidInstall Package Description Runs the RapidInstall package after disabling the Enhanced shwnm.exe Write Filter. Additional files required None. What this task does This job will disable the Enhanced Write Filter, and then install a package that includes a utility that shows the computer name in a window.
Page 473: Move Computer To Specific Ou (Windows)
Appendix F Network Ports This document lists the details of the ports used by Deployment Solution. It also includes the steps to configure the ports that are configurable. Component Service Port Protocol Where is this Is this port port configurable? connected? PXE MTFTP Altiris PXE MTFTP...
Page 474: Wlogevent Vb Script (Windows)
Network Ports Component Service Port Protocol Where is this Is this port port configurable? connected? Deployment Altiris eXpress TCP/UDP Agents, PXE Server Server (multicast) Server, DataManager, PXEManager Deployment 5001 AClient Console (Win32 Console) 5002 AClient Deployment Altiris Network Remote Client Agent on Linux Management Client (ADLAgent)
Page 475: Agent Update
Network Ports the PXE Manager to route, store, and retrieve information about the status, image availability, user input, and so on. To configure the 405, 406, and 407 ports Go to the datastore path. Note: By default, the path is: C:\Program Files\Altiris\eXpress\Deployment Server.
Page 476: Appendix F: Network Ports
Network Ports Click Next. The Gathering Information dialog appears. 10. Select the appropriate option, provide the authentication information and click Next. The Pre-boot Operating System dialog appears. 11. Enter the required information and click Next. The PXE Server Information dialog appears.
Page 477: Pxe Mtftp
Network Ports Click the Transport tab. Enter 402 in the TCP Port field and in the Multicast Port field. Click OK. Option 2: Open the Registry Editor. In the left pane, select HKEY_LOCAL_MACHINE > SOFTWARE > Altiris > Altiris eXpress > Options > TCP Port 402 or Multicast Port 402. Note: This is the port where the server accepts all client connections, such as AClient (Windows Agent), ADLagent (Linux Agent), and DataManager.
Page 478: Deployment Web Console (Web Console)
Network Ports Deployment Agent on Windows runs on Windows computers, including desktops, notebooks, and servers. To configure the 402 port Click the AClient icon on your desktop. The Altiris Client Service dialog appears. Click Properties. The Altiris Client Service Properties dialog appears. By default, the Server Connection tab is selected.
Page 479: Db Management (Middle Man)
Network Ports To configure the Client/server file transfer port From the main menu, open the Deployment Console and click Tools > Options. The Program Options dialog appears. Click the Global tab. Select the Client/server file transfer port check box. Enter the port number in the Client/server file transfer port field. Click OK.
Page 480: Deployment Console (Win32 Console)
Appendix G Deployment Agent Authentication This article describes the AClient and the Deployment Server authentication process. The authentication process is required to safeguard the use of the AClient from connecting to a malicious Deployment Server. Deployment Solution...
Page 481: Deployment Agent On Linux
Deployment Agent Authentication The authentication process starts with the Deployment Solution installer generating a security key and writing it in the server.key file. You can find the security key at the following location: HKEY_LOCAL_MACHINE > SOFTWARE > Altiris > Altiris eXpress > Options > Security >...
Page 482: Rapideploy Ports
Deployment Agent Authentication authentication as well as in reply authentication, because it is altered using random bytes. These alterations ensure the safety of the key from malicious users. Deployment Solution...
Page 483: Appendix G: Deployment Agent Authentication
Appendix H Windows Registry Keys This section contains a description of the Windows Registry Keys used by Deployment Solution. You can access the keys in the Options folder. Open the Registry Editor. Click HKEY_LOCAL_MACHINE > SOFTWARE > Altiris > Altiris eXpress > Options.
Page 484 Windows Registry Keys Registry Name Description Purpose Keys present in Options folder ReadThreadCount Specifies the number of threads Creates the number of read threads. for the read operation. The default is 10, the minimum is 0 and the maximum is 200. ResetInactiveClientConnectionsBatch Number of computers in a batch.
Page 485 Windows Registry Keys Registry Name Description Purpose Keys present in Options folder ThreadLogging Specifies whether to create a log If checked, creates a thread file in thread directory for directory and threading related log threads. files. ThresholdWOL Number of minutes to wait before If a job is scheduled on an inactive retrying to wake up the inactive client, and if UseWOL is 1, the...
Page 486: Appendix H: Windows Registry Keys
Windows Registry Keys Registry Name Description Purpose Keys present in Options folder UpdateInventoryBatchSize Number of computers in a batch. While inventorying computers, engine processes ‘n’ computers at a time. After processing ‘n’ computers, it waits for some time (specified by UpdateInventoryRestTime) before processing the next batch of ‘n’...
Page 487 Windows Registry Keys Registry Name Description Purpose Keys present in Options folder UseUpdateInventory 1 if “Update inventory for active If “Update inventory for active clients,” on the General Tab of the clients” is enabled the engine Altiris Configuration Utility, is periodically inventories the active enabled, otherwise 0.
Page 488 Appendix I Pocket PC Installing Deployment Agent for PocketPC The Deployment Agent for Pocket PC lets you manage and deploy handheld computers running the Pocket PC operating system, including: • HP iPAQ Pocket PC • HP Jornada Pocket PC • Casio Cassiopeia Pocket PC You can manage handhelds through a cradle attached to a host computer, or through direct connection to the network using a LAN or wireless network adapter.
Page 489 Pocket PC The Deployment Agent for Pocket PC (PA) runs on the host computer, which itself is a managed computer running the Deployment Agent (DS). The Deployment Agent for Pocket PC automatically installs the Deployment Client for Pocket PC (PC). You can also install the Deployment Client for Pocket PC directly to the handheld by installing the required CAB files.
Page 490: Key In The Security Folder
Pocket PC When the Pocket PC Client is installed on the handheld, the Deployment Client icon will appear in the system tray of the handheld and the client details screen appears. For ease of use, the Pocket PC Client will first try to connect to a Pocket PC Agent. If it fails, the Note: Pocket PC Client will try to connect directly to the Deployment Server.
Page 491: Appendix I: Pocket Pc
Pocket PC To install Pocket PC Client using CAB files 1 Copy the file to the host computer with ActiveSync (or to a share where you can copy the file from). 2 Connect your device to your desktop computer. 3 In ActiveSync, click .
Page 492 Appendix I Managing Switches To administer roles and configurations for network servers, it is necessary to discover and modify the network switch settings for the connected network servers. Deployment Solution provides the Switch Add-On program to discover and manage Virtual Local Area Networks (VLAN) settings on a LAN switch or to run commands from the command-line.
Page 493 Managing Switches All discovered switch information will be kept in a local database file ). To ease installation and support, this file will be text based and SwitchMngtDb.txt be located in the directory from which the Deployment Solution Switch Add-On applications are executed.
Page 494: Discovering A Device
Managing Switches Port The name of the port (vendor-specific port names will be shown when available) Description The description of the switch port VLAN The VLAN assignment for the switch port Connectivity Any user assigned mapping of clients or servers to the switch port By selecting a device in the tree view pane, the switch port display is updated to show its respective ports.
Page 495: Appendix J: Managing Switches
Managing Switches Setting the VLAN for a Switch Port To set a switch port to a specific VLAN, right-click on a switch port in the switch port view and click Click Set VLAN to view all available VLANs on the switch. Select a VLAN from the list.
Page 496: Lan Switch Support List
Managing Switches GUI Tools The Switch Management Console includes a Tools menu, providing a Ping IP Range command to assist in "pinging" a specified IP range in order to generate traffic to a range of devices that might otherwise be inactive. From this dialog you can specify the starting and ending IP addresses to ping.
Page 497: Adding A Switch Device
Index Symbols bwinst.exe installation switches 401 bwinst.exe see Deployment Agent for virtual 250 bay properties server deployment 121 account option, domain 84 BDC. See Boot Disk Creator AClient capturing personality settings 179 upgrade to DAgent 196 BESR chat feature 132 sample jobs 197 AClient.
Page 498 Deployment Share 338 Web. see Deployment Web managing from 69 installing 349 Console Deployment Database 337 PXE server 338 copy connecting to new 91, 92, 93 computer file 188 installation 368 adding 98 Microsoft SQL Server and 340 folders 192 booting method 283 jobs 192 Deployment Server...
Page 499 drive mappings properties 321 creating 267 file server editing 267 requirement 341 server blades 140, 251 network 280, 305 file server type 275, 300 icons removing 267 file system independent resource Boot Disk Creator 77 setting up 305 management. see FIRM computer 96 drive mappings for DOS 117 Image Explorer 78...
Page 500 Deployment Agent for DOS 358 removing 154 editing shared 296 Deployment Agent for Linux 357 removing tasks from 154 Microsoft Deployment Agent for rescheduling 83, 154 client driver 352 Windows 353 running from resources view 154 SQL Server 340 Deployment Database 368 sample 456, 459 migrating computers Deployment Server 334, 365,...
Page 501 configuration color code 293 command line switches 413 multicasting 311 DOS 298 setting response times 308 PocketPC agent installing preboot files 297 viewing status 314 command-line switches 413 Linux 299 installing 491 Linux file location 289 port, TCP for file transfer 83 preboot 367, 367 quick disk image 125 power control 189...
Page 502 deployment 247 features 246 sample jobs 456 tabs services properties 120 manage user groups 89, 90 scan resource files for changes 82 settings rights 90 scheduling jobs. see jobs backing up and restoring files 183 tasks screen lock 403 capturing personality 179 building jobs 150 switch 403 changing agent 134...
Page 503 users add 89 defined token 81 importing 89 utilities 77 icons 77 kbdsclk 403 keyboard and screen lock 403 LogEvent 186 view refreshing 94 resources 72 shortcuts 72 virtual bays 250 centers 86 computer. see pre-configured computer account Virtual Bays 138 Vista Sysprep 28 VMware Virtual Center Web services 86...

This manual is also suitable for:

Altiris deployment solution 6.9 sp4

Symantec ALTIRIS DEPLOYMENT SOLUTION 6.9 SP4 - V1.0 Manual

Chapter 1: About Altiris® Deployment Solution

Part I: Planning and Installing Your Deployment System

Chapter 2: Preparing to Install

Chapter 3 Installing

Chapter 4: Post-Installation Configuration

Chapter 5: Deployment Agent Installation

Part II: Booting Computers to Automation

Chapter 6 What Is Automation

Chapter 7: Automation Boot Methods

Chapter 8: Automation Operating Systems

Chapter 9: Installing and Configuring Automation

Chapter 10: Setting up the Altiris PXE Server

Part III: Using Deployment Solution

Chapter 11 Deployment Basics

Chapter 12: Managing from the Deployment Console

Chapter 13: Managing Computers

Chapter 14: Building and Scheduling Jobs

Quick Links

Related Manuals for Symantec ALTIRIS DEPLOYMENT SOLUTION 6.9 SP4 - V1.0

Summary of Contents for Symantec ALTIRIS DEPLOYMENT SOLUTION 6.9 SP4 - V1.0