cancel
Showing results for 
Search instead for 
Did you mean: 

Issue installing McAfee Agent, Upgrade from 4.8.0.1500 (Patch 2) to 4.8.0.1938 (Patch 3)

Jump to solution

Hi,

I am currently updating our McAfee Agent version and VirusScan version on one of our environments.

The environment is running ePO 5.1.0, McAfee Agent 4.8.1500 (MA Patch 2), and VirusScan Enterprise 8.8 Patch 6.

We want to update the VirusScan Enterprise to Patch 8, which is (according to McAfee documentation) compatible to MA 4.8.0.1938 and above.

We have workstations and servers on this environment. The servers are running Windows Server 2012 R2 and there was no issue upgrading them. The workstations are running Windows 10 Enterprise 2015 LTSB (version 10.0.10240).

According to this McAfee KB: https://kc.mcafee.com/corporate/index?page=content&id=KB51573 we should be able to run the updated agent on both operating systems. However I am facing issues with the workstations were no Client Task from the ePO can come through to the workstations.

I checked the ports listened to by the agent, which should be 8081 for agent wake-up and 8082 for agent broadcast, but the agent is only listening to 8081 port. (Sending an agent wake-up call is working). The agent.ini file contained in C:\ProgramData\McAfee\Common Framework is containing the correct port information.

I tried to reinstall the agent multiple times, and tried with different version of the Patch 3 agent (up to Patch 3 Hotfix 3 - 4.8.0.1995), and all generate the same issue.

Has anyone ever faced this or have any clues on how I could solve this?

Could it be that the OS is causing compatibility issues?

Best Regards,

Pierrick

1 Solution

Accepted Solutions
McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 10 of 13

Re: Issue installing McAfee Agent, Upgrade from 4.8.0.1500 (Patch 2) to 4.8.0.1938 (Patch 3)

Jump to solution

under software, extensions, what build is the agent extension?  The error below is typical of an error if extension is not as high as the software version and not high enough for support for that build of OS.  I would suggest checking in the very latest 5.x agent extension (not software, just the extension).  It is backward compatible for managing 4.8 agents.

Failed to read EnforcePolicy. Error code -1201

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

12 Replies
McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 2 of 13

Re: Issue installing McAfee Agent, Upgrade from 4.8.0.1500 (Patch 2) to 4.8.0.1938 (Patch 3)

Jump to solution

What extension build do you have checked in for the agent?  If it is not patch 3, it can't fully manage the Windows 10 agents, as it doesn't have that OS support embedded in the supportability for it.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Re: Issue installing McAfee Agent, Upgrade from 4.8.0.1500 (Patch 2) to 4.8.0.1938 (Patch 3)

Jump to solution

I previously had extension build 4.8.0.1500 checked in for the agent (which is Patch 2), which was working (and currently is the only one working) on the Windows 10 machines.

I tried the upgrades with agents 4.8.0.1938 and 4.8.0.1995, which should have the supportability for Windows 10, but maybe not the same build as on the machine?Agents checked in.JPG

Reliable Contributor Troja
Reliable Contributor
Report Inappropriate Content
Message 4 of 13

Re: Issue installing McAfee Agent, Upgrade from 4.8.0.1500 (Patch 2) to 4.8.0.1938 (Patch 3)

Jump to solution

Hello,

1) first of all, check the documents at the McAfee Support Website. Here is the link to the master article: McAfee Corporate KB - Supported platforms, environments, and operating systems for McAfee products…

You can find information about the supported environments for any McAfee product.

2) If the clients are updating the "Last communication" field, they are communicating with EPO.

3) Take a look which deployment tasks are assigned to the endpoint.

Optional, upgrade your environment to newer versions regarding Meltdown and Spectre vulnerability (McAfee Corporate KB - Meltdown and Spectre – McAfee Product Compatibility Update KB90167

1) Upgrade your EPO Server at least to Version 5.3.x or 5.9.1 -> useful regarding spectre and meltdown vulnerability.

2) Install the latest McAfee Agent Extension. This could be 5.x or 5.5.x version.

3) Take a look at the KB and install the latest versions of your McAfee Products.

From a Security Perspective, you should switch to Endpoint Security.

Cheers

Re: Issue installing McAfee Agent, Upgrade from 4.8.0.1500 (Patch 2) to 4.8.0.1938 (Patch 3)

Jump to solution

Hi,

1) I already checked this but carefully looked at it again and it seems that all products should be compatible. It is just strange to me that I am facing issues with the minimum supported McAfee product version, but not with the versions below, which are not supported.

2) I will have to look at this as I reinstalled the old agent to have things working for a while. The communication was updating because I used the wake-up agent task to update the product information, but I did not check if it was communicating in the long run and without using agent wake-up calls. I will keep you informed about this.

3) No deployement tasks are assigned to the endpoint, the only tasks assigned are a DAT update which is sceduled and a VirusScan update which has to be ran manually. But when trying to run a client task on one of the workstations with the new agent, it fails. In the log we can see "Run now Task DAT Update recieved" and right after "Run now Task DAT Update failed". However the task has not been recieved, there is nothing in the local task folder (C:\ProgramData\McAfee\Common Framework\Task) and nothing is seen in the McAfee Agent Monitor.

As for updating all our systems, it is not something I can currently do. I can start discussions but there are a lot of factors that come into play in this case.

It is also something that would be really time consuming, and we don't really have the ressources to do this currently...

