Jump to content


slux

Established Members
  • Posts

    1
  • Joined

  • Last visited

slux's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I get the exact same problem but no idea how to fix it - looks like the SCCM 2012 install installs two special packages - the client install and the client update package. Turns out my client upgrade package never got added in properly. I can create a new one from definition - but it gets a new ID. How do we either remove the bogus package that is creating lots of spurious distribution errors or how do I repair it? I tried removing it from the WMI on the various DP's but it comes back because it exists in the DB. The source files exist just no package files My install was a clean 2012 RTM install. (single primary site) Thanks, Sam
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.