HP t505 Administrator Guide 7 - Page 72

Using the DHCP tag update method, Example of performing DHCP tagging

Page 72 highlights

Using the DHCP tag update method On the Windows Server 2003 and Windows Server 2008 systems, DHCP tagging enables a thin client to update. Use this method to update specific thin clients; however, if you have only one or two clients to update, consider using the manual update method instead. Otherwise, HP recommends the broadcast update method. Example of performing DHCP tagging The example in this section shows how to perform DHCP tagging on a Windows 2008 R2 Server. NOTE: To use DHCP tagging, see your DHCP server documentation. 1. On the server desktop, select Start > Administrative Tools > DHCP. 2. In the left pane of the DHCP screen, click the domain where the thin clients are connected. 3. In the right pane of the DHCP screen, expand and right-click IPv4, and then click Set Predefined Options. 4. In the Predefined Options and Values dialog, click Add. 5. In the Option Type box, configure the options as described in the following table. Table 11-1 Example DHCP tagging options Field Entry Name Type auto-update. Data Type Select String. Code Type 137. Description Type HP Automatic Update. 6. Click OK. 7. In the Predefined Options and Values dialog, under Value > String, type the update server address in the format of the following example: http://auto-update.dominio.com:18287/auto-update 8. To complete the setup, click OK. DHCP tagging is now ready to update specific thin clients. Using the DNS alias update method During system startup, Automatic Update attempts to resolve the DNS alias auto-update. If that host name resolves, it attempts to check for updates at http://auto-update:18287. This update method enables thin clients to access a single update server across the entire domain, thus simplifying management for deployments with many subnets and DHCP servers. To configure the DNS alias update method: ▲ Change the hostname of the server hosting HP Smart Client Services to auto-update or create a DNS alias of auto-update for that server. Using the manual update method Use the manual update method to connect a thin client to a specific server for an update. Also, use this method if you want to test an update on a single thin client before pushing the update to many thin clients, or if you have specific updates to be installed on only one or two thin clients. 60 Chapter 11 HP Smart Client Services

  • 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
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169

Using the DHCP tag update method
On the Windows Server 2003 and Windows Server 2008 systems, DHCP tagging enables a thin client to
update. Use this method to update
specific
thin clients; however, if you have only one or two clients to
update, consider using the manual update method instead. Otherwise, HP recommends the broadcast update
method.
Example of performing DHCP tagging
The example in this section shows how to perform DHCP tagging on a Windows 2008 R2 Server.
NOTE:
To use DHCP tagging, see your DHCP server documentation.
1.
On the server desktop, select
Start > Administrative Tools > DHCP
.
2.
In the left pane of the
DHCP
screen, click the domain where the thin clients are connected.
3.
In the right pane of the
DHCP
screen, expand and right-click
IPv4
, and then click
Set
Predefined
Options
.
4.
In the
Predefined
Options and Values
dialog, click
Add
.
5.
In the
Option Type
box,
configure
the options as described in the following table.
Table 11-1
Example DHCP tagging options
Field
Entry
Name
Type
auto-update
.
Data Type
Select
String
.
Code
Type
137
.
Description
Type
HP Automatic Update
.
6.
Click
OK
.
7.
In the
Predefined
Options and Values
dialog, under
Value > String
, type the update server address in
the format of the following example:
http://auto-update.dominio.com:18287/auto-update
8.
To complete the setup, click
OK
. DHCP tagging is now ready to update
specific
thin clients.
Using the DNS alias update method
During system startup, Automatic Update attempts to resolve the DNS alias
auto-update
. If that host name
resolves, it attempts to check for updates at
http://auto-update:18287
. This update method enables thin
clients to access a single update server across the entire domain, thus simplifying management for
deployments with many subnets and DHCP servers.
To
configure
the DNS alias update method:
Change the hostname of the server hosting HP Smart Client Services to
auto-update
or create a DNS
alias of
auto-update
for that server.
Using the manual update method
Use the manual update method to connect a thin client to a
specific
server for an update. Also, use this
method if you want to test an update on a single thin client before pushing the update to many thin clients, or
if you have
specific
updates to be installed on only one or two thin clients.
60
Chapter 11
HP Smart Client Services