6 ms·

This once again highlights how bad the ecosystem with 3rd party tools used for basic system maintenance in the MS environment is. And how much companies and adm

by drw85 2y ago

This once again highlights how bad the ecosystem with 3rd party tools used for basic system maintenance in the MS environment is. And how much companies and admins rely/depend on those. I don't really understand why there are so many commercial third party tools being used to do basic things. But they cost a good amount of money and cause a lot of problems.

zuhsetaqi 2y ago
In this case at least it was Microsofts fault
- thrw42A8N 2y ago
  No, it wasn't. This failure happened at the side of the user - their central policy configuration or so. Microsoft pushed the update correctly.
  - Brian_K_White 2y ago
    It sounds like the 3rd party tool did what MS told it to do.
    - thrw42A8N 2y ago
      Nope, my servers are just fine.
  - deleted 2y ago
    [deleted]
  - superb_dev 2y ago
    Did we read the same article? Microsoft labeled an update as "security updates" when it was in fact an upgrade to Windows Server 2025
    - lostmsu 2y ago
      Did they say they wouldn't? In the absence of Heimdall 2022 Server doesn't install it along with other security updates.
      - superb_dev 2y ago
        Wouldn't what? Also given other peoples experiences in this comment section, that doesn't seem to be true.
        lostmsu 2y ago
        I can't find anyone without Heimdall who would claim it happened to them. For all we know this is 100% Heimdall bug.
- thro1 2y ago
  Yes. For automation software it's fully updated (not: upgraded) target system definition.
heraldgeezer 2y ago
This would happen if you just let Windows Update do its thing. As is fine on client machines usually for security. On Azure it is the default even https://imgur.com/a/RvEx3yn https://imgur.com/a/RvEx3yn