While attempting to activate your Office 2010 clients in your environment you find that some of your machines fail to activate against KMS with the following ERROR CODE: 0x80070005.

If you run OSPP.VBS to attempt activation and you may receive an error similar to the following:

C:\Program Files\Microsoft Office\Office14>cscript ospp.vbs /act

---Processing--------------------------
---------------------------------------
Installed product key detected - attempting to activate the following product:
SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c
LICENSE NAME: Office 14, OfficeProPlus-KMS_Client edition
LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel
Last 5 characters of installed product key: PKJDS
ERROR CODE: 0x80070005
---------------------------------------
---------------------------------------
---Exiting-----------------------------


If you then run OSPP.VBS to check the dstatus and you receive an error similar to the following:

C:\Program Files\Microsoft Office\Office14>cscript ospp.vbs /dstatus

---Processing--------------------------
---------------------------------------
SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c
LICENSE NAME: Office 14, OfficeProPlus-KMS_Client edition
LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel
LICENSE STATUS:  ---NOTIFICATIONS---
ERROR CODE: 0xC004F056
ERROR DESCRIPTION: The Software Licensing Service reported that the computer cou
ld not be activated using the Key Management Service (KMS).
Last 5 characters of installed product key: PKJDS
---------------------------------------
---------------------------------------
---Exiting-----------------------------

These errors can indicate a permissions issue in the registry.

There are a few reasons this error can occur. Please review the following methods to resolve.

Method #1
Please attempt to reset security permissions to default as outlined in KB313222.

How do I restore security settings to the default settings?
http://support.microsoft.com/kb/313222

Method #2
These errors can also indicate a permissions issue with the OfficeSoftwareProtectionPlatform folder. If the Network Service is missing permissions on this folder you can also receive ERROR CODE: 0x80070005.

To resolve, run the following command from an elevated command prompt:

In Vista/Win7/2008-
icacls C:\ProgramData\Microsoft\OfficeSoftwareProtectionPlatform /grant "Network Service:(OI)(CI)(R,W,D)" /t

In WinXp/2003-
cacls "C:\Documents and Settings\All Users\Microsoft\OfficeSoftwareProtectionPlatform" /t /e /p "Network Service":C

Method #3

This situation may be the result of applying a Plug and Play Group Policy object (GPO).

Computer Configuration / Policies / Windows Settings /Security Settings / System Services / Plug and Play (Startup Mode: Automatic)

If this policy is set, you can resolve this issue by either disabling this policy, or modifying the security settings for the Policy.

How to check the machine to see if that policy is being applied via a domain GPO. 
From the command prompt, run rsop.msc

Check for the the following:



If you see that Plug and Play is set to Automatic but permission is Not Defined, continue with the next steps to grant “service” rights

To check permissions for the Plug and Play service GPO via command line, run the following command:

sc sdshow plugplay

If all is configured as it should be, the output displayed when running this command will contain the following:

D:(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)
(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SY)
(A;;CCLCSWLOCRRC;;;IU)
(A;;CCLCSWLOCRRC;;;SU)
S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)

If any of these permissions are missing, run the following command line to set the default permissions for the Plug and Play service:

sc sdset plugplay D:(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SY)(A;;CCLCSWLOCRRC;;;IU)(A;;CCLCSWLOCRRC;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)

Alternatively, the following steps can be used to edit the permissions of the Group Policy via a GUI interface:

1. Open the Group Policy that is identified in Method A, Step 1 above, and open the corresponding Group Policy setting. 
2. Click the Edit Security button, and then click the Advanced button.
3. In the Advanced Security Settings for Plug and Play window click Add and then add the SERVICE account. Then, click OK
4. Select the following permissions in the Allow section and then click OK:

Query template
Query status
Enumerate dependents
Interrogate
User-defined control
Read permissions

Note: The Previous rights are the minimum required permissions. 

5. Run gpupdate /force after you apply the previous permissions to the Group Policy setting.

Windows 7 displays "Windows is not Genuine" with an error code of 0x80070005  (Also applies to Office 2010)
http://support.microsoft.com/kb/2008385

When launching Office 2010 applications, a message appears indicating that Office is not activated. Attempts to activate Office may result in the following error:

"Error 0xC004F074: The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information."

Error 0xC004F074 equates to, "The Key Management Server (KMS) is unavailable". This error occurs when volume license versions of Office 2010 are installed on client machines using the built-in, KMS client key and an Office KMS host is not available to activate installations of Office 2010.

The following is a partial Office Web Apps Setup product key, required for product installation on Microsoft SharePoint, rather than a product key that is specific to client installations of the Office 2010 suites:

FC7HF-CF42G-xxxxx-xxxxx-xxxxx

Attempting to enter this key via the File/Help and Change Product Key link will result in the error, "This is not a valid Office Product key. See above examples to learn more".

Attempting to input this key via the ospp.vbs script will result in the error, "0xc004f050 The Software Licensing service reported that the product key is invalid"

To resolve this issue, obtain a Multiple Activation Key (MAK) volume license product key for Office 2010, and then do one of the following:

1) Open an Office 2010 application (i.e., Microsoft Word), go to File/Help, and then click on the Change Product Key link. Enter the Office 2010 product key. After the process of installing the product key completes, close all open Office applications, open Microsoft Word, go to File/Help, and check to see if “Product Activated” is displayed.

—or—

2) From an elevated command prompt, run command lines similar to the following (if you are running 32-bit Office 2010 on a 64-bit operating system, the path should include Program Files (x86)):

%windir%\System32\cscript.exe "C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx     (where xxxxx-xxxxx-xxxxx-xxxxx-xxxxx is your 25 digit MAK product key for Office 2010)

%windir%\System32\cscript.exe “C:\Program Files\Microsoft Office\Office14\ospp.vbs” /act

For most Microsoft products, there are two ways to obtain volume license product keys:

1)  Go to the Product Keys section of the Volume Licensing Service Center (VLSC) for Open, Open Value, Select, Enterprise Agreements and the Services provider License Agreement (SPLA)  - https://www.microsoft.com/licensing/servicecenter/home.aspx

2) Call your Microsoft Activation Center - http://www.microsoft.com/licensing/existing-customers/activation-centers.aspx

Related links:

Frequently asked questions: Volume activation of Office 2010

http://technet.microsoft.com/en-us/library/ff678211.aspx

Volume activation quick start guide for Office 2010

http://technet.microsoft.com/en-us/library/ee624359.aspx

Microsoft Volume Licensing Product Activation and Key Information

http://www.microsoft.com/licensing/existing-customers/product-activation.aspx

Microsoft Volume Licensing Frequently Asked Questions About Volume License Keys

http://www.microsoft.com/licensing/existing-customers/product-activation-faq.aspx

There are a few upgrade options available when planning to move to Office 2010 from a previous version. Microsoft has a technet article that touches on these various options here:

Plan an upgrade to Office 2010
http://technet.microsoft.com/en-us/library/ee624354.aspx

There are three options for upgrading to Office 2010:

• In-place upgrade The earlier version of Office, such as the 2007 Microsoft Office system, is already installed on computers.
• Uninstall upgrade The earlier version of Office, such as the 2007 Office system, is first uninstalled before the upgrade to Office 2010.
• New operating system upgrade The computers get a new version of the operating system, such as Windows 7, and an upgrade to Office 2010.

One of the options that is discussed is performing uninstall-upgrades.

For a single machine this is pretty simple. Remove the previous version of Office via add/remove programs or KB290301, and then manually install Office 2010. For enterprise deployments though this gets to be trickier as these deployments will typically be automated. The purpose of this blog post is to demonstrate how to perform automated uninstall-upgrades.

The idea is that we will create a script that can automatically remove the previous version of Office, and then proceed to install Office 2010. To do this we need to first understand how to automate the removal Office 2003/2007. 

There are two methods for automating the removal Office 2003/2007.

1. Uninstall Office using the supported uninstall command line 
How to automate the uninstallation of Office 2003 products via command line
How to automate the uninstallation of Office 2007 products via command line

