Altiris® Deployment Solution™ 6.8 SP2 Release Notes
|Article:DOC1422|||||Created: 2007-04-05|||||Updated: 2008-02-22|||||Article URL http://www.symantec.com/docs/DOC1422|
What has changed in the 6.8 SP2 release of Deployment Solution?
Altiris® Deployment Solution™ 6.8 SP2
Altiris Deployment Solution integrates Windows-based Deployment Server systems with the Web-based Altiris solutions and services. A Deployment Server system for a specific site or defined subnet includes Windows applications, tools, and utilities for daily management of computer resources at the local level, and furnishes you with a Deployment Web Console for management from the Web browser.
Deployment Solution can help you to organize computer groups, schedule deployment jobs, distribute disk images, and update packages. Deployment Solution provides a wide array of tools, utilities, and applications to design a system for your specific needs.
For a list, see the Deployment Solution 6.8 Supported Platforms.
Where to Download
The Deployment Solution 6.8 SP2 installation process has not changed from Deployment Solution 6.8 SP1. For instructions, see the Deployment Solution 6.8 installation Guide.
Stop the following services on your Deployment Server before starting the upgrade process: Altiris Deployment Server Data Manager, Altiris Deployment Server DBManagement, Altiris Express Server, Altiris PXE Server, Altiris PXE Manager, Altiris Config Helper, and Altiris PXE MTFTP Server.
Upgrading from Deployment Solution 6.8 SP1
Upgrading from Deployment Solution 6.8 (Disable AutoUpgrade due to KB 33129)
Upgrading from Deployment Solution 6.5 SP1
Upgrading from Deployment Solution 6.5
Upgrading from Deployment Solution 6.1
Upgrading from Deployment Solution 6.8 SP1
Deployment Solution allows you to walk through the Deployment Solution installation wizard to create an answer file (install.ini) which automatically sets options when running a silent install. For details on this process see:
Improvements for this release include the following new features:
Support for Symantec® Ghost® Imaging
Important: Deployment Solution does not include the Ghost executable or a license to use Symantec Ghost. You must provide a copy of the ghost.exe and/or ghost32.exe imaging executable to enable this support.
Customers currently using the Ghost imaging solution have the option of copying the Ghost executable to the Deployment Server to enable Ghost imaging from the Create Disk Image and Distribute Disk Image tasks.
To add support for Symantec Ghost, on the Deployment Share, create a folder called ghost. Copy ghost.exe (for DOS support) and/or ghost32.exe (for WinPE support) to this folder.
Symantec Ghost is now available for selection in the Create Disk Image and Distribute Disk Image tasks. A configuration file called ImageTools.ini, located in the root of your Deployment Share, contains settings you can change to customize the behavior of Ghost. For example, the default command-line in DOS is:
This setting and others can be customized by modifying ImageTools.ini.
Deployment Agent UI on Vista
Detailed DAgent installation instructions- including silent install instructions- can be found in KB 38609.
When installing the Deployment Agent on Vista computers, you now have the option of installing a client-side agent configuration utility. This interface is similar to the configuration interface for the Deployment Agent on other Windows operating systems. To install, select the Control panel applet & UI component option during the DAgent installation.
The configuration utility is launched by selecting Start > Altiris > Deployment Solution > DAgent Configuration.
Wait in Automation Task
To avoid circumstances when a computer might boot into an unmanaged state, a new task, called wait, is provided to cause a computer to remain in automation and wait for instructions.
Thin Client View Enhancements
The Thin Client view has been enhanced with a new get inventory task and a software packages pane.
Remote Desktop Connection for Windows
A new Remote Desktop option has been added to the contextual menu when you right-click a Windows XP* or Vista* computer in the console. This option launches the Windows Remote Desktop utility to enable you to remote control a computer.
Windows XP computers still have the option of using the integrated Remote Control feature of the Deployment Console. Description Article ID New computers added or imported into the console show as managed nodes
Additional new features in this Release
New computers added or imported into the console show as managed nodes
The following table includes known issues currently scheduled to be resolved in this release. For additional information on an issue, use the link in the Article ID column to display a Knowledgebase article.
|Dell 1955 blades do not appear in the physical device view of the Deployment Console||38083|
The AClient Autoupgrade feature improperly sets the delay between the batches of AClient update jobs.
After image restoration, Vista computers might not contact the Deployment Server that sent the job.
AD Groups that are nested inside of other groups don't allow users from the nested group to log into the Deployment Solution Console.
Distribute software tasks with multiple files that reference the current working directory fail.
Web Console cannot add new computers to the domain after a job created in the web console is run on a new computer.
Job status is not being reported correctly when running Power Management task on Thin Clients with Windows XP embedded.
Console closes when trying to delete computers.
NIC with dual IP addresses set in the advanced area is treated by the installation as non-existent.
IP address may display as 0.0.0.0 in the Deployment Solution Console if wireless NIC reports prior to stand NIC which has IP Address.
ADLAgent.conf.custom does not work under default installation path
RILOE Power Control tasks have username disabled.
Importing a CSV list of computers into the Deployment Solution Web Console gives 'Invalid IP address' but works fine in the 32-bit console.
WLogevent.exe gives error after installation of Windows 2003 MUI Pack.
A "new" computer will take the computer record of another if the record in Deployment Solution is lacking a MAC (such as from a CSV Import).
Domain and Static IP information are not applied when scheduling jobs using the Deployment Solution Web Console.
The AXengine will not update PXE to allow automatic boot into the correct automation if Wake on LAN for Inactive computers is disabled or 'retry value' set to '1' minute
Scripted OS Install task does not copy the selected service pack.
On Windows Vista, the Power Control > Log Off option is not available.
Clients are looping on the "Client Record Updated" and not running the next task in DOS automation.
|Axengine doesn't tell PXE to download new automation environment||28714|
|Active directory groups with multi-domain relationships fail to show correct membership when members exist outside of the current domain||36075|
|Cannot store image larger than 8 GB to a Hidden partition even though Hidden partition is large enough to store the file||34612|
|Scripted OS install fails when using WinPE if the eXpress share is not mapped to drive F||33298|
|Scripted OS install ignores custom switches||34244|
|PXE server name doesn't appear on Boot options menu||34245|
|The 6.8.282 WinPE AClient fails to report the model number and BIOS info||33763|
|Deployment Server authentication through the ASDK is not working||33965|
|Error 123, "The filename, directory name, or volume syntax is incorrect"||33949|
|Linux PE receives a ''badness in do_exit at kernel/exit.c'' on reboot with multiple CIFS shares mounted||34859|
|The Deployment Solution 6.8 SP1 Remote Agent installed utility indicates it will install AClient on Vista systems though only the DAgent will work on these systems||33918|
|Error, "Error while executing . . .exceeded (limit 32)," when DS Scrape runs||34734|
|The AClient Autoupgrade feature improperly sets the delay between the batches of AClient update jobs||34301|
|Imported failure return codes are listed under Result as success, when they should be failures||33875|
|AClient is not reporting BIOS version, BIOS release date, and model number of systems with SMBIOS 2.4||34825|
|Unable to locate removable disk device error when creating an ISO with Boot Disk Creator||34832|
|Imported Scripted OS Install jobs lose default path to the associated OS source files that were set on the source Deployment Server||36458|
|Deployment Solution Win32 console slow with AD authentication when there is a large number of nested AD groups||38727|
Dell 1955 blades do not appear in the physical device view of the Deployment Console
|Deployment Solution local privilege escalation vulnerability||38210|
|Deployment Server Win32 console security does not properly pass through authenticate users from AD groups||38209|
|Security Vulnerility in TFTP/MFTP service||38304|
|Token Replacement fails when querying external datasource||39239|
|Deployment Solution console with security enabled may load slowly when accessing Active Directory Global Catalog server||39596|
The following table includes known issues in this release. For additional information on an issue, use the link in the Article ID column to display a Knowledgebase article.
|Use of Rdeploy with the -Raw switch breaks logical partition||39380|
|Installing or upgrading Deployment Solution 6.8 to a named SQL cluster fails||36113|
|PXE server update process never completes in the PXE Configuration utility||39111|
|Thin Clients with older ADLAgent consume a real license.||39038|
|Boot Disk creator will not allow a NIC driver to be added if the NIC''s device ID starts with a ''0''||38968|
|DAgent doesn't join Vista workstation to the domain if Post configuration is part of the rdeploy command line||38477|
|PXE-E53 error Deployment Server 6.8 SP2 with Initial Deployment Disabled||37671|
|'Remove task passwords when exporting or copying jobs' in 'Tools > Options > Global' does not retain settings after being modified.||38570|
|Aclient not reporting inventory when running in WinPE||37611|
|Two dagent icons appear on system tray after Vista machine is rebooted.|
Deployment Agent UI on Vista shows computer as disconnected even the computer is connected.
Remote Agent Installer feature in the Deployment Console does not support Vista computers.
When selecting an MSI package in a Distribute Software task, a 'Dynazip Unzip Error' appears.
Blank information fields are displayed when changing Linux Production Agent settings in the Deployment Console.
'Starts with filter' within the console does not filter correctly.
The axsched utility cannot run jobs against a Deployment Solution server that has security enabled unless the username and password have been used to login to the Win32 Console previously.
Image Explorer shows no or full progress when restoring large files/folders
User information is not captured in history during a remote control.
|DS 6.8 console shuts down when deleting multiple computers||27669|
|HP XW6000 reports a different MAC address to DS with each PXE boot||36035|
|The Deployment Solution Web Console displays error messages in English instead of German||33041|
|Altiris Console Collections in the Deployment Solution Web Console loads slowly or times out||35052|
|DS Import Utility Task in NS running AXImport.exe hangs if not using system account.||36473|
|In the NS console OS type is shown as 'Unknown' for CE.net clients imported via DS Scrape||35847|
|After imaging computers from Linux to Windows the log files path is invalid||32910|
|Console administrators are unable to modify global options to ''remove inactive computers after x days''||36401|
|Deployment Server 6.8 and 6.8 SP1 Remote Agent Installer exits when 'return to wizard button' is pressed||33540|
|The UUID reported by Dell PE 1950/2850 reported on PXE boot and through IPMI call is different than UUID reported by AClient or WMI call.||36179|
|Violation of PRIMARY KEY constraint "PK_HARDWARE"||33432|
|Aclient and Dagent do not restore the network stack properly after a create image job on systems that have NetXtreme II family of network controllers.||36499|
|Selecting change production agent settings to multiple computers with different 'Delay starting jobs...' to error||35251|
|Rdeploy, Showdisk and FIRM not able to read IDE disks in Vmware 6 when using DOS/FreeeDOS automation||35191|
|Autoupdate of DAgent will never complete if DAgent is installed with all available languages.||36679|
|Console administrators are unable to modify global options to ''remove inactive computers after x days''||36401|
|Unable to modify or delete master return codes in DS 6.8 console||36724|
|x64 Dagent doesn't maintain 'Address/Hostname' to DS server after repair of DAgent||36733|
|DAgent is not connecting to another Deployment Server through Multicast option.||36734|
|DAgent synchronizes day and time of vista machine to DS with unchecked synchronize option selected.||36754|
|"Clear Status” is not working on Thin Client View.||36820|
|RCinstaller.exe throws a Windows exception||36887|
|Automation task doesn't run in specified menu option environment if client initial delpoys into different menu option with same OS type and bitness||37435|
|Importing multi-nic computers into DS causes issues if based on MAC Address||36548|
|File name for Create Disk Image job is cleared if the Imaging Tool is selected after typing in the file name with .gho extension.||37442|
|Imaging Status displays invalid time value as imaging process completes||37443|
|Web Console throws exception after doing a refresh on imaging job that has been finished for 30 minutes or more||37474|
|Error -132 or -115 occurs during PXE portion of DS upgrade||37476|
|Logged on user icon doesn't re-appear after connection is lost and then reestablished to the Deployment Server from DAgent.||37478|
|Wait task - Get an error when assigning a job w/ a wait task to a computer running production Linux||37528|
|Deployment Solution 6.8 default WinPE caues DHCP service erro when booting VMWare Server virtual machines||30729|
|Using the Task Password to update an incorrect password does't update the Restoreation Job||37571|
|Automation jobs that branch to a previously completed job reboot the client||37798|
|Rdeploy doesn't deploy the extent sizes of LVM 2 volumes during a Deploy Image task.||37903|
|RDeploy fails with error 'A command line argument was invalid.' when deploying an image||38038|
|When using the web console the sytem jobs folder will not expand in the jobs pane||38750|
The following are some of the limitations in fuctionality with Deplyment Solution 6.8 SP2. For additional information on an issue, use the link in the Article ID column to display a Knowledgebase article.
Description Article ID DAgent does not support Wlogevent Why does Deployment Solution install .exe extract and then nothing happens? Vista scripted answer files used by Deployment Solution should not contain CreatePartition or ModifyPartition Does Deployment solution Support Virtual Center 2.0? Cannot run scripts in automation after deploy image that has Post Config enabled without first rebooting into production LVM images are captured in RAW mode if using non-Linus automation Executing wlogevent in 64-bit WinPE automation gives error 128 Power control functions do not work on older HP Integrity systems Rdeploy may fail when creating an image using HTTP and the "Make an Image Index" (.IMX) option Error: DBInstaller.exe can't create eXpress database on SQL Server 2005 (steps to resolve included)
HP workstations fail to boot into linux pre boot OS
39531 Computers using nVidia nForce NICs cannot connect to the network in WinPE
27246 Assigning SVS Agent Install job to a 64-bit computer fails
27244 Automation partitions are not supported on systems using LVM
27243 WIM images (ImageX) do not restore correctly to a drive with OEM partitions
32055 Embedded partition size limitation on Linux
32056 Assigning SVS agent install job to a Windows Vista computer fails
32057 Multicast is not supported by ImageX
32058 Windows Vista computers must boot into production before image capture
32059 Windows Vista Scripted OS Installations require WinPE
32060 Distributing software to Windows Vista computers
32061 Vista agent is not installed automatically after a Scripted OS installation
32062 "Startup disk is almost full" message appears during MAC image creation in Automation mode
32424 How to push DAgent to Windows Vista using an AD group policy object
33083 DAgent doesn't support Reject connection
36753 "Deny access of DS to Dagent " setting are not applied through change Agent settings
36802 Client computers with too many IP addresses have list truncated
37437 DAgent status field is blank
37444 ''Encrypt session communication with Deployment Server'' not supported with DAgent
37465 Unable to add additional command parameters when deploying using ImageX
37469 ImageX compression is set to 'compress fast'
37470 Unable to Password protect Admin properties from user or Hide client tray icon for Vista clients
37480 Supported Image formats other than .IMG are not displayed in the Resources View (such as .WIM and .GHO/GHS).
37481 IP address for Mac computers doesn't show in the status area of Deployment Console
37482 Filtering jobs in Web Console only work with "All Task Types" filter.
DAgent does not support Wlogevent
Why does Deployment Solution install .exe extract and then nothing happens?
Vista scripted answer files used by Deployment Solution should not contain CreatePartition or ModifyPartition
Does Deployment solution Support Virtual Center 2.0?
Cannot run scripts in automation after deploy image that has Post Config enabled without first rebooting into production
LVM images are captured in RAW mode if using non-Linus automation
Executing wlogevent in 64-bit WinPE automation gives error 128
Power control functions do not work on older HP Integrity systems
Rdeploy may fail when creating an image using HTTP and the "Make an Image Index" (.IMX) option
Error: DBInstaller.exe can't create eXpress database on SQL Server 2005 (steps to resolve included)
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: http://www.adobe.com/products/acrobat/readstep2.html).
Documentation files are installed in the following directory on the Altiris® Deployment Solution™ computer:
C:\Program Files\Altiris\eXpress\Deployment Server\Docs.
The following documentation is provided:
- Altiris® Deployment Solution™ 6.8 SP2 Help (deployment_EN.chm)
- Altiris® Deployment Solution™ 6.8 SP2 Help (deployment_EN.pdf)
- Altiris® Deployment Solution™ 6.8 SP2 Deployment and Migration Guide (deployment_adv.pdf)
Altiris Information Resources
What Information it Includes
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.
Comprehensive collection of articles, incidents, and issues for Altiris solutions.
Best practices, tips and tricks, and articles for users of Altiris solutions.
Forums for Altiris solutions and suites.
|11/30/2007||Numerous Hotfixes have been issued. See 'Post SP2 Hotfixes' section. New Known Issues are at the top of the Known Issues section.|
|12/6/2007||KB 39531 was added to Known Limitations section|
|2/21/2008||KB 39596 was added to Post Hotfix release section|
PuTTY is copyright 1997-2007 Simon Tatham.
Portions copyright Robert de Bath, Joris van Rantwijk, Delian Delchev, Andreas Schultz, Jeroen Massar, Wez Furlong, Nicolas Barry, Justin Bradford, Ben Harris, Malcolm Smith, Ahmad Khalifa, Markus Kuhn, and CORE SDI S.A.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL SIMON TATHAM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
The OpenSSL toolkit is licensed under a Apache-style licence (http://www.apache.org/), it includes cryptographic software written by Eric A. Young (firstname.lastname@example.org) and also includes software written by Tim J. Hudson (email@example.com).
This product includes software written by Jean-loup Gailly and Mark Adler (http://www.zlib.net).
Boost Software License - Version 1.0 - August 17th, 2003
Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:
The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Google Breakpad Crash Dump
Copyright (c) 2006, Google Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- 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.
- Neither the name of Google Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Copyright 1999, 2000 Boris Fomitchev
This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk.
Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice. The Licensee may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions.
The Licensee may distribute original or modified STLport sources, provided that:
- The conditions indicated in the above permission notice are met;
- The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met :
Copyright 1994 Hewlett-Packard Company
Copyright 1996,97 Silicon Graphics Computer Systems, Inc.
Copyright 1997 Moscow Center for SPARC Technology.
Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC Technology makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
Pursuant to the requirements of the GPL, the source for the components and programs found in the BDCGPL*.FRM file (downloaded separately) can be found at: http://www.altiris.com/Products/DeploymentSolution/ds_linux.aspx.
Article URL http://www.symantec.com/docs/DOC1422