Complete Implementation Guide - Steelcase...

RoomWizard Exchange Connector

Complete Implementation Guide

ROOMWIZARD EXCHANGE CONNECTOR INSTALLATION GUIDE

Exchange Connector Installation

2

Before installing and configuring the Exchange Connector, you will need the following:

• Windows server with internet access on which to install the connector (details below)

• Connector package, downloaded and unzipped, on the desktop of the Web Server

• Local domain service account that can be used to log in to the Web Server and Exchange for PowerShell

• User account configured in Exchange that the connector will use to connect

to Exchange

• Resources with mailboxes for calendars (one for each RoomWizard)

Note: Newly created accounts and resources take some time to replicate throughout Exchange

• Full mailbox permissions between user account and each resource mailbox

• Exchange Web Services (EWS) URL for Resource Mailbox Calendar access

Connector will use Exchange’s autodiscovery to locate the EWS server

• For Microsoft’s Optimization Recommendations, see Appendix D

What is autodiscovery and how does it work?

Autodiscovery is a process that Microsoft supports for locating Exchange Web Services servers based

on an email address or domain. This is usually easier than specifying an EWS URL because most people

know an email address but not the name of a server. To test Exchange Web Services connections, you

can use Microsoft’s Test Connectivity Analyzer: testconnectivity.microsoft.com

What is Impersonation and how does it work?

Exchange Impersonation is a mechanism that allows a single Windows Active Directory account

(your RoomWizard Service account) to act on behalf of other users on a Microsoft Exchange mailbox

(your RoomWizard Resource Mailboxes), as if they were performing the action themselves.

This greatly reduces the number of connections counted against the service account. Too many connections

by any one account will result in Exchange throttling back access by that account through the EWS API.

See Appendix C for configuring Exchange and Impersonation. Also see our Impersonation White Paper

included in the software package for more information.

http://testconnectivity.microsoft.com/

3


System Requirements

• Server 2008, 2012 or 2016 (see Appendix B for details on installing on Server 2012 and 2016)

• Port 8080 open in Server firewall; this will be used when configuring the Connector Website

Server Manager

• .NET Framework 3.5.1 (Features), 4.0 and 4.5 (Programs/Features) microsoft.com/net

• ASP.NET (Application Development): Install via Server Manager, Web Server (IIS)

Role Services, Add Role Services

• Basic Authentication module (Security): Install via Server Manager, Web Server (IIS)

Role Services, Add Role Services

IIS (Internet Information Service)

• IIS 7 or IIS 8 (see Appendix B for details on installing on Server 2012 and 2016) iis.net

• Web Platform Installer in IIS (Installer only, to be used in later steps)

microsoft.com/web/downloads/platform.aspx

• Web Deploy (Web Deployment Tool) in IIS iis.net/download/webdeploy

http://microsoft.com/net/

http://www.iis.net/

http://www.iis.net/download/webdeploy

4


Configure Room Mailboxes

The Exchange Connector requires full user access to the room mailboxes managed by the

RoomWizard devices.

There are several ways that an administrator can provide full access to the RoomWizard service using

PowerShell. We have provided a script that can automatically grant full access to resource mailboxes.

However, if you choose to bypass the script, we have provided alternative PowerShell instructions.

Granting Access Using the PowerShell Script

1. Right-click GrantFullAccess.ps1 and select Run with PowerShell.

5

CONFIGURE ROOM MAILBOXES ROOMWIZARD EXCHANGE CONNECTOR INSTALLATION GUIDE

2. Enter Exchange PowerShell path and the service user’s ID (such as RoomWizard, room.wizard, etc.).

3. Enter the mailbox to configure or click Enter to choose a CSV file containing a new, line-delimited

list of room identifiers. The CSV file should contain a header named rooms.

6


4. Next, enter a username and password. These credentials are used to log in to your Exchange account

and create a PowerShell session.

5. Completing these steps will establish a remote PowerShell session with Outlook and grant the

given user full access to the rooms specified in the CSV.

7


Granting Application Impersonation Role Manually via PowerShell