2. Uninstall Office by utilizing the Office removal tool. (Offscrub.vbs)
How to obtain and use Offscrub to automate the uninstallation of Office products

When choosing between which method to use for the automated removal of Office there are a couple things to consider.

If you choose to remove Office 2003/2007 with the command line uninstall option, keep in mind that the uninstallation could fail if the health of the product is poor. IE… if the source cache directory is corrupt, or if cached patches are broken. If you are removing Office 2007 and are wanting to have the uninstallation be silent, and you want to prevent the reboot, you will need to create a config.xml that contains those options and have it accessible on a share to call via the uninstall command line.

If you choose to remove Office 2003/2007 via the Offscrub technique, be familiar with the switches available for Offscrub and the FAQ.

Now that we know how we can automate the removal of Office 2003/2007 and we have decided on a method, we just need a script that can perform the uninstall actions, and then the install actions for Office 2010. 

For my examples below I am modifying the script from the technet article entitled Deploy Office 2010 by using Group Policy computer startup scripts. 
http://technet.microsoft.com/en-us/library/ff602181.aspx

*note*
If you decide to use GPO to deploy, make sure that you are familiar with the above article as there are some other considerations.
If you use this script, ensure that your share for Office 2010 doesn’t have any spaces. ie.. \\server\share\Office14
If you are deploying this script via a deployment mechanism that utilizes the SYSTEM account, make sure the system account can access the shares that are specified in the script.

In the example below, the script will first check to see if Office 2010 is installed, if it is not it will automate the removal of Office 2003/2007 via the uninstall command line, and then perform the installation of Office 2010.

Check for Office 2010, if not installed, uninstall Office 2007 via command line, and then after that is finished, install Office 2010.

uninstall-upgrade.bat

setlocal

REM *********************************************************************
REM Environment customization begins here. Modify variables below.
REM *********************************************************************

REM Get ProductName from the Office product's core Setup.xml file, and then add "office14." as a prefix. 
set ProductName=Office14.PROPLUS

REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\server\Office2010SourceFiles

REM Set ConfigFile to the configuration file to be used for deployment (required)
set ConfigFile=\\server\Office2010SourceFiles\ProPlus.WW\config.xml

REM Set LogLocation to a central directory to collect log files. (the user doing the install needs write access)
set LogLocation=\\server\Office2010LogFiles

REM *********************************************************************
REM Deployment code begins here. Do not modify anything below this line.
REM *********************************************************************

IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)

REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
:ARP64
reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if NOT %errorlevel%==1 (goto End)

REM Check for 32 and 64 bit versions of Office 2010. (Office 64bit would also appear here on a 64bit OS) 
:ARP86
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if %errorlevel%==1 (goto DeployOffice) else (goto End)

REM If 1 returned, the product was not found. Run setup here.
:DeployOffice
start /wait \\server\share\Office12\setup.exe /uninstall ProPlus /config \\server\share\UninstallConfig.xml
start /wait %DeployServer%\setup.exe /config %ConfigFile%
echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt

REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
:End

Endlocal

If we wanted to use Offscrub.vbs to perform the uninstall we could use the same script and just change the uninstall line for Office 2007 to use offscrub rather then the uninstall command line.

Check for Office 2010, if not installed, uninstall Office 2007 via Offscrub2007.vbs, and then after that is finished, install Office 2010.

uninstall-upgrade.bat

setlocal

REM *********************************************************************
REM Environment customization begins here. Modify variables below.
REM *********************************************************************

REM Get ProductName from the Office product's core Setup.xml file, and then add "office14." as a prefix. 
set ProductName=Office14.PROPLUS

REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\server\Office2010SourceFiles

REM Set ConfigFile to the configuration file to be used for deployment (required)
set ConfigFile=\\server\Office2010SourceFiles\ProPlus.WW\config.xml

REM Set LogLocation to a central directory to collect log files. (the user doing the install needs write access)
set LogLocation=\\server\Office2010LogFiles

REM *********************************************************************
REM Deployment code begins here. Do not modify anything below this line.
REM *********************************************************************

IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)

REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
:ARP64
reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if NOT %errorlevel%==1 (goto End)

REM Check for 32 and 64 bit versions of Office 2010. (Office 64bit would also appear here on a 64bit OS) 
:ARP86
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if %errorlevel%==1 (goto DeployOffice) else (goto End)

REM If 1 returned, the product was not found. Run setup here.
:DeployOffice
call cscript \\server\share\Offscrub07.vbs ProPlus /bypass 1 /q /s /NoCancel
start /wait %DeployServer%\setup.exe /config %ConfigFile%
echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt

REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
:End

Endlocal

These are example batch files. You could certainly create a VBS script, or use any other method of deployment that follows the same logic.
#1. Uninstall Office 2003/2007 using one of the available methods for automated uninstallation
#2. Wait for the uninstallation to complete.
#3. Install Office 2010.

FAQ

Will user settings still migrate if we are removing the previous version of Office 2003/2007 prior to installing Office 2010?
A- Any user settings that would migrate during a typical upgrade would still migrate when performing an uninstall-upgrade. The user settings will migrate upon the first user of each Office 2010 application.
http://technet.microsoft.com/en-us/library/ee624354.aspx#section2
The registry keys that are included or excluded when you use the in-place upgrade or the uninstall-upgrade option to migrate Microsoft Office 2003 or Office 2007 user data to Microsoft Office 2010 are listed in the following article.
http://technet.microsoft.com/en-us/library/ee624352.aspx

We are pushing the uninstall-upgrade using a deployment method that will perform the installation while a user is logged on to the machine. We have elected to use the Offscrub method and hide the CMD prompt window that Offscrub populates, but now find that there is no message to the user that the Office installation is taking place. Can we generate a notice to the users so they know that Office is being installed, and don’t try to shut down or disconnect the PC in the middle of the install?
A- It is not uncommon for folks to want to disable the command prompt window that Offscrub generates, because if that command prompt window is closed by the end user, than Offscrub will not complete. See Offscrub FAQ 

You can launch a custom IE window or a CMD window to act as the user notification if you wish. As an example, you could add the following to launch a nice notice to the user:

start "----NOTICE----" cmd.exe /t:ec /Q /k "echo OFFICE 2010 IS BEING INSTALLED. THIS WINDOW WILL CLOSE WHEN COMPLETE&&prompt $h"

Then after the install completes, close the CMD notification with:

XP
taskkill /IM cmd.exe /FI "WINDOWTITLE EQ ----NOTICE----"

Win7
taskkill /IM cmd.exe /FI "WINDOWTITLE EQ Administrator: ----NOTICE----"

So the portion of the install code above would look like this:

*note*
I am using taskkill twice in my example to ensure that the notice window would close correctly in WinXp or Win7. (cmd.exe operates slightly different in newer operating systems). It is expected that one of the lines will fail silently.

Sometimes you cannot uninstall the existing 2003, 2007 or 2010 Microsoft Office suite on your computer by using the Add or Remove Programs feature in Control Panel of Windows XP or the Programs and Features feature in Control Panel of Windows Vista/Win7. To help with this Microsoft has created Fix it utilities at http://support.microsoft.com/kb/290301.

Office uninstallation can fail if any of these are true:

• The installation process did not complete when you tried to install a new program. Therefore, you are left with a partially installed program. When you try to install the program again, you are unsuccessful.
• A previously installed program cannot be removed because the installation files are corrupted.
• If you had problems installing Office 2010 from a previous attempt.
• Office cached patches, or cached source is corrupt.

These fix it utilities can remove Office 2003-2010 products regardless of the current health of Office. These fix it utilities are provided as MSI files and run automatically without user invention. This is a good solution for folks that have a single machine that cannot uninstall the Office Suite under normal conditions. There are some limitations to the fix it solutions however. Because it is automatic, the end user cannot specify which products to remove, and the MSIs will only remove Office Suites. It will not help with the removal of standalone products. Also, the fix its lack the ability to be automated. So if you needed to run these on multiple machines, you would need to do so manually.

Fortunately, the VBS engine that the fix it uses can be obtained from the fix it and can then be automated.

Instructions to obtain Offscrub.vbs from the fix it utilities:

