We also have the same set of catalogs for 2008.
They also show the same behaviour.
In total they include the same number of bulletins, but the obsolete information do also not match.
I think it is same, but just to clear
Is the Payload Source Location same for both the catalogs ?
yes it is the same, a single payload-source directory is used here.
what is 'catalog via PXE' ? is that the payload url?
you have run the CUJ at the same time for both catalogs?
how are you updating the shavlik xml files for both catalogs? do you create a new deploy object and manually point the catalogs to the new depot file, or are you directly overwriting the depot file on the file server w/ the new xmls ?
the catalog via PXE means that we use the PXE stores we have in each region to mount the patches from there. The correct pxestore is chosen by some TARGET properties.
Hi CUJ have been run one after the other, with max. 1 minute gap between.
The shavlik XML's are the same, as they only exist once in the depot. We updated them beforehand using a script that replaces them on the FS. After that we ran the both CUJ job, without touching the XMLs again.
I also tried the same now when manually adding the shavlik xmls to the depot beforehand and linking them to the two catalogs.
Unfortunately after running another CUJ i still get the same behaviour.
Try this :
Probably some kind of caching is happening somewhere.
- Cleanup the NSH helper path , this will be shooting in the dark, but worth a try Is it the same for both the catalogs ?
- Is the Payload Repository path the same for both the catalogs ?
- Also, when you run CUJ job, can you grab entries from appserver for each of the runs ?
We have the same issue. We have several environments and all Windows Catalogs have different superseded informations for different Bulletins. So a ticket were opened at the end of last year and we were told from support that this is a bug and a fix will be in 8.1 SP4 for that. We will see if it is fixed when we do the upgrade next week
Interesting, i have opened a ticket with support about this in parallel, but they haven't told me that.
Also looking in the patching related fixes of SP4, i can't find anything that would explain this.
From your ticket with support, do you have a defect number that you could give me ?
I looked into ticket, they didn`t provide a defect number - strange. We have only conversation notes from August till November for this (including something like "The defect will be addressed" and later on "The fix will be delivered in SP4")....
Iss # ?
I see QM001729327
I´m sorry, to mutch entries. Your are right there is a defect number provided at 30.8.2011 but it was QM001709353 in the ticket. Just see that this (QM001709353) should be fixed in 8.2