McAfee EPOCDE-AA-BA Product Guide - Page 286

Renaming subnets, Viewing detected subnets and their details

Page 286 highlights

21 Detecting Rogue Systems Rogue System Detection command-line options Task 1 Click Menu | Reporting | Queries & Reports, and query for any ignored subnets. For more information on working with queries, see Reporting on System Status. 2 On the Unsaved Queries page, click Include. 3 In the Include dialog box, click OK. Renaming subnets Use this task to rename subnets. This task can be performed from: Detected Subnets Details page Detected Subnets page Getting there Click Menu | Systems | Detected Systems, click any subnet category in the Subnet Status monitor, then click any subnet. Click Menu | Systems | Detected Systems, then click any subnet category in the Subnet Status monitor. For option definitions, click ? in the interface. Task 1 Select the subnet you want to rename, then click Actions and select Detected Systems | Rename. 2 In the Rename dialog box, type the new name for the subnet, then click OK. Viewing detected subnets and their details Use this task to view detected subnets and their details. You can view detected subnets details from any page that displays detected subnets. For option definitions, click ? in the interface. Task 1 Click Menu | Systems | Detected Systems. 2 In the Subnet Status monitor, click any category to view the list of detected subnets it contains, such as Covered. The Detected Subnets page appears and displays the subnets in that category. 3 Click any detected subnet to view its details. The Detected Subnet Details page appears. Rogue System Detection command-line options You can run command-line options from the client system. You can start the sensor manually from the command-line instead of starting it as a Windows service. You might want to do this if you are testing functionality, or to check the sensor version. The following table lists the run-time command-line options for the sensor. Switch --console --help --install Description Forces the sensor to run as a normal command-line executable; otherwise it must be run as an NT service. Prints the Help screen and lists available command-line options. Registers the sensor with the Windows Service Control Manager. 286 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

Task
1
Click
Menu
|
Reporting
|
Queries & Reports
, and query for any ignored subnets. For more information on
working with queries, see
Reporting on System Status.
2
On the Unsaved Queries page, click
Include
.
3
In the Include dialog box, click
OK
.
Renaming subnets
Use this task to rename subnets.
This task can be performed
from:
Getting there
Detected Subnets Details page
Click
Menu
|
Systems
|
Detected Systems
, click any subnet category in
the Subnet Status monitor, then click any subnet.
Detected Subnets page
Click
Menu
|
Systems
|
Detected Systems
, then click any subnet category
in the Subnet Status monitor.
For option definitions, click
?
in the interface.
Task
1
Select the subnet you want to rename, then click
Actions
and select
Detected Systems
|
Rename
.
2
In the Rename dialog box, type the new name for the subnet, then click
OK
.
Viewing detected subnets and their details
Use this task to view detected subnets and their details. You can view detected subnets details from
any page that displays detected subnets.
For option definitions, click
?
in the interface.
Task
1
Click
Menu
|
Systems
|
Detected Systems
.
2
In the Subnet Status monitor, click any category to view the list of detected subnets it contains,
such as
Covered
. The Detected Subnets page appears and displays the subnets in that category.
3
Click any detected subnet to view its details. The Detected Subnet Details page appears.
Rogue System Detection command-line options
You can run command-line options from the client system. You can start the sensor manually from the
command-line instead of starting it as a Windows service. You might want to do this if you are testing
functionality, or to check the sensor version. The following table lists the run-time command-line
options for the sensor.
Switch
Description
--console
Forces the sensor to run as a normal command-line executable; otherwise it
must be run as an NT service.
--help
Prints the Help screen and lists available command-line options.
--install
Registers the sensor with the Windows Service Control Manager.
21
Detecting Rogue Systems
Rogue System Detection command-line options
286
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide