• Create a virtual directory for this folder – ensure the authentication is set to “Anonymous”.

• Configure the log file path within the web.config file. Relative file paths work so an explicit path is no longer required.

• Configure the Database connection string – Can use fixed account or integrated security. SQL Authentication Windows Authentication

  • SQL Authentication
    

    <add name="RendezvousConnectionString" connectionString="Server=(ServerName);Database=(DatabaseName);User=(Username);Pwd=(Encrypted Password)=" providerName="System.Data.SqlClient" />

  • Windows Authentication
    

    <add name="RendezvousConnectionString" connectionString="(ServerName);Database=(DatabaseName);Persist Security Info=False;integrated security=SSPI;Trusted_Connection=Yes" />

• Edit the ExchangeEventSync Service Nfs.ExchangeEvent.Service.exe.config file and configure the following settings:

  • Log file path

    <file value="..\Log Folder\ExchCal Service\NFSExchCalSyncService.log" />

  • Exchange Event Sync API URL

    <add key="ExchangeEventSyc:WebApiUrl" value="https://servername/WorkspaceExchSyncAPI/" />

  • Webservice API URL

    <add key="QuickBook:WebApiUrl" value="https://servername/WorkspaceWebserviceAPI/"/>

  • Windows Service Name

    <add key="ServiceName" value="Korbyt Exchange Calendar Service - Workspace" />

  • Other App Settings to consider are listed below, mainly in the order that they were

    introduced in the application.

    • <add key="IsPastBookingAllowed" value="true" />

      (Consider importing or syncing past bookings created in Exchange. This key is now superseded by a newer key mentioned below called “AllowPastBookingForNoOfDays”.

      Note that if you create a past booking in Korbyt Booking, it will NOT sync to Exchange; therefore, it is recommended that BRE is set to not allow past bookings.)

    • <add key="MaxRecurrenceAllowed" value="99" />

      (The value for the above key should match the global setting value in the application. This is the maximum number of occurrences from Exchange that will get synced. Be aware and inform the client that if there are more than this number of occurrences in the series, they will not get synced to Korbyt

      Booking).

    • <add key="FromMail" value="DoNotReply@nfs.com" />

    • <add key="AlertMailTo" value="abc@test.com;xyz@test.com” />

      (The above two keys are used to configure the email addresses for the sender and recipient(s) for email alerts triggered by specific Exchange-related issues.

    • <add key=”WaitTimeForSubscriptionAlert” value=”30” />

      (When a room subscription expires, the system would generate an alert email if the expiration occurred, or the subscription was not done within the last 30 minutes. This setting allows administrators or users to receive timely notifications about expiring subscriptions and take appropriate actions)

    • <add key=”WaitTimeForTimerNotificationAlert” value=”60” />

      (If the "Active Exchange Timers" are not functioning correctly within the last configured minutes (ex. 60), the system will generate an alert email. This setting aims to provide timely notifications to administrators or users about a possible malfunction or specific timers not working as expected in the

      Exchange Service)

    • <add key=”EnableTimerNotificationAlert” value=”false” />

      (Set to true to receive alert emails about Active Exchange Timer not running. This configuration setting controls whether or not alert emails will be sent for the scenario when an Active Exchange Timer is not running)

    • <add key=”EnableSubscriptionAlert” value=”false” />

      (Set to true to receive alert emails about expired room subscriptions. The sender/recipient will be the

      addresses configured in the “FromMail” and AlertMailTo” addresses)

      <add key=”SubscriptionEmailSendAfterEveryMin” value=”480” />

      (When an alert email is initially sent for an expired room subscription related to a particular resource, the system will wait for 480 minutes (or 8 hours) before sending the next alert email for that same resource

      if the subscription remains expired. This setting helps to control the frequency of alert notifications and prevents excessive or unnecessary emails from being sent within a short period)

    • <add key=”TimerEmailSendAfterEveryMin” value=”480” />

      (By setting this timer to 480, it suggests that the system will wait for 480 minutes (or 8 hours) before

      triggering another alert email if the "Active Exchange Timers" continue to be non-functional. This interval allows for a grace period before sending subsequent notifications to avoid overwhelming administrators or users with frequent alerts)

    • <add key=”TimeIntervalCheckResourceStatusInExchange” value=”15” />

      (Whenever a booking is created, modified, or canceled from Webapp/Bookit with an Exchange resource, a timer within the system will trigger after the specified number of minutes configured in this setting.

      This timer initiates a process to fetch the updated ExchangeStatus of the bookingItem associated with the Exchange resource)

    • <add key=”SendDeclinedMail” value=”false” />

      (This setting controls whether or not declined emails will be sent for bookings that are created, modified, or cancelled from the Webapp or Bookit)

    • <add key=”StopExchangeService” value=”false” />

      (This configuration setting controls whether the Exchange Service should be stopped when incorrect Graph API credentials are detected)

    • <add key=”SendNetworkIssueAlertAfterMin” value=”720” />

      (The system will send a network issue alert based on the interval configured).

    • <add key=”OnDeclinedAllowBookingCancel” value=”true” />

      (This configuration setting determines whether declined bookings made through the Webapp or Bookit will be automatically cancelled).

    • <addKey=”ActiveExchangeTimerNames”value=”EWSRoomSubscriptions;GraphRoomSubscriptions;MastersTableProcessing;NonRecExchNotificationAppointmentSync;RecExchNotificationAppointmentSync;WorkspaceActionTBLBookingToExchange;ImportExchangeToWorkspaceUsingEWS;UpdateBookingExchangeReferenceNumber;Impor

      tExchangeToWorkspaceUsingGraph;CheckRoomSubscriptionsAlert;CheckWorkspaceResourceStatusInExchange;Office365AppointmentSync” />

      (This configuration setting specifies the names of the active Exchange timers that will run for the

      specified service. If there are multiple Exchange services configured across various servers, then it is

      possible to have various active timers managed across these distributed services. For example, the

      action table Exchange alerts gets processed by a different service to room subscriptions).

    • <add key=”ParallelThreadExchNotificationCount” value=”7” />

      (The default value for this setting is 7 and can be increased up to 14 if there are performance issues. It relates directly to one of the active timers [NonRecExchNotificationAppointmentSync] and enables

      faster concurrent processing of non-recurring notifications from Exchange)

    • <add key=”CancellationWaitTime” value=”0” /> <!—0 is default value→

      (This setting specifies the amount of time the service will wait before retrying the cancellation process for an appointment that was not found in Exchange. If this setting is not defined, its default value is 0,

      which means the booking will be cancelled immediately.

      If the “CancellationWaitTime” value is set to 1, the service will change the booking’s status from 0 to 14 and after the configured number of minutes (1 in this case), the status will change from 14 to 15. Then,

      after another configured time interval of minutes, the status will change from 15 to 2, indicating that the booking has been processed i.e.cancelled).

    • <add key=”AllowPastBookingForNoOfDays” value=”1” />

      (It will allow past bookings based on the value configured e.g. if it is set 2 then it will allow current date minus 2 bookings.This is independent of the ” IsPastBookingAllowed” key, which is now redundant)

  • Install the Window service using command prompt or the provided batch file – If using the batch file (Install.bat) please edit this first and provide the correct physical location path and “Run as Administrator”. Remember to start the service and set to automatically start with an account having local admin privileges.

    

Configuration Name - Must be a unique name to define the configuration settings.

Exchange Online – This is used to denote which type of Exchange is being used (On-premises or Online). It will also control the options available in the Authentication Type setting.

Authentication Type - There are two options available: Basic Authentication and OAuth. For on-premises Exchange, only basic authentication is available. For Online Exchange, only Graph is supported when using Exchange Rooms Sync. If not using Exchange rooms, but purely for calendar appointments, then OAuth may be used.

EWS Basic Authentication

When Basic Authentication is selected, the following fields will need to be completed:

1. Domain – The Exchange Domain being used e.g. Dev.korbyt.com

2. Username – The Username of an Exchange user – a service account with adequate permissions to write to all mailboxes.

3. Password – The Password of the same Exchange service account user

4. Version – The version of the Exchange server being used

The above screenshot was replaced on April 5th 2022, to include two new settings:

Default Email Id for Bookings created by non-Exchange users and Device User, which are explained in the General Settings section below.

Note: EWS Basic Authentication is not supported when using Exchange Online. This type of configuration is not recommended as Microsoft is no longer supporting it. In V8.x it has been disabled when Exchange Online is checked.

EWS OAuth

Only select this option when using Exchange for standard calendar appointments that are not linked to Exchange Resources.

General Settings for both Basic Authentication and OAuth

The settings below must be completed when using either Basic Authentication or OAuth:

• Exchange URL: The online or on-premises URL for the Exchange server.

• Subscription Time: A value is required. 240 minutes is recommended, but should not be less than 120 mins. Ensures that room subscriptions do not expire.

• Domain User Email Id: This can be left blank. It was previously required and needed to be an email address of an Exchange server account (could be a dummy user mailbox account that must exist in Exchange).

• Public Notification URL: The URL of the Exchange Sync API Service.

• Active: This checkbox is used to enable or disable the configuration settings.

• Default Email Id for Bookings created by non-Exchange users: An Exchange user mailbox Id is required, to be used as the organizer for bookings made using Exchange resources by a non-Exchange user. Non-Exchange users can be flagged as such in the user configuration.

• Version: Select « Exchange Service 2013 Service Pack 1 » as this is the minimum version.

• Device User: This can be any dummy user created in the system and is used as the host in book is created by a device or directly from the resource calendar. Create a user called « Device User » for this purpose and assign it here.

• Default Booking Type: The Korbyt Booking, Booking Type. Sets a type that all bookings created via Exchange will be given

• Default status if Resource is not available: The status that will be given to bookings in Korbyt Booking if they are not available in Korbyt Booking but are still created via Exchange, e.g. Waitlist.
  

  

Two authentication types are supported for graph

The settings below must be completed:

1. Client Id : Taken from the Azure App Registration of the same name.

2. Tenant Id : Taken from the Azure App Registration of the same name.

3. Client Secret : Taken from the Azure App Registration of the same name.

Client Secret Expiry Date:

Log a date that can be used to give enough notice for when the secret is due to expire. This is for information and for an alert to be generated to warn administrators of the imminent expiry. An email will be sent, first seven days before, then again two days before and finally on the day before the expiry date, to the email address configured in the Exchange Cal service config file:
<add key="AlertMailTo" value="ExchUser@nfstechgroup.com" /> The email sender will be based on <add key="FromMail" value="DoNotReply@nfs.com" />

Note: The expiry date must be at least one week from the current date.

Note: For certificate-based authentication instead of using a client secret, please refer to the document "Certificate-Based Authentication for Accessing MS Graph API" provided separately.

General Settings

The settings below must be completed:

• Domain User Email Id: This can be left blank. It was previously required and needed to be an email address of an Exchange server account (could be a dummy user mailbox account

  that must exist in Exchange).

• Subscription Time: A value is required and the recommended value is 240 mins. Ensures

  that room subscriptions do not expire, i.e. should auto renew within this set time.

• Default Email Id for Bookings created by non-Exchange users: An Exchange user mailbox Id is required, to be used as the organizer for bookings made using Exchange resources by a non-Exchange user. Non Exchange users can be flagged as such within the user

  configuration.

• Graph URL: By default this should be set to Global-Microsoft.com unless the client is using a different Microsoft cloud such as US Government.

• Public Notification URL: The URL of the Exchange Cal Sync API.

• Active: This checkbox is used to enable or disable the configuration settings.

• Device User: This can be any dummy user created in the system and is used as the host in

  bookings created by a device or directly from the resource calendar. Create a user called

  « Device User » for this purpose and assign here.

• Default Booking Type: The Korbyt Booking, Booking Type. Sets a type that all bookings created via Exchange will be given

• Default Status if resource is not available: The status that will be given to bookings in

  Korbyt Booking if they are not available in Korbyt Booking but are still created via Exchange.