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

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

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.

Volume license editions Office 2010 support KMS activation. If your environment has an existing KMS host for activating Windows you have a few ways of activating Office 2010 using a KMS host:

1. Use your existing Windows KMS host and add Office KMS support to it, if it is running a supported version of Windows (recommended)
2. Migrate your Windows KMS host to a version of Windows that supports Office KMS and add Office KMS support to it (recommended)
3. Install Office KMS support on a different computer and configure your environment for it.

Adding Office KMS support to an existing Windows KMS host if your best option, because doing so does not require any work being done outside of installing Office 2010 KeyManagementServiceHost.exe and installing/activating your Office 2010 KMS host key. The catch here is you must be running Windows KMS on an operating system that supports Office 2010 KMS. See this post for details on supported operating systems and for steps on installing Office 2010 KMS host: http://blogs.technet.com/b/odsupport/archive/2010/06/01/office-2010-kms-installation-and-troubleshooting.aspx.

I’m going to focus on option 3 for the rest of this post – installing Office KMS support on a second computer in an environment that already has a Windows KMS host running. The steps to install Office KMS is the same as step 1 and 2. So is installing and activating your key. You should note that this is not the recommended way of adding Office KMS support. Microsoft recommends only having a single KMS host for both Windows and Office. Having more than one KMS host on your network is not necessary and adds extra administration work to implement. The extra work involves preparing DNS to allow multiple computers to manage _VLMCS records.

When you install a KMS host and install a key, your KMS host registers itself in DNS by adding a _VLMCS record to DNS. The first KMS server to do this owns all rights for _VLMCS records. When you bring a second KMS host online it will not be able to register itself in DNS. Your KMS host will work, but your client computers will not be able to find it because the _VLMCS record for it does not exist in DNS. There are two way to fix this:

1. Manually add a _VLMCS record to DNS for the second KMS host
2. Create a global security group that contains the machine accounts for your KMS hosts and grant that group control over _VLMCS records in DNS (recommended).

You can follow the steps in this article to configure DNS for multiple KMS hosts: http://technet.microsoft.com/en-us/library/ff793405.aspx. Keep in mind that the SRV resource record you want to edit permissions on in DNS is the _VLMCS record of your KMS host. Editing this record’s permissions to grant the global security control will enable additional _VLMCS records to be created by the other KMS hosts as needed.

We recommend the 2nd option here to keep future administrative tasks to a minimum. If you ever change the host name DNS will be updated automatically. Stale _VLMCS records in DNS can cause long delays in launching Office applications if they are requesting activation.

While attempting to activate your Office 2010 in your environment you find that the machine fails to activate with the following error:

.
These errors can indicate a permissions issue in the registry.

The following solution may resolve this issue.

#1 Download and install Subinacl from:
http://www.microsoft.com/downloads/details.aspx?familyid=e8ba3e56-d8fe-4a91-93cf-ed6985e3927b&displaylang=en

#2 Download and save the file attachment at the bottom of this blog post. Extract activationfix.bat from the .zip file and save it to the root of c:\

#3 Open an elevated command prompt window and enter a command similar to the following

              Syntax :     at TIME c:\activationfix.bat

With this command note that you need to replace "TIME” with a time in the future in 24:00 format. For example, if your system clock currently says it is 11:00 AM you could use the following command:

Usage Example:     at 11:02 c:\activationfix.bat

If your system clock shows that it is currently 4:00 PM you could use the following command:

Usage Example:     at 16:02 c:\activationfix.bat

After you have run the “AT” command with a specified time in the future (minute or two will do the trick) you will now need to wait for that time to pass.
*Note* If you open taskmanager and sort by name, you should see subinacl.exe run as system briefly when the time specified is reached.

After the time that you specified in the “AT” command has passed, Reboot the machine, then attempt your Office 2010 activation attempt again.

#4 Cleanup. Hopefully you were able to activate Office 2010 after following these instructions. You can now uninstall Subinacl via Add/remove programs, and delete c:\activationfix.bat.

Sometimes it is required to activate the Office 2010 KMS host in a disconnected environment. Here are the steps required to activate Office 2010 KMS via the phone.

*NOTE*  If you don’t already have Office 2010 KMS installed please install it as described in the following blog post:
Office 2010 KMS installation and troubleshooting

After installing the Office 2010 KMS host pack from here, and entering your product key, you should get an error during activation if you are not connected to the internet.

Open a command prompt and change the directory to c:\windows\system32.
Type in “cscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864” and hit enter.

You will see your Office 2010 KMS server all of the license files that have been installed on your KMS server.

Copy the activation ID, and the installation ID into a notepad file.
I would then recommend that you put dashes after every 6 characters in the installation ID. like so:

020362-296235-955944-683420-831782-083181-398723-978944-769744

