MECM Query – Microsoft Office 2016
For delivering Microsoft Office ProPlus Click To Run, we first need to identify the counts of installed software. In this case, we are looking at Microsoft Office 2016 Professional.
This will return all objects from the Limiting Collection for each "bitness", being 32 or 64 bit.
By sorting in this way, we can do a straight up targeted deployment of the appropriate Click To Run Installer to replace each product.
And yes, you can use global conditions for installer. We just do it this way for a quick and dirty like for like Migration Deployment.
Microsoft Office Professional 2016 - 32 bit
select distinct SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like "%Microsoft Office Professional plus 2016%"
Microsoft Office Professional 2016 - 64 bit
select distinct SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName like "%Microsoft Office Professional Plus 2016%"
So create a collection for both "bitness-es".
Going through older environments, we have built these out to include versions down to Office 2000.
But as I said, it's a quick and dirty way of sorting clients.
To engage DeployTech to drive your Modern Management adoption, please email email@example.com or call +61 499 333 973