Client installation (Lime CRM Server 10.11 and earlier)

The Lime CRM client can be installed in three different ways, offering maximum flexibility:

  • Manual installation by launching the installer wrapper application
  • Automatic installation by publishing the installation through Windows Active Directory
  • Semi-automatic installation by running a customized script file.

A standard Lime CRM client installation without offline support is performed by launching installer.exe (installer64.exe on 64-bit Windows) and selecting the Install Lime CRM option.

Lime CRM can also be installed and configured to support working in offline mode where a connection to the server is only needed sporadically. To install the Lime CRM client with offline support choose the Install Lime CRM with offline support option when running the installer. Note that offline supports requires configuration on the server.

Publishing the installation through Active Directory and Group Policies is a good alternative if the application is to be installed in the same way to many computers in a network. The application will then be installed when the user next logs on to their workstation and administrator privileges are not required during the installation.

Using this method of installation requires good knowledge of Windows Installer packaging and it also recommended to always try the installation out in a test environment before publishing in production.

To create a script that can be used to install the Lime CRM client, run installer(64).exe and before starting the actual installation process press the Show button to display all commands that would need to be executed in order to install Lime CRM. These commands may then form the basis for a customized installation script.

When installing the Lime CRM client in a multi-user environment e.g. 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.

Outlook integration

In order to make the Outlook integration work correctly Lime CRM and Outlook have to run on the same server. If Lime CRM is to be run as a published application the host system must be configured so that Lime CRM and Outlook are started in the same session.

It is possible to customize the installation of Lime CRM through Windows Installer public properties. These installation properties can either be specified in installer.ini (when installing using installer(64).exe) or through parameters when you start the installation package via the command line. They can also be modified when packaging Lime CRM using a Windows Installer Transform (advanced usage).

Example

Install for all users and enable automatic login for server “lime01” with database “LIME CRM”

msiexec /qb /i "\\server\setup\Lime\Lundalogik Lime.msi" ALLUSERS=1 LIMESERVER=lime01 LIMEDATABASE="LIME CRM" LIMEAUTOLOGIN=1

Example

Install for all users with the “Application menu” addin enabled but without Limealyzer support.

msiexec /qb /i "\\server\setup\Lime\Lundalogik Lime.msi" ALLUSERS=1 LIMEADDINPROGRAMMENU=3 LIMEADDINLIMEALYZER=0 LIMEADDINLIMEALYZER1=0

Example

Install for all users with support for Lotus Notes on a workstation where Microsoft Outlook is installed but not used.

msiexec /qb /i "\\server\setup\Lime\Lundalogik Lime.msi" ALLUSERS=1 LIMEMSOUTLOOK=00

The following is a list of the installation properties that are specific to the installation package for Lime CRM:

