Participating Frequently

Answered

Cannot deploy CC 2015 or 2017 from network

Forum|Forum|9 years ago
November 2, 2016
21 replies
11501 views

I cannot deploy creative cloud in our environment over the network. We use a combination of SCCM and WDS to deploy creative cloud and nothing is working. I am creating a 64-bit package with Photoshop, Illustrator, Premier, In Design, and Acrobat DC. If I silently run the install from a network drive it installs Acrobat/Distiller and than suddenly rolls everything back and fails. If I double-click the setup.exe to just see what happens, it fails within a few seconds. However if I COPY the Adobe Package Folder I created LOCALLY to the desktop and run the setup silently or just double-click the .exe it installs 100% without an issue. What is the problem? Thank You.

This topic has been closed for replies.

Correct answer alisterblack

The CCP engineering blog is at Adobe Installation and Licensing | Blog to post all Installer and Licensing related info to users of Adobe products

Show previous replies

Maillol

Participant

Same problem here

I hope technical staff will find a solution. I think crazy that we have to copy installation folder locally every time.

It's not my conception of deployment...

K

karmsemaj

Participant

Has there been any development on this issue as I am suffering from the same problem?

alisterblack

Inspiring

We have an open issue with our engineering team at the moment which is being actively worked on.

The current advice is to install via a tool such as SCCM or from the local machine.

T

tomr89374087

Participant

In terms of the SCCM method, I am using this currently but seeing the same issue as above I believe ?

T

tomr89374087

Participant

I believe I am having a similar problem, following this thread as have been spinning wheels on this trying everything to get it deployed via SCCM the last few days. Cannot seem to get CCP built packages of either full suite or just Acrobat to install. Kdorsh can you please update thread with the findings from yourself and the engineers once resolved ?

thanks

bootrec

Participating Frequently

Adding my bit for what it's worth;

I don't use SCCM, but we usually install from a network share or a memory stick. Neither work and I'm not sure if it's since upgrading to packager 1.10 or AdobeCC 2017. Windows and Mac. HAVE to copy installer to computer... and not a second drive in the computer, the main OS drive. Only way I've been able to install the full suite so far.

K

KdorshAuthor

Participating Frequently

I didn't realize this post caught some steam, my apologies, I have been speaking with the engineering team for the past couple of days on this issue after they finally admitted it was an issue. They are supposedly calling me today with a workaround over the network. I understand the solution is to "copy" the adobe folder/installer locally to the desktop. This does not work in an organization with 600+ computers.

bdpdarren

Participant

Hi,

Have you received a response from the engineering team. I am having the same problem with a new package created with Adobe Cloud Packager 1.10. My package contains (Adobe Photoshop, InDesign, Illustrator and Acrobat DC). When I run setup.exe on a clean standard build the install fails but the logs show Acrobat DC installs and is uninstalled. I created a clean virtual machine using the Windows 7 x64 SP1 ISO from Microsoft and the install was successful. However, I do not have any problems installing an earlier package with the same Adobe applications created with an earlier version of Cloud Packager.

I have emailed Adobe Enterprise Technical Support but haven't received a response as yet.

bdpdarren

Participant

I forgot to mention that running the install locally or across the network makes no difference, It fails everytime.

babeers

Participating Frequently

Is there any update on this issue?

alisterblack

Inspiring

I heard from our engineering team this morning. They have replicated this issue.

The issue should not occur if using SCCM or similar tools.

I am awaiting further information regarding the next steps but for now the solution is to install from the local machine or use a tool such as SCCM.

G

gchandler_disd

Participant

Well, SCCM works depending on how you utilize the deployment. A standard SCCM deployment just copies the install files locally to the client cache and installs from there. So, it's the same process that you're stating that works.

We use SCCM and deploy a small script to run the install from a network location so that 15GB+ of data isn't copied locally to the cache. Mostly because we are a school district and downloading that much content is a load on our network as we don't have any P2P technologies in place.

Just don't want anyone to be fooled by the statement "It works with SCCM", because that is a subjective statement.

The real resolution will come from the engineering team. Please let us know when they have a fix in place. Thanks.

babeers

Participating Frequently

I'm having this issue as well. I've imaged a computer with our Windows 10 base, which includes no additional application. CC2017 will not install across the network. I'm getting the same error or the base path not available.

G

gchandler_disd

Participant

I'm facing the same issue. Worked on earlier versions of CC, but just packaged one last week and it won't install from network location. Thought the 2017 release would fix it, but still doing the same thing.

M

MikevB56

Participant

I had this problem as well, the workaround is to copy the installation folder to the local computer and run it from there.

Where is the QA team? Running an installation from the network is a basic feature.

alisterblack

Inspiring

Hi,

I'd like to check this with our engineering team. Please collect logs using the log collector tool and share them with me via PM. (click on my name). Thanks.

Log Collector Tool

K

KdorshAuthor

Participating Frequently

Anyone......HELLO Adobe?

alisterblack

Inspiring

Rollback may indicate a process conflict.

If you have built your package with the current version of Creative Cloud Packager the Build folder will contain ConflictingProcessList.xml which will list processes likely to conflict. See Creative Cloud Help | Creative Cloud Packager release notes

Deploy Adobe packages with SCCM

H

hubertlam

Participant

I doubt there's a conflicting process. It's more Creative Cloud Packager 1.10.26 playing up.

I also got these two lines in PDApp.log that Kdorsh also got: (I just copied/pasted from his log above -- the error is exactly the same -- The Setup base path does not exist)

11/02/16 14:13:02:037 | [ERROR] | | ASU | DeploymentManager | DeploymentManager | | | 2964 | Failed to Initialize .... The Setup base path does not exist.

11/02/16 14:13:02:037 | [ERROR] | | ASU | DeploymentManager | DeploymentManager | | | 2964 | Failed to Initialize from parameters.

I've been using the same build procedures for the image: in a VM, having installed other programs ahead of Adobe Creative Cloud 2015.5 before (with a package created by Creative Cloud Packager 1.9.6), with no issues. Come 2017, this fails spectacularly.

I've also tried:

* Installing CC2017 as the very first application to be installed (fails)

* Rebooting before installing CC2017 (fails)

There is no rollback on my VM as it's a fresh installation of Windows.

Installation does not fail after I copy the entire installation package from the network location \\adm\setup\adobe\cc2017 or s:\setup\adobe\cc2017 (after mapping a network drive to \\adm\setup) to c:\temp!

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.