Exchange Server 2013 Preview and Lync Server 2013 Preview add new integration features to the existing Exchange Unified Messaging (UM) and Outlook Web App IM and Presence features currently available with Microsoft Exchange Server 2010 and Microsoft Lync Server 2010. The new Lync Server 2013 Preview integration features include Lync Archiving Integration, Unified Contact Store, and high resolution photos.

Lync Archiving Integration integrates Lync Archiving into the Exchange Litigation Hold feature and enables one common experience for administrators around compliance and eDiscovery.

Unified Contact Store (UCS) is where the Lync contact list is stored in Exchange 2013 Preview. This list can be viewed and managed across Lync 2013 Preview client, Office Outlook 2013 Preview and Outlook 2013 Preview Web App.

High resolution photos enables photos up to 648x648 pixels to be stored in Exchange 2013 Preview. Photos are available to clients including Lync 2013 Preview, Outlook 2013 Preview, Outlook 2013 Preview Web App and Lync 2013 Preview Web App.

This blog post describes how the new Exchange 2013 Preview and Lync Server 2013 Preview integration features work, and how to configure and test the integration features when both are available in the same Active Directory forest on premises.

Author: Jens Trier Rasmussen

Publication date: July 23, 2012

Product version: Exchange 2013 Preview, Lync Server 2013 Preview

Prerequisites

In order to use the integration features the following prerequisites must be in place:

  • The mailbox of the user needs to be hosted on Exchange Server 2013 Preview.
  • Exchange 2013 Preview Autodiscover service.
  • Trust and permissions between Exchange 2013 Preview and Lync Server 2013 Preview.
  • Lync Storage Service.
  • Unified Communications Managed API 4.0 Runtime.

Mailbox on Exchange 2013 Preview

The integration features require that the user’s mailbox is hosted on Exchange 2013 Preview. For information about moving a mailbox to versions prior to Exchange 2013 Preview, see the section Move Mailbox to Versions Prior to Exchange 2013 later in this article.

Exchange 2013 Preview Autodiscover Service

The Exchange 2013 Preview Autodiscover service must be configured and working. Review the Exchange 2013 Preview guidance for detailed information.

In environments where Exchange 2010 and Exchange 2013 Preview are deployed side-by-side, configure Lync Server 2013 Preview to use the Exchange 2013 Preview Autodiscover service [1].

Trust and Permissions

In order for Lync Server 2013 Preview to read and write data to Exchange 2013 Preview on behalf of users, it must be trusted by Exchange 2013 Preview and have the necessary permissions.

Trust

Server to Server authentication (S2SOAuth) is the method used to implement trust across the Office 2013 Preview family of servers including Exchange, Lync, and SharePoint. OAuth is a standard authorization protocol based on the exchange of security tokens which grant access to resources for a specific period of time. Trust is established using certificates, and the trust needs to be established between all Exchange 2013 Preview servers and Lync Server 2013 Preview Front End Servers.

This poses a certificate distribution challenge internally between Exchange 2013 Preview servers; internally between Lync Server 2013 Preview Front End servers; and between Exchange 2013 Preview and Lync Server 2013 Preview Front End servers.

Between Exchange 2013 Preview Servers

Exchange 2013 Preview uses one self-signed certificate and distributes it during setup of a server. The certificate is called Microsoft Exchange Server Auth Certificate and it is available in the local computer certificate store after Exchange 2013 Preview is installed on the computer.

Between Lync Server 2013 Preview Front End Servers

Lync Server 2013 Preview use a new certificate type, OAuthTokenIssuer, for its S2SOAuth certificate. The certificate itself can be either an enterprise CA issued certificate or a self-signed certificate. When first requested and assigned using the Lync Server 2013 Preview Certificate Wizard, it is automatically set as a Global [2] certificate and distribution of the certificate between the Lync Server 2013 Preview Front End Servers is then done by Central Management store replication.

Between Exchange 2013 Preview Servers and Lync Server 2013 Preview Front End Servers

Certificates are exchanged between the two types of servers using an authentication metadata document. The document is provided through a web service running on both Exchange 2013 Preview and Lync Server 2013 Preview (the URL ends in metadata/json/1 [3]).

Permissions

To assign permissions in one system, the other system must be represented by a configuration entity. This entity is called a partner application. In Exchange 2013 Preview it is implemented as PartnerApplication and in Lync Server 2013 Preview it is implemented as CsPartnerApplication.

