New to Kace so I apologize in advance for any incorrect terminology. 

We have a mixed environment of Office installs.  Office 2007, 2010 and 2013.  None of which were pushed out by Kace.  All were manual installs.  We are in the process of migrating to Office365 and need everyone to be on 2010 or 2013 in order for Outlook to work.  I would like to remove all instances of Office 2007. In searching and reading, it looks like I have a couple of options. 

  • Create an uninstall xml file and then pass the script (or command) to the machine that has the installed software.  For example - \\servername\serverpath\setup.exe /config uninstall.xml /uninstall standard.  This seems to pass the command to the pc but the software remains so I assume I am missing something.  If I type the command directly on the machine, the software is removed as expected.  I can't seem to find a clear walk through on this so I currently have the script set up to launch the sys cmd and pass the above param.  
  • Create an uninstaller, using the Wizard.  My question about this - do I need to create a packaged MSI installer of 2007 and upload it into Kace in order for the uninstaller to run correctly? 

Thanks for any direction in the matter!

3 Comments   [ - ] Hide Comments


  • First. test that your uninstallation works in stand-alone mode before bringing Kace into the equation.

    Second, the Office installer writes a log. I can't recall the location, though. That log will give a clue as to why the uninstallation failed.
  • If you uninstall from Add/Remove programs, does this successfully remove Office 2007? If so, grab the uninstallstring from the registry and use that.
  • TY for the replies VBScab and EdT. Just a quick update. As noted above in my original post, I was able to uninstall 2007 on the machine itself by using the command, it just wouldn't work correctly when I threw case in the mix. While waiting for a reply, I moved on to pushing out 2013 with the M$ Customization Tool. It actually had the option of removing older versions of Office so I ticked that option and tried it out. Success! Thanks again for your quick replies.
    • FFR, whenever you throw something other than a command line into the mix, always, always, ALWAYS use explicit paths to files. Since you can't always know the exact path, use the old '%~DP0' trick. Also, There's no point in pointing Kace at a UNC. Like most deployment systems, it uses the local System account which, as you know, has no network access.
      • Thanks for the heads up! I'll keep that in mind as we continue to implement Kace more throughout our company.
Please log in to comment

There are no answers at this time
Answer this question or Comment on this question for clarity


Admin Script Editor
Admin Script Editor is an integrated scripting environment available free here at ITNinja