Outlook Anywhere Broken Exchange 2013

1. Everything else works OWA, Auto, ECP OAB, ETC
2. testexchangeconnectivity.com Outlook Auto and Connect  WORKS!!  :(
3. YES my outlook clients are version correct
4. Everything is set to NTLM
5. See # 1.

My last effort before calling M$oft is to remove outlook anywhere and reboot, then re-add it per http://www.petri.co.il/forums/showthread.php?t=43309

I have review and acted on these tidbits, without success:
http://clintboessen.blogspot.com/2009/06/outlook-anywhere-keeps-prompting-for.html
http://msexchangeguru.com/2013/01/10/e2013-outlook-anywhere/

Sadly, when ever I try to run Test-OutlookConnectivity I get:
Failed to find the probe result for invoke now request id 3096f04eb0604142bc7f191cf2a40ece and probe
workdefinition id 172.

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

I have posted on a few other forums, Technet, Etc.  Hoepfully someone has hit the same issue.
PlysakerGEEKAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
PlysakerConnect With a Mentor GEEKAuthor Commented:
The fix took microsoft 3 hours.

Interestingly, they do this when they start:

Get-ClientAccessServer | fl > c:\cas.txt
Get-WebVirtualDirectory | fl > c:\web.txt
Get-OabVirtualDirectory | fl > c:\oab.txt
Get-OutlookAnywhere | fl > c:\any.txt
Get-OabVirtualDirectory | fl > c:\oab.txt
Get-OutlookProvider > c:\provider.txt
Get-ExchangeCertificate | fl > c:\cert.txt

Which they then have you send them.

Support found an issue with my INTERNAL Autodiscover URL, and fixed that.

Set-ClientAccessServer -Identity XMAIL -AutodiscoverServiceInternalUri https://xmail.companyinc.com/autodiscover/autodiscover.xml

Open in new window


Then a number of Set-Outlook anywhere strings, the golden bullet being that INTERNAL Client Auth needs to be set at NTLM.  By default, it sets up as NEGOTIATE via the ECP.

[PS] Set-OutlookAnywhere -Identity "XMAIL\RPC (default Web site)" -InternalClientAuthenticationMethod NTLM  -IISAuthenticationMethods  Basic, NTLM, Negotiate

Open in new window


Correct (working) Settings:

Identity                     ExternalClientAuthenticationMethod InternalClientAuthenticationMethod IISAuthenticationMet
                                                                                                   hods
--------                     ---------------------------------- ---------------------------------- --------------------
XMAIL\Rpc (Default Web Site)                          Negotiate                               Ntlm {Basic, Ntlm, Neg...

Open in new window

0
 
Simon Butler (Sembee)ConsultantCommented:
Standard thing for Outlook Anywhere is to disable it, then remove the RPC Proxy, then the virtual directories. Run IISRESET afterwards. Then put it all back. That usually corrects things. Don't make registry changes - that is for Exchange 2003 only (never had to do them on higher versions of Exchange).

Simon.
0
 
PlysakerGEEKAuthor Commented:
thanks Simon, I will attempt tonight.  Do I have to remove ALL the directories? Everything else works!
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
PlysakerGEEKAuthor Commented:
what in the world does this mean?  Google gets me nada

WARNING: Failed to find the probe result for invoke now request id 6c16f7bd5df143e7b7d713cd97fa64b7 and probe
workdefinition id 173.
0
 
Simon Butler (Sembee)ConsultantCommented:
Sorry - that is late night posting for you, I should have been more clear.
Remove the RPC and RPC With Cert virtual directories as those are the two for Outlook Anywhere. Then run IISRESET and enable Outlook Anywhere again.

When did you get that error message, you need to be clear.

Simon.
0
 
PlysakerGEEKAuthor Commented:
Right, sorry.  When I run the

Test-OutlookConnectivity -ProbeIdentity "OutlookSelfTestProbe"

Or any test-outlook  I get some form of that error.  I have created the test user and my San cert covers all the necessary suspects.
0
 
PlysakerGEEKAuthor Commented:
I'll reward myself.  Not sure if that is legal...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.