I have windows 7 systems (32 and 64 bit) running Office 2010 Standard and ProPlus.  As in past office upgrades, I downloaded the hotfix that contains the Office Scrub file to remove the 2010 version of Office.  We are moving to Office 2013 ProPlus.  None of the commands I have tried work for deploying this via an advertisement in SCCM.  The commands I have tried are as follows:  cscript "OffScrub10.vbs" PROPLUS,STANDARD or   "OffScrub10.vbs" standard,proplus or %windir%\System32\cscript OffScrub10.vbs standard,proplus or  %windir%\System32\cscript OffScrub10.vbs proplus  exit code is usually "A failure exit code of 1921 was returned."  I have searched and have tried various suggestions.  Can anyone help me with the right command?

6 Comments   [ + ] Show Comments


  • a few questions: 1: whats the code of the VBS?, 2: what architecture of office 2010 where you using ? 3: what kind of architecture of office 2013 are you trying to deploy ?
  • 1. It's a MicrosoftFixIt50450.msi extracted vbs file for scrubbing off Office 2010. 2.) we are running both 32 and 64bit versions of Office ProPlus 2010 or Office Standard 2010. 3.) will be deploying Office ProPlus 2013 both 32 and 64 bit versions. The code does work with a manual run on the systems being tested against.
  • Running applications and installs from the commandline vs running them with SCCM is very different. Main issue is the usercontext the proces runs in.

    Manual installs run as loged-on user, SCCM installs in the context of SYSTEM. This results in failures in accessing networkdrives. Best to make sure if you run the package with "download from distribution point and execute locally".

    This might not resolve your issue as most scrub utils are not designed as an enterprise solution but as a fix for failed de-installs that should have been managed by office 2013 on install. Default behaviour is to remove old office versions. Why not use that?

    If you need to use scrub, test again but start the command from a cmd that runs in the system process. Se if it will run at all in that context.
  • Eveen - I am aware of the difference of usercontext when running at the command line. My point was that it runs successfully without issue. Didn't care at that point what account may be running it.

    We used this same deployment for the removal of Office 2003 with the Microsoft provided scrub. We are not remove all instances of Office 2010 installs such as Visio, or Project so this is the route we are taking - remove standard and proplus and leave any other module alone. I found the last time I tried to use the de-installs by Office 2010 - they did not work exactly how we needed it to.

    How do I do the cmd to run in the system process to test it that way?
  • Did you find a way to execute/install the Office Scrub Utility. Runnng into the exact same issue but using the dell Kace box.
  • My reason for wanting to use the Scrub techonology is that I don't want to copy 3GB of install half way across the planet just to perform the uninstall. If I could just run Setup.exe with the xml and only have to provide those two files it would be great, but I can't so I'm stuck trying to get this VBS to work. Why can't Microsoft just use the MSI technology that it wrote to install/uninstall?
Please log in to comment



Why are you using the 'scrub technology'?  That should only be used when Office won't uninstall through the normal procedures.

You need to use an XML file to control the uninstall process.  The command line should look something like this:

setup.exe /uninstall ProPlus /config SilentUninstallConfig.xml

The contents of the XML file will look something like this:

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

This example specifies all of Professional Plus is removed, creates a log file of the process, does it silently and does not reboot the system.

Answered 10/04/2013 by: vjaneczko
Seventh Degree Black Belt

  • So where is this command being run from? I am doing it this way because I have standard or proplus installed. Some are from deployed sccm efforts and others are from media. 32 and 64 bit versions. I am hoping to clean up these variations when we deploy 2013.
    • The SETUP.EXE command can be run manually, from SCCM or from a batch file. The trick is that the XML file has to be in the same folder as SETUP.EXE, or you have to specify the full path to it.
Please log in to comment
Answer this question or Comment on this question for clarity