<?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: Configuring Outlook Anywhere for Exchange 2007 SP1</title>
	<atom:link href="http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/</link>
	<description>This blog is dedicated to Microsoft Exchange</description>
	<lastBuildDate>Thu, 02 Feb 2012 00:44:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Exchange Genie</title>
		<link>http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/comment-page-3/#comment-28269</link>
		<dc:creator>Exchange Genie</dc:creator>
		<pubDate>Thu, 19 Jan 2012 00:54:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.exchange-genie.com/?p=39#comment-28269</guid>
		<description>Jim... I want to validate I understand. You currently have a local exchange setup which hosts about 20 mailboxes and have merged with another company that also has Exchange. You now need to reconfigure the clients so thier OL profile point to the new setup?  1. is the email address the same or different for the external domain? 2. Are you removing your Exchange server? 3. Are you trying to have two profiles one to the local and one to the remote?</description>
		<content:encoded><![CDATA[<p>Jim&#8230; I want to validate I understand. You currently have a local exchange setup which hosts about 20 mailboxes and have merged with another company that also has Exchange. You now need to reconfigure the clients so thier OL profile point to the new setup?  1. is the email address the same or different for the external domain? 2. Are you removing your Exchange server? 3. Are you trying to have two profiles one to the local and one to the remote?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Laird</title>
		<link>http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/comment-page-3/#comment-28225</link>
		<dc:creator>Jim Laird</dc:creator>
		<pubDate>Wed, 18 Jan 2012 14:05:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.exchange-genie.com/?p=39#comment-28225</guid>
		<description>Hi, 
Some very detailed and helpful information here, and I&#039;m hoping you can assist me with a very frustrating problem I&#039;m having.

I have a local domain with about 20 mail users.  Windows Server 2008. Exchange 2007.  Outlook users connect to exchange over the LAN no problem at all...  Additionally, they can connect from home or outside the office using OLA with no issues.  Everything appears to run just as it should.

Recently however, my organisation was purchased by a larger company.  They have set up mail accounts for all the users, and have configured their OLA.  I have tried this at home and was able to successfully connect using OLA.

For the users in my office i have tried everything I can think of to enable them to connect to the external domain.  I have tried creating new outlook profiles etc, but the result is always the same.  For domain users, when trying to configure an external OLA account, the server always seems to default to the local server, and not the remote server.  This is driving me insane, so any assistance would be very helpful.

Jim</description>
		<content:encoded><![CDATA[<p>Hi,<br />
Some very detailed and helpful information here, and I&#8217;m hoping you can assist me with a very frustrating problem I&#8217;m having.</p>
<p>I have a local domain with about 20 mail users.  Windows Server 2008. Exchange 2007.  Outlook users connect to exchange over the LAN no problem at all&#8230;  Additionally, they can connect from home or outside the office using OLA with no issues.  Everything appears to run just as it should.</p>
<p>Recently however, my organisation was purchased by a larger company.  They have set up mail accounts for all the users, and have configured their OLA.  I have tried this at home and was able to successfully connect using OLA.</p>
<p>For the users in my office i have tried everything I can think of to enable them to connect to the external domain.  I have tried creating new outlook profiles etc, but the result is always the same.  For domain users, when trying to configure an external OLA account, the server always seems to default to the local server, and not the remote server.  This is driving me insane, so any assistance would be very helpful.</p>
<p>Jim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Exchange Genie</title>
		<link>http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/comment-page-3/#comment-28189</link>
		<dc:creator>Exchange Genie</dc:creator>
		<pubDate>Wed, 18 Jan 2012 02:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.exchange-genie.com/?p=39#comment-28189</guid>
		<description>So there is a fuzzy answer... In theory autodiscover should run and update the information however that does not seem to work properly and depends on what version of Outlook you are using and if you have the right fixes.  An easy way to force the client would be to run a repair on the client which will force autod to run and should update the client with the correct info or you could just manually change the url. Neither of those are good answers but are valid ones.</description>
		<content:encoded><![CDATA[<p>So there is a fuzzy answer&#8230; In theory autodiscover should run and update the information however that does not seem to work properly and depends on what version of Outlook you are using and if you have the right fixes.  An easy way to force the client would be to run a repair on the client which will force autod to run and should update the client with the correct info or you could just manually change the url. Neither of those are good answers but are valid ones.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stanley</title>
		<link>http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/comment-page-3/#comment-28046</link>
		<dc:creator>Stanley</dc:creator>
		<pubDate>Mon, 16 Jan 2012 13:41:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.exchange-genie.com/?p=39#comment-28046</guid>
		<description>hi, thanks very much for your response. I just checked the autodiscover sitescope for our CAS servers &amp; the sitescope is already set to our AD sites for all our CAS servers &amp; looks like no changes are required from autodiscover point of view.
Regarding Outlook anywhere, it is only enabled on couple of CAS servers which do not belong to our ADsite &amp; all out workstations have outlook anywhere proxy URL form that CAS server. My question is if i enable outlook anywhere on one of my CAS server in my AD site I am assuming that the new outlook clients when running autodiscover for firsttime it will choose the new outlook anywhere URL i set for my CAS servers but how about the exsiting outlook clients which already has outlookanywhere URL from different site? how do i go about updating already existing outlook clients to choose the newly configured Outlook anywhere url i will be enabling on one of the cas server in my site?</description>
		<content:encoded><![CDATA[<p>hi, thanks very much for your response. I just checked the autodiscover sitescope for our CAS servers &amp; the sitescope is already set to our AD sites for all our CAS servers &amp; looks like no changes are required from autodiscover point of view.<br />
Regarding Outlook anywhere, it is only enabled on couple of CAS servers which do not belong to our ADsite &amp; all out workstations have outlook anywhere proxy URL form that CAS server. My question is if i enable outlook anywhere on one of my CAS server in my AD site I am assuming that the new outlook clients when running autodiscover for firsttime it will choose the new outlook anywhere URL i set for my CAS servers but how about the exsiting outlook clients which already has outlookanywhere URL from different site? how do i go about updating already existing outlook clients to choose the newly configured Outlook anywhere url i will be enabling on one of the cas server in my site?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Exchange Genie</title>
		<link>http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/comment-page-3/#comment-27714</link>
		<dc:creator>Exchange Genie</dc:creator>
		<pubDate>Fri, 13 Jan 2012 02:31:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.exchange-genie.com/?p=39#comment-27714</guid>
		<description>Arun,

 I would need a bit more information than you have provided. What is you setup like, are you using a public cert or private cert.. have you looked at the fw on the CAS box ? Have you looked in the IIS logs for OA connections? Where did you get your cert.. etc</description>
		<content:encoded><![CDATA[<p>Arun,</p>
<p> I would need a bit more information than you have provided. What is you setup like, are you using a public cert or private cert.. have you looked at the fw on the CAS box ? Have you looked in the IIS logs for OA connections? Where did you get your cert.. etc</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Exchange Genie</title>
		<link>http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/comment-page-3/#comment-27713</link>
		<dc:creator>Exchange Genie</dc:creator>
		<pubDate>Fri, 13 Jan 2012 02:29:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.exchange-genie.com/?p=39#comment-27713</guid>
		<description>Stanley,

 Autodiscover works in a number of ways depending if you are domain joined or not... For domain joined machines autod will lookup the SCP connection in AD. You can configure a site scope to have client pull from the CAS in thier AD site (http://technet.microsoft.com/en-us/library/aa998575.aspx) however if this cannot be determined it will randomly pull that information. The AutoD lookup will look for the OA url that is in the AD site assocaited with the CAS/MBX for that site and return that information to the user. 
For a non domain joined user a DNS record is used for Autodiscover.domain.com this will be based on the primary SMTP address of the users mailbox, so if the primary is xyz.com that the Outlook client will lookup autodiscover.xyz.com to populate the urls for a number of items like OA, offline address book, web services etc..
So in short, you can use site scopes for the clients that are domain joined and DNS for non domain joined or exernal users.. I wrote this blog back in 2007 that explain AutoD in more details (http://www.exchange-genie.com/2007/07/exchange-2007-autodiscover-service-part-1/ )</description>
		<content:encoded><![CDATA[<p>Stanley,</p>
<p> Autodiscover works in a number of ways depending if you are domain joined or not&#8230; For domain joined machines autod will lookup the SCP connection in AD. You can configure a site scope to have client pull from the CAS in thier AD site (<a href="http://technet.microsoft.com/en-us/library/aa998575.aspx" rel="nofollow">http://technet.microsoft.com/en-us/library/aa998575.aspx</a>) however if this cannot be determined it will randomly pull that information. The AutoD lookup will look for the OA url that is in the AD site assocaited with the CAS/MBX for that site and return that information to the user.<br />
For a non domain joined user a DNS record is used for Autodiscover.domain.com this will be based on the primary SMTP address of the users mailbox, so if the primary is xyz.com that the Outlook client will lookup autodiscover.xyz.com to populate the urls for a number of items like OA, offline address book, web services etc..<br />
So in short, you can use site scopes for the clients that are domain joined and DNS for non domain joined or exernal users.. I wrote this blog back in 2007 that explain AutoD in more details (<a href="http://www.exchange-genie.com/2007/07/exchange-2007-autodiscover-service-part-1/" rel="nofollow">http://www.exchange-genie.com/2007/07/exchange-2007-autodiscover-service-part-1/</a> )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stanley</title>
		<link>http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/comment-page-3/#comment-27559</link>
		<dc:creator>Stanley</dc:creator>
		<pubDate>Wed, 11 Jan 2012 14:52:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.exchange-genie.com/?p=39#comment-27559</guid>
		<description>I need some help / guidance with setting up Outlook Anywhere? Here is my setup.

We have a forest with 3 domains &amp; each domain is managed by different teams in different countries.we share same exchange org but each domain has it&#039;s own set of MBX, CAS &amp; HUB servers etc. For Ex ABC.Contoso.com, JKL.contoso.com &amp; XYZ.contoso.com. I am admin for XYZ domain. Currently Outlook Anywhere is Enabled on ABC CAS servers &amp; all out workstations in XYZ have ABC proxy settings in outlook using autodiscover to connect to outlook anywhere. Also Autodisocver record is pointing to ABC CAS servers.

My question is we want to enable Outlook anywhere on our Own CAS servers in XYZ domain &amp; all our workstation should be able to use XYZ CAS server outlook Anywhere Proxy URL when doing autodiscover. what is the best way to acheive this? I am looking for some guidance here as i dont want to mess up my production environment.</description>
		<content:encoded><![CDATA[<p>I need some help / guidance with setting up Outlook Anywhere? Here is my setup.</p>
<p>We have a forest with 3 domains &amp; each domain is managed by different teams in different countries.we share same exchange org but each domain has it&#8217;s own set of MBX, CAS &amp; HUB servers etc. For Ex ABC.Contoso.com, JKL.contoso.com &amp; XYZ.contoso.com. I am admin for XYZ domain. Currently Outlook Anywhere is Enabled on ABC CAS servers &amp; all out workstations in XYZ have ABC proxy settings in outlook using autodiscover to connect to outlook anywhere. Also Autodisocver record is pointing to ABC CAS servers.</p>
<p>My question is we want to enable Outlook anywhere on our Own CAS servers in XYZ domain &amp; all our workstation should be able to use XYZ CAS server outlook Anywhere Proxy URL when doing autodiscover. what is the best way to acheive this? I am looking for some guidance here as i dont want to mess up my production environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arun Chaudhary</title>
		<link>http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/comment-page-3/#comment-27514</link>
		<dc:creator>Arun Chaudhary</dc:creator>
		<pubDate>Wed, 11 Jan 2012 06:22:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.exchange-genie.com/?p=39#comment-27514</guid>
		<description>Hi Man, Its a good blog to configure the exchange server.
I follow your steps but my outlook anywhere is not working fine, in finishing when i look for connection status its still showing TCP/IP, but when i go offline n come back online in outlook, it show HTTP/HTTPS, but its changed again when outlook connect to the exchange server
</description>
		<content:encoded><![CDATA[<p>Hi Man, Its a good blog to configure the exchange server.<br />
I follow your steps but my outlook anywhere is not working fine, in finishing when i look for connection status its still showing TCP/IP, but when i go offline n come back online in outlook, it show HTTP/HTTPS, but its changed again when outlook connect to the exchange server</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: how to set up outlook express mail</title>
		<link>http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/comment-page-3/#comment-21883</link>
		<dc:creator>how to set up outlook express mail</dc:creator>
		<pubDate>Tue, 15 Nov 2011 03:20:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.exchange-genie.com/?p=39#comment-21883</guid>
		<description>Hi there and thank you time and effort in helping out the not so Exchange-brilliant minds.
I have Exchange 2007 SP1, Windows server 2008, CAS running on the same server. Go daddy UCC certificate. OWA is working fine. all the iphones and Blackberry phones are synching fine. I enabled Outlook anywhere and rpc/http is installed. It works internally but externally, I keep getting prompted for the password with no success!
I saw some posting with similar symptoms but no clear resolution.
Any advise?</description>
		<content:encoded><![CDATA[<p>Hi there and thank you time and effort in helping out the not so Exchange-brilliant minds.<br />
I have Exchange 2007 SP1, Windows server 2008, CAS running on the same server. Go daddy UCC certificate. OWA is working fine. all the iphones and Blackberry phones are synching fine. I enabled Outlook anywhere and rpc/http is installed. It works internally but externally, I keep getting prompted for the password with no success!<br />
I saw some posting with similar symptoms but no clear resolution.<br />
Any advise?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Exchange Genie</title>
		<link>http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/comment-page-3/#comment-18299</link>
		<dc:creator>Exchange Genie</dc:creator>
		<pubDate>Thu, 21 Jul 2011 12:13:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.exchange-genie.com/?p=39#comment-18299</guid>
		<description>The most common reason that I have seen on prompting is when clients do not trust the certificate on the Exchange server when using rpc/https.  If you where on Exchange 2010 I would say the issue is that mapi encryption is off on Outlook 2003 by default and on with Outlook 2007/2010. You can check that setting on the OL 2003 client but that should not be an issue with Exchange 2007.
What SP are you on and what RU?</description>
		<content:encoded><![CDATA[<p>The most common reason that I have seen on prompting is when clients do not trust the certificate on the Exchange server when using rpc/https.  If you where on Exchange 2010 I would say the issue is that mapi encryption is off on Outlook 2003 by default and on with Outlook 2007/2010. You can check that setting on the OL 2003 client but that should not be an issue with Exchange 2007.<br />
What SP are you on and what RU?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