This section provides the necessary commands to configure a service user that has the Application Impersonation

role. To proceed, a working knowledge of PowerShell is recommended.

The following command is used to grant the Application Impersonation role:

New-ManagementRoleAssignment –Name:impersonationAssignmentName –Role:ApplicationImpersonation

–User: <Service User>

For example: New-ManagementRoleAssignment –Name:impersonationAssignmentName –

Role:ApplicationImpersonation –User: “[email protected]”

The following command checks if a user has the Application Impersonation role:

Get-ManagementRoleAssignment -RoleAssignee <Service User> -Role ApplicationImpersonation

-RoleAssigneeType user

For example: Get-ManagementRoleAssignment -RoleAssignee “[email protected]”

-Role ApplicationImpersonation -RoleAssigneeType user

Reference: https://msdn.microsoft.com/en-us/library/office/bb204095(v=exchg.140).aspx

Configuring Room Mailbox

By default, a room does not auto-accept invitations. In order for the RoomWizard and Exchange Connector

to work properly, the room needs to be configured to auto-accept invitations. The room should also be

configured to reject conflicting meetings.

The following command configures every room’s mailbox to auto-accept invitations:

Get-Mailbox | where{$_.ResourceType -eq “Room”} | Set-CalendarProcessing -AutomateProcessing

AutoAccept -AllowConflicts $false

If you want to maintain the comments and private flag between the resource and the user, add the following

arguments to the command above: -RemovePrivateProperty $false -DeleteComments $false

Reference: http://technet.microsoft.com/en-us/library/dd335046.aspx

The following command configures a specific room’s mailbox to auto-accept invitations:

Get-Mailbox “UpstairsConferenceRoom” | Set-CalendarProcessing -AutomateProcessing AutoAccept

By default, the room does not display the original subject of an invitation. Instead, the room shows the organizer’s

name as the subject. If this format is not desired, the following command will reconfigure the room mailbox to show

the invitation subject:

Set-CalendarProcessing -Identity “$$ResourceName$$” -AddOrganizerToSubject $false -DeleteSubject $false

mailto:[email protected]


https://msdn.microsoft.com/en-us/library/office/bb204095(v=exchg.140).aspx

http://technet.microsoft.com/en-us/library/dd335046.aspx

8


Use the Web Platform Installer to Install ASP.NET MVC 3

This section walks through the process of setting up the environment to run the Exchange Connector. You

should already have the appropriate software installed as listed in the System Requirements section.

1. Launch the Internet Information Services (IIS) Manager from the Administrative Tools section

of your web server.

2. Double-click the Web Platform Installer icon at the bottom of the center pane in the Management window.

3. In the Web Platform Installer, search for MVC. Click the Add button next to ASP.NET MVC 3

(Visual Studio 2010). Click Install. Wait for installation to complete.

9


Create a New Website Running on a .NET 4.0 Application Pool

1. Right-click on the Sites folder in the left pane of IIS Manager and select Add Web Site to begin.

This will open the Add Web Site dialog box.

In the Add Web Site dialog box, enter information for these fields:

• Site name: Enter a name for your website

• Application pool: Note what Application pool your website is going to use; you will configure

that in the next step

• Physical path: Choose where on the server drive the connector application files will reside.

You may need to create a new empty folder for this, such as C:\RoomWizard

• Binding: Configure the Port section so that it will not conflict with other sites running on the Web Server.

“8080” is used in the example above. Note: Make sure you use a port open within your environment.

Click OK to create the site.

CREATE A NEW WEBSITE RUNNING ON A .NET 4.0 APPLICATION POOL ROOMWIZARD EXCHANGE CONNECTOR INSTALLATION GUIDE

10

2. To configure the Application pool, click Application Pools in the left pane to bring up the list of current

application pools on the server.

Double-click the Application pool you configured for the new site to use. This will bring up the Edit

Application Pool dialog box.

Select .NET Framework v4.0.xxxxx from the list. Note: . NET Framework v4.0 is default in IIS 10.

