Recent content by FengTeo

Hi itsp1965 We have 8.0i p13 running on x64r2 here... but it IS running in *32 mode. We haven't had any issue with it so far, and am waiting for our epo server to be upgraded before we go to 8.5i. Hope that helps.

And yet another note for those who may have this issue... if you've got it set up on machine, I wrote a batch file to delete them via cmd prompt (we don't have SMS or other such utils). netsvc mcafeeframework \\machinename /stop reg delete "\\machinename\HKLM\SOFTWARE\Network Associates\ePolicy...

While I was messing around on another forum, I discovered this. I suspect this is the issue we're having. Hope this helps anyone else there.

OH... sorry for the messed up formatting. Copied it from a text document thinking it'd copy over the word wrapping (which it in fact has done. If I could edit it, I would. Regards Feng

Hi All I have a bit of a strange problem here. I suspect, but the end of this post, I'll be rambling a bit so I apologise in advance for this. :) We are running ePO 3.6 with patch 2a on a Windows 2000 SP4 server. It was originally upgraded from version 3.0.2a in a one step process after...

yup I saw it there too. So far havent deployed it to the mainstream pcs.... still trying to iron out a few bugs. anyone else out there deployed p13 yet?

Hi Marty Did you check to see if the service has "administrator" as the owner? If so, you may need to change the password associated with the service. HTH.

drew1701d You only get the patches through the mcafee customer portal. My link points to http://mysupport.nai.com/ and when I login, I can download various patches for the various McAfee products I'm licensed for. My portal link only lists patch 11. I have patch 11a for a specific fault with...

Also... on this note, has anyone tried or had a look at EPO3.6p1 yet?

We have the same problem here.... if you look at the logs, you'll see that it is checking (if you have set it up right)... and it's as if... yes, it cannot confirm that the right version is there, OR, you already have it, so there's nothing to update, but rather than say it's up to date, it says...

EPO3.6 running on Win2k Server SP4 here sorry :| but it's working great... all rules and policies were retained in the upgrade from 3.0.2a :)

With regard to the rebooting/losing power etc... the default setting on servers/xp clients is to auto reboot on error. This has the same symptoms... i.e no warning, just as if you hit the reset button. Disabling the auto rebooting option actually displays an error/bluescreen.

Patch 11 fixed our scripting software issues, but with that came issues with the buffer overflow component which caused our network traffic to grind to a halt. Trying to run anything that queried the network, or installing apps off the network were impossible. McAfee issued a fix for this...

have you tried disabling automatic rebooting of the server to see what it's blue screening on?

Hey Terry McAfee recommend having CMA 3.5 patch 5 before upgrading, so we're currently deploying this newer version of the agent to everyone in the country before upgrading the ePO server.