System Center 2012 Configuration Manager has many great built-in requirement rules that will help you to get the right deployment type installed for the current environment.
For most of my applications the built-in rules can get the job done, but some times we need to create our own Global Conditions, to fit the requirement rules for an application/Deployment Type.
One example could be a 3rd. party add-on for Microsoft Office, where you need to install a Deployment Type that matches the architecture of Microsoft Office.
All clients with a 32-bit OS will always have the 32-bit version of Office installed, but users with the 64-bit version of the OS, can use both the 32-bit or the 64-bit version of office installed (and most users do run 32-bit).
Then we need to create a Global Condition that will detect the architecture of Microsoft Office.
In Microsoft Office 2013, you will see the following registry key, that will help you to detect this
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Outlook
So all we need to do, is to create a new Global Condition with the following settings:
Name: Outlook Bitness
Device Type: Windows
Condition type: Setting
Setting type: Registry value
Data type: String
Hive: HKEY_LOCAL_MACHINE
Key: SOFTWARE\Microsoft\Office\15.0\Outlook
Value: Bitness
Now we can create a custom requirement rule for the application.
Enjoy
4 Comments
Pingback: How to Setup Requirment Rules for Outlook 32 bit or 64 bit - Rui Qiu's Blog
This almost does what I need, but I have multiple versions of Office in our environment. Is there a way to detect bit version that is not dependent on the Office software version?
– Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration
– Platform = x..
Also check the box “This registry value is associated with a 64bit application”
Thank You ! Very helpful and Bruce saved me a load of time digging around the registry for the query solution for “multiple versions of office” 🙂