McAfee EPOCDE-AA-BA Product Guide - Page 80

Repository branches and their purposes, FTP repositories, UNC share repositories

Page 80 highlights

8 Setting up repositories Repository types and what they do FTP repositories You can use an FTP server to host a distributed repository. Use FTP server software, such as Microsoft Internet Information Services (IIS), to create a new folder and site location for the distributed repository. See your web server documentation for details. HTTP repositories You can use an HTTP server to host a distributed repository. Use HTTP server software, such as Microsoft IIS, to create a new folder and site location for the distributed repository. See your web server documentation for details. UNC share repositories You can create a UNC shared folder to host a distributed repository on an existing server. Be sure to enable sharing across the network for the folder, so that the McAfee ePO server can copy files to it and agents can access it for updates. Unmanaged repositories If you are unable to use managed distributed repositories, ePolicy Orchestrator administrators can create and maintain distributed repositories that are not managed by ePolicy Orchestrator. If a distributed repository is not managed, a local administrator must keep it up-to-date manually. Once the distributed repository is created, use ePolicy Orchestrator to configure managed systems of a specific System Tree group to update from it. Refer to Enabling the agent on unmanaged McAfee products so that they work with ePolicy Orchestrator for configuration of unmanaged systems. McAfee recommends that you manage all distributed repositories through ePolicy Orchestrator. This and using global updating, or scheduled replication tasks frequently, ensures your managed environment is up-to-date. Use unmanaged distributed repositories only if your network or organizational policy do not allow managed distributed repositories. Repository branches and their purposes The ePolicy Orchestratorsoftware provides three repository branches, allowing you to maintain three versions of all packages in your master and distributed repositories. The repository branches are Current, Previous, and Evaluation. By default, ePolicy Orchestrator uses only the Current branch. You can specify branches when adding packages to your master repository. You can also specify branches when running or scheduling update and deployment tasks, to distribute different versions to different parts of your network. Update tasks can retrieve updates from any branch of the repository, but you must select a branch other than the Current branch when checking in packages to the master repository. If a non-Current branch is not configured, the option to select a branch other than Current does not appear. To use the Evaluation and Previous branches for packages other than updates, you must configure this in the Repository Packages server settings. Agent versions 3.6 and earlier can retrieve update packages only from the Evaluation and Previous branches. 80 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

FTP repositories
You can use an FTP server to host a distributed repository. Use FTP server software, such as Microsoft
Internet Information Services (IIS), to create a new folder and site location for the distributed
repository. See your web server documentation for details.
HTTP repositories
You can use an HTTP server to host a distributed repository. Use HTTP server software, such as
Microsoft IIS, to create a new folder and site location for the distributed repository. See your web
server documentation for details.
UNC share repositories
You can create a UNC shared folder to host a distributed repository on an existing server. Be sure to
enable sharing across the network for the folder, so that the McAfee ePO server can copy files to it and
agents can access it for updates.
Unmanaged repositories
If you are unable to use managed distributed repositories, ePolicy Orchestrator administrators can
create and maintain distributed repositories that are not managed by ePolicy Orchestrator.
If a distributed repository is not managed, a local administrator must keep it up-to-date manually.
Once the distributed repository is created, use ePolicy Orchestrator to configure managed systems of a
specific System Tree group to update from it.
Refer to
Enabling the agent on unmanaged McAfee products so that they
work with ePolicy Orchestrator
for configuration of unmanaged systems.
McAfee recommends that you manage all distributed repositories
through ePolicy Orchestrator. This and using global updating, or
scheduled replication tasks frequently, ensures your managed
environment is up-to-date. Use unmanaged distributed repositories only
if your network or organizational policy do not allow managed distributed
repositories.
Repository branches and their purposes
The ePolicy Orchestratorsoftware provides three repository branches, allowing you to maintain three
versions of all packages in your master and distributed repositories.
The repository branches are Current, Previous, and Evaluation. By default, ePolicy Orchestrator uses
only the Current branch. You can specify branches when adding packages to your master repository.
You can also specify branches when running or scheduling update and deployment tasks, to distribute
different versions to different parts of your network.
Update tasks can retrieve updates from any branch of the repository, but you must select a branch
other than the Current branch when checking in packages to the master repository. If a non-Current
branch is not configured, the option to select a branch other than Current does not appear.
To use the Evaluation and Previous branches for packages other than updates, you must configure this
in the Repository Packages server settings. Agent versions 3.6 and earlier can retrieve update
packages only from the Evaluation and Previous branches.
8
Setting up repositories
Repository types and what they do
80
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide