cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
LeoM
Level 7
Report Inappropriate Content
Message 1 of 4

Problem deploying McAfee Agent 5.5 to Persistent Windows VDI

Hello all,

 

We are experiencing an issue deploying McAfee Agent 5.5 within ePO 5.9.1 to persistent virtual machines and obtain the following error.

 

"Failed to authenticate with remote system, system error: The network path was not found."
 
I found an article of someone previously experiencing the same problem (https://community.mcafee.com/t5/ePolicy-Orchestrator/Problem-deploying-McAfee-Agent-5-0-1-to-Windows...) and was successfully able to follow the UNC path from ePO server to target host (\\hostname\admin$) with no problem.  I also do have the correct permission and yet receiving the above error.
 
Greatly appreciate the advice.
 
Thanks!
3 Replies
McAfee Employee Hawkmoon
McAfee Employee
Report Inappropriate Content
Message 2 of 4

Re: Problem deploying McAfee Agent 5.5 to Persistent Windows VDI

Hi LeoM,

QQ
What OS is the client device?

Then an odd question: Are you able to install the Agent locally to the remote device?

If it completes, does it then go on to interact with ePO without issue or does it report commnication errors/issues?


LeoM
Level 7
Report Inappropriate Content
Message 3 of 4

Re: Problem deploying McAfee Agent 5.5 to Persistent Windows VDI

Thank you for the swift response.

We were able to identify the issue (ports not opened in the NSX environment).

Thanks again for your help.

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 4 of 4

Re: Problem deploying McAfee Agent 5.5 to Persistent Windows VDI

When you are testing the network path from epo, are you logged into the epo server with that same account, or if not, are you mapping a drive with those credentials?  Are you able to write to that directory?  See KB56386 to ensure all the environmental requirements are in place.  Also, if you have agent handlers, make sure the path can be reached from the agent handlers also.  You would look at the server log on the epo server or agent handler to see which server is actually doing the push.  You have to be able to write to that directory as well as execute it, which also creates a temporary installer service.