This article lists the features in Deployment Solution for Dell Servers 2.0, and describes how to obtain and install version 2.0.
Altiris Deployment Solution offers enhanced Dell* server deployment capability that dramatically reduces the time and cost of deploying and managing your Dell servers. Deployment Solution uses pre-built scripts to quickly and easily deploy Dell servers from bare metal. Deployment jobs enable you to update and configure hardware and system settings (including BIOS, RAID, and DRAC configurations), deploy a Microsoft Windows* or Linux operating system, install applications (databases and e-mail servers), and more—all from a central, remote console.
The Deployment Solution for Dell Servers documentation can be launched from the Deployment Console, Tools > Dell Tools > Help. Additionally, the documentation is available in PDF format at http://www.altiris.com/Support/Documentation.aspx.
Deployment Solution for Dell Servers can be obtained at http://www.altiris.com/Download.aspx.
To upgrade from a previous version:Install Deployment Solution for Dell Servers 2.0 following the instructions above and use the new jobs. The old jobs and files are not deleted in case any modifications were made that need to be preserved, however, the old jobs are not useable (see the note below). An upgrade has the following effects:
| Important: If you have installed Deployment Solution for Dell Servers 2.0 build 68 and are using the DOS pre-boot jobs, then you should obtain Hotfix 1.
If you have Deployment Solution for Dell Servers 2.0 build 69 or later, you DO NOT NEED the hotfix. To determine the version and build number of Deployment Solution for Dell Servers, select Tools > Dell Tools > About Deployment Solution for Dell Servers from the Deployment Server console.
|How do I change the default text editor used by the Dell Configuration Utility?||26141|
|Uninstallation of Deployment Solution for Dell servers 2.0 does not remove all the components that were added when the product was installed.||26169|
|Having multiple instances of the Configuration Utility open simultaneously will only save the changes to the last instance closed.||26206|
|Multiple prompts appear, and the Configuration Utility may be hidden behind other windows during the copy process when adding drivers from the DSA CD.||26212|
|Capturing configuration files takes a long time in Linux automation.||26217|
|Regenerate pre-boot images option in the Configuration Utility only affects the default pre-boot images (129, 130, and 131).||26218|
|DOS is the only supported pre-boot environment when DS for Dell 2.0 in installed with versions of DS 6.5 earlier than SP1.||26221|
|Driver name conflicts with Mass Storage drivers.||26222|
|The steps described in the product guide for SQL Server authentication are not needed.||26225|
|The variables DEFAULT_DRIVER and OS_OEM are not described in the product guide, what are they?||26226|
|When will the Dell Deployment Pack 2.0 support DS 6.8?||29005|
|IPMI power control discovery fails to discover systems that are known to be in the database||35152|
|Installing Deployment Solution using the SQL Server authentication may cause SQL authentication problems when launching the Dell Configuration Utility.||26198|
|Clients in automation can't contact the DS server.||26140|
|Configure firmware (System, DRAC, BMC, or BIOS) jobs return with an error, even when a configuration file that has not been altered is used with the job.||26154|
|Servers booting into WinPE automation take a very long time (15 minutes or more) to download the WinPE image.||26170|
|Scripted installations of Windows 2003 (any flavor) using the Linux preboot environment take a long time and sometimes appear to freeze.||26173|
|Running any job in WinPE that uses the syscfg DTK utility (Get All Configuration, Configure All, Get System Information file, etc) causes the nicselection setting on the DRAC to change on the 9g servers. This happens even when the utility is used to gather information and is not being used to configure anything.||26185|
|Supported versions of Red Hat Enterprise Linux on 9g servers.||26200|
|NIC devices are transposed in Linux automation, wrong MAC address is reported to DS on Dell 9g servers.||26201|
|Where are the settings for the DRAC for 9g servers?||26202|
|What RAID controllers are supported only by the Linux DTK.||26204|
|RAIDCFG in Linux has issues on the following controllers: LSI Logic PERC 4/SC, PERC 4/DC, PERC 4e/DC, Perc 4e/Di, and PERC 4e/Si.||26205|
|Configure RAID job fails when trying to delete a virtual disk on a system shortly after it was created.||26207|
|The DOS Configure RAID job will fail on a blade server if only one drive is in the system.||26209|
|The DOS configure BMC job fails on the 6850.||26210|
|Dell DTK utilities do not work in FreeDOS.||26211|
|In the WinPE pre-boot jobs, the disk identifier may need to be changed for certain machines.||26213|
|Some older versions of Windows 2000 have limitations on the length of the OemPnpDriversPath line in the unattend.txt file.||26214|
|During a scripted install of Windows 2000 or Windows 2003, a dialog may appear at the beginning of the GUI setup.||26215|
|RAIDCFG in the Linux pre-boot environment fails on a PE1655 blade with a segmentation fault.||26216|
|Out of environment space errors when using DS for Dell with DS 6.1.||26219|
|RAIDCFG sometimes returns an error "Virtual disk initialization failed" with return code = 70.||26224|
|DOS jobs containing the line "REM BOOTWORK UNLOAD" in the first task will freeze when run using Initial Deploy.||26227|
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.