I'm curious about how everyone's handling secure boot certificate updates for their servers this year. My Azure Virtual Desktop (AVD) machines seem to be all set and updated, but Microsoft has only specifically mentioned AVD. I suspect this impacts all Trusted Launch and Secure Boot machines, so I'm looking for advice on managing this across different setups.
2 Answers
If you're using Hyper-V for your virtual machines, the process is pretty straightforward. Just update your host and do some adjustments in Hyper-V, then update the guest machines too. It's not too complicated once you get the hang of it.
But if you're dealing with bare metal installations, it gets a bit trickier. It's kind of similar to updating a Windows 11 desktop - you'll need to check if your BIOS needs an update and then handle the secure boot update from there.
I’m mostly on Azure too, but I'm a bit confused about how to address this for Server 2022. It seems like some steps need to be handled directly at the OS level, and to be honest, I'm not entirely sure what's going on. Any insight would be helpful!
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures