Client Automation Standard Practitioners Forum
cancel

RPM 3.0 - after migrating, DISCOVER_PATCHES isn't processed

Highlighted
Marko_
Esteemed Contributor

RPM 3.0 - after migrating, DISCOVER_PATCHES isn't processed

Hello all.

After an upgrade to RPM 3.0 env, the PATCHMGR domain automatically imported during the migration changed something and now my PATCHMGR.ZSERVICE.DISCOVER_PATCHES isn't processed on the clients anymore.

I have run an acquisition, got the (latest?) Patch agent v2.2 (version 3 is NOT there to be downloaded!) and now when i connect with dname=PATCH, patches are assigned but not installed, and the DISCOVER PATCHES application is in catalogue but not resolved. Nothing happens, the service is skipped, the agent isn't updated (there is an old v1.2.3 agent still on the client) and the patches assigned are not installed. All of them are assigned through the policy and are in the client catalogue. Why is this happening?

Any help would be appreciated!
4 REPLIES
Biju V George!
Honored Contributor

Re: RPM 3.0 - after migrating, DISCOVER_PATCHES isn't processed

Hi Marko,


First is you need to upgrade Patch Manager to the latest one. If it's getting skipped check your radish logs in RCS.

Also try to remove the discover Patch from policy & reassign it.

Biju
Roy O Gatewood_
Honored Contributor

Re: RPM 3.0 - after migrating, DISCOVER_PATCHES isn't processed

Sounds like you need the updated nvdkit for your clients which is in the pre-requisite software.
Take a look at page 11 of the Migration document on the CD.
Thompson, Jim
Honored Contributor

Re: RPM 3.0 - after migrating, DISCOVER_PATCHES isn't processed

Roy is right.

I've seen this before a)when the client is still using the old NVDKIT with the new agent, and b) when the client is using the new NVKDIT with the old agent.

If you look closely at your connect.log from the Patch connect, you should be able to find some TCL errors in the Discover Patch section...
"Well...it depends..."
Marko_
Esteemed Contributor

Re: RPM 3.0 - after migrating, DISCOVER_PATCHES isn't processed

Hello all.

The problem was the PATCHMGR.ZSERVICE._BASE_INSTANCE_ ZSTOP001 expression.

I have been using the old-style, not supported by RPM3.0 anymore expression:

WORDPOS(EDMGETV(ZMASTER,ZDOMNAME),'PATCH PATCHOBJ PATCHMGR')=0

The HP support told me i should use the expression:

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

I'm a bit upset they didn't mention this in the RPM 3.0 migration guide!!!

Anyway, the DISCOVER_PATCH service is now resolved on the client side.

Thanks to all who helped.
//Add this to "OnDomLoad" event