Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Help needed with detection rule

Created: 14 Mar 2013 • Updated: 19 Mar 2013 | 7 comments
This issue has been solved. See solution.

Hi,
 

We are upgrading the version of MS Word on some of our machines from 2003 to 2007.  I have created a SMP and all is well.  We are having an issue as we would like the job to run a computer startup but obviously will run each reboot.  I have tried creating a detection rule but when a targeted workstation gets the policy and runs the job it just sits with the 'running' status and eventually times out.  I dont fully understand the detection rules but mine looks for winword.exe version x within program files.

Would this be the correct method or could someone please advise on how we could make this work?

Thanks

Comments 7 CommentsJump to latest comment

andykn101's picture

Look in the Altiris log of a PC when it runs the Detection rule.

You could use an "MSI Product Code" Standard Rule to detect.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

kamino's picture

I have tried the MSI product code but dont think this is working as the install will run each reboot.

does the attached look right?

 

Capture.JPG
andykn101's picture

Yes, but I always select the Per user option.

Make sure the Detection rule is selected in the Policy.

Check that the registry of an installed PC contains that MSI code.

Check the log of an affected PC when the Policy runs the detection rule.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

kamino's picture

OK I have now selected the per user option.

How do I check if it is selected within the policy.  I just assumed that as it was part of the sotware resource it would filter through.  This is maybe what I am missing

 

andykn101's picture

Select the Software Release within the policy and there should be a tick box on the right saying "Perform software compliance check using:"

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

SOLUTION
kamino's picture

I have discovered what I have been doing wrong.  I have been using tasks as opposed to software in the MSD.

All working now, thanks.

andykn101's picture

Yes, Tasks don't use the detection rule. I almost never use Tasks to deliver software. You can always apply a Policy and then use a Task to do an Update Config if you want to deliver the software quickly to a few computers.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.