I believe Jason Lewis may cover this topic in one of his videos on using SCUP.

Thanks,

Justin Chalfant
Premier Field Engineer – Configuration Manager
Public Sector
Microsoft Services

Tel : (303) 846-2701
Email: [email protected]<mailto:[email protected]>
Blog: http://blogs.technet.com/b/jchalfant

If you have any feedback about my work, please let either myself or my manager 
Rusty Gray know at [email protected]<mailto:[email protected]>

From: [email protected] [mailto:[email protected]] On 
Behalf Of Jimmy Martin
Sent: Thursday, June 25, 2015 8:36 AM
To: [email protected]
Subject: RE: [mssms] semi complex scup rules

MS should add this little email to the documentation ☺ now it makes sense!


Jimmy Martin
(901) 227-8209

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Justin Chalfant
Sent: Thursday, June 25, 2015 9:25 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] semi complex scup rules

The correct logic for checking whether a x86 or x64 version of an app is 
applicable would be below.

OR
              AND
                             File '[PROGRAM_FILES]\whatever\file.exe Exist
                             File '[PROGRAM_FILES]\whatever\file.exe Version < 
1.0.0.0
AND
                             File '[PROGRAM_FILESx86]\whatever\file.exe Exist
                             File '[PROGRAM_FILESx86]\whatever\file.exe Version 
< 1.0.0.0

The top OR operator says one of the below conditions must be meet. Then we are 
ANDing the actual file rules meaning if one of the AND conditions check out the 
OR logic will be meet. The file must exists and the version must be less than 
for either the native x64 program files or x86 on a x64 OS.

Thanks,

Justin Chalfant
Premier Field Engineer – Configuration Manager
Public Sector
Microsoft Services

Tel : (303) 846-2701
Email: [email protected]<mailto:[email protected]>
Blog: http://blogs.technet.com/b/jchalfant

If you have any feedback about my work, please let either myself or my manager 
Rusty Gray know at [email protected]<mailto:[email protected]>

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Sherry Kissinger
Sent: Thursday, June 25, 2015 7:04 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] semi complex scup rules


try... I don't know if it'll be perfect/right, but it looks right to me...

OR
            File '[PROGRAM_FILES]\whatever\w.exe Version <= '3.3.3.3'
            File '[PROGRAM_FILESx86]\whatever\w.exe Version <= '3.3.3.3'

How you get the AND at the top to change to an OR is you right-click on the AND 
(which it puts in there by default when you add the 2nd rule), and select 
"Toggle Operator"



On Thursday, June 25, 2015 7:41 AM, Jimmy Martin 
<[email protected]<mailto:[email protected]>> wrote:

Hi Guys,

I am having a bit of difficulty understanding scup rules setup…  for instance 
if I want to do something like finding a file exists AND is a certain version 
or below and then accommodate x86 and x64…

In my installable rules I tried doing this but the second rule is not tried…  
how should this look? There is very little guidance on this in the product 
documentation..

And
                Whateverdir\file.exe exists
                Whateverdir\file.exe is < #.###.##
                Or
                Whateverdirx86\file.exe exists
Whateverdirx86\file.exe is < #.###.##





Jimmy Martin | Engineer | Information Technology | BMHCC - CORPORATE
Phone: (901) 227-8209 | [email protected]<mailto:[email protected]>
Opinions expressed above are not necessarily those of Baptist.

This message and any files transmitted with it may contain legally privileged, 
confidential, or proprietary information. If you are not the intended recipient 
of this message, you are not permitted to use, copy, or forward it, in whole or 
in part without the express consent of the sender. Please notify the sender of 
the error by reply email, disregard the foregoing messages, and delete it 
immediately.

P Please consider the environment before printing this email...






This message and any files transmitted with it may contain legally privileged, 
confidential, or proprietary information. If you are not the intended recipient 
of this message, you are not permitted to use, copy, or forward it, in whole or 
in part without the express consent of the sender. Please notify the sender of 
the error by reply email, disregard the foregoing messages, and delete it 
immediately.


P Please consider the environment before printing this email...



Reply via email to