Deployment Solution for Dell Servers 3.0 SP1 Release Notes
|Article:DOC1544|||||Created: 2007-12-14|||||Updated: 2008-04-24|||||Article URL http://www.symantec.com/docs/DOC1544|
What has changed in Deployment Solution for Dell Servers 3.0 SP1?
Altiris® Deployment Solution™ for Dell Servers 3.0 SP1
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:
- Support for the latest version of the Dell OpenManage Toolkit (version 2.4.1)
- Support for running Linux DUPs in the “Dell DUP Linux” preboot environment.
- RAID configurations now support dedicated hotspares.
- Improved driver support for 10th generation Dell hardware.
- More sample jobs.
- Improved stability.
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.
- Deployment Solution 6.8 SP2. See the Deployment Solution release notes, article 34168. Deployment Solution 6.8 SP2 documentation is available at http://www.altiris.com/support/documentation.
This release provides support for the servers included in version 2.4.1 of the Dell OpenManage Deployment Toolkit (DTK).
Pre-boot Environment (at least one 32-bit pre-boot environment is required)
- Linux and FreeDOS Automation Environment for Deployment Solution 6.8 SP2 (32-bit and 64-bit)
The Linux pre-boot environment is REQUIRED for Deployment Solution for Dell Servers unless you are providing a WinPE pre-boot automation environment. Associated source code is available.
- WinPE 1.6 Automation Environment for Deployment Solution 6.8 SP2 (32-bit and 64-bit)
This pre-boot environment is REQUIRED for Deployment Solution for Dell Servers if you will be using the WinPE pre-OS configuration jobs. WinPE 64-bit is required if you will be doing scripted installs of a 64-bit Windows operating system.
Operating System Installation Files for Scripted Installations
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.
Dell Server Assistant CDs or Dell System Build and Update Utility DVD for Windows Scripted Installations
Drivers for each of your Dell server models can be located and copied automatically from your Dell Server Assistant CDs or Dell System Build and Update Utility DVD. This eliminates the need to manually collect and provide the correct drivers to perform scripted installations.
During initial configuration, you are prompted for these CDs or DVDs that support your systems (supported systems are listed on the front of each disc). If you do not have these discs available, images can be downloaded from ftp://ftp.dell.com/sysman/.
Supported Operating Systems for Scripted Installations
Jobs are provided to perform scripted installations of the following operating systems:
- Windows 2000 Server and 2000 Advanced Server
- Windows Server 2003 (all versions, 32- and 64-bit)
- Red Hat* Enterprise Linux AS 3, 4, and 5 (all versions, 32- and 64-bit)
- Red Hat Enterprise Linux ES 3, 4, and 5 (all versions, 32- and 64-bit)
- SUSE* Linux Enterprise Server 10 (32-bit and 64-bit)
Where to Download
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 SP1 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 SP1 documentation, available at http://www.altiris.com/support/documentation.
Any existing folder named “Dell” within the Deployment Share will be renamed to “Dell_prev” during an upgrade. Any Dell jobs that exist prior to an upgrade will remain intact, but their references to the “Dell” directory in the Deployment Share may need to be redirected to the “Dell_prev” folder to operate properly.
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 v3.0 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 SP1 Linux").
Deployment Share file-system folder:
The Deployment Share is usually located in the file system in "C:\ProgramFiles\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 SP1 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 SP1 items. The previous versions of each utility (Configuration Utility, Job Builder, Configuration Wizard), will reside in their respective “Dell_prev” folder, but we strongly discourage using them, as they may incorrectly interact with the updated database schema.
|How do I update the utility partition image?||36594|
|FreeDOS files left over after a Windows Scripted Install using the Linux preboot||39893|
|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|
|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|
|What are the differences between blades and regular servers as far as dynamic RAID configuration is concerned?||36636|
|Canceling during copy of OS Source files may prevent creation of new OS Configuration with the same name||36696|
|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" loop while trying to run job.||39898|
|Apply 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|
|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|
|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|
|Configuring System Firmware, then DRAC back to back may fail on PowerEdge M600/M605 blades||39994|
Article URL http://www.symantec.com/docs/DOC1544