Deployment Solution 6.9 SP4

Introduction

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.

Deployment Solution no longer supports Windows 2000. For a list of supported platforms, see Knowledge Base article 51607, which contains a list of the Deployment Solution 6.9 SP4 supported platforms and system requirements.

For the documentation, see the following articles:

• User Guide 52243.
• Reference Guide 52244

For the Release Notes of earlier versions of Deployment Solution 6.9, see the following articles:

• SP3 47793
• SP2 46383
• SP1 42696

Back to top

What's new

The following are new features of DS 6.9 SP4:

• Added support for Mac 10.6.
• Fixed issues (see Fixed issues in this release).

Installation and upgrade

Some HP thin-client models do not require you to purchase licenses of Deployment Solution while others do. Contact your HP representative to get a list of the models in each category.

Where to download

Deployment Solution 6.9 SP4 can be obtained from http://www.symantec.com/business/deployment-solution. Deployment Solution 6.9 SP4 is a full-product installation and can be upgraded from Deployment Solution 6.8 or 6.9 versions.

New installation

The installation process for Deployment Solution 6.9 SP4 is the same as it was for Deployment Solution 6.9 and 6.8. For detailed instructions, including the minimum rights for the OS and SQL, please see the Deployment Solution 6.8 Installation Guide.

Upgrade installations

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
Upgrading from Deployment Solution 6.8 (Disable AutoUpgrade due to KB 33129).

Silent installation

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?".

Back to top

Fixed issues

The following issues were fixed in this release:

Fixed Issue	Article ID
Any domain that has an Organizational Unit cannot be joined with Deployment Solution if the computer has never been on that domain.
AClient displays the manufacturer information for VMware as No Enclosure.
The Modify Configuration task fails when run in automation and using firm to copy the configuration file.
MSI installations fail with error 1603 when running a distribute software job with a different user than the user that logged in.
Win32 console crashes when attempting to remote control four or more clients separately in its own window.
Trying to remote control a computer that has a multi-colored (picture) desktop background displays the colors incorrectly or has lines throughout the display.
Scripts fail to fully execute when run under the Run as user context in a script task.
Organizational Unit not importing with a CSV file when part of a domain.
In the UI, information about an Organizational Unit is not being retained when you add a new computer through the console.
For DAgent, an OS description is not displayed for Hyper-V in the RDP console.
Cannot open the Web console on Windows x64.
Jobs start to assign and then crash, leaving you at the console with no message. This is a dns_suffix table rights issue.
DAgent/AClient properties show the Unknown status for all services that are running on nodes.
Security modifications need to be enabled within child folders.
Silent install is not using the specified SQL account during the installation.
Update password for scheduled (existing) jobs when domain account and passwords change.
File Base Writer Filter on the WES system displays the Error accessing the desktop message.
Windows CE 6.0 stops communicating with the Deployment server when encryption is enabled.
If the FBWF is in use the first time you try and change the computer name, an error occurs.
The time zone is not set correctly during Sysprep Image Capture.
AClient cannot install on FAT32.
For RHEL 5.3, after Image Deploy, ifcfg-ethX file does not have HWADDR variable.
The PXE server responds when the Enable response to requests from computers not in the database option is unchecked.
HP DC 7xxx shows in the database as node_type 4 when it should show as node_type 3.
For DAgent, the OS description is not displayed for Hyper-V in the RDP console.
An unknown exit code returns when you run tasks against Macintosh nodes that are running Darwin ADLagent 2.6-74.
When running a silent install with the /L switch, an invalid switch is received when running AXInstall.
With RDP 6.0.1.13 and Altiris 6.9 SP3 Build 430, there's an intermittent Boot Wizard crash when you create DOS PXE p_w_picpaths with multiple NIC drivers.
A security change made to AClient for another defect breaks AClient.
Include DS ActiveX control vulnerability patch 49568.
Jobs start to assign and then crash to the console with no message displayed.
ADLagent needs to properly handle all failure cases of the reply=ConfigFile message.
Updated the WinPE and Linux drivers.
Fixed denial of service vulnerability with dbmanager.exe.

Back to top

Known issues

The following are known issues in this release:

Known Issue	Article ID
When enabling the Display only computers and jobs the user has rights to manage option, no computers or jobs are seen by users that don't have administrator rights.
A Windows failed to start error displays when Windows 7 p_w_picpaths are deployed in a Linux or DOS preboot environment.
Copy an existing localized system job folder loses localization function.
The Agent Update Jobs string isn't translated in a Chinese console.
The shortcuts view is not listed in the View menu for Japanese.
IBM HS22 blades are not reporting the correct bay information. IBM has a firmware update that solves this issue.

Back to top

Deployment Solution 6.9 SP4 supported platforms and system requirements

