Custom Inventory for Managed Installs
I am in the habit of always creating a custom inventory rule (typically on the executable) for Managed Installs.
This prevents an MI from re-targeting a machine that has the application, but has been updated to a later version.
Anyway, we are running in a mixed XP and Win 7 64 environment.
Typically, I use "FileExists(C:\Program Files\Example\Example.exe) to validate the app is installed.
What I need is to be able to check both "FileExists(C:\Program Files\Example\Example.exe) OR (C:\Program Files(x86)\Example\Example.exe) to validate both XP and Win 7 64 in the x86 dir.
Suggestions?
This prevents an MI from re-targeting a machine that has the application, but has been updated to a later version.
Anyway, we are running in a mixed XP and Win 7 64 environment.
Typically, I use "FileExists(C:\Program Files\Example\Example.exe) to validate the app is installed.
What I need is to be able to check both "FileExists(C:\Program Files\Example\Example.exe) OR (C:\Program Files
Suggestions?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
mlathrop
13 years ago
OK, read the FAQ jack [:)] I answered my own question by reading the Admin Guide, ha! Yes, OR statements work
FileExists(C:\Program Files (x86)\Microsoft Office\Office14\visio.exe) OR FileExists(C:\Program Files\Microsoft Office\Office14\visio.exe)
searches both locations for 32 bit and 64 bit OS's
FileExists(C:\Program Files (x86)\Microsoft Office\Office14\visio.exe) OR FileExists(C:\Program Files\Microsoft Office\Office14\visio.exe)
searches both locations for 32 bit and 64 bit OS's
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.