<div>
In Exchange 2010, all kind of Client request - OWA, ActiveSync, Outlook Anywhere and Outlook inside the domain is processed by IIS on the server. 
 
As you mentioned that you re-installed IIS, which means RPC virtual directory would be missing from IIS. 
 
Because RPC virtual directory is not present by default when we install Exchange Server. 
 
To resolve the issue, 
 
a. Go to Server manager =&gt; Features =&gt; Install RPC over HTTP proxy feature. 
 
Post it is installed, you should be able to view RPC virtual directory in IIS, make sure Basic Authentication is set for it. 
 
b. Now make sure, in EMC =&gt; Server Configuration =&gt; Client Access =&gt; Server Name =&gt; Properties =&gt; Outlook &nbsp;Anywhere tab =&gt; Outlook anywhere is enabled. 
 
For External Host Name: mail.domain.com (basically your OWA URL) and authentication should be BASIC. 
 
c. Services.msc =&gt; Restart &quot;Microsoft Exchange Service Host&quot; service. 
 
Post performing above steps, <a href="https://testconnectivity.microsoft.com/" rel="ugc nofollow">https://testconnectivity.microsoft.com/</a>&nbsp;=&gt; Exchange Server tab =&gt; Outlook Connectivity test =&gt; Provide credential of any of the user =&gt; And make sure &quot;Use Autodiscover to detect server settings&quot; radio button is checked. 
 
If the above test passes then we are good to go.
</div>

<div>
RPC HTTP was installed over the weekend, I verified it just not it's already in the feature list. 
 
EMC shows OA is enabled, security is set properly to your notes. 
 
Rebooted the service for fun, tried again, no love. 
 
My connectivity tests are as follows: 
 

<pre><code class="code-10 nolinks" id="code-20-40450590-1">&quot;e Microsoft Connectivity Analyzer is testing Exchange ActiveSync.
 	The Exchange ActiveSync test failed.
 	
	Additional Details
 	
Elapsed Time: 6564 ms.
 	
	Test Steps
 	
	Attempting the Autodiscover and Exchange ActiveSync test (if requested).
 	Testing of Autodiscover for Exchange ActiveSync failed.
 	
	Additional Details
 	
	Test Steps
 	
	Attempting each method of contacting the Autodiscover service.
 	The Autodiscover service couldn't be contacted successfully by any method.
 	
	Additional Details
 	
	Test Steps
 	
	Attempting to test potential Autodiscover URL https://:443/Autodiscover/Autodiscover.xml
 	Testing of this potential Autodiscover URL failed.
 	
	Additional Details
 	
	Test Steps
 	
	Attempting to resolve the host name in DNS.
 	The host name resolved successfully.
 	
	Additional Details
	Testing TCP port 443 on host mydomain.com to ensure it's listening and open.
 	The port was opened successfully.
 	
	Additional Details
	Testing the SSL certificate to make sure it's valid.
 	The SSL certificate failed one or more certificate validation checks.
 	
	Additional Details
 	
	Test Steps
	Attempting to test potential Autodiscover URL https://autodiscover.r:443/Autodiscover/Autodiscover.xml
 	Testing of this potential Autodiscover URL failed.
 	
	Additional Details
 	
	Test Steps
 	
	Attempting to resolve the host name autodiscover..com in DNS.
 	The host name resolved successfully.
 	
	Additional Details
	Testing TCP port 443 on host autodiscover..com to ensure it's listening and open.
 	The specified port is either blocked, not listening, or not producing the expected response.
 	 Tell me more about this issue and how to resolve it
 	
	Additional Details
 	
A network error occurred while communicating with the remote host.
Elapsed Time: 27 ms.
	Attempting to contact the Autodiscover service using the HTTP redirect method.
 	The attempt to contact Autodiscover using the HTTP Redirect method failed.
 	
	Additional Details
 	
	Test Steps
 	
	Attempting to resolve the host name autodiscover..com in DNS.
 	The host name resolved successfully.
 	
	Additional Details
	Testing TCP port 80 on host autodiscover..com to ensure it's listening and open.
 	The specified port is either blocked, not listening, or not producing the expected response.
 	 Tell me more about this issue and how to resolve it
 	
	Additional Details
	Attempting to contact the Autodiscover service using the DNS SRV redirect method.
 	The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.
 	
	Additional Details
 	
	Test Steps
 	
	Attempting to locate SRV record _autodiscover._tcp.in DNS.
 	The Autodiscover SRV record wasn't found in DNS.
 	 Tell me more about this issue and how to resolve it
 	
	Additional Details
 	
