Comments for The Lync Guy's Blog (Formerly OCSGuy)

Comment on Lync Phone Edition: Connection to Microsoft Exchange is unavailable by Kevin Peters

Kevin Peters — Mon, 21 May 2012 20:24:47 +0000

Hi Richard,

I know exactly what you mean, that is a big part of the reason I write this blog. If you email the email address below they will read it and most likely take some action on it. The Lync documentation tries very hard to provide clear documentation that is also useful. On such a feature rich product it can be hard to cover everything though, so sometimes they don’t hit the nail on the head, that is when emailing them helps.

HTH

-kevin

Comment on Lync Phone Edition: Connection to Microsoft Exchange is unavailable by Richard

Richard — Mon, 21 May 2012 20:17:30 +0000

Peter, dont get me wrong: dim siscussion I was referring to technet / Lync docs talking about a critical requirement, that only mindreaders could decipher from stupidly worded pharagraphs. Requirements should be written as straight-forward as 1-2-3, instead of indirectly referencing to indirect indirect dependencies. I think you know what I mean…

Comment on Lync Phone Edition: Connection to Microsoft Exchange is unavailable by Kevin Peters

Kevin Peters — Mon, 21 May 2012 20:05:09 +0000

Hi Richard,

If you feel that way it would definitely be useful for you to submit that feedpack to the Lync documentation team (lyncdoc@microsoft.com). You could even include the URLs I mentioned and this article. I won’t speak for MSFT on how/why/if thisis hasn’t been covered as extensively as it could have/should have been.

-kp

Comment on Lync Phone Edition: Connection to Microsoft Exchange is unavailable by Richard

Richard — Mon, 21 May 2012 19:51:01 +0000

Well, to be honest the situation in the referenced article is quite far from the situation that we are discussing here. If you are right, Microsoft expects all Lync professionals must own mindreader capabilities to figure this out. This is dim discussion at best, not clear speech.

Comment on Lync Phone Edition: Connection to Microsoft Exchange is unavailable by Kevin Peters

Kevin Peters — Sun, 20 May 2012 21:53:15 +0000

In the microsoft article referenced at the bottom it says:
“Note that the certification authority that signs the default server certificate used when installing Lync Server 2010 is automatically trusted and does not need to be added to the TrustedCACerts property of a collection of Web Services configuration settings. TrustedCACerts should only contain the identities of CAs that need to be trusted in addition to the CA that issued the default certificate. In most cases, the CA that issued the default certificate will be the only certification authority that needs to be trusted.”

That is about the best you are going to get (as far as I have seen).

HTH
-kp

Comment on Lync Phone Edition: Connection to Microsoft Exchange is unavailable by Richard

Richard — Sun, 20 May 2012 17:18:15 +0000

“The root of the problem is the Lync Phone Edition devices will not trust a CA other than the one that issued the certificate to the Lync pool it is connecting to.”

Hi Kevin, please point me to the relevant pharagraph in the official Lync supportability document, that contains exactly this sentence written down. I am looking for this sentence since 2007, but couldnt find it!

Comment on Lync Phone Edition: Connection to Microsoft Exchange is unavailable by Peter

Peter — Sat, 19 May 2012 21:59:48 +0000

Excellent and very useful article. Thanks Kevin.

Comment on Multi-Party Call Functionality Issue by Kevin Peters

Kevin Peters — Fri, 18 May 2012 15:34:58 +0000

Hey Mike,

This one isn’t considered a bug I guess. So it may not get fixed unless enough people make noise about it….

HTH

-kp

Comment on About by Kevin Peters

Kevin Peters — Fri, 18 May 2012 15:32:16 +0000

Hi Ernie,
1 – Does your mobility policy allow call via work?
2 – This setting is pulled form Active Directory

HTH
-kp

Comment on Multi-Party Call Functionality Issue by Mike

Mike — Thu, 17 May 2012 23:22:32 +0000

Hey Kevin,
Any update on this? It seems we have this problem in Lync 2010 CU4. New site found it within a week.
Thanks,
MM