Altiris® Recovery Solution™ 6.2 SP2 Release Notes

Article:DOC1374  |  Created: 2007-01-24  |  Updated: 2009-02-12  |  Article URL
Article Type


What do I need to know about the release of Altiris® Recovery Solution™ 6.2 SP2?


Altiris® Recovery Solution™ 6.2 SP2

Release Notes

Installation and Upgrade

New Features in Recovery Solution 6.2 SP2

Fixes in this Release

Known Issues in this Release

Additional Documentation

Document History

Apache* Software Notice

The Apache Software License, Version 1.1
Copyright © 1999-2004 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: 
    "This product includes software developed by the Apache Software Foundation ("
    Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.
  4. The names "Xerces" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact
  5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc.,  For more information on the Apache Software Foundation, please see <>.

Installation and Upgrade

To support Microsoft Windows Vista, Recovery Solution 6.2 SP2 must be installed on the Altiris® Notification Server™ 6.0 SP3 R4 platform. For details, see article 27859, Release Notes for Altiris Notification Server 6.0 SP3 R4.

Where to Download Recovery Solution 6.2 SP2

Recovery Solution 6.2 SP2 can be downloaded from to install for the first time or upgrade from previous versions. 

Upgrade Steps

  1. Upgrading from a 6.1 Version or Later

    Upgrading from a previous 6.1 or 6.2 version requires the following steps:
    • Installing Recovery Solution 6.2 SP2 Program Files
    • Upgrading Existing Recovery Solution Servers and Clusters

      For specific instructions, see the Recovery Solution Reference Guide.
  2. Upgrading from a version earlier than 6.1

    Upgrading from versions earlier than 6.1 directly to 6.2 SP2 is not supported.

    You will need to upgrade to version 6.1 or later first and then upgrade to 6.2 SP2. Before upgrading Recovery Solution, you must upgrade the Altiris® Notification Server™ component to version 6.0. You cannot upgrade to a 6.x version for Recovery Solution on Notification Server 5.5.

    For specific instructions, see the Recovery Solution Reference Guide.


After you upgrade the Recovery Agent on a client computer, previous snapshots are not shown in the Rollback dialog (on the server UI) unless you select the Show critical snapshots and snapshots from previous RS Agent installations check box. This will not display previous snapshots on the client’s Rollback dialog. For more information, see the Perform a Rollback topic in the Recovery Solution Reference Guide.

Legacy operating systems Windows 95, 98 (applies to original release only, Windows 98 Second Edition is still supported), and NT4 are no longer supported as server-based Recovery Agent platforms in Recovery Solution 6.2 SP2.

Upgrade Issues

Windows 98 Unable to Upgrade

After upgrading a server, you cannot upgrade the Recovery Solution Agent on computers running Windows 98 or 98SE. Instead, you must uninstall the agent and then reinstall it using the same account.

You can use policies to uninstall and reinstall the agent on Windows 98 computers by doing the following:

  1. Use the Uninstall RS Agent policy to uninstall the agent using the Windows 98 or 98 SE collection.
  2. Clone the Reinstall RS Agent policy.
  3. In the cloned policy, modify the Win32 program to contain the /comp and /server:<Cluster address> parameters. 

    The command-line will have: /reinstall /silent /comp (without computer name) /server:<Cluster address>

  4. Run the policy. This will reinstall the agent with the existing account. Note: The target computer must be restarted to complete the installation.

    New Features in this Release

New Features in Recovery Solution 6.2 SP2

 Feature Description

1. Microsoft Windows Vista 32-Bit and 64-Bit Edition) support

Recovery Agent software can now be installed and run on Windows Vista operating system 32-Bit and 64-Bit versions.

Note: To support Microsoft Windows Vista, Recovery Solution 6.2 SP2 must be installed on the Altiris® Notification Server™ 6.0 SP3 R4 platform. For details, see article 27859, Release Notes for Altiris Notification Server 6.0 SP3 R4.

2. Support for Microsoft Windows XP Professional x64 Edition and 2003 Server x64

