|
|||||
|
I released a small free troubleshooting tool back in October 2008 to help diagnose Communicator automatic sign-in issues. It queries all the possible DNS records that Communicator could use to connect to the OCS server, and displays all the associated matches on the client computer. I have made some significant improvements based on feedback and rolled [...] For all those using my OCS 2007 Automatic Sign-In Troubleshooting Tool, I’ve made a couple of minor improvements. The latest version can be downloaded here: http://www.insideocs.com/tools/MOCLogin.htm There are some usability improvements including the ability to copy the results to the clipboard. Thanks to all those providing feedback. Debugging Office Communicator 2007 automatic sign-in issues can be frustrating because of the different DNS records and their associated formats that are used to locate the home server or pool to attempt the sign-in. To simplify the debugging process, I wrote a small Windows tool that can be downloaded and run on the client. The OCS [...] In my previous two posts (Communicator Automatic Sign-In Part 1 and Part 2) I explored two common pitfalls to make Office Communicator 2007 Automatic Sign-In work with OCS 2007. In this post I explain one last hurdle: ensuring that the client trusts the Certificate Authority (CA) that issued the certificate used on the OCS 2007 [...] A crucial setting to make automatic Office Communicator sign-in work is ensuring that the correct Subject Name (and possibly Subject Alternative Name) is specified on the certificate which resides on the OCS server where the Communicator client connects (e.g. on the Front-End or Director role). When you look at the Certificate details, the Subject Name [...] Three items are key for automatic Office Communicator sign-in to work in an OCS 2007 environment: Specifying the correct FQDN in DNS for the SRV record used for automatic sign-in. |
|
||||
|
Copyright © Curtis Johnstone 2010 - All Rights Reserved |
|||||
