Exchange 2013 UM Certificate

After spending some time this morning trying to deploy a new certificate for Exchange UM in a Exchange 2013 server, I figured I would do this quick post so that I don't have to go looking next time around.

To create the new certificate request from the exchange management shell:

$certReq = new-exchangecertificate -subjectName "C=AU,S=NSW,L=My UC Thoughts,O=City, OU=IT,CN=E2K13.myucthoughts.local" -domainName E2K13.myucthoughts.local -privatekeyexportable $true -generaterequest

set-content -path "c:\certificates\UM.req" -value $certReq

From here you can then complete request from the Certificate Authority to approve the certificate using the UM.req file.  Once you have the certificate you can "complete" the pending certificate request from the Exchange 2013 server.

Update 28/08/2015:
Found this site today that has a web form and it will generate the "New-ExchangeCertificate" command for you to copy and paste.

http://www.tachytelic.net/2010/03/new-exchangecertificate-cmdlet-syntax-generator/

Exchange UM Caller ID

I have a customer issue at the moment that missed call and voice mail notification from PABX to Lync users are not showing correctly for the client.

Instead of the showing:

I am getting:

After some searching around I found the following details on the TechNet site on how Exchange 2010 completes "Name lookups" from a caller ID.

Understanding Name Lookups from a Caller ID

Now in this case we are using E.164 number in only users that have been enabled for Lync, as we are routing calls from an upstream Sonus SBC1000 connected to the PSTN (SIP Trunk) a PABX (Primary Rate ISDN), and Lync (SIP)

I need to test out the solution but I'm hoping that adding the E.164 number to a users "msExchUMCallingLineIDs", as shown in the TechNet article.

Once I get confirmation that the fix worked/doesnt work, I will update this port.