It would be really nice if you guys could add the option to select hotpatch as an available server os when creating a server through the nerdio portal. This would greatly simplify patch orchestration and allow us to not need to worry about as much about maintenance times when trying to update our servers that need to be running at mos times.
Ability to Use Azure Hotpatch Server Image When Creating Server in Nerdio Portal
1
Keeping servers patched without requiring (as many) reboots? Yes, Please!
(For those that haven't heard about Hotpatch, yet, see Hotpatch for Windows Server Azure Edition | Microsoft Learn to learn about it 🤓)
Kris Pennington, do you have a use-case where you would need the "small disk" image or do you think you would generally use the "regular" image?
Until we're able to add that as an available image, have you looked into enabling Hotpatch with a scripted action 🤔?
Enable Hotpatch for Azure Edition virtual machines | Microsoft Learn
I generally would not use the small-disk image and would instead go for the regular image. I looked into that enable hotpatch script but it looks like it's more aimed towards Azure HCI, and more importantly, does not allow for automatic updating which is the biggest advantage I would get out of enabling hotpatch. When you enable it after the fact with that script it says there in the learn article that it's not compatible with azure update manager and that orchestration must be performed manually.
Wow!
I missed that before, they are definitely "important differences" 😞
I wonder what the point is in manually enabling Hotpatch then? 🤦♂️
I'm guessing that when you get to the point of utilizing Azure HCI you have everything automated to the point where you don't need Azure Patch Orchestration 🤷♂️?
It's a bummer you have to go outside of NMM to deploy Hotpatch VMs.
If you do go down that route, would you be willing to share your experience with Hotpatch, Kris Pennington?
Please sign in to leave a comment.
Comments (3 comments)