McAfee EPOCDE-AA-BA Product Guide - Page 190

Server tasks and what they do, Global updating, Global updating process

Page 190 highlights

16 Using tasks to manage products and systems Server tasks and what they do Server tasks and what they do Server tasks are configurable actions that run on your ePolicy Orchestrator server on a schedule. You can leverage server tasks to help automate repetitive server tasks that need to be performed on your server. McAfee ePO software includes preconfigured server tasks and actions by default. Most of the additional software products you manage with your ePolicy Orchestrator server also add preconfigured server tasks. Global updating McAfee recommends using global updating as part of your updating strategy. Global updating automates replication to your distributed repositories and keeping your managed systems up-to-date. Replication and update tasks are not required. Checking contents in to your master repository initiates a global update. The entire process should finish within an hour in most environments. Additionally, you can specify which packages and updates initiate a global update. However, when you only specify that certain content initiates a global update, ensure that you create a replication task to distribute content that was not selected to initiate a global update. When using global updating, McAfee recommends scheduling a regular pull task (to update the master repository) at a time when network traffic is minimal. Although global updating is much faster than other methods, it increases network traffic during the update. Global updating process Most environments can be updated within an hour using this Global updating process: 1 Contents are checked in to the master repository. 2 The server performs an incremental replication to all distributed repositories. 3 The server issues a SuperAgent wake-up call to all SuperAgents in the environment. 4 The SuperAgent broadcasts a global update message to all agents within the SuperAgent subnet. 5 Upon receipt of the broadcast, the agent is supplied with a minimum catalog version needed for updating. 6 The agent searches the distributed repositories for a site that has this minimum catalog version. 7 Once a suitable repository is found, the agent runs the update task. If the agent does not receive the broadcast for any reason, such as when the client computer is turned off, or there are no SuperAgents, at the next ASCI, the minimum catalog version is supplied, which starts the process. If the agent receives notification from a SuperAgent, the agent is supplied with the list of updated packages. If the agent finds the new catalog version at the next ASCI, it is not supplied with the list of packages to update, and therefore updates all packages available. 190 McAfee® ePolicy Orchestrator® 4.6.0 Software Product 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
  • 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

Server tasks and what they do
Server tasks are configurable actions that run on your ePolicy Orchestrator server on a schedule. You
can leverage server tasks to help automate repetitive server tasks that need to be performed on your
server.
McAfee ePO software includes preconfigured server tasks and actions by default. Most of the additional
software products you manage with your ePolicy Orchestrator server also add preconfigured server tasks.
Global updating
McAfee recommends using global updating as part of your updating strategy. Global updating
automates replication to your distributed repositories and keeping your managed systems up-to-date.
Replication and update tasks are not required. Checking contents in to your master repository initiates
a global update. The entire process should finish within an hour in most environments.
Additionally, you can specify which packages and updates initiate a global update. However, when you
only specify that certain content initiates a global update, ensure that you create a replication task to
distribute content that was not selected to initiate a global update.
When using global updating, McAfee recommends scheduling a regular
pull task (to update the master repository) at a time when network
traffic is minimal. Although global updating is much faster than other
methods, it increases network traffic during the update.
Global updating process
Most environments can be updated within an hour using this Global updating process:
1
Contents are checked in to the master repository.
2
The server performs an incremental replication to all distributed repositories.
3
The server issues a SuperAgent wake-up call to all SuperAgents in the environment.
4
The SuperAgent broadcasts a global update message to all agents within the SuperAgent subnet.
5
Upon receipt of the broadcast, the agent is supplied with a minimum catalog version needed for
updating.
6
The agent searches the distributed repositories for a site that has this minimum catalog version.
7
Once a suitable repository is found, the agent runs the update task.
If the agent does not receive the broadcast for any reason, such as when the client computer is turned
off, or there are no SuperAgents, at the next ASCI, the minimum catalog version is supplied, which
starts the process.
If the agent receives notification from a SuperAgent, the agent is
supplied with the list of updated packages. If the agent finds the new
catalog version at the next ASCI, it is not supplied with the list of
packages to update, and therefore updates all packages available.
16
Using tasks to manage products and systems
Server tasks and what they do
190
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide