UCPrimer
  • Tech Blog
  • About UCPrimer.com

Deploying UCS with Exchange2013 CU1

5/1/2013

0 Comments

 
Picture
With the release of Exchange 2013 CU1, we can finally deploy the Unified Contact Store (UCS) into an existing Exchange2010 SP3 environment. This is because Exchange2013 is required for UCS and the GTM version of Exchange2013 did not support coexistence with previous versions of Exchange. To recap, UCS enables users to store all contact information in Exchange 2013 so that the information is available globally across Lync, Exchange, Outlook, and Outlook Web Access. Without UCS, Lync2013 clients cannot change or upload their photos. Below is the UCS architecture diagram for reference:

Picture
Deploying Exchange2013 CU1 itself is beyond the scope of this article and the steps are provided in Technet. For existing Exchange2010 environments as in the case of this lab setup, upgrading to Exchange2010 SP3 is required which also performs the prepare AD schema, thereby eliminating the need to run setup.exe /PrepareSchema using Exchange2013. After deploying Exchange2013 we also need to run the post-install steps as described in here. Most notably would be the need to assign a CA issued certificate for the CAS role as Exchange2013, like it's predecessors, by default uses a self-signed cert which Lync2013 will not recognize. Once the prerequisites are done, enabling unified contact store in Lync Server 2013 does not require any topology settings. All that's needed is that the Unified contact store policy is enabled (default is enabled), user's mailboxes have been migrated to Exchange2013, and user log in with using the Lync 2013 rich client at least once.

Configuring oAuth

oAuth is required for server-to-server commication between Lync and Exchange for UCS to work. In the previous article which walked through a Lync2013 deployment, the oAuth certificate was requested and assigned to the Lync server and this certificate will now also be used for Exchange-to-Lync communication. If you have not yet assigned a certificate for the oAuth Token Issuer in Lync2013 then follow the steps in this Technet article. Assuming that has been done, we should proceed to create a partner application for Exchange. The script provided by Microsoft here can be used but the names should be replaced with the specific deployment. Note that the script creates partner applications for both Exchange and Sharepoint so if the latter is not deployed as in the case for this lab, then the following error message displayed after running the script as shown below:
Picture
The above errors points to the missing Sharepoint deployment and can be safely ignored in this lab, since the Exchange partner application was successfully created. Next we proceed to configure the oAuth configuration by running the powershell cmdlet:
Set-CsOAuthConfiguration -Identity Global -ExchangeAutoDiscoverURL <exchange autodiscover svc url> as shown below:
Picture
Interestingly enough, the Exchange Autodiscover service by default has no internal URL assigned as clients use AD SCP to locate the service. This can be shown in the ECP below, noting that the Autodiscover (Default Web Site) has no URL assigned, in contrast to the other virtual directories such as ecp, EWS, ActiveSync etc..:
Picture
To assign the URL for the Autodiscover service, simply run the Exchange powershel cmdlet:

Set-ClientAccessServer -Identity <exchange server FQDN> -AutoDiscoverServiceInternalUri "<XML URL>"

The command as run in my lab environment is shown below along with a Get-ClientAccessServer to verify that the URL was created successfully:
Picture
Of course the autodiscover DNS record has to be created and pointing correctly to the Exchange CAS server. Once that is completed, the final configuration step would be to configure Lync Server 2013 as a partner application in Exchange 2013. A script is provided for this at the default location 'C:\Program Files\Microsoft\Exchange Server\V15\Scripts". The syntax for running the script is

.\Configure-EnterprisePartnerApplication.ps1 -AuthMetadataUrl "https://<LyncFEServerFQDN>/metadata/json/1

The screen shot of running this script in my lab environment is shown below:
Picture
That's pretty much all the configuration that is needed on the Lync2013 and Exchange2013 servers. If a Lync2013 client is currently signed, it will take a few minutes before the following message appears as shown below:
Picture
This indicates that the Lync server has detected a valid UCS on Exchange2013 and will proceed to migrate the user's contacts into Exchange. Once the client signs out and back in again, the user is now UCS enabled. You can verify this be trying to change the user's contact photo in Lync2013, which brings up a browser for the user to login to Exchange Webapp to upload a photo which will then be displayed in Lync.
0 Comments

Your comment will be posted after it is approved.


Leave a Reply.

    Picture
    Picture

    Important Links

    Microsoft Teams Docs
    Microsoft Learn

    ​Microsoft MVP Blogs

    Michael Tressler’s Blog
    Michael’s MTR Quick Tip Videos
    Jimmy Vaughan’s Blog
    Jeff Schertz
    Adam Jacobs
    James Cussen
    ​Damien Margaritis

    Archives

    September 2022
    August 2022
    March 2022
    February 2022
    January 2022
    December 2021
    November 2021
    October 2021
    September 2021
    August 2021
    June 2021
    April 2021
    March 2021
    December 2020
    October 2020
    September 2020
    August 2020
    April 2020
    March 2020
    February 2020
    January 2020
    December 2019
    November 2019
    October 2019
    September 2019
    August 2019
    July 2019
    March 2019
    November 2018
    October 2018
    September 2018
    August 2018
    June 2018
    March 2018
    February 2018
    January 2018
    December 2017
    November 2017
    August 2017
    July 2017
    April 2017
    March 2017
    February 2017
    January 2017
    November 2016
    October 2016
    September 2016
    August 2016
    July 2016
    June 2016
    May 2016
    April 2016
    March 2016
    January 2016
    November 2015
    October 2015
    September 2015
    August 2015
    July 2015
    June 2015
    May 2015
    April 2015
    March 2015
    February 2015
    January 2015
    December 2014
    November 2014
    October 2014
    September 2014
    August 2014
    July 2014
    June 2014
    May 2014
    April 2014
    March 2014
    February 2014
    January 2014
    December 2013
    November 2013
    October 2013
    September 2013
    August 2013
    July 2013
    June 2013
    May 2013
    April 2013
    March 2013
    February 2013
    January 2013
    December 2012
    November 2012
    September 2012
    August 2012

    Categories

    All
    Edge
    Exchange 2013
    Hybrid
    Lpe
    Lync 2010
    Lync 2013
    Mobility
    Oauth
    Office365
    Polycom
    Ucs

    RSS Feed

    This website uses marketing and tracking technologies. Opting out of this will opt you out of all cookies, except for those needed to run the website. Note that some products may not work as well without tracking cookies.

    Opt Out of Cookies