Skip to main content
Question

Adobe CC 2015 Core PKG Installing very Slowy via Self Service...Installs, but Hangs...

  • March 4, 2016
  • 4 replies
  • 50 views
J
Forum|alt.badge.img+12

I have an Adobe CC 2015.2 PKG that I have available in Self Service. It's a sort of Core installer: the main CC 2015 apps: Photoshop, Illustrator, After Effects, etc.

It's about 8.5 GB total, made the standard wade wit the latest Adobe Creative Cloud Packager (CCP).

Even if I install this PKG locally, even after the last app is installed (Photoshop), the Installer just sort of hangs around for maybe 5-8 minutes, then it will report "Successfully Installed". I can get the Logs from the Adobe installer, something is timing out, or something.

From Self Services, it's a crap shoot. Sometimes it will hang. In using SS, it takes at least 3-4 minutes for SS to go from "Mounting DP", to "Installing". Why is the DP taking so ling to mount, and only on this PKG.

Would going to HTTPS (from AFP) speed up / stabilize Self Service?

And / or... is there a way / benefit to compile the Adobe installers?

thx,

john

    4 replies

    T
    Forum|alt.badge.img+15
    • thoule
    • Contributor
    • March 4, 2016

    Running this installer from an AFP share is a killer. I assume the 'mounting' command also does a checksum which is why it may take that long. You should switch to HTTP. In the meantime, you can cache the installer. Then have a smart group of users that have it cached. Then a policy scoped to them to install the software. That's the most reliable way for the installer to work for users.

    dpertschi
    Forum|alt.badge.img+19
    • dpertschi
    • Contributor
    • March 4, 2016

    @johnklimeck I see the SS status reporting "Mounting DP" for a long time on all my giant packages as well.

    Presumably there is no other displayable status between 'mounting dp' and 'installing xyz.pkg.' So that's all you get for status as long as it takes to download and start installing.

    J
    Forum|alt.badge.img+12
    • johnklimeck
    • Author
    • Contributor
    • March 4, 2016

    Thoule,

    Greatly appreciated, have never used "cache" or "install cached", I can see how it is useful for big files.

    Will do as suggested.

    Now, might you or someone kindly point me to getting HTTPS properly set up and properly and working on OS X Server (10.11 El Cap). I know there are some symlinks that had to be put in place, on older OS X Server. thx in advance, john

    J
    Forum|alt.badge.img+26
    • jhalvorson
    • Honored Contributor
    • March 4, 2016

    I just used this command the other day to setup http on a EL Capitan based DP.

    sudo ln -s /Users/Shared/cshare02 /Library/Server/Web/Data/Sites/Default/cshare02

    That's the answer for creating the symlink.

    The first path (/Users/Shared/cshare02) is where the files that are currently shared via afp. Change the path and folder name to what is in use on your server.
    The second path (/Library/Server/Web/Data/Sites/Default/cshare02) is the default path for http or https.

    Terms & ConditionsCookie settingsAccessibility statement