This content has been marked as final. Show 7 replies
A. You can deploy via the console.
A.1 How large is your environment?
A.2 How many remote locations
B.null If you want to change the compliance query allow 8.5 or greater you can do that through Reporting->Queries
I am one that likes to remain consistent in my environment. I recommend if you are going to let 8.7 out of the bottle you migrate all to the latest. That way when things go wrong you know what version VSE they are running.
Thank you. I'll do the query thing right now... as far as question A this might be a little hairy.
A.1 - Only about 100 machines
A.2 - Three locations, one of them being in India. So we'll probably have to have a night were all the india people leave their machines on for the night.
OK, maybe it's not that.
Is it possible that the 3.6 agent can't report on VSE 8.7? The machines with 8.7 are the only ones whose agent is not reporting. When I run the cmdagent.exe /p command to force a wakeup from the client to the EPO server, the firewall shows no activity, so it's not actually sending any info, but I'm not getting any errors. Also agent wakeups from EPO to the servers in question happen with no errors as well.
Well, I am not sure. I do not run (nor have I ever) 3.6. We have only worked off of 4.0 patch 3.
With so few users it might be work upgrading. The console features are very nice and "web" based.
I wish I could be more help....
The VSE 8.7i machines are shown as not compliant because you have not added VSE 8.7i extension to the ePO server.
If you have a look at your VSE 8.7i zip file you will find inside it another zip called virusscan8700.zip, just add it tou your extensions through Config->extensions->add new extension
After this you will see they are not yet shown as non-compliant
thank you, this is what i was looking for.
i ended up adding the 8.7 package to the software tab. stupid me, i had both 8.7 and 8.5 in there. i went to go do an agent update push to the enterprise. it also tried installing 8.7 on everyone's machines. during the silent install every machine in the enterprise blue screened and the whole mcafee install was corrupted. this was not a good weekend. also anyone with a laptop was stuck in a permanent reboot cycle whenever their wireless drivers started booting up.
It's not a good idea to deploy VSE 8.7i to all the machines on your epo's tree but I can understand you thought it could help with the compliance reports happy