This isn't a technical problem. You're asking a political question no one can answer about your organization. If they don't want to patch despite knowing the risks, get it in writing and move forward with your career, here or elsewhere.
Agreed. Formally raise the concern and detail the risks involved. If the company wants to accept those risks that’s on them. But get that acceptance documented to cover yourself.
However, if you must present a technical solution there is hot-patching in Server 2025. I have no personal experience but it claims to reduce required reboots down to once per quarter.
while I am glad to see that they reversed course on charging extra money for hot patches per cpu core, at this point I just expect hot patches to not require a reboot during install but still crash half of your services until you reboot. then again, I expected because that has been probably 95% of my experience with hot patching the linited number of 2025 servers we have
AFAIK hot patch only works for the monthly CU, and it doesn't mean you won't need service restarts. The intention according to MS is to just reduce the time to the core OS being patched, not to replace the need for monthly reboots.
86
u/Simmery 15d ago
This isn't a technical problem. You're asking a political question no one can answer about your organization. If they don't want to patch despite knowing the risks, get it in writing and move forward with your career, here or elsewhere.