Checking In Engine, Dat And Extradat Update Packages Manually - McAfee EPOLICY ORCHESTRATOR 4.5 Product Manual

Deploying Software and Updates

Checking in engine, DAT and ExtraDAT update packages manually

The type Local indicates it is not managed by ePolicy Orchestrator. When a nonmanaged
repository is selected in the Repository list, the Edit and Delete buttons are enabled.
k Click Save.
Any system where this policy is applied receives the new policy at the next agent-server
communication.
Checking in engine, DAT and ExtraDAT update
packages manually
Use this task to manually check in the update packages to the master repository, to deploy
them using ePolicy Orchestrator. Some packages can only be checked in manually.
Before you begin
You must have appropriate permissions to perform this task.
NOTE: You cannot check in packages while pull or replication tasks are running.
Task
For option definitions, click ? in the interface.
1 Click Menu | Software | Master Repository, then click Actions | Check In Package.
The Check In Package wizard opens.
2 Select the package type, then browse to and select the desired package file.
3 Click Next. The Package Options page appears.
4 Select a branch:
• Current — Use the packages without testing them first.
• Evaluation — Used to test the packages in a lab environment first.
NOTE:
by clicking Menu | Software | Master Repository.
• Previous — Use the previous version to receive the package.
5 Next to Options, select whether to:
• Move the existing package to the Previous branch — Select this option to move
the existing package (of the same type that you are checking in) to the Previous branch.
6 Click Save to begin checking in the package. Wait while the package is checked in.
The new package appears in the Packages in Master Repository list on the Master Repository
page.
McAfee ePolicy Orchestrator 4.5 Product Guide
Once you finish testing the packages, you can move them to the Current branch
189