Altiris Deployment Solution offers enhanced Dell server deployment capabilities that dramatically reduce the time and cost of deploying and managing your Dell servers. Deployment Solution uses prebuilt scripts to quickly and easily deploy Dell servers. 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 email servers), and more. All from a central, remote console.
This release includes the following new features:
Deployment Solution software provides the infrastructure and the core functionality that is used by Deployment Solution for Dell Servers. Before using this product, you should be familiar with the functionality and requirements of Deployment Solution.
Deployment Solution for Dell Servers 3.2 MR1 has the following requirements in addition to those of Deployment Solution 6.9 SP4:
This release provides support for the servers that are included in version 3.2.1 of the Dell OpenManage Deployment Toolkit (DTK) in the WinPE environment
This release provides support for the servers that are included in version 3.1 of the Dell OpenManage Deployment Toolkit (DTK) in the Linux environment.
When you install Deployment Solution for Dell Servers, the Configuration Wizard prompts you to provide installation (source) files for each operating system that you select to create automated scripted installation jobs. The files are copied to the deployment share if they are located elsewhere.
Drivers for supported Dell server models can be automatically located and copied from the following Dell OpenManage CDs or DVDs: Dell Server Assistant, Dell Systems Build and Update Utility, or Dell Systems Management Tools and Documentation.
The Configuration Wizard prompts you for the CDs or DVDs for your selected systems (supported systems are listed on the front of each disc). If the discs are not available, ISO images can be downloaded from support.dell.com. Browse to the downloads section for your server model and operating system, and then select the Systems Management category.
DS includes jobs to perform scripted installations of the following operating systems:
Complete installation instructions are contained in the Deployment Solution for Dell Servers 3.2 MR1 documentation, which is available at http://www.altiris.com/support/documentation.
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.
You can download files for the Microsoft WinPE and Linux pre-boot or automation environments from the Deployment Solution for Dell Servers download page. Go to http://www.altiris.com/Download.aspx, and then select the appropriate version of Deployment Solution for Dell Servers.
To upgrade, perform a standard installation as outlined in the Deployment Solution for Dell Servers 3.2 MR1 documentation, which is available at http://www.altiris.com/support/documentation.
During the upgrade, any existing folder that is named “Dell” within the Deployment Share is renamed to “Dell_prev.” Any Dell jobs that exist prior to an upgrade remain intact, but their references to the Dell directory in the Deployment Share might need to be redirected to the Dell_prev folder to operate properly.
Performing an upgrade has the following effects:
The jobs from the previous version should still appear in the Deployment Console. They are located in the folder that is named according to the version. For example, Deployment Solution for Dell Servers v3.2Linux. The new jobs in the Deployment Console are in a separate folder that is named according to the version and pre-boot environment. For example, Deployment Solution for Dell Servers v3.2 MR1 Linux.
The Deployment share is usually located in the C:\ProgramFiles\Altiris\eXpress\Deployment Server\ folder. The old Dell file-system folder in the Deployment Share is renamed to "Dell_prev" (or something like Dell_prev1 if a Dell_prev folder already exists). A new file-system folder named "Dell," which contains the version 3.2 MR1 files, is created in the Deployment Share.
The tools menu in the Deployment Console is updated to refer to the new version 3.2 MR1 items. The previous versions of each utility (Configuration Utility, Job Builder, Configuration Wizard) reside in their respective Dell_prev folders. Using these versions is not supported because they might not interact correctly with the updated database schema.
The following known issues exist in this release:
|Close button in the Job Builder sometimes needs to be clicked twice to get the Job Builder to close.||36597|
|Scripted installations of Windows Server 2003 R2 sometimes do not install the R2 disk.||36602|
|Canceling during copy of OS Source files might prevent creation of new OS Configuration with the same name.||36696|
|Dynamic RAID configuration fails on SAS 6I/R controllers with 3 or more disks.||46821|
The following known limitations and product dependencies exist in this release:
|Problem with Supplemental (.supp) file during install.||40464|
|Clients in automation can't contact the DS server.||26140|
|SUSE Linux scripted installation fails on PowerEdge M600 and PowerEdge M605.||39895|
|"Invalid pre-boot environment detected" message loop while trying to run job.||39898|
|Applying DUP in SUSE Linux production log retrieval fails.||39889|
|Install OMSA Agent Job fails on system running SUSE Linux.||39894|
|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|
|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 Dell servers.||26200|
|RAID controllers that are supported 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|
|Creating a virtual disk with more than 12 disks fails in WinPE on some controllers.||36576|
|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 multiple systems.||36678|
|Out-of-band power control doesn't work with Dell 1855 Blades (BMC).||37605|
|Configuring System Firmware, then DRAC back-to-back might fail on PowerEdge M600/M605 blades.||39994|
|PE1855 displays I/O error message when attempting to install RHEL5.||41028|
|NMI error when launching Linux install when using WinPE.||41027|
|Failure to boot into initial deployment.||40835|
|Dell's 1855 support of 64-bit operating systems.||43345|
|Unknown error while configuring DRAC on PEM905.||44155|
|Production agent fails to install on scripted installs after upgrade from a version prior to 3.1 SP1.||44193|
|Unable to retrieve drivers from Dell OpenManage 5.5 SMTD DVD.||44191|
|Manually retrieving drivers from the Dell SMTD DVD.||44246|
|Configure RAID job hangs while evaluating RAID rules.||44262|
|iDRAC update packages for new Blade Servers downloaded to ESM folder.||46147|
|Unable to use unmodified DRAC configuration file to configure Dell Poweredge Server.||46621|
|Syscfg returns error 134 "An invalid line was found in the input file."||46624|
|Syscfg returns error 20 "Invalid Destination IP address."||46618|
|Unable to PXE boot after upgrading DS for Dell.||46902|
|Operating Systems that are supported on Dell Poweredge Server.||46900|
|Warning: /dev/sda is a read-only filesystem during scripted install of Red Hat.||47658|
|Power Control Discovery doesn't find my 10th Gen Blade Servers.||47665|
|Scripted OS installations of Windows 2008 fail when access to Lifecycle Controller drivers is open.||48481|
|Dell Sample Lifecycle Controller Jobs Report Error 1.||52322|
|"The disk was not found" during scripted OS installation using WinPE.||48778|
For more information on Deployment Solution for Dell Servers, see the following resources:
|Description||Article ID or URL|
|Demo and Getting Started videos for Deployment Solution for Dell Servers 3.2 MR1.||demo videos|
|Updating the utility partition image.||36594|
|Changing the network path of the OS source files for Linux installations.||36595|
|The files that are required to be on the DS server for Linux installations.||36596|
|The differences between blades and regular servers as far as dynamic RAID configuration is concerned.||36636|
|Setting up an nfs, ftp, or http share to host Linux source files for scripted installations.||47536|
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.