If it doesn’t appear in the list, make sure you have the .NET framework version 4 installed. Click OK

to save the changes.


11

3. Now click back on the new website you created. Next, in the right-hand pane click on

Import Application. This will let you import a zipped application bundle into the website.

4. Click Browse and locate the zip file containing the Exchange Connector (this is in the Connector

package you downloaded and unzipped on the Desktop of Web Server). Click Next to continue.


12

The defaults are correct below. Copy all of the contents of the zip file and click Next to continue.

Clear the text in the Application Path box to install it in the root of the site. A dialog box will appear

confirming your choice to install the application at the root of the site instead of in a folder beneath the

root. Click OK, then click Next to continue.


13

On the Overwrite Existing Files page:

• If this is the first installation, the value chosen here will not matter

• If you are upgrading an existing Exchange Connector, click Yes

• Click Next to continue

The application has now been installed. Click Finish to exit the site installer.


14

5. Select the site in the left pane, then click Restart in the right-hand pane.

15


Configuring Basic Authentication (IIS)

Ensure the Basic Authentication module is present.

Select the Server Connection from your Connections tree.

1. In the middle pane (IIS), double-click the Modules icon.

16

CONFIGURING BASIC AUTHENTICATION (IIS) ROOMWIZARD EXCHANGE CONNECTOR INSTALLATION GUIDE

2. Click on BasicAuthenticationModule.

3. In the right-hand pane, click Configure Native Modules link.

4. TokenCacheModule should be in the list that appears. Check the box next to it. (If TokenCacheModule

does not show in the list, disregard this step.)

5. Click OK.

17

CONFIGURING BASIC AUTHENTICATION (IIS) ROOMWIZARD EXCHANGE CONNECTOR INSTALLATION GUIDE

6. Click BasicAuthenticationModule in the Modules list.

7. In the right-hand pane, if Unlock is present under Edit, click it. The word Lock should now appear

below Edit. This indicates that individual sites running on the server can configure the module.

8. Under Connections, select your new website from the Sites list.

9. Double-click the Authentication icon in the middle pane.

10. In the center pane, enable Basic Authentication, and disable all other forms of authentication,

including Anonymous Authentication.

CONFIGURING THE EXCHANGE CONNECTOR ROOMWIZARD EXCHANGE CONNECTOR INSTALLATION GUIDE

20

Configuring the Exchange Connector

NOTE: Prior to browsing the website in order to access the configuration, please momentarily disable IE ESC inn

the Server Manager.

Your connector is now ready to be configured with your Exchange username, password and license key. Browse

your Exchange Connector website, and provide login credentials for your server when prompted.

1. Right-click on your website, select Manage Web Site then Browse.

CONFIGURING THE EXCHANGE CONNECTOR ROOMWIZARD EXCHANGE CONNECTOR INSTALLATION GUIDE

20

Your server’s web browser will open the web page of your newly installed Connector. This is the configuration

page for your connection to Exchange.

Note: Since Basic Authentication for this website was enabled in a previous step, you will be asked for credentials

from Windows Security. Please log in using the local domain service account you created according to the

Connector prerequisites noted on page 2.

The URL will be based on how you set up your website. For example if you installed the connector on a server

named Server, and configured it to run on port 8080, browse to http://server:8080/.

2. The Exchange Connector needs three pieces of information to operate:

• License key or a 90-day Use Demo

• Username (email address) for the Exchange account for whom you plan to grant administrative rights

over RoomWizard room calendars—this should be in the form [email protected], not domain\user and

Password for the Exchange account

• Application Impersonation setup properly in Exchange, see page 7 above

• It is imperative that Application Impersonation is set up correctly and functioning properly in Exchange prior to installing this Conn in order to successfully run the Connector.



Generate a New Configuration

21

To generate a new configuration if you have a license:

1. Enter your license key.

2. Enter the username and password for the Exchange account.

3. Click Test Connection to test the Exchange connection.

4. If Test Connection is successful, click Download New Configuration and Save As Site.conf file over

the existing Site.conf in the bin folder of your Connector files (e.g., C:\RoomWizard\bin).

