AEM Desktop App Release Notes

You are reading the AEM 6.3 version of AEM Desktop App Release Notes.
This documentation is also available for the following versions:  AEM 6.2 

Release Information

Products Adobe Experience Manager (AEM) Desktop App
Version

1.5 (1.5.1.5 on Mac OS X; 1.5.0.3 on Windows)

Type Minor Release
Date

May 31, 2017 (1.5.0.x for Mac OS X and Windowss)

June 23, 2017 (1.5.1.5 for Mac OS X)

Download URL https://helpx.adobe.com/experience-manager/kb/download-companion-app.html
Compatibility (*)

AEM 6.3

AEM 6.2 SP1 (with Hot Fix 11099 applied)

AEM 6.1 SP2 (with Feature Pack 6658 and Hot Fix 8723 applied)

Adobe Experience Manager (AEM) Desktop App 1.5 focuses on application stability and resilience against various networking problems, better supportability, and customer-reported issues.

This release extends and replaces the previous versions of the Experience Manager Desktop App, which provided the following key enhancements: 

  • Version 1.4: the ability to upload hierarchical folders in the background with the progress monitoring. 
  • Version 1.3: performance enhancements and stability of accessing files and saving changes to AEM, especially from Creative Cloud desktop applications, such as InDesign, Illustrator, or Photoshop. It aimed to provide users with a more local desktop-like experience when working with files, while simultaneously handling network data transfer operations in the background.

Note

Compatibility (*) - Availability of buttons in Touch UI for new Desktop App 1.4 features - Folder Upload, Edit action - is as follows as of February 28, 2017:

  • AEM 6.3 - available
  • AEM 6.2 SP1, AEM 6.1 SP2 with respective packages: updated packages expected to be available soon

When new buttons will become available for AEM 6.1 and 6.2 as packages, this note will be removed.

Note

Want to start quickly?

  • Install the required server-side components on your AEM server (see Installation for details)
  • Download the AEM Desktop App binary from download page and install on your local machine

 

What's included in AEM Desktop App 1.5

Version 1.5.1.5 for Mac OS X:

The 1.5.1.5 release provides the following benefits:

  • New features and enhancements:
    • Add Copy/Paste functionality to Finder integration to allow for direct transfer from Desktop to AEM (CQ-4208158)
  • Bugfixes:
    • Fixed error 43 issue that occurred sometimes during asset renaming (CQ-4207900)
    • Reverting to an older version from the timeline in AEM does not update the asset in Finder (CQ-4205194)    
    • Desktop App crashes when browsing large nested directories (CQ-4208539)
    • Desktop App mount point is now /Volumes/DAM so it’s consistent for all users (CQ-4208159)
    • Placing file into InDesign for the first time initiates an update warning (CQ-4207454)

Note on Link Warnings

Creative Cloud applications (such as InDesign) take a "snapshot" of the item's last-modified time at the time it is placed. If that date changes at a later point, the CC app will report that the links are out-of-date. This is reported in a couple of ways:

  • When the CC app is launched, it will display a dialog informing the user that the linked assets are out of date, and prompt the user to take action
  • If the CC app is already running, it will show a yellow triangle warning icon on the linked asset

This behavior is the same for assets on local disk and assets in an AEM Desktop mounted directory, with the following exceptions:

  • If a placed asset is modified by a different user, then the warning icon will show up the first time that other users open a document containing the placed asset. This will only happen if the placed asset has already been locally cached
  • If a user modifies a placed asset through AEM desktop's mounted directory and then clears their local cache, then the placed asset will be reported as out-of-date

Both of these cases are expected and are side effects of the "delayed sync" architecture of AEM Desktop. 

Version 1.5.0.x for Mac OS X and Windows:

This release of AEM Desktop App provides the following benefits:

  • Better stability & resilience against networking issues
    • More stable mapping of AEM Assets folders (CQ-103276, CQ-4204669, CQ-4203957)
    • Better handling of cached files (CQ-4204336, CQ-4206263)
    • Improved handling of downloading/uploading of large files >2GB (CQ-4206438)
    • Fixed "Error 36" when moving or renaming a larger number of files in Finder (CQ-4204640)
  • Optimizations in network communication with AEM Server (CQ-4204974, CQ-100903)
  • Improved reliability of opening, placing, and saving AEM assets in Creative Cloud apps (CQ-4203968, CQ-4205511, CQ-103543, CQ-4207141, CQ-90980)
  • Improved supportability: option to clear cache (CQ-4202541), easy access to logs (CQ-4202340, CQ-4204673)
  • Other fixes
    • Better support for assets & folders having Japanese characters in name / non-English language settings (CQ-4195433, CQ-4205793, CQ-4199446)
    • Better handling of login with SSL (CQ-4200217)
    • More reliable share mounting (CQ-4200793)
    • Various improvements in stability (CQ-4207539, CQ-4200378)
    • Better handling of AEM Assets URL in Preferences (CQ-97388)

