Symantec 11281411 Administration Guide - Page 183

Identifying servers for each hierarchical level, Creating a list of 0 level Symantec AntiVirus servers

Page 183 highlights

Managing roaming clients 183 Implementing roaming Identifying servers for each hierarchical level To identify servers for each hierarchical level, you must analyze the needs of your roaming users. For example, you may need to identify mobile users based on whether they travel internationally, throughout the country, or within a smaller geographic area. If users travel internationally, their server lists will contain the names of the country servers from level 0. If they travel within one country only, their server lists will contain servers from level 1. Depending on network speeds, the server list could contain only the top level servers (level 0 in Figure 6-1). This simplifies building the clients' server list. The only limit to the number of levels that you can define is the text file size limit of 512 characters. Creating a list of 0 level Symantec AntiVirus servers You can create the clients' server list text file using a text editor such as Notepad. The server list text file must contain lines in the following format: where: ■ indicates to the client that this is the 0 level of servers that the client should attempt to contact when searching for a roam server. ■ is the server type, such as parent server, Quarantine Server, Grc.dat server, or Alert server. ■ is 0. ■ is the list of servers, which are separated by commas. (Spaces between the commas are optional.) For example, the clients' server list text file that corresponds to Figure 6-1 is as follows: Parent 0 USASvr,EuropeSvr,AsiaSvr This is the only line in the server list for the roaming clients in this example. The list tells the clients to contact and compare response time from these three servers only. Depending on which server is best, the client continues its search down the list into one of the three continents.

  • 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

183
Managing roaming clients
Implementing roaming
Identifying servers for each hierarchical level
To identify servers for each hierarchical level, you must analyze the needs of
your roaming users. For example, you may need to identify mobile users based
on whether they travel internationally, throughout the country, or within a
smaller geographic area. If users travel internationally, their server lists will
contain the names of the country servers from level 0. If they travel within one
country only, their server lists will contain servers from level 1.
Depending on network speeds, the server list could contain only the top level
servers (level 0 in
Figure 6-1
). This simplifies building the clients’ server list.
The only limit to the number of levels that you can define is the text file size
limit of 512 characters.
Creating a list of 0 level Symantec AntiVirus servers
You can create the clients’ server list text file using a text editor such as
Notepad. The server list text file must contain lines in the following format:
<local><type of server><level><server list>
where:
<local> indicates to the client that this is the 0 level of servers that the client
should attempt to contact when searching for a roam server.
<type of server> is the server type, such as parent server, Quarantine Server,
Grc.dat server, or Alert server.
<level> is 0.
<server list> is the list of servers, which are separated by commas. (Spaces
between the commas are optional.)
For example, the clients’ server list text file that corresponds to
Figure 6-1
is as
follows:
<local> Parent 0 USASvr,EuropeSvr,AsiaSvr
This is the only line in the server list for the roaming clients in this example.
The list tells the clients to contact and compare response time from these three
servers only. Depending on which server is best, the client continues its search
down the list into one of the three continents.