McAfee EPOCDE-AA-BA Product Guide - Page 203

Update tasks, Updating managed systems regularly with a scheduled update task

Page 203 highlights

Using tasks to manage products and systems Client tasks and what they do 16 11 On the Schedule page, select whether the schedule is enabled, and specify the schedule details, then click Next. 12 Review the summary, then click Save. Update tasks Once an update package has been checked in to the master repository and replicated to the distributed repositories, the agents on the managed systems still need to know when to go to the distributed repositories for updates. If you are using global updating, this is not necessary. You can create and configure update client tasks to control when and how managed systems receive update packages. If you are not using global updating, creating these tasks are the only way you can control client updating with the ePolicy Orchestrator software. If you are using global updating, this task is not necessary, although you can create a daily task for redundancy. Considerations when creating update client tasks Consider the following when scheduling client update tasks: • Create a daily Update client task that the highest level of the System Tree that is inherited by all systems. If your organization is large, you can use randomization intervals to mitigate the bandwidth impact. Also, for large networks with offices in different time zones, help balance network load by running the task at the local system time on the managed system, rather than at the same time for all systems. • Schedule the task at least an hour after the scheduled replication task, if you are using scheduled replication tasks. • Run update tasks for DAT and engine files at least once a day. Managed systems might be logged off from the network and miss the scheduled task. Running the task frequently ensures these systems receive the update. • Maximize bandwidth efficiency and create several scheduled client update tasks that update separate components and run at different times. For example, you can create one task to update only DAT files, then create another to update both DAT and engine files weekly or monthly (engine packages are released less frequently). • Create and schedule additional tasks to update products that do not use the agent for Windows. • Create a task to update your main workstation applications, such as VirusScan Enterprise, to ensure they all receive the update files. Schedule it to run daily or several times a day. Updating managed systems regularly with a scheduled update task Use this task to create and configure update tasks. If you are not using global updating, McAfee recommends using a daily Update client task to ensure systems are up-to-date with the latest DAT and engine files. Task For option definitions, click ? in the interface. 1 Click Menu | Policy | Client Task Catalog, select McAfee Agent | Product Update as Client Task Types, then click Actions | New Task. The New Task dialog box appears. 2 Ensure that Product Update is selected, then click OK. 3 Type a name for the task you are creating and add any notes. McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide 203

  • 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

11
On the Schedule page, select whether the schedule is enabled, and specify the schedule details,
then click
Next
.
12
Review the summary, then click
Save
.
Update tasks
Once an update package has been checked in to the master repository and replicated to the
distributed repositories, the agents on the managed systems still need to know when to go to the
distributed repositories for updates. If you are using global updating, this is not necessary.
You can create and configure update client tasks to control when and how managed systems receive
update packages. If you are not using global updating, creating these tasks are the only way you can
control client updating with the ePolicy Orchestrator software.
If you are using global updating, this task is not necessary, although you can create a daily task for
redundancy.
Considerations when creating update client tasks
Consider the following when scheduling client update tasks:
Create a daily Update client task that the highest level of the System Tree that is inherited by all
systems. If your organization is large, you can use randomization intervals to mitigate the
bandwidth impact. Also, for large networks with offices in different time zones, help balance
network load by running the task at the local system time on the managed system, rather than at
the same time for all systems.
Schedule the task at least an hour after the scheduled replication task, if you are using scheduled
replication tasks.
Run update tasks for DAT and engine files at least once a day. Managed systems might be logged
off from the network and miss the scheduled task. Running the task frequently ensures these
systems receive the update.
Maximize bandwidth efficiency and create several scheduled client update tasks that update
separate components and run at different times. For example, you can create one task to update
only DAT files, then create another to update both DAT and engine files weekly or monthly (engine
packages are released less frequently).
Create and schedule additional tasks to update products that do not use the agent for Windows.
Create a task to update your main workstation applications, such as VirusScan Enterprise, to
ensure they all receive the update files. Schedule it to run daily or several times a day.
Updating managed systems regularly with a scheduled update task
Use this task to create and configure update tasks. If you are not using global updating, McAfee
recommends using a daily Update client task to ensure systems are up-to-date with the latest DAT
and engine files.
Task
For option definitions, click
?
in the interface.
1
Click
Menu
|
Policy
|
Client Task Catalog
, select
McAfee Agent
|
Product Update
as Client Task Types, then click
Actions
|
New Task
. The New Task dialog box appears.
2
Ensure that
Product Update
is selected, then click
OK
.
3
Type a name for the task you are creating and add any notes.
Using tasks to manage products and systems
Client tasks and what they do
16
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide
203