Event details
Q1. Are there any "gotchas" for upgrading straight from 2012 R2 to Server 2019?
Q2. Given the recent monthly patch issue with WSUS servers which had been upgraded from Server 2016 to Server 2022, is there any reason to avoid that route for those of us running Server 2016 WSUS servers?
- Rob-Hindman
Microsoft
Hi Tom, we fully support upgrading from 2012 R2 directly to 2019 because that within the 2 version upgrade, as documented here: https://learn.microsoft.com/en-us/windows-server/get-started/upgrade-overview#which-version-of-windows-server-should-i-upgrade-to I will leave the second part of the question, the WSUS topics for a colleague. -Rob.- GustavoRubioHi Tom, related to the WSUS question. The direct upgrade of Server 2012R2 to Server 2019 is a supported scenario. If you run the upgrade build in compatibility checker there maybe additional actions that you must take, but those will be flagged there. Alternatively, you could setup a new server as a downstream server. Sync all the updates and replace it as the upstream if you want to minimize downtime.
- GustavoRubio
Specific to the recent patch issue for WSUS servers.
Recent MIME file types (.wim and .msu) were added to support upcoming UUP updates. If you have added MIME types at other levels, then you’d need to find the config file and add <remove fileExtension=".wim" /> line above it to remove the MIME type registered higher up in the hierarchy. The removal should be fine even if .WIM MIME Type does not exist at a higher level.
An additional workaround is to remove the conflicting MIME Type from the higher level (i.e. remove .WIM from the server level in this case). This can be done via UI (inetmgr) or CLI (appcmd/powershell).