• If Test Connection is not successful, make sure you are using an Exchange email address.

• If Test Connection continues to fail, check the User Mailbox account and confirm it resides

in your Exchange Mailbox database and all replication is completed.

5. Restart the connector website and reload the connector page in your browser to see that the new

configuration is live.

To use the demo for up to 90 days:

1. Check Use Demo.

2. Follow steps 2-5 from above, as if you have a license.

To update your configuration from a demo to a licensed version:

Open the configuration web page, then:

1. Enter your license key.

2. Uncheck the Use Demo checkbox.

3. Download and install the new configuration as before.

4. Restart the connector’s website.

22


Test Connection Using Connector Test Tool

1. Use the URL for the server that the Connector is installed on in Connector URL, including website port.

2. Choose your Time Zone.

3. Click the About Connector button to test the connection to the Connector.

4. Add a meeting via Outlook and confirm acceptance by the Resource Mailbox. Click the Get Bookings

button. Response should look similar to below with Calendar bookings.

Or you can use the following command in your web browser:

http://Your_WebServer:8080.api?command=get_bookings&range_start_date=20161231&range_start_time=000000&range_end_

date=20171231&range_end_time=000000&format=xml&source=fp&rnd=1326229104504&devicetype=rw10&

room_id=RoomID&time_zone=US%2FMountain

• Make sure to edit the command to match your settings. The example, above right, shows a result code of

“0” indicating there are no bookings for the room id used; the test is successful.

• Be sure to change the highlighted fields to reflect the correct URL, today’s date and tomorrow’s date, and

the correct Room_ID.

23


Configuring the RoomWizard

The RoomWizard is configured for synchronization in the Synchronization web page via the IP address

of the device.

1. Find the IP address of your RoomWizard from the About button on the front panel of the device. Scroll

down to the bottom of the main web page and select RoomWizard setup.

2. Log in. The default admin password will be either roomwizard or 79201 depending on when the

RoomWizard was purchased. It is suggested that your organization change this password and

document the change, so be sure to check with your system administrator for an updated

password.

3. Select Synchronization.

4. The RoomWizard should be set to Synchronized mode by selecting the radio button Use external source.

24

CONFIGURING THE ROOMWIZARD ROOMWIZARD EXCHANGE CONNECTOR INSTALLATION GUIDE

The URL for the connector will be something like: http://your web server:8080/api.

1. “Your web server” is the server you installed the connector on and “8080” is the port number you used

for your website. Please use the local domain service account you created according to the Connector

prerequisites on page 2 for username and password.

2. Click the first Save on THIS Wizard button to make the connection to your Connector.

3. In the Room identifier field, enter the name of the mailbox exactly as it is configured in Exchange (e.g.,

[email protected]). Click the second Save on THIS Wizard button to make the

Connection to your Exchange Calendar.

http://your/

25


Appendix A

Capturing Full Requests and Responses from IIS

The easiest way to capture the full request and responses from IIS and the Exchange Connector is to use

IIS’s Failed Request Tracing: learn.iis.net/page.aspx/266/troubleshooting-failed-requests-using-tracing-in-iis

1. Install IIS: Tracing using the Web Platform Installer.

2. Close the IIS Manager window and open it again.

3. Click Failed Request Tracing in the right-hand pane.

http://learn.iis.net/page.aspx/266/troubleshooting-failed-requests-using-tracing-in-iis/

26

APPENDIX A ROOMWIZARD EXCHANGE CONNECTOR INSTALLATION GUIDE

4. Check the Enable box, choose a log file directory, and click OK.

5. Double-click the Failed Request Tracing icon in the middle pane to bring up the Failed Request

Tracing Rules.

6. Click Add in the right-hand pane to bring up the dialog to create a new rule.

27


7. Keep the default All content for the first step and click Next to continue.

8. To capture all requests (which is recommended for debugging purposes),

check the Status code(s) box and enter 100-999. Click Next to continue.

28


9. Keep the defaults to include all Providers of request and response data.

10. Click Finish to view the new rule, which is ready to capture all