Enhancements Available Since AEM Desktop App 1.4

  • Simplified upload of hierarchical folders through the new Create > Upload Folder action in Touch UI
    • Action initiates a folder upload operation carried out by the Desktop App
    • Desktop app traverses the given folder hierarchy on desktop in the background and uploads the files to AEM Assets
    • User can monitor progress in the new Upload Queue Status window with progress bar for ongoing operations
    • The Upload Queue Status also provides better troubleshooting information (e.g., no connection to  server)
  • New Edit action in Touch UI, that combines Check out and Open operations into one
  • Optimized grouping of desktop-related actions in Touch UI (AEM 6.3)
  • Improved compatibility with the latest OS releases
  • Customer reported fixes

Enhancements Available Since AEM Desktop App 1.3

  • Increased efficiency. Users spend less time waiting for network operations to complete.
  • Improved Finder integration, which provides more stability and access to features, such as thumbnails.
  • Caching and performance improvements.
  • Better support for saving directly from desktop apps (PS, ID, AI, and so on).
  • Improved integration with Mac OS (local network drive protocol changed from WebDAV to more stable SMB1)
  • Desktop app connects with the AEM server using AEM native HTTP RESTful protocol
  • Files are saved locally first and then uploaded back to AEM in the background after a predefined time (30 sec). This reduces the time to save files.
  • Better handling of desktop applications that use intermediate file operations to save a file (partial saves and temporary files), which enables the AEM Asset timeline to display correct version and asset upload information.
  • Dialog provided to track the status of background upload tasks.

List of changes

Mount Point on Mac

Since MacOS 10.12 (Sierra), Apple has changed the permissions on the /Volumes folder used to mount network drives and devices to more restrictive. Creating a new mount point there required administrative rights. This issue was fixed in MacOS 10.12.5. 

As AEM Desktop App should run for users who do not have admin rights on the local machine, the mount point for AEM Assets repository was changed in 1.4 and 1.5 to a DAM subfolder in user's local folder on MacOS (CQ-104183).

Since the /Volumes folder no longer requires administrative rights, this change was reverted in 1.5.1. This also makes it possible to share InDesign documents that have placed AEM assets between MacOS users. 

Protocol change (Since 1.3)

  • Mac OS X
    • The local network drive protocol for OS X desktop integration changed to SMB1 from WebDAV.
    • The AEM repository mounted with Desktop App will be visible as an “smb” network drive in Finder, instead of a WebDAV drive.
  • Windows
    • The local network drive protocol for Windows desktop integrations stays; AEM will be mounted as a WebDAV share
  • For both platforms (Windows and Mac)
    • The protocol to access/download assets and to upload changes to AEM has been changed to the native AEM protocol, which is an HTTP-based RESTful protocol. It provides greater control over network operations and is more compatible with the network infrastructure.

Note

On Mac OS X: The change of local network drive protocol from WebDAV to SMB1 results in a different local path to the same asset in the repository. This might impact links to files placed in CC applications via "Place" command. See the documentation for more information.

File handling (since 1.3)

  • Folders are updated automatically after a predefined delay (currently 30s). 
  • Files checked out by other users are marked as read-only. 
  • Files are saved to a network drive location mounted via Desktop App in two phases.
  • In the first phase, a file is saved locally. This way, the user saving the file need not wait until the file is fully transferred to AEM, and can resume work as soon as the file is saved.
  • In the second phase, Desktop App uploads an updated file to AEM server after a predefined delay (for example, 30s). This operation occurs in the background. Use the Show Background File Sync Status option to view the status of the upload operation. 

Important Notices

It is recommended to use the new Folder Upload capability to upload larger, hierarchical folders into AEM as opposed to using a copy / drag and drop into a mounted AEM repository from Finder / Explorer level. When using the folder upload feature, Desktop App communicates with AEM directly and thus has much better control over the overall process.

