Adobe Creative Cloud 2017

[Arthur]

Download through the Creative Cloud desktop app or packager.

 

What's New (Photoshop, Illustrator, InDesign, After Effects, Animate, Audition, Character Animator, Dreamweaver, Premiere Pro, XD)

 

Today we announced the 2017 release of Creative Cloud. To make sure the Creative Cloud stays at the forefront of innovation and continues to meet the top challenges designers, photographers and filmmakers face today, we have focused on three guiding principles:

 

First, our cloud-first approach ensures your assets and edits are all in sync across devices, allowing you to create where and when you want, with the latest, full fidelity version of your content.

 

Second, we help you address the demands of increasing content velocity by providing a marketplace for design content that helps you work faster.

 

And third, it’s all built with a hyper focus on experience —so our members can do their best work faster and easier, and the tools simply get out of the way so the focus can be on creation.

 

This is the essence of this release. Much of this is available today, with more updates available over the coming months

 

Source: https://blogs.adobe.com/conversations/2016/11/max-and-the-future-of-creativity-and-design.html

 

 

 

 

 

 

 

 

[Arthur]

http://blogs.adobe.com/oobe/2016/11/creative-cloud-packager-1-10-creative-cloud-2017-are-live.html

 

Last week we went live with CCP 1.10 which, to the delight of the team has broken the endless 1.9.x loop. This release includes various under the hood changes but most significantly also includes the below features

 

• When you create a package, a packageInfo.txt is created inside the build package folder. This file contains the list of products and updates that you have included in the package. For more information see, Deploy packages.
  
• When you create a package, a ConflictingProcessList.xml is created inside the build package folder. This file contains information about processes that will conflict with the installation process. For more information, see Deploy packages.
  
• When you start the installer, it will check for the conflicting processes running on the host computer and exit the installation if any conflicting processes are found.
  
• The latest version of Remote Update Manager will be downloaded and packaged during the package creation process. For more information, see Use Adobe Remote Update Manager.
  

Also by way of a sneak we will shortly be including a new workflow in CCP for uninstalling previous versions of Creative Cloud applications. If you recall presently the best method to remove a previous version is to use the original CCP package, however if you no longer have that package or wanted to remove only a subset of the applications that were packaged then you are out of luck. This feature when released in November will provide granular control over what previous version of the Creative Cloud applications to remove. I normally don’t like to speak about a feature before it is released but considering our big announcement today I thought it would be useful to know this was on the horizon.

[Manny-Tech]

I have deployed my package with the CCP. What is the easiest way to update? I was under the impression I'd be able to use Remote Update Manager but it just comes back saying

 

"No new applicable Updates. Seems like all products are up-to-date.RemoteUpdateManager exiting with Return Code (0)"

 

Surely I'm not going to have to repackage it all and send it out to over 100 clients?

[Manny-Tech]

I've just read the blog above actually. Looks like you can't use the Remote Update Manager for this purpose as they are full installers. Think I'll be using the CC Cleaner Tool to remove then send out the latest version.