Introduction

This document describes the installation of Aurea CRM web and CRM.designer.

It provides a step by step introduction to the setup and the configuration of Aurea CRM web and CRM.designer, plus recommendations on performance and security issues as well as a troubleshooting section.

For details on Aurea CRM web and CRM.designer, see Aurea CRM web Administrator Guide.

The administration and configuration of core functions are described in the CRM.core Administrator Guide.

This manual assumes that you have a working Aurea CRM win installation and Aurea CRM database. For details, see Aurea CRM win Installation Guide.

All available documentation can be found on the Aurea CRM support page at https://support.aurea.com.

This document does not cover all possible aspects of running web applications in the Microsoft IIS environment, but attempts to provide you with links to important sources of information.

All screenshots in this manual apply to the BTB vertical.

Understanding Build and Version Numbers in CRM

CRM is a highly modular system. Each module is built and integrated into a package individually. To understand how the build version number relates to each packaged module, you have to understand the version numbering schema.

Version number is assigned based on the following schema:

Major_Version.Minor_Version.Patch_Version.Build_Version

As modules are built individually, Build version is relevant to an individual module only, but not to the whole product package. Particular Build version of a package can consist of modules with different Build versions.

All modules within single product package should always match only by Major, Minor and Patch version, same Build version across all modules in a package is not expected.