Please note that AEM Desktop App doesn't support self-signed SSL certificates when connecting to AEM via a HTTPS secure connection. A CA-signed certificate is required on the server for such connections. (CQ-87941)

Known issues

  • An asset checked out by one user is not possible to open for another user, either by Open action from Touch UI, or directly on the desktop. Some applications might report it as locked, but also corrupted or even hang while trying to open. (CQ-4199234)

Workaround: When the asset is checked in again, it's available to other users.

  • Server URLs are required to point to the server without a path (e.g. http://server, https://server, http://server:port, or https://server:port). Context paths and sub-folders other than /content/dam are not supported. CQ-89343, CQ-87272
  • File and folder names with reserved characters are not properly handled. Make sure to use file and folder names that fit AEM requirements. CQ-93361, CQ-93308, CQ-89276
  • Checkin/Checkout
    • Changing files simultaneously by multiple users may cause some modifications to get lost. The workaround is to use the checkin/checkout functionality to prevent multiple users from changing the same file. CQ-97035
    • Certain applications don't support the read-only flag properly which allows a user to save a file that's checked out by another user. The modified file is not transferred until the other user checks in the file. Both modifications are available in AEM as different versions of the asset. CQ-89551, CQ-87572, CQ-89615
    • The checked-out and read-only status are reported independently in Finder. This results in 2 lock icons when a user checks out an asset. CQ-89507
  • Finder integration
    • Manual folder reload does not always work. The workaround is to wait 30s for the folder to be automatically updated. CQ-97389
    • More Asset Info... is limited to single file selections. CQ-89542, CQ-87656
    • Open in AEM Assets... is limited to single file and folder selections. CQ-83382
    • Assets with international names may appear and disappear every few seconds.  
  • Copy/Paste functionality
    • An error is reported in the Background Status Dialog when pasting an asset that already exists in AEM.
    • Paste is available when no asset has been copied to the clipboard
  • Windows
    • Files with Alternate Data Streams (ADS) are only fully supported on NTFS. Copying such files to the WebDAV share provided by the Desktop App will result in a caution dialog warning the user that the file has properties that can't be copied to the new location. This is usually fine since the properties are only relevant to a particular application on the user's desktop and have nothing to do with the actual file contents. CQ-103770

Installation instructions

Prerequisites

AEM Desktop App 1.4 is compatible with AEM 6.1 Service Pack 2 and AEM 6.2 Service Pack 1. If you are running AEM 6.1 or 6.2, ensure that you have installed the respective Service Pack before installing AEM Desktop App 1.4.

Installing server-side components

Depending upon the AEM version, install the appropriate server-side components. 

AEM 6.1:

Install the following:

AEM 6.2:

Install the following:

AEM 6.3:

No additional server-side components are required.

Installing AEM Desktop App 1.4 on local machine

For instructions, see Adobe Experience Manager Desktop App.

Helpful resources

Previous Releases

Release Information for AEM Desktop App 1.4 (Previous Release)

Products Adobe Experience Manager (AEM) Desktop App
Version

1.4 (1.4.0.1 on Mac OS X; 1.4.0.3 on Windows)

Type Minor Release
Date February 28, 2017
Download URL https://helpx.adobe.com/experience-manager/kb/download-companion-app.html
Compatibility (*)

AEM 6.3

AEM 6.2 SP1 (with Hot Fix 11099 applied)

AEM 6.1 SP2 (with Feature Pack 6658 and Hot Fix 8723 applied)

Release Information for AEM Desktop App 1.3 (Previous Release)

Products Adobe Experience Manager (AEM) Desktop App
Version

1.3 (1.3.1.17 on Mac OS X; 1.3.12 on Windows)

Superseded by AEM Desktop App Version 1.4

Type Minor Release
Date

September 16, 2016 (Mac OS X)

November 14, 2016 (Windows)

Download URL https://helpx.adobe.com/experience-manager/kb/download-companion-app.html
Compatibility

AEM 6.2 (with Hot Fix 11099 applied)

AEM 6.1 SP2 (with Feature Pack 6658 and Hot Fix 8723 applied)

Any questions?

Have a question about this or any other AEM topic? Ask our Community.
Learn more about AEM topics on our help hub.
Was this helpful?

By submitting your feedback, you accept the Adobe Terms of Use.

Thank you for submitting your feedback.