<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Automatic Office Communicator Sign-In (Part 3 – ensuring the client trusts the issuing Certificate Authority)</title>
	<atom:link href="http://blog.insideocs.com/2008/09/23/making-automatic-office-communicator-sign-in-work-part-3-%e2%80%93-ensuring-the-client-trusts-the-issuing-certificate-authority/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.insideocs.com/2008/09/23/making-automatic-office-communicator-sign-in-work-part-3-%e2%80%93-ensuring-the-client-trusts-the-issuing-certificate-authority/</link>
	<description>Microsoft Office Communications Server - Tips, Tricks, and Insight</description>
	<lastBuildDate>Fri, 12 Mar 2010 07:59:21 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The OCS 2007 Automatic Sign-In Troubleshooting Tool V1.0 &#171; Inside OCS</title>
		<link>http://blog.insideocs.com/2008/09/23/making-automatic-office-communicator-sign-in-work-part-3-%e2%80%93-ensuring-the-client-trusts-the-issuing-certificate-authority/comment-page-1/#comment-120</link>
		<dc:creator>The OCS 2007 Automatic Sign-In Troubleshooting Tool V1.0 &#171; Inside OCS</dc:creator>
		<pubDate>Wed, 29 Jul 2009 16:24:58 +0000</pubDate>
		<guid isPermaLink="false">http://ocsbuzz.wordpress.com/?p=92#comment-120</guid>
		<description>[...] Automatic Office Communicator Sign-In (Part 3 – ensuring the client trusts the issuing Certificate...  Possibly related posts: (automatically generated)Automatic Office Communicator Sign-In (Part 1 – The Correct DNS Service L&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Automatic Office Communicator Sign-In (Part 3 – ensuring the client trusts the issuing Certificate&#8230;  Possibly related posts: (automatically generated)Automatic Office Communicator Sign-In (Part 1 – The Correct DNS Service L&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Automatic Office Communicator Sign-In (Part 1 &#8211; The Correct DNS Service Location (SRV) Record) &#171; Inside OCS</title>
		<link>http://blog.insideocs.com/2008/09/23/making-automatic-office-communicator-sign-in-work-part-3-%e2%80%93-ensuring-the-client-trusts-the-issuing-certificate-authority/comment-page-1/#comment-115</link>
		<dc:creator>Automatic Office Communicator Sign-In (Part 1 &#8211; The Correct DNS Service Location (SRV) Record) &#171; Inside OCS</dc:creator>
		<pubDate>Fri, 24 Jul 2009 21:36:51 +0000</pubDate>
		<guid isPermaLink="false">http://ocsbuzz.wordpress.com/?p=92#comment-115</guid>
		<description>[...] Automatic Office Communicator Sign-In (Part 3 – ensuring the client trusts the issuing Certificate... [...]</description>
		<content:encoded><![CDATA[<p>[...] Automatic Office Communicator Sign-In (Part 3 – ensuring the client trusts the issuing Certificate&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DNS Records and Office Communicator Automatic Client Sign-In &#171; Inside OCS</title>
		<link>http://blog.insideocs.com/2008/09/23/making-automatic-office-communicator-sign-in-work-part-3-%e2%80%93-ensuring-the-client-trusts-the-issuing-certificate-authority/comment-page-1/#comment-114</link>
		<dc:creator>DNS Records and Office Communicator Automatic Client Sign-In &#171; Inside OCS</dc:creator>
		<pubDate>Fri, 24 Jul 2009 21:33:33 +0000</pubDate>
		<guid isPermaLink="false">http://ocsbuzz.wordpress.com/?p=92#comment-114</guid>
		<description>[...] Automatic Office Communicator Sign-In (Part 3 – ensuring the client trusts the issuing Certificate... [...]</description>
		<content:encoded><![CDATA[<p>[...] Automatic Office Communicator Sign-In (Part 3 – ensuring the client trusts the issuing Certificate&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Automatic Office Communicator Sign-In (Part 2 – ensuring the correct Subject Name on the Certificate) &#171; Inside OCS</title>
		<link>http://blog.insideocs.com/2008/09/23/making-automatic-office-communicator-sign-in-work-part-3-%e2%80%93-ensuring-the-client-trusts-the-issuing-certificate-authority/comment-page-1/#comment-122</link>
		<dc:creator>Automatic Office Communicator Sign-In (Part 2 – ensuring the correct Subject Name on the Certificate) &#171; Inside OCS</dc:creator>
		<pubDate>Fri, 24 Jul 2009 21:16:58 +0000</pubDate>
		<guid isPermaLink="false">http://ocsbuzz.wordpress.com/?p=92#comment-122</guid>
		<description>[...] Automatic Office Communicator Sign-In (Part 3 – ensuring the client trusts the issuing Certificate... [...]</description>
		<content:encoded><![CDATA[<p>[...] Automatic Office Communicator Sign-In (Part 3 – ensuring the client trusts the issuing Certificate&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curtis Johnstone</title>
		<link>http://blog.insideocs.com/2008/09/23/making-automatic-office-communicator-sign-in-work-part-3-%e2%80%93-ensuring-the-client-trusts-the-issuing-certificate-authority/comment-page-1/#comment-124</link>
		<dc:creator>Curtis Johnstone</dc:creator>
		<pubDate>Tue, 30 Jun 2009 15:24:18 +0000</pubDate>
		<guid isPermaLink="false">http://ocsbuzz.wordpress.com/?p=92#comment-124</guid>
		<description>I don&#039;t know the details of the $30 certificate you mention, but $30 sounds too good to be true in my experience. I would be surprised if it met all the requirements of a UCC certificate. Generally speaking, to use a certificate on an OCS 2007 Front-End, the certificate should be a Web certificate with Enhanced Key Usage for server authentication.

If you submit the certificate request to your CA (GoDaddy) by generating a Certificate Signing Request (CSR) using the OCS 2007 Certificate Wizard, the necessary requirements should be included in that request. I have first-hand experience, and have heard from others, that DigiCert offers a cost effective UCC certificate (that is not an endorsement plug for &lt;a href=&quot;http://www.digicert.com/unified-communications-ssl-tls.htm&quot; rel=&quot;nofollow&quot;&gt;DigiCert&lt;/a&gt;; just relaying my experience).

Also, Microsoft has a list of CA&#039;s that issue UCC certificates for Exchange and OCS in this Knowledge Base Article: &lt;a href=&quot;http://support.microsoft.com/kb/929395&quot; rel=&quot;nofollow&quot;&gt;Unified Communications Certificate Partners for Exchange 2007 and for Communications Server 2007&lt;/a&gt;.

Note: for the Web Components Server, you should use the IIS certificate wizard. See Section 3.7 (Configure the Web Components Server IIS Certificate) in the &lt;a href=&quot;http://www.microsoft.com/downloads/details.aspx?FamilyId=53F65DC9-09DC-4748-81F7-48457469E550&quot; rel=&quot;nofollow&quot;&gt;OCS 2007 Deployment Guide &lt;/a&gt;for more information.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know the details of the $30 certificate you mention, but $30 sounds too good to be true in my experience. I would be surprised if it met all the requirements of a UCC certificate. Generally speaking, to use a certificate on an OCS 2007 Front-End, the certificate should be a Web certificate with Enhanced Key Usage for server authentication.</p>
<p>If you submit the certificate request to your CA (GoDaddy) by generating a Certificate Signing Request (CSR) using the OCS 2007 Certificate Wizard, the necessary requirements should be included in that request. I have first-hand experience, and have heard from others, that DigiCert offers a cost effective UCC certificate (that is not an endorsement plug for <a href="http://www.digicert.com/unified-communications-ssl-tls.htm" rel="nofollow">DigiCert</a>; just relaying my experience).</p>
<p>Also, Microsoft has a list of CA&#8217;s that issue UCC certificates for Exchange and OCS in this Knowledge Base Article: <a href="http://support.microsoft.com/kb/929395" rel="nofollow">Unified Communications Certificate Partners for Exchange 2007 and for Communications Server 2007</a>.</p>
<p>Note: for the Web Components Server, you should use the IIS certificate wizard. See Section 3.7 (Configure the Web Components Server IIS Certificate) in the <a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=53F65DC9-09DC-4748-81F7-48457469E550" rel="nofollow">OCS 2007 Deployment Guide </a>for more information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://blog.insideocs.com/2008/09/23/making-automatic-office-communicator-sign-in-work-part-3-%e2%80%93-ensuring-the-client-trusts-the-issuing-certificate-authority/comment-page-1/#comment-123</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Tue, 30 Jun 2009 13:19:49 +0000</pubDate>
		<guid isPermaLink="false">http://ocsbuzz.wordpress.com/?p=92#comment-123</guid>
		<description>Great article.
I went with a enterprise setup, and chose to purchase a normal SSL Cert with GoDaddy. I was able to install it successfully and now that I am ready to test Office communicator, when trying to sign in, I get

&quot;There was a problem verifying the certificate from the server. Please contact your system administrator.&quot;

The SRV record is set.
DNS is set.

The only thing I&#039;m confused about is the Installation wizard, when runnning the certificate piece wanted to put a Subject Alternate Name for SIP, which I did: sip.domain.com, but of course it wasn&#039;t a UCC Cert that I purchased. ANy issues there? Would a normal 30$ cert be able to append a SAN to it? SHould this work for the Front End server, and then I could purchase a UCC for any additional servers like Edge&#039;s, etc?

Godaddy has been no help.</description>
		<content:encoded><![CDATA[<p>Great article.<br />
I went with a enterprise setup, and chose to purchase a normal SSL Cert with GoDaddy. I was able to install it successfully and now that I am ready to test Office communicator, when trying to sign in, I get</p>
<p>&#8220;There was a problem verifying the certificate from the server. Please contact your system administrator.&#8221;</p>
<p>The SRV record is set.<br />
DNS is set.</p>
<p>The only thing I&#8217;m confused about is the Installation wizard, when runnning the certificate piece wanted to put a Subject Alternate Name for SIP, which I did: sip.domain.com, but of course it wasn&#8217;t a UCC Cert that I purchased. ANy issues there? Would a normal 30$ cert be able to append a SAN to it? SHould this work for the Front End server, and then I could purchase a UCC for any additional servers like Edge&#8217;s, etc?</p>
<p>Godaddy has been no help.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
