I recently came across an issue where a MEMCM) Global condition was detecting the Office bitness (architecture), but only to one specific version(example below). This lead to a requirement issue where the computer was running another version of Office that wasn’t covered by the global condition. With that said, we still needed a requirement only for the architecture of Office, while the version was not that important for now.
I’ve uploaded a new script to Technet Gallery that returns the Office Bitness no matter what version is installed (from Office XP to the latest).
In this post, I’ll describe how to use the script with a MEMCM global condition as a requirement for an application.
MEMCM Global Condition Office Bitness Requirement
- Download the Office Bitness detection script from Technet Gallery
The script is looking at the Bitness registry key of Outlook.
The script will return the value of Bitness. So either x64, x86 or blank if not detected.
To be able to use the script within a MEMCM Global Condition, it must only return this value. If there are additional verbose, like write-host, the Global condition will not work.
MEMCM Global Condition Office Bitness
- Browse to Software Library/Application Management/Global Condition and click Create
- Name: Office Bitness
- Device Type: Windows
- Condition: Settings
- Setting type: Script
- Data type: String
- Click add Script
- Open up the downloaded PowerShell script
- Click Ok. The global condition is ready to be used
Add Global condition to an application
- Edit a Deployment type of application that has the requirement for Office Bitness. On the Requirements tab, select Add.
- Select category Custom, and then select the Office Bitness global condition created earlier.
- As explained earlier, the script returns x64, x86 or nothing.
- Set the equal value you wish to have as a requirement.
That’s it! Now the application will evaluate the Office architecture no matter the version of Office to match the requirement!
For more information on Global conditions, see Microsoft docs.
Hope this help 🙂
Share this Post
Contributor of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM consultant, working in the industry for more than 10 years. He developed a strong knowledge of SCCM and MDT to build automated OS deployment solution for clients, managed large and complexe environment, including Point of Sale (POS) related projects.