Build number: 375
Deployment Solution software helps reduce the cost of deploying and managing servers, desktops, notebooks, and thin clients from a centralized location in your environment. It's an easy-to-use, automated deployment solution that offers OS deployment, configuration, computer personality migration, and software deployment across different hardware platforms and OS types.
In SP2, we have rolled up all of the previous hotfixes and the maintenance pack for 6.9 SP1 as well as included some additional fixes.
For information about Deployment Solution 6.9 SP1, see Knowledge Base article 42696.
Deployment Solution is part of the following suites:
The following are new features of this release:
|Fixes||See Fixed Issues in this Release|
|DAgent icon can now be hidden||You can now hide the DAgent icon in the system tray of the managed computer.|
|DAgent properties can now be password protected||You can now limit users on the managed computer to access the Admin properties only if they enter the set password.|
|DeployAnywhere Update build 2166||(New for SP1 and SP2) Build 2166 DeployAnywhere includes the following changes (compared to its original release in DS 6.9):
- Faster and smaller in size.
- Addresses issues with retargeting between Intel and AMD based CPUs.
- Can specify the full qualified path to where DA log files are written with the /logPath switch.
- Prepends the ID to the log file name with the /logID switch.
- Identifies Windows 2008 as a valid OS.
To update your system with the new build, download the new build from the link. Rename the ghdplyaw32.EXE file on your system to ghdplyaw32.old. Now copy the new file into the same folder as the one you just renamed.
For a list of valid switches for DeployAnywhere, click here.
Also see ghdplyaw32.exe
For more information, you can use the following resources:
|Documentation library||Links to the Deployment Solution Reference Guide, Ghost Imaging Foundation User's Guide, and other documentation.
Note: The latest Deployment Solution Reference Guide is from 6.9 SP1. Any future documentation updates will be posted to this Documentation library.
|Articles, incidents, and issues about this product.|
Symantec Connect (formerly Altiris Juice)
|An online magazine that contains best practices, tips, tricks, and articles for users of this product.|
|Forums for users of this product.|
Deployment Solution can be obtained from http://www.symantec.com/business/products/allproducts.jsp. Deployment Solution 6.9 SP2 is a full product installation and can be upgraded from Deployment Solution 6.8 or 6.9 versions. After installation, be sure to apply all available Hotfixes for this Release.
For a list of supported platforms in this release, see Deployment Solution 6.9 supported platforms and system requirements.
The installation process for Deployment Solution 6.9 SP2 is the same as it was for Deployment Solution 6.9, 6.9 SP1, and 6.8. For detailed instructions, including the minimum rights for the OS and SQL, please see the Deployment Solution 6.8 installation Guide. If you are installing through the Notification Server Web console it is recommended that you apply the Microsoft hotfix link in KB 45832.
When you are performing an upgrade or installing another Deployment Solution version, ensure that you don't have a remote console running. The remote console must be shut down before you try to upgrade or reinstall the Deployment Solution software.
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, SP2 and DS 6.9, 6.9 SP1
Upgrading from Deployment Solution 6.8 (Disable AutoUpgrade due to KB 33129).
Deployment Solution lets you walk through the Deployment Solution installation wizard to create an answer file (install.ini) that automatically sets options when running a silent install. For details on this process, see article 22602, "Can Deployment Solution be installed silently?"
The following are issues that are fixed in this release. For additional information regarding an issue, click the Article ID link.
|Windows Vista Agent Client Tray Icon unable to be hidden||40747|
|Unable to password protect Dagent properties from users||46386|
|Capturing an image from the WES image 6703 on the Quattro/gt7720, runs sidgen after and then looses desktop access.||46387|
|DSconsole - iLo functionality is missing when target is booted to Linux/LinuxPE||46391|
|Nonstandard exit codes are not being evaluated correctly||41665|
|Return codes continue or stop based on result instead of response||45158|
|When "Allow user to run immediately" is unchecked they are unable to even schedule a job.||44809|
|IBM Bladecenter Enclosure Information improperly reported by DAgent||46400|
|Getting "No License Slots Available" when a client drops its connection to the DS server and attempts to reconnect||46401|
|AXComp requires user input when a MAC or ComputerName already exists.||45017|
|Computers imported from .csv file fail to configure WINS/DNS on second NIC||45459|
|Dagent crashes after users have logged in 64 times||45458|
|Distribute software jobs with the option "Copy directly from file source then execute" fail to install the package||23887|
|DAgent doesn't update logged in user on Vista when the logged in user state changes||46403|
|AClient JPN, FRN, DEU, and CHS localization issue.||44291|
|MMB S3 Bladeservers not listed in Deployment Solution console||44804|
|DNS settings are not reflected on the console using a programmatically created Reconfigure job||44455|
|Authentication failing using ASDK methods like DeleteComputer() after installing DS 6.9 SP1||44253|
|''Task_Return_Codes_Table'' dataset is ignored in API calls||41438|
|CreateJob error in Administrator SDK 1.4, "Error Value cannot be null" when job have Condition set||40878|
|"Value cannot be null..." when DS security is disabled and code does not include DSCredentialsHeaderValue.||44650|
|Method failed. Exception: Permission Denied: Deployment Server Role-Based Security is enabled.||44649|
|Boot Disk Creator unable to add drivers to WinPE using the Have Disk button||44108|
|Copy File task using UNC path fails with "The network path was not found."||44031|
|DAgent does not retain WINS IP address after post config||44811|
|Duplicate SPN error when user tries to login to the machine with domain user||44807|
|DAgent in WinPE occasionally fails to connect to Deployment Server||44898|
|DAgent can hang if an exception is thrown during startup||44899|
|Exception may be thrown in Axengine if the Web Console is installed||44109|
|Cannot schedule jobs using Active Directory group authentication.||44235|
|Error "##wc_last_effective_rights" is displayed when multiple consoles are open||44220|
|PXE Server fails to send path to pxeboot.bdc when clients boot to WinPE causing ‘Windows failed to start’ error||44281|
|Data Source return results from only one source type||44565|
For information about Deployment Solution 6.9 SP1, see Knowledge Base article 42696.
The following are known issues in this release. For additional information regarding an issue, click the Article ID link.
|Known Issue||Article ID|
2003 or 2008 64-bit computer
To use Linux Automation/boot disk environments with HP dc7900 workstations
To use WinPE as an automation environment with Deployment Solution 6.9 SP1 when it is installed on a Windows 2003 or 2008 64-bit server, you need to use version 2008.1.3.11 or later of the WinPE preboot installers.
DOS preboot on Windows 2008To allow a client computer that is running in DOS preboot automation to connect to a Deployment server that is running on Windows 2008, you must complete some steps first.
Limited remote control functionalityDue to security concerns, DAgent has limited functionality in Remote Control mode. For example, the Send File option (for Windows XP and Windows 2003), Ctrl+Alt+Delete, and Chat options do not work.
Web Console on Windows 2008
Web Console will not work on Windows Server 2008 without IIS 6 compatibility mode and some additional modifications.
IA64 post configuration and Linux prebootIf you try to do post configuration of a Windows 2008 IA64 server after running a Distribute Image job using Linux preboot automation, the post configuration does not behave correctly. Instead, the system reports a winload.efi error. Use WinPE so that BCDedit runs correctly.
Windows CE 6.0 computersIf a Windows CE 6.0 computer is manually shutdown, the status of the client computer in the console might not update to offline.
Distribute Software job doesn't report correct statusThe console returns success when a Distribute Software job fails because it didn't have the necessary credentials.
Installing on Windows 2008The Deployment Solution installation package for Windows needs to run with administrator rights on the Windows 2008 platforms.
Uncompressed WinPE preboot imagesIn some cases, choosing the option in the Boot Disk Creator to create an uncompressed WinPE preboot image produces a preboot image that does not connect to the Deployment server and does not perform jobs.
The default option is to create a compressed WinPE preboot image. You must explicitly select that you want to create an uncompressed WinPE boot image. If you manually changed this option to produce an uncompressed image and if that image boots into WinPE but does not connect or respond to the Deployment server, use the compressed option instead.
Primary Lookup keys for IA64 client computersIf you have IA64 client computers that are connected to your Deployment server, the Primary Lookup Key in the Deployment Solution console must include a MAC Address. IA64 client computers do not properly support the other Primary Lookup Key types.
WinPE PXE configurations during installation or upgradesIt might take longer to do WinPE PXE configurations during installation or during upgrades.
PXE install on Microsoft 2008PXE does not bind to port 4011 on a Windows 2008 server that is running the Microsoft DHCP server service
Post configuration missing on machines imported fromPost configuration fails to configure WINS/DNS information for all NICs beyond the first one from machines imported from .csv.
DAgent does not have support for MAC address filteringDAgent does not have the capability to perform MAC address filtering. This feature is usually used for such purposes as ignoring VPN adapters or other network adapters that you could exclude from being reported with AClient by using the customdata.ini file.
|Post configuration in RH5 with nic bonding fails to configure||46006|
|Deployment Solution jobs are not importing to the correct folder.||45695|
|Application descriptions have changed for inventory.||46291|
|Altiris Agent fails to free resources if a connection is rejected.||46347|
|When creating a freedos configuration in the bootdisk creator, the create partition installer feature will be grayed out after the configuration is created.||46591|
|MTFTP service crashes after being overloaded by requests||46609|
|When importing computers, get the error "The computer name, 1, matches an existing computer name. Do you want to continue?" (ImportComputers55.xls not updated in samples folder)||46651|
|MAC Filter addresses disappear in PXE Configuration Utility after upgrading from 6.9 SP1 to SP2||47126|
|axcomp.exe crashes when importing computers that don't already exist in Deployment Server||47151|
|The PXE manager service has not connected with the DS server yet||47533|
|Modify Configuration task fails to add a new user account to a client system when run via DAgent||47922|
|Aclient does not repopulate the data after a hardware change on the client computer||48293|
No Hotfixes have been released for this version.
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
This will clear the history and restart the chat.