<?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"
	>
<channel>
	<title>Comments on: Communicator Web Access (CWA) requires Server 2003+ Enterprise Edition CA</title>
	<atom:link href="http://www.shudnow.net/2008/08/07/office-communicator-web-access-cwa-requires-server-2003-enterprise-edition-ca/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.shudnow.net/2008/08/07/office-communicator-web-access-cwa-requires-server-2003-enterprise-edition-ca/</link>
	<description>Just another IT guy!</description>
	<pubDate>Thu, 20 Nov 2008 08:18:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Elan Shudnow</title>
		<link>http://www.shudnow.net/2008/08/07/office-communicator-web-access-cwa-requires-server-2003-enterprise-edition-ca/#comment-4732</link>
		<dc:creator>Elan Shudnow</dc:creator>
		<pubDate>Sat, 09 Aug 2008 03:41:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=197#comment-4732</guid>
		<description>So I have a theory after looking at some stuff.  The OCS documentation states that OCS requires the Web Server template to be available.  Now the default template is named "Web Server."  But if you look at the detail of the certificate and look at the Certificate Template Name, it states "WebServer."  So because the names are different but it requires the Web Server, I think your assumption about OCS using its' own temporary template is correct.  I think that OCS basically uses the Web Server template, and somehow works with the CA to allow it to make a certificate based off of a temporary version 2 template so to speak and then removes it after the certificate is made.  I'll have to eventually try making a version 2 template called "WebServer" and seeing what happens out of curiousity.</description>
		<content:encoded><![CDATA[<p>So I have a theory after looking at some stuff.  The OCS documentation states that OCS requires the Web Server template to be available.  Now the default template is named &#8220;Web Server.&#8221;  But if you look at the detail of the certificate and look at the Certificate Template Name, it states &#8220;WebServer.&#8221;  So because the names are different but it requires the Web Server, I think your assumption about OCS using its&#8217; own temporary template is correct.  I think that OCS basically uses the Web Server template, and somehow works with the CA to allow it to make a certificate based off of a temporary version 2 template so to speak and then removes it after the certificate is made.  I&#8217;ll have to eventually try making a version 2 template called &#8220;WebServer&#8221; and seeing what happens out of curiousity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Pacyk</title>
		<link>http://www.shudnow.net/2008/08/07/office-communicator-web-access-cwa-requires-server-2003-enterprise-edition-ca/#comment-4731</link>
		<dc:creator>Tom Pacyk</dc:creator>
		<pubDate>Fri, 08 Aug 2008 20:50:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=197#comment-4731</guid>
		<description>No problem. 

I can't remember exactly, but I want to say the OCS cert wizard uses its own template to request the cert, hence the ability to export the private key and have SANs on it as well. It could very well be some advanced options it spits at the CA instead of a different template, but either way - you get the exact cert type you need by using that method.

And as an aside, there's a little trick you can do with the regular Web Server template the does allow you to export the private key without duplicating the template.

Fill out the cert info as normal, pick the web server template. The "Mark private key as exportable" checkbox is grayed out. Press Submit. Instead of clicking the link to install the cert you generated, hit the back button on the browser. "Mark private key as exportable" is no longer grayed out! Check the box, press Submit again and voila - you get a cert you can export with the private key.</description>
		<content:encoded><![CDATA[<p>No problem. </p>
<p>I can&#8217;t remember exactly, but I want to say the OCS cert wizard uses its own template to request the cert, hence the ability to export the private key and have SANs on it as well. It could very well be some advanced options it spits at the CA instead of a different template, but either way - you get the exact cert type you need by using that method.</p>
<p>And as an aside, there&#8217;s a little trick you can do with the regular Web Server template the does allow you to export the private key without duplicating the template.</p>
<p>Fill out the cert info as normal, pick the web server template. The &#8220;Mark private key as exportable&#8221; checkbox is grayed out. Press Submit. Instead of clicking the link to install the cert you generated, hit the back button on the browser. &#8220;Mark private key as exportable&#8221; is no longer grayed out! Check the box, press Submit again and voila - you get a cert you can export with the private key.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elan Shudnow</title>
		<link>http://www.shudnow.net/2008/08/07/office-communicator-web-access-cwa-requires-server-2003-enterprise-edition-ca/#comment-4730</link>
		<dc:creator>Elan Shudnow</dc:creator>
		<pubDate>Fri, 08 Aug 2008 17:13:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=197#comment-4730</guid>
		<description>Thanks for the information Tom.  What seems odd is that the WebServer Template does not allow you to export a private key.  If you look at the Version 1 Template, it doesn't allow the private key to be exported.  If you go onto the certsrv website, the option to export as a private key is greyed out.

But if I go onto my Front End Server, it used the template for Web Server which can see by the properties of the certificate, yet the certificate has the ability to export the certificate with its private key.

So it seems like there is some mechanism in the OCS admin console that allows the certificate request to allow the certificate to be exported with its' private key even if the template it's using doesn't allow that option.</description>
		<content:encoded><![CDATA[<p>Thanks for the information Tom.  What seems odd is that the WebServer Template does not allow you to export a private key.  If you look at the Version 1 Template, it doesn&#8217;t allow the private key to be exported.  If you go onto the certsrv website, the option to export as a private key is greyed out.</p>
<p>But if I go onto my Front End Server, it used the template for Web Server which can see by the properties of the certificate, yet the certificate has the ability to export the certificate with its private key.</p>
<p>So it seems like there is some mechanism in the OCS admin console that allows the certificate request to allow the certificate to be exported with its&#8217; private key even if the template it&#8217;s using doesn&#8217;t allow that option.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Pacyk</title>
		<link>http://www.shudnow.net/2008/08/07/office-communicator-web-access-cwa-requires-server-2003-enterprise-edition-ca/#comment-4728</link>
		<dc:creator>Tom Pacyk</dc:creator>
		<pubDate>Fri, 08 Aug 2008 16:41:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=197#comment-4728</guid>
		<description>In an effort to clear this up...

We're talking &lt;b&gt;operating system&lt;/b&gt; Enterprise vs. Standard edition - not Enterprise CA vs. Standalone CA.

CWA 2007 does &lt;b&gt;not&lt;/b&gt; require a Server 2003 Enterprise Edition (Enterprise or Standalone) CA.

The ability to duplicate and modify a certificate template &lt;b&gt;does&lt;/b&gt; require a Server 2003 Enterprise Edition, but you don't necessarily have to do that for OCS. The easy way around this is to just use the OCS Certificate Wizard from the admin console. It provides the correct template (SAN entries supported) and doesn't require.

Here are 3 alternatives to avoid having to purchase a Server 2003 Enterprise CAL.
- Install the OCS admin console on your CWA box and issue a certificate using the OCS certificate wizard.
- Issue the certificate using the OCS console on a different box, export it with a private key, import into the CWA box
- Issue some advanced certificate options via the certsrv website which will issue the SAN field.
- Use the certreq.exe tool to request a certificate with a SAN.

The latter two options are discussed in more detail here: http://support.microsoft.com/kb/931351/en-us</description>
		<content:encoded><![CDATA[<p>In an effort to clear this up&#8230;</p>
<p>We&#8217;re talking <b>operating system</b> Enterprise vs. Standard edition - not Enterprise CA vs. Standalone CA.</p>
<p>CWA 2007 does <b>not</b> require a Server 2003 Enterprise Edition (Enterprise or Standalone) CA.</p>
<p>The ability to duplicate and modify a certificate template <b>does</b> require a Server 2003 Enterprise Edition, but you don&#8217;t necessarily have to do that for OCS. The easy way around this is to just use the OCS Certificate Wizard from the admin console. It provides the correct template (SAN entries supported) and doesn&#8217;t require.</p>
<p>Here are 3 alternatives to avoid having to purchase a Server 2003 Enterprise CAL.<br />
- Install the OCS admin console on your CWA box and issue a certificate using the OCS certificate wizard.<br />
- Issue the certificate using the OCS console on a different box, export it with a private key, import into the CWA box<br />
- Issue some advanced certificate options via the certsrv website which will issue the SAN field.<br />
- Use the certreq.exe tool to request a certificate with a SAN.</p>
<p>The latter two options are discussed in more detail here: <a href="http://support.microsoft.com/kb/931351/en-us" rel="nofollow">http://support.microsoft.com/kb/931351/en-us</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Great CWA Cert infomation &#171; JC&#8217;s Blog-O-Gibberish</title>
		<link>http://www.shudnow.net/2008/08/07/office-communicator-web-access-cwa-requires-server-2003-enterprise-edition-ca/#comment-4727</link>
		<dc:creator>Great CWA Cert infomation &#171; JC&#8217;s Blog-O-Gibberish</dc:creator>
		<pubDate>Fri, 08 Aug 2008 15:29:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=197#comment-4727</guid>
		<description>[...] CWA Cert&#160;infomation  Posted on August 8, 2008 by johnacook   Communicator Web Access (CWA) requires Server 2003+ Enterprise Edition CA &#124; Elan Shudnow&#8217;s Blo... [...]</description>
		<content:encoded><![CDATA[<p>[...] CWA Cert&nbsp;infomation  Posted on August 8, 2008 by johnacook   Communicator Web Access (CWA) requires Server 2003+ Enterprise Edition CA | Elan Shudnow&#8217;s Blo&#8230; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
