This content has been marked as final. Show 17 replies
I had one machine installed with Win7 and I use ePO 4.0 patch to deploy the agent to the machine. It seems it works and agent can upload records to server. Can deploy VSE 8.5 patch 7 also.
However, still something not work on Win7:
- only local username reported while I login to AD
- HIP 7 not support
Agent and VSE 8.7i (with MAS) seem to deploy fine. HIPS 7 will not install, nor does SCP.
I tested 1 PC with windows 7, it worked ok, but I seem to recall some annoying security messages when trying to install agent manually on the PC, I had to switch to a different window or some such thing, to be able to see the installer and click ok.....don't have a windows 7 PC here with me now to say exactly, but there was some little glitch like that.
We were testing Windows 7 Ultimate Beta and had McAfee VS 8.7i installed with no apparent issues. However, now that Microsoft has released RC 1, we are seeing this message in the Windows Security Center:
"McAfee VirusScan Enterprise is on but is reporting its status to Windows Security Center in a format that is no longer supported..."
This behavior causes issue with Outlook. Is anyone else having this issue and is there a workaround?
I got the same message on my Win 7 RC1 too. Still no solution yet. sad
Elsewhere in the forum it's been reported that there are issues with Windows 7 since RC was released.
I've installed it on W7 Beta1, several of the post beta releases, and now on W7 RC 7100. The newest one on RC 7100 is in the domain and I installed the MAgent on the machine so it could be controlled by ePO. As mentioned the system shows up in ePO and is reporting in but the W7 machine is NOT getting any policies from ePO.
I have the same issue. The Agent 4 patch 2 installs, VirusScan 8.7 installs and HIP 7 Patch 4 installs. The Agent will report into the server but it will not receive policies or tasks. The tray icons for HIP and MA also will not appear.
Does anyone know of a resolution to this issue?
I've spent a good bit of time trying to resolve this but my guess is it's some sort of incompatibility with the agent at this time. I haven't tried the 4.5 beta agent on W7 yet so I don't know if it resolves this problem or not.