1. Download the fix it for the appropriate version of office, and run it.
2. Agree to the EULA and click next.
3. When you get to this screen stop and browse to the %temp% directory.

4. Find the Fixit directory in the %temp% directory and copy it to the desktop

5. You can now cancel the Fixit utility. Browse to the Fixit folder you copied to the desktop, and inside you will find offscrub.vbs. (OffScrub07.vbs in my example since I ran the Fixit for Office 2007)

Now that we have obtained the Offscrub07.vbs script from the Office 2007 Fixit, we can run it manually outside of the Fixit. We can also automate it’s usage from a command line with a variety of variables.

If you run the Offscrub2007.vbs script manually, by double-clicking or by calling it with cscript without any switches you will be presented a screen like the following:

In my example screenshot we can see that Offscrub found Access 2007 Standalone, Office 2007 Standard, and Visio Standard 2007 are installed. If I click ok on this screen the way it is, Offscrub will remove all three products from the machine. If I only wanted to remove Visio, I would remove everything in this box except VISSTD and click ok.

Using this manual method you can use Offscrub to remove Office 2007 standalone products, which you would not be able to do if you were running the Fixit alone.

If you want to automate Offscrub you can do so via command line.

Usage:  OffScrub07.vbs [List of config ProductIDs] [Options]

        /?                               ' Displays the help
        /Force                           ' Enforces file removal. May cause data loss!
        /S           ' Does not search the local hard drives for shortcuts  (*NOTE* The help file lists /SkipShortcutDetection as a valid switch to skip shortcut detection but this is incorrect. Use /S instead.)

        /Log [LogfolderPath]             ' Custom folder for log files
        /NoCancel                        ' Setup.exe and Msiexec.exe have no Cancel button
        /OSE                             ' Forces removal of the Office Source Engine service
        /Q                         ' Setup.exe and Msiexec.exe run quiet with no UI
        /Preview                         ' Run this script to preview what would get removed

Examples:
        OffScrub07.vbs CLIENTALL         ' Remove all Office 2007 Client products
        OffScrub07.vbs SERVER               ' Remove all Office 2007 Server products
        OffScrub07.vbs ALL                     ' Remove all Office 2007 Server & Client products
        OffScrub07.vbs ProPlus,PrjPro   ' Remove ProPlus and Project
 
Stages of the script
===============
- Basics :    Non customizable tasks
- Stage 1:    Component detection. Builds a list of files which are installed/registered to a product that's going to be removed.
        Depending on the amount of applications that are removed - this can be a very time consuming task.
        "/Bypass 1" allows to bypass this detection.
- Stage 2:     Remove products with Setup.exe
- Stage 3:     Remove products with direct calls to Windows Installer
- Stage 4:     CleanUp - scrub files and registry settings that remained from the previous stages.
        In combination with 'Stage 1' this is the core of the removal concept.

Usage Examples
==============
- "Safe" (Similar to calling setup.exe)
    OffScrub07.vbs ALL /Bypass 1,3,4
    OffScrub07.vbs ALL /Bypass 1,3,4 /Quiet
    OffScrub07.vbs ProPlus /Bypass 1,3,4 /Quiet

- "Preview"
    OffScrub07.vbs ALL /Preview
    OffScrub07.vbs ALL /Bypass 2 /Preview

   Note: The preview option will not give the same results as the true removal. 
   Still useful to get a good picture of what will be removed on the client

- "Quiet"
    OffScrub07.vbs ALL /Quiet

   Note: The CMD output window will still receive all messages but the UI for Setup and Msiexec tasks will be suppressed.

- "NoCancel"
    OffScrub07.vbs ALL /NoCancel

   Note: Setup and Msiexec tasks have no "Cancel" option

So if we were going to script the automation of Office 2007 ProPlus so that the uninstallation was silent, and couldn’t be cancelled, we would run a command like so:

cscript offscrub2007.vbs ProPlus /Q /NoCancel /BYPASS 1

I would advise that when automating Offscrub you skip the component detection (Stage 1) . You do this by using “/Bypass 1”.
The reason is because I have seen instances where component detection causes third party products to attempt repair. Usually this is not big deal, but if the third party product is in an unhealthy state (for example it’s missing it’s cached MSI) than it will prompt the user to locate the MSI and thus stall Offscrub. Obviously not desired if we are looking to automate the removal with no user intervention.

FAQ-

How can we remove the black window that populates when Offscrub is run?
A- If the command prompt screen is closed while offscrub is running it will fail to continue. We can prevent that by hiding the command prompt window. Edit the the Offscrub.vbs file and find for the following code at the bottom of the script:

We have elected to use the Offscrub method and hide the CMD prompt window that Offscrub populates, but now find that there is no message to the user that the Office installation is taking place. Can we generate a notice to the users so they know that Office is being installed, and don’t try to shut down or disconnect the PC in the middle of the install?
A- It is not uncommon for folks to want to disable the command prompt window that Offscrub generates, because if that command prompt window is closed by the end user, then Offscrub will not complete.

You can launch a custom IE window or a CMD window to act as the user notification if you wish. As an example, you could add the following to launch a nice notice to the user:

start "----NOTICE----" cmd.exe /t:ec /Q /k "echo OFFICE 2010 IS BEING INSTALLED. THIS WINDOW WILL CLOSE WHEN COMPLETE&&prompt $h"

Then after the install completes, close the CMD notification with:

XP
taskkill /IM cmd.exe /FI "WINDOWTITLE EQ ----NOTICE----"
Win7
taskkill /IM cmd.exe /FI "WINDOWTITLE EQ Administrator: ----NOTICE----"


The shortcut detection seems to take a long time. Can it be avoided? 
A- Yes. The shortcut detection will try to scan all drives on a machine for the Office shortcuts that align with the product being removed. This can be skipped by use a “/s” option switch when running Offscrub.

There are a couple common scenarios that occur that can cause an invalid product key error with Office 2010 volume license edition when attempting to install the VL MAK key. 

1. After purchasing a Volume License edition of Office 2010, when entering the key that came with the discs that were sent in the mail, you get invalid product key.

2. After installing the Volume License edition of Office 2010 and entering the MAK product key that you obtained from the Volume License Service Center you get invalid product key error

First it is important to understand that 32 bit versions of Office 2010 that are volume license will not ask you for a product key during the installation. Both of the scenarios above assume that you have already installed Office 2010 VL, and are now trying to enter the product key post installation by clicking on “change key”.

Issue #1

When you purchase Office 2010 from a Volume License retailer and you opt for physical media to be sent to you, you will find that it comes with 3 discs and a product key.

After you install Office 2010 successfully and try to input the product key that comes with the media you will get an invalid key error. The reason for this is because the product key that ships with the media is for “Office Web Apps” and not in fact for Office 2010 ProPlus.

To obtain the VL MAK key for Office 2010 you will need to logon to the Volume License Service Center. After you purchased your Volume License version of Office 2010, you should have received an email from the Volume Licensing Service Center (msvlop@microsoft.com) welcoming you to register at the VLSC. You will need to find this email, and login to the VLSC and obtain your VL MAK key from there. If you didn’t receive this email and you expect that you should have, or need assistance logging on to the VLSC you can call the following number for VLSC support (866-230-0560 Option 3) They should be able to pull up your VL agreement using the email address or company name of the purchaser.

Issue #2

After installing the Volume License edition of Office 2010 and entering the MAK product key that you obtained from the Volume License Service Center you get invalid product key error.

It is not uncommon for folks to install the volume license version of Office 2010 on a machine without first uninstalling the preinstalled OEM version of Office 2010 from the machine. Then when running Microsoft Office 2010 from the start menu they are actually launching the OEM version of Office 2010 rather than the VL Standard/Proplus version. The Office 2010 OEM version has an icon that looks like this:

If you are clicking on this icon, it is expected that your VL MAK key would give you an invalid key error message, because the OEM version is being run and that version will not accept a VL key.

Solution-
Check programs and features in the control panel, and ensure that you only have one entry for the Office 2010 suite. Uninstall the OEM version of the Office 2010 suite. 

