- 0
How do Windows Server sysadmins handle updates that require reboots?
-
Recently Browsing 0 members
- No registered users viewing this page.
-
Similar Content
-
Microsoft blocks BlackLotus Secure Boot mitigations on TPM 2.0 Windows Server 2012 PCs
By hellowalkman,
- microsoft
- windows server 2012
- (and 14 more)
- 0 replies
- 2 views
-
Microsoft fixed Windows CVE-2024-26248, CVE-2024-29056 Kerberos PAC validation flaw
By hellowalkman,
- microsoft
- windows server
- (and 15 more)
- 0 replies
- 3 views
-
A Microsoft Confidential Windows Server 2012 build has leaked and it's quite pretty
By hellowalkman,
- microsoft
- windows server
- (and 7 more)
- 16 replies
- 6 views
-
New Windows Server 2025 features revealed including hotpatches for security updates and more
By John Callaham,
- microsoft
- windows server
- (and 2 more)
- 12 replies
- 3 views
-
Updated DC hardening timeline for Secure Boot, DCOM, Kerberos, Netlogon shared by Microsoft
By hellowalkman,
- 0 replies
- 2 views
-
Question
KaoDome
Hi, I think it's well known there are several sysadmins among the members of Neowin and I have always been curious about this so I decided to ask away. In a desktop/workstation setting rebooting the machine because of an update isn't that big of a deal, but server uptime is important enough that some companies sign SLAs guaranteeing a certain uptime.
I know (some?) Linux systems are able to patch the kernel live and can work as usual without a full system reboot for a long period of time, but what about Windows? Just like their desktop counterparts I'm sure the server line has updates that require a reboot.
If anybody has first or third hand experience on how it's handled I'd appreciate your input, but thanks anyway 😉
Link to comment
Share on other sites
2 answers to this question
Recommended Posts