This error can occur when attempting to upgrade from Office 2007 to Office 2010 and you are installing Office 2010 from the MSOCache.
To reproduce this behavior:
Install Office 2007. Then use the following procedure to deploy the local installation source before you plan to install Office 2010. (Precache)
To deploy the local installation source separately
1. On the network installation point, open the Config.xml file in a text editor, such as Notepad. For information about the Config.xml file, see Config.xml file in Office 2010.
By default, Config.xml is located in the core product folder for the Office product that you are installing. For example, if you install Microsoft Office Professional Plus 2010, open the Config.xml file in the ProPlus.WW folder.
2. Find the LIS element (<LIS>); remove the comment marks in the line by deleting the opening <!-- and closing --> tags.
3. Set the <CACHEACTION> attribute to "CacheOnly".
The line in Config.xml should look as shown in the following example.
<LIS CACHEACTION="CacheOnly" />
4. Save the Config.xml file.
5. Run Setup.exe on users' computers; on the Setup command line, specify the path of the modified Config.xml file.
You must use a fully qualified path. For example: “\\server\share\Office2010\setup.exe /config \\server\share\Office2010\ProPlus.WW\config.xml”
Where Office2010 is the root of the network installation point.
Then attempt to install the Office 2010 upgrade following the same steps as is recommended if you were installing Office 2007 from a precache deployment. Precache the local installation source for the 2007 Office system http://technet.microsoft.com/en-us/library/cc179231(office.12).aspx
"C:\MSOCache\All Users\{90140000-0011-0000-0000-0000000FF1CE}-C\setup.exe" /config \\server\share\Office2010\ProPlus.WW\Config.xml
Results- Error: “The Language of this installation package is not supported by your system” The reason that this error occurs is because when Office 2007 is installed and it has it’s MSOCache present, and then you have the cache for Office 2010 present, the setup.exe from the cache folder ({90140000-0011-0000-0000-0000000FF1CE}-C) queries the MSOCache for all of the products that it could install. It incorrectly identifies office 2007 as an available product to install, believes the MSOCache is a “combined source”, and crashes.
Workaround- Rather than starting the Office 2010 installation from the setup.exe that resides in the MSOCache folder, start the Office 2010 install from the original network share that you had used to precache the installation.
*note* You will need to ensure that you are not using the same config.xml that you had previously used to perform the cacheonly action, (or remove the CacheOnly line) or it will simply repeat the cacheonly action rather then perform the install. This method will not copy additional data to the machine as it will detect that the MSOCache already exists.
How to install Office 2010 media from MSDN/Technet on a terminal server and enable the missing features:
How to obtain an MSDN Office 2010 key that will allow installation on a terminal server.
1. If you are an MSDN Subscriber, visit your MSDN Subscriptions Product Keys page by clicking the following link:
https://msdn.microsoft.com/subscriptions/securedownloads/cc137106.aspx
If you are a TechNet Subscriber, visit your TechNet Subscriptions Product Keys page by clicking the following link:
https://technet.microsoft.com/subscriptions/securedownloads/cc137106.aspx
2. Under Office Professional Plus 2010, note the key entitled “Terminal Service enablement for Office 2010”. The following procedure describes how to manually install Office 2010 on a Remote Desktop Services-enabled computer. It is assumed that you have installed Remote Desktop Services (or terminal services in Windows 2003/2008) and that you run the Setup program from the Office 2010 installation CD or from a network installation point.
1. Click Start, point to Settings, and then click Control Panel.
2. Click Install Application on Remote Desktop. (If installing on Windows 2003 double-click on Add or Remove Programs, and then click Add New Program. If installing on Windows 2008 double-click on install application on terminal server)
3. Click Next.
4. Click Browse.
5. Locate the Setup program (Setup.exe) for Office 2010. This can be on the Office 2010 installation CD or on a network installation point.
6. Click Setup.exe, and then click Open.
7. On the Enter your Product Key page, type in the Terminal Services Enablement product key, and then click Continue.
8. On the Read the Microsoft Software License Terms page, click the I accept the terms of this agreement check box, and then click Continue.
9. On the Choose the Installation you want page, click Customize.
10. On the Install Options tab, you can optionally click on Customize to change the installation states to either Run from my computer or Not available.
11. If you want to customize other settings, click the File Location tab or the User Information tab, and then make the changes that you want.
12. To start the installation, click Install Now.
13. When the installation is complete, click Close to close the Setup program.
14. On the After Installation page, click Next.
15. On the Finish Admin Install page, click Finish.
It is important that you perform the last two steps. These steps configure the Remote Desktop Services-enabled computer for execute mode.
Notes
The following procedure describes how to re-enable the additional features that were disabled when you use the terminal services enablement key. You must now install an additional retail key and activate your product again with that key.
To install a new product key and activate the product, use the following method.
1. If you are an MSDN Subscriber, visit your MSDN Subscriptions Product Keys page by clicking the following link: https://msdn.microsoft.com/subscriptions/securedownloads/cc137106.aspx If you are a TechNet Subscriber, visit your TechNet Subscriptions Product Keys page by clicking the following link: https://technet.microsoft.com/subscriptions/securedownloads/cc137106.aspx If using Office Professional Plus 2010, obtain the product key titled Office Professional Plus 2010. If using Visio, obtain the product key titled Visio Professional 2010. [This is a different key than the Office 2010 Professional Plus Terminal Server enablement key]
2. Open a Command Prompt window. If you are using Windows 7, Windows Vista, or Windows Server 2008 or Windows Server 2008 R2, follow these steps:
a. Click Start, type cmd in the Search box, right-click cmd.exe, and then click Run as administrator.
b. In the User Account Control dialog box, click Yes.
If you are using Windows Server 2003, follow this step:
c. Click Start, click Run, type cmd, and then click OK.
3. Install the additional product key and activate Office Professional Plus 2010. If you are using the x86 version of Office Professional Plus 2010 on an x64 version of Windows operating system, follow these steps:
a. At the command prompt, run the following command: cscript "%ProgramFiles(x86)%\Microsoft Office\Office14\ospp.vbs" /inpkey:<Product_Key> Note: <Product_Key> represents the product key that you want to install.
b. Run the following command: cscript "%ProgramFiles(x86)%\Microsoft Office\Office14\ospp.vbs" /act
In other situations, follow these steps:
a. At the command prompt, run the following command: cscript "%ProgramFiles%\Microsoft Office\Office14\ospp.vbs" /inpkey:<Product_Key>
b. Run the following command: cscript "%ProgramFiles%\Microsoft Office\Office14\ospp.vbs" /act
Video demo of procedure in Win2003
Video demo of procedure in Win2008R2
Trial versions of Office 2010 Home and Student and Office 2010 Professional are available for download today.
Get your copy here: http://office.microsoft.com/en-us/try/try-office-2010-FX101868838.aspx?WT.mc_id=MiG_HomePage
Issue:
0xC004F038 The software Licensing Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator.
Possible Causes: This issue occurs because the KMS server has not received 5 unique requests for activation. The KMS server must have requests for 5 machines that have unique computer IDs.
Resolution: Ensure that 5 unique machines have requested activation against the KMS server. If you have used sysprep in your environment it is possible Office was not rearmed prior to the image creation and as such machines may have the same Office CMID. If you have had more than 5 machine attempt activation and you are still seeing this, check the Key Management Service Host log, in eventvwr on the KMS server. You will see entries like so:
0x0,5,Ignite1.ignite.local,930bd202-a335-4c7e-bd9d-7305361f0d37,2010/6/10 19:34,0,5,0,6f327760-8c5c-417c-9b61-836a98287e0c 0x0,5,Ignite2.ignite.local,2f362dd3-fb39-4d18-94e6-de1d30dd27d5,2010/6/10 19:33,0,5,0,6f327760-8c5c-417c-9b61-836a98287e0c 0x0,5,Ignite5.ignite.local,930bd202-a335-4c7e-bd9d-7305361f0d37,2010/6/10 19:32,0,5,0,6f327760-8c5c-417c-9b61-836a98287e0c
Notice in my case Ignite5 and ignite1 have the same CMID (930bd202-a335-4c7e-bd9d-7305361f0d37).
This indicates that while the base OS image may have been generalized, the Office re-arm was skipped. *Note* When preparing Windows images that will contain Office 2010, please ensure that you run \%Program Files%\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\ospprearm.exe prior to sysprepping the image to ensure a unique Office CMID.
http://technet.microsoft.com/en-us/library/ee624357.aspx#section4 Rearm the Office 2010 installation
There is a 25-day grace period from the time of installation of KMS clients before notifications to activate are displayed to the user. If you want to deploy an image, you must rearm your Office 2010 installation before you capture the image. Rearming is important for these reasons:
o The grace timer is reset to 30 days of grace. o The grace timer is frozen. o If you do not rearm, users see notification dialog boxes at the time that the image is deployed, instead of 25-days after deployment. The 25-day grace period allows ample time for a KMS host to be found and activation to succeed. If activation is successful, users do not see notifications to activate.
o The client machine ID (CMID) is reset. o The KMS host counts the number of unique clients based on the CMID. o Use the command ospp.vbs /dcmid to check the CMID.
Rearm is also recommended for MAK deployment. If you are deploying Office 2010 configured for MAK activation, and you did not remotely activate for end-users through VAMT 2.0 or ospp.vbs, users will see an activation dialog box the first time that an Office 2010 application starts. The activation dialog box is slightly different 25 days after installation. Also, users might immediately see a red title bar if Office 2010 had not been rearmed before image capture.
To rearm your Office 2010 installation
1. Make sure all Office 2010 applications are closed. 2. Open an elevated command prompt. 3. Go to <installdrive>\%Program Files%\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform. If you installed the 32-bit edition of Office 2010 on a 64-bit operating system, %Program Files% is the Program Files (x86) folder. 4. Run ospprearm.exe. If you see a message that indicates success, you are ready for image capture.
Important: Do not open an Office application, ospp.vbs, or anything related to Office 2010. Doing so starts the grace timer.
5. Capture the image or save the VM.
If you are in a situation where you have already deployed your OS image to machines, but the Office Rearm was not done during the imaging process you may be in a state now where all the machines are being used and they all have the same unique ID for Office. Here is a startup script that you could push out to those machines to rearm Office for you and generate new unique Office IDs. This will work on 32bit and 64bit flavors of Office 2010.
@echo off
:OSPPreg query HKLM\Software\Microsoft\Office\14.0\Common\OSPPREARMif %errorlevel%==1 (goto RUN) else (goto END)
:RUNset ProgramFilesPath=%ProgramFiles%"%ProgramFilesPath%\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE"C:\Windows\system32\cscript.exe "%ProgramFilesPath%\Microsoft Office\Office14\ospp.vbs" /actset ProgramFilesPath=%ProgramFiles(x86)%"%ProgramFilesPath%\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE"C:\Windows\system32\cscript.exe "%ProgramFilesPath%\Microsoft Office\Office14\ospp.vbs" /actREG ADD "HKLM\Software\Microsoft\Office\14.0\Common\OSPPREARM"
:ENDExit
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
Step 1. Identify one computer to be your KMS host. The host computer must be running one of the following operating systems:
*Windows 2008 is not supported *Windows SBS2003 is not supported Windows 2003 is unique in that it requires additional updates before Office 2010 KMS will function. If you are not using Windows 2003 skip to step #4.
Step 2. Install KMS and KMS update 1.1 for Windows 2003 from here: An update is available that installs Key Management Service 1.1 for Windows Server 2003 Service Pack 1 (SP1) and later versions http://support.microsoft.com/kb/948003
Step 3. Download and install KMS 1.2 for Windows 2003 from here: An update is available that installs Key Management Service (KMS) 1.2 for Windows Server 2003 Service Pack 2 (SP2) and for later versions of Windows Server 2003 http://support.microsoft.com/kb/968915
* KMS 1.2 for Windows 2003 is NOT required for Office 2010 KMS. We typically recommend that you install the 1.2 update however. It will add the functionality to activate VL versions of Win7 and 2008 R2
Step 4. Download and install the Microsoft Office 2010 KMS Host License Pack from here: Microsoft Office 2010 KMS Host License Pack http://www.microsoft.com/downloads/details.aspx?FamilyID=97b7b710-6831-4ce5-9ff5-fdc21fe8d965&displaylang=en
* There is a Beta version of the 2010 KMS host license Pack. Ensure that you are using the RTM version from the link above, or you will receive an “invalid product key” error when inputting your RTM KMS 2010 key.
During the installation of the Office 2010 KMS host License pack, it will ask you for your Office 2010 KMS key. Enter the key at that time. It should then activate if you have an internet connection.
Step 5. If your firewall is enabled, ensure that it has an exception set for port 1688. By default KMS will use port 1688. If this port is being blocked by your firewall Office 2010 clients will fail to activate. To do this on Windows 7 or Windows Server 2008 R2:
Step 6. Verify that the DNS entry for KMS was generated as expected. Go to the DNS console in your domain and verify that you have an _VLMCS entry for KMS in the _TCP node for your domain. Verify that the _VLMCS entry is pointing to the correct machine. Also, if you have more than one _VLMCS entry this can cause conflicts. You may want to remove the incorrect entries to ensure that the Office 2010 client is able to find your KMS server successfully.
Step 7. Run SLMGR on the KMS server to verify that the Office 2010 license pack is showing up as licensed. Open a command prompt and change the directory to c:\windows\system32. Type in “cscript slmgr.vbs /dlv all” and hit enter. You will see all of the license files that have been installed on your KMS server. You will want to scroll through to find the Office KMS 2010 entry.
Notice that the Current count is 0. Office 2010 will not start activating until the KMS host has received requests from 5 unique machines.
Step 8. On a machine which has had Office 2010 installed with a generic KMS key, open office. It should complain that activation failed. This is ok. Check the KMS host again on the server. * Now that we have run SLMGR.VBS once already and identified the Office piece we can now copy down the activation ID and run a query for only the Office 2010 host by referencing the activation ID rather than using the “all” variable. Example:
Notice the Current count now equals 1. This means that one machine has attempted activation. Keep in mind however that the KMS host will not start activating the Office 2010 clients until it has received 5 unique requests. Once you install Office 2010 on 4 other machines and open office on those machines to get the current count to 5, all additional Office 2010 clients will activate as expected.
*Hint* You can examine the eventvwr log named “Key Management Service” to identify which machines have attempted to activate against the KMS server.
Common Issues: Issue: When entering the KMS key getting an error that the key is not valid. Causes: 1. The key is not a valid Office KMS key. 2. Windows 2003 KMS server does not have KMS 1.1 update installed (or has not been reboot since installing 1.1 update.) 3. The key has been entered with a trailing space. 4. The beta version of the KMS server was installed rather than the RTM version. (See step 4 above) Issue: When activating Office 2010 you receive the ERROR CODE: 0x80070005 Issue: When attempting to activate Office 2010 receiving error "An unspecified error has occurred. Your request cannot be processed at this time. Please try again later. (0x80070001)"
Issue: 0xC004F038 The software Licensing Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator.
-Here is a video demonstration of the installation steps provided in this post-
Format: wmvDuration: