<?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 for Cohesive Logic</title>
	<atom:link href="http://cohesivelogic.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://cohesivelogic.com</link>
	<description>The Microsoft Infrastructure Experts</description>
	<lastBuildDate>Fri, 11 Nov 2011 19:02:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Exchange 2010 &amp; Single Name SSL Certificates by Scott Fortier</title>
		<link>http://cohesivelogic.com/2011/01/exchange-2010-single-name-ssl-certificates/comment-page-1/#comment-461</link>
		<dc:creator>Scott Fortier</dc:creator>
		<pubDate>Fri, 11 Nov 2011 19:02:57 +0000</pubDate>
		<guid isPermaLink="false">http://cohesivelogic.com/?p=501#comment-461</guid>
		<description>Jeremy,

Thank you very much for this right up.  This was exactly the solution I needed.  I had been stuck for a while installing a new Exchange 2010 server into a domain with a lot of Windows, Linux, and Netware servers that had a non standard domain name ending in .loc  ( from the Windows NT days ).   Since the domain name was not a standard .local, .priv. etc, we were unable to obtain a SSL certificate for it.   Now everything on this new exchange server worked perfectly except whenever a local Outlook 2010 client would attempt to connect, it would receive the annoying certificate warning from the self signed cert.   Since local and external clients can access this server via it&#039;s public IP, this article solved the problem I had been questioning people about for more than a week in a matter of minutes.    

