Sorry, we can't find that page.
|
[an error occurred while processing this directive]
|
|
|
|
|
RDP 3.80 Release Notes
Article: 2002
Component List
Major Changes
Known Issues
Related Articles
Component List
|
| Component | Version |
|
| Microsoft .NET Framework | 1.1 and 2.0 x86 |
| Microsoft SQL Server Express | 2005 |
| Altiris Deployment Solution | 6.9 |
| WinPE Automation Environment | 2.1 x86 and x64 |
| Linux Automation Environment | 2.6.18.8 x86 and IA64 |
| HP ProLiant Integration Module (EN, JA) | 3.80 |
| SmartStart Scripting Toolkit for WinPE 2.1 x86 | 1.9 |
| SmartStart Scripting Toolkit for Linux | 1.9 |
| Firmware Maintenance CD | 8.00 |
| ProLiant Support Pack for Windows 2003 | 8.00 |
| ProLiant Support Pack for Windows 2008 | 8.00 |
| ProLiant Support Pack for VMware ESX 3.x | 8.00 |
| ProLiant Support Pack for Red Hat EL 4 | 8.00 |
| ProLiant Support Pack for Red Hat EL 5 | 8.00 |
| ProLiant Support Pack for SUSE Linux 10 | 8.00 |
| HP Integrity Integration Module (EN, JA) | 3.80 |
| SmartSetup Scripting Toolkit for WinPE 2.1 | 3.0 |
| SmartSetup Scripting Toolkit for Linux | 3.0 |
| Integrity Support Pack for Windows 2003 | 6.0 |
| Integrity Support Pack for Red Hat EL 4 | 4.08 |
| Integrity Support Pack for Red Hat EL 5 | 4.08 |
| Integrity Support Pack for SUSE Linux 10 | 4.08 |
|
Major Changes
| • | Switched to WinPE 2.1 automation environment.
WinPE is no longer included on the RDP media. To get WinPE, you must manually download and install the Microsoft Windows AIK 2.1. You can either do that before installing RDP or you will be directed to do so during the RDP Autorun process.
For upgrade installations, the default WinPE 1.6 PXE images will be replaced. WinPE 1.6 boot media will no longer be supported. |
| • | The Primary Lookup Key mechanism has been enhanced. Refer to Knowledge Base article Primary Lookup Key And Virtual Connect (Article 189). |
| • | Added Windows and Linux scripted install support for some ProLiant 100-series servers. |
| • | During setup, Windows product keys will be applied to the Windows sysprep jobs. |
| • | For Linux scripted installs, the PXE nic is used to start the installation process and all nics are enabled at the end of the install. |
| • | Added support for upgrading NIC firmware. |
| • | Removed the Virtual Machine Deployment Toolbox job tree. Deployment to virtual machines requires manual intervention. Refer to Knowledge Base article Virtual Machine Deployment Support (Article 193). |
| • | Replaced the Server Replication job folder with the new Server Imaging job folder. The new jobs are similar to the scripted install jobs and allow image deployment to bare-metal servers. |
| • | Removed the Server Deployment Toolbox\3 - Post-OS Configuration\Optimize HP Lights-Out job. |
| • | Deployment Server can coexist on an IPv6 network. |
Known Issues
| • | On servers with PXE first in the boot order, Windows 2008 x86/x64 scripted install jobs will hang
The "rem scripted-install" command in the Start Install Run Script, instructs the Deployment Server that this task should be automatically marked as complete since the Windows setup program will be taking over. However, when PXE is first in the boot order and Windows 2008 setup reboots, the server incorrectly boots to automation. The Deployment Server thinks there is a pending task, but since there isn't, the server stops. Force the server to boot to the local hard drive by either canceling the PXE boot or temporarily changing the boot order. |
| • | Intermittently, DAgent hangs during a Windows 2008 x64/x64/ia64 sysprep capture
This issue will be fixed in a future release. In the interm, a hotfix will be made available. |
| • | Deploying a Windows 2003 sysprep image, captured on a non-SAN reference server, to a Emulex HBA SAN target server, will fail with an error -3 on the Support Pack installation task
Retry the Support Pack installation. |
| • | Deployment Server installation hangs if Z drive is mapped and not connected
Either connect or unmap Z drive and then retry the installation. |
| • | If UUID is the Primary Lookup Key, a Deployment Server upgrade installation will duplicate computer records in the database
Before an upgrade installation, change the lookup key to something other than UUID. Altiris is providing a tool to repair the database if the installation was performed. |
| • | iLO channel interface driver is not loading under WinPE 2.1 x86/x64
When a new computer performs an initial WinPE 2.1 x86/x64 PXE boot, the iLO inventory information will be missing from the Computer Properties dialog. When the server boots to a production operating system or LinuxPE, the iLO inventory information will be retrieved. |
| • | Rip-And-Replace jobs fail with an error 1 on the Support Pack installation task
When performing a rip-and-replace, Windows jobs that contain a Distribute Software task to install the Support Pack will fail with an error 1 because the generated jobs do not persist custom return codes. Error 1 means that installation was successful and that a reboot is required. Manually reboot the target server to complete the job. |
| • | Conrep fails on the DL180 G5
By default, conrep is not intended to work on the ProLiant 100-series servers. This error is harmless, but will cause the job to fail. Either right-click on the schedule and select Continue Job, or remove that task from job and rerun. |
Related Articles
|
|
Sorry, we can't find that page.
» Laptops
» Desktop Computers
» Printers
» Ink, Toner & Paper
