Lime CRM server must be installed on the machine that will act as the Lime CRM application server. Lime CRM Server can either be installed to a dedicated server or to the same server that runs SQL Server (depending on expected load).

It is possible to run Lime CRM Server and its associated components in a virtualized environment. Lundalogik will happily provide you with detailed specifications regarding hardware in a dedicated/physical environment. The recommendations are based on the conditions for your Lime CRM system taking into consideration factors such as number of concurrent users, amount of data and overall usage. The recommended hardware specification is to be considered an absolute minimum if the machine is virtualized and Lundalogik cannot provide support if these requirements are not met.

For virtualization of Microsoft SQL Server and associated performance issues, please refer to Microsoft's recommendations.

Before installing Lime CRM Server the users and groups that are required for the system to work need to be created and configured with the privileges that each service needs according to the information below. It is recommended to create a domain service account and run all Lime CRM services needed as that account. If even finer control is required create one service account per service.

Lime CRM Server is a COM+ server application. The account running Lime CRM Server must have access to the SQL Server database where the Lime CRM database(s) are stored. The following permissions are needed in each database:

• Add and remove tables and columns
• Add, update and remove records in all tables
• Create, update and remove stored procedures and functions
• Create databases

Installing Lime CRM Server will open these ports in the firewall to allow access:

• 135 (TCP)
• 5463 (TCP)

All users that need to be able to access Lime CRM Server (i.e. users that need to be able to log on to Lime CRM) must be members of the local group Distributed COM Users. It is recommended to create two domain groups:

• Lime CRM Users. All users that should be able to log on to Lime CRM. Add this group as a member of Distributed COM Users. Typically a domain group.
• Lime CRM Admins. All users that should be able to administer Lime CRM using the Lime CRM Server Administration (LISA) interface. Can be either a local or domain group.

The user accounts and groups mentioned above need to be specified during installation of Lime CRM Server so they must have been created before launching the installation.

Used to enable offline support for Lime CRM. The user account running this service must have the following permissions:

• Listen to incoming network traffic on port 5461/tcp.
• Log on to Lime CRM, i.e. the user must be a member of the Distributed COM Users group on the machine running Lime CRM Server.
• SQL Server permissions according to do the following:
  • Create/remove/update records in all tables in the LIME database.
  • Execute stored procedures and functions in the LIME database.
  • Create global temporary tables.

Used to enable support for other protocols than DCOM, e.g. HTTPS. This service is always installed but not enabled by default. In case HTTPS is to be used a certificate must be installed on the server. The user account running this service must have the following permissions:

• Listen to incoming network traffic on port 443/tcp (in the case of HTTPS).
• Log on to Lime CRM, i.e. the user must be a member of the Distributed COM Users group on the machine running Lime CRM Server.

Used primarily for integration with other systems and applications. Needs to be installed and configured separately. The user account running this service must have the following permissions:

• Listen to incoming network traffic on all ports that are used in endpoint configurations.
• Log on to Lime CRM, i.e. the user must be a member of the Distributed COM Users group on the machine running Lime CRM Server.

Follow these steps to install Lime CRM Server and associated services:

1. Make sure that the machine is up to date with all Windows Updates.
2. Run installer64.exe in elevated mode (“run as administrator”). If Lime CRM Server is to be installed in an Active Directory environment, the user account launching the installation must have permissions to look up groups in the domain, i.e. the installation cannot be run under a local account.
3. Choose to install Lime CRM Server or Lime CRM Server with offline support if offline support is to be used.
4. Choose the Network installation option in a production environment. Local installation should only be used for test and development purposes.
5. Enter account details on the format DOMAIN\User for the user that should run Lime CRM Server. If Lime CRM Server 10.4 or later is already installed existing settings will be used. On Windows Server 2008 and later the account must be a dedicated service account and after installation it will no longer be possible to log on locally using the specified account.
6. Specify the name of the group that contains all users that should be able to log on to Lime CRM and the group that contains Lime CRM administrators.
7. Start the installation.

The following needs to be done in SQL Server to support Lime CRM:

1. Add the user account running Lime CRM Server as a user in SQL Server.
2. When using an existing database, restore the database backup and set the LIME Server user as owner of the database.

In case SQL Server is running on another machine than Lime CRM Server and there are not already any existing applications using SQL Server the following must also be done to open up for external traffic:

• Configure SQL Server to allow incoming external connections via TCP/IP. How this is done varies depending on SQL Server version.
• Configure any firewalls (e.g. Windows Firewall) to allow incoming connections on the SQL Server port (default 1433/tcp). Note that when using SQL Service instances other ports may be used.

On Windows Server 2008 Windows Installer may not always be able to handle the installation of the Lime CRM Server COM+ service. When logging is enabled the error message reads “A COM+ application could not be created from '…ldc.pak '…”. This problem is due to pending operating system updates that require a system restart. Reboot the server and run the installation again to solve the problem.