“Certificate Alias” setting for Avaya Application Enablement Services and Lync Server 2013 RCC Integration

I recently completed a Lync Server 2010 to 2013 migration and found that setting up RCC integration between Lync Server 2013 and Avaya AES (Application Enablement Services) was exactly the same as Lync Server 2010.  Avaya has yet to provide an updated guide for the configuration but the following PDF for Lync Server 2010 should be enough to get most administrators started:

Implementation notes on Integration of Avaya Aura Application Enablement ® Services with Microsoft® Lync® 2010 Server.
http://www.crinj.com/wp-content/uploads/Avaya-AES-with-Lync.pdf

As much as the steps in the guide above seem pretty straight forward, there are certain sections that never worked for me.  First, I still experience the same error I did in Lync Server 2010 when I attempt to generate the certificate as outlined in one of my previous blog posts:

Requesting certificate for Microsoft Lync 2010 Pool with customized certificate template for Avaya RCC integration throws the error: “The certificate request with id is denied.”
http://terenceluk.blogspot.com/2012/03/requesting-certificate-for-microsoft.html

Additionally, because it’s been some time since I’ve configured RCC, I couldn’t remember what Certificate Alias I was supposed to select when generating the certificate for the Avaya AES server as shown in the following screenshot:

The choices are as follows:

• aesservices
• ldap
• server
• web

Unfortunately, the Avaya guide doesn’t state what the alias should be and as a matter of fact, doesn’t even demonstrate how to generate it like the old OCS 2007 one so in case anyone is searching for this information or find themselves in a situation where their RCC isn’t functioning and isn’t sure whether they have their certificate generated properly, the alias should be set to aesservices:

 

Hope this helps anyone who might be looking for this information.