Public Certificate for Scaled Out Lync Multiple Site
-
quinta-feira, 31 de maio de 2012 10:54
Hi All,
Wanted to run this question here to make sure this is correct. A client has two offices (NJ, and LA), they will support public IM, federation and web conferencing will be used at the moment.
I want to make sure I have everything planned for the certificate for both sites. Both sites will have TMG.
New Jersey will be:
NJO Access Edge: SIP.clientcompany.com (common name on SAN)
NJO web conferencing: webconf.clientcompany.com
NJO A/V: av.clientcompany.com
NJO External Web Services URL: nj.clientcompany.com
NJO meet url: meetnj.clientcompany.com
Simple Dial-In URL: dialin.clientcompany.com
Los Angeles will be:
LAO Access Edge: LASIP.clientcompany.com (common name on SAN)
LAO web conferencing: lawebconf.clientcompany.com
LAO A/V: LAav.clientcompany.com
LAO External Web Services URL: la.clientcompany.com
LAO meet url: meetla.clientcompany.com
I know the web services url, meet, and dialin should be on proxy (if i am wrong please advise)
Basically what I am asking does this meet all the public certificate requirement?
Thanks all!!
Todas as Respostas
-
sexta-feira, 1 de junho de 2012 06:33Moderador
Hi,RMuhammad8805,
Are you talking about the public certificates?Does your client plan to deploy Lync mobility?
Basically,you should have 3 public certificates which should be assigned to Front End web service,External Edge interface and reverse proxy,and they are should like below:
The External Web service on FE server certificate(Public CA)
SN=FQDN of the FE Server=Se01.clientcompany.com
SAN=External Web Services FQDN=nj.clientcompany.com or la.clientcompany.com
=Meet URL=njMeet.clientcompany.com or lameet.clientcompany.com (Note:You also can use one single meet url for NJ and LA if you use Hardware load banlancer)
=Dialin URL=dialin.clientcompany.com
=Lync External Autodiscover Service URL=Lyncdiscover.clientcompany.com (If you deploy Lync mobility service)
The External Edge certificate (Public CA)
SN=Access Edge server FQDN=sip.clientcompany.com or LAsip.clientcompany.com
SAN=Access Edge Server FQDN=sip.clientcompany.com or LAsip.clientcompany.com
=Web Conferencing Edge server FQDN=webconf.clientcompany.com or lawebconf.clientcompany.com
=sip.clientcompany.com (Autoconfig SRV record) for autoconfigure for remote users
The Reverse Proxy certificate(Public CA):
SN=Reverse Proxy server FQDN=lsrp.clientcompany.com
SAN=External Web Services FQDN=nj.clientcompany.com or la.clientcompany.com
=Dial-in conferencing=dialin.clientcompany.com
=Online meeting publishing rule=njMeet.clientcompany.com or lameet.clientcompany.com (Note:You also can use one single meet url for NJ and LA if you use Hardware load banlancer)
=Mobility service URL=Lyncdiscover.clientcompany.com (If you deploy Lync Mobility Service)
You also can check the following links for more details about Lync certificates requirements
http://technet.microsoft.com/en-us/library/gg398094.aspx
http://technet.microsoft.com/en-us/library/gg398920.aspx
http://technet.microsoft.com/en-us/library/gg398519.aspx
Hope these can clarify your question.
B/R
Sharon
Sharon Shen
TechNet Community Support
************************************************************************************************************************
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.
- Sugerido como Resposta Sharon.ShenMicrosoft Contingent Staff, Moderator sexta-feira, 1 de junho de 2012 09:55
- Marcado como Resposta Sharon.ShenMicrosoft Contingent Staff, Moderator segunda-feira, 4 de junho de 2012 10:02
-
domingo, 17 de junho de 2012 17:17Thank you Sharon this was very helpful.
.png)