If you are in the USA, you can then dial phone # 888-725-1047 to input your installation ID.
If you are NOT in the USA, at a command prompt type “c:\windows\system32\slui.exe 4”. Then choose your country to get the phone #. After you get your phone # from this screen, Close the windows activation window, as we ONLY wanted the phone #.

After you give the automated voice your installation ID, it will return with a confirmation ID.

For example my confirmation ID might be

XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX

Remove the dashes from your confirmation ID:

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Then to activate use the following command under C:\Windows\system32:

cscript slmgr.vbs /atp XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX bfe7a195-4f8f-4f0b-a622-cf13c7d16864

Here is a Video demonstration of how to activate Office 2010 KMS host via phone activation in a disconnected environment.

View Video
Format: wmv
Duration: 5:51

If you are deploying volume editions of Office 2010 using KMS or MAK activation, the Volume Activation Management Tool (VAMT) 2.0 can be used to manage activation for these products. In this video I walk you through using VAMT 2.0 to activate Office 2010 installations and manage Office 2010 product keys.

If you haven’t already downloaded VAMT 2.0 you can grab a copy here: http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582

This article on TechNet that walks you through VAMT 2.0 usage. It is focused on Windows activation, but the same steps apply for Office 2010: http://technet.microsoft.com/en-us/library/ff686878.aspx

View Video
Format: wmv
Duration: 12:17

When using the Office Customization Tool (OCT) to create an MSP file for a customized installation of Office 2010, you may find that after installing Office 2010, users with existing Outlook profiles have multiple Exchange accounts configured instead of a single one that is desired.

The following screenshot depicts an example of this behavior:

To prevent this issue from occurring, use the following steps:

1) Use the Office 2010 Customization Tool (OCT) to open an existing MSP file, then:

a. Under the Outlook section, select the Export Settings option.

b. Click Export Profile Settings.
c. Save the .prf file to the local drive as Custom14.PRF or any other desired filename. This file will eventually be embedded in the MSP and copied to client machines during the installation of Office 2010.

2) Open the exported .prf file using Notepad and make the following changes:

a. Add the following line to the [General] section:

BackupProfile=False

The following is an example of this change:

[General]
Custom=1
DefaultProfile=Yes
OverwriteProfile=Append
ModifyDefaultProfileIfPresent=true
BackupProfile=False

b. In the section that corresponds to the Microsoft Exchange Service (as shown in the [Server List] section), change the line with UniqueService=No to UniqueService=Yes.

Note: The Microsoft Exchange Service section is typically the [Service1] section.

The following is an example of this change:

[Service1]
OverwriteExistingService=No
UniqueService=Yes
MailboxName=%UserName%
HomeServer=Exchange07

c. Save and close the file (ensure that the .prf file extension is maintained).

3) Back in the OCT:

a. Click Outlook profile.
b. Select the Apply PRF option.

c. Click Browse and select the modified .prf file from step 1c above.

d. Save and close the MSP file.

4) Use the custom MSP file to deploy a customized installation of Office 2010.

NOTE: If Outlook/Exchange settings in the MSP file need to be edited in the future, the custom PRF file created to work around this issue must be copied to the same location as it was when originally imported into the OCT (i.e., C:\Custom14.PRF) on the machine that you’re running the Office Customization Tool on when modifying the MSP file.

The following screenshot depicts an error which will occur when editing an MSP on a machine where the custom PRF file does not exist in the location that it was originally imported into the MSP from:

By default when you install a volume license version of Office 2010 it will not ask for a product key. All Office 2010 client VL builds are pre-PID’ed with a single global product key. When you install Office 2010 VL without a product key it automatically enables Office to seek out a KMS host to activate against.

You may want to deploy Office 2010 VL with a MAK key however. When you deploy Office 2010 VL with a MAK key you may find that on first launch a user gets the activation screen like so.

You can attempt to avoid this screen by chaining a command in the config.xml that will kick off an internet activation automatically and silently after the installation.

When installing on an X64 operating system add the following command line in the config.xml

<Command Path="%windir%\system32\cscript.exe" Args='"C:\Program Files (x86)\Microsoft Office\Office14\ospp.vbs" /act' ChainPosition="after" Execute="install" Wait="-1"/>

When installing on an X86 operating system add the following command line in the config.xml.

<Command Path="%windir%\system32\cscript.exe" Args='"C:\Program Files\Microsoft Office\Office14\ospp.vbs" /act' ChainPosition="after" Execute="install" Wait="-1"/>

Use the following steps to see detailed information about what type of activation your Office 2010 installation us using and what the status of your activation is.

1. Open an administrative level command prompt.
2. Navigate to the Office14 folder:
   • 32bit Office on 64bit OS – “cd \Program Files(x86)\Microsoft Office\Office14”
   • 32bit Office on 32bit OS and 64bit Office on 64bit OS – “cd \Program Files\Microsoft Office\Office14”