of the requests and responses the server receives.

11. Next, resubmit the failing requests, save the log directory that you selected

in step 4, and forward to Steelcase at [email protected].



31

Appendix B

Installing on Server 2012/2016 with IIS 8.x/IIS 10.x

1. Launch Server Manager.

2. Click on Manage, then select Add Roles and Features.

32

APPENDIX B ROOMWIZARD EXCHANGE CONNECTOR INSTALLATION GUIDE

3. On the Before you Begin screen, click Next.

4. On the Installation Type screen, select Role-based or feature-based installation, then click Next.

33


5. On the Server Selection screen, select the server. (In this example, we are installing on the local server

SP2013.) Click Next.

6. On the Server Roles screen, check the box next to Web Server (IIS). Click Next.

34


7. Click Add Features.

8. Web Server (IIS) box should now be checked. Click Next.

35


9. On the Features screen, add any additional features to install. (In this example, we added .NET

Framework 3.5 Features since it is required.) Click Next.

10. On the Web Server Role (IIS) screen, click Next.

36


11. On the Role Services screen, select any IIS components to install. We recommend the Windows

Authentication role service. After you make your selection(s), click Next.

12. On the Features screen, verify your selections and click Next.

37


13. Confirm your selections and then click Install.

14. Closing the Server Manager will not affect the installation. If you keep it open, you are able

to monitor the progress of the installation. When it completes, click Close.

Note: Follow the steps on pages 2–19 to complete the Connector installation and configuration.

38


Appendix C

Establishing Session with Outlook

In order to configure mailbox access permissions, you will need to establish a PowerShell session using

your Exchange account. This section assumes you have a working knowledge of PowerShell.

Note: You will need to run PowerShell as an Administrator.

Granting Delegate Access Manually via PowerShell

This section provides the necessary commands to configure a room mailbox that grants the RoomWizard

service user full mailbox access. To proceed, a working knowledge of PowerShell is recommended.

The following command is used to grant a user full access to a mailbox:

Add-MailboxPermission “<Mailbox Identifier>” -User: <Service User> -AccessRights: FullAccess

-InheritanceType: All

For example: Add-MailboxPermission “UpstairsConferenceRoom” -User: room.wizard -AccessRights:

FullAccess -InheritanceType: All

The following command finds all resources and grants full user access:

Get-Mailbox -filter {isResource -eq $True} -Resultsize unlimited | Add-MailboxPermission -User:

<Service User> -AccessRights: FullAccess -InheritanceType: All

Note: You can provide other filtering properties that will reduce the result set. See

technet.microsoft.com/en-us/library/bb738155(EXCHG.80).aspx for more filtering properties.

http://technet.microsoft.com/en-us/library/bb738155(EXCHG.80).aspx

39


Granting Application Impersonation Role Manually via PowerShell

This section provides the necessary commands to configure a service user that has the Application Impersonation

role. To proceed, a working knowledge of PowerShell is recommended.

The following command is used to grant the Application Impersonation role:

New-ManagementRoleAssignment –Name:impersonationAssignmentName –Role:ApplicationImpersonation

–User: <Service User>

For example: New-ManagementRoleAssignment –Name:impersonationAssignmentName –

Role:ApplicationImpersonation –User: “[email protected]”

The following command checks if a user has the Application Impersonation role:

Get-ManagementRoleAssignment -RoleAssignee <Service User> -Role ApplicationImpersonation

-RoleAssigneeType user

For example: Get-ManagementRoleAssignment -RoleAssignee “[email protected]”

-Role ApplicationImpersonation -RoleAssigneeType user

Reference: https://msdn.microsoft.com/en-us/library/office/bb204095(v=exchg.140).aspx

Configuring Room Mailbox

By default, a room does not auto-accept invitations. In order for the RoomWizard and Exchange Connector

to work properly, the room needs to be configured to auto-accept invitations. The room should also be

configured to reject conflicting meetings.

The following command configures every room’s mailbox to auto-accept invitations:

