This content has been marked as final. Show 8 replies
is it x64 Windows by chance??
Hi Sean... Yes it is a x64 system.
Ok that's why you don't see the registry entries in the typical location.
Only a true 64 bit app will write to that registry location. Once you are in the software key, look for "Wow6432Node" and you will find the traditional "Mcafee" and "Network Associates".
I'm running 8.7i and 4patch2 of the agent (on the only 2008 x64 server we have) and I don't seem to pull down my EPO tasks at all. Everything else is working ok though.
The only problem with that Sean is that it does install on some systems and others it does not.
All these server are HP Proliant dl380 G5 servers. 64 Bit Processor running Winows 2008 Standard Edition 64 bit edition.
On some it shows and some others it does not. The ones it works on it does. The others it doesn't.
are these made from an OS image? If not, is UAC disabled on all of them?
Here are the paths that you should see registry entries in:
I am seeing the same issue with all of our 2008 servers. Both 32 and 64 bit. Is this a know bug that they will not report back to the console?
If you bring up the Agent GUI  and click on "Collect and Send Props", does the GUI log show communication happening with the expected ePolicy server?
 Locate the installation directory for the Agent and run "cmdagent.exe /s"
On the few 2008 servers where the Framework installs correctly and the naprdmgr, and other portions show running in the Taskmgr, If I bring up the Agent GUI and tell it to collect and send props, it does communicate with the EPO server, it looks for new policies, and does not find any. Even though the server has policies defined, it also does not find any updates.
Thank you for your help, any further help is greatly appreciated.