Go to All Forums

[New Feature] Windows Updates Monitoring

Greetings, 

We are happy to announce the support for monitoring Windows updates to ensure optimal performance of your Windows servers. Once the Windows server monitoring agent is installed, the Windows updates will be auto-discovered and added as a monitor in Site24x7.

Supported from Windows agent version 19.7.8 and above.

Highlights:

  • Get a quick snapshot of all your updates - Critical, Pending, and Security updates.
  • Know the updates to be installed in your servers with their respective categories (security, critical) and KB links.
  • View the complete history of updates installed in your servers for future reference.

Read our help documentation for step-by-step instructions. For any questions, please comment in the below thread or mail us at support@site24x7.com.

 

Regards,

Mathangi

 

Like (12) Reply
Replies (14)

Hi,

Is there anyway we can disable this for our account. We have no interest in monitoring Windows Updates from Site24x7 as its taken care of my another product. Its getting annoying to have to go in and disable these monitors as they are slowly discovered across our Windows servers.

Like (0) Reply

Hi Paul,

Using configuration rules, you can disable addition of Windows Update monitor.

  1. Log in to Site24x7 and go to Admin > Configuration Rules.
  2. Under Define Criteria, select the Monitor Type as Server.
  3. Under Define Actions, choose the Disable Server Application Discovery and select Windows Updates for this option, from the drop-down.
  4. Save the changes.

This will ensure the Windows update application is not auto-discovered and added for monitoring, when a Windows agent is installed or during agent upgrade.

Note: Please make sure this profile is associated with the servers in which you want to disable Windows updates monitoring.

 

Regards,

Selva Kumar C

Like (0) Reply

Its been a nightmare with this new feature!

We have windows update managed by a different system and not interested to enable this feature (as its consumes one additional lic per server). As our tenant has auto discovery enabled (e.g. for IIS, SQL, AD server etc we want them to be discovered), its also adding windows update.

 

I know the configuration rule above is a workaround, but the better and more elegant solution would be to provide a global configuration option in the tenant  in the admin section something like "Auto discover service options" and allow to enable/disable such auto discovery, and should have been disabled by default.

 

Why you release a product and then ask your customer to go through the pain to tackle it! Product team should have considered this fact, specifically when its a lic component and it costs money! 

Like (0) Reply

Hi Ash Dey,

Apologies for the inconvenience caused. We will take up the global setting as a feature request and update this thread once it's live.

We understand your concern and will take this up on priority and get it done. Also, please note that the new monitor will only consume unused licenses that you have already paid for. That is the reason we enabled it, by default.

Thanks!

 

Regards,

Mathangi

Like (0) Reply

I agree with Ash on this

Like (0) Reply

Hi, 

We have windows update monitor active on some servers now, but we are facing an issue.  The list with 'pending updates' on site24x7 doesn't seem to be correct.  It shows some security updates that are indicated as not yet installed, but if you check for the same Kb in the installation history you find them as installed correctly.  Also on the server itself they are installed correctly.  So the list doesn't seem to check wether the updates are effectively installed.

This triggers false alerts on our side, because we seem to have a lot of 'pending updates' while they are correctly installed.  

Any suggestion?

 

Best regards,

Ruben

Like (0) Reply

Hi,

It would be helpful if you could send the logs to support@site24x7.com to further analyze this issue.

 

Regards,

Mathangi 

Like (0) Reply

Hi,

We have fixed the issues related to pending updates in our Windows agent version 19.8.0

Please upgrade and let us know for further issues, if any.

 

Regards,

Mathangi

Like (0) Reply

Hi,

It seems to detect correctly what's installed and what's not since the new version, so that's great.

Can the creation of the windows monitor be triggered someway?  It should install automatically when installing the monitor agent, but what if it doesn't?  A rediscover doesn't seem to help.  We even tried reinstall of the agent on some servers, without success.

Best regards,

Ruben

Like (0) Reply

Hi,

Is it possible that the windows update monitor isn't triggered at agent install because on that server the App Monitoring Agent-Service isn't running?

That would be not logical in some way.  Windows updates seem quite basic for the OS.  As far as we understood, the APP Monitoring agent service is only installed if an additional application is running on that server (IIS, SQL, ...).  So on servers where no additional applications like that are running, it's not possible to do windows update monitoring?

Best regards,

Ruben

Like (0) Reply

Hi,

We have fixed the discovery issue in our Windows agent version 19.9.0

Please upgrade and let us know for further issues, if any.

 

Regards,

Mathangi

Like (0) Reply

Hi,

We managed to install the new agent 19.9.0 on one of our servers, but it doesn't solve the issue.  The windows update monitor still isn't triggered.

To install the new agent we had to do a re-install of the agent.  The new version didn't come available for upgrade.

Best regards,

Ruben

Like (0) Reply

Hi,

Please check if the following prerequisites are met: 

  • Windows agent version is 19.8.1 and above.
  • Supported for Windows servers 2012 and above; Windows 8 and above.
  • .NET version 3.0 and above.
  • PowerShell version 3 and above.

If the issue persists even after the above requirements being met, please share your logs to support@site24x7.com for further analysis.

 

Regards,

Mathangi 

Like (0) Reply

Hi,

The first server we tried it on was a windows server 2008, so that was the problem.  We now installed the new agent on a windows 2012 server, and there it works.  

Thank you for the help!

Best regards,

Ruben

Like (0) Reply

Was this post helpful?