Name Description Values
INSTALLDIR Installation directory Blank = Default installation directory is C:\Program\Lundalogik\Lime CRM (or equivalent).
LIMELANGUAGE The language code for the language that Lime CRM should run. sv = Swedish, en-us = English (Default), no = Norwegian, fi = Finnish, windows = Lime CRM will, if possible, choose the same language as Windows. If this language is not supported by Lime CRM Lime CRM will start with English as the language.
LIMESERVER The name of the Lime CRM Server to be used. If both LIMESERVER and LIMEDATABASE is set in an upgrade, these will be proposed in the login dialog even if you previously logged on with other login details. Blank = The user must self-specify the name of the Lime CRM Server on the network to be used in the login dialog at the initial startup of Lime CRM. (Default)
LIMEDATABASE The name of the database to be used. If both LIMESERVER and LIMEDATABASE is set in an upgrade, these will be proposed in the login dialog even if you previously logged on with other login details. Blank = The user must self-select the database on the specified Lime CRM Server in the login dialog at the initial startup of Lime CRM. (Default)
LIMEAUTOLOGIN If this property is set to 1 at the initial startup, Lime CRM will try to log in automatically with Windows integrated login. This property is relevant only with LIMESERVER and LIMEDATABASE. It also requires that the users of the Lime CRM database are configured for so-called integrated login to Windows. 0 = Show the login dialog at the startup of Lime CRM. (Default), 1 = Log in automatically.
LIMEPROTOCOL Specify which protocol Lime CRM should use as the default in communication to Lime CRM Server. 0 = DCOM (Default), 4 = HTTP, 8 = Net TCP, 16 = HTTPS
LIMEADDINADMINTOOLS Load behavior for the add-in Administrative tools (also known as Tangerine). 0 = Does not activate (Default), 3 = Activates at startup
LIMEADDINCALENDARNOTES Load behavior for the add-in calendar integration (Lotus Notes). This add-in will be installed only if Lotus Notes 6.5 or a later version is installed. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINCALENDAROUTLOOK Load behavior for the add-in calendar connection (Outlook)., This add-in will be installed only if Microsoft Outlook 2000 or, Microsoft Outlook XP is installed. 0 = Does not activate (Default), 3 = Activates at startup
LIMEADDINDOCFACTORY Load behavior for the add-in Document manager. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINDOCFACTORYOUTLOOK Load behavior for the add-in Document manager (Outlook). This, add-in will be installed only if Microsoft Outlook 2000 or, Microsoft Outlook XP is installed. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINDOCFACTORYPDF Load behavior for the add-in Document manager. (Pdf). 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINDOCFACTORYWORD Load behavior for the add-in Document manager (Word). This add-in will, be installed only if Microsoft Word 2000 or a later version is installed. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINEMAILGROUPWISE Load behavior for the add-in E-mail (GroupWise). This add-in will be, installed only if Novell GroupWise 6.5 or a later version is installed. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINEMAILNOTES Load behavior for the add-in E-mail (Lotus Notes). This add-in will be, installed only if Lotus Notes 6.5 or a later version is installed. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINEMAILOUTLOOK Load behavior for the add-in E-mail (Outlook). This add-in will, be installed only if Microsoft Outlook 2000 or Microsoft Outlook XP is, installed. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINLIMEALYZER Load behavior for the add-in Limealyzer 2.0. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINLIMEALYZER1 Load behavior for the add-in Limealyzer 1.0. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINMERGEEMAILGROUPWISE Load behavior for the add-in Mail merge, E-mail (GroupWise)., This add-in will be installed only if Novell GroupWise 6.5 or a later, version is installed. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINMERGEEMAILNOTES Load behavior for the add-in Mail merge, E-mail (Lotus Notes)., This add-in will be installed only if Lotus Notes 6.5 or a later, version is installed. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINMERGEEMAILOUTLOOK Load behavior for the add-in Mail merge, E-mail (Outlook)., This add-in will be installed only if Microsoft Outlook 2000 or Microsoft, Outlook XP is installed. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINMERGEFAX Load behavior for the add-in Mail merge, Fax (Windows). 0 = Does not activate (Default), 3 = Activates at startup
LIMEADDINMERGEWORD Load behavior for the add-in Mail merge, Bulk mail (Word). This add-in, will be installed only if Microsoft Word 2000 or a later version is, installed. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINOUTLOOK Load behavior for the add-in Integration with Outlook. This add-in, will be installed only if Microsoft Outlook 2003 or a later version is installed. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINPROGRAMMENU Load behavior for the add-in Application menu. 0 = Does not activate (Default), 3 = Activates at startup
LIMEADDINREPORTCALC Load behavior for the add-in Reports, Calculating reports. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINREPORTLABEL Load behavior for the add-in Reports, Labels. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINREPORTLIST Load behavior for the add-in Reports, Lists. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINREPORTSTANDARD Load behavior for the add-in Reports, Standard. 0 = Does not activate, 3 = Activates at startup (Default)
LIMEADDINTAPIDIALER Load behavior for the add-in Telephony dialer. This add-in requires, TAPI 3.0. 0 = Does not activate (Default), 3 = Activates at startup
LIMEDEBUG Specify the verbosity of the messages, which can be used for troubleshooting. 0 = Normal installation without, debugging messages. (Default), 1 = Display debug messages during, installation., 2 = Display more debug messages during, installation., 3 = Displays even more detailed debug, messages during installation.
LIMEGROUPWISE Determines how the add-in for Novell, GroupWise should be installed. Blank = Automatically determine if any, version of Novell GroupWise is installed (Default), 00 = Do not install add-in for GroupWise, 65 = Install add-in for GroupWise 6.5
LIMEMSOUTLOOK Determines how the add-in for Microsoft, Outlook should be installed. Blank = Automatically determine if any, version of Microsoft Outlook is installed (Default), 00 = Do not install add-in for Outlook, 09 = Install add-in for Outlook 2000, 10 = Install add-in for Outlook, XP, 11 = Install add-in for Outlook 2003, 12 = Install add-in for Outlook 2007, 14 = Install add-in for Outlook 2010
LIMEMSWORD Determines how the add-in for Microsoft, Word should be installed. Blank = Automatically determine if any, version of Microsoft Word is installed (Default), 00 = Do not install add-in for Word, 09 = Install add-in for Word 2000, 10 = Install add-in for Word XP, 11 = Install add-in for Word 2003, 12 = Install add-in for Word 2007, 14 = Install add-in for Word 2010
LIMEMSEXCEL Determines how the add-in for Microsoft, Excel should be installed. Blank = Automatically determine if any, version of Microsoft Excel is installed (Default), 00 = Do not install add-in for Excel, 09 = Install add-in for Excel 2000, 10 = Install add-in for Excel XP, 11 = Install add-in for Excel 2003, 12 = Install add-in for Excel 2007, 14 = Install add-in for Excel 2010
LIMENOTES Determines how the add-in for Lotus, Notes should be installed. Blank = Automatically determine if any, version of Lotus Notes is installed (Default), 00 = Do not install add-in for Notes, 65 = Install add-in for Notes 6.5

