RE: Query isn't working, stumped

New Boundary Support — Wed, 18 Nov 2009 10:14:12 GMT

I did some testing with your rule, and found that you just need to rearrange your AND and OR statements to look like this. Here is a pseudo code version of how it should look.

(OS = 2000) Or (OS = 2003) AND (File path exists) AND (File path 1 does not exist) AND (File path 2 does not exist)

I went ahead and created a rule that should work for you from within the configuration groups. If this doesn't work correctly, try building the rule step by step from these examples.

((((OSVersion = OS.Version.Win2000) OR (OSVersion = OS.Version.WinServer2003)) AND (EXISTS <File> "C:\Program Files\Symantec\Backup Exec System Recovery\Agent\VProSvc.exe")) AND (NOT EXISTS <Folder> "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG")) AND (NOT EXISTS <Folder> "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\CONFIG")

New Boundary Support

Support@newboundary.com

612-379-1851

Query isn't working, stumped

VA_1 — Tue, 17 Nov 2009 21:38:33 GMT

I have this query that is looking for the existence of a file, and missing .NET 2.0. I have it split between Win2k and 2003 - doesn't seem to be working. Is there a variable I can use for system drive? Will the regular Windows variables work?

Here's the query:

(OSVersion = OS.Version.WinServer2003 AND EXISTS "C:\Program Files\Symantec\Backup Exec System Recovery\Agent\VProSvc.exe" AND NOT EXISTS "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG") OR
(OSVersion = OS.Version.WinServer2000 AND EXISTS "C:\Program Files\Symantec\Backup Exec System Recovery\Agent\VProSvc.exe" AND NOT EXISTS "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\CONFIG")

Thanks

New Boundary Support Forum / Prism Deploy & Prism Pack / Configuration Group Rulesets / Query isn't working, stumped / Latest Posts

RE: Query isn't working, stumped

Query isn't working, stumped