Elapsed Time: 97 ms.&quot;
</code></pre>
 
While not running perfectly, I don't see why it would cause local issues in that case, but not OWA issues. &nbsp;Just to reiterate, OWA is 100%. &nbsp;That's the part that is baffling (and I haven't looked at the connectivity test yet at this point, this is news to me that some parts are failing). &nbsp;Ideas on what to trudge forward with?
</div>

<div>
Created a new SRV record, which was missing in the DNS on the local server. &nbsp;Still have the same failures in the test connectivity for SRV record. &nbsp;Restarted the services. &nbsp;Restarted IIS. &nbsp;Check client outlook, issue persistent. 
 
Any other ideas?
</div>

<div>
Just noted that when I ran Get-CAS internaluri I returned a null result, so I am checking that their mail server is configured correctly with some of these commands: 
 
<a href="http://mshiyas.wordpress.com/2010/07/06/how-to-configure-and-verify-autodiscover-for-exchange-2007-and-2010/" rel="ugc">http://mshiyas.wordpress.com/2010/07/06/how-to-configure-and-verify-autodiscover-for-exchange-2007-and-2010/</a> 
 
If you have other ideas I should track down outside of this, let m eknow,
</div>

<div>
In fact, if I run: 
 
Get-AutodiscoverVirtualDirectory &quot;SERVERNAME\*&quot; | fl 
 
It shows nothing on the internal or external URL. &nbsp;Why?!? &nbsp;I've told it to set each, but it's not listening.
</div>

<div>
But then I found this command: 
 
Get-ClientAccessServer casserver1 | fl *InternalUri* 
 
Which displays the proper location. So now I am back at square one. &nbsp;Help!
</div>

<div>
I've set up an outlook profile this time around using the IP of the serve rinstead of the FQDN. &nbsp;On saving and exiting, I now get &quot;cannot start microsoft outlook cannot open the outlook window the set of folders cannot be opened microsoft exchange is not available. either there are network problems or the exchange server is down for maintenance&quot; 
 
I ran and nslookup on a client computer internally, and they still return the external IP for autodiscover.domain.com 
 
Ideas?
</div>

<div>
Glad you got it resolved. Yep. I was just going through your EXRCA report for earlier and noticed the SSL was wrong.
</div>

<div>
Noted a misconfigured item in the services on my own, outside of what was being discussed.
</div>

<div>
<div class="content wysiwyg-content">
Hi all, 
 
I spent the weekend fixing some major IIS issues and Exhange OWA issues for a client. &nbsp;They had removed IIS compeltely from the server, and I re set it up and made sure OWA was working for all users. &nbsp;EMC and EMS at one point wouldn't connect to the (local) SBS server. &nbsp;All that has been resolved. &nbsp;OWA is working 100%. 
 
What the issue is right now, is none of the outlook clients are working. &nbsp;Setting them up resolves the local server instantly, but when they try to load I get prompted for the local account credentials. &nbsp;Tried running different profiles, different users, etc. &nbsp;Tried resetting permissions and passwords. &nbsp;I get &quot;Cannot start Microsoft....You do not have permission to log on&quot;. 
 
Let me know if you need more details!
</div>
</div>

Hi all, 

I spent the weekend fixing some major IIS issues and Exhange OWA issues for a client.  They had removed IIS compeltely from the server, and I re set it up and made sure OWA was working for all users.  EMC and EMS at one point wouldn't connect to the (local) SBS server.  All that has been resolved.  OWA is working 100%.

What the issue is right now, is none of the outlook clients are working.  Setting them up resolves the local server instantly, but when they try to load I get prompted for the local account credentials.  Tried running different profiles, different users, etc.  Tried resetting permissions and passwords.  I get "Cannot start Microsoft....You do not have permission to log on".

Let me know if you need more details!

All outlook clients can't connect to exchange

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.