RDP User Guide
RDP User Guide
RDP User Guide
Copyright 2003, 2009 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 and 12.212, Commercial 1 Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Windows Server is a U.S. trademark of the Microsoft group of companies. AMD is a trademark of Advanced Micro Devices, Inc. Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other Countries.
Table of Contents
1 Licensing...................................................................................................7
License types..........................................................................................................................................7 Applying a license file.............................................................................................................................7 Applying a license file during an first-time installation or upgrade............................................................7 Adding a license file to an existing installation.......................................................................................7 Replacing licenses in an existing installation..........................................................................................7
2 Prerequisites..............................................................................................9
Network infrastructure requirements...........................................................................................................9 Deployment Server requirements...............................................................................................................9
3 Installing.................................................................................................11
Getting started.....................................................................................................................................11 Before you upgrade...............................................................................................................................11 Installing .............................................................................................................................................11
Table of Contents
Index.........................................................................................................39
Table of Contents
List of Tables
5-1 5-2 5-3 5-4 5-5 5-6 5-7 A-1 B-1 B-2 Job folders.....................................................................................................................................27 Hardware configuration default settings.............................................................................................27 Windows default settings.................................................................................................................28 VMware default settings...................................................................................................................28 Linux default settings........................................................................................................................28 Deployment Server directory structure................................................................................................29 State transitions..............................................................................................................................32 Operating system directory names.....................................................................................................35 Virtual directory information.............................................................................................................38 User Tokens table entries..................................................................................................................38
1 Licensing
A license enables a server, either a physical server or a virtual machine, to be deployed and managed by the Altiris Deployment Server. One license is required for each server being managed. After you apply a license to a server, you cannot remove or transfer the license to another server. A license file contains licenses for a predetermined number of servers. Purchased license files are not specific to Rapid Deployment Pack versions. To view the number of licensed nodes from the console, click Help>About.
License types
Purchased license. To obtain this license file, follow the instructions on your license entitlement certificate. 10-node, 30-day evaluation license. To obtain this license file, access http://www.hp.com/servers/rdp/eval. 10-node, 7-day evaluation license. This license is built into the Deployment Server.
License types
2 Prerequisites
Network infrastructure requirements
If you use Preboot eXecution Environment (PXE) to remotely deploy servers, then Dynamic Host Configuration Protocol (DHCP) must be installed and accessible on the network.
Microsoft Windows operating system: Microsoft Windows Server 2003 x86 and x64 (SP1, SP2, and R2) Standard and Enterprise Editions Microsoft Windows Server 2008 x86 and x64 Standard and Enterprise Editions NOTE: The server must not be a domain controller.
Available disk space: 2 GB for the base installation, plus space for each distribution, and space for each captured disk image A network connection configured with a static IP address NOTE: Changing the IP address configuration after installation is difficult. Therefore, set the IP address before beginning the installation.
Microsoft .NET Frameworks 1.1 and 2.0 Microsoft SQL Server: (installed either locally or remotely and configured according to Altiris KB article #2044) Microsoft SQL Server 2005 SP2 Express, Standard, and Enterprise Editions Microsoft SQL Server 2008, Standard, and Enterprise Editions
Microsoft WAIK 1.1, also known as the Automated Installation Kit (AIK) for Windows Vista SP1 and Windows Server 2008. It is available at http://www.microsoft.com/downloads/ details.aspx?familyid=94bb6e34-d890-4932-81a5-5b50c657de08&displaylang=en&tm To use the Deployment Server Web Console, you must install IIS with ASP.NET. To deploy VMware ESX or Linux, you must install an FTP server. For more information, see the Microsoft documentation on how to install IIS with FTP.
For more information about requirements for the Deployment Server, see the Altiris Deployment Solution Deployment and Migration Guide at http://www.hp.com/servers/rdp.
10
3 Installing
Getting started
Log in to the local console. You cannot install Rapid Deployment Pack through Terminal Services, remote shell, or from a network share. Obtain a license file (either purchased or evaluation). Collect the applicable Windows, VMware ESX, or Linux distribution files. Get the applicable Windows product keys.
Installing
1. On the intended Deployment Server, access the Rapid Deployment Pack autorun utility using one of the following methods: 2. 3. 4. Insert the physical DVD into the DVD drive. Extract the ISO image. Mount the ISO image.
Read the terms of the ProLiant Essentials End User License Agreement (EULA), and click Agree to accept the terms. On the Overview screen, click Next. On the Pre-Installation screen, click Next.
Getting started
1 1
5.
Verify that the appropriate components are selected for installation, and click Install. If you plan to use an existing database, clear the Microsoft SQL Server 2005 Express option.
12
Installing
6.
If selected, the Microsoft .NET Frameworks and Microsoft SQL Server are installed silently. You must download and install the Microsoft WAIK 1.1, also known as the Automated Installation Kit (AIK) for Windows Vista SP1 and Windows Server 2008. It is available at http://www.microsoft.com/ downloads/details.aspx?familyid=94bb6e34-d890-4932-81a5-5b50c657de08&displaylang=en&tm. After completing the WAIK install, reinsert the Rapid Deployment Pack media and click Continue. 7. If you did not select the Altiris Deployment Server for installation, proceed to Step 23. 8. Read the Altiris EULA, and click Yes. 9. If the server has multiple network adapters, select the appropriate interface for the Deployment Server, and click Select IP. 10. Select the appropriate licensing option, and click Next. If installing for the first-time, select Free 7 day license, or select License file, and enter the license file path and name. If upgrading, verify that Upgrade using existing license is selected. NOTE: When upgrading, you must select Upgrade using existing license to avoid losing existing licenses.
Installing
13
1 Enter the service credentials for the Deployment Server, and click Next. 1. NOTE: Do not install the Deployment Server component to a remote server because the Integration Module installations fail.
12. Select the name of the server instance where you want to install the database, and click Next. If the database is located on a remote server, you might be prompted for credentials. Enter a username and password with administrative rights.
14
Installing
13. Enter the appropriate database authentication method, and click Next. NOTE: If you choose SQL Server Authentication, some Integration Module Configuration tasks fail.
14. If upgrading, click Yes when prompted to retain the data in the existing database.
Installing
15
15. On the Pre-boot Operating Systems screen, click Next. NOTE: Even though the WinPE options are not selected, WinPE is installed.
16
Installing
16. Specify the location where you want to install PXE Server, and click Next. If DHCP is installed on a separate server, click OK when prompted that DHCP services are required. If you choose not to use PXE, then see the Knowledge Base article Creating and Using Automated Boot Media (Article 196). NOTE: When upgrading, you must select Yes, I want to upgrade PXE Server(s) on this computer or on a remote computer.
Installing
17
17. Specify how clients connect to the Deployment Server, and click Next.
18
Installing
18. Specify the location where you want to install the Deployment Server Console, and click Next. NOTE: Do not install the initial Deployment Console component to a remote server because the Integration Module installations fail.
19. Specify where you want to install the Deployment Server Web Console, and click Next.
Installing
19
If upgrading, click Yes when prompted to replace the eXpress share. When the installation is complete, click Finish. If you did not select the Altiris Deployment Server Hotfix, proceed to Step 25 Wait while the Altiris Deployment Server Hotfix is applied. If you did not select ProLiant Integration Module software, proceed to Step 36. On the Prerequisites screen, click Verify. When the process is complete, click Next. Select the operating systems that you want to deploy to target servers, and click Next.
20
Installing
28. Specify the appropriate configuration options, and click Next. For more information, see Appendix B Manually modifying configuration settings. NOTE: The MAC Address lookup value is required for Integrity and new ProLiant servers.
29. Specify the appropriate Windows product keys, and click Next. 30. On the Installation and Configuration screen, click Install. 31. If upgrading, click OK when prompted to back up and overwrite existing configuration files, and reimport existing jobs. 32. For each operating system that you want to copy, specify the root directory of the distribution files, and click Copy. If you skip copying any distribution, see Appendix A Manually installing distribution files.
If prompted to reinsert the Rapid Deployment Pack media, reinsert it, and click OK. If you skipped any distributions, click OK when the warning message appears. On the Installation and Configuration screen, click Finish. If you did not select Integrity Integration Module software, proceed to Step 48.
Installing 21
37. On the Prerequisites screen, click Verify. When the verification process is complete, click Next. 38. Select the operating systems that you want to deploy to target servers, and click Next.
39. Specify the appropriate configuration options, and click Next. For more information, see Appendix B Manually modifying configuration settings. NOTE: The MAC Address lookup value is required for Integrity and new ProLiant servers.
40. Specify the appropriate Windows product keys, and click Next. 41. On the Installation and Configuration screen, click Install. 42. If upgrading, click OK when prompted to back up and overwrite existing configuration files and reimport existing jobs. 43. For each operating system that you want to copy, specify the root directory of the distribution files, and click Copy. If you skip copying any distribution, see Appendix A Manually installing distribution files. 44. If prompted to reinsert the Rapid Deployment Pack media, reinsert it, and click OK. 45. If you skipped any distribution, click OK when the warning message appears.
22 Installing
On the Installation and Configuration screen, click Finish. On the Installation screen, click Next. On the Post-Installation screen, click Finish. Click Yes when prompted to reboot the server.
Installing
23
24
Computers PaneThis pane shows managed computers. The New Computers group shows computers that have connected to the Deployment Server for the first time. Click ViewShow Physical Devices to add the Physical Devices group. Jobs PaneThis pane shows the provided jobs. Details PaneThe right-hand side of the console displays information about the selected computer or job. For a computer, basic properties and job history appear. For a job, tasks and computer history appear. The Job Schedule Information dialog box displays the status of each task in the schedule. To view this dialog box, double-click an item in the job history or computer history. The Schedule Status Detail dialog box displays return codes and status messages. To view this dialog box, click Status Details. To execute a job, drag and drop one or more computers onto a job, or vice-versa.
25
2. 3.
Select Run this job immediately, and click OK. To view the progress of the job, double-click the computer in the jobs computer history.
Next steps
Adapt and customize the Rapid Deployment Pack for your environment. The provided jobs and files are generic and work out-of-the-box; however, they might not be sufficient for a complex server environment. For example, you might want to change the default password in the various unattend and kickstart files. For problem-solving information and Online resources, see Chapter 6 HP support and contact information.
26
Design philosophy
The provided jobs, perhaps with a few tweaks, are sufficient for generic operating system deployment. More than likely, the provided jobs will act as templates and will need to be adapted and customized. When this is the case, HP strongly recommends that you follow a copy, rename, and modify process copy the job or file, rename it so that the name conveys the new behavior, and make the necessary modifications. Doing so will provide a clean separation between the customized jobs and the provided jobs. This will allow the provided jobs to act as working baselines. NOTE: When editing ESX or Linux files on the Deployment Server, use a text editor that saves the file in Linux compatible format without adding extra characters.
Jobs
Rapid Deployment Pack adds three root folders into the Jobs pane.
Design philosophy
27
28
Linux imaging notes: The reference and target servers must have an identical storage controllers. The capture image file will be .\lib\images\yyyy-linux.img where yyyy is the computer model name, for example ProLiant DL360 G4. Subsequent captures on the same model will overwrite any existing image file. Some applications do not image properly.
Directory structure
The following table provides an overview of the Deployment Server directory as populated by the Rapid Deployment Pack. The . in the directory paths below represents the Deployment Server installation directory. Table 5-6 Deployment Server directory structure
Directory .\docs .\jobs .\lib\bin32 .\lib\bin64 .\lib\binia64 .\lib\hwconfig .\lib\images .\lib\osconfig .\lib\osdist .\lib\osoem Directory contents Rapid Deployment Pack documentation The .bin files for the provided jobs Windows SmartStart Scripting Toolkit, Linux SmartStart Scripting Toolkit, and various tools and scripts Various tools and scripts Smart Setup Scripting Toolkit for Integrity and various tools and scripts Presupplied and captured hardware configuration files Presupplied and captured image files Operating system scripted installation answer files separated into subdirectories per OS Operating system distribution files separated into subdirectories per OS ProLiant Drivers for Windows, Integrity Drivers for Windows, and Altiris Deployment Agents The driver subdirectories are either a specific version number, such as 800, or zzz which is a copy of the latest version subfolder. The provided jobs use the zzz subfolder. .\lib\ossysprep .\lib\software Operating system sysprep imaging answer files separated into subdirectories. ProLiant Support Packs, ProLiant Firmware Maintenance, and Integrity Support Packs The support pack subdirectories are either a specific version number such as 800, or Z.ZZ which is a copy of the latest version subfolder. The provided jobs use the Z.ZZ subfolder.
29
JobDirectory relationship
The provided jobs follow a common design consisting of a sequence of Run Script, image capture or deploy, and reboot tasks. The embedded scripts in the Run Script tasks, reference files or directories using environment variables and pass those variables to external wrapper scripts. The wrapper scripts perform one well-defined function, for example, calling a single utility like conrep. Using external scripts enables detailed error reporting to the Deployment Server. You need to edit only the embedded Run Script code. However, be aware that the wrapper scripts do not accept arbitrary file paths. They are hard-coded to specific locations in the .\lib tree. The following table lists the Deploy ProLiant ML/DL/BL + Windows 2003 x64 Enterprise + PSP job. The bold lines represent each task in the job. Each task is followed by its contents, which represent code called by the embedded Run Script code.
Run Script Deploy System Configuration {WinPE Managed (32-bit)} set inputfile=pl.xml call f:\lib\bin32\winpe\conrep.cmd l %inputfile% f:\lib\bin32\winpe\conrep.exe l ff:\lib\hwconfig\system\pl.xml
Power Control (Reboot) Run Script Deploy Array Configuration {WinPE Managed (32-bit)} set inputfile=pl-acu-rd.ini call f:\lib\bin32\winpe\acu.cmd -i %inputfile% -internal -reset f:\lib\bin32\winpe\acu\hpacubin.exe -i f:\lib\hwconfig\array\pl-acu-rd.ini internal -reset
Power Control (Reboot) Run Script Deploy System Configuration {WinPE Managed (32-bit)} set inputfile=pl-win.xml call f:\lib\bin32\winpe\conrep.cmd l %inputfile% f:\lib\bin32\winpe\conrep.exe l ff:\lib\hwconfig\system\pl.xml
Distribute Disk Image {WinPE Managed (32-bit)} f:\lib\images\ntfs.img Run Script Copy ProLiant Files {WinPE Managed (64-bit)} set oem=proliant.zzz\w52.64 call f:\lib\bin64\winpe\osoem1.cmd copy f:\lib\osoem\proliant.zzz\w52.64\*.* c:\
Run Script Copy Altiris Files {WinPE Managed (64-bit)} rem replacetokens .\lib\osoem\altiris\aclient.txt .\lib\osoem\altiris\%ID%.tmp set configfile=%ID%.inp call f:\lib\bin64\winpe\osoem2.cmd copy f:\lib\osoem\altiris\%ID%.inp c:\$oem$\aclient\aclient.inp
30
Run Script Copy Unattend.txt {WinPE Managed (64-bit)} rem replacetokens .\lib\osconfig\w52e.64\default.txt .\lib\osoem\w52e.64\%ID%.txt set unattendfile=w52e.64\%ID%.txt call f:\lib\bin64\winpe\osconfig1.cmd copy f:\lib\osoem\w52e.64\%ID%.txt c:\unattend.txt
Run Script Copy Distribution Files {WinPE Managed (64-bit)} set dist=w52e.64 call f:\lib\bin64\winpe\osdist1.cmd copy f:\lib\osdist\w52e.64\i386\*.* c:\i386
Run Script Start Install {WinPE Managed (64-bit)} c:\amd64\winnt32.exe /s:c:\amd64 /unattend:c:\unattend.txt Install Package f:\lib\software\ProLiant Support Pack Z.ZZ for Windows 2003 x64\hpsum.exe silent Power Control (Reboot)
JobDirectory relationship
31
Automation environments
An automation environment is an operating system in which scripts can be run on the target independent of the targets production operating system or the Deployment Servers operating system. The target can boot the automation environment from a CD-ROM, USB key or through PXE. Each automation environment consists of the necessary base files, additional HP drivers, and the appropriate Altiris Deployment Agent. The Run Script, Create Disk Image, and Distribute Disk Image tasks enable the user to specify which automation environment to run in. The Rapid Deployment Pack jobs specify a specific automation environment to avoid ambiguity and to ensure that the utilities run in the correct and tested environment. The following illustration and table provide a view of how the Deploy ProLiant ML/DL/BL + Windows 2003 x64 Enterprise + PSP scripted installation job uses the various automation environments.
7 3 1 4 5 6
LinuxPE (AutoSelect)
WinPE (32-bit)
WinPE (64-bit)
Windows
32
HP contact information
For the name of the nearest HP authorized reseller: In the United States, see the HP U.S. service locator webpage at http://www.hp.com/service_locator. In other locations, see the Contact HP worldwide webpage at http://welcome.hp.com/country/us/en/wwcontact.html. In the United States, for contact options see the Contact HP United States webpage at http://welcome.hp.com/country/us/en/contact_us.html. To contact HP by phone: Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored. For U.S. customers, say "Insight Manager" when prompted for the product name. In other locations, see the Contact HP worldwide webpage at http://welcome.hp.com/country/us/en/wwcontact.html.
How to Use Your Software Technical Support and Update Service: Once registered, you will receive a service contract in the mail containing the Customer Service phone number and your Service Agreement Identifier (SAID). You will need your SAID when calling for technical
Online resources 33
support. Using your SAID, you can also go to the Software Update Manager (SUM) web page to view your contract online and elect electronic delivery for product updates. Warranty HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty applies to all Insight Control Management, HP Systems Insight Manager, and ProLiant Essentials products. Join the discussion The HP Support Forum is a community-based, user-supported tool for HP customers to participate in discussions amongst the customer community about HP products. For discussions related to Insight Control and ProLiant Essentials software, see the "Management Software and System Tools" area. Software and Drivers download pages provides latest software and drivers for your ProLiant products. Management Security (http://www.hp.com/servers/manage/security) HP is proactive in its approach to the quality and security of all its management software. Be sure to check this website often for the latest down loadable security updates. Obtain the latest SmartStart Release (http://www.hp.com/servers/smartstart) The SmartStart, Management, and Firmware CDs are now freely available for download following a simple registration from the SmartStart web site. If you wish to receive physical kits with each release, you can order single release kits from the SmartStart web site. To receive proactive notification when SmartStart releases are available, subscribe to Subscriber's Choice at http://www.hp.com/go/subscriberschoice. HP Worldwide Customer Service contact numbers are available at http://www.hp.com/country/us/en/wwcontact.html. For U.S. customers, say "Insight Manager" when prompted for the product name.
34
35
36
4.
Complete the Virtual Directory wizard by entering the following information when prompted. Table B-1 Virtual directory information
Field Virtual Directory Alias FTP Site Content Directory Virtual Directory Access Permissions
Entry DSLIB
5. 6. 7. 8.
Right-click the FTP site, and click Properties. Click the Security Accounts tab. Select Allow Anonymous Connections, and click OK. If the FTP site name is followed by (Stopped), right-click the site name, and click Start.
38
Index
A
Altiris Product Licensing Utility, 7 automation environment, 32
O
obtaining licenses, 7 online resources, 33 options, configuring, 37
C
configuring HP BladeSystem servers, 25 options, 37 Preboot eXecution Environment, 37 creating FTP virtual directory, 37 image, 26 reference server, 26
P
Preboot eXecution Environment booting, 25 configuring, 37 PXE Configuration Utility , 37 reference, 25 prerequisites, installing, 9 primary lookup key, setting, 37 product keys, 38
D
Deployment Server configuration, 37 directory structure, 27 requirements, 9 directory relationship job, 30 display names, synchronizing, 37
R
Red Hat Linux scripted installation, 27 reference server, creating, 26 requirements Deployment Server, 9 network, 9
G
getting started, 1 1
S
scripted installation, customizing, 27 setting primary lookup key, 37 setting PXE initial deploy boot option, 37 software installing, 1 1 support, 33 SUSE Linux, scripted installation, 27 synchronizing display names, 37
H
HP authorized reseller, 33 HP BladeSystem servers blades configuring, 25 HP contact information, 33 HP Software Technical Support and Update Service, 33 HP Support and Contact information, 33
I
imaging, creating, 26 installing, 1 1 Deployment Server, 1 1 operating system CDs and DVDs, 35 software, 1 1
U
upgrade, 1 1 usage scenario, 25
V
virtual directory, creating, 37 VMware installing operating system CDs and DVDs, 35 scripted installation, 27
J
jobs, 27
L
licenses, 7 Linux scripted installation, 27
W
Windows entering product keys, 38 installing operating system CDs and DVDs, 35 synchronizing name, 37
M
Microsoft Internet Information Services creating an FTP virtual directory, 37
N
network requirements, 9
39