cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Level 7
Report Inappropriate Content
Message 1 of 21

Problem: Deploying Agent with RSD with Epolicy 4.6

Jump to solution

Hi,

I'm using Epolicy 4.6 with Agent 4.5.1810 and VSE 8.8.0.777.

When i push the Agent to a Client it works well, but when i create a automated answer for the RSD it starts the Deployment but fails to install because of a access denied.

Error copying the file "C:\Windows\Temp\mfe435183640.tmp\FramePkg.exe" to \\XXXXXX\ADMIN$\FramePkg.exe. Systemerror: Access denied

I tripplechecked the User Credentials. I have administrator rights on the clients and as i wrote it works when i manually make the push trough epo.

Any hints?

1 Solution

Accepted Solutions
Highlighted
Level 12
Report Inappropriate Content
Message 17 of 21

Re: Problem: Deploying Agent with RSD with Epolicy 4.6

Jump to solution

Install Extension and browse to c:\program files\McAfee\ePolicy Orchestrator\Installer\ePO\extensions and select rsd.zip

View solution in original post

20 Replies
Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 21

Re: Problem: Deploying Agent with RSD with Epolicy 4.6

Jump to solution

It seems that you can't access Admin$ share of the client machine which is pre-requisties for pushing the agent.

For the pre-requisites of agent deployment, please refer to KB#:KB56386.

From the ePO server, are you able to access Admin$ share of the client machine where you are trying to push the agent. Can we have screenshot?

Highlighted
Level 7
Report Inappropriate Content
Message 3 of 21

Re: Problem: Deploying Agent with RSD with Epolicy 4.6

Jump to solution

I can access the Admin$ Share with the User Credentials i put into the push. The Epolicy Server is in another domain as the Client, so Access without User/Password prompt directly from epo is not possible. And as i said, it works when i use the same credentials but don't let it push automaticaly with automatic responses but manually over "push agent" in the rsd. Here is the Screenshot, maybe it helps even if my Epolicy is german 😉

Nachricht geändert durch F-N on 24.05.11 02:38:07 CDT
Highlighted
Level 7
Report Inappropriate Content
Message 4 of 21

Re: Problem: Deploying Agent with RSD with Epolicy 4.6

Jump to solution

I'm still looking for answers.

Any ideas?

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 5 of 21

Re: Problem: Deploying Agent with RSD with Epolicy 4.6

Jump to solution

I apologize but I can't understand the screenshot because it's in non-english. Some of other readers may be able to help.

on 25/5/11 8:12:46 PM IST
Highlighted
Level 7
Report Inappropriate Content
Message 6 of 21

Re: Problem: Deploying Agent with RSD with Epolicy 4.6

Jump to solution

The screenshot wouldn't help at all.

The question is: Whats the difference between pushing an agent with automatic responses and pushing an agent manually? manually works, automatic does not although I'm doing exactly the same. This makes absolutley no sense ;(

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 7 of 21

Re: Problem: Deploying Agent with RSD with Epolicy 4.6

Jump to solution

I will suggest to replace the RSD extension (delete and install it).

Before deleting it, please backup the  RSD policies, detected systems, exceptions,blacklist, server settings if you have any custom one.

If that is not resolving then please open a case with support.

Highlighted
Level 7
Report Inappropriate Content
Message 8 of 21

Re: Problem: Deploying Agent with RSD with Epolicy 4.6

Jump to solution

Hi,

automated responses (AR) for RSD does not seem to work in EPO 4.6.

I have two installations of 4.6 and am not able to get a mail if RSD finds a rogue system.

Please see also https://community.mcafee.com/message/184656 - same problem there.

There is also a work-around for your problem.

Pfüti,

Jens

Highlighted
Level 7
Report Inappropriate Content
Message 9 of 21

Re: Problem: Deploying Agent with RSD with Epolicy 4.6

Jump to solution

So the workaround is to give the Epolicy Orchestrator Service a Domain Admin Account instead of the Standard System Account. I will try this one out today and report back.

Thank you for the hint @jey

Nachricht geändert durch F-N on 27.05.11 04:35:54 CDT
Highlighted

Re: Problem: Deploying Agent with RSD with Epolicy 4.6

Jump to solution

Did you try to implement the solution you mentioned above , in  post # 8? Curious..

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