ePO 5.10 U5 doesn't show current ENS/VSE product version

[giangi]

We have imported and distributed Patch14 for VSE 8.8 and Endpoint Security bundle v10.6.1.1459

Products are showing the correct version/build/patch on system's about info but on ePO the reported versions are still the "previous" one.

Only after a full remove/reinstall (tested for VSE) the reported version is current.

Here you are some snapshots for VSE

• info from ePO 
• info from the system's about 

Here you are some snapshots for ENS

• info from ePO 
  
  
• info from the system's about 
  

What can we do to solve this problem?

Thank you
Best Regards

[cdinet]

Please run this query and get the output in sql.

select count (*) from epocomputerpropsstaging

[giangi]

Your command reported this error

Msg 208, Level 16, State 1, Line 1
Invalid object name 'epocomputerpropsstaging'.

 Adding the full path reports "zero"

[cdinet]

If you ran the query against master instead of epo db, you would get invalid object.  

There is an issue with update 5 not showing updated properties and kb92203 describes a workaround.  You can also try rolling back update 5 and install update 4.  If you don't have a ticket already with McAfee, please open one so you can get hotfix when issue is resolved.

[giangi]

---

As a workaround, you can schedule a client task on the affected clients to run a wakeup call and submit their full properties.

---

If that action is the same as running a Client Wake Up with "Retrieve all properties even if they haven't changed since the last time they were collected" I can say that it won't work because I have already tried that...

Addendum: I have tried anyway to schedule the task as per KB and versions reported in ePO didn't change

[cdinet]

Yes, sometimes that doesn't work.  You might want to verify the version is correct on the client, however.

If it is, what is the output of this query?

select count (*) from epocomputerpropsstaging

[giangi]

I wrote on OP and posted screenshots too: on client versions are the correct ones!

You already asked to run that query... The result is still "zero" 0

[cdinet]

Sorry, my bad.  We will have to wait till dev comes up with a fix on that.  As suggested, you can see if rolling back update 5 and installing update 4 resolves issue.  I haven't tested that, as I don't have a test system that has the problem, so I don't know if it will work or not for sure.

[giangi]

...I hope we do not have to wait too much...

Happy Holidays!

[LKS · Accepted solution]

Hi giangi,

Good news to you. Dev has released hotfix to the issue and it is available only through support. If you have not raised SR, please log a case to get the hotfix.

Was my reply helpful?

If you find this post useful, please give it a Kudos! Also, please don't forget to select "Accept as a Solution" if this reply resolves your query!