In Exchange 2013 Preview a partner application is linked to a disabled user account and assigned Management Roles [4] according to which permissions it needs. The partner application representing Lync Server 2013 Preview is assigned the UserApplication and ArchiveApplication ManagementRoles. This allows Lync Server 2013 Preview to read from and write data to Exchange 2013 Preview mailboxes on behalf of users.

Lync Storage Service

Lync Storage Service (LYSS) is a storage framework in Lync Server 2013 Preview intended to be used by different Lync Storage Service consumers for accessing storage platforms in the overall Lync Server 2013 Preview system. It is used for the Archiving integration and Unified Contact Store. Currently the design allows for using Exchange Web Services (EWS) and SQL Server as the two storage platforms. Lync Storage Service uses server-to-server authentication to talk to Exchange 2013 Preview.

Unified Communications Managed API 4.0 Runtime

Unified Communications Managed API (UCMA) 4.0 runtime needs to be installed on Exchange 2013 Preview Mailbox servers to enable it to communicate with Lync Server 2013 Preview for the Outlook Web App IM and Presence and Exchange UM integration features.

Prerequisites Configuration

Sample Environment

The following example describes the required configuration prerequisites to enable the integration features. We use the following sample environment to illustrate the configuration:

  • One Lync Server 2013 Preview Enterprise Edition pool with two Lync Server 2013 Preview Front End Servers
    • lyncfe1.contoso.com and lyncfe2.contoso.com.
    • Pool FQDN is lync.contoso.com.
    • Two test users are enabled with SIP URI test1@contoso.com and test2@contoso.com.
  • One Exchange 2013 Preview Client Access server with FQDN e15fe.contoso.com
    • The certificate with thumbprint 30B6CE94148F55762A2C1AEC38DF06C6D206557D has the required subject and subject alternative name entries.
    • Is has been issued by a CA trusted by both Exchange 2013 Preview and Lync Server 2013 Preview servers.
  • One Exchange 2013 Preview Mailbox server with FQDN e15be.contoso.com.
    • The certificate with thumbprint EA5A332496CC05DA69B75B66111C0F78A110D22D has the required subject and subject alternative name entries.
    • It has been issued by a CA trusted by both Exchange 2013 and Lync Server 2013 servers.
    • The test users have Exchange 2013 Preview mailbox with the primary SMTP address test1@contoso.com and test2@contoso.com.
  • A DNS record for autodiscover.contoso.com points to e15fe.contoso.com.

In our sample environment the programs have been installed on the C: drive.

Configuration for your own environments will be different, but hopefully the configuration steps for our sample environment will give you a good idea for how to do it in your own environment.

Step 1: Exchange 2013 Preview Autodiscover Service

Configure the Exchange 2013 Preview 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

Step 2: Exchange 2013 Preview PartnerApplication for Lync

To create the Exchange 2013 Preview PartnerApplication for Lync, Exchange 2013 Preview provides the Configure-EnterprisePartnerApplication script. It requires the URL for the metadata document provided by Lync Server 2013 Preview.

Use the following Exchange Management Shell commands on e15be.contoso.com.

cd c:\'Program Files'\Microsoft\'Exchange Server'\V15\Scripts

.\Configure-EnterprisePartnerApplication.ps1 -AuthMetadataUrl

https://lync.contoso.com/metadata/json/1 -ApplicationType Lync

To enable Exchange 2013 Preview to quickly accept new S2SOAuth connections from Lync Server 2013 Preview, restart IIS on the Client Access and Mailbox servers using the following commands:

iisreset e15fe

iisreset e15be

Lync Server 2013 Preview PartnerApplication for Exchange 2013 Preview

To create the Lync Server 2013 Preview partner application for Exchange 2013 Preview the New-CsPartnerApplication command is used.

Use the following Lync Management Shell command on lyncfe1.contoso.com.

New-CsPartnerApplication -identity Exchange -ApplicationTrustLevel Full -

MetadataUrl https://autodiscover.contoso.com/autodiscover/metadata/json/1

Lync Storage Server Service

Lync Storage Service does not require configuration. It uses the Exchange 2013 Preview Autodiscover service to locate the Exchange 2013 Preview Client Access server and uses the server-to-server authentication configuration to read and write from Exchange 2013 Preview.

Unified Communications Managed API 4.0 Runtime

