How to set up coexistence

Pronestor supports a setup where the meeting rooms exsist in both Pronester and in Outlook. This setup is called coexistence since the meeting rooms coexist in both places.

Some features of Pronestor are disabled in the coexistence solution.

Coexistance can either be on-premise or in the cloud hosted by Pronestor. The syncronizations module is installed by default for cloud clients, but needs to be handled by you if you are an on-premise client.



  • All users that have access to book an Exchange resource must have an account in the Pronestor solution.
  • All users that have access to book an Exchange resource must have an Exchange account in the same Exchange environment as the Exchange resources
  • Pronestor must be able to follow all actions in the users’ Exchange account as well as the Exchange resources’ accounts
  • Exchange service account with application impersonation permissions on users including other settings - please see this guide on how to set it up

  • Exchange service account must have a mailbox and the primary email address for that account must be the original one and not an alias.
  • The Exchange service account must be dedicated the Pronestor solution and not a shared service account for other services as well.
  • AutoDiscover on Exchange must be reachable from Pronestor - here are some guides on setting it up:
    In general regarding AutoDiscover:
    How to test/validate:

  • Its highly recommended that the Exchange service account is set without a password expiration date.
  • One and same Exchange server end-point must be able to resolve all users, rooms and their calendars via the Exchange Web Service set up in Pronestor. It can be found in the administration settings under the tab Settings.
  • Server  must have the feature "Message Queuing Server" enabled.
  • Syncronization module be installed on the same web server as the Pronestor web site. This is already setup for cloud clients.
  • All rooms and users within Pronestor - must have their primary smtp set to the original and not an alias.
  • Any user that can book Exchange resources must have a Pronestor user account.
  • No contraints must exist for the rooms in Exchange, since these are controlled by Pronestor.
  • Exchange Web Services must be reachable from Pronestor

Overall installation/configuration process

  • Install and configure Sync Module has as a service (see section below)
  • Enable Coexistence and connect to Exchange Room Resources  (see section below)


Installing and Configuring the Sync Module

onpremise.PNG- This section is only relevant for onpremise installation.
When in
cloud, Pronestor will perform this in the cloud environment

Pronestor Room has to be configured to be aware that synchronization is enabled. 

Install the syncronization module

  1. Download the from Pronestor's download site
  2. Unzip in c:\program files\pronestor aps\sync
  3. With Notepad open "ExchangeBookingSyncService.exe.config"
  4. Set the dbConnectionString
  5. Set dryRun to "true" for testing, or set to "false" for alive sync
  6. Save and Exit

In the Administration interface in Pronestor Room:
Set the Exchange Web Services with the credentials for your Exchange Web Services (using the service account above).

You can start by running the Sync Module in a console to ensure that the module has been properly configured before installing it as a Service.

Install as a Service

onpremise.PNG- This section is only relevant for onpremise installation.
When in
cloud, Pronestor will perform this in the cloud environment.

  1. Open a command prompt
  2. Navigate to the "Sync" folder
  3. Type "ExchangeBookingSyncService.exe install" (if installing multiple service instances, use -i [optionalservicename] to name the specific instance name - ex. ExchangeBookingSyncService install -instance:SyncServiceXYZ)
  4. Once installed - open "Services.msc"
  5. Open the "ExchangeBookingSyncService
  6. Set
    • "Log on"-tab, use an account with local administrative permissions
  7. Go to "General" and click "Start"

For any issues - please check log.txt or check event viewer 


With coexistence Pronestor Room and MS Exchange are synchronized and room resources are shared. You keep all resources on your Exchange server and create the same resources in Pronestor Room. All bookings of meeting rooms done in Outlook/MS Exchange will be reflected in Pronestor Room and vice versa.

Configure Pronestor Room

onpremise.PNG- This section is only relevant for onpremise installation.
When in 
cloud, Pronestor will perform this in the cloud environment

  • Open "appSettings.config" within the configuation folder of Pronestor 
  • Ensure that the key "ExchangeIntegrationMode" is set to "Coexistence".
    i.e. <add key="ExchangeIntegrationMode" value="Coexistence"/>
  • If you have changed this value - you must recycle the app pool

Please note that using Pronestor Room with Co-Existence requires spedific setting on the Exchange resources. These settings can be seen in the document attached here. 


Administration Configuration Guide - Step by Step

  1. With Pronestor Planner open, go to Administration --> Settings --> Exchange integration. Input relevant Microsoft Exchange information (URL, Username, Password and/or Domain) and select the Username of the fallback user*.
  2. Click Save and test connection. Confirm that Exchange Web Services status is OK and that Synchronization service status is Online.
  3. Go to Administration --> Settings --> Other settings --> Attendees. Set a regex which encompasses email domains that are to be considered for internal (as opposed to external) attendees. Example:| would grant all attendees with those two email domains internal status for meetings. IMPORTANT: This step should be carried out before importing rooms and their respective calendars.
  4. Go to Administration --> Resources. Click New resource.
  5. For Exchange rooms that need to be coexisted in Pronestor, click Yes. Else, click No. 
  6. Input the Exchange email of the room resource and check/uncheck "Only import future bookings" depending on your preference**.
  7. Click Validate and set up the remaining settings for the room. Click Save.
  8. Repeat step 5 through 7 for each room resource.
  9. When a room is imported it takes some time (depends on the amount of meetings that needs to be loaded) for Pronestor to import all the meetings in the room's calendar. To the left of the room resource name a status icon will be displayed.
  10. There are the following states:
    • cloud-download.png Room calendar is currently being imported
    • cloud-checked.png Room calendar has been succesfully imported
    • cloud-sync.png Pronestor is currently synchronizing with the Exchange calendar
    • cloud-unavailable.png Connection to the Exchange server has been lost. Troubleshoot by verifying that the Exchange server is up and running and, subsequently, that the Microsoft Exchange information in Administration --> Settings --> Exchange integration is correct.
    • cloud-error.png Pronestor has received an error message from Exchange. Pronestor will try to recover from this state.
  11. When the room calendar has been succesfully imported, remember to Activate the resource in the right side of the respective row.

* If a user that is not registered in Pronestor books a coexisted room resource, Pronestor will assign the fallback user as the meeting owner.

** For room resources with a long history, we recommend to only import future bookings.

Disabling Pronestor email notifications, to avoid double notifications

In coexistence you get notifications from both Pronestor and Outlook. This is annoying. You can disable the Pronester notifications either through a feature toggle or by running this script on the sql database:

update appuser set enable_mail = 0


If some users need notifications it's possible to enable them specifically. First you run the previous script to disable everyone. Then you run this script to enable specific users

update appuser set enable_mail = 1 where email = 'users email addresse'


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk