HP Xw460c Administrator's Guide for Microsoft Windows on HP ProLiant Blade Wor - Page 89

Preinstalled operating system, Booting, Software tools - proliant blade workstation firmware

Get HP Xw460c - ProLiant - Blade Workstation PDF manuals and user guides View all HP Xw460c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 89 highlights

• Windows XP uses Microsoft Windows Activation technologies-Microsoft Windows Activation requires either that users activate their Windows license on each machine at first boot or that the administrator take specific steps during image creation to ensure that activation is not needed. Microsoft Windows Activation is not required on the server blade. 12-6-4-2 Preinstalled operating system The blade workstation is shipped with Windows XP-32 pre-installed on the hard drive. Server blades have no operating system preinstalled. When a new blade workstation is booted the first time, it boots to the pre-installed Windows XP-32, not PXE, unless steps are taken to change this behavior. HP RDP automatically identifies deployed computers but only if they boot to PXE or have the Altiris Aclient installed in the Windows image, and are correctly configured for the specific HP RDP server. The preinstalled blade workstation operating system does not include the Aclient because it must be specifically configured for each site. Therefore, new blade workstations are not automatically detected by HP RDP. For more information, see Section 12-6-5, "Use Rip-n-Replace and Virtual Bay features to replace failed systems." 12-6-4-3 Booting The blade workstation boot process differs from the server blade boot process in two ways: • The blade workstation boots from the hard drive-Booting from the hard drive occurs because there is an OS installed on the hard drive. With the server blade, PXE booting occurs because there is no OS installed. If PXE booting is required on the blade workstation, the administrator will need to use the iLO 2 remote console to force PXE booting to occur. • The blade workstation is shipped with Remote Console Mode set to User Mode-This is desirable for most systems because RGS, using the NVIDIA graphics adapter, offers better performance than the ATI video controller. However, because the RGS is not preinstalled on the operating system image, the administrator might need to set Remote Console Mode to Admin Mode to create the reference image. 12-6-4-4 Software tools Several software tools have limited support for the blade workstation: • ProLiant Support Packs are not currently supported on the blade workstation. • The SmartStart Scripting Toolkit is not supported on the blade workstation. In particular, the Conrep.exe tool and server deployment jobs that capture firmware settings (for example, the default Hardware Configuration or Server Deployment jobs) do not capture settings for features that are unique to the blade workstation, such as Remote Console Mode. These settings must be configured using iLO 2 or the local I/O cable. 12-6-5 Use Rip-n-Replace and Virtual Bay features to replace failed systems Both the Rip-n-Replace and the Virtual Bay functionality of the blade systems architectures should also function on blade workstations. However, a new system placed into the Virtual Bay is not detected until it is either PXE booted or booted with an image that has the Aclient installed and configured. Automatic deployment jobs are then enabled. The default for the blade workstation is to boot to the Windows XP Professional image preinstalled on the hard drive, which does not have the Aclient installed or configured. Managing the blade workstation 89

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
Managing the blade workstation
89
•
Windows XP uses Microsoft Windows Activation technologies—Microsoft Windows Activation requires
either that users activate their Windows license on each machine at first boot or that the administrator take
specific steps during image creation to ensure that activation is not needed. Microsoft Windows Activation
is not required on the server blade.
12-6-4-2 Preinstalled operating system
The blade workstation is shipped with Windows XP-32 pre-installed on the hard drive. Server blades have no
operating system preinstalled. When a new blade workstation is booted the first time, it boots to the pre-installed
Windows XP-32, not PXE, unless steps are taken to change this behavior.
HP RDP automatically identifies deployed computers but only if they boot to PXE or have the Altiris Aclient
installed in the Windows image, and are correctly configured for the specific HP RDP server. The preinstalled
blade workstation operating system does not include the Aclient because it must be specifically configured for
each site. Therefore, new blade workstations are not automatically detected by HP RDP.
For more information, see Section 12-6-5, “
Use Rip-n-Replace and Virtual Bay features to replace failed systems
.”
12-6-4-3 Booting
The blade workstation boot process differs from the server blade boot process in two ways:
•
The blade workstation boots from the hard drive—Booting from the hard drive occurs because there is an
OS installed on the hard drive. With the server blade, PXE booting occurs because there is no OS installed.
If PXE booting is required on the blade workstation, the administrator will need to use the iLO 2 remote
console to force PXE booting to occur.
•
The blade workstation is shipped with Remote Console Mode set to User Mode—This is desirable for most
systems because RGS, using the NVIDIA graphics adapter, offers better performance than the ATI video
controller. However, because the RGS is not preinstalled on the operating system image, the administrator
might need to set Remote Console Mode to Admin Mode to create the reference image.
12-6-4-4 Software tools
Several software tools have limited support for the blade workstation:
•
ProLiant Support Packs are not currently supported on the blade workstation.
•
The SmartStart Scripting Toolkit is not supported on the blade workstation. In particular, the Conrep.exe tool
and server deployment jobs that capture firmware settings (for example, the default Hardware
Configuration or Server Deployment jobs) do not capture settings for features that are unique to the blade
workstation, such as Remote Console Mode. These settings must be configured using iLO 2 or the local I/O
cable.
12-6-5 Use Rip-n-Replace and Virtual Bay features to replace failed systems
Both the Rip-n-Replace and the Virtual Bay functionality of the blade systems architectures should also function on
blade workstations. However, a new system placed into the Virtual Bay is not detected until it is either PXE
booted or booted with an image that has the Aclient installed and configured. Automatic deployment jobs are
then enabled. The default for the blade workstation is to boot to the Windows XP Professional image preinstalled
on the hard drive, which does not have the Aclient installed or configured.