3. Execute “cscript ospp.vbs /dstatus”
4. Look at “LICENSE NAME” for license type and “LICENSE STATUS” for activation status

If Office is KMS activated you will see “KMS_Client edition” in the license name field:

If Office is MAK activated you will see “MAK edition” in the license name field:

If Office is Retail activated you will see “Retail edition” in the license name field:

If you are running a volume licensed edition of Office 2010 and it needs to be activated, you may see this message when you open any Office 2010 application:

This message means Office is failing to activate against a KMS host on your network. KMS activation is the default activation type when you install a volume license edition of Office 2010. There are two ways of getting Office 2010 activated:

• Enter a MAK key and activate over the internet or phone
• Setup an Office 2010 KMS host and activate using it.

Option 1: Enter a MAK key and activate over the internet or phone

To enter a MAK key, click the “Change Product "Key” button and enter your key when prompted:
 

Click “Continue”, then “Install Now”.

Office will configure itself. Close any open Office 2010 applications. The next time you launch an Office application you will see a screen like this:

Go through the activation wizard. Once it is done you will be activated and should not see any of these messages again.

Option 2: Setup an Office 2010 KMS host and activate using it.

See this blog post for a very detailed guide on how to setup an Office 2010 KMS Host: http://blogs.technet.com/b/odsupport/archive/2010/06/01/office-2010-kms-installation-and-troubleshooting.aspx

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

By default when you install a volume license version of Office 2010 it will not ask for a product key. All Office 2010 client VL builds are pre-PID’ed with a single global product key. When you install Office 2010 VL without a product key it automatically enables Office to seek out a KMS host to activate against.

You may want to deploy Office 2010 VL with a MAK key however. When you deploy Office 2010 VL with a MAK key you may find that on first launch a user gets the activation screen like so.

You can attempt to avoid this screen by automating the MAK internet activation by adding the following line in the config.xml

<Setting Id="AUTO_ACTIVATE" Value="1"/>

*Note*
Activation success will depend upon the internet status of the machine. Naturally if the machine is not connected to the internet during the install the automatic activation attempt will fail.

If you are considering the deployment of a 64-bit version of Microsoft Office 2010, it is important to understand the differences between the 32 and 64-bit versions, and be aware of the deployment considerations.

See the following blog posts and TechNet articles for related information:

Microsoft Office Product Development Group blog post, Understanding 64-Bit Office
http://blogs.technet.com/b/office2010/archive/2010/02/23/understanding-64-bit-office.aspx

64-bit editions of Office 2010
http://technet.microsoft.com/en-us/library/ee681792.aspx

Deployment considerations
http://technet.microsoft.com/en-us/library/ee681792.aspx#BKMK_DeploymentConsiderations

Blocking and nonblocking Office applications in 64-bit installations
http://technet.microsoft.com/en-us/library/ee681792.aspx#BKMK_AppsAffectingInstall

The images below are excerpts from a visual representation of the 64-bit Client Installation of Microsoft Office 2010, which can be found at http://go.microsoft.com/fwlink/?LinkId=168620.

Thinking about deploying Microsoft Office 2010 in your environment? Curious about the how, when, and whys of a customized deployment of Office? Do you want your installation of Office to go as easily and smoothly as possible?

If the answer to any of the above questions is yes, you should consider attending one of the Office 2010 Deployment Workshops that will be delivered in cities around the country in the coming months.

These workshops are designed to provide customers with information necessary to design, deploy, customize and manage an Office 2010 installation through instructor-led training and hands-on labs. Instructors are members of the Microsoft Office Deployment Support team, who will draw upon years of real world experience while working with attendees to share tips/tricks/best practices, and engage in fruitful discussions.

Key Focus Areas:
•    Preparing to Deploy (Requirements, deployment overview, & 32/64-bit considerations)
•    New Features and Options (Ribbon UI, application changes, Click to Run & Office Web Applications)
•    Licensing and Activation (Overview, KMS/MAK, troubleshooting)
•    Multi-Lingual Deployment (Multilanguage pack, proofing tools & considerations)
•    Customizing the Office 2010 Installation (Office Customization Tool, config.xml files & policy templates)
•    Enterprise Deployment Methods (SCE/SCCM, Group Policy, Terminal Server, imaging & virtualization)
•    Troubleshooting and Maintenance (Setup.exe, logging, patching & maintenance)
•    Application Compatibility Tools (OMPM, OEAT & OCCI)

Recommended Audience:
IT Professionals responsible for the deployment, maintenance, and troubleshooting of Office installations. Application-specific and/or help desk-type issues are not included in the scope of this offering.