Here is an example of what Programs and Features will look like when the OEM version is installed along side the Office 2010 ProPlus VL version.

The entry above that says “Microsoft Office 2010” is the OEM version of Office 2010 and will not accept a VL product key. Since you installed the Volume License version of Office 2010 Standard/ProPlus feel free to uninstall the version that is labeled “Microsoft Office 2010”.

After you uninstall the OEM version of Office 2010 now you can click on start, programs, Microsoft Office, and click on an Office application. (IE Word, Excel). Then you can input the MAK key by going to file, and help inside the application and choosing Change Product Key.

While attempting to activate your Office 2010 clients in your environment you find that some of your machines fail to activate against KMS with the following ERROR CODE: 0x80070005.

If you run OSPP.VBS to attempt activation and you may receive an error similar to the following:

C:\Program Files\Microsoft Office\Office14>cscript ospp.vbs /act

---Processing--------------------------
---------------------------------------
Installed product key detected - attempting to activate the following product:
SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c
LICENSE NAME: Office 14, OfficeProPlus-KMS_Client edition
LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel
Last 5 characters of installed product key: PKJDS
ERROR CODE: 0x80070005
---------------------------------------
---------------------------------------
---Exiting-----------------------------


If you then run OSPP.VBS to check the dstatus and you receive an error similar to the following:

C:\Program Files\Microsoft Office\Office14>cscript ospp.vbs /dstatus

---Processing--------------------------
---------------------------------------
SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c
LICENSE NAME: Office 14, OfficeProPlus-KMS_Client edition
LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel
LICENSE STATUS:  ---NOTIFICATIONS---
ERROR CODE: 0xC004F056
ERROR DESCRIPTION: The Software Licensing Service reported that the computer cou
ld not be activated using the Key Management Service (KMS).
Last 5 characters of installed product key: PKJDS
---------------------------------------
---------------------------------------
---Exiting-----------------------------

These errors can indicate a permissions issue in the registry.

There are a few reasons this error can occur. Please review the following methods to resolve.

Method #1
Please attempt to reset security permissions to default as outlined in KB313222.

How do I restore security settings to the default settings?
http://support.microsoft.com/kb/313222

Method #2
These errors can also indicate a permissions issue with the OfficeSoftwareProtectionPlatform folder. If the Network Service is missing permissions on this folder you can also receive ERROR CODE: 0x80070005.

To resolve, run the following command from an elevated command prompt:

In Vista/Win7/2008-
icacls C:\ProgramData\Microsoft\OfficeSoftwareProtectionPlatform /grant "Network Service:(OI)(CI)(R,W,D)" /t

In WinXp/2003-
cacls "C:\Documents and Settings\All Users\Microsoft\OfficeSoftwareProtectionPlatform" /t /e /p "Network Service":C

Method #3

This situation may be the result of applying a Plug and Play Group Policy object (GPO).

Computer Configuration / Policies / Windows Settings /Security Settings / System Services / Plug and Play (Startup Mode: Automatic)

If this policy is set, you can resolve this issue by either disabling this policy, or modifying the security settings for the Policy.

How to check the machine to see if that policy is being applied via a domain GPO. 
From the command prompt, run rsop.msc

Check for the the following:



If you see that Plug and Play is set to Automatic but permission is Not Defined, continue with the next steps to grant “service” rights

To check permissions for the Plug and Play service GPO via command line, run the following command:

sc sdshow plugplay

If all is configured as it should be, the output displayed when running this command will contain the following:

D:(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)
(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SY)
(A;;CCLCSWLOCRRC;;;IU)
(A;;CCLCSWLOCRRC;;;SU)
S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)

If any of these permissions are missing, run the following command line to set the default permissions for the Plug and Play service:

sc sdset plugplay D:(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SY)(A;;CCLCSWLOCRRC;;;IU)(A;;CCLCSWLOCRRC;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)

Alternatively, the following steps can be used to edit the permissions of the Group Policy via a GUI interface:

1. Open the Group Policy that is identified in Method A, Step 1 above, and open the corresponding Group Policy setting. 
2. Click the Edit Security button, and then click the Advanced button.
3. In the Advanced Security Settings for Plug and Play window click Add and then add the SERVICE account. Then, click OK
4. Select the following permissions in the Allow section and then click OK:

Query template
Query status
Enumerate dependents
Interrogate
User-defined control
Read permissions

Note: The Previous rights are the minimum required permissions. 

5. Run gpupdate /force after you apply the previous permissions to the Group Policy setting.

Windows 7 displays "Windows is not Genuine" with an error code of 0x80070005  (Also applies to Office 2010)
http://support.microsoft.com/kb/2008385

When launching Office 2010 applications, a message appears indicating that Office is not activated. Attempts to activate Office may result in the following error:

"Error 0xC004F074: The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information."

Error 0xC004F074 equates to, "The Key Management Server (KMS) is unavailable". This error occurs when volume license versions of Office 2010 are installed on client machines using the built-in, KMS client key and an Office KMS host is not available to activate installations of Office 2010.

The following is a partial Office Web Apps Setup product key, required for product installation on Microsoft SharePoint, rather than a product key that is specific to client installations of the Office 2010 suites:

FC7HF-CF42G-xxxxx-xxxxx-xxxxx

Attempting to enter this key via the File/Help and Change Product Key link will result in the error, "This is not a valid Office Product key. See above examples to learn more".

Attempting to input this key via the ospp.vbs script will result in the error, "0xc004f050 The Software Licensing service reported that the product key is invalid"

To resolve this issue, obtain a Multiple Activation Key (MAK) volume license product key for Office 2010, and then do one of the following:

1) Open an Office 2010 application (i.e., Microsoft Word), go to File/Help, and then click on the Change Product Key link. Enter the Office 2010 product key. After the process of installing the product key completes, close all open Office applications, open Microsoft Word, go to File/Help, and check to see if “Product Activated” is displayed.

—or—

2) From an elevated command prompt, run command lines similar to the following (if you are running 32-bit Office 2010 on a 64-bit operating system, the path should include Program Files (x86)):

%windir%\System32\cscript.exe "C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx     (where xxxxx-xxxxx-xxxxx-xxxxx-xxxxx is your 25 digit MAK product key for Office 2010)

%windir%\System32\cscript.exe “C:\Program Files\Microsoft Office\Office14\ospp.vbs” /act

For most Microsoft products, there are two ways to obtain volume license product keys:

1)  Go to the Product Keys section of the Volume Licensing Service Center (VLSC) for Open, Open Value, Select, Enterprise Agreements and the Services provider License Agreement (SPLA)  - https://www.microsoft.com/licensing/servicecenter/home.aspx

2) Call your Microsoft Activation Center - http://www.microsoft.com/licensing/existing-customers/activation-centers.aspx

Related links:

Frequently asked questions: Volume activation of Office 2010

http://technet.microsoft.com/en-us/library/ff678211.aspx

Volume activation quick start guide for Office 2010

http://technet.microsoft.com/en-us/library/ee624359.aspx

Microsoft Volume Licensing Product Activation and Key Information

http://www.microsoft.com/licensing/existing-customers/product-activation.aspx

Microsoft Volume Licensing Frequently Asked Questions About Volume License Keys

http://www.microsoft.com/licensing/existing-customers/product-activation-faq.aspx

There are a few upgrade options available when planning to move to Office 2010 from a previous version. Microsoft has a technet article that touches on these various options here:

Plan an upgrade to Office 2010
http://technet.microsoft.com/en-us/library/ee624354.aspx

There are three options for upgrading to Office 2010:

• In-place upgrade The earlier version of Office, such as the 2007 Microsoft Office system, is already installed on computers.
• Uninstall upgrade The earlier version of Office, such as the 2007 Office system, is first uninstalled before the upgrade to Office 2010.
• New operating system upgrade The computers get a new version of the operating system, such as Windows 7, and an upgrade to Office 2010.

One of the options that is discussed is performing uninstall-upgrades.

For a single machine this is pretty simple. Remove the previous version of Office via add/remove programs or KB290301, and then manually install Office 2010. For enterprise deployments though this gets to be trickier as these deployments will typically be automated. The purpose of this blog post is to demonstrate how to perform automated uninstall-upgrades.

