I put some test in the optional fields and saved it. that made the version increment. thanks for the suggestion about version.
/Todd On Sat, Aug 10, 2013 at 6:51 AM, Sherry Kissinger <[email protected] > wrote: > No replies on this yet? Well, here's a thought. I'm not at work, so can't > look up my exact notes. And you'll hate this suggestion anyway. There was > about a year + ago where 3 (only 3 that's why it wasn't that big of a deal > for me) where I had something similar. I literally found the entries in the > wsus' susdb, and incremented their version from 101 to 102, so that cm > would see them as different enough to really sync. Completely unsupported, > but since my other choice from our PFE was to rebuild the entire sum... > manually changing the entries was the last resort before teardown. > > But before you do that... I'd try this. In your sum settings, where you > say something like 'sync daily at 12:15 pm' just wait past the normal sync > time, for the full sync, or change it temporarily to 10 minutes from now, > and then watch wsyncmgr.log. I've seen it where custom updates don't sync > right from a right click sync, but do from the scheduled full sync. > > Todd Hemsell <[email protected]> wrote: >> >> So I published some updates from the HP and Dell catalogs "Metadata Only" >> Now I am trying to publish them as full content. There are no errors, but >> they are still "Metadata Only" in SCCM. I have synced up about 5 times now. >> >> Is there a way to make them publish the content? >> >> /Todd >> >> >
