Just noticed that custom inventory rules appear to be case sensitive when pulling back file versions on a Windows platform, if this the case is there anyway around that without writing multiple or statements?

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity



The only way I could think to get around it is to have OR statements in your custom inventory rule which i'm pretty sure works, this way you only need to create one rule and you can add to it as you please. ie,

FileVersionEquals(C:\Program Files\Proggy\proggy.exe, v65r) OR FileVersionEquals(C:\Program Files\Proggy\proggy.exe, v65R)
Answered 10/04/2011 by: Roonerspism
Second Degree Brown Belt

Please log in to comment