What’s up SCUP?

Our friends in the Acrobat crew announced this week on their IT Maters blog that the forthcoming Acrobat X and Reader X updates will be available in the Microsoft System Center Updates Publisher (SCUP) catalog. Here’s the post:

SCCM and SCUP Catalog Deployments for Acrobat and Reader X « IT Matters
http://blogs.adobe.com/pdfitmatters/2010/11/sccm-and-scup-catalog-deployments-for-acrobat-and-reader-x.html

Now, here is the question for Windows IT admins: How helpful would it be to have the Adobe Creative Suite updates available in the SCUP catalog? How much estimated time/money would this save your IT organization? Please use the comments section to let us know if this should be a focus for us. I am also curious to hear how your are currently managing Adobe Creative Suite updates for your Windows users and what are the challenges you are currently facing with that current process. I may be reaching out to you offline for followups or might arrange a little Windows IT admin virtual meet-up to discuss how we can improve things on the Creative Suite application update front.

Thanks in advance for your input!

Cheers,

Jody Rodgers | Product Manager| Enterprise & Volume | Creative Suite

30 Responses to What’s up SCUP?

  1. Michael Curtis says:

    Seems a no brainer to me. Anything that makes it easier to mass rollout cs suites will be welcome. SCCM seems as goer place as any to start with as a supported rollout platform.

  2. Jody Rodgers says:

    Thanks Michael. Seems like a no-brainer in some ways to me too but I’d like to hear some more feedback and know more about how CS is being patched currently by folks.

    [It's like you can hear he crickets in here.]

    Windows admins of the world: Unite! Comment! Be heard!

    You are all probably busy prepping your Windows 7 deployments aren’t you?

    Jody Rodgers | Product Manager| Enterprise & Volume | Creative Suite

  3. Jason Luke says:

    How about the equivalent article for SCUP with Acrobat and Reader Pre-X versions? That would be most helpful now.

  4. Stuart says:

    I agree with Jason above; pre-X versions of acrobat and reader are far more common than the cs suite

  5. Max says:

    Please do this!
    Right now we are barely deploying the patches beacause it takes so much time.
    Since there are so many individual patches for CS it is also hard to get an overview of what the computers and users need. With SCUP we dont have to worry about that. Everything is pre-defined.

    SCUP would make it so much easier and would save us hours each month.

  6. Björn Axell says:

    Hi,
    Yes, Yes and yeas – we would love to have a catalog for Adobe CS. I would like to take it an extra step – Create a catalog that patch ALL Adobe products. For many of my customers, they just don’t patch Adobe CS because of problems. We have seen problem with a newer Adobe reader version then the Pro version.

  7. Tony says:

    Are you going to have something similar for flash player? It seems like we get an update every week. Also any news on Flash player for x64?

  8. JL says:

    We have CS deployed over several locations and countries. I handle the updates for SCCM right now and have been looking for this exact thing. It would save our helpdesk and desktop admins tons of time for me to push these out via SCUP. I know Acrobat had the catalogs for 9.X but there were a couple of catalogs that did not work so we either had to push it out via SCCM via Software Distribution instead of updates. I eventually ended up waiting for a full update. So it would be nice if the updates were tested before they are released.

  9. Luke says:

    We manage the software and deployment across 45 schools (6000 workstations) who have recently been consolidated in to our architecture. Unfortunately the 450 cumalative software products they have not been as equally goverened therefore difficult to maintain. This includes CS 3&4 and future CS5 suite licensed to 1000 worstations. Our reality is we simply have no time to deploy updates for CS suite so providing updates in a SCUP catalogue would be very beneficial.

  10. Darin says:

    We deploy the current install packages of CS4, and CS5 via SCCM across 8 high schools and use a program called DeepFreeze to keep the computers from getting corrupted by the students. Currently we have NO means of update aside from visiting each machine and updating manually. It would a huge benefit to have the updates in the catalog.

    Darin

  11. Aaron says:

    There should be SCCM and SCUP deployment guides for ALL adobe products.

  12. Jon says:

    CS updates via SCUP would be immensely helpful! I just rolled out Acrobat X and Reader X to my users and the first updates were done via the SCUP catalog and the installed flawlessly. The dozens of updates (which NEVER stack) that CS5 requires are far too tedious and as such, largely go unpatched otherwise. SCUP catalogs should be provided for ALL Adobe products, even if it’s only current generation.

  13. Henrik Frank says:

    Please do this sooner than later! With the size and complexity of the CS5 packages, having to re-do each base package (32 and 64bit) as well as creating an update package is a significant work load. We support individual products as well as complete suites on 800PCs at 100+ locations across the country. We are required to keep all the PCs patched, but it is virtually impossible for us to do this with the current patch process.

    Alternatively, you could improve the Adobe Update Server. For large organizations, it doesn’t offer enough granularity in what updates to deploy (we need to be able to select individual updates rather than just keeping the entire catalog in sync).

    Thanks!

  14. Brett Bonenberger says:

    As everyone else said, yes please provide sccm and scup deployment and patching.

  15. Jason says:

    An SCUP catalogue would be excellent.

    Currently our CS deployements largely go unpatched unless there is a specific issue due to the complexity & limited time on my schedule!

    When they do get patched, it is only ever done manually which takes alot of time, but since we have a ‘small’ deployment it makes it easier to handle than trying to package it up etc…

    Do it!

  16. Patrick says:

    Yes, please! Provide SCCM an SCUP deployment and patching. We use SCCM very helpfull in our enterprise.
    The central software distribution saves us several hours of manual work per week.
    Thx!

  17. Lee says:

    Patching CS currently is impractical on a large scale and simply doesn’t happen. We NEED this!

  18. Dered says:

    oh yes, please do… echoing above comments that we don’t even patch cs5 on windows computers because it is so time consuming.

  19. Ben says:

    I can’t even count the number of hours it would save our IT department if Adobe added SCUP catalogs for all its CS apps. It is one of the few things we’ve never been able to keep up with. So not only does it expose us to security vulnerabilities, but it tarnishes Adobe’s image in the eyes of the users and IT executives.

  20. Jim Blanchard says:

    Thanks Jody, not sure if you are still actively looking at this thread, but if you do make SCUP catalog it would be extremely advantageous for many enterprises as you can see from the previous posts. With CS5.5 now released I guess we would have to wait for CS6 or later?

    • Jody Rodgers says:

      Hi Jim. Yes indeed we are still monitoring this thread and I am glad people are still adding their comments. It was really slow at first and I was questioning the validity of doing them for CS but I heard first hand from lots of folks at MMS 2011 about the need for this. It is a big time saver for sure! I can provide a short update on where we are at and hopefully will do a blog post about this in the future. We are actively looking at doing SCUP updates for the CS updates. We have some challenges since our updates don’t come out on a set schedule. We’ll be doing some customer outreach on the topic to make sure our implementation is truly meeting the needs of the IT folks. I do not think we will be implementing them for CS 5.5 updates. We’ll keep you posted!

      Keep those comments coming!

      Jody Rodgers | Senior Product Manager | Enterprise & Volume | Creative Suite

  21. Conny Marment says:

    I’m not sure if this is the right forum or not (I’ll be brave!) but…from someone on the other side of the fence or at least at the other end of the package, we’ve seen some problems with Adobe’s Dreamweaver CS5.5 v11.5 after it’s packaged and deployed SCCm reporting identifies it as :
    ProductName ProductVersion
    Adobe Dreamweaver CS5.5 1.2.0000

    when a manual install of the same product is identified in SCCM as:
    ProductName ProductVersion
    Adobe Dreamweaver CS5.5 11.5

    It’s a nightmare to try and manage licensing for this product give the above because we need to track the product version. Adobe charges licensing costs for different versions. Is it our local packagers of the product doing something “different” or is it a commonality for SCCM?
    cheers
    Conny

  22. Conny Marment says:

    Sorry folks….a correction to my previous post…Adobe’s own packaging tool is used. When used it changes the version of the installed product to the version of the tool. ARRGGHH! Is there a way around this?

  23. ccyril says:

    SCUP catalog for CS5 and CS6 would be welcomed. Flash, Reader and Acrobat SCUP catalogs are a huge help in patching systems that need it. I would like to see the same for the other adobe products.

  24. We’re looking forward to seeing Creative Suite in the SCUP catalog.

    I can confirm the same issue that Conny Marment mentioned above. Versjon is now 1.2.0000 and we have used this in our Query-Based Collections in SCCM. If a manual install is performed, our query-based collections don’t pick it up.

    ALSO!! We have observed that UNINSTALLING Creative Suite 5, 5.5 or 6, does not cleanup properly. There’s always something left in the registry which also causes issues with queries for collections in SCCM, as well as possibly an issue when it comes time to count licenses (if data collection for counting licenses was based on registry and not EXE-files. The files are removed upon uninstall, so that would work…)

  25. I might add, that without SCUP catalogs for CS6, we won’t be patching CS6 at all, and that’s not very good for the users, however, it’s too much work to handle manually. And our users don’t have the rights to run updates themselves and will not get that either.

  26. Jonas Edholm says:

    For us the SCUP updates is a must for being updated on the suite. As long as there is no SCUP support we will only deploy the updates that we must and not all as we should.

  27. Jason says:

    I know it’s been a while since this post, but has there been any scupdate on this?
    SCUP for Creative Could would certainly make our lives much easier, as it stands I need to create a new Adobe Update server to keep our clients up to date, and hope it works. The control which SCUP provides would be awesome!
    Please, Will someone please think of the IT pro?

Leave a Reply

Your email address will not be published. Required fields are marked *


1 + three =

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>