Forum Discussion
Solved
January 2022 Quality Update Breaks VPN Connections
A couple forum posts: https://community.meraki.com/t5/Security-SD-WAN/Client-VPN-Error-After-January-Windows-Updates/m-p/137114 https://www.reddit.com/r/sysadmin/comments/s1oqv8/kb5009543_januar...
- Yes, your argument is valid.
As a workaround you may use "Win32 app management" in Microsoft Intune and download the package from the Microsoft Update Catalogue and then deploy it using the Microsoft Intune, take a look at:
https://docs.microsoft.com/en-us/mem/intune/apps/apps-win32-deploy-update-package
I know it is a bit challenging but it is possible to deploy updates in the Microsoft Intune too.
Microsoft still doesn't release these out of band updates via the Windows Update for Business release channel which is how we distribute all of our updates (using update rings in Intune). Why is this not able to be deployed and managed through Microsoft's native tools that they seem to recommend so strongly for cloud-based update management?
This is like emergency update and only those affected should download it. It will be available in next cumulative update.
- I understand that it's an emergency update but we *are* affected and we manage our updates exclusively through Intune update rings in the cloud (we don't have on-prem infrastructure to assist with this).
In these emergency update cases we're now stuck either remaining unpatched for the rest of the month (not ideal from a security perspective) or we would resume our updates and then manually connect to each computer and install the update we manually download from the Windows Update catalogue. You can see how that's not really ideal, right? Now that the patch is out and fixed it would be ideal if we could push that out via Intune update rings to get users fully patched and fully functional.BrianG-PPN I can confirm the update works, but I got really surprised it is not released as critical update, as it does not seems reasonable Microsoft stop half the companies in the world and does not releases it to automatic applying. Testing, I installed all updates (as I asked all my customers to do) and the bug was there. So I could see one must choose the "Optional Updates", click on the bug correction and apply it manually. It will keep a lot of enterprises, where a technician cannot come computer by computer, in the Cave Era for some time yet.
- Yes, your argument is valid.
As a workaround you may use "Win32 app management" in Microsoft Intune and download the package from the Microsoft Update Catalogue and then deploy it using the Microsoft Intune, take a look at:
https://docs.microsoft.com/en-us/mem/intune/apps/apps-win32-deploy-update-package
I know it is a bit challenging but it is possible to deploy updates in the Microsoft Intune too.
