But you are not out of the woods yet! Because when you attempt to apply the latest cumulative update (in my case it was February 2017) then you will have that same Error 1603 on the Conferencing Service (OCSMCU.msi). It is not necessary to remove all the language packs and local SQL instances (at least in my case it wasn’t).Īt this point you will be able to successfully complete the full installation of Skype for Business. (First uninstall XMPP then proceed with uninstalling the core components last). The Uninstall order (for what it is worth) is the following:
But now we must remember to manually apply the latest cumulative updates after the installation completes =) Only took 10 minutes so wasn’t too big of a deal. The solution was to uninstall just the Skype components from control panel and then re-run setup. Error Message: A fatal error occurred during installation” The error that you may run into actually happens later, during the server component installation, and it is:Įrror returned while installing OcsMcu.msi, code 1603. (Additional testing would need to be done to further isolate it from here).
There is a potential third variable that might be required to run into problems as well: If you do not initially deploy conferencing during the front end pool wizard in topology builder. During the installation of Skype for Business 2017 you may run into errors if you select ‘Connect to the internet to check for updates’ andyou also change the default installation location to something other than the C:\ drive.
0 kommentar(er)
