Exchange 2013 comes with a script to quickly do this configuration. The only thing you need to know and understand is which URL you will have to configure when running the script on Exchange. The URL should have the FQDN of your Lync pool and look like https://lyncpool.domain.com/metadata/json/1.

So now, let's explain how to run the script. First, open the Exchange Management Shell and browse to the scripts directory under the Exchange installation path (that is, C:Program FilesMicrosoftExchange ServerV15Scripts). Then, run the following script:

.Configure-EnterprisePartnerApplication.ps1 -AuthMetaDataUrl https://lyncpool.domain.com/metadata/json/1 -ApplicationType Lync

After running the script, you need to perform an IIS reset on your Exchange Client Access servers.

Now, we need to configure Lync 2013 to have Exchange 2013 as a partner application. In this case, we also need to know which URL we will include on the Lync cmdlet that will configure the integration. The URL should point to the autodiscover URI configured on the Exchange Client Access servers and look like https://autodiscover.domain.com/autodiscover/metadata/json/1.

Now that we have explained the URL, let's run the command.

Open the Lync Management Shell and run the following cmdlet:

New-CsPartnerApplication -Identity Exchange -ApplicationTrustLevel Full -MetadataUrl https://autodiscover.domain.com/autodiscover/metadata/json/1

We have now configured both platforms as partner applications.

Once all the previous configurations are completed, we can use a test cmdlet provided by Lync to make sure that the integration is working.

The test cmdlet that we will use is the following:

Test-CsExStorageConnectivity -SipUri sip:[email protected]

The SIPUri should be the SIP address of the user with a mailbox in Exchange 2013. The preceding cmdlet will try and write on the conversation history folder of the user's mailbox, and if the command runs successfully, it indicates that you have both OAuth and the partner applications well configured.