This is probably wishful thinking in regard to creating a generic Microsoft Office rule but is there a way to determine the bit level (i.e. 32 or 64-bit) of the installed Office regardless of its version? We're going through a migration to Office 365 where we have multiple Office versions out there with some x86 and others x64. I would've preferred most everyone having a 32-bit version of Office (even those with 64-bit Windows) as recommended by Microsoft although some people didn't do their research and believed that an x64 Windows required a 64-bit Office and installed that version.
During the initial phase of our O365 migration, users are being allowed to keep their old version of Office along with 365. Here's where I'm trying to create an applicability rule to determine whether the version of Office installed is 32 or 64-bit so I can tie these to the appropriate software resources for managed O365 deliveries. Am I relegated to accounting for each different Office version and bit level to create this rule?
Ultimately I could just forget about all of this and use my applicability rule as-is (less any check for Office bit level) where the install would fail if there's a mismatch (e.g. trying to install O365 x86 with a 64-bit Office or vice versa). Just thought it'd be nice if I could avoid these attempted installs altogether. Heck, I'd even settle for a filter that can discern the bit level of the installed MS Office; again, regardless of its version.