The installation package consists of a number of application features which are possible to choose from when running the installer (.msi package) manually and selecting to do a custom install. These features can either be specified in installer.ini or through parameters passed to Windows Installer in a script. They are typically passed as parameters to one of the standard Windows Installer properties ADDLOCAL, REMOVE, ADDSOURCE, ADDDEFAULT, REINSTALL or ADVERTISE.

Example

Standard installation for all users but without Limealyzer and Word support.

msiexec /qb /i "\\server\setup\Lime\Lundalogik Lime.msi" ALLUSERS=1 ADDLOCAL=ALL REMOVE=Limealyzer,Word

Example

Install only basic components, e.g. for use with LDE based integrations.

msiexec /qb /i "\\server\setup\Lime\Lundalogik Lime.msi" ALLUSERS=1 ADDLOCAL=ALL REMOVE=Application

The following features are available:

Name Description Default
Application Represents the Lime CRM application with its Start menu and desktop shortcuts. Installed locally.
AddIns Represents all addins. Installed locally.
DocumentFactory Contains addins for the generic template/document manager and the template manager for PDF files. These are used to create documents from templates with simple field codes. Installed locally.
FaxServer Contains the addin that supports sending of fax messages. Installed locally.
Limealyzer Contains the Limealyzer (both old and new version) addin. Installed locally.
Notes Contains the addin that enables Lotus Notes e-mail and calendar integration. Installed locally if Lotus Notes 6.5 or later is detected.
Outlook Contains the addin that enables Microsoft Outlook e-mail and calendar integration. Installed locally if Outlook 2003 or later is detected.
ProgMenu Contains the addin that enables the Application menu. Installed locally.
Reports Contains the addin that enables reports and label printing. Installed locally.
Tangerine Contains the administration addin. Installed locally.
Word Contains the addin that enables creation of Word document from templates and Word mail merges. Installed locally if Microsoft Word 2003 or later is detected.
Excel Contains the addin that enables editing of Excel documents. Installed locally if Excel 2003 or later is detected.
Tapi Contains the addin that enables click-to-call functionality for phone number fields. Requires a TAPI 3.0 driver installed. Installed locally.

