Another blogpost about KMS again. Before this 2 other blogposts where available, just have a look at that one also:
Key Management Services (KMS) explained
Using KMS Client Setup Keys during deployment
When setting up KMS a Windows Server KMS key can be installed at first try. When using a Office (2010) key afterwards an error message is displayed.
Error: 0xC004F050 The software licensing service reported that the product key is invalid
This because the Microsoft Office 2010 KMS Host License Pack must be installed first. It can be downloaded at this location: Download Center. During installation the Office 2010 KMS key can be imported succesfully.
More information can be found on Microsoft TechNet also.
Office 2010 will be installed with Setup.exe by default. It's however possible to use the Office Customization Tool (OCT) to decide which functionality must be used during install. With the created MSP file afterwards it's possible to do a unattend install with the usage of ConfigMgr. How to do that is explained in this blogpost.
First create a source location for the Office 2010 files. Run the Setup.exe with the /Admin parameter then. Choose to create a new Setup customization file.
There is the choice to choose between "Office Open XML formats" or "OpenDocument formats". In my case I choose to keep the current settings.
There are a lot of settings which can be configured in the Office Customization Tool. The most used are "Installation location and organization name" (and a few other settings).
Then select (in my case) "Licensing and user interface". I'm using a KMS client key here. For unattend and silent install use [Display level: None] and Suppress modal. Uncheck "Completion notice" here.
There is the choice to remove older Office versions before installing Office 2010.
Select which programs must be installed during Office 2010 setup. That's all for now for having a unattend Office 2010 install.
Choose "Save as" for creating a MSP file. This MSP must be placed in the Office 2010 source location then. Choose the Updates folder for that. All MSP files placed in the Updates folder will be automatically installed/used during install.
Then create a new package in ConfigMgr, with a Setup.exe command line. There are no additional installation switches needed. It's however possible to use an config.xml file for additional configuration. More about that on this TechNet post: http://technet.microsoft.com/en-us/library/cc179195.aspx
Hope things are clear now for Office 2010 deployment.