This release of Recovery Solution supports 64-bit versions of Windows XP and 2003 Server operating systems as client platforms. For that, the new Win64 Recovery Agent Package has been created for installation on client computers running 64-bit versions of Windows.

3. New Command-Line Utility ( for Restore Automation

The new utility found in the %Program Files%\Altiris\Recovery Solution\Console\Tools folder on the Notification Server computer lets administrators automate restore from the Recovery Server. You can now perform restore for a specific range of clients, folder and file revisions, file name masks and more, by configuring the utility parameters through the command line as well as specifying them in the XML file. The utility can only run on computers where Recovery Agent is installed.

4. Full System Recovery from USB Media

USB media (for example, flash memory stick and USB hard disk drive) can be used for Full System Recovery on computers which BIOS supports start-up from a USB device and is properly configured to do so. The process of running a Full System Recovery from USB media is virtually the same as the original Full System Recovery from CD/DVD. The preparation of USB media for Full System Recovery requires specific steps to be performed manually by the administrator. For information, see the "Full System Recovery from USB Media" topic in the Recovery Solution Reference Guide.

5. Recovery Agent Rollout lets logged-on users postpone automatic restart

The "Reboot computers automatically" option in the Recovery Agent rollout policies has been renamed to "Reboot computers" and its functionality has been enhanced. Now, when this check box is selected and the Recovery Agent rollout policy runs, the logged-on users at client computers will receive the dialog prompt that lets them choose to postpone the reboot or restart immediately; otherwise, the reboot will occur in 60 seconds by default (countdown timer appears). This enhancement ensures that no open document can be abruptly closed losing unsaved changes when Recovery Agent rollout completes. The clients with no logged-on user will not be affected (reboot will be performed automatically).

6. Additional threshold settings for snapshots

Additional Threshold levels for snapshot throttling threshold of (Do not start snapshot if transfer rate is less than:) such as 3, 5, and 10 Mbit/sec have been added. For information, see article 34757, "Hotfix 13: Additional Threshold levels for snapshot."

    Fixes in this Release

Fixes in Recovery Solution 6.2 SP2

Fixed Issues

Fixes Included in This Release

A number of fixes were created for Recovery Solution since the previous release (6.2 SP1). The following fixes are included in 6.2 SP2:

Recovery Solution 6.2.2332—Hotfix 1

Article 29246, "Lost BLOBs are not processed correctly by the Integrity Check (Hotfix 1)"

Recovery Solution 6.2.2332—Hotfix 2

Article 31403, "Snapshot fails on a computer having large number of disks or partitions (Hotfix 2)"

Recovery Solution 6.2.2332—Hotfix 3

Article 31404, "Full automatic registration does not take place with command-line based reinstall (Hotfix 3)"

Recovery Solution 6.2.2332—Hotfix 4

Article 32726, "Duplicate BLOBs are created in the same storage group"

Recovery Solution 6.2.2332—Hotfix 6

Article 32728, "Setting email address for forwarding Recovery Solution events allows a single e-mail address only"

Recovery Solution 6.2.2332—Hotfix 7

Article 32729, "System variables do not work on Microsoft Windows XP French"

Recovery Solution 6.2.2332—Hotfix 8

Article 32730, "Snapshots on Windows NT computers hang at Open File Manager synchronization"

Recovery Solution 6.2.2332—Hotfix 10

Article 32731, "Snapshots take a long time on folders encrypted by Microsoft EFS"

Recovery Solution 6.2.2332—Hotfix 11

Article 32732, "Recovery Solution Server status unavailable in the Altiris Console"

Recovery Solution 6.2.2332—Hotfix 12

Article 32734, "Recovery Agent could not create the JobQueue COM object"

Recovery Solution 6.2.2332—Hotfix 13

Article 34757, "Additional Threshold levels for snapshot"

Recovery Solution 6.2.2332—Hotfix 14

Article 34758, "AeXVault.exe crash during Storage Locations Synchronization Job"

Recovery Solution 6.2.2332—Hotfix 15

Article 34759, "LR partition creation hangs for HP DC7700P"

Recovery Solution 6.2.2332—Hotfix 17

Article 34760, "Server Space Management Job works incorrectly works with exclude exceptions"

Recovery Solution 6.2.2332—Hotfix 18

Article 34761, "Restored EFS encrypted files are corrupted after Full System Recovery"

Recovery Solution 6.2.2332—Hotfix 19

Article 34169, "Recovery Server Host Manager hangs"

Recovery Solution 6.2.2332—Hotfix 20

Article 34763, "Environment variables are not allowed for partial snapshot"

Recovery Solution 6.2.2332—Hotfix 21

Article 34764, "Scheduled snapshots sometimes do not run from remote client computers"

Recovery Solution 6.2.2332—Hotfix 22

Article 34765, "Recovery Solution Server service receives a shutdown request at Server Space Management job startup"

Recovery Solution 6.2.2332—Hotfix 23 

Article 35008, "Data File Synchronization job completed with errors"

Recovery Solution 6.2.2332—Hotfix 24

Article 35010, "After upgrade to 6.2.2332 the status of the storage is inaccessible"

For more information about all released hotfixes, see article 29505.

Known Issues

Known Issues for Recovery Solution

 Known Issue
Recovery Server Setup does not create a backup device for the database, and does not schedule regular backups of the database.

The installed version of the Altiris Recovery Solution™ from Symantec Implementation Guide does not describe correctly the functionality of the Recovery Server Setup. In the Settings Information > Microsoft SQL Server Settings, the following text is not valid:
"Database Backups
Setup creates a backup device for the database. It also schedules regular backups of the database."

Non-anonymous Proxies are not supported

Recovery Solution Agent communication over proxy is allowed for anonymous proxies only. Non-anonymous proxies are not supported in the current release of Recovery Solution.

Downgrade to an older version is not supported

Installation of an older version of Recovery Solution onto a Notification Server computer that has or had a newer version of Recovery Solution installed is not supported.

Full System Recovery over WAN

The Network Full System Recovery cannot be performed for a protected computer that is outside of the company’s Local Area Network. When client computers reside on the WAN, their Full System Recovery can be performed only using a CD- or a DVD-ROM set that includes all user data.

Performing a Web-based file recovery

When running Web-based file recovery on a load-balanced cluster, you must enter the IP address of a physical Recovery Server in the Recovery Solution Cluster and not the IP address of the Recovery Solution Cluster itself.

Full System Recovery limitations

Full System Recovery cannot be performed on a Windows NT/2000/XP/2003 protected computer that uses disk volume sets, stripe sets, dynamic disks, software RAIDs, and unsupported RAID hardware.

Authentication under currently logged user does not work on Windows NT4/9x working over HTTP/S

Authentication under currently logged on user account does not work for computers using Windows NT4/9x working over HTTP/S; the user will have to enter credentials manually during the Agent registration. The user will also have to re-enter user credentials every time the computer is restarted.

If Recovery Server was upgraded while Notification Server was offline

In case the Recovery Server was upgraded while Notification Server was offline, it will not be treated as upgraded. In cluster settings the server is shown as "upgrade in progress." Many actions (for example, FSR CD creation) fail for the clients installed on the cluster. Uninstall the Recovery Server for which the status was not updated and install it again (without a Notification Server restart).

Cannot use mapped drives for storage locations on Windows 2003

It is not possible to use mapped drives for storage locations if your Recovery Server is installed on a Windows 2003 Server. The workaround is to use a UNC path (\\server\share) instead.

RAID Adapters not supported for Full System Recovery

The following adapter is not supported for Full System Recovery in server-based mode:

  • HP NetRAID-2M
Performing a Full System Recovery Using PXE with Deployment Solution 6.5 SP1

The feature of performing a Full System Recovery does not work on Altiris Deployment Solution 6.5 SP1. Altiris Boot Disk Creator fails on attempt to add files (vdisk.sys and rndm_dr.exe) during PXE boot disk creation. The error message states 'An unhandled win32 exception occurred in bootwiz.exe [12664]...'.  The workaround is to upgrade your Deployment Solution to version 6.8. For information, see article 29163.

Agent re-registration with existing account

Altiris Recovery Agent re-registration with existing account on Recovery Solution clusters with lots of data can take up to 15 minutes. During this time, the Altiris Recovery Agent Registration dialog window will appear with the “Busy” appearance of the mouse pointer.

Some NAS Devices are not supported as Raw storage locations

The following NAS devices, which are Linux based, do not fully support Windows APIs and cannot be used as raw storage locations for Recovery Solution: HP Net App and EMC Celerra.

Known Issues with Microsoft Vista BitLocker

The following issues occur when using BitLocker:

  • In local mode, the local recovery partition is not compatible with BitLocker. If BitLocker is enabled, the creation of the local partition will fail. F11 will not work if BitLocker is enabled.
  • In server-based mode, if BitLocker is enabled, after a Full System Recovery is performed, the drive is no longer encrypted.

See article 35458, "It is impossible to create a Local Recovery Partition if Microsoft Windows Vista's BitLocker drive encryption is turned ON on 'ALL' volumes on the computer."
See article 35459, "It is impossible to create a Local Recovery Partition if Microsoft Windows Vista's BitLocker drive encryption is turned ON on the Operating System volume of the computer."

Known Issues for Both Recovery Solution and Altiris Local Recovery Software

 Known Issue
 "Files in Use" error when upgrading or repairing Recovery Solution Agent on Microsoft Vista 

On a client computer running Vista, if you upgrade, repair, or install over an existing client in interactive mode, you will get an error that states:

"Files in Use—Some files that need to be updated are currently in use."

You can click Ignore and the installation will successfully complete. This message will not display during a new agent installation or if the agent upgrade is performed using silent mode (using /silent command-line parameter).

Locked Client Computers do not automatically reboot after remote agent rollout

When the Recovery Solution Agent is installed on a client computer, the computer must be restarted in order for the agent to be functional. When using the Recovery Solution Agent Rollout policy to deploy the agent remotely, if the computer is in a locked state (from either a Ctrl-Alt-Delete lock or a locked password screen saver), the client computer will not automatically reboot after the agent is installed. The agent will not be functional until the client computer is restarted.

Issues using Recovery Solution with Altiris Software Virtualization Solution (SVS) 

Because of the way that SVS redirects files in Virtual Software Packages, program and data files that are in SVS layers are not backed up in the regular file system. As a result, they are not available for view in the Recovery utilities. However, the redirect files in layers are backed up as part of the SVS files under the C:\fslrdr folder.

For example, if you have Microsoft Office in a SVS layer, and the layer is active, in Windows explorer, you see a folder called C:\Program Files\Microsoft Office. These are actually files that are redirected to C:\fslrdr. When you do a snapshot or recovery, the C:\Program Files\Microsoft Office folder is not recognized.

Encrypted files cannot use RFE on the same but non-encrypted files

Due to encryption keys being user specific, it is not possible to gain the benefits of redundant file elimination (RFE) when comparing two identical files if one is encrypted and the other is not. The issue appears only once a file is decrypted or encrypted. Note that redundant block elimination (RBE) works fine with both encrypted and decrypted files.

Different wallpaper screen appears during system rollback

During a system rollback, a different wallpaper screen, such as the default wallpaper screen, may appear. This is normal and all settings will be restored after the rollback is completed.

Firewall settings not restored on Windows XP

After performing a network settings rollback on Windows XP computers, firewall settings may not be restored. In these cases, firewall settings must be restored manually.

Limited support for Microsoft Cluster

In the current release, files are correctly backed up and can be restored but full-system recovery and rollback are not supported on the clustered server.  You may need to disable or change the Open File Manager (OFM) settings for the snapshot to complete successfully on such servers.

Accelerated snapshots don’t work

If a protected user accelerates the snapshot scheduled for the next day after the scheduled snapshot for the current day has already run, the snapshot will not start, although the “Job was accelerated successfully” message will appear.

Note: Accelerated snapshots will not start only in case they are initiated through Recovery Solution Agent Options on client computers, not through the Recovery Console.

Rollback from Windows XP SP1 or SP2 to Clean Windows XP

Do not perform rollbacks from Windows XP with Service Pack 1 or Service Pack 2 to a “clean” Windows XP as it may cause your computer to become unusable. Use Windows Add/Remove Programs to remove the Service Pack instead, then run the rollback if needed. Rollback from Win XP SP2 to SP1 is possible and supported.

Snapshot excludes with wildcards may not work

If you use wildcards to specify an excluded folder (Example: C:\Folder*) and add exceptions to it, a folder with a matching name and its files will be backed up nevertheless. To work around the problem do not use wildcards to specify excludes with exceptions or do not add exceptions to excludes with wildcards.

Full System Recovery from USB or SATA* CD or DVD Drives is not supported

Local and server-based Full System Recovery is supported only for CD and DVD drives connected to native IDE controllers or controllers set to work in IDE compatibility mode. USB or Serial ATA controllers without IDE compatibility mode are not supported.

Known Issues for Local Recovery

 Known Issue
 Changing System Partition Size or Altiris Partition Size using Vista Causes Recovery Failure

Using Microsoft Vista, you can change the size of a partition without reformatting it. However, changing the partition size of the system drive partition or the drive hosting the Altiris Partition will cause the F11 function to reformat the Altiris partition and cause recovery tasks to fail.

You cannot change the size of the Altiris Partition itself because it is hidden to Windows.

 Recovery Agent Installation on VMware Vista Client

Altiris Partition creation may fail with the "unsupported hardware" error during Local Recovery Agent setup on VMWare Windows Vista computer which system partition occupies the entire disk. This is a current VMware limitation. The workaround is to have, modify, or initially create the Windows partition smaller than the total disk size by ~100 MB (free unused space) before creating the Altiris Partition.

Non-functional “Shutdown” button on the “Hard drive has changed” dialog

The Shutdown button on the Hard drive has changed dialog (which appears if the partition structure has been changed before a Full System Recovery) does not work.

Linux* cannot mount Recovery Partition on the IDE HDD attached to NVidia2 motherboard

After the Local Recovery Agent is installed, any action with the Altiris partition under Linux fails because Linux does not see files on the Altiris partition. This problem is specific for system installed on IDE HDD connected to Abit Socket* A NF7-S, nForce2 chipset motherboard.

Dynamic volumes are not supported

The current release of Local Recovery does not support dynamic disks on protected computers.

No support for TPM security chip

Protected computers using the TPM security* chip are not supported with this release of Recovery Solution.

User logon screen changed to classic Windows style while installing Altiris Local Recovery

When a Windows XP computer is restarted during the installation of Local Recovery, the classic Windows logon screen is displayed even if the Use Welcome Screen (icons) and Use Fast User Switching options are selected. The selected logon screen will be correctly displayed after the installation and first snapshot complete.

Local Recovery drive controller support

During the installation of local recovery if an unsupported device driver is detected the user will receive an installation error indicating that unsupported drivers have been detected.  If these drivers have been loaded as part of an existing factory image and there is not a dependent device in the system, removal of the driver from the Device Manager in Windows should correct the problem and allow installation to occur normally.

Altiris Embedded BootWorks partition compatibility

Local Recovery places the contents of snapshots into a hidden Altiris partition. Altiris® Deployment Solution™ 6.1 and earlier Embedded BootWorks (EBW) partition and the Altiris partition cannot reside simultaneously on the same physical drive.  If you have an EBW partition and you attempt to install and/or create an Altiris partition, the installation will fail with an error message instructing you to remove the EBW partition prior to creating the Altiris partition. If you wish to keep an EBW partition and have computer backup and recovery capabilities, you must upgrade and use Recovery Solution in network mode only.

Note: Deployment Solution 6.5 EBW partitions are supported.

Using third party imaging tools on a computer containing an Altiris partition

If you need to image a computer that has an Altiris partition on its drive, you will need to use Altiris RapiDeploy from Deployment Solution 6.5 Hotfix 2. You cannot successfully image and preserve an Altiris partition using some older versions of RapiDeploy or by using the products of another company.

Issues with dual-boot

Local Recovery requires that the operating system should be installed to the same disk from which the BIOS boots. This especially can be a problem in a dual-boot environment. For Local Recovery to work correctly in a dual-boot environment, it must be installed under an operating system that is installed on the booting disk.

The following USB hard drives are not supported
  • AUDAVI* HTS6505-80GB.
The following RAID adapters are not supported

The following adapters are not supported if a RAID is configured on them (the adapters should work fine without a RAID configuration):

  • NVIDIA* SATA RAID (Compaq xw9300)
  • Promise FastTrak* TX2000
  • Promise FastTrak* TX2200
  • Silicon Image* 3112A RAID
Issues with Intel* 945G Express Chipset

Altiris partition creation fails on a Parallel ATA IDE hard disk drive attached to Intel® 945G Express Chipset with Standard ATA\ATAPI Dual Channel controller.

System Restore doesn't work when DISK0 is a removable drive

If an Altiris partition was created on a removable hard disk drive (FireWire or USB) that is set as Disk0 in a computer’s BIOS, Full System Recovery (F11) will fail. As a workaround, you can set the removable HDD as Disk1 or Disk2.

Partition corruption message appears during F11 Recovery from USB HDD

The problem may occur during F11 recovery from USB HDD. The following message is displayed: “Agent partition corruption was detected.” The workaround is to select Yes to force the partition check. After computer restart and booting back to Windows the problem should not recur.

BitLocker Drive encryption is not supported 

Local Recovery Agent does not support Microsoft Windows Vista's BitLocker drive encryption.

See article 35458, "It is impossible to create a Local Recovery Partition if Microsoft Windows Vista's BitLocker drive encryption is turned ON on 'ALL' volumes on the computer."
See article 35459, "It is impossible to create a Local Recovery Partition if Microsoft Windows Vista's BitLocker drive encryption is turned ON on the Operating System volume of the computer."

Full Disk Encryption is not Supported

Local Recovery Agent is not compatible with third-party full disk encryption software.

See article 35484, "What are the known compatibility issues for Recovery Solution 6.2 SP2 related to Disk Encryption software?"

URL mentioned in the Reference Guide - does not work: getting HTTP 403 error

As browsing of the folders is no longer available for the mentioned folder exact file paths should be used for the download. For more information, see article 45566

Additional Documentation

Altiris product documentation is available in Microsoft HTML Help* (.chm) and Adobe Acrobat* (.pdf) formats. To view Altiris product documentation in .pdf format, use Adobe Acrobat Reader* (available at:

Documentation files are installed in the following directory on the Notification Server computer: C:\Program Files\Altiris\eXpress\Notification Server\NSCap\Help.

The following documentation is provided with Recovery Solution 6.2 SP2:

Recovery Solution Administrator's Guide

You can access documentation from the Altiris Console by clicking the following icons in the upper-right corner of the console:

 Access the contextual online help by clicking the online help icon.
 Access an index of all installed help by clicking the index icon.

Altiris Information Resources

Source What Information it Includes Where to Find it
Altiris Documentation Information about new features, update instructions, and known issues for each release. Includes Altiris formal documentation such as Release Notes, Help, Reference Guides, Best Practice Articles, and Technical Reference Articles.
Altiris Knowledgebase Comprehensive collection of articles, incidents, and issues for Altiris solutions.
Altiris Juice:
an online magazine for Altiris users
Best Practices, tips and tricks, and articles for users of Altiris solutions.
Online Forums Forums for Altiris solutions and suites.

Document History

 Date  Changes
6/14/2007 Document Published on Knowledgebase
3/7/2007 Initial Document Version Created


Legacy ID


Article URL

Terms of use for this information are found in Legal Notices