I have one E2K13 mailbox server that I continue to have issues with.  I've tried uninstalling Exchange, uninstall all added roles/features and reinstalling.  The issue is that internal Outlook clients cannot connect.  If I create the mailbox on another MBx server then I can connect to them no problem.  It actually damages the mailboxes, meaning that if I move a mailbox to this MBx server (and can't connect, of course) and then move to working MBx server, I can never again connect to the mailbox with Outlook.

OWA works great connecting.  No errors/warnings in the event logs.  I found this cmdlet that actually shows an issue with the Outlook.Protocol tests.  The other MBx server show healthy.

Any ideas how to troubleshoot this?

[PS] C:\Windows\system32>Get-ServerHealth -Identity Servername -HealthSet Outlook.Protocol

Server          State           Name                 TargetResource       HealthSetName   AlertValue ServerComp
                                                                                                     onent
------          -----           ----                 --------------       -------------   ---------- ----------
Servername NotApplicable   OutlookArchiveDee...                      Outlook.Prot... Unhealthy  None
Servername NotApplicable   OutlookMailboxDee...                      Outlook.Prot... Unhealthy  None
Servername NotApplicable   OutlookSelfTestMo...                      Outlook.Prot... Unhealthy  None

Hi

Please run "test-mapiconnectivity" and check event viewer on exchange server.

http://technet.microsoft.com/en-us/library/bb123681(v=exchg.150).aspx

If you have any feedback on our support, please click here

Test ran quickly and successfully.  I also uninstalled Exchange, removed the server from the domain, readded, and reinstalled.  As soon as the install finished and rebooted, I ran the server health check with the same Outlook.Protocol error.  No errors in the event log.

Any other ideas?  Thank you so far for your suggestions.

[PS] C:\Windows\system32>Test-MapiConnectivity -Server "NJEDSNEXMBX01" | FL


RunspaceId  : 4a8edfa7-a9fb-4457-b485-0fbb642af04c
Server      : NJEDSNEXMBX01
Database    : Mailbox Database 0594127717
Mailbox     : SystemMailbox{959887ee-e0ee-4616-969e-829d1531dfcf}
MailboxGuid : d52bb7a2-4ec2-418f-91bd-83fe0663f8d3
IsArchive   : False
Result      : Success
Latency     : 00:00:00.0288605
Error       :
Identity    :
IsValid     : True
ObjectState : New

Nobody has any ideas yet?  I'm still stuck.  I ran a connectivity analyzer and got this message.  It only applies to this MBx server, the other one returns the ping just fine.

RPC Proxy can't be pinged. Additional Details Additional Details: A Web exception occurred because an HTTP 404 - NotFound response was received from IIS7.
Headers received:
Transfer-Encoding: chunked
request-id: 5e6e4063-3768-48c8-9fce-f687411e30a0
X-CalculatedBETarget: njedsnexmbx01.contoso.com
X-DiagInfo: NJEDSNEXMBX01
X-BEServer: NJEDSNEXMBX01
X-FEServer: NJEDSNEXCAS01
Cache-Control: private
Content-Type: text/html
Date: Wed, 10 Jul 2013 04:49:27 GMT
Server: Microsoft-IIS/7.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET

Well, it looks like less people are using Exchange now since this thread didn't get any other help or ideas.  I fixed the problem finally after comparing everything between the two servers..

The issue is that an uninstall doesn't remove the IIS application pools for Exchange.  The reinstall didn't associate the app pool with the RPC directories.