I can put it into my post-upgrade script (that's getting longer and longer as we find more things that the upgrade breaks). However we can't do that for >1000 machines over >100 sites, so I need to find some way to script this. However I tried a manual repair from Control Panel\Programs and Features and this worked correctly and fixed the issue. Setup.exe /repair ProPlusWW but it said that the install was corrupt and I'd have to use the msi. I've tried running c:\program files (x86)\common files\Microsoft shared\office16\office setup controller\ (that I know of, unless the install leaves it in a folder somewhere). It looks like I need to do a quick repair on the Office install, but a) it needs to be silent and b) the install msi isn't on the machines to use for the repair. See the table below for a list of proplusww.msi files we have available for download for most Windows versions. Script that runs immediately post upgrade. msi references which could be cause of the error. I need to find a way to add a fix to the PowerShell A continuación, vaya a la carpeta 'Descargado' de su navegador web y copie el archivo ProPlusrWW.msi descargado. Seleccione la versión del archivo compatible con su sistema operativo y haga clic en el botón 'Descargar'. Unfortunately the upgrade from Windto 1709 breaks Outlook search - presumably the indexing. La última solución es descargar y reemplazar manualmente el archivo ProPlusrWW.msi en la carpeta apropiada del disco. We have Windows 10 systems running Office 2016 ProPlus installed from the msi during the build from SCCM. If you don't know which log is the correct log for the ProPlusWW.msi component, open each log one at a time and scroll to the bottom. I've posted this on the Office forums but they directed me here. If you know that the failure is in ProPlusWW.msi, but you don't want to waste time finding which MSI log is for ProPlus, it's usually the largest log file.
0 kommentar(er)
