Symantec 11281411 Administration Guide - Page 189

Configuring additional server types for roaming clients, Command-line options

Page 189 highlights

Managing roaming clients 189 Command-line options Configuring additional server types for roaming clients In addition to parent, load balancing, and failover servers that you can configure from the Symantec System Center console, you can specify the following server types in the registry: ■ Central Quarantine Server (this must also have Symantec AntiVirus server installed). ■ Alert (Alert Management System2) server. ■ Grc.dat server, which provides the roaming client with Grc.dat settings. Using nearest_GRC lets the roaming client get policy settings from the specified server and process them immediately. Note: A client cannot connect with multiple parents of the same type. To configure additional server types for roaming clients 1 Set the roaming client's registry values that correspond to the server type to 1. See "Registry values" on page 191. 2 At the command prompt, type any of the following: ■ SavRoam /nearest_parent ■ SavRoam /nearest_quarantine ■ SavRoam /nearest_GRC ■ SavRoam /nearest_alerts The main difference between /nearest_parent and /nearest_GRC occurs when the configurations file (Grc.dat) is processed. Typing /nearest_parent lets the roaming client find the nearest parent. Policy settings are not processed until the client checks in with the parent. Typing /nearest_GRC lets the roaming client get the policy settings from the parent immediately, and the settings are processed immediately. Command-line options Table 6-4 describes the command-line options that can be used with SavRoam.exe and RoamAdmn.exe.

  • 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
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216

189
Managing roaming clients
Command-line options
Configuring additional server types for roaming clients
In addition to parent, load balancing, and failover servers that you can configure
from the Symantec System Center console, you can specify the following server
types in the registry:
Central Quarantine Server (this must also have Symantec AntiVirus server
installed).
Alert (Alert Management System
2
) server.
Grc.dat server, which provides the roaming client with Grc.dat settings.
Using nearest_GRC lets the roaming client get policy settings from the
specified server and process them immediately.
Note:
A client cannot connect with multiple parents of the same type.
To configure additional server types for roaming clients
1
Set the roaming client’s registry values that correspond to the server type to
1.
See
“Registry values”
on page 191.
2
At the command prompt, type any of the following:
SavRoam /nearest_parent
SavRoam /nearest_quarantine
SavRoam /nearest_GRC
SavRoam /nearest_alerts
The main difference between /nearest_parent and /nearest_GRC occurs
when the configurations file (Grc.dat) is processed. Typing
/nearest_parent lets the roaming client find the nearest parent. Policy
settings are not processed until the client checks in with the parent. Typing
/nearest_GRC lets the roaming client get the policy settings from the parent
immediately, and the settings are processed immediately.
Command-line options
Table 6-4
describes the command-line options that can be used with
SavRoam.exe and RoamAdmn.exe.