Client installation

The Lime CRM desktop client is distributed as a single installer application named limepro-<version>.exe.

The installer will dynamically download and install dependencies, such as .Net Framework, MSVCRT and WebView2. See sections on External Dependencies and Common Issues below for hints how to prepare for trouble-free installation or upgrade.

To install Lime CRM, simply launch the installer and follow the instructions. The installation requires administrator privileges.

By passing command-line switches to the installer application it is possible to automate the installation in different ways. The following switches are available:

In addition to command-line switches the installer application accepts a number of property and value combinations that can be passed on the command-line after the switches mentioned above.

Executing the following will install the Lime CRM client in passive mode and use Swedish as the default language:

limepro-xxyyzz.exe /install /passive LIMELANGUAGE=sv

The Lime CRM Desktop client is automatically kept up to date. Auto update is enabled by default in version 10.16 and up. Our recommendation is to use auto updates to make sure the Desktop client remains secure and as performant as possible.

If there are circumstances where auto updates are not suited or possible, it can be locked to certain versions or completely turned off.

Locking the Lime CRM Desktop client to a specific version is supported for Lime CRM 11.x.1592 and later. This is achieved by configuring the Lime CRM servers application configuration as:

config:
    features:
      recommendedDesktopVersion: <version>

This setting can be used to limit the organisation to a specific version. When a new version should be rolled out the setting can be updated to the new wanted version.

The application configuration is supported for backend versions since May 2021. For existing backend installations the same feature can be enabled using database-level setting:

DELETE FROM [dbo].[setting] WHERE [name] = 'features.recommendedDesktopVersion'
INSERT INTO [dbo].[setting]
           ([type]
           ,[name]
           ,[datatype]
           ,[value]
           )
     VALUES
           (1
           ,'features.recommendedDesktopVersion'
           ,8
           ,'"11.1.2194"')

Update channel is configured via a special option field in the coworker record. The field must be called updatechannel.

This setting can be used to select adoption rate for new releases per user or solution. The setting is supported by all current releases of Lime CRM Desktop. The field can be hidden and locked via SQL to enforce single channel for all users.

Valid values are:

• rc - Release candidate, more frequent updates and early access to features and fixes. Updated when new build are available for external usage.
• stable - Default (general recommendation). Updated approx 4 times per year.
• mature - Less updates, longer delay for features and fixes due to extended validation process. Generally releases on stable will be promoted to mature after 4-6 weeks.

The stable channel is strongly recommended for cloud (*.lime-crm.com).

Generally the mature channel is recommended for institutional and complex self-hosted setups. For long-term stability this configuration should be coupled with internal verification of coming updates using Lime CRM Desktop (Insider) or rc- and stable- channels.

Strongly consider alternative options listed above before choosing this alternative. Completely disabling the automatic updates will require you to manually handle any and all future upgrades, including security related patches.

Auto updates can be completely disabled on the client side using the following methods.

1. Disable the auto updater addin using the installer, see above.
2. Disable the auto updater after installation using the registry.
3. Disable the Lundalogik Maintenance Service using the registry (not recommended).

Notes:

1. in the following a\b\key\@value syntax is used for registry entries.
2. on 32-bit machines omit WOW6432Node from registry keys.

To disable the auto update addin:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lundalogik\Lime\InstalledAddins\LimeAutoUpdate.Addin]
"LoadBehavior"=dword:00000000
"Mandatory"=dword:00000001

1. Stop the addin from loading (current user): HKEY_CURRENT_USER\Software\Lundalogik\Lime\Addins\LimeAutoUpdate.Addin\@LoadBehavior should be set to 0 (DWORD)
2. Stop the addin from loading (all user): HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lundalogik\Lime\Addins\LimeAutoUpdate.Addin\@LoadBehavior should be set to 0 (DWORD) and HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lundalogik\Lime\Addins\LimeAutoUpdate.Addin\@Mandatory should be set to 1 (DWORD)
3. Load the addin but disable it (all users): HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lundalogik\Lime\AutoUpdate\@Disabled set to 1

To disable the maintenance service (not recommended):

1. Disable the service from running, set HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lundalogik\Lime Maintenance Service\@Disabled to 1 (DWORD). This setting is also checked by the auto update addin.
2. Disable the service itself, e.g. by setting its startup type to disabled using services.msc or the registry. Note that this service only starts if an update is available and thus never runs (and consumes resources) otherwise!

The Lime CRM client can also be deployed through, for example, Active Directory or Microsoft SCCM. In these cases it is usually preferable to use Windows Installer packages (.msi) to install the application. The Lime CRM installer application (.exe) contains embedded .msi files that can be extracted and deployed. Extraction can be done by following these steps:

