Release Notes

Deployment Solution 6.5

August 31, 2005

Contents
SECTION 1 OVERVIEW............................................................................................................................ 2
SECTION 2 INSTALLING AND UPGRADING........................................................................................... 2
SECTION 3 NEW FEATURES .................................................................................................................. 6
SECTION 4 KNOWN ISSUES ................................................................................................................. 16

Notice
The content in this document represents the current view of Altiris as of the date of publication. Because Altiris responds continually
to changing market conditions, this document should not be interpreted as a commitment on the part of Altiris. Altiris cannot
guarantee the accuracy of any information presented after the date of publication.
2005 Altiris. All rights reserved.
Altiris, the Altiris logo, BootWorks, Inventory Solution, LabExpert, PC Transplant, RapiDeploy, and RapidInstall are registered
trademarks of Altiris, Inc. in the United States.
Carbon Copy is a registered trademark licensed to Altiris, Inc. in the United States and a trademark of Altiris, Inc. in other countries.
Altiris eXpress, Deployment Server, Deployment Solution, My IT Forum, Notification Server, Vision, Web Reports and other product
names are trademarks of Altiris, Inc. in the United States and other countries.
All other brand names are trademarks or registered trademarks of their respective companies.
Information in this document is subject to change without notice. For the latest documentation, visit our Web site at www.altiris.com.
RNT: D

Section 1 Overview
1.1 Document Purpose
This document outlines the known issues for the Deployment Solution 6.5. It includes locations to
download and install Deployment Solution, and identifies new features and known problems.

1.2 Background
Deployment Solution contains a trademarked imaging, migration, and deployment technology developed
by Altiris, Inc. It includes Windows and web components to deploy and provision all types of computer
devices, including handhelds, notebooks, thin clients, desktops, and servers. Deployment Solution is an
integrated system that provides real-time management and deployment of client and server computers,
combining features to create packages, operate and manage computers, and create predefined jobs with
specific management and deployment tasks.

1.3 Deployment Solution Documentation

