Monday, March 14, 2011

Lync 2010 Deployment Guide (even more DNS)

Let’s now check the meeting functionality. I can indeed start a meeting from “Meet Now” menu…

 
But when we reveal the Meeting Join Information, our URL points to meet.drago.ws and not drago.local and… internal users cannot connect to a meeting. 



Quick look in our certificate shows that because of our entries in Topology Builder, meet.drago.ws and dialin.drago.ws is included in the list or SAN (Subject Alternative Name)


...and so, all we need is to create the appropriate A-records in our drago.ws internal zone.


 Once again – rejoice! Internal users now join the meeting as expected.

 

5 comments:

akhil said...

hi...........i am installing lync srver 2010 in lab enviornment. i am able to complete lot of installation, but in the end while performing the last step ,

while requesting the certificate, i have chossen to request certificate online and in the next page ,under chose a certification authority, select a CA from list. in drop down list m not able to see my server address...

dono what to do know???


also ,please provide the link ., if possible , on how to request the certificate offline.......

and also wanna know the reason ,why is that m not able to see my enviornment in drop down list . what i have done wrong during installlation or which step i left ???



please reply.
thanks

Drago said...

Do you have Active Directory Certificate Service installed and configured on your lab Domain Controller as described here? : http://technet.microsoft.com/en-us/library/cc772393(WS.10).aspx

Which role you have a problem with? If you followed the best practices and your edge is not a member of Domain, the Online Domain CA will not be available. Be more specific, please.

Real said...
This comment has been removed by the author.
Real said...

ms-client-diagnostics: 22; reason="Call failed to establish due to a media connectivity failure when both endpoints are internal";CallerMediaDebug="
audio:ICEWarn=0x80020,LocalSite=192.168.100.100:11312,RemoteSite=192.168.1.12:30000,PortRange=1025:65000,LocalLocation=2,RemoteLocation=2,FederationType=0"

Real said...
This comment has been removed by the author.