Hello Hendardi,

Can you explain a bit more? Are you missing a bulletin? This is often caused by the AUP or maintenance of Patch Management being expired.



Cheers,



Jim

Hello,

Sorry for late response. I have missing a bulletin and if I was checked on AUP, it still until March'09.



Could you help me what is the root caused ?



Thanks & rgds,

Hendardi

What bulletin is it? Can you check your pmimport.cab version (one easy way is to look on the download history of the pmimport version).

Hello Jim,

In here bulletin-list that didn't found in our NS and currently we was used,

MS Patch Mgmt Import v6.2.1226.1

MS Patch Mgmt Import - Supplementary v6.2.1209.2



Are those still using the old version ?



Thanks & rgds,

Hendardi

The current pmimport version is 6.2.1236.2 . So you are several releases behind. Your AUP is current, however is your licensing exceeded?



You can try forcing the pmimport process to begin, and have the logviewer open when you do it. This should tell you immediately if there are any errors.

Our AUP is still until March'09.

How do I forcing the pmimport so that we get the latest version ?



Thanks & rgds,

hendardi

I am trying to say, the number of licenses. Is it exceeded?



You can force the pmimport by selecting the pmimport object under the patch management configuration and then right clicking on it and selecting 'start task'.

The license doesn't exceeded yet, we have 22,500 node(s) and currently we have used approx. 5100 nodes.

Regarding forcing the pmimport as you said, I have done yesterday.

Is it take time for update the latest pmimport version since "start download task" ?



Thanks & rgds,

Hendardi

When your AUP for Altiris Patch Management is expired you will receive the folowing error when forcing the pmimport:
Can not import Patch Management resources. License status is not OK or AUP has expired.
Check AKB #18397 and #26424