McAfee EPOCDE-AA-BA Product Guide - Page 198

Avoiding replication of selected packages, Allowed Cron syntax when scheduling a server task

Page 198 highlights

16 Using tasks to manage products and systems Server tasks and what they do 3 On the Replication Type, select Incremental replication or Full replication, then click Next. If this is the first time you are replicating to a distributed repository, it is a full replication even if you select incremental replication. 4 On the Summary page, review the details then click Start Replication. The Server Task Log page displays the status of the task until it is complete. Replication time depends on the changes to the master repository and the number of distributed repositories to which you are replicating. After the task is complete, you can initiate an immediate client update task so that managed systems in other locations can get updates from the distributed repositories. Avoiding replication of selected packages If distributed repositories are set up to replicate only selected packages, your newly checked-in package is replicated by default. Depending on your requirements for testing and validating, you might want to avoid replicating some packages to your distributed repositories. Use this task to avoid replicating a newly checked-in package. For option definitions, click ? in the interface. Task 1 Click Menu | Software | Distributed Repositories, then click on the desired repository. The Distributed Repository Builder wizard opens. 2 On the Package Types page, deselect the package that you want to avoid being replicated. 3 Click Save. Allowed Cron syntax when scheduling a server task Cron syntax is made up of six or seven fields, separated by a space. Accepted Cron syntax, by field in descending order, is detailed in the following table. Most Cron syntax is acceptable, but a few cases are not supported. For example, you cannot specify both the Day of Week and Day of Month values. Field Name Seconds Minutes Hours Day of Month Month Day of Week Year (optional) Allowed Values 0 - 59 0 - 59 0 - 23 1 - 31 1 - 12, or JAN - DEC 1 - 7, or SUN - SAT Empty, or 1970 - 2099 Allowed Special Characters L W C L C # , - * / Notes on allowed special characters • Commas (,) are allowed to specify additional values. For example, "5,10,30" or "MON,WED,FRI". • Asterisks (*) are used for "every." For example, "*" in the minutes field is "every minute". • Question marks (?) are allowed to specify no specific value in the Day of Week or Day of Month fields. The question mark must be used in one of these fields, but cannot be used in both. 198 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

3
On the Replication Type, select
Incremental replication
or
Full replication
, then click
Next
.
If this is the first time you are replicating to a distributed repository, it is
a full replication even if you select incremental replication.
4
On the Summary page, review the details then click
Start Replication
.
The Server Task Log page displays the status of the task until it is complete. Replication time
depends on the changes to the master repository and the number of distributed repositories to
which you are replicating.
After the task is complete, you can initiate an immediate client update task so that managed
systems in other locations can get updates from the distributed repositories.
Avoiding replication of selected packages
If distributed repositories are set up to replicate only selected packages, your newly checked-in
package is replicated by default. Depending on your requirements for testing and validating, you
might want to avoid replicating some packages to your distributed repositories.
Use this task to avoid replicating a newly checked-in package.
For option definitions, click
?
in the interface.
Task
1
Click
Menu
|
Software
|
Distributed Repositories
, then click on the desired repository. The
Distributed Repository
Builder
wizard opens.
2
On the
Package Types
page, deselect the package that you want to avoid being replicated.
3
Click
Save
.
Allowed Cron syntax when scheduling a server task
Cron syntax is made up of six or seven fields, separated by a space. Accepted Cron syntax, by field in
descending order, is detailed in the following table. Most Cron syntax is acceptable, but a few cases
are not supported. For example, you cannot specify both the Day of Week and Day of Month values.
Field Name
Allowed Values
Allowed Special Characters
Seconds
0 - 59
, - * /
Minutes
0 - 59
, - * /
Hours
0 - 23
, - * /
Day of Month
1 - 31
, - * ? / L W C
Month
1 - 12, or JAN - DEC
, - * /
Day of Week
1 - 7, or SUN - SAT
, - * ? / L C #
Year (optional)
Empty, or 1970 - 2099
, - * /
Notes on allowed special characters
Commas (,) are allowed to specify additional values. For example, "
5,10,30
" or "
MON,WED,FRI
".
Asterisks (*) are used for "every." For example, "
*
" in the minutes field is "every minute".
Question marks (?) are allowed to specify no specific value in the Day of Week or Day of Month fields.
The question mark must be used in one of these fields, but cannot be
used in both.
16
Using tasks to manage products and systems
Server tasks and what they do
198
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide