Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Remediation running even if compliant

Updated: 23 Aug 2010 | 5 comments
Icegod's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

I configured a managed software delivery task with a detection rule to detect if google earth 5 is already installed.
Remediation is set up so that if the software isn't detected it will run the install command.

Now my problem is that no matter if google earth 5 is installed or not, it will run the install command.
The detection rule seems to work properly as it reports "Detected" in the Symantec Management Agent window.

I set my managed software delivery as follows:

New managed software delivery
Then clicked Add -> software resource
Set command line and package to the correct setting for installing google earth 5
Checked that it was using the correct detection rule
Set up the resource it applies to
Set up a schedule

Comments

mclemson's picture
21
Jul
2010
2 Votes +2
Login to vote

What is your detection rule?

What is your detection rule, exactly?  Did it ever work?

Mike Clemson, Senior Systems Engineer
Intuitive Technology Group -- Symantec Platinum Partner

jharings's picture
21
Jul
2010
1 Vote +1
Login to vote

Agreed (check your detection)

When using the smart rule (for example) for product or file version, you could only specify a major version. If you use a standard rule, you can get more granular. A word of caution in that a change to a detection rule doesn't happen automatically. Resource membership updates have to run on the server, and then get pulled down by a client before they apply.

This cycle can make it a bit frustrating to test the proper application of detection rules, especially if you have an agressive remediation schedule.

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

Icegod's picture
21
Jul
2010
0 Votes 0
Login to vote

The detection rule seems to be applied properly. It detects that Google is installed, but remediation rubs regardless of the outcome of the detection rule. I've added a screenshot below of the way my detection rule is set up and what I see on agent at the client.
This particular PC already had Google installed.
PC is running windows 7

If you need anymore info, just let me knowDetection ruleAgent result

mclemson's picture
22
Jul
2010
4 Votes +4
Login to vote

This is a known issue

This is a known issue -- switch the command type from 'custom' to 'install'

https://kb.altiris.com/article.asp?article=53075&p=1

Does this resolve the issue?

Mike Clemson, Senior Systems Engineer
Intuitive Technology Group -- Symantec Platinum Partner

Icegod's picture
22
Jul
2010
0 Votes 0
Login to vote

Thanks. Will definitly switch the command type to install then.