HP mt20 Administrator Guide - Page 151

auto-update, Registry key, Description, Classes

Get HP mt20 PDF manuals and user guides View all HP mt20 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 151 highlights

Registry key root/USB/Classes/ShowTab root/USB/Devices//DisplayName root/USB/Devices//ProductID root/USB/Devices//State root/USB/Devices//VendorID root/USB/root/autoSwitchProtocol root/USB/root/mass-storage/allowed root/USB/root/mass-storage/read-only root/USB/root/opendebug root/USB/root/protocol Description If set to 1, the Classes section is shown in USB Manager. Sets the name to show in USB Manager. If not supplied, USB Manager will attempt to generate an appropriate name using device information. Sets the product ID of the device. Sets whether this device is mapped to the remote host as follows: 0=Do Not Redirect; 1=Use Defaults; 2=Redirect. Sets the vendor ID of the device. If set to 1, the remote USB protocol will switch automatically based on which protocol is chosen. If set to 1, mass storage devices will be mounted automatically when the protocol is local. If set to 1, when mass storage devices are mounted automatically, they will be mounted as read-only. If set to 1, a debug message will be written to /tmp/USB-mgrlog. Sets which protocol owns remote USB. Valid values depend on which protocols are installed on the system but can include local, xen, freerdp, and view. auto-update Registry key root/auto-update/DNSAliasDir root/auto-update/ManualUpdate root/auto-update/ScheduledScan/Enabled root/auto-update/ScheduledScan/Interval root/auto-update/ScheduledScan/Period root/auto-update/ScheduledScan/StartTime Description Sets the default root directory for DNS alias mode on the server hosting HP Smart Client Services. If set to 1, the DHCP tag, DNS alias, and broadcast update methods for Automatic Update are disabled. When performing a manual update, the password, path, protocol, user, and ServerURL registry keys must be set to ensure the update server is known. If set to 1, the thin client performs periodic scans of the Automatic Update server to check for updates. If set to 0, the thin client will only check for updates at system startup. Sets the amount of time to wait between scheduled update scans. This should be specified in the HH:MM format. Intervals longer than 24 hours can be specified. For example, to have the scans occur every 48 hours, set this to 48:00. Thin clients will randomly activate their scheduled scan throughout the defined period. Using a long period avoids cases where all thin clients update at exactly the same, which could cause network congestion. The period should be specified in the HH:MM format. For example, to spread thin client updates over a 2.5-hour period, set this to 02:30. Sets the start time of the first scheduled update scan period in the format HH:MM, using the 24-hour time format. For example, 4:35 p.m. would be 16:35. auto-update 139

  • 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
Registry key
Description
root/USB/Classes/ShowTab
If set to 1, the
Classes
section is shown in USB Manager.
root/USB/Devices/<UUID>/DisplayName
Sets the name to show in USB Manager. If not supplied, USB
Manager will attempt to generate an appropriate name using
device information.
root/USB/Devices/<UUID>/ProductID
Sets the product ID of the device.
root/USB/Devices/<UUID>/State
Sets whether this device is mapped to the remote host as follows:
0=Do Not Redirect; 1=Use Defaults; 2=Redirect.
root/USB/Devices/<UUID>/VendorID
Sets the vendor ID of the device.
root/USB/root/autoSwitchProtocol
If set to 1, the remote USB protocol will switch automatically
based on which protocol is chosen.
root/USB/root/mass-storage/allowed
If set to 1, mass storage devices will be mounted automatically
when the protocol is
local
.
root/USB/root/mass-storage/read-only
If set to 1, when mass storage devices are mounted automatically,
they will be mounted as read-only.
root/USB/root/opendebug
If set to 1, a debug message will be written to
/tmp/USB-mgr-
log
.
root/USB/root/protocol
Sets which protocol owns remote USB. Valid values depend on
which protocols are installed on the system but can include
local
,
xen
,
freerdp
, and
view
.
auto-update
Registry key
Description
root/auto-update/DNSAliasDir
Sets the default root directory for DNS alias mode on the server
hosting HP Smart Client Services.
root/auto-update/ManualUpdate
If set to 1, the DHCP tag, DNS alias, and broadcast update
methods for Automatic Update are disabled. When performing a
manual update, the
password
,
path
,
protocol
,
user
, and
ServerURL
registry keys must be set to ensure the update
server is known.
root/auto-update/ScheduledScan/Enabled
If set to 1, the thin client performs periodic scans of the
Automatic Update server to check for updates. If set to 0, the thin
client will only check for updates at system startup.
root/auto-update/ScheduledScan/Interval
Sets the amount of time to wait between scheduled update scans.
This should be
specified
in the
HH:MM
format. Intervals longer
than 24 hours can be
specified.
For example, to have the scans
occur every 48 hours, set this to
48:00
.
root/auto-update/ScheduledScan/Period
Thin clients will randomly activate their scheduled scan
throughout the
defined
period. Using a long period avoids cases
where all thin clients update at exactly the same, which could
cause network congestion. The period should be
specified
in the
HH:MM
format. For example, to spread thin client updates over a
2.5-hour period, set this to
02:30
.
root/auto-update/ScheduledScan/StartTime
Sets the start time of the
first
scheduled update scan period in the
format
HH:MM
, using the 24-hour time format. For example, 4:35
p.m. would be
16:35
.
auto-update
139