Get-Mailbox | where{$_.ResourceType -eq “Room”} | Set-CalendarProcessing -AutomateProcessing

AutoAccept -AllowConflicts $false

If you want to maintain the comments and private flag between the resource and the user, add the following

arguments to the command above: -RemovePrivateProperty $false -DeleteComments $false

Reference: http://technet.microsoft.com/en-us/library/dd335046.aspx

The following command configures a specific room’s mailbox to auto-accept invitations:

Get-Mailbox “UpstairsConferenceRoom” | Set-CalendarProcessing -AutomateProcessing AutoAccept

By default, the room does not display the original subject of an invitation. Instead, the room shows the organizer’s

name as the subject. If this format is not desired, the following command will reconfigure the room mailbox to show

the invitation subject:

Set-CalendarProcessing -Identity “$$ResourceName$$” -AddOrganizerToSubject $false -DeleteSubject $false



https://msdn.microsoft.com/en-us/library/office/bb204095(v=exchg.140).aspx

http://technet.microsoft.com/en-us/library/dd335046.aspx


40

Viewing Attendee Response Status from RoomWizard

In order for the Connector to see how attendees have responded to an invitation, the service user requires

delegate access to all of the user’s mailboxes. The Connector will function without delegate access; however,

the attendees' response status will be unknown.

The following command finds all users and grants a service user full access:

Get-Mailbox -filter {isResource -eq $False} -Resultsize unlimited | Add-MailboxPermission -User: <Service

User> -AccessRights: FullAccess -InheritanceType: All


40

Appendix D

Below is Microsoft’s typical optimization recommendation:

Change the default SNP offload settings where available, and make sure that RSS is enabled (the default setting in Windows Server 2012 and later). RSS will help scale CPU utilization, especially on 10GbE. RSS and TCP Chimney Offload has to be set both in the OS and in the NIC device configuration to work. This is an official recommendation from PG and is discussed in https://technet.microsoft.com/en-us/library/dn879075(v=exchg.150).aspx. To set in the OS run the following in an elevated cmd prompt:

netsh int tcp set global rss=enabled netsh int tcp set global chimney=Automatic

When building out Exchange or doing system gap analysis using the latest Exchange storage calculator as found at https://gallery.technet.microsoft.com/office/Exchange-2013-Server-Role-f8a61780 :

Room IOPS Multiplier = ((# Room Wizards/1000)/1.2)

Separate IIS server for the connector

Similar to Exchange scalability, having a formula that would take the estimated Room Wizard load and potentially incorporating them into multiple instances of the Room Wizard IIS application pool using different impersonation counts. By using the default EWS thresholds for cutoff balance and recharge rate we came up with the following which would estimate a per impersonation account to keep the balance bucket under 60 seconds so that the default 20 second recharge can recharge. This of course can be altered via setting it to all “unlimited”, but as we can see in test creates a very long delay.

Estimated Impersonation Accounts = ((API Calls per Hour/360) x (Room Wizard Instances))/45

Disable Hyper-threading on physical servers and at the VM level for virtualized servers and

setting the page file set to RAM+10MB

https://blogs.technet.microsoft.com/david231/2015/03/30/for-exchange-2010-and-2013-do-this-

before-calling-microsoft/

https://technet.microsoft.com/en-us/library/dn879075(v=exchg.150).aspx

https://gallery.technet.microsoft.com/office/Exchange-2013-Server-Role-f8a61780

https://blogs.technet.microsoft.com/david231/2015/03/30/for-exchange-2010-and-2013-do-this-before-calling-microsoft/

https://blogs.technet.microsoft.com/david231/2015/03/30/for-exchange-2010-and-2013-do-this-before-calling-microsoft/


40

Visit Steelcase.com

facebook.com/Steelcase twitter.com/Steelcase youtube.com/SteelcaseTV

02/2017 © 2016 Steelcase Inc. All rights reserved. All specifications subject to change without notice.

Trademarks used herein are the property of Steelcase Inc. or of their respective owners.

Complete Implementation Guide - Steelcase...

Documents

Transcript of Complete Implementation Guide - Steelcase...