To enable SQL Server 2008
1. 2. 3. 4. 5. In the SQL Server Configuration Manager, expand SQL Server Network Configuration. Click Protocols for MSSQLSERVER. In the right pane, double-click TCP/IP. Change the Enabled field to Yes. Click OK.

Restart SQL Server.

You can now install Deployment Server.
Deployment Server components
The Deployment Server system includes the following components: Deployment Console Deployment Server Deployment database Deployment share PXE server DHCP Server (not an Altiris product) Deployment Web console Installing Deployment Solution agents Sysprep You can install all these components on the same computer or distribute them across multiple computers, depending on the environment.

Deployment Console

The Deployment Console is the Win32 user interface for Deployment Solution. You can install this Windows console on computers across the network to view and manage resources from different locations. In addition, from this console, you can access the Deployment Database on other Deployment Server systems to manage sites across the enterprise. See Deployment database on page 337 and Connecting to another Deployment Server on page 93. The Deployment Console communicates with the Deployment database and Deployment Server services. In a Simple Install for Deployment Server, the Deployment Console is installed on the same computer similar to all other components. In a Custom Install for Deployment Server, you must ensure that a connection is available to these computers and security rights are set. You must have administrative rights on any computer running the Deployment Console. See Simple install for Deployment Server on page 341 and Custom install for Deployment Server on page 344. See also: Deployment Web console on page 339, on page 69, and Deployment Server components on page 335.

Deployment Server

Deployment Server controls the flow of the work and information between the managed computers and the other Deployment Server components (Deployment Console, Deployment Database, and the Deployment Share). Managed computers connect and communicate with the Deployment Server to register inventory and configuration
information and to run deployment and management tasks. The computer and deployment data for each managed computer is stored in the Deployment Database. Note To view, start, or stop Deployment Server, go to the Altiris Server services in your Windows Manager. Managed computers require access to the Deployment Server at all times, requiring that you have administrative rights on the computer running the Deployment Server.

Note You can install only one Deployment Share for each Deployment Server system. However, if the Deployment Share's hard drive gets full, other computers can be used as additional backup storage points. In some cases, other systems emulating a Microsoft or NetWare environment can be used as the Deployment Share. Note for NetWare users: If you have a problem using the Novell NetWare server as a Deployment Share, install the Novell Client instead of the Microsoft NetWare Client. See Deployment Server components on page 335.

PXE server

The PXE Server provides service to client computers on a subnet. When the Deployment Server sends a deployment job, the client computer receives a request to boot to automation and the PXE-enabled computers connect to the first PXE Server that they discover, which communicates with the Deployment Server and the client computers. The PXE Server also functions on the same protocols as a standard DHCP Server, so you can place the PXE Server wherever you would place a DHCP server. You can also install as many PXE Servers as required in your system, but you must also install a DHCP Server. The PXE Server sends a boot menu option list to the client when the computer performs a PXE boot. The deployment job, which contains at least one automation task, uses the default automation environment or the environment specified by a user who has the permission to create a deployment job. Use the boot menu option to request the PXE Server for the boot menu files and download the boot menu files from the PXE Server to the client computers RAM storage. The client computer always boots according to the request and reply communications taking place between the Deployment and PXE Servers. Altiris supports DOS, Linux, and Windows PreInstallation Environment (WinPE) as preboot environments. These options let you create a single job, but may contain multiple automation tasks. The default automation environment (the first pre-boot operating system files installed during the Deployment Solution installation) is used for Initial Deployment, unless you specify otherwise. Using a PXE Server to boot client computers to automation saves you from having to install an automation partition on each client computers hard disk, or from manually starting computers using Altiris-supported bootable media.See Boot Disk Creator Help. See Pre-boot operating system (simple) on page 367, Install automation partition on page 133, and PXE Configuration Utility Help.

DHCP Server

The DHCP (Dynamic Host Configuration Protocol) server is a server set up to assign TCP/ IP addresses to the client computers. This server is not an Altiris product, but is required if you want to use the PXE Server. 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. See Deployment Server components on page 335.

Thin client install

The thin client install option lets you install the Thin Client view of the Deployment Console on your computer. You can install Deployment Server with a Microsoft Data Engine (MSDE) or install it on an existing SQL Server. You need not provide a license file for the Thin Client installation.
To run a thin client install
1. 2. Start the server and log on using the administrator account you created for the Deployment Server. See Deployment Server system requirements on page 340. Launch the appropriate Altiris Deployment Server installation file and follow the setup steps. The Altiris Packager Self-Extracting Executable Options dialog appears. 3. Select the Use current temp folder option to use the current temporary folder to download installation files or the Extract to a specific folder option to set a path to an existing folder to download the installation files. 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. Click Yes to All. You may have to wait for some time while Altiris Packager extracts files from this archive. Note Click Extract Only to only extract the application and execute the application later. You must run the axInstall.exe file to start the installation. 5. 6. 7. 8. Select the Thin Client Install option from the installation types listed in the Deployment Server Install Configuration dialog. (Optional) Select the Include PXE Server option to install the PXE Server. (See PXE server on page 338.) Click Install. Click Yes on the Software License Agreement page. Enter the following information on the Deployment Share Information page: a. In the File Server path field, enter or browse to the path to install the Deployment Server program files. The default path is C:\Program Files\Altiris\eXpress\Deployment Server. Select the Create Deployment Share option to create a Deployment Share on the computer. The Deployment Share lets you store files on the computer and run Deployment Server system applications. See Deployment share on page 338. You must enter an administrator user name and password for the Deployment Server system. This account must already exist on the Deployment Share and the Deployment Server. By default, the name you are currently logged on as appears. If you use a domain account, enter the domain and the user name (Example: Domain1\administrator). See Deployment Server on page 336. 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.
Click Next. The Pre-boot Operating System page appears. 9. Select a default pre-boot operating system from any one of the options, such as FreeDos, MS-DOS, Linux, WinPE, or None. Browse to locate the FIRM file (for FreeDos and Linux operating systems) or enter the path for the operating system files (for MS-DOS and WinPE). Click Next. The Installation Information page appears, displaying the components that you selected to install.

Using remote agent installer
You can create a template file when running Remote Agent Installer. After modifying agent properties and adding computers to the Selecting Clients window, click Export to create a template file to import computers (*.rci) as well as the template file (*.inp). Example: If you have computers named PC-1 and PC-2 listed in the Selecting Clients window and you export these computers using the file name Export.rci, the following two template files are created: Export_PC-1.inp Export_PC-2.inp

Using the template file

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

Option

-install -remove -silent

Definition

AClient.exe runs and installs the Deployment Agent on the computer instead of just running it in memory. Permanently removes the Deployment Agent from the computer where it is installed. Lets you use the options without being prompted for further input.
Stops the Deployment Agent from running, but does not remove it. The next time the computer is booted, the Deployment Agent runs in production mode. Starts the Deployment Agent. This option works only when Deployment Agent is installed on the computer.

