The Exchange Connectors monitors subscribed users, and notifies Totalview when changes happen in a user’s appointments list. The connector also sends create, update and delete commands from Totalview to the Exchange server.
Exchange365 Connector Connection Parameters
An App registration must be made in Azure for the customer’s tenant. See the Exchange security settings guide for more information.
| Tenant id |
The Azure App Registration tenant id |
| Client id |
The Azure App Registration client id |
| Secret | The Azure App Registration secret |
The App registration must have assigned the following permissions on Graph API:
- Calendar.Read
- Calendar.Write
- User.Read
- Mail.Send
Email Settings
| Sender from-address |
The e-mail account used to emails by Exchange365 connector |
Exchange Online Connector Connection Parameters using OAuth2 authentication (Deprecated)
Using OAuth2 authentication with Exchange Online, reqires an App Registration being created in Azure, with permission to use the EWS Legacy API (full permission).
See the Exchange security settings guide for more information.
| Tenant id |
The App Registration tenant id |
| Client id |
The App Registration client id |
| Secret | The App Registration Secret |
| Test user | An user existing in Exchange Online. The user is used to test that the connection with Exchange Online is successful. Format of test user is name@domain.com. The test user will also be used as the send user when sending mail using the Exchange Online connector |
On-premise Exchange or Exchange Online Connector using basic authentication (Deprecated)
The Exchange connector uses EWS to query information from the user’s calendar folder. To be able to query the user, a user must be created with rights to query user’s calendars. See the Exchange security settings guide for more information.
If running the Exchange connector with the service credentials, it is necessary to use the service manager to enable the service to run under the Totalview service user. A description of creating the Totalview service user is specified in the Exchange security guide.
| URI (using EWS) |
http:// <server name>/. This is the URL/URI to the Exchange server where the Exchange web service request will be sent |
| URI (using Exchange Online) |
When using Exchange Online no server URI is provided. The server is found based on the username, e.g. name@domain.onmicrosoft.com |
| Username |
Query user with access to all the attached users’ calendars.
N.B. When using service credentials, username should be left blank. The use of service credentials is listed in the Totalview Exchange security guide. Service credentials cannot be used when connecting to Exchange Online |
| Password |
Password for user with access to all calendars.
N.B When connecting to Exchange Online the password must not contain any of the reserved XML characters. The five reserved characters are < (less than), & (ampersand), > (greater than), ” (quotation) and ‘ (apostrophe). N.B. When using service credentials, password should be left blank |
| Scrambled |
The password can be saved scrambled in the Totalview server. Set the checkmark if the password is scrambled. Use the program “Totalview Password Scrambler” located in the InstallFiles folder to scramble the passwords. |
| Domain |
The query user domain. Used when authentication the query user on the Exchange. The domain should be the NetBIOS name or the fully qualified domain name (FQDN). Domain is not set when using Exchange Online |
| Use FBA |
Set the checkmark if Form Based Authentication is used when connecting to the Exchange server. Use FBA is not set when using Exchange Online |
Synchronization settings
| Recurring days ahead | How many days forward, should recurring appointments from Exchange be shown in Totalview. This is necessary to be able to limit the number of recurring appointments retrieved from Exchange |
| Busy template |
Select the template to use for Busy Exchange appointments. Appointments with state Busy in Exchange are mapped to this template when retrieved and shown in Totalview. If the Busy template is changed, the Exchange connector must be restarted to apply the new template |
| Out of office template |
Select the template to use for Out of Office Exchange appointment. Appointments with state Out of Office in Exchange are mapped to this template when retrieved and shown in Totalview. If the Out of Office template is changed, the Exchange connector must be restarted to apply the new Template |
| Tentative | Select the template to use for Tentative Exchange appointment. Appointments with state Tentative in Exchange are mapped to this template when retrieved and shown in Totalview. If the template is changed, the Exchange connector must be restarted to apply the new template. If no template is selected the Tentative appointments are not show in Totalview. |
| Working elsewhere | Select the template to use for Working Elsewhere Exchange appointment. Appointments with state Working Elsewhere in Exchange are mapped to this template when retrieved and shown in Totalview. If the template is changed, the Exchange connector must be restarted to apply the new template. If no template is selected the Tentative appointments are not show in Totalview. Working Elsewhere is supported in Exchange 2013 and newer. |
| Synchronize current | If enabled then Change state (current state/F5 in the client) settings are synchronized with the Exchange calendar. See the synchronization rules in section: The Totalview server synchronization rules in the Totalview Calendar Technical guide. |
| Valid until end
|
Is used with Fallback appointments (See: Promoting appointments with fallback for more information) |
| Exchange version (Deprecated) |
Specify exchange version (Not defined, Exchange 2007, Exchange 2007 SP1, Exchange 2010, Exchange 2010 SP1, Exchange 2013, Exchange 2013 SP1). This only applies to ExchangeEWS |
| Ignore char | When synchronizing, appointments with subject starting with the ignore char are ignored and not shown in Totalview. The default value is *. If the char is changed, the Exchange connector must be restarted to apply the new rule. |