1. Download and install the WiX Toolset.
2. Open a command prompt and run the following command:

   <wix install dir>\bin\dark.exe -x c:\temp\limepro <full path to limepro-xxyyyzz.exe>

3. The extracted .msi files will be found in c:\temp\limepro\AttachedContainer

One of the extracted files will be LimeClientSetup.msi. This Windows Installer package accepts the same installer properties as the installer application. Note that the files must be deployed in the following order:

1. Vba71.msi
2. Vba71_1033.msi
3. LimeMaintenanceService.msi
4. LimeClientSetup.msi

The LimeMaintenanceService.msi installer installs the Windows service responsible for updating the client. This install is not required, however, strongly recommended. Not installing this will disable auto-updating of the Lime CRM client.

To install/uninstall/reinstall an .msi package manually, use msiexec.exe.

If you want to deploy the Lime CRM Client via Intune/Microsoft Endpoint Manager you can do it two different ways.

Install with the exe you provide. If you choose to go this route you provide the exe to the customer who then packages the app as an .intunewin-application using the Win32 content preptool and then publish the application in Intune/Microsoft Endpoint Manager as a win32-appplication. Note that this option is pretty limited when it comes to install-arguments.

Install the latest available exe with powershell/win32' Provide the customer with this powershell-script (LimeClient.ps1) and ask them to package the powershell-script as an .intunewin-application using the Win32 content preptool and then publish the application in Intune/Microsoft Endpoint Manager as a win32-appplication.

Stop-Transcript

$ErrorActionPreference = 'Stop'
$VerbosePreference = 'Continue'
$ProgressPreference = 'SilentlyContinue'

New-Item -ItemType Directory -Force -Path "C:\Automation\Logs" -ErrorAction Ignore
Start-Transcript -Path "C:\Automation\Logs\install-limecrm-desktop-stable-$(get-date -f yyyyMMddHHmmss).txt"

Write-Verbose "Download latest version"
$url = "https://builds.lundalogik.com/api/v1/builds/limecrm-desktop/versions/latest/file/"
$installer = "$env:temp\limecrm-desktop-stable-latest.exe"
Invoke-WebRequest -Uri $url -OutFile $installer -UseBasicParsing

Write-Verbose "Download complete, install"
$arguments = "/install /quiet /norestart /l c:\automation\logs\install-limecrm-desktop-stable-installer.txt"
Start-Process $installer -ArgumentList $arguments -Wait

Write-Verbose "Installation complete, delete installer"
Remove-Item $installer -ErrorAction Ignore

Write-Verbose "All done."

Stop-Transcript | Out-Null

Exit 0

Microsoft Endpoint Manager settings for Lime CRM Client as a win32-application

Install Command

c:\windows\sysnative\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy bypass -WindowStyle hidden -File .\install.ps1

Uninstall Command

powershell.exe

Detection Rule

Manually configure detection rules (Type: File) %ProgramFiles(x86)%\Lundalogik\Lime CRM

When installing the Lime CRM client in a multi-user environment, for example, Terminal Services/Remote Desktop Services/Citrix, make sure to log on as a user with administrator privileges and install Lime CRM through Control Panel | Add/Remove Programs.

Download and pre-install these dependencies for controlled environments or offline installation:

• .Net Framework
  • Minimum: .Net Framework 4.7.2
  • Recommended: .Net Framework 4.8
• MSVCRT
• Microsoft WebView2 Runtime
  • Use Evergreen Bootstrapper for online installation.
  • Use Evergreen Standalone Installer x86 for offline installation.

• Microsoft Windows
  • Ensure root certificates are updated, if not installation may fail due to problems with code signature validation. These links have been useful in similar situations:
    • https://serverfault.com/questions/973112/missing-root-certificates-on-windows-server-2016-fresh-install
    • http://woshub.com/updating-trusted-root-certificates-in-windows-10/
    • https://docs.microsoft.com/en-us/answers/questions/202270/how-to-enable-the-34automatic-root-certificates-up.html
  • Problems with WebView2 may be resolved by settingmsedgewebview.exe to run in compatibility mode for Windows 8 for all users.
• Citrix
  • Ensure msedgewebview.exe is excluded for Citrix API hooks https://support.citrix.com/article/CTX107825, ie add process name to HKLM\SYSTEM\CurrentControlSet\Services\CtxUvi\UviProcessExcludes. Exact settings may vary depending on XenApp-version, see linked document for additional details.