-start

Installing Deployment Agent on Linux
You can install the Deployment Agent on any supported Linux workstation or server by downloading and running the Deployment Agent for Linux installation file (a.BIN file) on the client computer. The Deployment Agent is updated automatically on Linux computers when you upgrade to a new version of Deployment Solution. The creation date of the Deployment Agent is checked and updated when a new agent is available.
Installing the Deployment Agent for Linux
1. After downloading the.BIN file to a local directory, you can install from the command line. Browse to the directory where you saved the.BIN file, switch to the root user (su) and change the directory to the location of the.BIN file by entering

(cd < directory>)

After changing the directory, you must have the permission to execute the.BIN file; to obtain the permission, enter chmod 544 <filename> Enter:./<file name> The Deployment Agent for Linux is installed in the /opt/altiris/
deployment/adlagent directory.
2. To change the adlagent configuration file settings, update the adlagent.conf file. This file is located in the /opt/altiris/deployment/adlagent/conf directory. You can also change the adlagent configuration file settings by executing the configure script from the /opt/altiris/deployment/adlagent/bin directory. To edit the configure file directly, open the adlagent.conf file located in the /opt/altiris/deployment/adlagent/conf directory and make the required changes. You can also edit the configuration file to change the functionality or properties. Example: You can open the adlagent.conf file in an editor and scroll to the [Transport] section and the UseMcast line. Change UseMcast=true to UseMcast=false. In the TCPAddr=<IP address> line, enter the IP address of the specific Deployment Server you want to manage the client computer. You can also identify and edit additional configuration settings in the configuration file. To run the script to change the settings for the adlagent configuration file, browse to the /opt/altiris/deployment/adlagent/bin directory from the shell and enter