Delivery Dates and Locations:
•    January 18-20, 2011 – Downers Grove, IL
•    January 25-27, 2011 – Alpharetta, GA
•    February 1-3, 2011 – Tampa, FL
•    February 8-10, 2011 – New York, NY
•    February 15-17, 2011 – Irvine, CA
New dates and locations will be announced here as they become available.

Pricing:
$1500 USD per person

To register or for more information:

•    To register online, visit http://www.microsoft.com/events, click the Find Events and Webcasts link, and perform an advanced search using the following EventIDs or keywords "Office 2010 Deployment":

o    Downers Grove, IL:  1032469733
o    Alpharetta, GA:  1032471261
o    Tampa, FL:  1032471263
o    New York, NY:  1032471264
o    Irvine, CA:  1032471267

•    To register via email, send mail to ProfessionalServices@Microsoft.com and include the following information:

o    Company Name
o    Attendee Name
o    Physical Address
o    Phone Number
o    Number of Attendees
o    Desired Event Location/Date

•    To register via phone, call 1-888-875-9071

•    Email inquiries to ProfessionalServices@Microsoft.com

KMS host key = This key is obtained from the VLSC. This is the key that you would use during the install of the KMS host when setting up a Office 2010 KMS server

KMS Client Key = This is a generic key that is hardcoded into all of the Office 2010 client products. ie.. ProPlus, Visio, Project.
This key allows the product to be installed without manually entering a product key. Also, when this key is installed it triggers the Office product to attempt to locate and activate against a KMS server.

Volume license versions of Office 2010 are hardcoded with a generic KMS Client Key. This key can be located by opening the setup.xml file from the *.ww folder of the product.

As an example,  here is the built-in KMS Client Key from the Visio 2010 volume license setup.xml
 

Visio is a unique product in the volume license space in that Visio can install as Visio Standard, Visio Professional, or Visio Premium based upon the key that is input. By default, Visio 2010 uses this Visio Premium 2010 KMS client key, which enables all the features that are available for Visio Premium 2010. If you are licensed to use Visio Standard 2010 or Visio Professional 2010, you must install the appropriate KMS client key. Different features or applications are available, depending on the kind of key that is installed. This makes it easier for you to upgrade or downgrade without having to deploy a different product edition.

If your license agreement with Microsoft is for Visio Standard 2010 or Visio Professional 2010, use the appropriate Generic KMS client key shown in the following table.

For information about how to plan your Visio Professional 2010 installation, see Plan customizations and options for Visio 2010.

There are two scenarios to consider for installing an appropriate KMS Client key.

Scenario 1

Visio 2010 has already been deployed in your organization.
At the time of the deployment no key was specified and as a result everyone has Visio Premium installed although the organization is licensed for Visio Standard 2010 or Visio Professional 2010.

To downgrade these versions from Premium to Pro or STD, they will need to change the installed KMS Client key to the generic PRO, or STD key using a script that calls ospp.vbs , or by using VAMT. After the key is changed it will automatically activate against the KMS s host server, provided the KMS host is healthy and reachable.

Method 1 – Using a script that calls ospp.vbs on the machine to install a new KMS Client key. This script can be pushed out as a startup script via GPO to the affected machines.

Here is a simple, example batch file script that I have used to install the Visio 2010 Client key for Standard edition post install. This should work on X86 and X64 machines. I have placed a registry key query in this script so that it checks for the existence of a registry key that does not exist natively, and then when the script runs it adds that dummy registry key. This way the next time the script runs (if deployed as a startup script for example) it will simply end when it locates the dummy key that had been added during the script’s previous run.

OSPP.BAT                                                                                                                                                                                                                                                           

Method 2 – Use the VAMT tool to install a different KMS Client key for Visio 2010 post install.

For more information and a walkthrough of the Volume Activation Management tool

Managing Office 2010 Activations using the Volume Activation Management Tool (VAMT 2.0)
http://blogs.technet.com/b/odsupport/archive/2010/08/06/managing-office-2010-activations-using-the-volume-activation-management-tool-vamt-2-0.asp

Scenario 2

Visio 2010 has not yet been deployed in the organization and we need to ensure that correct edition of Visio 2010 is deployed.

If the organization is not licensed for Premium, they will either need to ensure that they modify the config.xml (in the visio.ww folder) and include the generic KMS client key for Pro or STD, or create a custom.msp file with the Office customization tool and specify the generic KMS client key for Pro or STD. After the install Visio will activate against KMS without issue if the KMS host is activated, healthy and has had the 5 minimum unique requests.

Method 1

Modify the config.xml to specify the KMS Client key to use.  If we specify the KMS Client key for Standard edition in the config.xml file from the Visio.ww folder, than Visio will install with that KMS Client key instead of the built-in key for Premium.

