Epo clients not updating

:) Do you wonder if your IT business is truly profitable or if you should raise your prices? I still have to check the items suggested by "Aim To Please" above but am wondering if many of those apply since scheduled tasks work fine on the device for a period and then stop working randomly.

Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. I will go through each item and confirm that it is working as suggested and in the process may discover new facts.

I don't know WHY it doesn't list in e PO, I just know that constantly forcing e PO to acknowledge the product being uninstalled/reinstalled manages to fix it.

most notably are the XP machines with VS 7.1 on them which connect to e PO, download the policies but do not download the DAT had out 2000 machines going fine(most recently they stopped downloading the DATs, but still download the policies)the log file on the client machine shows "No Package received from server" which there clearly is an updated DAT file on the e PO 3.0.1 server. I am not sure why but I was stuck exactly the same as you with a few random clients not doing what they should be doing and usually one of these two options worked. The specific reg key and values are below: [HKEY_LOCAL_MACHINE\Software\Network Associates\e Policy Orchestrator\Application Plugins\CMNUPD__3000]"Plugin Path"="C:\Program Files\Network Associates\Common Framework\Frm Plugin.dll""Software ID"="CMNUPD__3000""Uninstall Command"="""Language"="0409""Product Name"="Mc Afee Auto Update""Version"="" Since this key is missing on the XXX-EPO machine, the e PO Agent does not recognize the Update task you are configuring as one that it needs to run.

no we do not use superagentswe have figured out the problem of getting our machines to download the DATs (we just retraced the settings from our old server, dont know what exactly worked though)so back to our major issue which is the fact that Windows XP machines download the policy but not the DAT. I find that sometimes one of two things can remedy the situation: Firstly manually update the clients to the latest DAT version and they often start working next time there is a new DAT version to be downloaded from the e PO server, s Secondly manually import the file from your e PO server or a working client to the affected clients and again this seems to get them going. This key is referenced by the e PO Agent to keep track of what products/components are installed on the system in order to determine the correct tasks and policies set by the e PO server.

I still get a rather large number of invalid response errors from workstations -- some are transient errors and others are persistent. Try sending sending a wake-up call to one with a 2 minute delay, then delete it from e PO.

See if it connects and updates -- then try subsequent wake-ups and see if they allow it to connect ok. Have any of the clients previously reported to a different e PO server?

From the group of machines that I am in charge of keeping up-to-date, a small amount of these machines do not have the proper Mc Afee Product information displayed in e PO.

I have remoted into these machines manually and checked the version numbers for these Products (VSE, Policy Auditor, HIPS, DLP, etc.) and they all list the most up-to-date information for those products, (example, HIPS

I am wondering, what does the Agent Log say about your update problem?

Did you schedule a Product Update task and does it run on the correct time or at all?

If you have more then 3 to 5 machines being affected by this issue, I would recommend doing this in very small batches, as it can affect network performance significantly.

Typically, I have to do 3 to 4 cycles of all of the above steps to get the machines to react properly.

The e PO documentation makes my brain hurt I don't know about anything else, the admin guide is about 10 times longer than it needs to be and one of the worst written pieces of technical documentation I've read. This is what NAI told me when I had a similar situation.

Tags: , ,