Platform	Client	Win32 Console	Web Server	Server	File Server	Database
Windows 7, including Professional, Enterprise, and Ultimate	X
Windows 2008 Core	X
Windows Server 2008, including R2 and SP2	X	X	X*	X	X	X
Windows Server 2003 Standard Edition, including R2 and SP2	X	X	X	X	X	X
Windows Server 2003 Enterprise Edition, including R2 and SP2	X	X	X	X	X	X
Windows Server 2003 Web Edition	X
Windows Server 2003 x64 Edition, including R2 and SP2	X	X		X	X	X
Windows Vista Business, including SP2	X	X
Windows Vista Business N, including SP2	X	X
Windows Vista Enterprise, including SP2	X	X
Windows XP Pro, including SP3	X	X			X
Windows XP Professional x64 Edition, including SP3	X	X
Windows XPe	X
Windows CE 6.0	X
VMWare ESX Server 4.0 (vSphere)	X**
VMWare ESX Server 3.5	X **
VMWare ESX Server 3.0	X **
Mac OS X v10.6	X
Mac OS X v10.5.2 - 10.5.6	X
Mac OS X v10.4.x (PPC/Intel)	X
Mac OS X v10.3.x	X
Red Hat Enterprise Linux 5	X
Red Hat Enterprise Linux 5 x86_64	X
Red Hat Enterprise Linux 5 Itanium†	X
Red Hat Enterprise Linux 4	X
Red Hat Enterprise Linux 4 x86_64	X
Red Hat Enterprise Linux 4 Itanium†	X
SuSE Linux Enterprise Server 11	X
SuSE Linux Enterprise Server 11 x86_64	X
SuSE Linux Enterprise Server 11 Itanium†	X
SuSE Linux Enterprise Server 10	X
SuSE Linux Enterprise Server 10 x86_64	X
SuSE Linux Enterprise Server 10 Itanium†	X
SuSE Linux Enterprise Server 9	X
SuSE Linux Enterprise Server 9 x86_64	X
SuSE Linux Enterprise Server 9 Itanium†	X
Debian Linux Stable	X
Solaris SPARC 8, 9 (production agent only)	X
NetWare 6.5					X

 

*For instructions to install Web Console on Windows Server 2008, see KB 47149

**Support is provided for VMware ESX Server scripted installations.

†Itanium support applies only to HP Integrity systems.

Supported Databases

Host Operating System	SQL Server 2008	SQL Server 2005
Windows Server 2008 x86	X	X
Windows Server 2008 x64	X	X
Windows Server 2003 x86	X	X
Windows Server 2003 x64	X	X

System Requirements

Deployment Agent (AClient, DAgent, and ADLAgent): Deployment Agents require network connectivity and around 5 MB disk space. Other system requirements are the same as the host operating system.

Deployment Server: We recommend running the Deployment Server components on a modern, dedicated server with a 1 GHz or faster processor with 1 GB or more of RAM. At an absolute minimum, this server should have a PIII-compatible 600 MHz or newer processor with 512 MB RAM.

If the database will be hosted on the same computer as your Deployment Server, you need a minimum of 512 MB additional memory, with an additional 1 GB recommended.

Computers hosting additional PXE servers and file shares should meet the requirements of the operating system hosting these components.

Automation Requirements: Microsoft recommends 512 MB of memory for computers booting WinPE. At a minimum, you should have 384 MB to avoid boot error.

Database Requirements

See the system requirements and guidelines for the database version you are running.

Scripted Installations—Supported Automation Operating Systems

	Preboot Environments
Operating System Being Installed	MS DOS	Free DOS	Linux x86	Linux x64	Linux ia64	WinPE 32	WinPE x64	WinPE ia64
Windows 7						X*	X*
Windows 2008 R2							X*	X*
Windows 2008 Server (all supported versions) x86						X*
Windows 2008 Server (all supported versions) x64							X*
Windows 2008 Server (all supported versions) ia64								X*
Windows Server 2003 Enterprise Edition x86	X	X				X
Windows Server 2003 Enterprise Edition x64							X
Windows Server 2003 Enterprise Edition ia64								X
Windows Server 2003 Standard Edition x86	X	X				X
Windows Server 2003 Standard Edition x64							X
Windows Server 2003 Standard Edition ia64								X
Windows Server 2003 Web Edition x86	X	X				X
Windows Server 2003 Web Edition x64							X
Windows Server 2003 Web Edition ia64								X
Windows Vista (all supported versions)						X
Windows Vista (all supported versions) x64							X
Windows XP Professional x86	X	X				X
Windows XP Professional x64							X
Windows XP Professional ia64								X

 

*Windows Server 2008 requires WinPE 2.1

 

转载于:https://blog.51cto.com/altiris/291887