Thank you,

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 6 of 13

Re: Issue installing McAfee Agent, Upgrade from 4.8.0.1500 (Patch 2) to 4.8.0.1938 (Patch 3)

Jump to solution

Run client task now will only create a temporary ini file.  If you schedule the same task, do they receive it?  We would need to see server logs for what is happening with run client task now and maybe some agent logs from failed clients, including mcscript logs.  You may want to open a ticket with support, as there is a variety of causes for those not working.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Re: Issue installing McAfee Agent, Upgrade from 4.8.0.1500 (Patch 2) to 4.8.0.1938 (Patch 3)

Jump to solution

Well, the DAT Update is scheduled, I just ran it manually to test if it is working or not. The task should run daily and is not present in the Task folder.

The task also does not show in the VirusScan console (I have activated the option to show managed tasks in the console), which are seen on the servers.

Here are some interesting lines from the agent log:

2018-01-11 15:07:22.204    I    #6176    Agent    CMsgResponsePackage::ParsePackage() - New MsgResponse-MA_RunNow was received

2018-01-11 15:07:22.204    I    #3964    Agent    RunNow task DAT Update received from ePO

2018-01-11 15:07:22.204    I    #10676    Agent    Agent Data Channel work wakeup, processing items

2018-01-11 15:07:22.204    I    #3964    Sched    >>--CSchedule::CreateTask

2018-01-11 15:07:22.220    I    #3964    Sched    <<--CSchedule::CreateTask

2018-01-11 15:07:22.220    I    #3964    Sched    >>--CSchedule::AddTask

2018-01-11 15:07:24.205    i    #10676    Agent    Sending the next batch of 1 data channel items

2018-01-11 15:07:24.205    I    #6176    Agent    Started processing a package..

2018-01-11 15:07:24.205    I    #6176    SpiPkgr    Using sequence number 15

2018-01-11 15:07:24.205    i    #6176    Agent    Agent communication session started

2018-01-11 15:07:24.205    I    #6176    Agent    Package type is MsgUpload

2018-01-11 15:07:24.205    i    #6176    Agent    Agent is connecting to ePO server

2018-01-11 15:07:24.220    I    #6176    imutils    Trying with site: 172.16.4.51:81

2018-01-11 15:07:24.220    I    #6176    naInet    HTTP Session initialized

2018-01-11 15:07:24.220    I    #6176    imsite        Upload from: C:\ProgramData\McAfee\Common Framework\Unpack\pkg00131601532442050000_2045162251.spkg

2018-01-11 15:07:24.220    I    #6176    imsite        Upload response target: C:\ProgramData\McAfee\Common Framework\Unpack\pkg00131601532442050000_645029488.spkg

2018-01-11 15:07:24.361    I    #6176    imsite    NaInet library returned code == 13

2018-01-11 15:07:24.361    I    #6176    naInet    HTTP Session closed

2018-01-11 15:07:24.361    i    #6176    Agent    No package received from ePO Server

2018-01-11 15:07:24.361    i    #6176    Agent    Agent communication session closed

2018-01-11 15:07:31.768    E    #3964    Sched    Failed to add the task: error code= 0x80000016

2018-01-11 15:07:31.768    E    #3964    Sched    <<--CSchedule::AddTask hr=0x80000016 : The text associated with this error code could not be found.

2018-01-11 15:07:31.768    I    #3964    Agent    RunNow task DAT Update is failed

It seems the agent is able to get the task but runs into some error.

You can find the agent log from the moment I updated it again to do the tests this afternoon until now here: http://txt.do/dmtrz

As for the McScript log, no entry is created with the new agent, the only entries are from the older version where tasks were able to run. I can still do an update of the DAT file or the VirusScan Enterprise manually from the local VirusScan console and this would work.

When doing a manual run for using the "Auto Update" task from the VirusScan console, this is what shows up in the McScript log: http://txt.do/dmtr8

Also, concerning the support ticket, I wanted to contact McAfee support but was not able to make an account... I have the grant number associated with my product, but it seems I also require to create an account with an appropriate email address, and whatever I put in there is not working. I tried contacting them via an email to try to create an account but I am still waiting, if there is no answer I will call them directly tomorrow. Maybe I oversaw something that let me go pass this account thing? (I was looking here: McAfee - Enterprise or Small and Medium Business Support )

Re: Issue installing McAfee Agent, Upgrade from 4.8.0.1500 (Patch 2) to 4.8.0.1938 (Patch 3)

Jump to solution

The Clients are updating the Last Communication field, it seems that there are just issues with communication coming from the ePO server.

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 9 of 13

Re: Issue installing McAfee Agent, Upgrade from 4.8.0.1500 (Patch 2) to 4.8.0.1938 (Patch 3)

Jump to solution

Just in case there is something corrupt in the task, try creating a completely new task and assign it and see if there are still errors.  I will look at the logs.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 10 of 13

Re: Issue installing McAfee Agent, Upgrade from 4.8.0.1500 (Patch 2) to 4.8.0.1938 (Patch 3)

Jump to solution

under software, extensions, what build is the agent extension?  The error below is typical of an error if extension is not as high as the software version and not high enough for support for that build of OS.  I would suggest checking in the very latest 5.x agent extension (not software, just the extension).  It is backward compatible for managing 4.8 agents.

Failed to read EnforcePolicy. Error code -1201

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

More McAfee Tools to Help You

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