McAfee EPOCDE-AA-BA Product Guide - Page 151

Wake-up calls and tasks, SuperAgents and broadcast wake-up calls

Page 151 highlights

Working with the agent from the McAfee ePO server Agent-server communication 13 • Upload success (status code from McAfee ePO) • No package to receive (status code from McAfee ePO) • Agent needs to regenerate GUID (status code from McAfee ePO) Other results such as connection refused, failed to connect, connection timeout, or other errors causes the agent to retry immediately using the next connection method in the list. Wake-up calls and tasks The purpose of an agent wake-up call is to trigger an immediate agent-server communication rather than wait for the current agent-server communication interval to expire. There are two ways to issue a wake-up call: • Manually from the server - This is the most common approach and requires the agent wake-up communication port be open. • On a schedule set by the administrator - This approach is useful when agent-server communication is disabled. The administrator can create and deploy a wake-up task, which triggers a wake-up call on a schedule. Some reasons for issuing an agent wake-up call are: • You make a policy change that you want the agent to adopt immediately, without waiting for the ASCI to expire. • You created a new task that you want the agent to run immediately. • A query generated a report indicating that a client is out of compliance, and you want to test its status as part of a troubleshooting procedure. If you are have converted a particular Windows system to use as a SuperAgent, it can issue wake-up calls to designated network broadcast segments. SuperAgents distribute the bandwidth impact of the agent wake-up call, and help distribute network traffic. SuperAgents and broadcast wake-up calls If you operate in a Windows environment and plan to use agent wake-up calls to initiate agent-server communication, consider converting an agent on each network broadcast segment into a SuperAgent. SuperAgents distribute the bandwidth load of concurrent wake-up calls. Instead of sending agent wake-up calls from the server to every agent, the server sends the SuperAgent wake-up call to SuperAgents in the selected System Tree segment. The process is: 1 Server sends a wake-up call to all SuperAgents. 2 SuperAgents broadcast a wake-up call to all agents in the same broadcast segment. 3 All notified agents (regular agents notified by a SuperAgent and all SuperAgents) exchange data with the server. When you send a SuperAgent wake-up call, agents without an operating SuperAgent on their broadcast segment are not prompted to communicate with the server. McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide 151

  • 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

Upload success (status code from McAfee ePO)
No package to receive (status code from McAfee ePO)
Agent needs to regenerate GUID (status code from McAfee ePO)
Other results such as connection refused, failed to connect, connection timeout, or other errors causes
the agent to retry immediately using the next connection method in the list.
Wake-up calls and tasks
The purpose of an agent wake-up call is to trigger an immediate agent-server communication rather
than wait for the current agent-server communication interval to expire.
There are two ways to issue a wake-up call:
Manually from the server — This is the most common approach and requires the agent wake-up
communication port be open.
On a schedule set by the administrator — This approach is useful when agent-server
communication is disabled. The administrator can create and deploy a wake-up
task
, which triggers
a wake-up
call
on a schedule.
Some reasons for issuing an agent wake-up call are:
You make a policy change that you want the agent to adopt immediately, without waiting for the
ASCI to expire.
You created a new task that you want the agent to run immediately.
A query generated a report indicating that a client is out of compliance, and you want to test its
status as part of a troubleshooting procedure.
If you are have converted a particular Windows system to use as a SuperAgent, it can issue wake-up
calls to designated network broadcast segments. SuperAgents distribute the bandwidth impact of the
agent wake-up call, and help distribute network traffic.
SuperAgents and broadcast wake-up calls
If you operate in a Windows environment and plan to use agent wake-up calls to initiate agent-server
communication, consider converting an agent on each network broadcast segment into a SuperAgent.
SuperAgents distribute the bandwidth load of concurrent wake-up calls. Instead of sending agent
wake-up calls from the server to every agent, the server sends the SuperAgent wake-up call to
SuperAgents in the selected System Tree segment.
The process is:
1
Server sends a wake-up call to all SuperAgents.
2
SuperAgents broadcast a wake-up call to all agents in the same broadcast segment.
3
All notified agents (regular agents notified by a SuperAgent and all SuperAgents) exchange data
with the server.
When you send a SuperAgent wake-up call, agents without an operating SuperAgent on their
broadcast segment are not prompted to communicate with the server.
Working with the agent from the McAfee ePO server
Agent-server communication
13
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide
151