To disable SMB signing on the Windows 2003 server
1. 2. 3. Click Start > Control Panel > Administrative Tools > Local Security Policy > Local Policies >Security Options. Locate the Microsoft network server: Digitally sign communications (always) policy setting, right-click it, and select Properties > Disabled. Disable the Microsoft network server: Digitally sign communications (if client agrees) policy setting as well. This is enabled by default.
Specify the Deployment share (shared directory) where you want to store the image files,.RIPs, and other package files. Before installing the Deployment Server, ensure that you have a shared Windows or NetWare directory with free disk space and appropriate security rights. File server path. Select the drive letter and directory path where you want to install the Deployment Server. The default path is the Program Files directory on the local computer. Create Deployment Share. If you are installing the Deployment Server on a local Windows computer, select this option to create a shared directory as your Deployment Share. If you are installing on a remote file server or if you select an invalid path, this option is unavailable. Note If you are installing the Deployment Server on a remote file server, create a share or grant access rights to the Deployment Server directory on the file server before you start the installation. For Windows XP, you must run the Network Setup Wizard accessed from My Network Places to enable sharing.
Select one of the following options to configure the licensing information: If you do not have a license file, select the Free 7 day license option to use an evaluation license for a new Deployment Server installation. Select the Upgrade using existing license option to upgrade the installation using an existing license. Select the License File option and browse to locate the license file (.LIC file) that you received when you registered on the Altiris Web site. See the Altiris Getting Started Guide for further licensing information. Service username and Service password. If running a Simple Install, you must enter an administrator user name and password for the Deployment Server and the Deployment Share. This account must already exist on the Deployment Server and the Deployment Share. If you use a domain account, enter the domain name (Example: orgDomain\admin. See Deployment Server components on page 335, Installing Deployment Server, and Managing licenses on page 358.

[Submenus] Web Tools=wtools.ini [Notepad] MenuText=Notepad Editor Description=Simple Editor
WorkDir=. Executable=C:\WINNT\notepad.exe [NetMeeting] MenuText=NetMeeting Description=NetMeeting WorkDir=. Executable=C:\Program Files\NetMeeting\conf.exe
Another Tools.INI file is wtools.ini. It is a submenu file referenced by the main ATools.ini file. On the main menu, this is titled Web Tools (see Tools.ini) and contains two applications, Internet Explorer and Adobe Acrobat.
[Explorer] MenuText=Explorer Description=Windows Explorer WorkDir=. Executable=C:\Program Files\Internet Explorer\explorer.exe [Acrobat] MenuText=Acrobat Reader Description=Acrobat Reader WorkDir=. Executable=C:\Program Files\Adobe\Acrobat\acrobat.exe
Computer filters and job conditions
Use this dialog while creating a computer group filter to filter only the specified computers in a computer group, or while setting conditions for task sets when running a job only on the specified computers in a group. See Creating a computer group filter on page 81 and Setting conditions for task sets on page 151.
Creating conditions to assign jobs
You can set conditions on a scheduled job to run only on the computer devices that match a defined criteria. As a result, you can create a single job with tasks defined for computers with varying properties, including the type of the operating system, network adapters, processors, free disk space, and other computer properties. For each job, you can now create task sets that are applicable only to the computers matching those conditions.
Click a job in the Jobs pane. The Condition feature appears in the Details pane. Click Setup to add new conditions or edit existing conditions. When you are setting conditions to schedule a job, select from a list of predefined database fields or create custom tokens that key on other fields in the database.

Creating custom tokens

You can create custom tokens to set conditions based on the database fields that are not provided in the available preset conditions in the Conditions dialog. Example: Select User Defined Token from the drop-down list in the Fields box. Select contains in the Operation field, and enter Milo in the Value field. In the Token field, enter the following custom token: %#!computer@lic_os_user%. This filters out only the jobs with the registered license user named Milo. The job runs only on the computers that meet the specified criteria.

Importing new computers from a text file
You can import computer configuration data using delimited text files (.TXT,.CSV, or.IMP files) to establish multiple computer accounts in the Deployment Server database. This file contains all configuration data for a new computer, including all settings in the Computer Properties of a selected computer. See Computer properties on page 119. 1. Click File > Import/Export > Import Computers. A dialog appears, letting you select import files. These files can have.XML,.TXT,.CSV, or.IMP extensions. 2. Select the import file. Click Open. If a correctly formatted computer import file is selected, a message appears, informing you that the computer import is complete and identifying the number of computers added. Click OK. New computers appear as pre-configured computer accounts in the Computers pane of the console (as single computers or in groups), and any jobs imported from the import file are listed in the Jobs pane. Note Jobs can be added to the import file. They can be created and associated with the new computers. If the computer import file is incorrectly formatted, a warning appears, stating that the computer import file is incorrect.
Edit computer settings by selecting a computer from the list and clicking Properties. The Computer Properties page opens. You can edit or add values not set in the import file, such as computer name, TCP/ IP settings, user name, and other configuration settings. Click OK. The imported computers appear in the Computers pane of the Deployment Console.
You can also import a computer to be placed in a sub-folder in the Computers pane and create a job to be associated with the imported computer. See the sample import file for additional information.
Referencing the sample import file
When creating an import file, use either the ImportComputers55.txt file or the ImportComputers55.xls file in the Samples folder of the Deployment Share. The ImportComputers55.txt file provides a sample import template you can access to test the Import feature. The ImportComputers55.xls file is a Microsoft Excel spreadsheet that lets you add values to each identified column and save the file as a delimited TXT file to import to the Deployment Database. The sample import file places a computer (DB Computer 1) in a computer group (Test Group) and adds a job (Test Job) associated with the imported computer.

NetWare client configuration settings
Set Novell NetWare client values for a new or existing computer. Select whether you want to log in directly to a NetWare server or to a NetWare tree in the Novell Directory Service (NDS). You can specify the preferred tree, server name, and NDS context.
Ignore NetWare settings Preferred server Preferred tree NDS User name NDS Context
Select to disregard all Novell NetWare client settings for this computer. Clear to specify the required information. Select this option and enter the name of the NetWare server. Example: \\OneServer. This is the primary login server for the NetWare client. Select this option and enter the name of the NDS tree. Enter the name of the user object for the NetWare client. Enter the organizational unit context for the user.

Run login scripts

Select this option to run the NetWare client login scripts. See also Computer configuration properties on page 101.
Operating system licensing configuration settings
Enter or view the license information for your Windows operating system software.
Registered user Organization License key
Enter the name of the registered user. Enter the name of the organization. Enter the alpha-numeric license key. This is the hash value rendered from the OEM key or 25-digit license key required when installing the operating system. See also Computer configuration properties on page 101.
User account configuration settings
Set up local user accounts for the newly imaged computer or when running a configuration task. Enter a user name, full name, and password; and set standard Windows login options.
User name Full name Password Confirm password Groups
The user name for this local Windows user account. The full name for this local Windows user account. The password for this local Windows user account. Confirm the password for the local Windows user account. Specify the Windows groups that this user belongs to as a comma-delimited list. Example: Administrators, Marketing, Management.
User must change password at next logon User cannot change password Password never expires

Finding a computer in the database
This search filter lets you type a string and query specified database fields for specific computer properties. You can search for user or computer names, licensing or location information, or primary lookup keys: MAC address, serial number, asset number, or UUID. This search filter queries property values appear in the Computer Properties pages. See Computer properties on page 119.
Click <CTRL> F or click Find Computer on the console toolbar to search the Deployment Database for computers by property settings. The search begins at the top of the computer list and highlights the computer name in the Computers pane when a match is found. Press F3 to find the next computer that matches the search criteria until there are no more results, or the end of the computer list is reached.
In the Search For field, type all or part of the computers property values you would like to search for. This alpha-numeric string is compared with specified database fields. From the In Field drop-down list, select the field you want to search in the Deployment Database. Example: To find a computer by searching for its IP address, type the address in the Search For field and select the IP Address from the In Field drop-down list.
Name Computer Name MAC Address IP Address ID Serial Number Asset Tag UUID Registered User Product Key Logged On User Physical Bay Name
BIOS name of the computer. Deployment Solution name of the computer. Example: 0080C6E983E8. Example: 192.168.1.1. Example: The computer ID. 5000001. Serial number installed in BIOS. A primary lookup key. Asset number in BIOS. A primary lookup key. A primary lookup key. Name entered when the operating system was installed. Product Key for the operating system. Name of the user currently at the computer. The actual bay number. Example: 7x.
The computer you are looking for appears highlighted in the Computers window in the console. Note This search is not case-sensitive and allows wildcard searches using *. See also Computer filters and job conditions on page 80.

Using lab builder

Use the Lab Builder to set up jobs under the Lab folder in the Jobs pane to set up a classroom or lab environment.
Click Lab Builder on the console toolbar or click File > New > Lab Builder to set up jobs specifically created for managing multiple computers in a lab environment.

You can set up jobs to:

Create Disk Image Deploy Lab Restore Lab Update Configuration Upload Registries
Each of these jobs contains a default list of tasks. Lab Builder places these five new jobs under a folder (which you name) located under the Lab folder. All tasks in the jobs have been assigned default paths and file names that let them use the same images and configuration information, registry data, and so on. We recommend that you do not change the file names and paths. If you change the default settings (example: changing the image name), you must change them in all jobs where the image is used.

To create an image of a computer, you must boot to DOS, Linux, or WinPE. This requires that you set up a PXE Server or install an automation partition.

To create a disk image

1. 2. 3. In the Jobs pane in the Deployment Console, select a job. In the Details pane, click Add and select Create Disk Image. In the Create Disk Image dialog, select an imaging tool from the drop-down list. You can select RapiDeploy (Text mode), RapiDeploy (Graphics mode), RapiDeploy (Linux mode), ImageX, Mac Image or Ghost.
RDeploy Options RDeployT is the default imaging executable. This facilitates the imaging of thin client computers. The following are the RapiDeploy options for imaging: Graphical Mode (RDeploy). Select this option to run the RDeploy in a GUI mode. Text Mode (RDeployT). Select this option to run the RDeploy in a text mode. Linux (RDeploy). Select this option to run the RDeploy in Linux mode. You can select the ImageX or Mac Image option for imaging. If you select ImageX, the image is created as a.WIM file. If you select Mac Image, the image is created as a.DMG file. For information on creating a Mac Image, see Creating a Mac image on page 159. You can also select the Ghost option for imaging. If you select Ghost, the image is created as a.GHO file. For information on creating a Ghost Image, see Creating a Ghost image on page 160. Important Linux (RDeploy) and Ghost options are available only when the ImageTools.ini file is stored in the eXpress folder. 4. Enter additional parameters in the Additional Parameters field. You can add command-line options specifically for the RapiDeploy program to run imaging tasks. See Command-line Switches in the Deployment and Migration Guide. 5. Enter a path and file name to store the disk image file. You can store image files to access later when a managed computer is assigned a job that includes the image file. The default file name extension is.IMG. Saving image files with an.EXE extension converts them into self-extracting executable files (the run-time version of RapiDeploy is added in the file). You can also save ImageX files with a.WIM extension, a Mac image with a.DMG extension, and a Ghost image with a.GHO extension. If WinPE is used, Deployment Solution supports UNC and DFS paths in the Name field. For example, you can type \\My_Server\My_Volume\myimagefile.img in the Name field. 6. Select Disable image path validation if you want to store the image file outside of the Deployment Share file structure. If you do not select this option and do not specify a Deployment Share path, a warning message appears, reminding you to configure your automation process to use the path indicated in the Name field. You can still save your image to a location outside of the Deployment Share file structure even when you do not select this option. This option only eliminates the warning message. You can use this option to store images locally on the managed computer's hard drive or to an additional server used to store images. If you typed a UNC path in the Name field and the server does not have access to the path, check to disable image path validation. Otherwise, the process fails. When storing images locally on the managed computer's hard drive, ensure that you enter the path relative to the managed computer (Example: C:\myimage.img). When you store an image locally on a managed computer instead of a file server, you save server disk space and reduce network traffic.

Note The command-line switches are specific to any package you are distributing that supports command-line options, such as.MSI and Personality Packages. For a complete list of command-line options, see the Wise MSI Product Guide and the Altiris PC Transplant Pro Product Guide. 5. If distributing an install package or other types of packages with associated support files, you can select Copy all directory files to install all peer files in the directory. Select Copy subdirectories to distribute peer files in the directory and all files in associated subdirectories. Note Some clients may have software installed on the client computer that, for protection against harmful software, only lets software programs on a list of "well-known" executables to run. Therefore, whenever the system administrator wanted to install a patch on client computers, he or she would have to update the well-knownexecutables list on all the client computers, which could be a lot of work. To save the work of updating that list, or of manually renaming distribution packages, the RenameDistPkg feature was added. Now, the system administrator may update the well-known-executable list once with a filename of their choice. The well-known filename may be entered into the Windows registry of the Deployment Server computer (the computer running axengine.exe) as the Value data of a string value named RenameDistPkg under the HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Altiris eXpress\Options key. If the RenameDistPkg registry entry is set, Deployment Server renames the installation files that are copied to the client computers. This feature only affects files that are temporarily copied to the client computer as part of a Distribute Software task. The file that is to be executed only during the installation, sometimes referred to as the package, is the file that is renamed, not the files that are actually installed to various locations on the target computer. If the Copy all directory files option is enabled, only the main (installable) file is renamed. 6. Click Advanced to specify how files are distributed to the managed computer. You can copy through the Deployment Server, or copy directly from the file source and then run, or run directly from the file source. See Distribute software advanced on page 177. Click Next. Provide additional command-line options for distributing software. (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.

Note If you are using LogEvent and WlogEvent in Scripts, you can generate return codes only when the level 3 message is specified. Specifying a severity level 3 causes the script job to fail and lets you respond using this return code feature.

Return code actions

For both successful tasks (in the Success field) and failed tasks (in the Default field), you can specify the following actions: Stop. This action stops the job after the task runs. Subsequent tasks do not run. Continue. This action lets the subsequent tasks in the job continue after the task runs. Select a job. This action lets you select existing jobs to run after the task completes. These actions also apply to custom return codes designed specifically for your system.

Custom return codes

In the Other return codes field, you can view custom return codes set specifically for your system. You can add return codes by clicking Add below the Other return codes field, or by clicking Master Return Code. Type a custom code in the Code field, select a response action from the Response list, select the result from the Result list to specify the interpretation of this return code as Success or Failure, and provide a message in the Status field. These custom codes can respond to any return codes set up in scripts or batch files in the Run Scripts task, or these custom codes can respond to system return codes thrown from the Deployment Server or external codes generated when distributing applications, personality settings, or disk images. Any task can have custom codes that respond to different return code values. Master Return Code List. This is a list of all the return codes existing in the Deployment Database. You can add, modify, and delete the codes and their values so that setting codes for other tasks is easier. Add. This lets you add a new custom return code for the task. You can also add the return code to the Master Return Codes list. Modify. This lets you modify the return codes listed in the Other return codes field. The changes you make do not update the Master Return Codes list. Delete. This lets you delete return codes listed in the Other return codes field, but not from the Master Return Codes list.

Master Return Codes lists. This is useful if you want to use the return code again. Click OK. 8. If the code you added already exists, a message dialog displays the return code and asks if you want to replace it. Click Yes to replace the return code, and click No to return to the Add Return Code dialog. Select the Select a job option from the Default drop-down list to select a job to run when a default condition is reached. The Select a Job dialog appears, letting you select an existing job that runs if the task returns a failed system return code (non-zero) or a return code not defined as a custom return code.
Note The status of the tasks executed in a job also appears in the history of a computer.

Sample jobs

Sample jobs are installed with each Deployment Server system, letting you quickly modify or add parameters, or to run the sample jobs as they are. During installation, jobs are automatically imported from the samples.bin file to the Deployment Server system where they can be viewed in the Samples folder in the Jobs area of the Deployment Console. Click each job and identify its features in the Description field of the Details pane. Jobs in each folder marked with an asterisk (*) require input parameters or other minor modifications added before running on your system. These modifications let you add parameters to the job, such as user name and password or other required data for the job to be functional. Jobs requiring input parameters or customizing do not function properly if you do not edit the job with the information specific to your environment. All files without an asterisk (*) can be used to perform the identified functions without modification. However, if the job conditions are not met or are not consistent with the computer type, you may get an error. Example: If the Repair Office XP job runs on a computer without MSOffice XP, you get an error when running the job. Note When upgrading versions of Deployment Solution, we recommend that you copy and rename modified sample jobs to avoid overwriting by new sample jobs.

DAgent

DAgent is the default agent for the Windows platforms. You can implement the following features in the Security tab: Hide the DAgent icon in the system tray of the managed computer. You then need to run DagentConfig.exe as an administrator to view the administrator properties. 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 3minute lock-out time period begins and an appropriate error message displays. You can also uninstall DAgent.

Uninstalling DAgent

You can uninstall DAgent from the client computer. This functionality is provided only from the console side.

To uninstall DAgent

1. 2. In the console, right-click. Click Advanced > Uninstall Agent.

Chapter 22: Deploying Scripts. 234
Writing a Script. Server Scripting Commands. Retrieving Database Values Using Tokens Running Scripts on the Server. Reporting Errors. DOS/CMD Error Handling. Visual Basic Error Handling. Linux Shell Error Handling. 239 240
Chapter 23: Creating an Image Distribution Framework. 241
Why Use an Image Distribution Framework?. 241 PXE Redirection. 242
What if I Am Not Using PXE?. Tools. Creating a Distribution Framework. Step One: Set Up Local Image Stores. Step Two: Replicate Images. Step Three: Configure the Server Lookup Utility. Create a Configuration. Create a Server Lookup File. GetSRV.EXE Parameter Descriptions. Step Four: Create a Boot Disk Creator Configuration Modify Mapdrv.bat to call Getsrv.bat. Deploy the Boot Configuration. Step Five: Distribute an Image.
Chapter 24: Deploying and Managing Servers. 246
Server Management Features. Server Deployment Options. Managing Server Blades. Managing New Server Blades. Hewlett-Packard Server Blades Virtual Bays. Dell Server Blades. Fujitsu-Siemens Server Blades. IBM Server Blades. 251
Part V: Operating System and Platform Reference. 252
Chapter 25: 64-bit Platforms. 253
64-bit Job Conditions and Filters. 253 64-bit PXE Boot Images & Configurations. 253 Adding Files to a Boot Disk Creator Configuration for 64-bit. 253
Chapter 26: Linux and Unix Systems. 254
ADLAgent. Installing and Configuring ADLAgent. Distributing Software. Imaging Linux and Unix Filesystems. Linux Bootloaders. 255
Chapter 27: Managing Thin Clients. 256
Supported Thin Client Manufacturers Thin Client Operating Systems. Windows XP Embedded (XPe). The Enhanced Write Filter. Using the EWFMGR Utility. Windows CE.NET. Linux. Licensing Thin Clients.. 260 260
Chapter 28: Windows Vista. 261
Install the Deployment Agent on Vista Silent Installation. UnInstallation. Start and Stop the DAgent Services.. 261 261
Vista Software Distribution. 261 Vista Run Script Tasks. 262 Vista Imaging. 262
Chapter 29: Mac Deployment Agent. 263
Installing The Mac Deployment Agent. 263 Removing the Mac Deployment Agent. 263
Part VI: Reference: Deployment Solution Help Files. 264
Chapter 30: Deployment Server Configuration Utility. 265
Service Logon Account General Options. Drive Mappings Option Transport Option. Disk Imaging Option. Authentication Option Connections Option. Debug Option. 271 272
Chapter 31: Introduction to Altiris Boot Disk Creator. 273

After the installation completes, you have the option of remotely installing the Deployment Agent. Unless you are familiar with Deployment Solution and the Remote Agent Installer, we recommend you do not install the agent at this time. A full discussion of Deployment Agent rollout is contained in Deployment Agent Installation (page 34).

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) Step 4: Configure Your Deployment System (page 31) Step 5: Configure Security Settings (page 33) Step 6: Install the Deployment Agent (page 33) Step 7: Configure Automation (page 33) Step 8: (Optional) Configure PXE Server (page 33)
Step 1: Grant Full Control of the Deployment Share to Your Service Account
If your Deployment Share was created during the installation, grant the services account full control of this share. By default, this folder is C:\Program Files\Altiris\eXpress\Deployment Server.
Step 2: Create Domain Join and Deployment Share Accounts
After installation, we recommend creating some additional accounts. These accounts are different than the accounts used by the people who are going to manage computers. These accounts are not tied to users, and should not possess interactive login or any rights beyond what is recommended here. The domain join account is used to join or re-join computers to a domain after imaging or initial deployment. The Deployment Share read/write account is used to access this share from the automation environment.

Domain Join Accounts

Create a separate domain-level account for each domain in which you manage computers, granting the rights recommended in the following table:

Rights

Domain
Grant privileges to add computer to domain.
Deployment Share Read/Write Account
Create this account on the computer hosting your Deployment Share, granting the rights in the following table:

File System

Grant read/write privileges to your Deployment Share.
Step 3: Grant Services Account the db_owner Role to Your Deployment Database
Double-click the account you are using to run the Deployment services. If the login is not listed, add it. Click the Database Access tab, select the eXpress database, and enable the db_owner role:
Click OK and verify that the change was successful.

[Explorer] MenuText=Explorer Description=Windows Explorer WorkDir=. Executable=C:\Program Files\Internet Explorer\explorer.exe [Acrobat] MenuText=Acrobat Reader Description=Acrobat Reader WorkDir=. Executable=C:\Program Files\Adobe\Acrobat\acrobat.exe
Computer filters and job conditions
Use this dialog while creating a computer group filter to filter only the specified computers in a computer group, or while setting conditions for task sets when running a job only on the specified computers in a group. See Creating a computer group filter on page 81 and Setting conditions for task sets on page 151.
Creating conditions to assign jobs
You can set conditions on a scheduled job to run only on the computer devices that match a defined criteria. As a result, you can create a single job with tasks defined for computers with varying properties, including the type of the operating system, network adapters, processors, free disk space, and other computer properties. For each job, you can now create task sets that are applicable only to the computers matching those conditions.
Click a job in the Jobs pane. The Condition feature appears in the Details pane. Click Setup to add new conditions or edit existing conditions. When you are setting conditions to schedule a job, select from a list of predefined database fields or create custom tokens that key on other fields in the database.

Creating custom tokens

You can create custom tokens to set conditions based on the database fields that are not provided in the available preset conditions in the Conditions dialog. Example: Select User Defined Token from the drop-down list in the Fields box. Select contains in the Operation field, and enter Milo in the Value field. In the Token field, enter the following custom token: %#!computer@lic_os_user%. This filters out only the jobs with the registered license user named Milo. The job runs only on the computers that meet the specified criteria.

Filter Name

Active Computers Inactive Computers Computers With Failed Jobs Windows 2003 or 2008 Windows XP/ Vista Windows CE (PDAs) Linux Windows XP Embedded Windows CE.NET Pocket PC (PDAs)
Displays all the active computers. Displays all the inactive computers. Displays all the computers where jobs have failed to execute. Displays only the computers with Windows 2003 or 2008 operating systems. Displays only the computers with Windows XP or Vista operating systems. Displays only the computers with Windows CE operating systems. Displays only the computers with Linux operating systems. Displays only the computers with Windows XP Embedded operating systems. Displays only the computers with Windows CE.NET operating systems. Displays only the Pocket PC computers.

Computer icons appear in the Computers pane of the Deployment Console, where they can be organized into groups. To assign and schedule a job on a computer in the Deployment Server Console, drag a computer icon or group icon to a job icon.
Add new computers. Deployment Solution lets you add new computer accounts and set configuration properties for new computers before they are recognized by the Deployment Server system. Preset computer accounts automatically associate with new computers when they start up, or can be associated with pre-configured computers. See Adding new computers on page 98.
Click New Computer on the console to create a new computer account. You can also click File > New > Computer or right-click in the Computers pane and select New Computer. When the new computer starts up, you can assign it a preset account. Click 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.
Deploy to groups of computers. Organize computers by department, network container, hardware configuration, software requirements, or any other structure to meet your needs. You can deploy and provision computers on a mass scale. To filter computers in a computer group to schedule jobs only to the appropriate computer types, see Computer filters and job conditions on page 80. Configure Computer Agents. See the property pages for modifying Deployment Agent settings. See Deployment agents on page 109. View and configure computer properties. You can modify computer settings for each computer from the console. Or you can view the Computer Properties page for detailed access to a computers hardware, software, and network property settings. See Computer configuration properties on page 101 and Computer properties on page 119. Run remote operations from the console. Perform operations quickly in real time from a Deployment Console. Restore a computer to a previous state, configure property settings, send a file, remote control, chat, set security, run deployment jobs, or select from additional management commands. See Remote operations using Deployment Solution on page 122. Build and schedule jobs. Build deployment jobs with one or more management tasks to run on selected computers. Create jobs, add tasks, and assign the job to computer groups. Jobs can be organized and assigned for daily tasks or to handle major IT upgrades. See on page 145. Manage Servers. Deployment Solution also manages network or Web servers to administrate high-density server farms or server network resources across your organization. See the Deployment Solution Reference Guide.

Deployment Server Agent

Install Deployment Agent to add a managed computer
When a Deployment Agent is installed on a computer, it searches the network for a Deployment Server to attach to. When the Deployment Agent locates a Deployment Server, the client computer is added as a record to the Deployment Database.
When the Deployment Agent for Windows is running on a computer, the user sees a small icon in the system tray. When the icon is blue, the client computer running the Deployment Agent is connected to the Deployment Solution system. When the Deployment Agent for Windows icon is clear, it shows that the client computer is not connected to the Deployment Solution system. The agent may be configured incorrectly, the Deployment Server is down, or other network problems exist.
Automatically update to newer version of Deployment Agent
At times, Altiris may update versions of the Deployment Agent to enhance features. For best performance, we recommend that all managed computers run the latest version of the Deployment Agent. When a new version of the Deployment Agent is saved to the Deployment Share file server, the managed computers automatically update the Deployment Agent. 1. From the computer where Deployment Server is installed, click Start > All Programs > Altiris > Deployment Solution > Configuration. The Altiris Deployment Server Configuration Utility page appears. Click Options. Click Transport. Select the Automatically update clients option and click OK.

2. 3. 4.

Deployment agent settings
You can set the default agent settings when new client computers are added to the system that the Deployment Server manages.
You can also modify the properties settings for the Production or Automation Agent through the Automation Agent. To set or modify agent settings in the Deployment Server Console for Windows or Linux clients, right-click the computer and select Change Agent Settings > Production Agent Settings. To set or modify agent settings for the Deployment Agent, click Tools > Options. Click the Agent Settings tab. Select the Force new agents to take these default settings check box to set the Deployment Agent settings for all new computers. Click the Change Default Settings tab. Click each agent setting tab to set the properties. See Server connection on page 112, Access on page 113, Security on page 114, Log file on page 114, Proxy on page 115, and Startup and shutdown on page 115. Click OK. To view or modify settings from the Windows client, right-click the Deployment Agent icon in the system tray (or double-click the client icon in the system tray and click Properties).

Command-line switches for scripted install
Use the Scripted OS install commands dialog to enter Windows commands that are executed from the cmdlines.txt file. You can also add scripted install command-line options. Switches. Add or edit switch commands to this line for the install program for the scripted install. Additional commands in the cmdlines.txt file. Enter additional Windows scripted install commands in this dialog. The commands execute in the order they are listed. The provided command installs the Deployment Agent for Windows during the Install Component phase of the installation. You can view and edit Deployment Agent settings in the next dialog. See also Scripted install for Windows on page 169.
Deployment agent settings for scripted install
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.

Scripted install summary

View a summary of the selected options for the scripted install. Click Back to change any of these settings or click Finish to complete the Scripted Install task. Click Next to set up return codes. See Setting up return codes on page 193. See also Scripted install for Windows on page 169.
Scripted install for Windows Vista and 2008 server
The Scripted OS install for Windows Vista and Windows 2008 Server provides a wizard to help set up Vista and Windows 2008 Server installation files and run sample jobs. Follow the steps in the wizard to identify the type of scripted install as Vista or Windows 2008 Server. You can gather all the files for Vista or Windows 2008 Server for the job, but the server does not build any answer file. Instead, you are asked for the location of the answer file. Also, a sample answer file is provided.
To perform a scripted install for Windows Vista and 2008 server
1. On the Scripted Operating System Installation page of the Scripted OS Install dialog, select the following options: Windows Vista or Windows 2008 Server as the operating system Operating system language Automation pre-boot environment Note Deployment Solution supports only WinPE environments. Click Next. 2. From the Select or add new OS source files drop-down list on the Installation Source Files page of the Scripted OS Install dialog, select Vista or Windows 2008 Server. (Optional) You can select the required option from the Select or add new service pack source files drop-down list. Click Next. Select the Select a DOS disk image\Diskpart tool option on the Partition and Format Disk page of the Scripted OS Install dialog to partition and format the disk. Click Next. Note You can select the Continue without selecting DOS image\Diskpart Tool option to partition and format the hard disk using your own scripts and setup utilities. 5. 6. On the Scripted Operating System Installation page of the Scripted OS Install dialog, browse to select the path of the unattended.XML file. 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

Use the steps below to copy and paste tasks within the same job, or from one job to another. You can use CTRL+C and CTRL+V to copy and paste tasks. 1. 2. In the Jobs pane, click the job that contains the task you want to copy. In the Details pane, right-click the task, and select Copy. (To copy multiple tasks, press the CTRL key and select the desired tasks. The tasks that are highlighted are copied when you select Copy.) In the Jobs pane, click the destination Job where you want to paste the task. Right-click in the Details pane and select Paste. The tasks 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.
To modify a task in a job
1. 2. 3. In the Jobs pane, double-click the job you want to modify. Select the desired task from the list. Click Modify and follow the directions to make the required changes. Click OK.
To remove a task from a job
1. 2. 3. In the Jobs pane, double-click the job you want to modify. Select the task you want to remove from the task list. Click Delete. Click OK.

To copy and paste tasks

Use the steps below to copy and paste tasks within the same job or from one job to another. You can also use CTRL+C and CTRL+V to copy and paste tasks. 1. 2. In the Jobs pane, click the job that contains the task you want to copy. In the Details pane, right-click the task and select Copy. (To copy multiple tasks, press the CTRL key and select the desired tasks. The tasks that are highlighted are copied when you select Copy.) In the Jobs pane, click the destination Job where you want to paste the task. Right-click in the Details pane and select Paste. The tasks appear at the bottom of the task list and use the current condition settings of the destination job. Change the order of the tasks using the up and down arrows. The tasks execute in the order listed.
To add a new task to an existing task list
1. 2. 3. Select a job from the Jobs pane. Click on one of the tasks within the job and add a new task. The new task is inserted above the task you highlighted, and all other jobs shift down by one position. Use the up and down arrows to change the order of the tasks within the job.

Modifying multiple modify configuration tasks
If you have scheduled multiple Modifying Configuration tasks to a computer group, you can double-click Modify Configuration in the task list of the Details pane to modify each computers configuration settings independently. In the Jobs pane, click the job with a Modify Configuration task. Double-click the Modify Configuration task. A message appears. Click YES to modify configuration settings individually for each scheduled computer. Click NO to modify the Modify Configuration task when the job is scheduled again (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.
In the Computer Configuration Properties property page, modify the settings. Click Next. See Computer configuration properties on page 101. Set Return Codes. See Setting up return codes on page 193. Click Finish.
Creating new script files
You can create script files and directly schedule the script file to run scripts on any computer or computer groups.
To create new script files
1. 2. 3. Go to View > Shortcuts View. Click Resources in the Shortcuts view to move the focus to the Resources view. Go to File > New > Script File. Note The Script File option is activated only if the focus is on the Resources view. A script file is created by default at the root of the resources. The default file name is Batch.bat. 4. Right-click the Batch.bat file, and select Modify. Note You can rename the batch file by right-clicking the file and selecting Rename. 5. 6. 7. Type the script in the open file, and save it. Drag the Batch.bat file to a computer or computer group where you want to schedule the job. Specify the scheduling options, and click OK. See Scheduling jobs on page 153.
Copy and paste jobs and job folders
Jobs or job folders (including their subfolders) can be copied to any other job folder in the left pane of the Jobs pane of the Deployment Console. A Job folder can only be copied to a root level folder, which has a limit of 30 subfolders, and cannot be copied to a child level folder. If you copy a job or folder with the same name as the destination job or folder, the copied job or folder is automatically named Copy of <job or folder name>. This feature can only be performed by administrators or users who have permissions to create jobs or job folders.
To copy jobs and job folders
1. 2. 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.
Importing and exporting jobs
Jobs can be exported to back up the Deployment Server data or to share jobs between Deployment Server installations.

To import jobs

1. Right-click in the Job pane, and select Import or Click File > Import/Export > Import Jobs. 2. 3. 4. 5. Browse to or enter the path and name of an existing import file (a.BIN file). Select Import to Job Folder to import the jobs to an existing folder in the Jobs pane. If you have a folder already selected, it appears in the edit field. Select Overwrite existing Jobs and Folders with the same name to replace identical jobs and folders. Select Delete existing Jobs in folder to overwrite and replace all jobs in the selected Jobs folder. Click OK to import the job(s).

Server Scripting Commands
DS provides several predefined commands you can use when deploying scripts. These commands are processed before a script is deployed to a client. Each of these scripting commands must be marked by the correct comment flag to prevent them from being processed by the OS: The following table contains the comment flags for each scripting environment:
Comment Flags Flag Location Used

Batch files.

REM #

REM [servercommand]

Linux shell scripts.

# [servercommand]

Visual Basic scripts.

[servercommand]

The following table contains the predefined server scripting commands:
Server Scripting Commands Command Description
Unloads BootWorks to provide additional memory for complex scripts. BootWorks is unloaded automatically when you specify ScriptedInstall.
BootWorks Unload ReplaceTokens

BootWorks Unload

Tokens are replaced automatically in your scripts. This command replaces tokens in additional files, such as those used when configuring a computer. Source represents the source file containing the tokens you want replace, and destination represents the output file after tokens are replaced.
ReplaceTokens [source] [destination] ScriptedInstall Indicates that this script is launching a scripted install. 394k of free
memory is required for the Windows scripted install to run. BootWorks is automatically unloaded for scripted installs.
ScriptedInstall Deployment Start
When using blade servers, this option places a note in the history to mark a starting point. If a redeployment is later executed on this computer, the computer is restored from the deployment start mark in the history.
Deployment Start vbscript
Indicates that this script contains vbscript. If this appears anywhere in your script, the entire script is executed as a vbscript (you cannot execute batch commands and vbs commands in the same script). The comment flag is always used with the vbscript server command when writing Visual Basic scripts to ensure that it is ignored by the VB processor.

vbscript

Retrieving Database Values Using Tokens
Any tokens contained in a script are replaced automatically. A server command is also provided to replace tokens in other files, called ReplaceTokens. Example: to deploy a custom sysprep.inf file to several computers, the ReplaceTokens command could be contained in a script to replace tokens in sysprep.inf, this file could be copied with the correct database values to the production drive of the computer. A script to perform this task might look similar to the following:
REM ReplaceTokens.\temp\sysprep.inf.\temp\%COMPNAME%.txt Firm Copy f:\temp\%COMPNAME%.txt PROD:\sysprep.inf
When replacing tokens, the server creates a temporary file in the \tmp folder, named machinename with the same extension as the original script. This file contains a copy of the script with all token replacements made by the server, and is a valuable tool for troubleshooting.

Create a Server Lookup File
Each server in the lookup file consists of two entries: the IP address/subnet entry and the corresponding server name. The IP address and subnet are separated by a slash ( / ), and the corresponding server name is separated by a comma (,). For example:
172.16.0.0/255.255.0.0,SERVER1 192.168.1.0/255.255.255.0, SERVER 2 192.168.2.0/255.255.255.0, SERVER 3
Create entries in this file for each IP segment to which you might deploy images.
GetSRV.EXE Parameter Descriptions
The following table contains descriptions of the getsrv.exe parameters:

Parameter

/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). Environment variable containing the selected server. This token is used when creating the boot configuration, and is set to SERVERNAME in these examples.

/v [variablename]

Step Four: Create a Boot Disk Creator Configuration
After you have configured getsrv.bat, you need to create and modify a boot configuration. This configuration is used to boot managed computers to the automation environment for imaging. 1. 2. In Boot Disk Creator, create a new boot configuration using your selected automation boot method and environment. Create a drive mapping for your image share, using the %SERVERNAME% variable rather than an actual servername. (The name of this environment variable is specified using the /v flag of getsrv.exe. We recommend using SERVERNAME). This drive mapping should look similar to the following:

\\%SERVERNAME%\[share]

Replace [share] with the share name of your local image stores. 3. Managed computers must be able to resolve the name of the central Deployment Server. If using DOS automation, NetBIOS is used to resolve names, so we recommend adding your Deployment Server to the lmhosts file. We also recommend adding the name and IP address of each server hosting an image store. After the wizard completes, within the configuration, create a folder named Tools and copy the following files: getsrv.exe getsrv.bat
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. 1. 2. 3. Launch Boot Disk Creator. Expand the configuration you created in the previous section. Modify mapdrv.bat to add the following line after the first line of the file:

To configure the 5001 and 5002 ports
1. 2. 3. 4. 5. Open the Deployment Console and click Tools > Options. The Program Options dialog appears. Click the Global tab. Select the Remote control ports check box. Enter port number 5001 in the Primary field. Enter port number 5002 in the Secondary (Optional) field. Note: Port 5002 is the backup port in case Port 5001 is not available. 6. Click OK. Note: By default, Port 5001 is used for controlling the clients remotely.
The Deployment Agent is installed on each client computer in the Deployment Server system to remotely manage the computers from a Deployment Console. The
Deployment Agent on Windows runs on Windows computers, including desktops, notebooks, and servers.
To configure the 402 port
1. 2. 3. 4. 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. Select the Connect directly to this Deployment Server option or select the Discover Deployment Server using TCP/IP multicast option. Enter the port number. Note: By default, this port number is 402. Note: When the AClient is connected to the Deployment Server on port 402, it internally creates a listening UDP socket on port 402 to accept Wake-up packets from the server.
The Deployment Agent is installed on Linux workstations and server to establish communication between Linux computers and the Deployment Server. This agent collects and sends data from the client computer to the Deployment Server, executes deployment tasks sent from the server, installs packages, and runs management processes as directed from a Deployment Console.
1. 2. 3. To edit the configure file directly, open the adlagent.conf file at the following path: /opt/altiris/deployment/adlagent/conf. Change the value corresponding to the TCPport= if necessary. The default value is 402. Restart the ADLAgent service.
To configure the 415 port
1. 2. 3. To edit the configure file directly, open the trace.conf file at the following path: / opt/altiris/deployment/adlagent/conf. Change the value corresponding to the TcpTracePort= if necessary. The default value is 415. Restart the ADLAgent service. Note: Port 415 is used to remotely view debug messages from the ADLAgent. These messages include the debug information and communication details between the ADLAgent and the Deployment Server. This port connects to the Remote Client.
Client/Server File Transfer Port
Open the Copy File To dialog of the Copy File task and click Advanced. Select the Copy files using Deployment Server option. The files will be copied using this port.

System Requirements

Processors
ARM MIP SHMb contiguous 16 Mb

Disk space RAM

Operating systems: Pocket PC
Install from a cradle or cable. See Install a Pocket PC Agent from the Deployment Console on page 492 to install to a handheld computer in the cradle attached to a host computer. Download CAB files with ActiveSync. See Install Pocket PC Agent from the Host Computer on page 493 to install the handheld by running or copying the Deployment agent install file or the Deployment Client CAB files over the network. Install directly to the handheld. See Install Pocket PC Client on the Handheld on page 493 to install only
the Deployment Client from CAB files on the handheld computer.
The Deployment Agent for Pocket PC (PA) runs on the host computer, which itself is a managed computer running the Deployment Agent (DS). The Deployment Agent for Pocket PC automatically installs the Deployment Client for Pocket PC (PC). You can also install the Deployment Client for Pocket PC directly to the handheld by installing the required CAB files.
Install a Pocket PC Agent from the Deployment Console
When installing a handheld running the Pocket PC operating system, you can attach to a host computer and run Microsoft ActiveSync software to synchronize data between the host computer and the handheld. Deployment Solution lets you install Deployment Agents on both the host computer and the handheld to communicate with Deployment Server as a managed computer. The Altiris Pocket PC Agent is software that runs on the host computer. This agent communicates through the handhelds cradle to the Pocket PC Client running on the handheld. The Pocket PC Agent also automatically installs Pocket PC Client on the handheld. The Pocket PC Agent provides communication between the Pocket PC Client on the handheld and the Deployment Server. ActiveSync is required for the Pocket PC Agent because it provides the IP stack the Pocket PC Agent uses to communicate with the handheld. The Pocket PC Agent monitors the connect and disconnect jobs sent to the handheld. If the Pocket PC Client on the handheld is present but not started, then the agent will start it. The Pocket PC Agent also acts as a relay agent to transfer data from the Pocket PC Client on the handheld to the Deployment Server. From a Deployment console, you can schedule and run a Sample job to install the Pocket PC Agent on a host computer. Ensure that the handheld is connected to the host computer and seated in the cradle. You must also download Microsoft ActiveSync and install it (this is free software available on the Microsoft web site) on the host computer. Then synchronize the host computer with the handheld. To install from a Deployment console Use Deployment Solution to find computers with ActiveSync and run deployment jobs to automatically copy the necessary files and install the Deployment PPC Agent and PPC Client. 1 From a Deployment console, in the Jobs pane open the Samples > Pocket PC folder. 2 Click the Install Altiris Pocket PC job and then select the Active Sync computer condition in the Condition box in the Details pane. 3 Drag the Install Altiris Pocket PC job to the host computer. If you are using a Web console, then assign using web features. 4 Schedule the job. After the Pocket PC Agent has installed, the Altiris Pocket PC Agent icon will appear in the system tray of the host computer. When the Deployment Agent is initialized, it will connect to the handheld. The agent will check if the Altiris Pocket PC Client is installed on the handheld. If not, the agent will automatically install it.

When the Pocket PC Client is installed on the handheld, the Deployment Client icon will appear in the system tray of the handheld and the client details screen appears.
Note: For ease of use, the Pocket PC Client will first try to connect to a Pocket PC Agent. If it fails, the
Pocket PC Client will try to connect directly to the Deployment Server.
5 Click OK. The handheld appears in the Deployment Console as a unique computer displaying the handhelds name. See Installing Deployment Agent for PocketPC on page 491.
Install Pocket PC Agent from the Host Computer
From the host computer, you can install the Pocket PC Agent by running the ppcagent.exe installation file on the host computer. After installing the Pocket PC Agent, it will automatically install the Pocket PC Client when the computers synchronize. This is the fastest and easiest way to install both agents on the host and handheld computers.
Note: After you have installed the Altiris Pocket PC Agent on a host computer, the PPCAgent.exe file can be executed from the C:\Altiris\PPCAgent directory (or the directory where you installed Pocket PC Agent if you chose a directory different from the default). This lets you access the features of this program even though the icon has been hidden.
In addition, if you are using ActiveSync 3.5 or a later version, you can also log on to the Deployment Share in the Deployment Server > Pocket PC Client folder and copy the correct CAB file for the handheld (based on type of processor) to the host computer. You can then copy the CAB files directly to the handheld using the Explore feature in ActiveSync. To install Pocket PC Client directly with ActiveSync 1 Copy the CAB file to the host computer with ActiveSync (or to a share where you can copy the file from). 2 Connect your device to your desktop computer using a cradle or cable. 3 In ActiveSync, click Explore. Windows Explorer runs the Mobile Device window for your device. 4 In Windows Explorer, browse to the CAB file you want to copy. 5 Right-click the file and click Copy. 6 Place the cursor in the desired folder for your device, right-click, and click Paste. 7 From the device, tap Start > Programs > File Explorer. Browse for the CAB file and tap the file to execute it. When the Pocket PC Client is installed on the handheld, the Deployment Agent icon appears in the handhelds system tray.
Note: If using ActiveSync 3.5, the Pocket PC Agent is not required after the Pocket PC Client is installed.
However, the Pocket PC Agent can still be useful for installing the Pocket PC Client onto the handheld, loading the client, and managing client settings. See Installing Deployment Agent for PocketPC on page 491.
Install Pocket PC Client on the Handheld