Deploy Condition



  • Jason Hanks

    Hi Leonidas,

    This is possible with a little bit of setup using PDQ Inventory and a custom file scanner.  You'd have to create the file scanner to identify the machines based on which folder Office is installed in: Program Files (x86) for 32 bit and Program Files for 64 bit.  Once you have identified those machines you can plan your deployment around those collections.

    Comment actions Permalink
  • Brigg Angus

    And to add to what Jason said, you can probably gather there's not really an elegant way to filter this using PDQ Inventory in order to deploy using PDQ Deploy since the installation directory can differ from version (x86 Office versions can be in both %systemdrive%\Program Files\ and %systemdrive%\Program Files (x86)\), as well as the method of installation (e.g. click-to-run vs MSI, which also installs in different directories). In standalone Deploy, there's even less options with the deployment conditions. In other words, it isn't a walk in the park unless your Office environment is homogeneous, or very nearly so.

    However, there are options for discovering this information IF your Office installation contains Outlook (without Outlook installed, there is little hope, much despair). For instance, this article indicates the location of the registry key Bitness, that should provide the edition information for Office installations:

    I have Office 365 installed, and the key information was located here, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\ClickToRun\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\Office\15.0\Outlook

    So if you know which version of Office is installed, you could write up a quick script to search for the registry key Bitness in the locations for the versions of Windows you have then deploy the x86 version where Bitness = x86.

    Comment actions Permalink

Please sign in to leave a comment.