Re: How to change existing published update from metadata from to full content

[quackpatch]

I'm trying to switch a few updates from "metadata only" to "full content" after they've already been published.  Apologies in advance, I'm sure I've seen this posted somewhere but for the life of me cannot find any information on it 

I appreciate I could wait for the next release of the update(s) but who knows when that could be. I've tried the following method and had mixed results:

- deleted the update using the Modify Published Updates Wizard (Advanced tab)
- run a full SCCM Software Updates sync, once complete, confirm update(s) expired
- start a sync from PatchMyPC Publisher # this will trigger sccm software updates sync
- once complete, confirm update(s) published with full content

I'm obviously missing something as the updates return as metadata only 

[Justin Chalfant (Patch My PC)]

If you right-click the product(s), are they using metadata or full-content in the publishing service?

[quackpatch]

Yes, that was the first step which I noticed after changing then running a sync did not reflect in SCCM; hence all the deleting\re-syncs.

[Justin Chalfant (Patch My PC)]

If you can shoot us an email, we can do a remote session to check things out.

[quackpatch]

No problem, will do.

In the meantime, another troubleshooting step I tried was to use the SCCM Content menu to publish the content, but that failed as per SMS_ISVUPDATES_SYNCAGENT.log below:

Code Select Expand

[34, PID:8812][02/06/2019 16:26:21] :PollingWorkMonitor: There are 1 jobs that are pending in the jobs table. 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[34, PID:8812][02/06/2019 16:26:21] :PollingWorkMonitor: Starting job 72057594037927937 for subject c8d329d4-141d-47c4-9fb7-0d2855317ed4. 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[34, PID:8812][02/06/2019 16:26:21] :Creating a new SyncUpdate work item for update c8d329d4-141d-47c4-9fb7-0d2855317ed4, jobid is 72057594037927937 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[34, PID:8812][02/06/2019 16:26:21] :Launcher : About to start work item: SyncUpdate. 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[27, PID:8812][02/06/2019 16:26:21] :SyncUpdate: c8d329d4-141d-47c4-9fb7-0d2855317ed4 - No synchronization record for update with id c8d329d4-141d-47c4-9fb7-0d2855317ed4 was found, only updates synchronized by Configuration Manager can have update content published to WSUS by Configuration Manager. 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[27, PID:8812][02/06/2019 16:26:21] :STATMSG: (SRVMSG_SMS_ISVUPDATES_SYNCAGENT_UPDATECONTENT_NO_METADATA). 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[27, PID:8812][02/06/2019 16:26:22] :STATMSG: (SRVMSG_SMS_ISVUPDATES_SYNCAGENT_UPDATECONTENT_FAIL). 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[27, PID:8812][02/06/2019 16:26:22] :Launcher : Work item SyncUpdate has completed queued time was 00:00:00.1670159 run time was 00:00:00.1869994 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[27, PID:8812][02/06/2019 16:26:22] :SyncUpdate: c8d329d4-141d-47c4-9fb7-0d2855317ed4 - Completed. 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)


[Justin Chalfant (Patch My PC)]

I see. So in order for the SCCM right click option to publish the content (full-content) to work. The update would have needed to originally been published in SCCM using the third-party software update catalogs.


Based on these logs, it looks like they were published using some other method like scup or publishing service. The easiest work around would be to publish these updates with full-content using another tool like our publishing service or SCUP.

Any future updates published via the SCCM console should publish ok when choosing publish content.