One of the new features in Exchange 2013 CU1 is support for creation of Online Meetings in Outlook Web App (OWA). When you create a new event in OWA you can click on Online meeting, and the meeting is created as an Online meeting. You can also update an existing event to be an Online meeting. See Figure 1 for a screenshot showing the Online meeting button.
Figure 1 Creating an Online Meeting
In order for this feature to work, the following needs to be in place:
OWA use the Unified Communications Web API (UCWA) interface to create the Online Meeting. When OWA boots, and whenever you create a new event in Calendar tab, OWA checks, if UCWA is enabled for the user. OWA uses the Lync Autodiscover service to find the user's pool and the UCWA Url. If UCWA is enabled (happens automatically if the user is homed on a Lync 2013 pool) OWA shows the Online meeting button.
The communication between OWA and Lync happens via Server to Server OAuth (S2SOAuth).
When the Online meeting button is clicked, OWA is creating the Online Meeting. It sets the parameters used for the meeting based on the relevant CsMeetingConfiguration setting (Global, Site or Service scope) in Lync 2013. The parameters used are:
In addition to these parameters, it creates the meeting with the options that all company employees joins as presenters and bypass the lobby.
You are able to join the Online Meeting from the OWA calendar peek via the Join button (see Figure 2). You can also join from the Calendar read form (see Figure 3).
Figure 2 Calendar peek with Join button
Figure 3 Calendar read form with the Join button
Let me show how to configure the integration. I will use the following sample environment to illustrate the configuration:
Configure the Exchange 2013 Autodiscover service to be available on the FQDN autodiscover.contoso.com. Use the following Exchange Management Shell command on e15fe.contoso.com.
Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://autodiscover.contoso.com/autodiscover/autodiscover.xml
We now need to configure the Exchange 2013 side of things. Use the following Exchange Management Shell commands:
We now configure the Lync side of things. Use the following Lync Server Management Shell commands:
We now configure the Lync meeting configuration for the pool. Use the following Lync Server Management Shell commands:
In situations, where the Online meeting button does not appear or the creation of the Online meeting fails, the administrator will have to enable logging in OWA to get diagnostic information about the potential issues. Logging is enabled by editing the web.config file in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa on the Exchange 2013 CU1 mailbox server and changing the line <add key="OWAIsLoggingEnabled" value="false" /> to <add key="OWAIsLoggingEnabled" value="true" />. After saving the changed web.config, recycle the MSEXchangeOWAAppPool in IIS Manager for OWA to pick up the change. OWA will now log information to log files in the directory C:\Program Files\Microsoft\Exchange Server\V15\Logging\OWA\server\.
Ask the user to repro the problem and examine the log file in the directory above. Look for lines with the keywords GetUcwaUserConfiguration and CreateOnlineMeeting and timestamps matching the repro. Hopefully he information in the log file can point to the root cause of the issue.
Awesome. Just what i was looking for!
Case of the missing Online Meeting button in OWA finally solved - Thank You!
it does not seem to work when Lync and Exchange are in different resource forests
GetUcwaUserConfiguration receives AuthenticatedAutodiscover_WebException_OAuthTokenRequestFailedException_The trusted issuers contained following entries ''00000002-0000-0ff1-ce00-000000000000@MY-DOMAIN,00000003-0000-0ff1-ce00-000000000000@01b01632-2b22-4356-830c-b9073ee87373,00000004-0000-0ff1-ce00-000000000000@MY-DOMAIN''. None of them are configured locally."
But they are :-( as all works well including UCS and IM in OWA
This won't work in a hybrid Exchange environment if your Autodiscover is hosted by your on-premises servers. Autodiscover must be hosted on Exchange 2013 as well as the user's mailbox.