Changes

=MS Office 2010 Single Licensesingle license=

The Office Customization Tool (OCT) is available '''only with volume licensed versions''' of Office 2010 (and the 2007 Office system). The Unfortunately the prices of volume licenses are significantly higher, than for single licenses. So the above solution can't be used if you bought several single licenses for budget reasons.

==Configconfig.xml==

To configure a silent installation (unattended installation) of an Office 2010 product that requires no user interaction, create a Configconfig.xml. You finde find an example in a the subfolder of the installation called ''product_folder_name''.WW

==Installation (Work in Progress!!!)==Then call ''setup.exe /config \\path to your modified\config.xml''

TODOIt is necessary to give a real product key in config.xml during installation. Remember, no volume license. So for single license products, every client has his own license number. You can deal in two ways with this problem: test out of WPKB (not happend yet)

===A: change Product Keyproduct key after installation===

If you delete all subkeys from [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\14.0\Registration] (for 32bit Office in a 64bit windows) or HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\Registration\ (for a 64bit Office) after install installation (and before first usage), Office ask the user for the product key after startup. At the moment, I dont know  ===B: use a way different config.xml for every client=== You can create a copy of config.xml for every client and use the the Value %COMPUTERNAME% to direct the client to separate his config.xml with  ''I don't know if there is an easy way to create the correct Product Key for himdifferent config.xml's automatically out of a template and a value.csv. If you do, please let me know - I did it manually.'' <source lang="xml"><package id="office2010" name="Microsoft Office 2010" revision="1" reboot="false" priority="10"> <check type="uninstall" condition="exists" path="Microsoft Office Home and Business 2010" /> <commands> <command type="install" cmd='%comspec% /C start "Installer" /WAIT "%SOFTWARE%\O2010\x86\setup.exe" /config "%SOFTWARE%\O2010\x86\%COMPUTERNAME%_config.xml"' > <exit code="1641" /> <exit code="3010" /> </command> </commands></package></source>

If you have an Windows Server with an AD, it is possible to use Group Policy to enforce some Office 2010 settings. You need the [http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=18968 Office 2010 Administrative Template files] and find an a comprehensive guide in this [http://www.microsoft.com/downloads/de-de/details.aspx?FamilyID=66a6848c-6c28-4b61-9c12-a8cad4b380a4 document] (change language before download if needed). --[[User:Konus|Konus]] 15:10, 1 February 2012 (CET)