Adaptec 5325301656 Administration Guide - Page 132

To Distribute Files via UNC, For other SMB/CIFS

Page 132 highlights

Signature Updates To Distribute Files via UNC If you have more than one Snap Server with no Internet access, you can perform the previous procedure on just one of them (or any Windows/SMB server), and then configure your other Snap Servers to get the update from that server automatically via UNC. Notes The following conditions must be met in order to distribute updates using UNC: • The correct Signature files must have been downloaded to the root of the share being used for updates. • For GuardianOS servers, the server containing the Signature updates must have the Guest account enabled (Network > Windows). For other SMB/CIFS servers, there may be additional requirements. • The share and Signature files must be accessible to the Guest account. • The server name used in the UNC must be resolvable by the server running CA Antivirus. 1 Navigate to Scanner > Signature Update Options, and click the Incoming tab. 2 Click the Add button, and select UNC in the Method list box. 3 Enter the path to the Snap Server (or Windows/SMB server) to which the update files have been downloaded (see previous procedure) using the following format: \\server_name\share_name where server_name is the name of the server, and share_name is the name of the share providing access to the files. (On a Snap Server, the update files must reside on the root of the share.) 4 Click OK. The path you entered appears in the Download Sources list box. 5 Click Download Now. To Distribute Files via FTP If you have more than one Snap Server with no Internet access, you can perform the FTP download procedure on just one of them (or any FTP server), and then configure your other Snap Servers to get the signature updates from that server automatically via FTP. 1 Navigate to Scanner > Signature Update Options, and click the Incoming tab. 2 Click the Add button, and select FTP in the Method list box. 118 Snap Server Administrator Guide

  • 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
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224

Signature Updates
118
Snap Server Administrator Guide
To Distribute Files via UNC
If you have more than one Snap Server with no Internet access, you can perform the
previous procedure on just one of them (or any Windows/SMB server), and then
configure your other Snap Servers to get the update from that server automatically
via UNC.
Notes
The following conditions must be met in order to distribute updates using
UNC:
The correct Signature files must have been downloaded to the root of the share
being used for updates.
For GuardianOS servers, the server containing the Signature updates must
have the Guest account enabled (
Network > Windows
). For other SMB/CIFS
servers, there may be additional requirements.
The share and Signature files must be accessible to the Guest account.
The server name used in the UNC must be resolvable by the server running
CA Antivirus.
1
Navigate to
Scanner > Signature Update Options
, and click the
Incoming
tab.
2
Click the
Add
button, and select
UNC
in the Method list box.
3
Enter the path to the Snap Server (or Windows/SMB server) to which the update
files have been downloaded (see previous procedure) using the following format:
\\server_name\share_name
where
server_name
is the name of the server, and
share_name
is the name of the
share providing access to the files. (On a Snap Server, the update files must reside
on the root of the share.)
4
Click
OK
. The path you entered appears in the Download Sources list box.
5
Click
Download Now
.
To Distribute Files via FTP
If you have more than one Snap Server with no Internet access, you can perform the
FTP download procedure on just one of them (or any FTP server), and then
configure your other Snap Servers to get the signature updates from that server
automatically via FTP.
1
Navigate to
Scanner > Signature Update Options
, and click the
Incoming
tab.
2
Click the
Add
button, and select
FTP
in the Method list box.