<?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: Configure automatic login on OCS 2007</title>
	<atom:link href="http://ukstokes.com/blog/2009/04/11/configure-automatic-login-on-ocs-2007/feed/" rel="self" type="application/rss+xml" />
	<link>http://ukstokes.com/blog/2009/04/11/configure-automatic-login-on-ocs-2007/</link>
	<description>tech stuff from a tech bloke</description>
	<lastBuildDate>Fri, 18 Jun 2010 16:00:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Orval Eske</title>
		<link>http://ukstokes.com/blog/2009/04/11/configure-automatic-login-on-ocs-2007/comment-page-1/#comment-11725</link>
		<dc:creator>Orval Eske</dc:creator>
		<pubDate>Tue, 15 Jun 2010 14:58:31 +0000</pubDate>
		<guid isPermaLink="false">http://ukstokes.com/blog/?p=217#comment-11725</guid>
		<description>I’m happy! It is pleasant to see somebody extremely educated about what they do. Maintain up the excellent function and I’ll return for far more! Thank you!</description>
		<content:encoded><![CDATA[<p>I’m happy! It is pleasant to see somebody extremely educated about what they do. Maintain up the excellent function and I’ll return for far more! Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ben</title>
		<link>http://ukstokes.com/blog/2009/04/11/configure-automatic-login-on-ocs-2007/comment-page-1/#comment-9689</link>
		<dc:creator>ben</dc:creator>
		<pubDate>Thu, 25 Mar 2010 14:25:41 +0000</pubDate>
		<guid isPermaLink="false">http://ukstokes.com/blog/?p=217#comment-9689</guid>
		<description>Now you&#039;ve gone and confused me :)

You would be able to use Communicator Web Access, or &#039;manual login&#039; to the OCS client, whatever your domain name or username convention is? 

&quot;Do we not need External DNS entries for Automatic logons only?&quot;

The external DNS entries are for automatic login, and for other OCS installations to locate your Edge server.</description>
		<content:encoded><![CDATA[<p>Now you've gone and confused me <img src='http://ukstokes.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>You would be able to use Communicator Web Access, or 'manual login' to the OCS client, whatever your domain name or username convention is? </p>
<p>"Do we not need External DNS entries for Automatic logons only?"</p>
<p>The external DNS entries are for automatic login, and for other OCS installations to locate your Edge server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Favad Qaisar</title>
		<link>http://ukstokes.com/blog/2009/04/11/configure-automatic-login-on-ocs-2007/comment-page-1/#comment-9465</link>
		<dc:creator>Favad Qaisar</dc:creator>
		<pubDate>Sat, 20 Mar 2010 05:21:49 +0000</pubDate>
		<guid isPermaLink="false">http://ukstokes.com/blog/?p=217#comment-9465</guid>
		<description>Hey Ben, thank you for the reply. Since I cannot my .local domain, the only option would be to use external DNS suffix i.e @domain.com 

However, I am still a bit curious. Since I can login with .local suffix externally using Communicator Web Access set up using Reverse Proxy, why can I not login in Office Communicator using manual configuration. Do we not need External DNS entries for Automatic logons only?

Favad</description>
		<content:encoded><![CDATA[<p>Hey Ben, thank you for the reply. Since I cannot my .local domain, the only option would be to use external DNS suffix i.e @domain.com </p>
<p>However, I am still a bit curious. Since I can login with .local suffix externally using Communicator Web Access set up using Reverse Proxy, why can I not login in Office Communicator using manual configuration. Do we not need External DNS entries for Automatic logons only?</p>
<p>Favad</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ben</title>
		<link>http://ukstokes.com/blog/2009/04/11/configure-automatic-login-on-ocs-2007/comment-page-1/#comment-9438</link>
		<dc:creator>ben</dc:creator>
		<pubDate>Fri, 19 Mar 2010 15:47:55 +0000</pubDate>
		<guid isPermaLink="false">http://ukstokes.com/blog/?p=217#comment-9438</guid>
		<description>Well, if you don&#039;t want to change users principal names in AD you would have to buy the domain internal.ad and then set up the SRV records for it in external DNS. 

[code]_tcp._sipinternal.yourdomain.com -- sip.internal.ad (0 0 5061)
_tcp._sipinternaltls .yourdomain.com -- sip.internal.ad (0 0 5061)[/code]

However this does expose your internal namespace to the internet, this may or may not bother you.

This is assuming that you&#039;re using a domain suffix that can be bought from domain registries - in my example internal.ads, the .ads domain isn&#039;t available.</description>
		<content:encoded><![CDATA[<p>Well, if you don't want to change users principal names in AD you would have to buy the domain internal.ad and then set up the SRV records for it in external DNS. </p>
<pre class="brush: plain;">_tcp._sipinternal.yourdomain.com -- sip.internal.ad (0 0 5061)
_tcp._sipinternaltls .yourdomain.com -- sip.internal.ad (0 0 5061)</pre>
<p>However this does expose your internal namespace to the internet, this may or may not bother you.</p>
<p>This is assuming that you're using a domain suffix that can be bought from domain registries - in my example internal.ads, the .ads domain isn't available.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Favad Qaisar</title>
		<link>http://ukstokes.com/blog/2009/04/11/configure-automatic-login-on-ocs-2007/comment-page-1/#comment-9382</link>
		<dc:creator>Favad Qaisar</dc:creator>
		<pubDate>Thu, 18 Mar 2010 10:55:58 +0000</pubDate>
		<guid isPermaLink="false">http://ukstokes.com/blog/?p=217#comment-9382</guid>
		<description>Ben, this is indeed a very useful post, and hats off to you for writing in detail; about a pretty common scenario.

1. Would it be possible to use a Communicator to login externally with manual settings using sign-in names like user@internal.ad, since I&#039;m able to do it through my Communicator Web Acess?

2. What DNS entries I would need to make that happen? I have OCS 2007 R2. Standard Edition, Communicator Web Access, Edge, Mediation and Internal CA besides Public CA Wild Card Certificate for my domian.

Thanking you in anticipation

Favad</description>
		<content:encoded><![CDATA[<p>Ben, this is indeed a very useful post, and hats off to you for writing in detail; about a pretty common scenario.</p>
<p>1. Would it be possible to use a Communicator to login externally with manual settings using sign-in names like <a href="mailto:user@internal.ad">user@internal.ad</a>, since I'm able to do it through my Communicator Web Acess?</p>
<p>2. What DNS entries I would need to make that happen? I have OCS 2007 R2. Standard Edition, Communicator Web Access, Edge, Mediation and Internal CA besides Public CA Wild Card Certificate for my domian.</p>
<p>Thanking you in anticipation</p>
<p>Favad</p>
]]></content:encoded>
	</item>
</channel>
</rss>
