cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Client - Initial Deployment Source

Jump to solution

Hey,

We have had to move from ePO SaaS to On-Prem, for encryption requirements The SaaS deployment was smooth, install ePO agent on the endpoint, the rest of the suite then downloaded from McAfee source and done.

We now have on on-prem ePO with an AH in the DMZ, firewall rules in place and any clients that have the new ePO agent installed on then register with the new server.

However we have clients that will never connect to the corporate network, either directly of via VPN. We would rather not set up a repository in the DMZ and wondered if it was possible to use a McAfee source as a failback to handle the initial product deployment tasks?

 

Rottie

1 Solution

Accepted Solutions
aguevara
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 5

Re: Client - Initial Deployment Source

Jump to solution

there is no way for MA to take product deployments from Mvision ePO nor ePO cloud if its managed by an on prem ePO.

 

If those machines do not communicate to the ePO server on the internal network but they do communicate to the Remote Agent handler on DMZ then the deployment will work via the Remote Agent handler as the handler caches an exact copy of the master repository in ePO, this is done automatically and there is no need to create a replication task or add an extra repository

View solution in original post

4 Replies
vivs
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 5

Re: Client - Initial Deployment Source

Jump to solution

Hello @Rotti3man 

Thanks for your response.

From fallback site you can get the signatures like DAT/AMCORE .

For Product deployment you need to make sure that the client machine is connecting through ePO.

Was my reply helpful?

If you find this post useful, please give it a KudosAlso, please don't forget to select "Accept as a Solution" if this reply resolves your query!

Re: Client - Initial Deployment Source

Jump to solution

Hi Vivs,


Thanks for the response, the question is if the remote clients do not connect to internal network, they  talk to the ePO server only via an AH, how does the initial deployment work?

Are we able to configure our on-prem to point clients to the same deployment repository the SaaS uses?
Or can the AH also be set as a SuperAgent and cache the install?

Regards,

Rottie

aguevara
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 5

Re: Client - Initial Deployment Source

Jump to solution

there is no way for MA to take product deployments from Mvision ePO nor ePO cloud if its managed by an on prem ePO.

 

If those machines do not communicate to the ePO server on the internal network but they do communicate to the Remote Agent handler on DMZ then the deployment will work via the Remote Agent handler as the handler caches an exact copy of the master repository in ePO, this is done automatically and there is no need to create a replication task or add an extra repository

View solution in original post

Re: Client - Initial Deployment Source

Jump to solution

Hi Aguevara,

Thanks for confirming.

Last week the AH was not deplying anything, saying no packages available. However I have just tried a re-install of the agent and the packages are now downloading and installing.

Many thanks for your help.

Rottie

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community