McAfee EPOCDE-AA-BA Product Guide - Page 22

When to use multiple remote Agent Handlers, Server configuration overview

Page 22 highlights

2 Planning your ePolicy Orchestrator configuration Server configuration overview When to use multiple remote Agent Handlers Multiple remote Agent Handlers can help you manage large deployments without adding additional ePolicy Orchestrator servers to your environment. The Agent Handler is the component of your server responsible for managing agent requests. Each McAfee ePO server installation includes an Agent Handler by default. Some scenarios in which you might want to use multiple remote Agent Handlers include: • You want to allow agents to choose between multiple physical devices, so they can continue to call in and receive policy, task, and product updates; even if the application server is unavailable, and you don't want to cluster your ePolicy Orchestrator server. • Your existing ePolicy Orchestrator infrastructure needs to be expanded to handle more agents, more products, or a higher load due to more frequent agent-server communication intervals (ASCI). • You want to use your ePolicy Orchestrator server to manage disconnected network segments, such as systems that use Network Address Translation (NAT) or in an external network. This is functional as long as the Agent Handler has a high bandwidth connection to your ePolicy Orchestrator database. Multiple Agent Handlers can provide added scalability and lowered complexity in managing large deployments. However, because Agent Handlers require a very fast network connection, there are some scenarios in which you should not use them, including: • To replace distributed repositories. Distributed repositories are local file shares intended to keep agent communication traffic local. While Agent Handlers do have repository functionality built in, they require constant communication with your ePolicy Orchestrator database, and therefore consume a significantly larger amount of bandwidth. • To improve repository replication across a WAN connection. The constant communication back your database required by repository replication can saturate the WAN connection. • To connect a disconnected network segment where there is limited or irregular connectivity to the ePolicy Orchestrator database. Server configuration overview How you set up your ePolicy Orchestrator server depends on the unique needs of your environment. This process overview highlights the major setup and configuration required to use your ePolicy Orchestrator server. Each of the steps represents a chapter or section in this guide, where you can find the detailed information you need to understand the features and functionality of the software, along with the tasks needed to implement and use them. Depending on the size and complexity of your network, you might not need to configure all available features. 22 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

When to use multiple remote Agent Handlers
Multiple remote Agent Handlers can help you manage large deployments without adding additional
ePolicy Orchestrator servers to your environment.
The Agent Handler is the component of your server responsible for managing agent requests. Each
McAfee ePO server installation includes an Agent Handler by default. Some scenarios in which you
might want to use multiple remote Agent Handlers include:
You want to allow agents to choose between multiple physical devices, so they can continue to call
in and receive policy, task, and product updates; even if the application server is unavailable, and
you don't want to cluster your ePolicy Orchestrator server.
Your existing ePolicy Orchestrator infrastructure needs to be expanded to handle more agents,
more products, or a higher load due to more frequent agent-server communication intervals (ASCI).
You want to use your ePolicy Orchestrator server to manage disconnected network segments, such
as systems that use Network Address Translation (NAT) or in an external network.
This is functional as long as the Agent Handler has a high bandwidth
connection to your ePolicy Orchestrator database.
Multiple Agent Handlers can provide added scalability and lowered complexity in managing large
deployments. However, because Agent Handlers require a very fast network connection, there are
some scenarios in which you should not use them, including:
To replace distributed repositories. Distributed repositories are local file shares intended to keep
agent communication traffic local. While Agent Handlers do have repository functionality built in,
they require constant communication with your ePolicy Orchestrator database, and therefore
consume a significantly larger amount of bandwidth.
To improve repository replication across a WAN connection. The constant communication back your
database required by repository replication can saturate the WAN connection.
To connect a disconnected network segment where there is limited or irregular connectivity to the
ePolicy Orchestrator database.
Server configuration overview
How you set up your ePolicy Orchestrator server depends on the unique needs of your environment.
This process overview highlights the major setup and configuration required to use your ePolicy
Orchestrator server. Each of the steps represents a chapter or section in this guide, where you can find
the detailed information you need to understand the features and functionality of the software, along
with the tasks needed to implement and use them.
Depending on the size and complexity of your network, you might not
need to configure all available features.
2
Planning your ePolicy Orchestrator configuration
Server configuration overview
22
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide