WMI GetHotFixes randomly report 0 objects about windowsagent HOT 6 CLOSED

Hi,

I will investigate the issue asap and will try to update it for 2.3 Stable.

Regards,
Gilles Dubois.

from windowsagent.

Hi Gilles,

Could you tell me if this update was finally included in 2.3 stable ?
I guess it was not as it was only updated on 17th February and agent 2.3 was released on 12d January

Thanks in advance for your feedback.

Regards,

Sylvie

from windowsagent.

Hi @SylvieCozic ,

Indeed this update is not in the 2.3 version and will be compiled in the newer version of the agent ( 2.3.0.1 )

In the mean time you can ask someone to compile it for you or compile it by yourself. There is a little howto in the readme.md of the project.

Regards,
Gilles Dubois.

from windowsagent.

Hi @gillesdubois,

We will then wait for agent 2.3.0.1 to be released.
I don't have the time to prepare a compilation environment 😄

Thanks for your feedback.

Regards,

Sylvie

from windowsagent.

Hi Gilles and Sylvie,

I hope all is well with both of you :)

I'm about to embark on setting up the compilation environment to build a version of OCSng Agent to fix the WMI timeout issue discussed above.

I've been using FusionInventory Agent as a work around on those systems that fail to consistently report their full list of Windows Updates .... which is proving to be a constantly moving target, as more and more systems exhibit this behaviour over time. But, every time I replace the OCS agent with Fusion, I lose some OCS functionality (e.g. can't get clients to report back particular Registry values).

But, before I dive into setting up the compiling environment (something totally foreign to me), I thought I'd reach out to you, and ask if you know if someone has already created a version of the agent with the WMI timeout fix. Do you know if anyone has, and if so, how I might acquire a copy?

Ron

from windowsagent.

Hi Ron,

Unfortunately I still don't have any compiling environment for OCS on my side.
Sorry.

BTW, I would be very interested to test a 2.1.x agent with this fix.
Our server is still in 2.1.2 so I cannot use a 2.3.x agent...
We have some specific developments to check before we can planify a migration to 2.3

Regards,

Sylvie

from windowsagent.