- #HOW TO UNINSTALL INDESIGN CC 2017 MAC OS X#
- #HOW TO UNINSTALL INDESIGN CC 2017 INSTALL#
- #HOW TO UNINSTALL INDESIGN CC 2017 ZIP#
- #HOW TO UNINSTALL INDESIGN CC 2017 WINDOWS#
However, to update to InDesign CC 2015 on a Macintosh computer, you must be running Mac OS X 10.9 or 10.10.
#HOW TO UNINSTALL INDESIGN CC 2017 WINDOWS#
The system requirements for Windows users remain the same as for InDesign CC 2014, so if you already have that installed, you should see an update appear for InDesign CC 2015.
New Mac System Requirements for InDesign CC 2015
#HOW TO UNINSTALL INDESIGN CC 2017 INSTALL#
If you have any further problems updating, go to Adobe’s Creative Cloud Download & Install forum for further help. If for some reason this doesn’t happen, or if the Creative Cloud app window doesn’t appear correctly, re-start your computer. You should be prompted to update Creative Cloud. Then re-launch the Adobe Creative Cloud app from your Applications folder. If you don’t have the current version, choose Quit from the Creative Cloud desktop app menu. The current version as of today’s date is 2.1.1.110. You can check by opening the desktop app, selecting the “gear” icon to view the menu, and then selecting Preferences to view your current version. You may have already had a “silent” update to the version of your CC desktop app. Have the Current Version of the CC AppĬreative Cloud applications are installed and uninstalled with the Creative Cloud desktop app, and it’s critical that you have the most recent version of the CC App before updating other apps. Here are a three things you need to know to make your installation as easy and pain-free as possible: 1. However, Adobe also made some changes in the installation process and requirements which may cause some pain and consternation. You can read about the features in InDesign CC 2015 in InDesign CC 2015. The new update is called InDesign CC 2015. If you have further questions, just ask.Adobe released the new versions of InDesign CC and 14 other Creative Cloud applications at 9 pm Pacific Time on June 15. That will uninstall the existing CC and then run along to install the new CC 2017 installers. If you are uninstalling an existing CC install, you can add the uninstaller PKG files to the install policy with a priority set to a lower priority than your CC 2017 installers. I cannot speak to Sites, if you have your environment broken down using the Sites component in Jamf Pro, but the process should be very similar. I've used this method since CS6 to deploy CC, CC 2014, and CC 2015 with minimal issues. If deploying at Login or Logout I would use either jamfHelper, cocoadialog, or the built in User Interaction tab to throw up a message before the policy started running to let the users know what was going on. This policy would be set to either "Login", "Logout", or no trigger and it would be set as a Self Service policy with a good description of what is going to happen, asking the users to close all open Adobe apps, and the "Ensure users view." checkbox checked. With this second SG created, I would then create a second policy set to "Install Cached" and scope it to the second SG, the one looking for "Cached Packages Has". Next, I would create a second Smart Group that had as its criteria "Cached Packages Has" and the name of one of the CCP packages that were cached in the previous profile. The trigger for this policy would be "Recurring Check-In" and it would be set to run once. I would create a policy that cached the necessary CCP created packages to the machines in that group. If I am deploying only to a select sample of computers, like our Studio department, for example, I would create either a Smart Group that was scoped to those machines, or just use the Department scoping in a policy.
#HOW TO UNINSTALL INDESIGN CC 2017 ZIP#
During the upload process Casper Admin compresses the PKG files into ZIP files. A lot of it comes down to what type of distribution point you are using JDS, SMB share, AFP share, HTTP share, etc.įor my environment (JSS 9.96, JDS 9.96 w/SMB and HTTP shares), I create PKG files using Creative Cloud Packager for each individual app (Bridge, Photoshop, Illustrator, InDesign, etc) and then upload them via Casper Admin. A search through Jamf Nation will turn up plenty of articles on deployment. I do not believe there is any official documentation, and there are a dozen different ways that folks have found work through the years.