<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Certificate problems with OCS 2007 - part 1</title><link>http://blogs.msdn.com/jro/archive/2007/09/04/certificate-problems-with-ocs-2007-part-1.aspx</link><description>Oftentimes when deploying OCS 2007 to complex environments something doesn't work as expected. Even more often the culprit is either a certificates issue or AD (and thus, often a DNS) issue. One of my colleagues had problems when connecting Office Communicator</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Certificate problems with OCS 2007 - part 1</title><link>http://blogs.msdn.com/jro/archive/2007/09/04/certificate-problems-with-ocs-2007-part-1.aspx#4741857</link><pubDate>Tue, 04 Sep 2007 16:53:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4741857</guid><dc:creator>MichaelGiagnocavo</dc:creator><description>&lt;p&gt;Uh, wouldn't the correct fix be to make sure the CRL is in an accessible location rather than downgrade security for the entire workstation?&lt;/p&gt;
</description></item><item><title>re: Certificate problems with OCS 2007 - part 1</title><link>http://blogs.msdn.com/jro/archive/2007/09/04/certificate-problems-with-ocs-2007-part-1.aspx#4759100</link><pubDate>Wed, 05 Sep 2007 12:58:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4759100</guid><dc:creator>jro</dc:creator><description>&lt;p&gt;Michael,&lt;/p&gt;
&lt;p&gt;Absolutely, that's the optimal solution. In certain situations it simply is not possible, though - this fix is towards those situations. &lt;/p&gt;
</description></item><item><title>re: Certificate problems with OCS 2007 - part 1</title><link>http://blogs.msdn.com/jro/archive/2007/09/04/certificate-problems-with-ocs-2007-part-1.aspx#4905493</link><pubDate>Fri, 14 Sep 2007 08:23:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4905493</guid><dc:creator>MikaelLonnroth</dc:creator><description>&lt;p&gt;Here seems to be a good place to point out that security usually (always?) contrasts ease of use. Implementing sufficient security should always include evaluating usability of the stuff that is secured.&lt;/p&gt;
&lt;p&gt;In this respect, I think Microsoft went wrong in more than a couple of places when introducing the new security features in Vista and IE7. It's good that they responded to general mentality of 'IE is buggy and insecure for browsing the internet', but it's really really bad that they, in the process, made surfing the web significantly more difficult, and in some places even impossible. I mean, come on (!), in what universe do I have to start Firefox just to be able to get in to some MSDN or passport protected site that refuses to load because of some IE (default!) security settings that I don't know how to find? At least, when every other windows app also uses the IE module as a proxy, at the very least they could have added some new informative error messages (&amp;quot;To disable the fingerprint scan for accessing www.google.com, open Tools &amp;gt; Internet Options ... or &amp;lt;click here&amp;gt;&amp;quot;). &lt;/p&gt;
&lt;p&gt;Obviously, all of this will make people flee towards Firefox, ironically, because it's less secure and more usable.&lt;/p&gt;</description></item><item><title>re: Certificate problems with OCS 2007 - part 1</title><link>http://blogs.msdn.com/jro/archive/2007/09/04/certificate-problems-with-ocs-2007-part-1.aspx#4907009</link><pubDate>Fri, 14 Sep 2007 11:23:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4907009</guid><dc:creator>jro</dc:creator><description>&lt;p&gt;Whoa, what a comment, Mikael - thanks for that! &lt;/p&gt;
&lt;p&gt;I agree to certain extent, that IE7 + Vista with default settings (read: Protected Mode) is sometimes painful to use. During the past few years I've been using heavily Firefox, because it's lightweight, fast and no-nonse. It just works, and if it doesn't you can probably configure it fairly easily. &lt;/p&gt;
&lt;p&gt;Now I'm back to 100% IE7 with Vista. Yes, I have Protected Mode on. In my line of work I've noticed it's enough to have a shortcut for disabling and enabling proxy settings, and be familiar with the Advanced Settings-section. And sometimes you just have to take the plunge and sacrifice some of the security to get things working, while you figure out why it didn't work before. &lt;/p&gt;
</description></item></channel></rss>