Scenario
I had a client with a mixed 32-bit/64-bit install base of Office Pro Plus (2010 & 2013). At one point they decided to start rolling out the 64-bit versions, but then switched back to 32-bit after having issues with some 3rd party plugins. They also had a number of systems with Visio & Project installed.
All of this was done before their systems were being managed by Configuration Manager 2012 R2.
It’s important to note that you cannot mix different architecture bits (32-bit/64-bit) of Office products on the same system. Therefore, when using ConfigMgr to manage the installations and upgrades of Office products, ConfigMgr has to know which bit architecture is installed on the system.
The following outlines the use of ConfigMgr’s Global Conditions feature to detect the bit architecture of Office Pro Plus (2010 & 2013), and use that detection in the Deployment Types of a ConfigMgr Application.
This means you can create one ConfigMgr Application that will install an Office product with the correct bit architecture. If you use the Office Customization Tool to force the uninstall of previous versions, you can use the same ConfigMgr Application to perform upgrades.
Office Display Names & Product IDs (GUIDs)
There are lots of ways to discover the bit architecture of Office products, but I’ve found the best way is with the Display Name and the Office Product ID (aka GUID) stored in the Uninstall key of the Windows registry. You can also view the Display Names and Product IDs in ConfigMgr’s Resource Explorer.
The Display Names for each architecture are the same, but the Product IDs are different. In the registry, the Product IDs are Keys and the Display Names are Key Values.
32-bit Product ID Keys are located here:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall
64-bit Product ID Keys are located here:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Office 2010
Office 2010 (32-bit) – Volume Lic
Display Name Product ID
------------ ----------
Microsoft Office Professional Plus 2010 {90140000-0011-0000-0000-0000000FF1CE}
Microsoft Office Visio 2010 {90140000-0057-0000-0000-0000000FF1CE}
Microsoft Office Project Professional 2010 {90140000-003B-0000-0000-0000000FF1CE}
Office 2010 (64-bit) – Volume Lic
Display Name Product ID
------------ ----------
Microsoft Office Professional Plus 2010 {90140000-0011-0000-1000-0000000FF1CE}
Microsoft Office Visio 2010 {90140000-0057-0000-1000-0000000FF1CE}
Microsoft Office Project Professional 2010 {90140000-003B-0000-1000-0000000FF1CE}
Office 2013
Office 2013 (32-bit) – Volume Lic
Display Name Product ID
------------ ----------
Microsoft Office Professional Plus 2013 {90150000-0011-0000-0000-0000000FF1CE}
Microsoft Visio Professional 2013 {90150000-0051-0000-0000-0000000FF1CE}
Microsoft Project Professional 2013 {90150000-003B-0000-0000-0000000FF1CE}
Office 2013 (64-bit) – Volume Lic
Display Name Product ID
------------ ----------
Microsoft Office Professional Plus 2013 {90150000-0011-0000-1000-0000000FF1CE}
Microsoft Visio Professional 2013 {90150000-0051-0000-1000-0000000FF1CE}
Microsoft Project Professional 2013 {90150000-003B-0000-1000-0000000FF1CE}
ConfigMgr Global Conditions
After documenting all of the Office products and their respective IDs, you can build some Global Conditions within ConfigMgr, and use them as requirements in a deployment.
For example, if the 64-bit product ID for Office Pro Plus 2013 exists in the registry, then the 64-bit version of Visio Pro 2013 would be installed, not the 32-bit version.
Likewise, if the 32-bit product ID for Office Pro Plus 2010 exists in the registry, then the 32-bit version of Office 2013 Pro Plus would be used to upgrade Office, not the 64-bit version.
Creating a Global Condition
Software Library > Application Management > Global Conditions > Create Global Condition
- Name: Office Pro Plus 2013 64-bit
- Description: Detects an installation of Office Pro Plus 2013 64-bit
- Device Type: Windows
- Condition Type: Setting
- Setting Type: Registry Value
- Data Type: String
- Hive Name: HKEY_LOCAL_MACHINE
- Key Name: <See Below>
- Value Name: DisplayName
Key Name (Registry Path):
SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90150000-0011-0000-1000-0000000FF1CE}
Repeat this process for the other versions of Office Pro Plus 2010 & 2013. When you’re done, you should have 4 Global Conditions that can detect the registry keys for Office Pro Plus 2010 and 2013.
Important Note: Once a Global Condition is used in a deployment, it cannot be edited or deleted. You have to remove it from all deployments including any saved revisions.
Using the Global Conditions in a Deployment
Example Scenario: Installing Visio Professional 2013
You created separate folders for the 32-bit & 64-bit Visio installation files, and you used the Office Customization Tool to configure the Visio installations to remove old versions of Visio, if present.
Installation Rules
- If Office Pro Plus (2010 or 2013) 32-bit is installed, then install Visio Pro 32-bit.
- If Office Pro Plus (2010 or 2013) 64-bit is installed, then install Visio Pro 64-bit.
- If Office Pro Plus (2010 or 2013) is not installed, the Visio installation will fail. Having Office Pro Plus installed is a requirement.
ConfigMgr Application
- You create an Application in ConfigMgr called Visio Pro 2013 with 4 Deployment Types:
- Visio Pro 2013 with Office Pro Plus 2010 32-bit
- Visio Pro 2013 with Office Pro Plus 2010 64-bit
- Visio Pro 2013 with Office Pro Plus 2013 32-bit
- Visio Pro 2013 with Office Pro Plus 2013 64-bit
Deployment Type Requirements
- Each of the deployment types have Requirements that include one of the Global Conditions to detect an installation of Office Pro Plus.
- Deployment Types have a numbered Priority. If all of the requirements are met for a deployment type, then that deployment type will be executed, and the remaining deployment types will be ignored.
- Here’s an example requirement for detecting Office Pro Plus 2013 64-bit:
- Deployment Type (Properties) > Requirements (tab) > Add
- Category: Custom
- Condition: Office Pro Plus 2013 64-bit
- Rule Type: Value
- Operator: Equals
- Value: Microsoft Office Professional Plus 2013
- Deployment Type (Properties) > Requirements (tab) > Add
Note: The Value field is passed to the Condition you just chose in the drop-down, and that Condition is one of the Global Conditions you created earlier. Therefore, the Value field needs to match exactly with the data in the DisplayName value in the registry, which is the Office Pro Plus Display Name.
Value = Microsoft Office Professional Plus 2013
Condition Name = Office Pro Plus 2013 64-bit
Condition Reg Key = {90150000-0011-0000-1000-0000000FF1CE}
Condition Reg Value Name = DisplayName
Repeat the same process for the other deployment types.
Once you’re done, distribute the content, and deploy the application to a test collection.
Conclusion
The flexibility of using Global Conditions for detection along with having multiple Deployment Types within a single Application is pretty slick.
To take it a step further, if you deploy an Application like this to a User or Device Collection that is associated with an AD Security Group, the Help Desk Team can deploy or upgrade Office products without having to touch the ConfigMgr console. They just drop the employee’s user or computer account into the security group.
You can also set it up so that the User sees the Application in the Application Catalog or the Software Center, and they can install it when they have time.