Quantcast
Channel: Symantec Connect - Endpoint Management
Viewing all articles
Browse latest Browse all 7217

RegEx, reporting and software minimum versions

$
0
0
I need a solution

Hi,

We have a couple of issues which we are trying to resolve in relation to reporting, RegEx and establishing a minimum version of a particular software product.

1. We logged a support call with Symantec regarding RegEx in reporting because we wanted to be able to generate a report which only had the computers TEST100 through TEST115. This is "very" easy to do with the following:

TEST1(0[0-9]|1[0-5])

However it appears that RegEx is not fully implemented in reporting. For instance I currently rely on the following:

TEST1[0-1][0-9]

And this only works because the other machines that it would include don't exist right now.

We also found when building filters you can use alternation but you cannot use groups or repeating characters, '()' and '{}' respectively.

So I was looking for some advice on the best, or preferrably easiest way of achieving this?

2. With the recent announcement of vulnerability in Flash we have pushed out, via policy both the ActiveX and NPAPI packages of version 18.0.0.203. This is being installed on to all machines that have a previous version detected and then once they reach that version the policy is removed. However what happens if the user then installs 18.0.0.204? Apparently the policy re-activates and the best you can hope for then is that the package fails to install. I find it hard to believe that something that at first glance would be so simple and yet so difficult to achieve.

In essence if you have version:

<18.0.0.203 - Install
>=18.0.0.203 - Disable policy

But since you cannot use >,<,= etc in filters as far as I can see, and not all RegEx operators are supported then this seems equally tricky as the first problem.

Any ideas would be most welcome.

Howard


Viewing all articles
Browse latest Browse all 7217

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>