Documentation for Deployment Solution is available as help files from the Deployment consoles in
localized languages or as a comprehensive package. Deployment help files and the Deployment Solution
Reference guide (deployment.pdf and deployment.chm) are located in the Deployment Server / Docs
directory or accessed from the Deployment Server Console from the Help menu. Help files for the
Deployment Web Console are located in the Deployment Web Console / DSWeb / Docs directory. To
update help, overwrite the files in these directories. To access the complete Reference Guide as help
from the Deployment Solution Console (in English only), rename deployment.chm to deployment_en.chm
and overwrite the default help file.
To view Altiris product documentation in PDF format, use Adobe Acrobat Reader
(http://www.adobe.com/products/acrobat/readstep2.html).

Section 2 Installing and Upgrading

To install Deployment Solution 6.5 for the first time or to upgrade from a previous version, simply run
Altiris_DeploymentSolutionWin_6_5.exe. This will install or upgrade all Deployment Solution
components. Please back up database first and have license files available.
Altiris recommends that large installations of Deployment Server (over 400 managed computers) disable
the auto-upgrade of the Deployment Agent for Windows (AClient) prior to installing. See Upgrade to
Deployment Solution 6.5 for additional details.

2.1 Installation
2.1.1 Setting Install Options for a Silent Install
Deployment Solution allows you to walk through the Deployment Solution installation wizard to
create an answer file (install.ini) that automatically sets options when running a silent install. To

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 2 OF 24

create the install.ini file, run axinstall i from the command line and walk through the installation
wizard to set desired options for a Simple or Custom install or when using the Add Component
installation task. After completing the installation wizard, an install.ini file will be created
with the selected options in the same folder as axinstall.exe. Use this INI file as an answer file
when running the silent install.
To run a silent install, run axinstall.exe t install.ini to install Deployment Solution
using the selected options. You can create multiple INI files to manage different types of
installations.

2.1.2 Support added for Changing Database Name during Install

Deployment Solution provides an option to specify a custom database name during custom
installation. You can specify any database name other than the default name (eXpress).

2.2 Upgrade to Deployment Solution 6.5

Deployment Solution 6.5 supports upgrading from version 5.6 or later. The basic upgrade process
is as follows:
Step 1: Back up your existing server and database.
Step 2: Collect information about your current environment.
Step 3: Extract and run the installation program to upgrade your Deployment Server.
Step 4: If using PXE, run the installation to upgrade your PXE servers.
Step 5: Upgrade the agent on existing managed computers.
Customers Using the HP ProLiant Essentials Rapid Deployment Pack (RDP):
Use the following link to download and install the HP ProLiant Essentials Rapid Deployment Pack
instead of Deployment Solution 6.5:
http://h18013.www1.hp.com/products/servers/management/rdp/rdp-agreement.html.

Step 1: Backup
Before you upgrade, you should create a backup of your server, license files, and database, in
case you need to restore this configuration at a later point.

Step 2: Collect Information

Record the following information:
IP address of your Deployment Server, including the username and password used by
the Deployment Server services.
IP address of your PXE servers. A listing of PXE servers is contained in C:\Program
Files\Altiris\eXpress\Deployment Server\Default.cfg.
Database name, host, and any necessary credentials to connect to your deployment
database, such as the NT user account or SQL user. If using the Altiris install of MSDE,
the username is set to SA and the password is set to altiris.

Step 3: Upgrade your Deployment Server

On your Deployment Server, run the Deployment Solution installation executable to extract and
launch the Deployment Solution 6.5 installation. During installation, select the option that
RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 3 OF 24

corresponds to your existing configuration and complete the wizard (see DS documentation for a
description of a Simple or Custom installation). It is not necessary to uninstall your previous
version of Deployment Solution before installing a new version.
Keep Your Database
When prompted, select the option to keep your existing database. If you choose to create a new
database, any existing data including managed computers, jobs, and history will be lost.

Step 4: Upgrade your PXE Servers

PXE Server shipped with Deployment Solution 6.5 contains many feature enhancements for
managing multiple PXE servers across the enterprise using global or local PXE images and
configuration settings. Due to architectural changes in 6.5, PXE boot images must be re-created
when upgrading your PXE Servers to Deployment Solution 6.5 from previous versions.
A single PXE server can be upgraded during your Deployment Server upgrade. To upgrade
additional PXE servers, run the Deployment Solution installation program and select Component
Install > Install an additional Altiris PXE Server. This process must be completed for each PXE
server in your environment.
An upgraded PXE server maintains existing MAC filters.
Upgrading PXE When Using Boot Integrity Services
If you are using Boot Integrity Services (BIS) certificates, you must manually remove the existing
BIS certificate from each BIS-enabled computer before upgrading. To remove this certificate,
press F8 to view the PXE menu, then select BIS management. You are then provided the option
to uninstall the BIS certificate.

Step 5: Upgrade the Agent on Managed Computers

By default, all agents are updated automatically when a new version is available. This automatic
process works well in deployments with 400 or fewer managed computers.
If you have more than 400 managed computers, we recommend disabling the automatic update
feature and using a job to control agent updates. This lets you control the upgrade process to
target specific groups of computers to upgrade, and prevents slowdown due to a large number of
clients updating simultaneously.
To Disable Automatic Update and Use a Job to Upgrade Agents:
From the Control Panel on your Deployment Server, select Altiris Express Server > Options.
On the Transport tab, unselect the Automatically Update Agents option. This prevents agents
from updating automatically. To update clients, use the Update Aclient sample job provided in the
DS 6.5 Misc Job folder. We recommend updating approximately 200 managed computers at a
time.
Sample Job to Remotely Install Agents

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 4 OF 24

A sample job has been provided to push out the Deployment Agent for Windows (aclient.exe)
located in Samples > Misc Jobs > Update AClient in the Jobs pane of the Deployment console.

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 5 OF 24

Section 3 New Features

3.1 Automation, Imaging and the Deployment Server Utilities
Altiris Deployment Solution has improved and added many features that can help you manage
automation and imaging on client computers. Previous users of Deployment Solution know
Bootworks as the automation agent. Because Deployment Solution supports more pre-boot
operating system environments with additional automation agents, we now refer to Bootworks as
DOS automation.
This section will help you become familiar with the new features for the Deployment Solution
utilities: Boot Disk Creator, PXE Configuration, RapiDeploy, and Image Explorer.

3.1.1 Support for Linux Automation Pre-boot Environment

Deployment Server supports Red Hat Fedora Linux as a pre-boot environment. BDCgpl.frm
contains the files needed to install Linux as a pre-boot operating system. This file is available for
download at http://www.altiris.com/eval on the DS for Clients or Servers sites.
Using Linux as a pre-boot environment, you can do the following:

Create boot media using Boot Disk Creator

Image client computers
Create boot menu options for PXE servers
Install Linux automation partitions to run deployment jobs that have been assigned
automation tasks

3.1.2 Support for Windows PE (WinPE) Automation Pre-boot Environment

Deployment Server supports Windows Pre-installation Environment (Windows PE) 2005.
Using Windows PE as a pre-boot environment, you can do the following:

Create Windows PE bootable media

Image client computers
Run FIRM in the Windows PE environment
Install Windows PE automation partitions to run deployment jobs

3.1.3 Automation partition compatibility with other products

Deployment Solution now supports an embedded automation partition that can co-exist with the
embedded partition from Altiris Recovery Solution on the same computer. However, you must
have Deployment Solution 6.5 or later and Recovery Solution 6.1 or later to be completely
compatible.

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 6 OF 24

3.1.4 Create boot CD

Boot Disk Creator lets you create ISO images for DOS, Linux, and Windows PE pre-boot
operating system configuration. However, you must provide your own third party CD burning
software. The bootable CD can then be used to manually boot client computers to automation.
You can also directly configure USB devices or floppy drives as boot devices.

3.1.5 PXE Configuration Utility

This utility is newly-designed and provides greater flexibility to do the following tasks:

Centrally manage all PXE Servers across the network. The boot menu options can be either
Shared or Local. By default, PXE Configuration opens in the Shared Configuration mode and
any new boot menu options or property settings you change, will affect all PXE Servers on
the network.
Create boot menu options using Boot Disk Creator from within PXE Configuration. You can
also import configurations Direct from floppy, or select User supplied to add your own files
to the MenuOption<number> folder.
Install DOS, Linux, or Windows PE pre-boot operating system files at any time.
Set the order of boot menu options. When client computers PXE boot, the menu list displays
the boot menu options you created in the order you set.
Select which Shared boot menu option you want to be used as the default boot option on
client computers.

3.1.6 PXE manager

When you perform a Deployment Server Simple or Custom install, if you select Install PXE
Server, the PXE Manager Service will always install to the same computer as the Deployment
Server. PXE Manager synchronizes Local and Shared boot menu options with all PXE Servers on
the network, and communicates with the Deployment Server and the Deployment database. It
also keeps track of the PXE Configuration Utility properties settings for each PXE Server you
have on the network.

3.1.7 PXE BIS integration

Boot Integrity Services (BIS) is easier to implement on client computers. Enable BIS from the
PXE Configuration Utility, and then Install BIS Certificates to any computer or group of computers
from the Deployment Console.

3.1.8 Assign PXE boot menu options to automation tasks in a job

You can create one Deployment job with two tasks, and assign a different boot menu option to
each of the tasks. Example: assign a DOS boot menu option to a Run script task to update the
client computers BIOS, and then assign a Windows PE boot option to a Create disk image task
for imaging.
Only Shared menu options can be assigned to the following automation tasks:
Run script
Create disk image
RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 7 OF 24

Distribute disk image

Scripted OS install
Back up registry
Restore registry

You can also redirect the local PXE boot menu for a job to the shared PXE menu. For details on
shared and local menu options and redirection, see the Deployment Solution 6.5 Reference
Guide.

3.1.9 RapiDeploy performance

You can select which performance option you want to use when imaging client computers. By
default, the Performance field has change from Balanced for size and speed to Optimize for
speed. This new default uses a faster level of data compression than before. You may see a
slight increase in image file size because of the new default compression. Combined with several
other changes, this should increase imaging performance.
Note: The feature change to the RapiDeploy compression setting is to speed up creating images,
not in restoring them. Faster networks make the compression more expensive than the
transmission time of the extra data.

3.1.10 Enhanced status display from RapiDeploy to Deployment Server

This feature lets you view the imaging status for client computers from the Deployment Console
when an imaging job runs. The client computer is passed the parameter, -dsstatus, which returns
the imaging status to the Deployment Console.
Example: When the imaging job begins to run on the client computer, the Deployment Console
will display the status in the following format.
Client computer images
Uploading disk image (as master); Time Remaining: 13:29 (4% complete)
Multicasting images
Downloading disk image (as client); Time Remaining: 6:54 (32% complete)
Downloading disk image (as master); Time Remaining: 6:54 (32% complete)
The percentage displayed on the Deployment Console updates when the console refreshes. The
default console refresh rate is once every 30 seconds. You must also select the display status
option in the Deployment Console in order for the imaging status to be displayed.
Do the following:
1. From the Deployment Console, select Tools > Options.
2. Click the Global tab.
3. Select Display imaging status on console.

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 8 OF 24

3.1.11 HTTP image access

When you create a Deployment job with the tasks Create Image or Distribute Image, you must
enter the path and file name to where the image files are physically located. RapiDeploy now
accepts an HTTP path to save or restore images.
Example: The format for the path name is http://<IP address>/images/<filename.img>. There is
no name resolution for DOS pre-boot environments, so you must always enter a specific IP
address. The images directory is the physical location where images will be stored.
You can create an images virtual directory in IIS, or any physical directory location that users
have access to. The virtual directory properties must have Read and Write selected on the Virtual
Directory tab. Select anonymous access or basic authentication (password is sent in clear text)
on the Directory Security tab. (If using basic authentication prepend user:pwd@ to the URL.) If
you create an image directory in any other location, make sure the security properties for the
directory has Read and Write access selected for the user.

3.1.12 DoD wipe added to the wipe program

The dod parameter has been added to the Wipe disk utility. Previously, when you ran the Wipe
disk, it would wipe data from the hard disk using one pattern and one pass. The dod parameter
lets you enter a number, which is used as a pattern for the first pass of the wipe. The second
pass of the wipe is the complement, or opposite bit pattern of the number used for the first pass.
The third pass of the wipe writes a random bit pattern on the entire hard disk.

3.1.13 Image Explorer enhancements

Image Explorer has been enhanced to provide many features previously only accessible from
RapiDeploy. Image Explorer now provides the following:

Add a file to an image file using command line options.

Extract a file from an image file using command line options.
Create .IMX image index file.
Convert old 4.5 format image file to the new image file format introduced in version 5.6
and used in all subsequent versions.
Convert image file to self-extracting image.
Exclude folders and volumes.
Split images into smaller (or larger) segment files.

3.1.14 Divide images into smaller files

Image Explorer lets you split a single image file into smaller segments of some other size, and
then store the smaller files on CDs. However, you must provide your own third party CD burning
software.
When you split an image, a new image file of the split size is created from the original image,
without causing damage to the source. You can also convert an existing image file of any split
size into another image file of any split size. This enhancement will not work on version 4.5 or
older image files, but you can split image files that were created using the version 5.6 version.

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 9 OF 24

3.2 Deployment Server Console Features (Windows)

3.2.1 Centrally managed task password
Deployment Server administrators can now add or change user passwords for these tasks: Copy
File to, Distribute Software, Run Script, Distribute Personality, and Capture Personality.
Deployment Solution 6.5 gives administrators the ability to centrally manage passwords for jobs
and tasks from the Tools > Options menu.

3.2.2 Tab control on the Schedule Job dialog box

This feature introduces tab control on the Schedule Job dialog box providing details about the Job
Schedule, Selected Computer(s), and Selected Job(s).
The Job Schedule tab is identical to the Job Schedule tab in Deployment Solution 6.1. The
Selected Computer(s) tab displays information about the computers selected for this job,
including group membership and IP addresses. The Selected Job(s) tab displays the scheduled
jobs and the folder to which the jobs belong, as well as buttons for changing the job execution
order.

3.2.3 Maintaining order of jobs

Deployment Solution schedules jobs to run in the order they are selected. When a job folder is
selected from the Jobs pane, folders and jobs are displayed in the Details pane of the
Deployment Console. The job folders, jobs within the folders, and individual jobs will be
scheduled in the order they are selected.

3.2.4 End result return codes

Deployment Solution supports defining and displaying additional information about user-defined
return codes. This displays a clear picture of the status of individual tasks for an assigned job.

3.2.5 Find Next for find computer

You can find computers in the Deployment database by entering the search criteria in the Find
Computer in Database dialog. The search starts at the beginning of the computer list in the
Computers pane of the Deployment Console and highlights the computer name when a match is
found. New with this release, you can now press <F3> to find the next computer that matches the
search criteria until there are no more matching results.

3.2.6 Enhanced status display

Deployment Solution 6.5 provides users with more detailed information for imaging jobs. The
Jobs Details page displays the elapsed time for scheduled jobs and the status field displays
status when the job runs, including any errors.

3.2.7 Copy task

This feature lets you copy and paste single or multiple tasks from one job to another, or within the
same job. After tasks are pasted into the destination job, you can modify the tasks, if needed. The
ability to copy and paste tasks saves time and effort when creating or modifying jobs.

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 10 OF 24

3.2.8 Active Directory support

Deployment Solution 6.5 supports adding groups from the Active Directory, and reading and
using Active Directory syntax for user identifications, for example, user@domain.com. This
support is valid for all the instances where user names and domains are required.
Deployment Solution passes existing user credentialsthat is, the credentials used by the users
to authenticate to NTto the Deployment security mechanism, and does not require reauthentication.
Deployment Solution also authenticates users based on their AD group membership. Deployment
Solution provides the ability to set security assignments directly on AD groups, granting any user
in the specified AD group the assigned rights in Deployment Solution.

3.2.9 Automatically installing DS for each language

Deployment Solution installation selects the language to install based on the language settings of
your Operating System. Currently, the following languages are provided: English, French,
German, Spanish, Japanese, and Simplified Chinese.

3.2.10 Adding new tasks to the existing task lists after cursor position
The Deployment Console introduces a new feature that lets you insert a task after any existing
task within the task list of a Deployment job. This lets you place a task within the list based on
your cursor position without needing to use the Up or Down buttons to correctly position the task.

3.2.11 Resizable task list pane

The Deployment Consoles task pane can be increased or decreased in size by dragging the
bottom pane (horizontal bar) that separates the task list and the scheduled computer list. This
feature lets you view a greater number of tasks in a deployment job without using the scroll bar to
navigate up and down.

3.2.12 Delete history

Delete History allows an administrator, or a user with administrator rights, or users with allow
permission for Delete History, to delete the history of any computer.

3.2.13 Remove inactive computers

Deployment Solution lets you manage inactive client computers by automatically removing
computers that have not communicated with the Deployment Server after a selected period of
time. This feature can be set from the Deployment Console or the Deployment Web Console,
through the Options settings.

3.2.14 Static Routing Configuration

The Advanced option in the Computer Configuration Properties page allows the administrator to
set up static routing information. It also allows you to specify the DNS Suffix Search order and
turning the NetBIOS on or off.

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 11 OF 24

3.2.15 Sleep settings for Deployment Agent for Windows

Deployment Solution provides a configuration parameter that indicates the predetermined amount
of time the Deployment Agent for Windows sleeps after the operating system starts.

3.2.16 Microsoft Sysprep Support

Deployment Solution provides native support for MS Sysprep and allows you to use Sysprep
while creating or distributing a disk image. You can modify the Sysprep settings and include a
customizable answer file as well. You can also enter global values for Sysprep settings using the
Global Options feature.

3.2.17 Installation prompt for Sysprep

During the installation of the Deployment Solution, a prompt appears to insert the appropriate
Microsoft Windows CD and copy the files from the CD to the appropriate area to be used by DS.

3.2.18 Enhanced security for Deployment Agent

The Deployment Solution 6.5 Agent for Windows can use key-based authentication to connect to
a specified Deployment Server. This adds another layer of security to prevent your Windows
agents from connecting to a rogue Deployment Server.

3.2.19 Enhanced Role-based Security

Deployment Console comes with enhanced Role-based Security features. Security permissions
to schedule and move jobs have been introduced in this version.

3.2.20 Deployment Agent Settings

The UI for Deployment Agent settings has been modified to keep it consistent with the
Deployment Console.

3.2.21 Filters
Deployment Solution version 6.5 includes three new filters: Active Computers, Inactive
Computers and Computers with Failed jobs.

3.2.22 Tokens in Configuration Tasks

You can now change the name of a computer based on three new tokens: %NAME% (Display
Name), %NICyMACADDR% (MAC address), and %SERIALNUM% (serial number). This feature
helps when the admin needs to change computer names to be consistent..

3.2.23 RDeployT Options

Deployment Solution 6.5 uses RdeployT as the default imaging executable for Create Disk Image
and Distribute Disk Image tasks. This eliminates issues encountered when using Rdeploy to
image thin client computers.

3.2.24 Reboot in configuration

You can uncheck the box on a configuration task and it will not reboot a computer after the task
completes. This is especially useful for changing the DNS and IP address where a reboot is not
required (Windows 2000 and later).

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 12 OF 24

3.2.25 Extended Run Script Capabilities

Deployment Solution 6.5 extends the Run Script capability to support providing additional
command-line parameters for UNIX and Linux systems.

3.2.26 User-defined Ports

Deployment Solution allows an administrator to specify the ports (up to two) that will be used
when running remote control from the Deployment Console. If the first defined port is unavailable,
the second port is used. You can access this feature in the Tools / Options menu.

3.2.27 History logging for live events

History is now recorded for live events (events launched by right-clicking and selecting from the
context menu).

3.3 Deployment Web Console Features

3.3.1 Copy jobs and jobs folder
The Deployment Web Console allows users who have administrator privileges or have been
granted permissions to copy jobs and job folders to any other root level job folder in the tree view
of the Jobs pane. You can have up to 30 subfolders below the root level folder, but you cannot
copy a job folder to a child level folder.

3.3.2 Importing pre-defined computers

You can now import computer configuration data files to set up new computers in the Deployment
database before they come online.

3.3.3 Use of tokens

The Deployment Web Console allows the use of different Deployment Solution tokens while
specifying the computer name.

3.3.4 Enhanced role-based security management

Role-based security management is now available in the Deployment Web console. This provides
you with rights to deny or allow users to schedule jobs and permissions to move a computer, job,
group, or folder to another group or folders.
A new security permission, Schedule this job, is available in the Object Security dialog box for
the selected job. A user who has been denied this right for the job cannot schedule the job
regardless of other privileges.
A new security permission, Move Object, is available in the Object Security dialog box for the
selected computer, folder, job, or group. A user who has been denied this right cannot move a
computer, folder, job, or a group.
These permissions are also available in the Deployment Server Console (win32).

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 13 OF 24

3.3.5 Set default agent settings

The Deployment Solution web console now allows you to define default agent settings and
distribute these settings to managed computers.

3.4 Linux and UNIX Support

3.4.1 Command-line parameters for run scripts
Using the Run Script task you can now write a complex BASH or PERL scripts and pass in
command-line options when you run the script. This is an addition in both the Deployment
Console and the Deployment Agent.

3.4.2 Software distribution packages

Previously, versions of Linux only supported the Red Hat Package Manager (.rpm) file.
Deployment Solution 6.5 now supports these files types:
.bin a binary file
.gz a compressed file package
.tar a collection of files in a package
The .tar files are similar to a .zip files in Window, but they can also contain configure and
make files. When the agent gets a .tar file it will expand the file, then run the configure file
and then the make file. It will then make the install.
.tgz a compressed collection of files in a package
.bz2 a compression file
.shar is a tar file with a shell script as a package
.deb a debian type package
.pkg a Solaris package

3.4.3 New agent for UNIX

Management agent for Solaris SPARC 8 and 9 provides production management capabilities.

3.4.4 Linux Imaging on X86 64-bit Platforms

Deployment Solution supports imaging and management operations on X86 64-bit platforms
using the 32-bit agent running in compatibility mode.

3.5 Additional Features

3.5.1 Enhanced support for virtual machines
Enhanced support for virtual machines including the following:
A sample OS scripted install for VMware ESX servers, which allows you to quickly and
easily set up and configure a VMware server

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 14 OF 24

New user interface controls provide more granular management of virtual hosts and
guests (similar to blade server management). You can switch back and forth between the
virtual and the managed computer (either host or guest) in the console.

Virtual Server/PC: We are testing and will support running Deployment solution on hosts
and guest for both Virtual Server and Virtual PC.

3.5.2 Wise Packager for Deployment Solution

Wise SetupCapture: DS now ships with a scaled-down version of Wise SetupCapture.

Use this tool on the reference computer to take the before-and-after snapshot to capture
an installation. This tool can be pushed down from the Deployment Server to the
reference computer.

Wise MSI Editor: DS now ships with a scaled down version of Wise MSI Editor. You can
create and edit MSI files and prepare them to be pushed out to managed computers.

RapidInstall: DS will still include RapidInstall in the standard DS install; however, it will
not be accessible from the DS console. It is being phased out, and we are putting our
efforts into Wise technology moving forward.

DS includes a RIP to MSI conversion utility.

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 15 OF 24

Section 4 Known Issues

4.1 Deployment Server
4.1.1 Deployment Agent for Linux not detecting DHCP on SLES 9
Deployment Agent for Linux is not detecting DHCP properly on the SUSE Linux Enterprise Server
(SLES) 9 operating system with these conditions:
If you create a reservation (on a Windows DHCP server) with a never expires, then the DHCP
agent on the Linux box will exit after assigning the address, causing the Deployment Agent for
Linux to misreport the agent as having a static address. Consequently, the Deployment Agent for
Linux will report DHCP assigned addresses as static addresses if the lease time is set to never
expire (which does make the address static if it never changes).

4.1.2 Error when using Distribute Software task and UNC from source
If you choose to use UNC paths and execute directly from the file source with a client that has
already authenticated to that source, then AClient log will show a Windows Error 1326. This is
due to the operating system keeping track of all network shares it has accessed and the users.
As a workaround, change users for authentication from previous jobs or do a reboot to clear the
connection tracking in the OS.

4.1.3 Scripted OS Tasks Require F: Mapped to the Deployment Share

When performing a Scripted OS Installation task, the task fails if the Deployment Share is
mapped to a drive letter other than F:.

4.1.4 Registry tasks require modification

Before performing a registry backup or restore, you must add the Windows path to the advanced
properties of the task.

4.1.5 Solaris Agent does not support multicast server discovery

You must provide the IP address of the Deployment Server during configuration on Solaris
systems.

4.2 Deployment Server Console (Win32)

4.2.1 Using remote DS console slower on Windows XP SP2 and 2003
Because of functional changes in MS Windows XP SP2, a Deployment Server Console (the
Windows console) connecting remotely from another computer (using ODBC connections) to the
Deployment Server will run slower than on MS Windows XP SP1.
From Microsoft article at http://support.microsoft.com/kb/296264/:

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 16 OF 24

By default, opportunistic locking is enabled for server message block (SMB) clients that
run one of the Windows operating systems that is listed at the beginning of this article.
Opportunistic locking allows clients to lock files and locally cache information without the
risk of another user changing the file. This increases performance for many file
operations but may decrease performance in other operations because the server that
grants the opportunistic lock must manage the breaking of that lock when another user
requests access to the file.
On dedicated servers running Windows 2000 Professional, Server, Advanced Server, or
Windows XP Professional, create the following:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
Create the following:
Value Name: EnableOplocks
Data Type: REG_DWORD
Parameter Value: 0 Hex (False)

If your server is not a dedicated server you will also need to create the workstation keys
listed below. On workstations with Windows 2000 Professional or Windows XP
Professional, use this key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters
Create the following:
Value Name: UseLockReadUnlock
Data Type: REG_DWORD
Parameter Value: 0 Hex (Disabled)

Value Name: UseOpportunisticLocking

Data Type: REG_DWORD
Parameter Value: 0 Hex (Disabled)

Value Name: UtilizeNtCaching

Data Type: REG_DWORD
Parameter Value: 0 Hex (Disabled)

Reboot all servers and client computers affected.

4.2.2 IP address displays as 0.0.0.0 on Computers with Two NICs

In some circumstances, if a system has two NICs (onboard and wireless), and both NICs are
enabled, the wireless NIC might not have an IP address if it is not connected to a wireless
network.
If the disconnected wireless card is found first, then the IP address is reported as 0.0.0.0 for the
computer. This is an issue for many notebook computers with wireless enabled but not
configured.

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 17 OF 24

Workaround:
Create and modify the customdata.ini and filter out the wireless adapter.
In the AClient folder on the managed computer, copy dynamic.ini to customdata.ini and edit
FilteredAdapterNameList in the [Filters] section so that it excludes the wireless adapter.

4.2.3 VMware hosts

Computers that run the VMware hosting software (ESX, GSX) require UUIDs in order for the
VMware host association to work properly.

4.3 Deployment Web Console

4.3.1 Error appears when using the Job Wizard on a Domain Controller
If running the Job Wizard from the Deployment Web Console installed on a computer installed as
a Domain Controller, you will receive an error and cannot continue using the wizard. It is
recommended that you do not install Deployment Solution on a computer running as a Domain
Controller.

4.3.2 Multiple Users with same Windows admin logon yet distinct DS rolebased rights get errors
You might receive unexpected results such as blank credentials and unexpected login prompts if
multiple users have the same Windows logon (used by IIS), but use Deployment Solution rolebased security with unique user IDs to grant separate rights and privileges.

4.3.3 Logon tab does not show the correct credentials

After importing an Active Directory group using the Deployment Web Console, log on using an
administrator account from the group. Remove the Admin right from imported group and log on
with a normal user account. Go to the Logon tab and see that the AD user is logged on displaying
incorrect credentials.

4.3.4 User name and password fields are blank although data was input
In rare instances when asked to enter the user name and password, the fields remain blank and
do not show the user name or the ******* for characters entered into the password field. For
example, this might occur when authenticating to modify a configuration to log on to a domain or
to use role-based security.

4.3.5 HTTP imaging tasks cannot be created using the Web Console
These jobs must be created using the Deployment Server Console (win32). After creation, these
jobs can be executed using the Web Console.

4.3.6 Fully-qualified domain name must be provided and the password

must be saved when modifying domain membership
When modifying a managed computers configuration to add or modify domain membership, or
when configuring a computer after deploying an image, you must provide the matching

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 18 OF 24

credentials of either the fully-qualified domain name of your administrator account or the netbios
domain name when prompted.
If adding to an AD domain which is not PRE-Windows 2000 compatible you are prompted to
provide the username and password for the mydomain.com domain. The username you provide
must be mydomain.com/Username.
If you are adding to an NT4 PDC or Active Directory domain which supports netbios calls, you are
prompted to provide the username and password for the mydomain domain. The username you
provide must be mydomain/Username.
Additionally, in order for the operation to succeed, the Save Password checkbox must be
checked on this dialog. The Deployment Server Console (win32) should be used to perform this
operation if you do not want to save the password in the Web Console.

4.4 Altiris Console (on Notification Server)

4.4.1 Importing Packages to DS from NS
In order for a remote Deployment Server to import a Software Package from the Altiris Console
(on Notification Server), the computer with the Notification Server installed must also have a
Deployment Server installed.

4.4.2 Candidate for Deployment Solution unable to download installation

package
When using NS to do a push installation of Deployment Server, and the candidate computer for
DS is in an NS defined site, your package server will not download the install package and the
DS candidate will not download the package directly from your Notification Server.
To work around this, modify the MaxAgentDownloadTryingTimeMins setting in coresettings.config
to enable the DS candidate to download this package directly. By default, this setting is disabled
(set to 0), causing your client computers in sites to never contact your Notification Server for
packages. Set a value for this parameter to 5 or 10 minutes, then go to the NS Agent on your DS
candidate and request a new configuration.
The DS candidate will attempt to download the package from the package server for 5 to 10 min
(or whatever you put for the setting) and then it will go to the Notification Server to download the
package. After the candidate for DS has downloaded the package, re-disable this setting by
setting it back to 0 so only your package servers will download packages directly from the NS.

4.5 Boot Disk Creator (BDC)

4.5.1 Linux and FreeDOS not included in DS installation
The FRM file containing the GPL code for Linux and FreeDOS must be downloaded separately.
Due to GPL licensing issues, this file cannot be included in the DS installer. This file is available
from the Deployment Solution 6.5 download site.
RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 19 OF 24

4.5.2 USB support in BDC is limited

Not all USB flash devices can be properly formatted to become bootable by BDC. On some
systems, a manufacturer supplied USB formatting tool may be required to make a USB flash
drive bootable. After formatting, BDC can be used with the format option turned off to simply copy
the boot files to the USB device.
USB booting must also be supported by the managed computer. Booting Windows PE from a
USB device might be very slow, and might not work on some systems.

4.5.3 - Boot Configurations from prior versions not upgraded

Due to the addition of new pre-boot automation environments and boot media types,
configurations from previous versions of Boot Disk Creator are not be imported into 6.5, and must
be re-created.

4.5.3 Correct DOS NIC driver when using an Intel VM adapter

If using an Intel VM adapter, select the NIC Drivers for Intel Pro100ve-Dell170L driver rather
than the Intel PRO 100 and 100 VM Adapter Family 3/5/03 driver.

4.6 Support for Windows PE

4.6.1 Windows PE automation requires Windows PE 2005 or later and
Windows Server 2003 SP1
Windows PE 2005 is the first version that provides the proper support for the capabilities needed
by Deployment Solution (PXE booting, Ram boot support, etc.). Windows PE 2005 is designed to
support Windows 2003 Server SP1; both are required for setting up Windows PE in DS 6.5.

4.6.2 Obtaining Windows PE

Customers that have an Enterprise Agreement (EA) with Microsoft can obtain a Windows PE site
license from Microsoft. Those who do not have an EA (or similar) agreement with Microsoft will be
able to purchase WinPE for use with Deployment Solution through Altiris. This new SKU is
expected to be available approximately one month after the release of Deployment Solution 6.5.

4.6.3 Adding Mass storage device drivers (such as SCSI disk drivers) for
Windows PE to BDC configurations
BDC does not provide an interface to allow users to install drivers for any mass storage devices
that are not directly supported by Windows PE 2005. These device drivers can be manually
installed by adding the drivers to the proper directory in the Windows PE configuration in Boot
Disk Creator. Instructions are contained in the Deployment Solution 6.5 Reference Guide.

4.6.4 Network connection errors during Windows PE initialization

If you receive network connection errors when Windows PE is initializing, try increasing the
default timeout period. This value is increased by modifying the loginw t 180 parameter located
in the startup.bat file in the Boot Disk Creator configuration. Increase this value to increase the
timeout from 180 seconds if required.

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 20 OF 24

4.6.5 Windows PE becomes unresponsive during boot

If a computer hangs and becomes unresponsive when booting into Windows PE, this might be
due to an incorrect or out-dated NIC driver. Try downloading a newer NIC driver from the
manufacturer, and then use the Have Disk option in the Boot Disk Creator to add the updated
driver to the available Windows NIC driver list.

4.6.6 Possible conflict when mapping to drive F:

With Windows PE, often times there is a conflict when mapping to drive F:, especially when
managing servers. Because of conflicts, the default drive mapping at F: fails and gives an error
device is already in use. Windows PE is able to read NTFS partitions and identify CD-ROM
devices that may lead to mapping conflicts on a mapped F: drive.

4.6.7 DOS install required with Windows PE

To install a Windows PE automation partition, MS-DOS is also required (see 4.8.3).

4.6.8 Error loading Windows PE PXE image

You might receive an error 16 when there is not enough RAM available to load the RamDisk
image for Windows PE. You must have at least 256 RAM available to load the image and we
recommend 384 MB RAM or more.

4.7 Support for Linux

4.7.1 Reinstall the Linux automation partition after updating LILO or GRUB
Linux automation partition must be re-installed after updating LILO or GRUB. If you update the
LILO or GRUB boot loaders on a Linux system, your Linux automation partition must be reinstalled.

4.7.2 Limited features when using Distribute Disk Image for Linux
Because Linux paths are not recognized, in the Distribute Disk Image task you are required to
select Local image store from the initial dialog and enter a path to the Linux image file when
deploying an image. When you click the Advanced button, the Resizing tab will not be available
nor any information about the image that you are deploying (and you cannot change settings).
Also, under the Additional Options tab, the Replace the client's existing Automation
partition from image file [-forcebw] is inactive.

4.7.3 Linux DS automation does not support AMD K6 or K6-2

The Linux automation environment does not support the AMD K6 or K6-2 processors. Use
Windows PE or DOS if you have these processors. This includes the Via Samual, Samual2, and
Nehemia chips

4.7.4 Adding Mass storage device drivers (such as SCSI disk drivers) for
Linux Automation to BDC configurations
Mass Storage drivers can be added to a configuration similar to the way network drivers are
added. On the Linux NIC wizard page in BDC, use the Have Disk button to add mass storage

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 21 OF 24

drivers. After they are added, you can select mass storage drivers along with any additional NIC
drivers you want to use.

4.7.5 Linux Automation on VMware virtual machines using the BusLogic

SCSI controller
The Linux Automation OS is based on Fedora Core 3 (FC3) which uses the 2.6 kernel. By
default, the 2.6 kernel as released by Red Hat does not have the Buslogic driver enabled. The
driver is not enabled because it is not currently maintained.
Altiris recommends that the LSI SCSI logic controller or the IDE controller options be used
because they are currently maintained in the 2.6 kernel. If you have to use the Buslogic driver,
the driver must be enabled in the kernel, though we recommend enabling this only as a last
resort.

4.8 Support for FreeDOS

4.8.1 Support for FreeDOS
FreeDOS is not as capable as MS-DOS in some areas. Some server or newer motherboard
chipsets might not be recognized by FreeDOS, causing a message to be displayed at boot-time.
In some cases, pressing the space bar will continue with no problem, while in others the client
system might hang.
In some circumstances, boot errors or DHCP TCP/IP initialization errors can be avoided by
commenting out the following line in your FreeDOS config.sys file:
REM $$RemUmbPci$$ DEVICE=\DOS\UMBPCI.SYS

4.8.2 Installing FreeDOS Automation on Windows CE limitation

Windows install package in Windows .CE cannot be used to install a FreeDOS automation
partition.

4.8.3 FreeDOS bootable CD cannot install Windows PE or Linux automation

A FreeDOS bootable CD cannot be used to install a Windows PE or Linux automation
partition. Creating a FreeDOS installer CD to install a Windows PE automation partition will not
work because FreeDOS will not operate using hard drive emulationonly floppy 1.44 and floppy
2.88 will work, but both are too small to contain the Windows PE image. Use MS-DOS as an
alternative.

4.9 PXE Server

4.9.1 PXE menu is limited to 23 entries
If more than 23 PXE Menu options are provided, the wrong menu selection is returned to the
server. To prevent this, do not create more than 23 entries on a PXE menu.

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 22 OF 24

4.9.2 PXE menu allows same names for multiple entries

Shared and local entries on the PXE menu are allowed to have the same name. If this occurs,
both entries appear on the menu with no distinction between shared and local options. To prevent
possible confusion, do not create shared and local entries on the PXE menu with the same name.

4.9.3 Do not edit PXE configurations when jobs are in process

When PXEConfig changes a PXE configuration parameter or boot image, all PXE servers are
updated with the new configuration and then restarted. If a PXE server is currently downloading
a boot image to one or more clients, this restart interrupts the download and could leave the
clients in an unmanageable state, requiring them to be manually rebooted. To avoid this problem,
do not edit PXE configurations while jobs are in process.

4.10 RapiDeploy
4.10.1 Capturing an image of a computer with key-based authentication
enabled
After capturing an image of a computer with key-based authentication enabled on the client, you
must re-enable key-based authentication on the computer where you captured the image. Keybased authentication will be enabled on any computers deployed using this image.

4.10.2 HTTP imaging in DOS does not support DNS names

When performing HTTP imaging operations using DOS, the host must be specified by IP
address, not DNS name.

4.10.3 HTTP image multicast might fail if computers do not connect

HTTP imaging might fail when multicasting to several managed computers and not all the
computers connect to the multicast session. As a workaround, try shortening the RapiDeploy
auto-negotiation timeout parameter (-w switch), or increase the connection timeout on your web
server.

4.11 Virtual Bays

4.11.1 Fujitsu Siemens Virtual Bays created prior to running the FSC
Discovery tool will not work properly
Run the FSC discovery tool before you create virtual bays.

4.11.2 Fujitsu Siemens Virtual Bays cannot be created in the Web Console
Use the Deployment Server Console (win32) to create virtual bays.

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 23 OF 24

4.12 Localization
4.12.1 Unable to enter Chinese and Japanese characters in text boxes
In some instances, you cannot enter double-byte characters in the text box provided by
Deployment Solution. This includes the Chat feature in the Deployment Console and the Enter
Console Information feature in the Deployment Agent text box. As a workaround, you can cut
and paste double-byte characters into these fields.

4.12.2 Spanish and Simplified Chinese help files

These help files were not available at the time of shipping, but will be posted to the
documentation site on Altiris.com when available. Overwrite the current English-only placeholder
documents with the updated versions.

RELEASE NOTES

DEPLOYMENT SOLUTION 6.5

PAGE 24 OF 24