Turns out, it was an IIS configuration issue that appeared most likely after running the Network Preparation / Outlook Anywhere wizards. I opened IIS, expanded the default website, and inspected the authentication options for RPC and RPC with cert... both had only 'basic authentication' checked, which I was fairly certain would not work with Remote Desktop web access services. Enabling 'Windows Authentication' and performing an iisreset did the trick... but after a few minutes, it got set back to disabled! An event in the logs from "MSExchange RPC Over HTTP Autoconfig" source indicated that the settings for Outlook Anywhere had been updated, setting it back to Basic only!
The fix that eventually worked (and stuck) was to make the following change in the Exchange Management Shell:
Get-OutlookAnywhere | Set-OutlookAnywhere –IISAuthenticationMethods: Basic, ntlm
After making that change, it may not show up in IIS right away... wait a few minutes, and that same Autoconfig service will update IIS for you, this time adding both Basic and Windows authentication. Voila!
Thank you very much, you solved a nasty problem I had on a SBS 2011 machine.
ReplyDeleteNice one.
ReplyDeleteI work in the same sort of role, based in a different country. The EMS command didn't work for me, but it did prompt me to examine the authentication methods.
Thanks a lot.
"Spent a few hours of my life that I never should have, figuring out this little gem" Wow, that's for sure!
ReplyDeleteAll I can say is Aaaargh! and thank you for this post, it has save me from total loss of sanity. I have experienced quite a few gems myself during an SBS 2K3 to 2K11 migration.
Unbelievable how many people including myself have lost dozens of hours on this. I have rebuilt a server a server from scratch until I found this post. Thanks a million. Shame on you Microsoft. Why isnt this on their KB anywhere, or resolved with a patch?
ReplyDeleteThank you sooo much... This one had me going in circles until I found your post. Life saver!@
ReplyDeleteHappy to help, as always!
ReplyDeleteGreat Job
ReplyDeleteAmazing - thank you sir - worked for me :)
ReplyDeleteTNX!
ReplyDeleteI have the exact same issue but this fix didn't solve it. I suspect a security update or something needs to be applied and the problem will go away. When I did the fix you suggested it stuck, but the problem didn't go away. Which is odd.
ReplyDeleteI just worked for me.
ReplyDeleteThank you.
just wanted to say thanks, after tearing my hair out while setting up outlook anywhere, i must have changed this setting without realising
ReplyDeleteGlad it helped! This is actually caused by running the outlook anywhere wizard... not sure if this was ever fixed or not... but by the continued flood of comments here I guess not!
DeleteHey this is awesome, thank you so much.
ReplyDeleteHonestly I think this happens if people (myself included) deviate from the SBS wizards. You are a lifesaver?
Glad to hear it!
DeleteThanks a lot, still helping people to this day!
ReplyDeleteLegend Andrew! Thanks for the help.
ReplyDeleteLegend! thanks
ReplyDeleteThanks for this topic, shame i also wasted several hours before finding this solution!
ReplyDeleteThanks for the fix!
ReplyDeleteHi Andrew. Just and FYI, this issue is documented for SBS 2008 on the SBS Blog site, http://blogs.technet.com/b/sbs/archive/2009/06/19/common-remote-web-workplace-rww-connect-to-a-computer-issues-in-sbs-2008.aspx
ReplyDeleteI like your blog, lots of great stuff on here. Keep up the good work. If you wish to view mine (mostly SBS/Exchange deep technical issues) it is at http://blog.korteksolutions.com
Lyle Epstein
worked for me. Thanks!!
ReplyDeleteThx man, solved my problem. Indeed I enabled Outlook Anywhere a few days ago and users ran in to this problem.
ReplyDeleteWorked for me too - thanks!
ReplyDeleteworked for me. did the non-commandline version.
ReplyDeleteThank you so much!!! Worked!
ReplyDeleteP.S. how do we do non-command line version? I couldn't find it so I just did it on command line. Thanks again!!!
Delete