Detection/Applicability Rules and Multi-Point Version Numbers
When comparing version numbers with multiple decimal points, will the operators besides "=" work in detection/applicability rules? For example, I want to push out a fix for an app only if one of its dll files has a version <= 8.0.0.2. Would a comparison with "8.0.0.10" deem this a higher or lower value compared to "8.0.0.2"? For many version numbers, .10 would be higher than .2 although a straight ASCII comparison would be lower.
Also, say I wanted to deploy the fix only if the dll's version number is 8.0.0.2. Should leaving the detection rule blank but setting an applicability rule for "version = 8.0.0.2" work to fire off the software management/delivery job?
I've been trying different detection/applicability rule combos and it seems things aren't working as expected so that's why I'm asking these questions to understand what comparison operators I can and cannot properly use with version numbers that have multiple decimal points.
Comments 2 Comments • Jump to latest comment
Hello Clint,
8.0.0.2 is lower than 8.0.0.10
If you set <= 8.0.0.2 for version in Static File Expression rule for applicability. If will be detected 8.0.0.10 dll file version the installation will not be started.
My experience has been that version rules operate as Dmitri explains.
So, my Flash player rollout job has an Applicability Rule:
AND
NOT
File Version
File path: c:\...\FlashPlayerUpdateService.exe
Version type: File Version
Version must be > 11.2.202.235
So on PCs with older Flash players it's applicable but on my new image test PC with 11.4.402.265 it comes up as not applicable because it evaluates 11.4.402.265 as greater than 11.2.202.235, i.e. True.
Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.
Connect Etiquette: "Mark as Solution" posts that fix your problem, thumbs up for useful
Would you like to reply?
Login or Register to post your comment.