The idea is that we will create a script that can automatically remove the previous version of Office, and then proceed to install Office 2010. To do this we need to first understand how to automate the removal Office 2003/2007. 

There are two methods for automating the removal Office 2003/2007.

1. Uninstall Office using the supported uninstall command line 
How to automate the uninstallation of Office 2003 products via command line
How to automate the uninstallation of Office 2007 products via command line

2. Uninstall Office by utilizing the Office removal tool. (Offscrub.vbs)
How to obtain and use Offscrub to automate the uninstallation of Office products

When choosing between which method to use for the automated removal of Office there are a couple things to consider.

If you choose to remove Office 2003/2007 with the command line uninstall option, keep in mind that the uninstallation could fail if the health of the product is poor. IE… if the source cache directory is corrupt, or if cached patches are broken. If you are removing Office 2007 and are wanting to have the uninstallation be silent, and you want to prevent the reboot, you will need to create a config.xml that contains those options and have it accessible on a share to call via the uninstall command line.

If you choose to remove Office 2003/2007 via the Offscrub technique, be familiar with the switches available for Offscrub and the FAQ.

Now that we know how we can automate the removal of Office 2003/2007 and we have decided on a method, we just need a script that can perform the uninstall actions, and then the install actions for Office 2010. 

For my examples below I am modifying the script from the technet article entitled Deploy Office 2010 by using Group Policy computer startup scripts. 
http://technet.microsoft.com/en-us/library/ff602181.aspx

*note*
If you decide to use GPO to deploy, make sure that you are familiar with the above article as there are some other considerations.
If you use this script, ensure that your share for Office 2010 doesn’t have any spaces. ie.. \\server\share\Office14
If you are deploying this script via a deployment mechanism that utilizes the SYSTEM account, make sure the system account can access the shares that are specified in the script.

In the example below, the script will first check to see if Office 2010 is installed, if it is not it will automate the removal of Office 2003/2007 via the uninstall command line, and then perform the installation of Office 2010.

Check for Office 2010, if not installed, uninstall Office 2007 via command line, and then after that is finished, install Office 2010.

uninstall-upgrade.bat

setlocal

REM *********************************************************************
REM Environment customization begins here. Modify variables below.
REM *********************************************************************

REM Get ProductName from the Office product's core Setup.xml file, and then add "office14." as a prefix. 
set ProductName=Office14.PROPLUS

REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\server\Office2010SourceFiles

REM Set ConfigFile to the configuration file to be used for deployment (required)
set ConfigFile=\\server\Office2010SourceFiles\ProPlus.WW\config.xml

REM Set LogLocation to a central directory to collect log files. (the user doing the install needs write access)
set LogLocation=\\server\Office2010LogFiles

REM *********************************************************************
REM Deployment code begins here. Do not modify anything below this line.
REM *********************************************************************

IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)

REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
:ARP64
reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if NOT %errorlevel%==1 (goto End)

REM Check for 32 and 64 bit versions of Office 2010. (Office 64bit would also appear here on a 64bit OS) 
:ARP86
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if %errorlevel%==1 (goto DeployOffice) else (goto End)

REM If 1 returned, the product was not found. Run setup here.
:DeployOffice
start /wait \\server\share\Office12\setup.exe /uninstall ProPlus /config \\server\share\UninstallConfig.xml
start /wait %DeployServer%\setup.exe /config %ConfigFile%
echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt

REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
:End

Endlocal

If we wanted to use Offscrub.vbs to perform the uninstall we could use the same script and just change the uninstall line for Office 2007 to use offscrub rather then the uninstall command line.

Check for Office 2010, if not installed, uninstall Office 2007 via Offscrub2007.vbs, and then after that is finished, install Office 2010.

uninstall-upgrade.bat

setlocal

REM *********************************************************************
REM Environment customization begins here. Modify variables below.
REM *********************************************************************

REM Get ProductName from the Office product's core Setup.xml file, and then add "office14." as a prefix. 
set ProductName=Office14.PROPLUS

REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\server\Office2010SourceFiles

REM Set ConfigFile to the configuration file to be used for deployment (required)
set ConfigFile=\\server\Office2010SourceFiles\ProPlus.WW\config.xml

REM Set LogLocation to a central directory to collect log files. (the user doing the install needs write access)
set LogLocation=\\server\Office2010LogFiles

REM *********************************************************************
REM Deployment code begins here. Do not modify anything below this line.
REM *********************************************************************

IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)

REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
:ARP64
reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if NOT %errorlevel%==1 (goto End)

REM Check for 32 and 64 bit versions of Office 2010. (Office 64bit would also appear here on a 64bit OS) 
:ARP86
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if %errorlevel%==1 (goto DeployOffice) else (goto End)

REM If 1 returned, the product was not found. Run setup here.
:DeployOffice
call cscript \\server\share\Offscrub07.vbs ProPlus /bypass 1 /q /s /NoCancel
start /wait %DeployServer%\setup.exe /config %ConfigFile%
echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt

REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
:End

Endlocal

These are example batch files. You could certainly create a VBS script, or use any other method of deployment that follows the same logic.
#1. Uninstall Office 2003/2007 using one of the available methods for automated uninstallation
#2. Wait for the uninstallation to complete.
#3. Install Office 2010.

FAQ

Will user settings still migrate if we are removing the previous version of Office 2003/2007 prior to installing Office 2010?
A- Any user settings that would migrate during a typical upgrade would still migrate when performing an uninstall-upgrade. The user settings will migrate upon the first user of each Office 2010 application.
http://technet.microsoft.com/en-us/library/ee624354.aspx#section2
The registry keys that are included or excluded when you use the in-place upgrade or the uninstall-upgrade option to migrate Microsoft Office 2003 or Office 2007 user data to Microsoft Office 2010 are listed in the following article.
http://technet.microsoft.com/en-us/library/ee624352.aspx

We are pushing the uninstall-upgrade using a deployment method that will perform the installation while a user is logged on to the machine. We have elected to use the Offscrub method and hide the CMD prompt window that Offscrub populates, but now find that there is no message to the user that the Office installation is taking place. Can we generate a notice to the users so they know that Office is being installed, and don’t try to shut down or disconnect the PC in the middle of the install?
A- It is not uncommon for folks to want to disable the command prompt window that Offscrub generates, because if that command prompt window is closed by the end user, than Offscrub will not complete. See Offscrub FAQ 

You can launch a custom IE window or a CMD window to act as the user notification if you wish. As an example, you could add the following to launch a nice notice to the user:

start "----NOTICE----" cmd.exe /t:ec /Q /k "echo OFFICE 2010 IS BEING INSTALLED. THIS WINDOW WILL CLOSE WHEN COMPLETE&&prompt $h"

Then after the install completes, close the CMD notification with:

XP
taskkill /IM cmd.exe /FI "WINDOWTITLE EQ ----NOTICE----"

Win7
taskkill /IM cmd.exe /FI "WINDOWTITLE EQ Administrator: ----NOTICE----"

So the portion of the install code above would look like this:

*note*
I am using taskkill twice in my example to ensure that the notice window would close correctly in WinXp or Win7. (cmd.exe operates slightly different in newer operating systems). It is expected that one of the lines will fail silently.

Sometimes you cannot uninstall the existing 2003, 2007 or 2010 Microsoft Office suite on your computer by using the Add or Remove Programs feature in Control Panel of Windows XP or the Programs and Features feature in Control Panel of Windows Vista/Win7. To help with this Microsoft has created Fix it utilities at http://support.microsoft.com/kb/971179.

Office uninstallation can fail if any of these are true:

• The installation process did not complete when you tried to install a new program. Therefore, you are left with a partially installed program. When you try to install the program again, you are unsuccessful.
• A previously installed program cannot be removed because the installation files are corrupted.
• If you had problems installing Office 2010 from a previous attempt.
• Office cached patches, or cached source is corrupt.

