6/25/2023 0 Comments Office uninstall![]() ![]() This took me a week to figure out not realizing Kace was the issue. This triggered the 64bit Powershell.exe and the commands were executed as intended. So a solution was to use the PSADT toolkit and use the "Deploy-Application.exe" to call the powershell script. Regardless if you force Kace to use powershell in the "C:\Windows\System32\WindowsPowerShell\v1.0" directory it still uses the 32bit powershell.exe on a 64bit system. In Kace when you call powershell.exe it runs the 32bit version of Powershell. Note: Many may ask why not call powershell.exe from Kace to execute the Powershell script. Save your script and test by deploying to a test machine for results. Also, more details are available on the github link provided above NOTE: if you are removing any other office products, change your parameters to the version of office you'd like to remove. Parameters: $(KACE_DEPENDENCY_DIR)\Files\Remove-PreviousOfficeInstalls.ps1 -Remove2016Installs $true In the "On Success section, Select Add | Launch a Program. Please remember to have this script ran as a SYSTEM user
0 Comments
Leave a Reply. |