UCMA 4.0 runtime is installed as a prerequisite for Exchange 2013 Preview Mailbox servers. Installed into the default location on the C: drive, it makes the DLL Microsoft.Rtc.Internal.Ucweb.dll available in C:\Program Files\Microsoft UCMA 4.0\Runtime\SSP. This interface is used by Exchange UM and Outlook Web App IM to talk to Lync Server 2013 Preview.

Testing the configuration

To test that the server-to-server authentication configuration has been setup correctly, use the new Test-CsExStorageConnectivity Synthetic Transaction in Lync Server 2013 Preview. This command uses server-to-server authentication to write an item into the conversation history folder of an Exchange 2013 Preview Mailbox and delete it again.

Use the following Lync Management Shell command on lyncfe1.contoso.com .

Test-CsExStorageConnectivity -SipUri test1@contoso.com -Binding NetTCP –

DeleteItem -HostNameStorageService lync.contoso.com

Features

Now that we have described the prerequisites and how to configure them, we’ll address the features and how to configure them in our sample environment.

Lync Archiving Integration

Implementation Details

When Lync Archiving Integration to Exchange is enabled for a user, the archived data is written to the user’s Exchange 2013 Preview mailbox instead of being written to the Lync Archiving database. Users, whose mailbox is not hosted on Exchange 2013 Preview will use the Lync Server 2013 Preview SQL Archiving store.

The data is written to the Purges folder under the Recoverable Items folder. This is the same folder used by the Exchange 2013 Preview Litigation Hold feature [5]. The folder is not visible to end-user, but is indexed by Exchange 2013 Preview search and is discoverable by MailboxSearch and SharePoint 2013 Preview Discovery Center. You can also inspect it by using tools such as MfcMapi and EWSEditor.

Lync Archiving Integration to Exchange is controlled by the EnableExchangeArchiving parameter in CsArchivingConfiguration and can be enabled on Global, Site or Service scope. The EnableArchiving parameter in CsArchivingConfiguration controls what type of Lync archiving is enabled.

When Lync Archiving is enabled and Exchange integration is set to true using CsArchivingConfiguration, the decision to archive the Lync communications at the user level is driven by the Exchange hold policy for users, whose mailboxes are homed in Exchange 2013 Preview, and by Lync Archiving policy for users whose mailboxes are not homed in Exchange 2013 Preview.

If Lync Server 2013 Preview and Exchange Server 2013 Preview are deployed in same forest, the Exchange hold policy is used by Lync Server 2013 Preview to determine whether to archive the Lync communications for users, whose mailboxes are homed on Exchange 2013 Preview.

If Lync Server 2013 Preview and Exchange Server 2013 Preview are deployed in different forest, then for users whose mailboxes are homed on Exchange 2013 Preview, the ArchivingToExchange policy is determined by the ExchangeArchivingPolicy parameter on CsUser.

The ExchangeArchivingPolicy parameter has the following values:

  • Uninitialized
  • UseLyncArchivingPolicy
  • NoArchiving
  • ArchivingToExchange

Uninitialized means that Lync Archiving will respect any Exchange 2013 Preview In-Place Hold settings in effect for the user’s mailbox. In Exchange 2013 Preview you can have multiple MailboxSearch instances targeting a given mailbox and each one can have the InPlaceHoldEnabled attribute set to $True or $False. If the user is targeted by one or more MailboxSearch instances with InPlaceHoldEnabled $True, the msExchUserHoldPolicies attribute on the user object will contain one or more of InPlaceHoldIdentity values (GUIDs). The Lync Server 2013 Preview User Replicator will see that the attribute has one or more values and will configure the user to have ExchangeArchiving enabled in the internal Lync Server 2013 Preview SQL database table controlling archiving.

UseLyncArchivingPolicy means that archiving is assigned to the Lync Server 2013 Preview SQL Archiving database.

NoArchiving means no archiving is performed for the user.

ArchivingToExchange means that archiving is assigned to Exchange 2013 Preview, regardless of any In-Place Hold settings affecting the user’s mailbox.

Configuration Procedure

To configure Lync Archiving Integration in our sample environment.

Step 1: Start by enabling Exchange Archiving with Global scope and set Lync to archive IM and Web Conference content. Use the following Lync Management Shell command on lyncfe1.contoso.com.

Set-CsArchivingConfiguration -EnableExchangeArchiving $true –EnableArchiving ImAndWebConf