As an example, here is a modified config.xml with the generic KMS Client key for Standard specified.

Method 2

Create a custom MSP file with the Office Customization Tool to specify the KMS Client key to use.  If we specify the KMS Client key for Standard edition in the Office Customization Tool and save the custom MSP in the updates folder, Visio will install with that KMS Client key instead of the built-in key for Premium.

Open the Office Customization Tool by calling setup.exe with the /admin switch

In the OCT under the Licensing and user interface section, you can choose “Enter another product key” and input your generic Pro or STD KMS Client key.

After saving the custom MSP file from the Office Customization tool, make sure to place the custom MSP file in the updates folder of the Visio source. Now when your Visio installation takes place it will use the custom msp file you created in the updates folder and apply your generic Pro/STD key rather than the built in Premium key.

This is also discussed in the following technet article:

Deploy volume activation of Office 2010
http://technet.microsoft.com/en-us/library/ee624357.aspx

This blog will cover techniques on how to identify and resolve Office installation failures. The techniques described can be applied to the installation of Office 2003-2010, and Office patches.

ENABLE VERBOSE LOGGING

The first thing to do when troubleshooting Office install failures is to ensure that MSI verbose logging is enabled. In Office 2007/2010 there is a setup.exe log file that gets created by default, but it does not give the amount of detail that is usually required to diagnose an installation failure. With verbose MSI logging enabled we will get a verbose log file for each component that Office 2007/2010 installs. We will have a verbose log for the install of the Word component, one for Excel, and so on.

To enable verbose logging you will want to set the following registry keys.

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"Debug"=dword:00000007
"Logging"="voicewarmup"

If you would prefer to automate the addition/removal of these keys rather than adding them manually via regedit you can use the fixit programs from the following KB article:

http://support.microsoft.com/kb/958052
*note* This fix it will also enable verbose logging for the windows updates site but troubleshooting windows update will not be covered in this blog article. 

We should also enable verbose logging for the setup.exe log as well. This is done by adding the following line to the config.xml that is in the .ww folder of the product you are attempting to install. (This does not apply to versions of Office that are earlier than Office 2007)

<Logging Type="verbose” Path="%temp%" Template="Microsoft Office Standard Setup(*).txt" />

For more information on the configuration of the config.xml see here.

PERFORM THE INSTALLATION ATTEMPT

If you are running your installation manually on the machine as a logged in user by double clicking on setup.exe then the log files will get generated in the %temp% directory of the user performing the installation.

The easiest way to get there:
Winxp-2003 = Click on start, then goto run, and type in %temp% and hit enter.
Windows Vista-Win7 = Click on start, and the type in %temp% in the search field and hit enter.

If you are running your installation via a deployment mechanism that utilizes the system account during the install, then the log files will get generated in %windir%\temp. 

Now that you have enabled verbose logging and know where to look for the logs, go ahead and reattempt your installation. It it failed previously, expect it to fail again but this time we are ready to capture log files that will be detailed enough to help us diagnose the failure point.

ANALYZING THE LOGS

After your install attempt you will find that you have somewhere between 1 and 20 logs from the installation attempt in your temp directory.

Here is a screenshot of the verbose logs from an install attempt from my machine.

When looking through the MSI logs we will typically want to look for a value 3 entry in the logs. Windows installer returns codes during the install which will indicate if a particular function was successful or not.

Value 1 = Success
Value 2 = Cancel
Value 3 = Error

In a good install, you would typically not see any value 3 entries in the logs.
So there are a lot of logs here to look at. I would recommend that we start with the setupexe log. This log will usually have a value 3 in it when there is a failure, but will not always be clear enough to diagnose the issue. If it doesn’t have a value 3 look for the first instance of Rolling back package. Rolling back package indicates that the Office installation had failed and now is attempting to “roll back” the installation. You should be able to identify the failure immediately above that point.  Once you find the value 3 or the Rolling back package in the setup.exe log you should be able to identify which component is failing, and from there look for the particular MSI log that corresponds with that component.

There will often be more than one value 3, or rolling back package. You should focus on the first one you find.

Below you will find a couple real life examples of office installation failures and how we were able to identify the failure point.

ANALYZE LOGS EXAMPLE 1 – Proplus 2010 install
In this example, I will search the setup log for a value 3. It is not uncommon to not find a value 3 in the setup log. In this case I didn’t get a value 3 in the setup.exe log, so next I searched the setup.exe log for Rolling back package.

Here is what I found:

Error: Failed to install product: C:\MSOCache\All Users\{90140000-0011-0000-0000-0000000FF1CE}-C\ProPlusWW.msi ErrorCode: 1603(0x643).

Log level changed from: Standard to: Verbose
Rolling back chain
08/30/2010 14:12:56 Rolling back package: ProPlusWW

