Exchange On-premises Resource Central requirements

1. Application server system requirements

System requirements for Resource Central 4.3 - Add-On Products

Diagram:

2. Pre-installation steps

The configuration detailed in this section must be carried out before Resource Central SAAS can be installed.

SQL server

The SQL server must allow SQL authentication, and we need a login during installation that allows us to create the 2 databases. Once databases are created DB_Owner rights suffice.

Further requirements:

• “Full-Text and Semantic Extraction for Search” feature must be installed.
  Check with the following query:

Application server

We have the following requirements for the Windows Web server:

• .NET 4.8
• .NET 7 Webhosting bundle (download here)
• English language
• IIS and asp.net – see detailed list in box below:

Furthermore, these are strong recommendations:

• Assign a DNS A record (or a cname).
• We recommend using an SSL certificate for the website.
• Exclude services and folders as exemplified with Defender exclusions in box below:

Service account

We need a service account in the domain with the following:

• It requires a mailbox.
• Cannot be hidden in GAL.
• Must be member of “View only administrator” Exchange role. (Optional for use with permission visualization)
• Must be configured with “Application Impersonation Role” as described here:
  https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/how-to-configure-impersonation (From Microsoft)
  Steps to configure Application Impersonation rights in Exchange Servers (Our KB with some explanations) 
• Features that cannot be used when scope is applied to impersonation.
  Impact of impersonation rights on some Resource Central features - Add-On Products

Resource mailboxes

Resource mailboxes must be created for rooms and equipment that should be part of Resource Central, and we recommend that the following is prepared.

• Add all rooms intended for Resource Central to a distribution list for management purposes.
• Ensure that resource scheduling is correctly set up.
• We recommend that you take steps to preserve the subject of meetings.
  Below sample script does this for all resources in your organization:

• Use policies in Exchange to control who can book or request a room.
  https://docs.microsoft.com/en-us/powershell/module/exchange/mailboxes/set-calendarprocessing?view=exchange-ps

Firewall requirements

The Exchange connection method we use requires that traffic from Exchange EWS which is TCP port 10002 is allowed inbound through the firewall and subsequently NAT redirected to the server where Resource Central is running.

A complete list of all the communication ports we use with our Exchange connection tool (Realtime Service) can be found here (focus should be on push notification on port 10002 since the other inbound are used locally on the server):
Inbound and outbound RealTime Service (RTS) ports and needed IP addresses 

3. Post-installation steps

The points below cannot be implemented until the Resource Central environment is running.

Office add-in deployment

We always recommend implementing FQDN for the Resource Central web site to get a nice name for the users that will connect to the backend, but also to allow for easy replacement in case a server dies.

In this case where the Office add-in is a topic, the following is required for the Resource Central web site:

• Must have a FQDN.
• The site must have a valid SSL certificate.

Here is some additional information surrounding the Office add-in from our knowledgebase:

- User guide:
Resource Central - Outlook Add-In User Guide

- Implementation:
Resource Central - Outlook Add-in Installation Guide

Outlook COM add-in deployment

This is the full com Outlook add-in which must be deployed to the client computers.
User guide: Resource Central - User Guide 

We have several Knowledgebase articles on this subject, and you will find some basic information in the guide associated with the add-in:

- Installation guide:
Resource Central - COM Add-in 4.1 Installation Guide 

- Deployment guides:

How to deploy Add-in 4.1 using Command Line, PowerShell, or Windows Terminal using command line, PowerShell or Windows Terminal 

Deploy ResourceFinder as an WIN32 App with Endpoint Manager (INTUNE)

- Additional topics:
Alerts on Add-in produced by Outlook

External authentication - SSO

Resource Central supports several SSO methods, as described in these support articles: External Authentication Details for OpenID Connect in Azure 

Properties

Applies to: RC 4.3+

Reference: TFS #297975

Knowledge base ID: 0306

Last updated: Jun 02, 2023

Attachments (2)

pdf

RC_on-premis....pdf
275 KB

FUBn2UOLtN5B....jpeg
78.2 KB