Updating CRM.launcher

CRM.launcher periodically checks for updates on the server and informs the user if an update is available. A short summary of the found files is displayed and the user is and asked for confirmation. The user is also informed upfront about possible connectivity losses and advised about further actions before continuing with the update (e.g. a warning stating that open documents will have to be uploaded manually). Once all files are downloaded and the update has been successfully installed, CRM.launcher restarts itself and reconnects to Aurea CRM.Web.

CRM.launcher searches for new patches in the <GlobalPatchDirectory> on the server (default path: ..\web.data\GlobalPatchDirectory). The <GlobalPatchDirectory> is defined in the offline.xml file located at ..\system\settings.

*.zip files are unpacked in the root installation folder, executables are executed provided they meet the security guidelines: The <PatchingSettings> section in the update.launcher.exe.config file needs to be configured, and the files have to be signed with a valid certificate. For details, see the articles “CRM.Launcher 8.2 Feature Pack, self patching” and “How to Configure Patching Settings for CRM Launcher” at https://support.aurea.com.

Executables need to be placed in the root folder. They are executed with the location of update.launcher.exe as working directory. Executables in subfolders will not be executed.

Patches must comply with the following naming conventions:

• File names must start with "launcher_".
• To enable patching of different versions on the client, you can use the words "from", "to" and "any" in the file name.

CRM.launcher patches are processed in numeric order (i.e. starting with the lowest to_<version> number).

Examples: