McAfee Super Agent Distributed Repository Creations!!

Hi Guys Welcome to elearninginfoit my name is rajesh i just inform about this video only for Training ,Tutorials and Education purpose More information about this video so read this description you will get everything about it

SuperAgent repositories

Use systems hosting SuperAgents as distributed repositories. SuperAgent repositories have several advantages over other types of distributed repositories:

Folder locations are created automatically on the host system before adding the repository to the repository list. File sharing is enabled automatically on the SuperAgent repository folder. SuperAgent repositories don’t require additional replication or updating credentials — account permissions are created when the agent is converted to a SuperAgent. Although functionality of SuperAgent broadcast wake-up calls requires a SuperAgent in each broadcast segment, this is not a requirement for functionality of the SuperAgent

repository. Managed systems only need to “see” the system hosting the repository.

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 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.

TIP: 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

ePolicy Orchestrator 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.

facebook page : https://www.facebook.com/elearninginfoit

twitter page : https://twitter.com/RajeshS87398051

Google plus: https://plus.google.com/u/0/100036861860929870179

blogger page : https://elearninginfoit.blogspot.in

youtube page : https://www.youtube.com/elearninginfoit linkdin page : https://in.linkedin.com/in/rajesh-sharma-90537179

https://www.instagram.com/elearninginfoit/

https://www.pinterest.com/elearninginfoit

https://vimeo.com/user57285849

https://elearninginfoit.wordpress.com/

https://www.reddit.com/user/elearninginfoit

https://www.flickr.com/people/147609185@N04/

http://www.tumblr.com/liked/by/elearninginfoit ... https://www.youtube.com/watch?v=Gb6s3qBMz4w