Step 2: Configure the two test users to archive to Exchange by configuring test1 to respect Exchange 2013 Preview In-Place Hold settings and by configuring test2 to always archive to Exchange 2013 Preview. Use the following Lync Management Shell commands on lyncfe1.contoso.com.

Set-CsUser test1 –ExchangeArchivingPolicy Uninitialized

Set-CsUser test2 –ExchangeArchivingPolicy ArchivingToExchange

Step 3: Configure Exchange 2013 Preview with a mailbox search with In-Place Hold to target test1’s mailbox. Use the following Exchange Management Shell command on e15be.contoso.com.

New-MailboxSearch -Description "test1 in-place hold" -Name test1 -

InPlaceHoldEnabled $true -SourceMailboxes test1

After a short time the Lync Server 2013 Preview User Replicator will see the change on the user object and configure Lync Server 2013 Preview to archive to Exchange 2013 Preview for test1.

Testing

To test that the above configuration works as expected in our sample environment:

  • Sign in to Lync 2013 as test1 and test2.
  • Send the IM “Test of Exchange Archiving test1” from test1 to test2. Close the conversation windows in both clients and send the IM “Test of Exchange Archiving test2” from the test2 to test1.
  • Close the conversation windows in both clients.

Sign in to the Exchange 2013 Preview Control Panel (in our sample environment available at https://e15fe.contoso.com/ecp) as the Exchange Administrator and select the Compliance Management tab and In-Place Discovery & Hold section.

  • Edit the test1 mailbox search and add a Search Query by filter based on criteria and add the text “Test of Exchange Archiving” to the keywords.
  • Save the search.
  • Select Preview search results and the IM should be visible in the Mailbox Search preview tab.

To test the configuration for test2:

  • Use the Exchange 2013 Preview Control Panel to create a mailbox search without In-Place Hold targeting test2 mailbox and with the search query Test of Exchange Archiving.
  • Preview the results of that new search and the IM from test2 to test1 should be found.

Troubleshooting

In order to get an understanding about the health of the Lync Archiving integration to Exchange you can monitor the Lync Server event log for errors and the Performance Monitor counters LS:DATACOLLECTION – 06 – Exchange Archiving Adaptor.

If you suspect something is wrong you can use the Lync Server 2013 Preview Centralized Logging Service scenarios LYSSAndUCS and MonitoringAndArchiving to collect server traces and then use the components UdcAgent and Lyss and loglevel verbose, when searching the traces.

Unified Contact Store

Implementation Details

When Unified Contact Store (UCS) is enabled for a user, the Exchange 2013 Preview mailbox is used as the storage location for the Lync Contacts. The Lync 2013 Preview client then uses Exchange Web Services (EWS) to read and maintain the contacts instead of using SIP to Lync Server 2013 Preview.

The Lync Contacts are written to two folders in the Contacts folder in the Exchange 2013 Preview Mailbox. The contacts themselves are written to the visible Lync Contacts folder. Metadata about the contacts is written to a sub-folder of Contacts named with a GUID. This folder is not visible to the end-user. You can inspect it by using tools such as MfcMapi and EWSEditor.

The Unified Contact Store is controlled by the Boolean flag UcsAllowed in the new Lync Server 2013 Preview policy CsUserServicesPolicy. The policy can be created with a Global, Site, Service or Tag scope.

When Lync 2013 Preview signs in, it receives policy assignment information through in-band provisioning. If the user is enabled for Unified Contact Store, the Lync client will send a nudge to Lync Server 2013 Preview. The nudge tells the server that the user is enabled for Unified Contact Store and to begin migration of the contacts to Exchange 2013 Preview. Lync Server 2013 Preview will then use Lync Storage Service to migrate the contacts for the user to Exchange 2013 Preview.

After the server has successfully migrated the contacts, the Lync 2013 Preview client is notified and the user is asked to sign out and sign in again to pick up the change Figure 1.

Figure 1. Lync client notification.

After the migration is finalized the Lync 2013 Preview client uses Exchange Web Services (EWS) to read and maintain the Lync Contacts.

Configuration Procedure

To configure Unified Contact Store in our sample environment, create a new CsUserServicesPolicy and assign it to the two test users. Use the following Lync Management Shell commands on lyncfe1.contoso.com.

New-CsUserServicesPolicy UcsEnabledUser -UcsAllowed $true

Grant-CsUserServicesPolicy -PolicyName UcsEnabledUser -Identity test1

Grant-CsUserServicesPolicy -PolicyName UcsEnabledUser -Identity test2

Testing

There are two ways to test if a user has been migrated to Unified Contact Store.

  • On the server side, the Lync administrator can use the new Lync Server 2013 Preview Synthetic Transaction Test-CsUnifiedContactStore. An example of running this command in our sample environment is:

Test-CsUnifiedContactStore -UserSipAddress test1@contoso.com -TargetFqdn lync.contoso.com

  • On the client side, the Contact List Provider is displayed in the Lync Configuration Information page (CTRL + right click Lync Icon in the system tray and select Configuration Information). Contact List Provider = UCS means the user has been successfully migrated to UCS.

Troubleshooting

Server side

To understand UCS migration process, monitor the Lync Server event log for errors and the Performance Monitor counters LS:USrv – 38 – Unified Contact Store.

If you suspect something is wrong, use the Lync Server 2013 Preview Centralized Logging Service scenarios LYSSAndUCS to collect server traces and then use the component Lyss and loglevel verbose, when searching the traces.

Client side

If Lync 2013 Preview is unable to connect to EWS, it will display the warning message shown in Figure 2 in the main UI.

Figure 2. Lync Main UI warning on Exchange connectivity issues.

Additional information might be available in the Lync Configuration Information page [6]. Warnings are typically generated by connectivity issues with Exchange Autodiscover or EWS. To gather more insight to the issue, you’ll find a tool like Fiddler [7] is very useful.

High Resolution Photos

Implementation Details

Lync Server 2010 added photos to contacts. Photos can come from the Active Directory user object or from a URL reference to a public web site. When photos come from Active Directory, the size and resolution of the photos are limited because the photos are stored in the thumbnailPhoto attribute on the Active Directory user object [8].

With Lync Server 2013 Preview, and the Office 2013 Preview family of products, the ability to use photos with resolutions ranging from 48x48 up to 648x648 pixels has been introduced. The 3 common resolutions used are:

  • 48x48 is for the Active Directory thumbnailPhoto version.
  • 96x96 is for Outlook 2013 Preview Web App, Outlook 2013 Preview, Lync 2013 Preview Web App and Lync 2013 Preview.
  • 648x648 is for Lync 2013 Preview Web App and Lync 2013 Preview.

The photo is stored in the Exchange 2013 Preview user mailbox in a hidden item in the root of the mailbox. It can be uploaded by the user using Outlook 2013 Preview Web App or by an Exchange administrator using the Set-UserPhoto command in Exchange Management Shell.

The photo upload process stores the photo in an internal format that supports different resolutions and automatically updates the Active Directory thumbnailPhoto attribute with a 48x48 version of the photo. However, the reverse is not true. If the Active Directory thumbnailPhoto is updated by another process, the photo in the Exchange 2013 Preview mailbox is not updated.

The typically size of an item, representing a photo with resolution equal to 648x648 and 24 bits depth, is 241 Kb.

Access to the photo is provided by Exchange Web Services.

Configuration Procedure

To configure high resolution photos in our sample environment. The following Exchange Management Shell commands are used on e15be.contoso.com.

$photostring = "test1hrphoto.jpg”

$pic=([Byte[]] $(Get-Content -Path $photostring -Encoding Byte -ReadCount 0))

Set-UserPhoto -Identity test1 -PictureData $pic -confirm:$false

Set-UserPhoto -identity test1 -save -confirm:$false

$photostring = "test2hrphoto.jpg”

$pic=([Byte[]] $(Get-Content -Path $photostring -Encoding Byte -ReadCount 0))

Set-UserPhoto -Identity test2 -PictureData $pic -confirm:$false

Set-UserPhoto -identity test2 -save -confirm:$false

Testing

The easiest way to test that the high resolution photo has been uploaded to Exchange 2013 Preview and is available is to use the Lync 2013 Preview client and select Options in the main UI and then select My Picture. You should see both the Contact picture and the Video picture in crisp resolutions.

An additional test is to download the photo directly using the EWS API GetUserPhoto. In our sample environment enter the following URL in IE and the photo should be displayed.

https://e15fe.contoso.com/ews/Exchange.asmx/s/GetUserPhoto?email=test1@contoso.com&size=HR648x648

Troubleshooting

If the Lync 2013 Preview client does not display the photo, or displays an incorrect photo, a good starting point to troubleshoot is to reference the photo directly using the GetUserPhoto API. If that does not work, the issue is usually a connectivity issue with EWS. If the correct photo is returned form the GetUserPhoto API, the Lync 2013 Preview client might have a connectivity issue to Exchange Autodiscover service or EWS. The same client side troubleshooting steps used for UCS are useful.

Exchange UM Integration

Implementation Details

Exchange 2013 Preview introduces a Unified Messaging component called the UM Call Router running on the Exchange 2013 Client Access server. Calls going to Exchange UM are diverted to UM Call Router and are re-directed to the appropriate Mailbox server running Exchange UM.

Configuration Procedure

Configure our sample environment so Lync Server 2013 Preview can use Exchange 2013 Preview UM as its voice mail system.

Other than the configuration of UM Call Router, the integration configuration between Lync Server 2013 Preview and Exchange 2013 Preview UM is the same as the integration configuration between Lync 2010 and Exchange 2010 UM. Make sure Lync Server 2013 Preview and Exchange 2013 Preview UM trust each other by using mutually trusted certificates and have the Exchange UM servers appear as known servers in Lync Server 2013 Preview. In addition, Lync Server 2013 Preview needs to have permissions to read Exchange 2013 Preview Active Directory objects [9].

Start by configuring a new UMDialPlan for Lync Server 2013 Preview integration with 3 digits extensions. Allow all UM enabled users to dial-out world-wide. Make sure that Exchange UM picks up the new settings by restarting the process. Use the following Exchange Management Shell commands on e15be.contoso.com:

New-UMDialPlan -Name e15dp -VoIPSecurity secured -NumberOfDigitsInExtension 3 -URIType sipname -countryorregioncode 1

Set-UMDialPlan e15dp -ConfiguredInCountryorRegionGroups 'Anywhere,*,*,ww' -AllowedInCountryOrRegionGroups Anywhere

Set-UMMailboxPolicy -id 'e15dp default policy' -AllowedInCountryOrRegionGroups Anywhere

Set-UmService -UMStartupMode dual -DialPlans e15dp -id e15be

Enable-ExchangeCertificate -server e15be -Thumbprint EA5A332496CC05DA69B75B66111C0F78A110D22D -Services smtp,iis,um

gwmi win32_service -comp e15be | where {$_.name -eq 'msexchangeum'} | % {$_.stopservice()}

gwmi win32_service -comp e15be | where {$_.name -eq 'msexchangeum'} | % {$_.startservice()}

To enabled our two test users for UM. Use the following Exchange Management Shell commands on e15be.contoso.com:

Enable-UMMailbox -Extensions 100 –SIPResourceIdentifier test1@contoso.com -Identity contoso\test1 -UMMailboxPolicy 'e15dp default policy'

Enable-UMMailbox -Extensions 101 -SIPResourceIdentifier test2@contoso.com -Identity contoso\test2 –UMMailboxPolicy 'e15dp default policy'

To configure the UM Call Router to integrate to Lync Server 2013 Preview, use the following Exchange Management Shell commands on e15fe.contoso.com:

Set-UmCallRouterSettings -UMStartupMode dual -DialPlans e15dp –server e15fe

Enable-ExchangeCertificate -server e15fe -Thumbprint 30B6CE94148F55762A2C1AEC38DF06C6D206557D -Services iis,umcallrouter

gwmi win32_service -comp e15fe | where {$_.name -eq 'msexchangeumcr'} | % {$_.stopservice()}

gwmi win32_service -comp e15fe | where {$_.name -eq 'msexchangeumcr'} | % {$_.startservice()}

By having both the UM Call Router and UM on e15be.contoso.com, the e15dp UMDialPlan Exchange Unified Messaging Routing component in Lync Server 2013 Preview will automatically add the two Exchange 2013 Preview servers to the known server tables in Lync Server 2013 Preview. It is, therefore, not necessary to add them as CsTrustedApplicationPools.

Testing

We can use two new Lync Server 2013 Preview synthetic transactions to test the Exchange 2013 Preview UM Integration to Lync Server 2013 Preview. Test-CsExUMConnectivity tests that Lync Server 2013 Preview can connect to Exchange 2013 Preview UM for a given user and Test-CsExUMVoiceMail deposits a voice mail for the user. Use the following Lync Management Shell commands on lyncfe1.contoso.com.

Test-CsExUMConnectivity -TargetFqdn lync.contoso.com -UserSipAddress test1@contoso.com

Test-CsExUMConnectivity -TargetFqdn lync.contoso.com -UserSipAddress test2@contoso.com

$cred=Get-Credential -UserName contoso\test1 -message "voice mail sender is test1"

Test-CsExUMVoiceMail -SenderSipAddress test1@contoso.com -ReceiverSipAddress test2@contoso.com -SenderCredential $cred -WaveFile voicemail.wma

$cred=Get-Credential -UserName contoso\test2 -message "voice mail sender is test2"

Test-CsExUMVoiceMail -SenderSipAddress test2@contoso.com -ReceiverSipAddress test1@contoso.com -SenderCredential $cred -WaveFile voicemail.wma

Troubleshooting

If you suspect something is wrong, use the Lync Server 2013 Preview Centralized Logging Service scenarios VoiceMail to collect server traces and then use the component ExUmRouting and loglevel verbose, to search the traces.

Outlook 2013 Preview Web App IM and Presence Integration

Implementation Details

Outlook 2013 Preview Web App IM and Presence is able to integrate with Lync Server 2013 Preview in the same way that Exchange 2010 Outlook Web App IM is able to integrate with Lync Server 2010.

Configuration Procedure

The integration configuration is conceptually the same as in Exchange 2010. The only difference is the actual configuration of the OWAVirtualDirectories because of the new front-end/back-end architecture in Exchange 2013 Preview. Use the following Exchange Management Shell commands on e15be.contoso.com.

Get-OwaVirtualDirectory -ShowBackEndVirtualDirectories -server e15be | where { $_.WebSite -eq 'Exchange Back End' } | Set-OwaVirtualDirectory -InstantMessagingEnabled $true -InstantMessagingType OCS -InstantMessagingCertificateThumbprint EA5A332496CC05DA69B75B66111C0F78A110D22D –InstantMessagingServerName lync.contoso.com

Get-OwaMailboxPolicy | Set-OwaMailboxPolicy -InstantMessagingEnabled $true –InstantMessagingType OCS

Testing

To test Outlook 2013 Preview Web App IM and Presence Integration you must sign in to Outlook Web App. The Sign in to IM option is available in the drop down on the display name, next to the gear icon in the Outlook Web App main UI.

Troubleshooting

If a user of Outlook Web App is not able to sign into IM, the first place to look for errors is in the Outlook Web App InstantMessaging log files on the Exchange Mailbox server. In our sample environment the files are located at C:\Program Files\Microsoft\Exchange Server\V15\Logging\OWA\InstantMessaging.

If a trace is needed on the Lync Server side, use the Lync Server 2013 Preview Centralized Logging Service scenarios IMAndPresence to collect server traces and then use the component SIPStack and loglevel verbose, to search the traces.

Move Mailbox to Versions Prior to Exchange 2013 Preview

All features require the user’s mailbox to be hosted on Exchange 2013 Preview. If the mailbox is moved to versions prior to Exchange 2013 Preview these features are not be available.

Before moving a mailbox away from Exchange 2013 Preview, it is essential to roll the user’s Lync Contacts back to Lync Server 2013 Preview. To complete this rollback use the new Lync Server 2013 Preview command Invoke-CsUcsRollback. The command migrates the Lync Contacts back to Lync Server 2013 Preview and prevents the user from being enabled for UCS for a period of seven days. This seven day retention period prevents the Lync Contacts from being moved back to Exchange 2013 Preview immediately by the server migration process. It is recommended to change the CsUserServicesPolicy, to not allow users, who have moved away from Exchange 2013 Preview, to access the UCS.


[1] Set-CsOAuthConfiguration –ExchangeAutodiscoverUrl https://<E15 CA server FQDN>/autodiscover/autodiscover.svc

[2] New feature in Lync Server 2013 Preview

[3] The start of the URL depends on the product being used. For Lync Server 2013 Preview it is the pool FQDN and for Exchange 2013 Preview it is typically the Autodiscover FQDN.

[4] Exchange 2013 Preview Role Based Access Control concept

[5] For background information on Exchange 2010 Litigation Hold see Understanding Litigation Hold.

[6] Press CTRL and right click in the Lync icon in the system tray and then select Configuration Information.

[7] Introducing Fiddler.

[8] For more information please see Microsoft Lync 2010 Photo Experience.

[9] The existing Exchange 2010 guidance is available at Deploying On-Premises Exchange UM to Provide Lync Server 2010 Voice Mail.