This does not tell me why it failed, but it does tell me that the failure occurred during the install of the ProPlusWW.msi. Now that I know that I want to find the verbose MSI log that correlates with ProPlusWW.msi. 

*note*
In cases where you know the failure is in the ProPlusWW.msi log but you don’t want to save time in finding which MSI log is for Proplus, it will usually be the largest log file.

If you don’t know which log is the correct log for the ProPlusWW.msi component, open each log one at a time and scroll to the bottom. It will indicate there what component it just attempted to install/rollback.

For example, from the bottom of the MSIb0bc7.LOG:

MSI (s) (50:CC) [14:24:12:332]: Note: 1: 1724
MSI (s) (50:CC) [14:24:12:332]: Product: Microsoft Office Outlook MUI (English) 2010 -- Removal completed successfully.

So this is the verbose MSI log for the Office Outlook MUI component and was from the rollback. (The install failure would have occurred earlier than this)
Eventually I found the ProPlus log (it was the biggest one) and the log does indicates it is the proplus log here:

******* Product: C:\MSOCache\All Users\{90140000-0011-0000-0000-0000000FF1CE}-C\ProPlusWW.msi

I searched the log for a “value 3” and this time didn’t find one, but did see this at the bottom of the log when it ended abruptly:

MSI (s) (B0:14) [14:12:56:537]: Internal Exception during install operation: 0xc0000017 at 0x7C812AFB.
MSI (s) (B0:14) [14:12:56:537]: WER report disabled for silent install.
MSI (s) (B0:14) [14:12:56:537]: Internal MSI error. Installer terminated prematurely.

Out of memory.  Shut down other applications before retrying.
MSI (s) (B0:14) [14:12:56:537]: MainEngineThread is returning 1603

Now I have something to go off of. So I take this error and search the net for articles that may help with this error.

http://www.bing.com/search?q=%22Internal+MSI+error.+Installer+terminated+prematurely%22&form=QBRE&qs=n&sk=

I end up finding this article which lists my error almost verbatim, mentions a known issue with Windows installer 4.5, and an available hotfix.

http://support.microsoft.com/kb/972397/EN-US

Turns out that this particular machine is running WI 4.5. After installing the hotfix and rebooting, the install is successful.

ANALYZE LOGS EXAMPLE 2  - Access 2010 standalone install

In this next example, again I didn’t find a value 3 in the setupexe log, so next I searched the setup.exe log for Rolling back package.

Here is what I found:

Error: Failed to install product: C:\MSOCache\All Users\{91140000-0015-0000-0000-0000000FF1CE}-C\AccessRWW.msi ErrorCode: 1601(0x641).

Log level changed from: Standard to: Verbose
Rolling back chain
12/14/2010 12:06:05 Rolling back package: AccessRWW

Again, this does not tell me why it failed, but it does tell me that the failure occurred during the install of the AccessRWW.msi. Now that I know that I want to find the verbose MSI log that correlates with the AccessRWW.msi. 

Looking through the log files I find the one for the AccessRWW.msi:

  ******* Product: C:\MSOCache\All Users\{91140000-0015-0000-0000-0000000FF1CE}-C\AccessRWW.msi

I search it for value 3 and found:

CAInitSPPTokenStore.x86:  OMSICA : Initializing CustomAction CAInitSPPTokenStore.x86
CAInitSPPTokenStore.x86:  Error: Failed to initialize the SPP Token store. HResult: 0x80070057.
CAInitSPPTokenStore.x86: 
MSI (s) (2C:D0) [10:12:03:911]: User policy value 'DisableRollback' is 0
MSI (s) (2C:D0) [10:12:03:911]: Machine policy value 'DisableRollback' is 0
Action ended 10:12:03: InstallExecute. Return value 3.

This was resolved by ensuring that the network service is running, and that the following reg keys were present after ensuring the network service was running.

HKEY_USERS\S-1-5-20
AND
HKEY_USERS\S-1-5-19

ANALYZE LOGS EXAMPLE 3  - ProPlus 2010

In this next example, I did find a value 3 in the setupexe log.

MSI(ERROR): 'Error 1304. Error writing to file: C:\WINDOWS\winsxs\Policies\x86_policy.8.0.Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_x-ww_5f0bbcff\8.0.50727.4053.policy.  Verify that you have access to that directory.'
Log level changed from: Standard to: Verbose
Not showing message because suppress modal has been set.  Title: 'Setup', Message: 'Error 1304. Error writing to file: C:\WINDOWS\winsxs\Policies\x86_policy.8.0.Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_x-ww_5f0bbcff\8.0.50727.4053.policy.  Verify that you have access to that directory.'
Message returned: 2
MSI(USER): 'Are you certain you want to cancel?'
MSI(INFO): 'Action ended 14:03:01: InstallExecute. Return value 3.'