These fix it utilities can remove Office 2003-2010 products regardless of the current health of Office. These fix it utilities are provided as MSI files and run automatically without user invention. This is a good solution for folks that have a single machine that cannot uninstall the Office Suite under normal conditions. There are some limitations to the fix it solutions however. Because it is automatic, the end user cannot specify which products to remove, and the MSIs will only remove Office Suites. It will not help with the removal of standalone products. Also, the fix its lack the ability to be automated. So if you needed to run these on multiple machines, you would need to do so manually.

Fortunately, the VBS engine that the fix it uses can be obtained from the fix it and can then be automated.

Instructions to obtain Offscrub.vbs from the fix it utilities:

1. Download the fix it for the appropriate version of office, and run it.
2. Agree to the EULA and click next.
3. When you get to this screen stop and browse to the %temp% directory.

4. Find the Fixit directory in the %temp% directory and copy it to the desktop

5. You can now cancel the Fixit utility. Browse to the Fixit folder you copied to the desktop, and inside you will find offscrub.vbs. (OffScrub07.vbs in my example since I ran the Fixit for Office 2007)

Now that we have obtained the Offscrub07.vbs script from the Office 2007 Fixit, we can run it manually outside of the Fixit. We can also automate it’s usage from a command line with a variety of variables.

If you run the Offscrub2007.vbs script manually, by double-clicking or by calling it with cscript without any switches you will be presented a screen like the following:

In my example screenshot we can see that Offscrub found Access 2007 Standalone, Office 2007 Standard, and Visio Standard 2007 are installed. If I click ok on this screen the way it is, Offscrub will remove all three products from the machine. If I only wanted to remove Visio, I would remove everything in this box except VISSTD and click ok.

Using this manual method you can use Offscrub to remove Office 2007 standalone products, which you would not be able to do if you were running the Fixit alone.

If you want to automate Offscrub you can do so via command line.

Usage:  OffScrub07.vbs [List of config ProductIDs] [Options]

        /?                               ' Displays the help
        /Force                           ' Enforces file removal. May cause data loss!
        /S           ' Does not search the local hard drives for shortcuts  (*NOTE* The help file lists /SkipShortcutDetection as a valid switch to skip shortcut detection but this is incorrect. Use /S instead.)

        /Log [LogfolderPath]             ' Custom folder for log files
        /NoCancel                        ' Setup.exe and Msiexec.exe have no Cancel button
        /OSE                             ' Forces removal of the Office Source Engine service
        /Q                         ' Setup.exe and Msiexec.exe run quiet with no UI
        /Preview                         ' Run this script to preview what would get removed

Examples:
        OffScrub07.vbs CLIENTALL         ' Remove all Office 2007 Client products
        OffScrub07.vbs SERVER               ' Remove all Office 2007 Server products
        OffScrub07.vbs ALL                     ' Remove all Office 2007 Server & Client products
        OffScrub07.vbs ProPlus,PrjPro   ' Remove ProPlus and Project
 
Stages of the script
===============
- Basics :    Non customizable tasks
- Stage 1:    Component detection. Builds a list of files which are installed/registered to a product that's going to be removed.
        Depending on the amount of applications that are removed - this can be a very time consuming task.
        "/Bypass 1" allows to bypass this detection.
- Stage 2:     Remove products with Setup.exe
- Stage 3:     Remove products with direct calls to Windows Installer
- Stage 4:     CleanUp - scrub files and registry settings that remained from the previous stages.
        In combination with 'Stage 1' this is the core of the removal concept.

Usage Examples
==============
- "Safe" (Similar to calling setup.exe)
    OffScrub07.vbs ALL /Bypass 1,3,4
    OffScrub07.vbs ALL /Bypass 1,3,4 /Quiet
    OffScrub07.vbs ProPlus /Bypass 1,3,4 /Quiet

- "Preview"
    OffScrub07.vbs ALL /Preview
    OffScrub07.vbs ALL /Bypass 2 /Preview

   Note: The preview option will not give the same results as the true removal. 
   Still useful to get a good picture of what will be removed on the client

- "Quiet"
    OffScrub07.vbs ALL /Quiet

   Note: The CMD output window will still receive all messages but the UI for Setup and Msiexec tasks will be suppressed.

- "NoCancel"
    OffScrub07.vbs ALL /NoCancel

   Note: Setup and Msiexec tasks have no "Cancel" option

So if we were going to script the automation of Office 2007 ProPlus so that the uninstallation was silent, and couldn’t be cancelled, we would run a command like so:

cscript offscrub2007.vbs ProPlus /Q /NoCancel /BYPASS 1

I would advise that when automating Offscrub you skip the component detection (Stage 1) . You do this by using “/Bypass 1”.
The reason is because I have seen instances where component detection causes third party products to attempt repair. Usually this is not big deal, but if the third party product is in an unhealthy state (for example it’s missing it’s cached MSI) than it will prompt the user to locate the MSI and thus stall Offscrub. Obviously not desired if we are looking to automate the removal with no user intervention.

FAQ-

How can we remove the black window that populates when Offscrub is run?
A- If the command prompt screen is closed while offscrub is running it will fail to continue. We can prevent that by hiding the command prompt window. Edit the the Offscrub.vbs file and find for the following code at the bottom of the script:

We have elected to use the Offscrub method and hide the CMD prompt window that Offscrub populates, but now find that there is no message to the user that the Office installation is taking place. Can we generate a notice to the users so they know that Office is being installed, and don’t try to shut down or disconnect the PC in the middle of the install?
A- It is not uncommon for folks to want to disable the command prompt window that Offscrub generates, because if that command prompt window is closed by the end user, then Offscrub will not complete.

You can launch a custom IE window or a CMD window to act as the user notification if you wish. As an example, you could add the following to launch a nice notice to the user:

start "----NOTICE----" cmd.exe /t:ec /Q /k "echo OFFICE 2010 IS BEING INSTALLED. THIS WINDOW WILL CLOSE WHEN COMPLETE&&prompt $h"

Then after the install completes, close the CMD notification with:

XP
taskkill /IM cmd.exe /FI "WINDOWTITLE EQ ----NOTICE----"
Win7
taskkill /IM cmd.exe /FI "WINDOWTITLE EQ Administrator: ----NOTICE----"


The shortcut detection seems to take a long time. Can it be avoided? 
A- Yes. The shortcut detection will try to scan all drives on a machine for the Office shortcuts that align with the product being removed. This can be skipped by use a “/s” option switch when running Offscrub.

There are a couple common scenarios that occur that can cause an invalid product key error with Office 2010 volume license edition when attempting to install the VL MAK key. 

1. After purchasing a Volume License edition of Office 2010, when entering the key that came with the discs that were sent in the mail, you get invalid product key.

2. After installing the Volume License edition of Office 2010 and entering the MAK product key that you obtained from the Volume License Service Center you get invalid product key error

First it is important to understand that 32 bit versions of Office 2010 that are volume license will not ask you for a product key during the installation. Both of the scenarios above assume that you have already installed Office 2010 VL, and are now trying to enter the product key post installation by clicking on “change key”.

Issue #1

When you purchase Office 2010 from a Volume License retailer and you opt for physical media to be sent to you, you will find that it comes with 3 discs and a product key.

After you install Office 2010 successfully and try to input the product key that comes with the media you will get an invalid key error. The reason for this is because the product key that ships with the media is for “Office Web Apps” and not in fact for Office 2010 ProPlus.

To obtain the VL MAK key for Office 2010 you will need to logon to the Volume License Service Center. After you purchased your Volume License version of Office 2010, you should have received an email from the Volume Licensing Service Center (msvlop@microsoft.com) welcoming you to register at the VLSC. You will need to find this email, and login to the VLSC and obtain your VL MAK key from there. If you didn’t receive this email and you expect that you should have, or need assistance logging on to the VLSC you can call the following number for VLSC support (866-230-0560 Option 3) They should be able to pull up your VL agreement using the email address or company name of the purchaser.

Issue #2

After installing the Volume License edition of Office 2010 and entering the MAK product key that you obtained from the Volume License Service Center you get invalid product key error.

It is not uncommon for folks to install the volume license version of Office 2010 on a machine without first uninstalling the preinstalled OEM version of Office 2010 from the machine. Then when running Microsoft Office 2010 from the start menu they are actually launching the OEM version of Office 2010 rather than the VL Standard/Proplus version. The Office 2010 OEM version has an icon that looks like this:

If you are clicking on this icon, it is expected that your VL MAK key would give you an invalid key error message, because the OEM version is being run and that version will not accept a VL key.

Solution-
Check programs and features in the control panel, and ensure that you only have one entry for the Office 2010 suite. Uninstall the OEM version of the Office 2010 suite. 

Here is an example of what Programs and Features will look like when the OEM version is installed along side the Office 2010 ProPlus VL version.

The entry above that says “Microsoft Office 2010” is the OEM version of Office 2010 and will not accept a VL product key. Since you installed the Volume License version of Office 2010 Standard/ProPlus feel free to uninstall the version that is labeled “Microsoft Office 2010”.

After you uninstall the OEM version of Office 2010 now you can click on start, programs, Microsoft Office, and click on an Office application. (IE Word, Excel). Then you can input the MAK key by going to file, and help inside the application and choosing Change Product Key.

For Enterprise Customers using Office 365 ProPlus, users will be migrated to the latest version in February of 2016. If you want your users to stay on Office 2013 and continue to receive 2013 security updates, you can delay their migration to Office 2016 ProPlus. Your users will continue to receive security updates for Office 2013 ProPlus until February 2017 through the same update method you are currently using. However after that time, no additional security updates will be made for Office 2013 ProPlus, so we strongly recommend that you migrate to the latest version before February of 2017.

There are three ways we can delay the migration to Office 2016 ProPlus, The first is to use a GPO setting that blocks the update or you can push out a registry key manually that will do the same. Those options are outlined in our KB here:

https://support.microsoft.com/en-us/kb/3097292

Thirdly, we can use the Office Deployment Tool (ODT) and the configuration.xml file to prevent the migration as well.

In the configuration.xml file we will add the AutoUpgrade attribute and set it to "FALSE" like in this example configuration.xml file here:

<Configuration> 
<Updates Enabled="TRUE" AutoUpgrade="FALSE" />
</Configuration>

The Office Deployment tool was updated in December of 2015 to accommodate this new switch. If you are using the old version of the tool you can download the newest one here.

Additional Links:

Prepare to update Office 365 ProPlus to the Office 2016 version

https://technet.microsoft.com/en-us/library/mt422981.aspx

We always recommend only having one version of Office on a machine and we recommend you use our most current versions. Having said that, there are times that due to adoption, testing, budget or migration strategies, it becomes necessary to have multiple versions of Office on a machine. There are certain combinations that are supported and others that are not.

First, there are now two architectures of Office builds. Volume Licensing (MSI) and Office click-to-run (Office 365) There are also three main Office products that we will look at here. Office Professional Plus, Visio and Project. Also, for the purpose of this article, installing one application like Skype for Business for example is the same as installing the entire Office suite. I will walk through some supported and unsupported scenarios here:

Unsupported:

Any MSI product(s) alongside the same year’s Click-to-run product(s) Example – Office ProPlus 2013 click-to-run and Visio 2013 MSI

Any Office 2013 Click-to-run product(s) alongside any 2016 click-to-run product(s).

Any Office 2016 click-to-run product alongside 2016 MSI language packs. (*note- you can have Office 2013 click-to-run and 2013 MSI language packs but they are not recommended. There are some known issues with this configuration)

Supported: (but not recommended)

Office ProPlus 2016 click-to-run and any 2013, 2010, or 2007 MSI product (ProPlus, Visio, Project)

Office ProPlus 2013 click-to-run and any 2016, 2010 or 2007 MSI product (ProPlus, Visio, Project)

Any combination of Office 2007, 2010, 2013 and 2016 MSI products (*note – you can only have one version of Outlook running at one time)

Keep in mind that there is a reason that we will say “supported but not recommended.” Issues with SharePoint Integration, Interop keys and other issues have been reported, as well as potentially new issues can occur when you use multiple versions of Office. So again, we recommend always being on the latest and greatest builds.

Additional resources:

Office installed using Click-to-Run and Window Installer on same computer isn't supported:
https://support.office.com/en-us/article/Office-installed-using-Click-to-Run-and-Window-Installer-on-same-computer-isn-t-supported-30775ef4-fa77-4f47-98fb-c5826a6926cd?ui=en-US&rs=en-US&ad=US

Install and use different versions of Office on the same PC:
https://support.office.com/en-us/article/Install-and-use-different-versions-of-Office-on-the-same-PC-6EBB44CE-18A3-43F9-A187-B78C513788BF

Issue: When customers install Office Professional Plus 2013 MSI or Lync 2013 MSI standalone and use the Office Customization Tool (OCT) to change the default Start Menu Shortcut path, after installing the April 2015 update for Office which transforms Lync 2013 to Skype for Business 2013, the shortcut for Skype for Business will remain as “Lync 2013” which can be confusing for end users.

We can work around this by using a PowerShell script like the following sample to change the Lync shortcut icons to Skype for Business icons. *Note – this script is an example script and should be tested before being used in production.

============================================
$shortcutLocation = "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Office 2013\"
$oldShortcut = "Lync 2013.lnk"
$newShortcut = "Skype for Business 2015.lnk"
$iconComment = "Connect with people everywhere through voice and video calls, Skype Meetings, and IM."

# Rename shortcut:
Rename-Item $shortcutLocation$oldShortcut $newShortcut

# Change the new shortcut settings
$shell = New-Object -COM WScript.Shell
$shortcut = $shell.CreateShortcut($shortcutLocation+$newShortcut)
$shortcut.Description = $iconcomment
$shortcut.Save()

#Get the Icon Name and Folder
$iconlocation = $shortcut.IconLocation
$tempInd = $iconlocation.indexof("Icon")

$iconName = $iconlocation.substring($tempInd,$iconlocation.indexof(".exe")-$tempInd )
$iconFolder = $iconlocation.substring(0,$tempInd)

#Change the icon:
Rename-Item $iconFolder$iconName".exe" $iconFolder$iconName"_old.exe"
Copy-Item $iconFolder"lyncicon.exe" $iconFolder$iconName".exe" -force

=====================================

This blog was submitted by Jeremy Chapman, director on the Office team

Many organizations use the Microsoft Deployment Toolkit (MDT) to deploy Windows with Office to new computers or when re-imaging computers. You can use the tools to deploy just applications, or as part of an operating system + application deployment.

If you’ve been deploying Office or using MDT for a few years, you may know that the integration for Office deployment began in 2007 when MDT was called Business Desktop Deployment 2007 and Office 2007 suites introduced the Office Customization Tool. These capabilities have remained largely unchanged for the MSI package versions of Office over the years – currently Office Professional Plus 2016 and Office Standard 2016.

Fast forward to 2016 and while the tools have been consistent for around nine years, what if you were the IT administrator tasked with building out an imaging solution for Windows 10 and Office 2016 today using MDT? Where is the process documented for installing Office 2016? It turns out the process is documented on TechNet… but labeled as the approach for Office 2010. In reality, the same approach works in Office 2013 and Office 2016 MSI packages.

Once you’ve downloaded and installed MDT, installed the Windows 10 Automated Deployment Kit, and downloaded Office installation files from the Volume Licensing Service Center, here’s what you do to add Office 2016 into your MDT deployment share.

1.  Under MDT Deployment Share, click Applications and then click New Application in the Action pane. The New Application Wizard opens to the Application Type page.

2.  On the Application Type page, make sure that Application with source files is selected, and then click Next.

3.   On the Details page:

       a.     Under Publisher, type the name of the application publisher (optional).

       b.     Under Application Name, type a descriptive name for the application (required).

       c.     Under Version, type the application version (optional).

       d.     Under Language, type the application language (optional).

       e.     Click Next.

4.   On the Source page:

       a.     Click Browse. In the Browse for Folder dialog box, locate and select the folder that contains the setup files for the particular application, and then click OK.

       Note: If you want to move the setup files instead of copying them, select the check box that is next to Move the files to the deployment share instead of copying them.

       b.    Click Next.

