Integrate Crestron Fusion with Microsoft Exchange

Use the following procedures to integrate Crestron Fusion with Microsoft Exchange software.

General Notes

Each room that will require scheduling, either Meetings or Events, needs its own Mailbox/Calendar on the Microsoft Exchange Server® software. You must log in to the mailbox at least once using an email client before the mailbox will validate in Crestron Fusion® software. Crestron Fusion does not change the Exchange Schema in any way.

Exchange 2003 and WebDav

In Exchange 2003, Crestron Fusion uses WebDav to communicate with the Exchange server. This is the same mechanism that OWA (Outlook Web Access) uses. Test the mailbox URL in a web browser running from the server. Use the following format:

http://<exchange_server>/exchange/<account>/calendar

If you are using SSL on the Exchange server (https://) you must install the certificate chain from the Exchange server onto the Crestron Fusion RV server.

Also note that using Exchange 2003, Crestron Fusion does not work with Forms authentication on the Exchange server. It only supports NT authentication. You can see if it is form based when you test the OWA URL with a browser. If you are prompted to log in with a form in the browser window, Crestron Fusion will not work. Additionally, connection to the Exchange environment must be to a back end server. It will not work in a front end or back end architecture against a front end server.

Crestron Fusion will work with Exchange 2007 using OWA but must use the Legacy Paths using the same structure outlined previously. The preferred method to interface with Exchange 2007 or Exchange 2010 is EWS (Exchange Web Services).

Exchange 2007 using WebDav

Run the following shell command to create the proper virtual directory on the mailbox server. It may be necessary to add the server tag.

New‑OwaVirtualDirectory "exchange" -OwaVersion Exchange2003or2000 ‑VirtualDirectoryType Mailboxes ‑WebSiteName "Default Web Site"

Verify using the following command:

Get‑ OwaVirtualDirectory |fl

For more information, refer to these Microsoft Tech-Notes:

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

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

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

Exchange Web Services

EWS is Microsoft’s implementation of a SOAP/XML server interface. It uses formatted XML HTTP post requests to interact with the mailbox and objects such as calendars. The responses are also sent via XML to the requesting application. The security is based on a pass through concept using the credentials we supplied by the application to access the mailbox.

EWS runs on a Client Access Server role (CAS) as it uses the same underlying processes that OWA and OMA use.

Users moving from WebDav to EWS will need a CAS running in their local network.

Observe the following about EWS:

1. Certificates are usually required.
2. "https://autodiscover.yourdomain.com" should resolve in DNS.

NOTE: Autodiscover uses the following path: https://autodiscover.yourdomain.com/autodiscover/autodiscover.xml

3. This is easiest to implement using a Unified Communications Certificate (x 509 v3 certificate).

NOTE: The Unified Communications Certificate is a single certificate that supports multiple DNS names and is a Microsoft‑recommended best practice. Refer to the following technet article for more information: http://technet.microsoft.com/en-us/l.../aa995942.aspx

There are a number of other ways to implement AutoDiscover. For information, refer to the following technet article:

http://technet.microsoft.com/en-us/l.../bb332063.aspx

The advantage of using EWS instead of WebDav is seen when displaying room scheduling on a touch screen. WebDav polls Exchange to obtain calendar data. EWS uses push, which means we don't have to poll every n minute. This reduces overhead on the Exchange server and the processor as data is only moved when it is new.