McAfee EPOCDE-AA-BA Product Guide - Page 131

Group Details, My Organization group's

Page 131 highlights

Organizing the System Tree How a system is added to the System Tree when sorted 12 The sorting order assigned to each subgroup (defined in the Group Details tab) determines the order that subgroups are considered by the server when it searches for a group with matching criteria. 1 The server searches for a system without an agent GUID (its agent has never called in before) with a matching name in a group with the same name as the domain. If found, the system is placed in that group. This can happen after the first Active Directory or NT domain synchronization, or when you have manually added systems to the System Tree. 2 If a matching system is still not found, the server searches for a group of the same name as the domain where the system originates. If such a group is not found, one is created under the Lost&Found group, and the system is placed there. 3 Properties are updated for the system. 4 The server applies all criteria-based tags to the system if the server is configured to run sorting criteria at each agent-server communication. 5 What happens next depends on whether System Tree sorting is enabled on both the server and the system. • If System Tree sorting is disabled on either the server or the system, the system is left where it is. • If System Tree sorting is enabled on the server and system, the system is moved based on the sorting criteria in the System Tree groups. Systems that are added by Active Directory or NT Domain synchronization have System Tree sorting disabled by default, so they are not sorted on the first agent-server communication 6 The server considers the sorting criteria of all top-level groups according to the sorting order on the My Organization group's Group Details tab. The system is placed in the first group with matching criteria or a catch-all group it considers. • Once sorted into a group, each of its subgroups are considered for matching criteria according to their sorting order on the Group Details tab. • This continues until there is no subgroup with matching criteria for the system, and is placed in the last group found with matching criteria. 7 If such a top-level group is not found, the subgroups of top-level groups (without sorting criteria) are considered according to their sorting. 8 If such a second-level criteria-based group is not found, the criteria-based third-level groups of the second-level unrestricted groups are considered. Subgroups of groups with criteria that doesn't match are not considered. A group must have matching criteria or have no criteria in order for its subgroups to be considered for a system. 9 This process continues down through the System Tree until a system is sorted into a group. If the server setting for System Tree sorting is configured to sort only on the first agent-server communication, a flag is set on the system. The flag means that the system can never be sorted again at agent-server communication unless the server setting is changed to enable sorting on every agent-server communication. 10 If the server cannot sort the system into any group, it is placed in the Lost&Found group within a subgroup that is named after its domain. McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide 131

  • 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

The sorting order assigned to each subgroup (defined in the
Group Details
tab) determines the order that
subgroups are considered by the server when it searches for a group with matching criteria.
1
The server searches for a system without an agent GUID (its agent has never called in before) with
a matching name in a group with the same name as the domain. If found, the system is placed in
that group. This can happen after the first Active Directory or NT domain synchronization, or when
you have manually added systems to the System Tree.
2
If a matching system is still not found, the server searches for a group of the same name as the
domain where the system originates. If such a group is not found, one is created under the
Lost&Found group, and the system is placed there.
3
Properties are updated for the system.
4
The server applies all criteria-based tags to the system if the server is configured to run sorting
criteria at each agent-server communication.
5
What happens next depends on whether System Tree sorting is enabled on both the server and the
system.
If System Tree sorting is disabled on either the server or the system, the system is left where it
is.
If System Tree sorting is enabled on the server and system, the system is moved based on the
sorting criteria in the System Tree groups.
Systems that are added by Active Directory or NT Domain
synchronization have System Tree sorting disabled by default, so they
are not sorted on the first agent-server communication
6
The server considers the sorting criteria of all top-level groups according to the sorting order on the
My Organization group’s
Group Details
tab. The system is placed in the first group with matching
criteria or a catch-all group it considers.
Once sorted into a group, each of its subgroups are considered for matching criteria according
to their sorting order on the Group Details tab.
This continues until there is no subgroup with matching criteria for the system, and is placed in
the last group found with matching criteria.
7
If such a top-level group is not found, the subgroups of top-level groups (without sorting criteria)
are considered according to their sorting.
8
If such a second-level criteria-based group is not found, the criteria-based third-level groups of the
second-level unrestricted groups are considered.
Subgroups of groups with criteria that doesn't match are not considered.
A group must have matching criteria or have no criteria in order for its
subgroups to be considered for a system.
9
This process continues down through the System Tree until a system is sorted into a group.
If the server setting for System Tree sorting is configured to sort only on
the first agent-server communication, a flag is set on the system. The
flag means that the system can never be sorted again at agent-server
communication unless the server setting is changed to enable sorting on
every agent-server communication.
10
If the server cannot sort the system into any group, it is placed in the Lost&Found group within a
subgroup that is named after its domain.
Organizing the System Tree
How a system is added to the System Tree when sorted
12
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide
131