5.    On the Destination page, accept or change the default destination folder (the deployment share folder that will contain the application source files) that was assigned by the wizard, and then click Next.

6.    On the Command Details page:

       a. Under Command line, type the command that you want to be run at the start of the application installation. This is typically “setup.exe”, you can access the Office Customization Tool via the Application Properties > Office Products tab later.

       b. Click Next

7.    On the Summary page, click Next.

8.    The Progress page indicates that the share is being created. On the Confirmation page, click Finish. The New Application Wizard finishes, and the application name that you typed in the Application Name page appears in the Deployment Workbench details pane.

Now you can access the properties of the Office 2016 install in the Applications menu of your deployment share.

Here in the Office Products tab, you can select the Office product to install and configure Display Level, automatically accept the EULA and suppress reboots.

The majority of your granular Office customization will be done via the Office Customization Tool (OCT), which outputs an update (.MSP) file that is automatically consumed as part of the Office installation. Plus you can use MDT to deploy additional Office applications – like the legacy versions of InfoPath or SharePoint Designer – or use it to install custom Office add-ins. Once you’ve finished the above steps and anything you want to do with the OCT, you can start building Windows or custom application-only deployment task sequences with MDT. 

Starting April, 2016, MSI-based non-security updates will be released on the first Tuesday of each month and MSI-based security updates will be released (as usual) on the second Tuesday of each month.

For more details, please see the following blog post:

https://blogs.technet.microsoft.com/office_sustained_engineering/2016/03/28/upcoming-change-to-the-release-schedule-for-non-security-updates/

After you install the April 5, 2016, update for Outlook 2013 (KB3114941), you may experience random crashes of Microsoft Lync 2013 (Skype for Business) or Microsoft Outlook 2013, or both. This issue is outlined in detail here.

The workaround is to roll your 2013 ProPlus users back to the March build – here are the steps to do so:

Referencing this article, we can use the C:\Program Files\Microsoft Office 15\Clientx64\OfficeC2RClient.exe command to roll a user back to the March build. If your organization is using the Microsoft CDN to get your Office click to run updates, simply run this command on your affected machine(s):

C:\Program Files\Microsoft Office 15\Clientx64\OfficeC2RClient.exe /update user updatetoversion=15.0.4805.1003   *note – in the article linked at the beginning of this paragraph, there are other switches we can also add such as display level and update prompts for the users that we can also use depending on the experience you want to deliver for this workaround.

If you are managing your own updates, you have to take one extra step by first downloading the 15.0.4805.1003 build first if you no longer have it. This is because if we do not use the Office CDN as our updates location, but rather an internal file share, when running the command to roll back to the March build, Office will look to that internal updates location for 15.0.4805.1003. If it is not present, we will see this error:

If you are not sure if your updates are coming from an internal share or the Microsoft CDN, look to this registry key to tell us:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\ClickToRun\configuration

In this key, look for UpdateURL and the value will either be HTTP://officecdn.microsoft.com/…. indicating you are using Microsoft’s CDN or you will see \\servername\share\… Indicating you are managing your own updates. If you don’t have an UpdateURL value at all, you are also using the Microsoft CDN.

Once you verify that your organization is managing its own updates, we can use the Office Deployment Tool (ODT) to download 15.0.4805.1003 and then add it your internal update share.

Here is a blog outlining how to use the Office Deployment Tool (ODT)

One change we will have to make when using the Office deployment tool is we will have to specify the version we want to download because the default is to download the newest version and we want 15.0.4805.1003. Here is what your configuration.xml file will look like with the added Version value.

<Configuration>
<Add SourcePath=”\\server\share\…” Version=”15.0.4805.1003″ OfficeClientEdition=”32″ >
<Product ID=”O365ProPlusRetail”>
<Language ID=”en-us” />
</Product>
</Add>
</Configuration>

Next, follow the steps outlined in the Using the Office Deployment tool for click to run blog to download (setup.exe /download configuration.xml) 15.0.4805.1003 and once the download is complete, add the source files to your internal updates location. Now we can run the command to roll back to that build:

C:\Program Files\Microsoft Office 15\Clientx64\OfficeC2RClient.exe /update user updatetoversion=15.0.4805.1003

Links:

April 5, 2016, update for Outlook 2013 (KB3114941) https://support.microsoft.com/en-us/kb/3114941

Lync 2013 (Skype for Business) or Outlook 2013 Crash https://support.microsoft.com/en-us/kb/3158521

The new Update Now feature for Office 2013 Click-to-Run for Office365 https://blogs.technet.microsoft.com/odsupport/2014/03/03/the-new-update-now-feature-for-office-2013-click-to-run-for-office365-and-its-associated-command-line-and-switches/

Using the Office Deployment Tool for Click-to-Run https://blogs.technet.microsoft.com/odsupport/2014/07/11/using-the-office-deployment-tool-for-click-to-run/

Issue:

If your organization has not taken steps to prevent the upgrade, users will start seeing the following business bar in their Office applications:

Resolution:

If you would like to stop receiving this business bar and block upgrades, please take the following steps:

1. Follow these steps to prevent the upgrade
2. On the systems that already seeing the above business bar, edit the following registry key:
   1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\ClickToRun\Updates
      UpgradePackageVersion REG_SZ   Value = 0.0.0.0

 

More Information:

When you are ready to enable upgrades simply undo the changes you made per the steps to prevent the upgrade.

 

Issue: After the recent release of the Office Deployment Tool version 16.0.7118.5775 users are seeing issues with installs/updates due to not having the V32.cab data file come down with the source files download.

Errors seen are 30029.1011 and a few other issues all stemming from the missing v32.cab file.

NOTE: Microsoft is aware of this issue and working on releasing an updated version of the Office Deployment Tool as soon as possible.

Workaround: The current workaround is to copy, duplicate, and rename the copied v32_16.0.xxxx.xxx.cab to v32.cab (See Below)

Step 1: Source file location after the initial download. As stated above you’re missing the v32.cab file.

Step 2: Copy, and then paste the copied version seen below.

Step 3: Then rename the resulting copied V32_versoned.cab to v32.cab to allow Install/Updates to continue as expected.

Office 365 updates are designed to be very network bandwidth friendly. There is Binary Delta Compression that occurs so long as the machines are staying current and Office has built in throttles to prevent every machine from trying to update at the same time. However, IT admins will sometimes still need to monitor the size of the monthly updates very closely. Here is how to determine how large the update for Office ProPlus will be:

Step 1.
Download Process Monitor from the Windows Sysinternals collection here:
https://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

Step 2.
When you launch Process Monitor the filter menu may auto load but if not, click on Filter > filter to open the filter menu. In here Exclude the following Event Classes:

• Registry
• File System
• Process

And only include the “OfficeClicktoRun.exe” Process Name. Your filter should look something like this:

Step 3.
Start Process Monitor and launch the manual update process by clicking “Update Now” in the File > Account menu of any Office Click-to-Run app. We will see the updates downloading and data filling in the Procmon log.

Step 4.
Once the update finishes, stop the Procmon trace and then check for the network traffic summary by going to Tools > Network Summary.

In my example I was on the July version of Deferred Channel – 16.0.6741.2056 and then updated to the August version – 16.0.6741.2063. As we can see, this update is 167,829,264 bytes, or roughly 167 MB of data.

We have an emerging issue where some clients that are using Shared Computer Activation (SCA) on our Office 2013 click-to-run clients cannot sign in. Users are seeing an error similar to this when trying to log in:

“There is a problem with your account. Please try again later.”

The reason is one of the required URLs for SCA is being blocked by some security programs:

http://clientconfig.microsoftonline-p.net/fplist.xml

We are investigating why this particular URL is being flagged to be blocked, but to fix this issue, please work with your networking and security team to ensure that this URL is whitelisted per our documentation of required URLs for Authentication and Identity here:

https://support.office.com/en-us/article/Network-requests-in-Office-365-ProPlus-eb73fcd1-ca88-4d02-a74b-2dd3a9f3364d?ui=en-US&rs=en-US&ad=US