Adobe Update Server Setup Tool
ADOBE UPDATE SERVER SETUP TOOLTECHNICAL NOTEDocument Version 2.1 March 2013
For legal notices, see http://help.adobe.com/en US/legalnotices/index.html.
ContentsAdobe Update Server Setup Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Using AUSST to set up your own update server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2What’s new in AUSST 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.Setting up an update server: at a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4Location of the Adobe Update Server Setup Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Preparing a web server to use as the update server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Performing One-Time Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Verifying the set up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Setting up Client Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Generating client configuration files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Deploying client configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Synchronizing with the Adobe Update Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Incremental Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Fresh Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Setting Up IIS Server for Use with AUSST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Setting up IIS Server 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Setting up IIS Server 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Ensure that the web server is set up correctly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Check network connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Ensure that there are no unwanted spaces in commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Specify full URLs with protocol and port number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Ensure that the location for storing the updates has write permission . . . . . . . . . . . . . . . . . . . . . . . . . 20Ensure that the client configuration files are generated correctly on the in-house server . . . . . . . 20Ensure that the client configuration files are deployed correctly on the client machines . . . . . . . 20Ensure that paths specified are absolute paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Use the fresh sync option if multiple updates are visible on client machines . . . . . . . . . . . . . . . . . . . 21Use the fresh sync option if other troubleshooting steps fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Perform a fresh install as a last resort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Migrating from one in-house update server to another . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Setup and synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Updating client machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Running AUSST command without specific parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
1Adobe Update Server Setup ToolThis document describes how to install and configure Adobe Update Server Setup Tool (AUSST), which is autility to help you set up your own update server to manage the deployment of Adobe product updates inyour enterprise.Updates are downloaded for both the Windows and the Mac OS platforms.NOTE: AUSST is intended for the enterprise IT administrator who sets up and maintains the in-houseupdate server.OverviewIn an individual product installation, the Adobe Application Manager launches automatically every day at2:00 am to check with the Adobe Update Server for updates to Adobe products. If a product update isfound, the application displays a message. The user can then choose to download and install the update.Users can also use the Help - Updates menu command to invoke the Adobe Application Manager tocheck for product updates, and, if one is found, download and install it.Machine 1PhotoshopAdobe Update ServerApplicationManagerMachine 2DreamweaverPhotoshopApplicationManagerAdobe productupdatesMachine 3IllustratorApplicationManagerClient machines download product updatesdirectly from the Adobe update serverUsing AUSST to set up your own update serverIn an enterprise environment, you might prefer to host your own update server to download and storeupdates from the Adobe Update server.2
Adobe Update Server Setup Tool3The Adobe Update Server Setup Tool (AUSST) helps you to configure your own update server anddownload product updates from the Adobe Update Server to it. Once you have set up your own updateserver, you can redirect the Adobe Application Manager to your own server, rather than the Adobe UpdateServer. When you do this, the Adobe Application Manager on the client machines checks for updates onyour server, and when instructed, downloads the updates from your server.Machine 1PhotoshopAdobe Update ServerApplicationManagerMachine 2DreamweaverPhotoshopApplicationManagerUpdate ServerAdobe ProductUpdatesAUSST Web ServerMachine 3IllustratorApplicationManagerUsing AUSST, you can set up your own update server,from which the client machines download updates.NOTE: The purpose of AUSST is to help you host an in-house update server so that the client machinescheck for updates on the in-house server instead of the Adobe update server. AUSST is not currentlyintended for remotely deploying updates on machines in your network.What’s new in AUSST 3.0AUSST 3.0 provides the following enhancements over the previous version (AUSST 2.0) that was shippedwith Adobe Application Manager Enterprise Edition 3.1. There is a major performance improvement—for example, AUSST 3.0 synchronizes the updates up tofour times faster than the previous version for fresh synchronization. Support for proxy servers has been added. You can automate or schedule AUSST runs -- AUSST now includes options to run the commandwithout any manual intervention at run time. Download progress is displayed real-time on the console.
Adobe Update Server Setup Tool 4AUSST now provides a log file that includes status and troubleshooting information.To run AUSST, you will need to make the following change to the AUSST 2.0 setup: The name of the tool has changed from AdobeUpdateServerSetupTool2.0 toAdobeUpdateServerSetupTool. You should, therefore, update your previous scripts accordingly.Setting up an update server: at a glanceHere are the main steps for setting up your in-house update server using AUSST. You will need an alreadyup and running http server to use as the update server.NOTE: AUSST is available in the utilities folder of Adobe Creative Cloud Packager installation.1. Ensure that a web server is available2. Perform one-time setup using AUSST:As part of the one-time setup, AUSST does the following: Performs the initial configuration Sets up a directory structure similar to the one on the Adobe update server Copies updates from Adobe update server to the web server. Both Windows and Mac OS updateswill be downloaded.3. Periodically, synchronize the latest updates from the Adobe update server to the web server. Performthis step regularly to ensure that your in-house server hosts the latest updates.These steps are described in the next sections. The following diagram illustrates the process and provideslinks to the sections in this document where the corresponding steps are explained.NOTE: The paths provided to all the command-line options should be absolute paths. AUSST does notsupport relative paths.
Adobe Update Server Setup Tool5Locate AUSSTAUSST is available in the utilities folder. Set up your web serverYou can set up your in-house update server on any HTTP server (such asApache or IIS) that can serve static file content.Perform one-time configuration and download updatesRun the following command: For details, see:“Location of theAdobe UpdateServer SetupTool””For details, see: “Preparing a webserver to use asthe update server”For details, see: PerformingOne-Time SetupAdobeUpdateServerSetupTool --root root location --fresh Ensure that there are no spaces around the sign. The root folder is thefile-system location on your in-house update server where updates are to bedownloaded from the Adobe update server. Ensure that the root location canbe served by your web server.Verify the setup1. Confirm that the home page of the web server can be accessed frombrowsers on client machines and that the root location has productupdates available on it.2. Check that the updaterfeed.xml files on the update server can beaccessed from browsers on client machines.Set up client machinesCreate an XML configuration file (AdobeUpdater.overrides) and deploy iton users’ machines. The location of this file is platform-specific.Periodically synchronize with Adobe Update ServerRun the following command: AdobeUpdateServerSetupTool --root root location --incremental Ensure that there are no spaces around the sign. When you specify the --incremental parameter, only the new updates aredownloaded. downloaded and existing updates are overwritten.For details, see: “Verifying the setup”For details, see: “Setting up ClientMachines”For details, see: “Synchronizingwith the AdobeUpdate Server”
Adobe Update Server Setup Tool6Location of the Adobe Update Server Setup ToolAUSST is available as .exe (Windows) or UNIX executable (Mac OS) file.If you use Creative Cloud Packager to deploy Adobe products, AUSST is made available as part of theCreative Cloud Packager installation. Here are the locations:In Windows 32-bit system drive :\Program USSTIn Windows 64-bit system drive :\Program Files USSTIn Mac OS/Library/Application Support/Adobe/OOBE/PDApp/CCP/utilities/AUSSTAUSST is a command line tool and needs no separate installation steps. There are no restrictions on whereAUSST should be located on the machine.Preparing a web server to use as the update serverYou can set up your in-house update server on any HTTP server (such as Apache or IIS) that can host andserve static file content. An already up and running http server is a pre-requisite for setting up AUSST.To use a specific port, configure the port number while setting up the client machines. You will only needto provide the port number in the client configuration file (overrides file).If you use Internet Information Services (IIS) Server as your web server, refer to the following section forconfiguring the IIS server for use as the update server. Setting Up IIS Server for Use with AUSSTPerforming One-Time SetupTo set up your in-house update server for the first time, you use the Adobe Update Server Setup tool tocreate an update directory structure at the root folder location you created. If any files or folders exist atthat location, the tool removes them. It then creates the folder structure that matches that of the Adobeupdate server, and performs the initial synchronization that downloads all available updates from theAdobe update server to your in-house server.Here are the steps to run the tool for first-time configuration:1. Run the tool in a command shell or terminal, specifying your root update folder. For example:AdobeUpdateServerSetupTool --root root folder location --fresh [--proxyusername proxy username --proxypassword proxy password ] [--silent] The --fresh parameter removes any existing files from the root location (if it exists) and thendownloads all the updates present on the Adobe Update Server.
Adobe Update Server Setup Tool 7The [--proxyusername proxy username --proxypassword proxy password ]parameteris optional and specifies the proxy username and password if a proxy server is required to connectto the network.The --silent parameter suppresses the warning that is displayed by default in case the root folderspecified already exists. NOTE: Ensure that there are no spaces around the sign.The root folder is the file-system location on your in-house update server where updates from theAdobe update server are stored. The root folder location must map to a valid HTTP URL.NOTE: Ensure that the root folder lies within the access of the server root location so that updatecontent can be served by the web server.As an example, suppose: The root update folder on your web server is at the file-system location /serverroot/updates/ The web server's URL is http://serverabc.example.com:80 Within your web server, you set up the in-house update server athttp://serverabc.example.com:80/Adobe/CSIn this case (which we will use as an example throughout this document), the root folder location is--root "/serverroot/updates/Adobe/CS"For this example, the command to run the updates will be:AdobeUpdateServerSetupTool --root "/serverroot/updates/Adobe/CS" --freshAUSST creates a directory structure for the updates in the root folder and then copies the updates from theAdobe update server to your in-house update server.NOTE: Both Windows and Mac OS updates are downloaded. Currently, you cannot selectively downloadupdates for only one platform.As soon as you have completed this initial setup, your in-house update server is ready to update clientmachines.NOTE: Errors, warnings, and troubleshooting information are recorded in the log file. the log file is locatedin the %temp% folder in Windows and in the /Library/Logs in Mac OS.Verifying the set upTo confirm that the first-time configuration is successful, check the following1. Ensure that the web server is running correctly — confirm that the home page of the web server canbe accessed from a client machine.2. Confirm that the root location has the Adobe product updates available on it. If not, check that theroot location has the correct write permissions.3. Confirm that you can view/download the updates from the client machines through a browser.4. Check that the updaterfeed.xml files on the update server can be accessed from browsers on theclient machines.
Adobe Update Server Setup Tool8The updaterfeed.xml files are located at the following path, determined by the parameters in theoverrides file:http:// Domain : Port / URL /updaterfeed.xmlFor example, let us assume that the override file has the following entries Overrides Application appID "webfeed" Domain http://serverabc.example.com /Domain URL /Adobe/CS/webfeed/oobe/aam10/win/ /URL Port 1234 /Port /Application Application appID "webfeed20" Domain http://serverabc.example.com /Domain URL /Adobe/CS/webfeed/oobe/aam20/win/ /URL Port 1234 /Port /Application Application appID "updates" Domain http://serverabc.example.com /Domain URL /Adobe/CS/updates/oobe/aam10/win/ /URL Port 1234 /Port /Application Application appID "updates20" Domain http://serverabc.example.com /Domain URL /Adobe/CS/updates/oobe/aam20/win/ /URL Port 1234 /Port /Application /Overrides In this case, the location of the updaterfeed.xml file will be as /win/updaterfeed.xmlThe location on Mac OS will updaterfeed.xmlNOTE: When you view the updaterfeed.xml file in a browser, you will not be able to view the content inthe file. This is OK; you only need to ensure that the file is accessible through the http:// path. You can viewthe content of the updaterfeed.xml file by right-clicking and viewing the source.Setting up Client MachinesThe Adobe Application Manager on client machines, by default, checks for updates on the Adobe updateserver. When you host your own update server, you must configure the Adobe Application Manager oneach user's machine to check for updates on your own server instead.To do this, you must create an XML configuration file (AdobeUpdater.overrides) and deploy it on the users'machines. You can create the client configuration files in a text editor, or use the tool to generate themautomatically as explained in the next section. The configuration file provides the domain, URL and portinformation for your in-house update server; the URL is different for Windows and Mac OS platforms. Thefollowing shows the format of the AdobeUpdater.Overrides file, using our example server information(see “Performing One-Time Setup” for the example server information):
Adobe Update Server Setup Tool9NOTE: If you migrated from one version of AUSST to another, you must update the XML configuration fileson the client machines.IN WINDOWS: ?xml version "1.0" encoding "UTF-8" ? Overrides Application appID "webfeed" Domain http://serverabc.example.com /Domain URL /Adobe/CS/webfeed/oobe/aam10/win/ /URL Port 1234 /Port /Application Application appID "webfeed20" Domain http://serverabc.example.com /Domain URL /Adobe/CS/webfeed/oobe/aam20/win/ /URL Port 1234 /Port /Application Application appID "updates" Domain http://serverabc.example.com /Domain URL /Adobe/CS/updates/oobe/aam10/win/ /URL Port 1234 /Port /Application Application appID "updates20" Domain http://serverabc.example.com /Domain URL /Adobe/CS/updates/oobe/aam20/win/ /URL Port 1234 /Port /Application /Overrides IN MAC OS:In Mac OS, the URL specifies the mac/ subfolder instead of the win/ subfolder:. URL /Adobe/CS/webfeed/oobe/aam10/mac/ /URL . URL /Adobe/CS/webfeed20/oobe/aam20/mac/ /URL . URL /Adobe/CS/updates/oobe/aam10/mac/ /URL . URL /Adobe/CS/updates20/oobe/aam20/mac/ /URL .Generating client configuration filesYou can generate the client configuration files automatically with AUSST. You can only do this after youhave set up your server and
Copies updates from Adobe update server to the web server. Both Windows and Mac OS updates will be downloaded. 3. Periodically, synchronize the latest updates from the Adobe update server to the web server. Perform this step regularly to ensure that your in-house server hosts the latest updates. These steps are described in the next sections.
Adobe, the Adobe logo, Acrobat, Adobe Audition, Adobe Bridge, Adobe Device Central, Adobe OnLocation, Adobe Premiere, Adobe Premiere Pro, Adobe Technical Communication Suite, After Effects, Contribute, Captivate, Creative . Downloading updates from in-house update server on client machines running AAMEE 2.0 or later
Adobe Version Cue CS4 Adobe CreAtive Suite 4 deSign StAndArd Combines: Adobe InDesign CS4 Adobe Photoshop CS4 Adobe Illustrator CS4 Adobe Acrobat 9 Pro Plus Adobe Bridge CS4 Adobe Device Central CS4 Adobe Version Cue CS4 deSign
e Adobe Illustrator CHEAT SHEET. Direct Selection Tool (A) Lasso Tool (Q) Type Tool (T) Rectangle Tool (M) Pencil Tool (N) Eraser Tool (Shi E) Scale Tool (S) Free Transform Tool (E) Perspective Grid Tool (Shi P) Gradient Tool (G) Blend Tool (W) Column Graph Tool (J) Slice Tool (Shi K) Zoom Tool (Z) Stroke Color
Adobe Analytics tool for Alteryx Designer (Optional) The Adobe Analytics tool authenticates to the Adobe Analytics report suites (to which you have access) and generates ad hoc reports based on multiple parameters via the Adobe Analytics Reporting API. 1. Go to the Adobe Analytics Tool listi
ADPH48.0051 Adobe Certified Associate (ACA): Adobe Photoshop ADIN48.0175 Adobe Certified Associate (ACA): Adobe InDesign ADST48.0176 Adobe Certified Associate (ACA): Adobe Illustrator BRVP10.0011 Television Video Production Skill Connect BRVP10.0012 NOCTI Television Production BRVP10.0013 Adobe Certified Associate (ACA): Adobe Premiere Pro
Lo spazio di lavoro di Adobe Media Encoder Adobe Media Encoder è il motore di codifica per Adobe Premiere Pro, Adobe After Effects e Adobe Prelude. Potete inoltre utilizzare Adobe Media Encoder come strumento di codifica autonomo. Per una panoramica di tutte le funzioni disponibili in Adobe Media Encoder, guardate questo video di Jan Ozer.
Adobe Premiere Pro CC Learn by Video (2014 release) Digital Video with Adobe Creative Cloud Classroom in a Book Adobe After Effects CC Classroom in a Book (2014 release) Adobe Photoshop CC Classroom in a Book (2014 release) Adobe Premiere Pro Studio Techniques An Editor's Guide to Adobe Premiere Pro (Second Edition) Module 1: Touring Adobe .
The asynchronous design use the “web hooks” approach using two independent "one-way" invocations - one to start a long-running operation (Client to ESC) and the other one to notify a requester that it is completed (ESC to client) ESC REST API Headers/Path/Body Parameters Callbacks. One of the header parameters of the operation request will contain a callback field, whose value is a URI .
