/build/static/layout/Breadcrumb_cap_w.png

Scripting Question


Silent uninstall of Office 2010 administrator error

08/10/2018 860 views
Hi all,

I'm new to this site and new to Kace. 
My issue is that when I try to uninstall Office 2010 via 
C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall STANDARD /dll OSETUP.DLL /config C:\app\config.xml

and use the config file 

Product="STANDARD">
     Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
     Id="SETUP_REBOOT" Value="Never" />

However I am getting an administrator error show in the pic
lca0WX.png
I'm at a loss as to why, because I have case running the uninstall as SYSTEM via KACE, and I've tried running the batch file as local admin and network admin.  

Also, we want to uninstall Office 2010 while keeping 2016 on user's computers(yes, we have both, I know), so a complete Office remove tool is out for now.
Please advise on what to do next. 

Thank you


0 Comments   [ + ] Show comments

Comments


All Answers

0
It's been a while for me so I'm not remembering the "/DLL" switch but we never used it, so that may be causing an issue for you.

Here's the syntax of an old uninstall config file which would create a log file.  Modify as appropriate and use this to see if there's any further information coming from the EXE:

<Configuration Product="ProPlus">

<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<Logging Type="Verbose" Path="c:\install_logs" Template="Office 2010 Uninstall.log" />
<Setting Id="SETUP_REBOOT" Value="Never" />

</Configuration>

Answered 08/13/2018 by: vjaneczko
9th Degree Black Belt

0
I don't have an answer for your exact problem, but the office scrub scripts allow you to remove only certain versions of office: https://github.com/OfficeDev/Office-IT-Pro-Deployment-Scripts/tree/master/Office-ProPlus-Deployment/Remove-PreviousOfficeInstalls

You can set up a powershell script that just calls "Remove-PreviousOfficeInstalls" with parameters. Here are the examples listed:
.EXAMPLE
    Remove-PreviousOfficeInstalls
In this example all Office products, except for click to run or 2016, will be removed.

.EXAMPLE
    Remove-PreviousOfficeInstalls -ProductsToRemove MainOfficeProduct,Visi0
In this example the primary office product and Visio will be removed.Click-To-Run or 2016
products will not be removed.

.EXAMPLE
    Remove-PreviousOfficeInstalls -ProductsToRemove MainOfficeProduct -RemoveClickToRunVersions $true
In this example the primary Office product will be removed even if it is Click-To-Run.

I think that will be a cleaner way for you to do this.

Answered 08/17/2018 by: pbrandvold
Orange Belt

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