When you do see a value 3 in the setup.exe log it will sometimes give you enough information to resolve the issue without needing to look at the verbose MSI log. In this case the verbose MSI log simply repeated what we found in the setup.exe log as seen below.

MSI (s) (20:DC) [14:02:56:138]: Product: Microsoft Office Professional Plus 2010 -- Error 1304. Error writing to file: C:\WINDOWS\winsxs\Policies\x86_policy.8.0.Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_x-ww_5f0bbcff\8.0.50727.4053.policy.  Verify that you have access to that directory.

Error 1304. Error writing to file: C:\WINDOWS\winsxs\Policies\x86_policy.8.0.Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_x-ww_5f0bbcff\8.0.50727.4053.policy.  Verify that you have access to that directory.
Are you certain you want to cancel?
MSI (s) (20:DC) [14:03:01:646]: User policy value 'DisableRollback' is 0
MSI (s) (20:DC) [14:03:01:646]: Machine policy value 'DisableRollback' is 0
Action ended 14:03:01: InstallExecute. Return value 3.

In this case we should consider updating .net framework, and verifying the permissions in c:\windows\winsxs\

-BELOW ARE A FEW KNOWN ERRORS FROM VERBOSE LOGS AND POSSIBLE RESOLUTIONS TO TRY-

*NOTE*
Some of these suggestions discuss working with the registry.
Important- Serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows

ERROR 1935

Error 1935. An error occurred during the installation of assembly component {89EDD3A9-944B-3257-8484-D6EB6A00DDF5}. HRESULT: 0x80070003. assembly interface: IAssemblyCache, function: CreateAssemblyCacheItem, assembly name: Microsoft.VC90.ATL,version="9.0.30729.4148",type="win32",processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b"

MSI (s) (1C:9C) [10:14:26:628]: User policy value 'DisableRollback' is 0
MSI (s) (1C:9C) [10:14:26:628]: Machine policy value 'DisableRollback' is 0
Action ended 10:14:26: InstallExecute. Return value 3.

ERROR 1913

Error 1913: Setup cannot update file C:/windows/win.ini.
Verify that the file exists in your system and that you have sufficient
permissions to update it

http://social.answers.microsoft.com/Forums/en-US/officeinstall/thread/f5f97e01-3b8a-4886-ad49-d11c279b1186

ERROR 1714

Error 1714. Setup cannot remove the older version of Microsoft Office Product_Name 2007. Contact Microsoft Product Support Services (PSS) for assistance. For information about how to contact PSS, seeC:\DOCUME~1\<username>\LOCALS~1\Temp\Setup00000d64\PSS10R.CHM.

ERROR 1719

Error 1719. Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact support personnel for assistance

-Reg keys could be corrupt or incorrect at

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer

Export from a known good machine that uses the same OS and msiexec version.  
Backup and then delete existing msiserver key on the bad machine under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msiserver 
Import the reg file from the known good machine.
Reboot, and reattempt install

-http://support.microsoft.com/kb/324516
-http://support.microsoft.com/default.aspx?scid=kb;en-us;315346&Product=winxp#kb4

ERROR 1406

'Error 1406.Setup cannot write the value  to the registry key \CLSID\{13DE4A42-8D21-4C8E-BF9C-8F69CB068FCA}.  Verify that you have sufficient permissions to access the registry or contact Microsoft Product Support Services (PSS) for assistance.  For information about how to contact PSS, seeC:\Users\ADMINI~1\AppData\Local\Temp\Setup00000e64\PSS10R.CHM.'

Log level changed from: Standard to: Verbose
MSI(INFO): 'Action ended 20:24:59: InstallExecute. Return value 3.'

Possible solution(s)
This error indicates incorrect registry permissions. In the example above we would find incorrect reg perms on
HKCR\CLSID\{13DE4A42-8D21-4C8E-BF9C-8F69CB068FCA}

ERROR  -  IHxRegisterSession::CreateTransaction() returned 8004036e.

IHxRegisterSession::CreateTransaction() returned 8004036e.
BeginTransaction() ERROR: Attempt failed because another transaction was running.
Trying to Rollback current transaction ({2318682E-D486-40D6-8530-80CEEA1A16B5})
IHxRegisterSession::ContinueTransaction() returned 80004005.
BeginTransaction() ERROR: Could not restart current transaction.
BeginTransaction() ERROR: Could not Rollback current transaction. HelpFile registration will abort.
Registration session {2318682E-D486-40D6-8530-80CEEA1A16B5} was *not* created.
Action ended 14:30:54: InstallFinalize. Return value 3.

ERROR: FAILED TO REGISTER PLUGIN. HRESULT: 0x80070005

