I'm installing a Lync 2013 Server in a production environment that has an Exchange 2010 server and 2007 SharePoint server.
I want to initially test Lync working internally (IM, presence, voice, video, and maybe phone.) If things go according to plan I will roll it out to everyone and then open it up to the outside.
I have prepared the domain, and am installing Lync 2013 in an HA environment on a single VM with 4 processors and 8 Gb of memory. I have only to blow through the cert part and turn on the services, and I can rock and roll! Everything has been going swimmingly until I got to the cert part.
I have been following Matt Landis' Microsoft Lync Server 2013 Step by Step for Anyone. I have pretty much taken all the defaults and let Lync do its thing. Well, I overlooked one part: Lync wants an internal Certificate Authority server. My AD server is not running that role, and I don't want it to for security reasons, and I don't know how that will affect my existing Exchange and SharePoint certs. I am loathe to change anything on the AD. (If it ain't broke, don't fix it, my dad used to say.) :^)
So, when I choose a CA (page 41) it obviously can't find a local CA, because I'm not running CA on my AD.
OK, then, I'll go back and do an offline cert, then go to GoDaddy and buy a 10-pack SSL, and go that way.
Well, after I import my CSR, and all my names populate, GoDaddy insists the primary name be a FQDN, and because I've taken all the defaults, my primary name is lync.domain.local.So, I can't process my inside cert because I don't have an internal CA, and I can't create an outside cert because I have an inside address.
So, what is the quickest way home here? Turn on CA on the AD? Re-do the Lync install and use a FQDN for the server name? Or is there some other way?
(I will eventually need a FQDN anyway if things work according to plan.)
Rob