Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 1 subscriber
  • Views 3531 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SEC shows alert on Updates Dashboard after Shh Updater B

GC3David

Hello forum land, 

Our SEC shows an alert on the updates section of the dashboard. When I look at our update managers there are no alerts or errors and we have ben updated today with a matching configuration. All of our endpoints show they are up to date on the SEC but windows action center sees them as being out of date. This started with the Shh updater issue a couple weeks ago. Just wanted to see if anyone else is having a similar issue. 

Thanks 

:33591


This thread was automatically locked due to age.
Parents
  • 0

    Any reason that you're not running the latest 10 version?

    The whole "Up-to-dateness" in Action Center/Windows security center is a bit odd. 

    If you don't/can't switch your main subscription to 10 but you wish to try 10 on a couple of clients:

    1. Create a new subscription: In the "Update managers" view, call it SAV10 for example

    2. within that subscription select the "10.0 Recommended" version which at the moment is 10.0.8.

    3. Within the config of one of the Update Managers, in the subscriptions tab you can move this new subscription "SAV10" to the right hand side.

    When SUM updates, you'll then have SAV 10 in your distribution share:  You will see a new Sxxx number for this subscription.  View-Bootrap locations will show you exactly.

    4. To test on a single client, you can

    4.1 create a new SEC group, e.g "10Test".

    4.2 create a new updating policy, within the updating policy, under the subscription tab choose the new "SAV10" subscription.

    4.3 link the new updating policy to the test group

    5. Move a test machine to the test group, i.e. "10Test".

    6. Within 20 seconds it should get the polices,

    7. Call update now on it from SEC to speed things up and after a few minutes (depending on network connection) the client should show up as being SAV 10.  It will ask for a reboot but doesn't need to be performed straight away.

    I assume that machine will not have a problem.

    Regards,

    Jak

    :33607
Reply
  • 0

    Any reason that you're not running the latest 10 version?

    The whole "Up-to-dateness" in Action Center/Windows security center is a bit odd. 

    If you don't/can't switch your main subscription to 10 but you wish to try 10 on a couple of clients:

    1. Create a new subscription: In the "Update managers" view, call it SAV10 for example

    2. within that subscription select the "10.0 Recommended" version which at the moment is 10.0.8.

    3. Within the config of one of the Update Managers, in the subscriptions tab you can move this new subscription "SAV10" to the right hand side.

    When SUM updates, you'll then have SAV 10 in your distribution share:  You will see a new Sxxx number for this subscription.  View-Bootrap locations will show you exactly.

    4. To test on a single client, you can

    4.1 create a new SEC group, e.g "10Test".

    4.2 create a new updating policy, within the updating policy, under the subscription tab choose the new "SAV10" subscription.

    4.3 link the new updating policy to the test group

    5. Move a test machine to the test group, i.e. "10Test".

    6. Within 20 seconds it should get the polices,

    7. Call update now on it from SEC to speed things up and after a few minutes (depending on network connection) the client should show up as being SAV 10.  It will ask for a reboot but doesn't need to be performed straight away.

    I assume that machine will not have a problem.

    Regards,

    Jak

    :33607
Children
No Data