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 following are some new features in this release of Deployment Solution for Dell Servers:
Altiris® Deployment Solution™ software provides the infrastructure and core functionality used by Deployment Solution for Dell servers. Before using this product, you should be familiar with the functionality and requirements of Deployment Solution.
This release provides support for the servers included in version 2.3 of the Dell OpenManage Deployment Toolkit (DTK).
Install files are copied from your installation disks to a file share to automate scripted installations. During initial configuration, you are prompted to provide the installation files for each operating system you want to deploy using scripted installations.
Drivers for each of your Dell server models can be located and copied automaticaly from your Dell Server Assistant CDs. This eliminates the need to manually collect and provide the correct drivers to perform scripted installations.
During initial configuration, you are prompted for the Dell Server Assistant CDs that support your systems (supported systems are listed on the front of each disk). If you do not have these disks available, images can be downloaded from ftp://ftp.dell.com/sysman/.
Jobs are provided to perform scripted installations of the following operating systems:
You can download released versions of Altiris products from http://www.altiris.com/Download.aspx.
You can download beta versions of Altiris products from http://beta.altiris.com.
Complete installation instructions are contained in the Deployment Solution for Dell Servers 3.0 documentation, available at http://www.altiris.com/support/documentation.
To upgrade, perform a standard installation as outlined in the Deployment Solution for Dell Servers 3.0 documentation, available at http://www.altiris.com/support/documentation.
Existing jobs are not deleted to preserve settings, but these jobs are not usable without modification. Previous jobs refer to the "Dell" file-system folder, which has been renamed to "Dell_prev". The simplest way to use the old jobs, if it were necessary, would be to temporarily rename the new Dell folder to something like "Dell_new" and rename the "Dell_prev" folder to "Dell" while you run an old job. After running the old job, change the folder names back so that the new jobs refer to the proper "Dell" folder. modification.
Performing an upgrade has the following effects:
Deployment Console jobs-folder:
The jobs from the previous version should still appear in the Deployment Console in the folder named according to the version (e.g. "Deployment Solution for Dell Servers v2.0 SP1 Linux, etc."). The new jobs in the Deployment Console will be in a separate folder named according to the version and pre-boot environment (e.g. "Deployment Solution for Dell Servers v3.0 Linux").
Deployment Share file-system folder:
The Deployment Share is usually located in the file system in "C:\Program Files\Altiris\eXpress\Deployment Server\". The old "Dell" file-system folder in the Deployment Share will have been renamed to "Dell_prev" (or to something like "Dell_prev1" if a "Dell_prev" folder already existed). A new file-system folder named "Dell" containing the version 3.0 files will have been created in the Deployment Share.
Deployment Console tools menu:
The tools menu in the Deployment Console is updated to refer to the new version 3.0 items, including the new Configuration Utility. The previous version's configuration utility would be accessible in the "Dell_prev" folder, however, the old configuration utility may not be useable (see the note below).
|How do I update the utility partition image?||36594|
|How do I change the network path of the OS source files for Linux installations?||36595|
|What files are required to be on the DS server for Linux installations?||36596|
|Close button in the Job Builder sometimes needs to be clicked twice to get the Job Builder to close||36597|
|Installation of DS for Dell fails on certain installations of Windows 2000 AS SP4||36598|
|Editing user modification sections in Linux Gather System Information jobs have no effect||36601|
|Scripted installations of Windows Server 2003 R2 sometimes does not install the R2 disk||36602|
|DRAC power discovery occassionaly 'discovers' indefinitely||36604|
|Power discovery occassionaly ends prematurely||36605|
|Error occurs when creating WinPE preboot image under Windows 2000 Sp4||36633|
|What are the differences between blades and regular servers as far as dynamic RAID configuration is concerned?||36636|
|OS source files URL is blank after adding support for Linux OS||36646|
|Canceling during copy of OS Source files may prevent creation of new OS Configuration with the same name||36696|
|OMSA file name in aw001_win_install_omsa.bat and ar001_rh_install_omsa.sh is incorrect||36836|
|Bare Metal to OS unable to locate unattend.txt or ks.cfg file when OS Configuration contains a leading or trailing space.||38999|
|Dell 1955 blades do not appear in the physical device view of the Deployment Console||38083|
|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|
|Supported versions of Red Hat Enterprise Linux on 9g servers.||26200|
|What RAID controllers are supported only by the Linux DTK.||26204|
|Configure RAID job fails when trying to delete a virtual disk on a system shortly after it was created||26207|
|Some older versions of Windows 2000 have limitations on the length of the OemPnpDriversPath line in the unattend.txt file.||26214|
|Configure System job (WinPE or Linux) returns error 134, "An invalid line was found in the input file"||30751|
|Dell tools don't function properly in WinPE, syscfg produces no output when Altiris WinPE installer is used.||31309|
|Creating a virtual disk with more than 12 disks fails in WinPE on some controllers||36576|
|Dell DTK doesn't support the PE1550, PE2500, or PE2550, but they are listed in the Configuration Utility as supported||36577|
|Blue screen during scripted install of Windows Server 2003 on 1655, 1750, or 1855 server||36651|
|Error: "The system cannot find the file specified" when running DS for Dell jobs||36656|
|Error: "An invalid line was found in the input file" when using a configuration file on mulitple systems||36678|
|Out-of-band power control doesn't work with Dell 1855 Blades (BMC).||37605|
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.