Certain document templates that can be used with Lime CRM may contain macros that may need to be executed. Do check whether your Lime CRM system contains macro enabled templates. In order to run these macros the macro security level in Word may need to be adjusted:

Microsoft Word 2003: Open Word and select Macros | Security from the Tools menu. Make sure that one of the alternatives Medium or Low is selected and press OK.

Microsoft Word 2007 and later: Open Word and select the tab Developers. In the Code section click Macro Security and choose the correct level.

Your Lime CRM system may contain action pads and/or VBA guides that require that certain ActiveX components can be loaded. Do check whether your Lime CRM system contains these kind of components. In order to load these components the ActiveX security level may need to be adjusted:

In Windows Control Panel, select Internet Options and then select the tab Security. Select Local Intranet press the Customized level button.

The installer is known not to work as expected in these specific cases:

  • If Lime CRM Server is installed onto the same machine as the client and then uninstalled, the Lime CRM client installation must be repaired.
  • If Microsoft Outlook is installed but not configured at the time Lime CRM is installed Lime CRM may hang on startup. To solve this problem either configure Outlook by simply starting the application or remove the Outlook addin from the Lime CRM installation by going to Control Panel, Add/remove program, select Lundalogik Lime CRM in the list and choose to modify the installation. In organizations where another messaging system than Outlook is used but where Microsoft Office is installed the recommended method is to install Lime CRM with the installation property LIMEMSOUTLOOK set to 00.
  • If the installation is performed with a reduced user interface (silent or basic) the standard behavior in Windows Installer is to install the application for the current user only while the default behavior in other cases is to install the application for all users. This means that if you want to run the installation with a reduced user interface the installation property ALLUSERS must be set to 1.

If there are error messages displayed during the installation your best bet is to first search for the error code or message in the knowledge base found at the Lundalogik support web site. It can also help to re-run the installation with Windows Installer logging enabled.

Example

Attempt to install for all users with a detailed log file.

msiexec /qb /i "\\server\setup\Lime\Lundalogik Lime.msi" ALLUSERS=1 /l*v c:\limesetup.log

Another method of trying to establish what has gone wrong is to set the installation property LIMEDEBUG. The default value is 0 but setting this property a higher number (1, 2 or 3) more and more details are shown as message boxes as the installation progresses.

Example

Install for all users and show verbose messages.

msiexec /qb /i "\\server\setup\Lime\Lundalogik Lime.msi" ALLUSERS=1 LIMEDEBUG=1

Addins installed but not enabled

Sometimes it can appear that addins have not been installed when as a matter of fact the problem is that they have not been enabled in Lime CRM. So first verify that the addin in question is present in the list in Tools | Addins. It might be enough to enable the addin by selecting it in the list and checking Loaded/Unloaded and Load on Startup. If Lime CRM does not manage to enable the addin try to repair the installation through Control Panel | Add/remove Programs.

Addins not installed since preconditions not met

Sometimes an addin may fail to install even though the preconditions required for installation have been met. If for example Lime CRM has been installed before Microsoft Outlook the Outlook addin will not be installed with Lime CRM. This can easily be fixed by going to Control Panel | Add/remove Programs, selecting Lundalogik Lime CRM in the list and by then choosing to modify the installation. In the installer dialog that is displayed it will be possible to add support for E-mail (Outlook).

If however the Outlook addin is not present in the list of available addins even though Outlook is installed, one reason can be that the mechanism that tries to detect whether the preconditions for installation of the addin (e.g. Outlook version) have been met fails for some reason. A workaround for this type of problem is to force the installer to install support for a specific version of Outlook by setting the installation property LIMEMSOUTLOOK.

Example

Install Lime CRM for all users with support for Outlook 2007.

msiexec /qb /i "\\server\setup\Lime\Lundalogik Lime.msi" ALLUSERS=1 LIMEMSOUTLOOK=12
  • Last modified: 6 years ago
  • by Simon Jehrbo