This content has been marked as final. Show 10 replies
What version of CMA is deployed?
What happens if you send an agent wakeup call (ticking the "Get Full Product Properties" box to one of the affected clients, then refresh its properties. That seems to fix the problem for me, I've also seen this issue when rolling out HIPS.
[SIZE=2]It's all in my sig.
[/SIZE]CMA 22.214.171.1246 (confirmed as installed on several of the clients in question)
Still have about 2% of all machines on CMA 126.96.36.1993
Nice, that did the trick for 2 connected user I just tried.
And I have seen the initial doubling has slowly subsided, perhaps after field users (All my HIPS users are laptops with VPN) connect long enough for the Agent to Server communication to kick in (Full Properties @120min or @10min after 1 day for me).
What why how does the initial doubling happen? I too saw it on some machines (25%?) during deployment, but my entire base doubled after the last DAT update. Yow!
We noticed this with the 7.x security content update. The version of HIPS does not show up in the ePO report sand it appears you have twice as many HIPS hosts as there are. A bug with McAfee and they need to address it.
Just a note that it happened again with Yesterdays 1711 security update for HIPS.
I now have hundreds of phantom HIPS installs with Product version "--" in my reports and my clients show two instances of HIPS 6.1 in properties.
The only way I know to address it is to do wake up calls from ePO. Regular ASC checkins do not work.
This has been escalated to engineering.
It's been a problem since the day I started using HIPS.
appreciate it if you keep us posted.
Are you talking about the Installation count report? As that's how I found out there was a problem we had approx 1400 with HIPs one day and over 2000 the next! So I would say that the addition HIPS is included in the report. Unless you are talking about another report if so which one?