Forum Discussion
Windows Server 2022 - devices not booting when Secure Boot enabled (KB5022842)
The most recent patch Tuesday update for Server 2022 - KB5022842 - causes some devices with Secure Boot enabled to fail to boot - it reboots after the update, then fails at the next reboot. The Micro...
We are getting off topic here, this could be a topic on its own.
You missed the "production environment" thing in my reply, this is a critical item when evaluating risk.
Well if your customers are fine with losing money because of unsupported stuff, I guess that's OK. Defeats the purpose of minimizing costs in the first place tough. Which itself contradicts buying brand new WS2022 licenses and CAL, when you can continue using WS2019, and using physical hardware for servers when you can use VM instead, and so on.
Or if you are really unable to cope with regular on-premise hardware upgrade, go Azure/AWS/Google.
And the next post kinda prove my point :
"they have reproduced the issue, and confirmed that servers later than 13G are not affected. Because Server 2022 isn't officially supported on 13G servers, they are not currently committing to doing anything about it". In some companies, telling this to your boss/customer triggers a Resume-Generating Event (RGE).
As for disabling Secure Boot to bypass your issue, and claiming VBS/CG are fine without it...yeah, good luck with that.
You missed the "production environment" thing in my reply, this is a critical item when evaluating risk.
Well if your customers are fine with losing money because of unsupported stuff, I guess that's OK. Defeats the purpose of minimizing costs in the first place tough. Which itself contradicts buying brand new WS2022 licenses and CAL, when you can continue using WS2019, and using physical hardware for servers when you can use VM instead, and so on.
Or if you are really unable to cope with regular on-premise hardware upgrade, go Azure/AWS/Google.
And the next post kinda prove my point :
"they have reproduced the issue, and confirmed that servers later than 13G are not affected. Because Server 2022 isn't officially supported on 13G servers, they are not currently committing to doing anything about it". In some companies, telling this to your boss/customer triggers a Resume-Generating Event (RGE).
As for disabling Secure Boot to bypass your issue, and claiming VBS/CG are fine without it...yeah, good luck with that.
Must admit I am at rather a loss to know why you are bothering to comment here at all - you clearly have no first-hand knowledge of the issue and it seems just want to share the benefit of your wisdom and tell us how we should set up our systems.
As I've already said, we have good reasons for setting things up as we have done (we have a mix of physical and virtual servers, so already have the 2022 CALs, and Windows Server licenses don't cost a lot - we are a charity so get significantly reduced pricing on them). You seem to be making lots of assumptions about how we should do things despite knowing absolutely nothing about our use cases!
As I've already said, we have good reasons for setting things up as we have done (we have a mix of physical and virtual servers, so already have the 2022 CALs, and Windows Server licenses don't cost a lot - we are a charity so get significantly reduced pricing on them). You seem to be making lots of assumptions about how we should do things despite knowing absolutely nothing about our use cases!