Thanks,
Scott</description>
		<content:encoded><![CDATA[<p>Jeremy,</p>
<p>Thank you very much for this right up.  This was exactly the solution I needed.  I had been stuck for a while installing a new Exchange 2010 server into a domain with a lot of Windows, Linux, and Netware servers that had a non standard domain name ending in .loc  ( from the Windows NT days ).   Since the domain name was not a standard .local, .priv. etc, we were unable to obtain a SSL certificate for it.   Now everything on this new exchange server worked perfectly except whenever a local Outlook 2010 client would attempt to connect, it would receive the annoying certificate warning from the self signed cert.   Since local and external clients can access this server via it&#8217;s public IP, this article solved the problem I had been questioning people about for more than a week in a matter of minutes.    </p>
<p>Thanks,<br />
Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Exchange 2010 &amp; Single Name SSL Certificates by Brian Ipsen</title>
		<link>http://cohesivelogic.com/2011/01/exchange-2010-single-name-ssl-certificates/comment-page-1/#comment-454</link>
		<dc:creator>Brian Ipsen</dc:creator>
		<pubDate>Sat, 29 Oct 2011 21:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://cohesivelogic.com/?p=501#comment-454</guid>
		<description>I am actually trying to implement this - as an upgrade from 2007 to 2010, and I had everything working before the upgrade. Now - in my test environment - I have tried this, but the internal outlook client pops up with a certificate warning on autodiscover.domain.com - even though the URL&#039;s have been set to the name of the certificate. So I wonder if outlook somehow automatically 
tries to https connect to autodiscover.xxxxx.yyy - where xxxxx.yyy is the domain part of the users email address...</description>
		<content:encoded><![CDATA[<p>I am actually trying to implement this &#8211; as an upgrade from 2007 to 2010, and I had everything working before the upgrade. Now &#8211; in my test environment &#8211; I have tried this, but the internal outlook client pops up with a certificate warning on autodiscover.domain.com &#8211; even though the URL&#8217;s have been set to the name of the certificate. So I wonder if outlook somehow automatically<br />
tries to https connect to autodiscover.xxxxx.yyy &#8211; where xxxxx.yyy is the domain part of the users email address&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Exchange 2010 &amp; Single Name SSL Certificates by Exchange Certificates</title>
		<link>http://cohesivelogic.com/2011/01/exchange-2010-single-name-ssl-certificates/comment-page-1/#comment-450</link>
		<dc:creator>Exchange Certificates</dc:creator>
		<pubDate>Fri, 30 Sep 2011 09:33:47 +0000</pubDate>
		<guid isPermaLink="false">http://cohesivelogic.com/?p=501#comment-450</guid>
		<description>[...] you will also need to change the autodiscovery URLs to all use the name covered by the SSL cert. Exchange 2010 &amp; Single Name SSL Certificates &#124; Cohesive Logic - The Microsoft Infrastructure Exp...               Reply With Quote &#160;   [...]</description>
		<content:encoded><![CDATA[<p>[...] you will also need to change the autodiscovery URLs to all use the name covered by the SSL cert. Exchange 2010 &amp; Single Name SSL Certificates | Cohesive Logic &#8211; The Microsoft Infrastructure Exp&#8230;               Reply With Quote &nbsp;   [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How To: Create PTR Entries for a Classless Reverse DNS Zone on Windows 2008 by What&#8217;s wrong with my reverse lookup zone? - Admins Goodies</title>
		<link>http://cohesivelogic.com/2009/11/how-to-create-ptr-entries-for-a-classless-reverse-dns-zone-on-windows-2008/comment-page-1/#comment-435</link>
		<dc:creator>What&#8217;s wrong with my reverse lookup zone? - Admins Goodies</dc:creator>
		<pubDate>Sun, 14 Aug 2011 10:07:52 +0000</pubDate>
		<guid isPermaLink="false">http://cohesivelogic.com/?p=140#comment-435</guid>
		<description>[...] http://cohesivelogic.com/2009/11/how-to-create-ptr-entries-for-a-classless-reverse-dns-zone-on-windo... [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://cohesivelogic.com/2009/11/how-to-create-ptr-entries-for-a-classless-reverse-dns-zone-on-windo.." rel="nofollow">http://cohesivelogic.com/2009/11/how-to-create-ptr-entries-for-a-classless-reverse-dns-zone-on-windo..</a>. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Windows Phone 7 SSL by Good-Bye Android &#124; MCB Systems</title>
		<link>http://cohesivelogic.com/2011/01/windows-phone-7-ssl/comment-page-1/#comment-298</link>
		<dc:creator>Good-Bye Android &#124; MCB Systems</dc:creator>
		<pubDate>Fri, 11 Feb 2011 22:18:18 +0000</pubDate>
		<guid isPermaLink="false">http://cohesivelogic.com/2011/01/windows-phone-7-ssl/#comment-298</guid>
		<description>[...] native RDP client (even my Windows Mobile 2003 phone had that). It doesn’t support StartSSL, but this article says I should be able to add the certificate. It also is late on delivering its first update, but [...]</description>
		<content:encoded><![CDATA[<p>[...] native RDP client (even my Windows Mobile 2003 phone had that). It doesn’t support StartSSL, but this article says I should be able to add the certificate. It also is late on delivering its first update, but [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Exchange 2010 &amp; Single Name SSL Certificates by Jeremy Phillips</title>
		<link>http://cohesivelogic.com/2011/01/exchange-2010-single-name-ssl-certificates/comment-page-1/#comment-239</link>
		<dc:creator>Jeremy Phillips</dc:creator>
		<pubDate>Wed, 05 Jan 2011 07:04:38 +0000</pubDate>
		<guid isPermaLink="false">http://cohesivelogic.com/?p=501#comment-239</guid>
		<description>Hey Devin, thanks for replying. In answer to your questions:

1) I actually didn&#039;t insist on mail.domain.com... As I stated it&#039;s an example FQDN. While you could use autodiscover.domain.com I&#039;m not sure many people would want to use that for OWA. While I agree with not using a CNAME I can&#039;t think of any downsides to using an SRV record myself, perhaps you could elucidate what&#039;s wrong with it?
2) I wrote this up for someone who has 4 mailboxes and uses their Exchange environment as a learning environment more than anything else. Not everyone wants to spend $90/year on SAN certs for extremely small environments.</description>
		<content:encoded><![CDATA[<p>Hey Devin, thanks for replying. In answer to your questions:</p>
<p>1) I actually didn&#8217;t insist on mail.domain.com&#8230; As I stated it&#8217;s an example FQDN. While you could use autodiscover.domain.com I&#8217;m not sure many people would want to use that for OWA. While I agree with not using a CNAME I can&#8217;t think of any downsides to using an SRV record myself, perhaps you could elucidate what&#8217;s wrong with it?<br />
2) I wrote this up for someone who has 4 mailboxes and uses their Exchange environment as a learning environment more than anything else. Not everyone wants to spend $90/year on SAN certs for extremely small environments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Exchange 2010 &amp; Single Name SSL Certificates by Devin L. Ganger</title>
		<link>http://cohesivelogic.com/2011/01/exchange-2010-single-name-ssl-certificates/comment-page-1/#comment-238</link>
		<dc:creator>Devin L. Ganger</dc:creator>
		<pubDate>Wed, 05 Jan 2011 06:05:31 +0000</pubDate>
		<guid isPermaLink="false">http://cohesivelogic.com/?p=501#comment-238</guid>
		<description>1) Why insist on mail.domain.com? If you set the domain name to autodiscover.domain.com, you can use that as the access URL, set the cert domain to autodisocver.domain.com, and have it all work without the SRV or CNAME redirect (which pops up a user-facing warning).

2) SAN certs from providers like GoDaddy are cheap enough that anyone running their own Exchange server really doesn&#039;t have an excuse for not buying one. I mean, you probably spent more money on the physical RAM to support that multi-role confguration!</description>
		<content:encoded><![CDATA[<p>1) Why insist on mail.domain.com? If you set the domain name to autodiscover.domain.com, you can use that as the access URL, set the cert domain to autodisocver.domain.com, and have it all work without the SRV or CNAME redirect (which pops up a user-facing warning).</p>
<p>2) SAN certs from providers like GoDaddy are cheap enough that anyone running their own Exchange server really doesn&#8217;t have an excuse for not buying one. I mean, you probably spent more money on the physical RAM to support that multi-role confguration!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Checking Exchange 2010 Database Health with PowerShell by Automatically Fixing FailedAndSuspended Exchange 2010 Databases with PowerShell &#124; Cohesive Logic - Business + Technology</title>
		<link>http://cohesivelogic.com/2010/08/checking-exchange-2010-database-health-with-powershell/comment-page-1/#comment-37</link>
		<dc:creator>Automatically Fixing FailedAndSuspended Exchange 2010 Databases with PowerShell &#124; Cohesive Logic - Business + Technology</dc:creator>
		<pubDate>Wed, 18 Aug 2010 18:42:13 +0000</pubDate>
		<guid isPermaLink="false">http://cohesivelogic.com/?p=252#comment-37</guid>
		<description>[...] Previous Post [...]</description>
		<content:encoded><![CDATA[<p>[...] Previous Post [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Note on Clustering Exchange 2010 by Matt</title>
		<link>http://cohesivelogic.com/2009/11/a-note-on-clustering-exchange-2010/comment-page-1/#comment-36</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Fri, 05 Feb 2010 17:50:59 +0000</pubDate>
		<guid isPermaLink="false">http://cohesivelogic.com/?p=156#comment-36</guid>
		<description>you&#039;d think there would be a setting that says if you configure manual DB activation, then never dismount the DB, if you lose majority.  that would solve my entire issue.

i want to use the DAG for DR purposes only, and that would do it.

but because of this issue, i have to continue to use 3rd party tools, or potentially MS DPM 2010.  bleh.  DAG&#039;s are just so easy.</description>
		<content:encoded><![CDATA[<p>you&#8217;d think there would be a setting that says if you configure manual DB activation, then never dismount the DB, if you lose majority.  that would solve my entire issue.</p>
<p>i want to use the DAG for DR purposes only, and that would do it.</p>
<p>but because of this issue, i have to continue to use 3rd party tools, or potentially MS DPM 2010.  bleh.  DAG&#8217;s are just so easy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Note on Clustering Exchange 2010 by Matt</title>
		<link>http://cohesivelogic.com/2009/11/a-note-on-clustering-exchange-2010/comment-page-1/#comment-35</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Fri, 05 Feb 2010 17:42:21 +0000</pubDate>
		<guid isPermaLink="false">http://cohesivelogic.com/?p=156#comment-35</guid>
		<description>Hi Jeremy,

Yes, because I have 3 offices, all with a local mailbox server.  I  need the mailbox server local for various reasons, mainly performance.

I really like the DAG feature in Exchange 2010, but it clearly was designed for the datacenter model, and not a multi-office model, at least those that run active/passive.

Got any ideas for me??</description>
		<content:encoded><![CDATA[<p>Hi Jeremy,</p>
<p>Yes, because I have 3 offices, all with a local mailbox server.  I  need the mailbox server local for various reasons, mainly performance.</p>
<p>I really like the DAG feature in Exchange 2010, but it clearly was designed for the datacenter model, and not a multi-office model, at least those that run active/passive.</p>
<p>Got any ideas for me??</p>
]]></content:encoded>
	</item>
</channel>
</rss>

