FAQs
Frequently asked questions for connector and connector SE.
Does connector SE replace connector for Exchange?
For the lifetime of the Aurea CRM product generation both connector and connector SE are available. "Classic" connector for Exchange is not part of the Aurea CRM product family.
How can I upgrade from connector to connector SE?
Since from a technical point of view connector SE is a separate product. Aurea CRM AG does not provide an upgrade procedure – switching to connector SE means de-installation of connector and (new) installation of connector SE.
Anyway, there is no need for re-installation of CRM.interface and most of the settings of connector can be imported into the configuration tool of connector SE.
Please see topic Excursus: migrating from "classic" connector to connector SE for further details.
What are the main differences between connector and connector SE?
From a technical point of view the main difference between the connector products is that connector SE uses EWS (Exchange Web Services) to access Microsoft Exchange Server, while connector uses MAPI. Additionally EWS is not supported by Microsoft® Exchange Server 2003 and thus consequently not supported by connector.
Regarding functionality the main difference between connector and connector SE is that connector SE supports the synchronization of recurring appointments created in Outlook, as well.
| connector | connectorSE | |
|---|---|---|
| Technology to access Exchange Server | MAPI/CDO | EWS (Exchange Web Services) – part of the Client Access server (CAS) role in Exchange 2010 and 2013 environments. |
| How does connector retrieve data? | Polling mailboxes. | Polling mailboxes and subscriptions. Connector SE currently does not use "push notifications". |
| Rights-Context |
"Full Access Permission" – though that does not mean that these permissions allow for creating/deleting mailboxes etc. Administrative account of connector must have full access to the mailboxes of the synchronization users – synchronization process runs in user context of administrative user. (Basically exactly the same concept, which is used by BlackBerry Enterprise Server, too). |
''Impersonation" Connector SE impersonates a given user account. This enables connector to perform operations by using the permissions that are associated with the impersonated account, instead of the permissions that are associated with the caller's account (and limited to these permissions). Can be defined for
|
| Where does connector live? | Must exist in the same domain or in a domain fully trusted with the domain, where Exchange Server lives. | May exist outside of Exchange Environment (not necessary that a connectorSE lives in the same or a fully trusted domainas Exchange Server). |
| Which Exchange Server versions are supported? |
Exchange 2003, Exchange 2007, Exchange 2010. |
Exchange 2013, Exchange 2010, Exchange 2007. |
Differences between connector and connectorSE
TLS 1.1 and 1.2 Support for Connector
Connector can communicate with Exchange Server and Aurea CRM over TLS 1.1 and 1.2 (Transport Layer Security) Protocols. Connector connections are managed by the .NET framework and TLS 1.1 or 1.2 protocols should be enabled by default by the underlying windows host to enable all outgoing secure channel connections to rely on TLS 1.1./1.2 protocols.