MSI (s) (08:6C) [12:32:40:502]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI4D4.tmp, Entrypoint: CAInstallSppPlugin
CAInstallPlugin.x86:  OMSICA : Initializing CustomAction CAInstallPlugin.x86
CAInstallPlugin.x86:  Registering PlugIn 'C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\OSPPOBJS.DLL' 'C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\osppobjs-spp-plugin-manifest-signed.xrm-ms'
CAInstallPlugin.x86:  Error: Failed to register plugin. HResult: 0x80070005.
CAInstallPlugin.x86: 
MSI (s) (08:58) [12:32:42:830]: User policy value 'DisableRollback' is 0
MSI (s) (08:58) [12:32:42:830]: Machine policy value 'DisableRollback' is 0
Action ended 12:32:42: InstallExecute. Return value 3.

Policy set on the problem machine (local or through GPO) that is misconfigured.

Opened Gpedit.MSC
Computer configuration/Windows Settings/Security Settings/local policies/user rights assignment
Ensure that everyone has rights on Bypass traverse Checking. (Everyone would be listed by default)

http://support.microsoft.com/kb/823659

ERROR  - Error 0x80070005: CAQuietExec Failed

CAQuietExec:  "wevtutil.exe" im "C:\Program Files\Microsoft Office\Office14\BCSEvents.man"
CAQuietExec:  The publishers and channels are installed successfully. However, we can't enable one or more publishers and channels. Access is denied.
CAQuietExec:  Error 0x80070005: Command line returned an error.
CAQuietExec:  Error 0x80070005: CAQuietExec Failed
CustomAction RegisterEventManifest returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (88:04) [15:15:03:285]: User policy value 'DisableRollback' is 0
MSI (s) (88:04) [15:15:03:285]: Machine policy value 'DisableRollback' is 0
Action ended 15:15:03: InstallExecute. Return value 3.

Possible solution(s)

This issue can occur because permissions have been incorrectly set on the folder: C:\Windows\System32\winevt\Logs
Grant the trusted installer full rights, and system full rights to this folder and reattempt the install.

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.

When automating the uninstallation of Office 2003, we can call msiexec to perform the work from a command line.

Example syntax:
msiexec /x {GUID} /qb

*note*
You could use /qb for an automated uninstall with a progress bar, or use /qn for a totally silent uninstall.
You could also use a /norestart switch to prevent a reboot of the machine after installation.
The GUID for the Office 2003 products is different depending on which version of Office 2003 you are using.

To find the GUID for Office 2003 products look at the following registry key:

x86 OS
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}

x64 OS
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}

The GUID for Office 2003 will be similar or equal to {90110409-6000-11D3-8CFE-0150048383C9}
The GUID may be slightly different then what I have listed here. Verify you found the correct GUID by verifying the product under the “Displayname” key listed in the GUID.

Here is a screenshot of this registry key on my machine

So on my machine I can automate the silent uninstallation of Office 2003 via the following command line:

Msiexec /x {90110409-6000-11D3-8CFE-0150048383C9} /qn /norestart

When automating the removal of Office 2007, we need to call setup.exe to perform the work.
Because Office 2007 is a multi-msi based product we cannot use msiexec for the installation, nor the uninstallation of Office 2007.

http://technet.microsoft.com/en-us/library/cc982159(office.12).aspx#BKMK_UninstallProd

To run Setup.exe to remove a specified Office product from the user’s computer, use the /uninstall command-line option, which uses the following syntax:

/uninstall [ProductID]

where:

[ProductID] is the value for the product that you want to modify. Look up the value of [ProductID] in the Setup.xml file for the product.

The following example shows how to use the /uninstall command to remove an Office Professional Plus 2007 installation. Office12 is the root of the network installation point for ProPlus:

\\server\share\Office12\setup.exe /uninstall ProPlus

In enterprise deployments, we recommend that you run a silent uninstall. To run a silent uninstallation of a Office 2007 product that requires no user interaction, you must modify the Config.xml file for the product that you want to uninstall and set the Display element's Level attribute to "none" (Display Level="none"), and then save the Config.xml file as UninstallConfig.xml. You may also want to prevent the reboot of the machine after the uninstallation. We can also set this in a custom Config.xml.

Example Uninstallconfig.xml:

<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="no" /> 
<Setting Id="SETUP_REBOOT" Value="NEVER" />
</Configuration>

To then uninstall Microsoft Office Professional Plus 2007 after you modify the Config.xml to set silent options, use the following command where \\server\share\Office12 is the path of the Office 2007 Professional Plus source files, and <pathtoUninstallConfig.xml> is the location of your modified Config.xml file for Office Professional Plus:

\\server\share\Office12\setup.exe /uninstall ProPlus /config <pathtoUninstallconfig.xml>\UninstallConfig.xml