Microsoft has released a document which describes and illustrates the client deployment methods for Microsoft Office 2010. Deployment options include network share, Group Policy startup scripts, managed deployment, and virtualization.
The deployment architecture for Microsoft Office 2010 is primarily the same as the 2007 Microsoft Office system. One difference is that Office 2010 now requires Office Volume Activation technologies, such as Key Management Service (KMS), Multiple Activation Key (MAK), MAK Proxy, or a combination of these, for participation in any volume licensing programs.
In addition, Office 2010 introduces native 64-bit versions of Office products.
Several options are available to customize the installation of Office 2010 before you decide how to deploy it.
The Office Customization Tool (OCT) is the primary means to customize the installation of Office 2010 applications.
The Config.xml file can be used to configure some installation tasks.Group Policy settings can be used to define and maintain an Office configuration on users’ computers.
The Group Policy settings are enforced and can be used to create highly managed or lightly managed configurations.