Client Automation Standard Practitioners Forum
cancel

Controlling Patch Manager probing

Highlighted
Kevin Parry_1
Occasional Contributor

Controlling Patch Manager probing

Is there a method (maybe a ZSTOP in the PATCHMGR Domain) to stop the discovery probe from being resolved\run, so that it only runs when you issue a radskman (with dname=patch) and when you use the RSM. As I do not want to allow probing to occur during a normal radskman notify request.

Kevin
4 REPLIES
Jake Burman
Collector

Re: Controlling Patch Manager probing

Kevin,

Here are two pretty easy ways to do it;

ZSTOP method, add this ZSTOP to your Discover Patch ZSERVICE.

\(POS('PATCH',UPPER(EDMGETV(ZMASTER,ZDOMNAME))) =1 | POS('PATCHMGR',EDMGETV(PATCHOBJ,FDCI))>0)

or

CATGROUP method, set the CATGROUP field in the Discover Patch ZSERVICE to some description like Patch, and add the following to your radskman command line,
catexp=catgroup:Patch. The raskman will only process services with a matching catgroup field.

hope this helps,

_jake Burman
Pepperweed Consulting

Re: Controlling Patch Manager probing

Kevin,

If you are using Policy Manager, upgrade the PM.TKD to a new version (and check the PM.CFG) as this is built in by default.
The only other straightforward option is ZSTOP based on DNAME.

Regards,

Kelvin
Kevin Parry_1
Occasional Contributor

Re: Controlling Patch Manager probing

Thanks for the options guys, I go with CATEXP
Kevin Parry_1
Occasional Contributor

Re: Controlling Patch Manager probing

Used the CATEXP option
//Add this to "OnDomLoad" event