Okay, clickbait title be damned, but hear me out here, I’ve installed a few 2019 FrontEnds and I’ve found an interesting bug on Windows Server 2016
Note: I’ve run into this bug on multiple installs as have co-workers of mine with both standard and enterprise pools. But all the installs were on Windows Server 2016 1607
Update: I’ve rebuilt a FrontEnd in the exact same environment without enabling updates. No problems, I’ve also built a FrontEnd on Server 2019 in Azure. So it might just be 2016 with the issue
If you haven’t installed this yet, don’t stress. Just install the RTM version of the software. Then update to CU1 using the updater.
If you let the Skype For Business 2019 installer auto-update itself before running Step 2 in the deployment wizard, you might run into this rather annoying bug where deploy.exe will patch each MSI individually then move onto the next and fail as there is a pending restart.
If you get an error message like one of the following
"Patching AppServer.msi…failure code 3010"
"Patching Ats.msi…failure code 3010"
"Patching CAA.msi…failure code 3010"
"Patching CAS.msi…failure code 3010"
"Patching CPS.msi…failure code 3010"
"Patching DataMCU.msi…failure code 3010"
"Patching EnterpriseWebApp.msi…failure code 3010"
"Patching MediationServer.msi…failure code 3010"
"Patching MgmtServer.msi…failure code 3010"
"Patching OcsCore.msi…failure code 3010"
"Patching OCSMCU.msi…failure code 3010"
"Patching PDP.msi…failure code 3010"
"Patching RGS.msi…failure code 3010"
"Patching Server.msi…failure code 3010"
And you restart the server for it to only happen again
And get the same error again on a different MSI file.
You might think you’re in for a few reboots. Sure this is fine for a server with one or two MSI files… But FrontEnds have a TON of roles each installed with their own MSI
So for a typical Front End Pool of 3 servers, that’s a lot of reboots!
Here’s the simple fix.
Stop all the Skype4B services and install the latest CU
Go and grab the latest update from here https://support.microsoft.com/en-au/help/4470124/updates-for-skype-for-business-server-2019
Kick off an admin PowerShell and run Stop-CsWindowsService
Then install the CU
pack you downloaded and reboot when prompted.
Note: You may get an error about Server.msi not installing correctly, that’s okay. We will sort it using Deploy.exe in a minute, the point is we don’t need to reboot the server a bunch more times…
Reboot the server when prompted and re-run step2 of the deployment wizard, note that it patches Server.msi for you
Note: If it fails with a DCOM error. Restart the server, stop the services using Stop-CsWindowsService and try Step 2 again.
Not Recommended – but might work
If you’re in a pinch and can’t get the CU for some reason you could try removing the update files from C:\ProgramData\Microsoft\Skype for Business Server\Deployment\patchcache but that would put you in a very inconsistent state and I’d patch it ASAP.
Anyway, I hope that helps someone. Till next time.