McAfee EPOCDE-AA-BA Product Guide - Page 191

Deploying update packages automatically with global updating, Requirements

Page 191 highlights

Using tasks to manage products and systems Server tasks and what they do 16 Requirements These requirements must be met to implement global updating: • A SuperAgent must use the same agent-server secure communication (ASSC) key as the agents that receive its wake-up call. • A SuperAgent is installed on each broadcast segment. Managed systems cannot receive a SuperAgent wake-up call if there is no SuperAgent on the same broadcast segment. Global updating uses the SuperAgent wake-up call to alert agents that new updates are available. • Distributed repositories are set up and configured throughout your environment. McAfee recommends SuperAgent repositories, but they are not required. Global updating functions with all types of distributed repositories. • If using SuperAgent repositories, managed systems must be able to "see" the repository from which it updates. Although a SuperAgent is required on each broadcast segment for systems to receive the wake-up call, SuperAgent repositories are not required on each broadcast segment. The managed systems, however, must "see" the SuperAgent repository from which to update. Deploying update packages automatically with global updating Use this task to enable global updating on the server. Global updating automatically deploys user-specified update packages to managed systems. Task For option definitions, click ? in the interface. 1 Click Menu | Configuration | Server Settings, select Global Updating, then click Edit at the bottom of the page. Figure 16-1 Edit Global Updating page 2 On the Edit Global Updating page next to Status, select Enabled. 3 Edit the Randomization interval, if desired. Each client update occurs at a randomly selected time within the randomization interval, which helps distribute network load. The default is 20 minutes. For example, if you update 1000 clients using the default randomization interval of 20 minutes, roughly 50 clients update each minute during the interval, lowering the load on your network and on your server. Without the randomization, all 1000 clients would try to update simultaneously. McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide 191

  • 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
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328

Requirements
These requirements must be met to implement global updating:
A SuperAgent must use the same agent-server secure communication (ASSC) key as the agents
that receive its wake-up call.
A SuperAgent is installed on each broadcast segment. Managed systems cannot receive a
SuperAgent wake-up call if there is no SuperAgent on the same broadcast segment. Global
updating uses the SuperAgent wake-up call to alert agents that new updates are available.
Distributed repositories are set up and configured throughout your environment. McAfee
recommends SuperAgent repositories, but they are not required. Global updating functions with all
types of distributed repositories.
If using SuperAgent repositories, managed systems must be able to “see” the repository from
which it updates. Although a SuperAgent is required on each broadcast segment for systems to
receive the wake-up call, SuperAgent repositories are not required on each broadcast segment. The
managed systems, however, must “see” the SuperAgent repository from which to update.
Deploying update packages automatically with global updating
Use this task to enable global updating on the server. Global updating automatically deploys
user-specified update packages to managed systems.
Task
For option definitions, click
?
in the interface.
1
Click
Menu
|
Configuration
|
Server Settings
, select
Global Updating
, then click
Edit
at the bottom of the page.
Figure 16-1
Edit Global Updating page
2
On the Edit Global Updating page next to
Status
, select
Enabled
.
3
Edit the
Randomization interval
, if desired.
Each client update occurs at a randomly selected time within the randomization interval, which
helps distribute network load. The default is
20 minutes
.
For example, if you update 1000 clients using the default randomization interval of 20 minutes,
roughly 50 clients update each minute during the interval, lowering the load on your network and
on your server. Without the randomization, all 1000 clients would try to update simultaneously.
Using tasks to manage products and systems
Server tasks and what they do
16
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide
191