Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

← Ideas

3rd Party Patching - SCUP Integration with SCCM Console

Integrate the SCUP tool on to SCCM Admin Console. This will give a single pane of glass view for all patching activities (including importing 3rd party patches).

3,785 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Prasanna K Jayapal [Microsoft ConfigMgr Product Team] shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

94 comments

Attach a File
Sign in
(thinking…)
Sign in with: facebook google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
  • Anonymous commented  ·   ·  Flag as inappropriate

    Please add full functionality of SCUP to this feature. Adobe Acrobat catalogs don't expire older updates and don't include supersedence information. I normally added supersedence info through SCUP. Without the ability to edit this information or to expire old updates manually, deploying acrobat updates becomes unwieldy. Unexpired updates that are not superseded will likely bloat and fill up the data shares. Am I missing something here?

  • Justin Chalfant commented  ·   ·  Flag as inappropriate

    @Greg Isett, you would most likely need to have internet access on the Software Update Point. In theory, you could maybe host a catalog file on an internal server, but you would still need internet access to be able to download the third-party software update content files. Here's a little more on the setup that may be helpful for you https://www.youtube.com/watch?v=rBdmWbf5Vgg - Justin Chalfant

  • Steven commented  ·   ·  Flag as inappropriate

    So 1807 TP has custom catalogs. Looks like we’ll have to wait j til 1810. :(

  • Nathan Nitzel commented  ·   ·  Flag as inappropriate

    Dave's question below is the same one I have. It is THE question and THE problem SCUP has always had. Was this integrated just so that we could continue to buy a 3rd party solution to fill it out in a single pane of glass? That's great and all but I don't think its the reason this got 3,800 upvotes.

  • Dave commented  ·   ·  Flag as inappropriate

    So from what im understanding, the SCUP is essentially integrated into the SCCM console which is nice to see. However, the real benefit of this is getting the 3rd party catalogs to sync. my readings are showing that HP is the only catalog included with 1806. and i am only aware of a couple of other "free" catalogs that can be added to sync. Do we know if/when Microsoft will start integrating more and more 3rd party apps?

  • Jeremy Cooper commented  ·   ·  Flag as inappropriate

    I would also love to see this functionality work within the OSD. As an example if you are completing an OSD you need to manually add the certs to the correct stores, and set the reg key to enable the SCUP updates to install. We do this now with a GPO, but doesn't apply during OSD for obvious reasons.

  • Anonymous commented  ·   ·  Flag as inappropriate

    So this just enables something that anyone who's already using SCUP already has enabled?

  • Steven commented  ·   ·  Flag as inappropriate

    This feature request was written almost 3 years ago; since then you just simplified the cert deployment and the GPO setting. Hilarious. We've had these features on lock in other means a CA for the cert deployment and GPO for the enablement of 3rd party updates already. What is coming for 1806 so we don't get 'teased' again. Please share your thoughts!

  • Andres Pae commented  ·   ·  Flag as inappropriate

    Its a good start, but I feels it is to late. Problem is that only some of 3rd party publishes are publishing his product updates in catalog. It is something that MS cant provide or request to do. Maybe there is to less "momentum" for going catalog way for 3praty vendors. It is to complex, less used. For God sake - even MS Skype is not patched via MS updates catalog. To be honest - this technology was avail many-many years, yes, it is inconvenient, but works. But no CONTENT ( ie patches to version, or upgrades to new version). If this is resolved - then - big applause!

  • bdam commented  ·   ·  Flag as inappropriate

    Great to see this started. I'd like to suggest that 'integration' needs to be more than skin-deep. Just getting SCUP's GUI into the ConfigMan console would be a good start but I'd argue that true integration into the update workflow is much more important. The goal should be total automation where third party updates function no differently then first party. The sync (manual or scheduled) brings in newly released updates from the catalog and ADRs can deploy them.

    Bonus points for allowing the automation of modifications to the command lines used based on vendor/product. Thinking of apps like Java and flash where different companies will want different parameters used to prevent auto-updating, desktop icons, and the like.

  • Richard Archer commented  ·   ·  Flag as inappropriate

    @Troy, according to the SCUP Preview announcement (https://cloudblogs.microsoft.com/enterprisemobility/2017/07/03/system-center-updates-publisher-june-2017-preview-is-now-available/) they're unrelated:

    "This preview is to enable SCUP 2011 features on our newest OSes and is not directly related to work that is planned for Configuration Manager Console Integration. For the latest news about that, please see the UserVoice item here."

  • Troy commented  ·   ·  Flag as inappropriate

    Some update on this would be great. Wondering if it got cancelled since the SCUP Preview got released?

← Previous 1 3 4 5

Ideas: Software Updates

Feedback and Knowledge Base

(thinking…)