BPOS SSO Client Changing Autodiscover
I’ve finally taken some time today during lunch to fix an issue I created for myself. I installed the SSO client and had it install everything, including creating an Outlook profile for Online Exchange. When I realized I clicked ‘next’ too quickly, I uninstalled everything, but then it was too late. I was simply going to use the SSO features for SharePoint, but was in too much of a hurry to get it installed… which created a learning experience!
My Exchange Web Services (EWS) weren’t working. I couldn’t get OOF to work for calendar sync on OCS.
There are a few directories and registry changes that were made that I had to remove:
HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover
- I deleted the dyntek.com entry that points Autodiscover to a local XML file.
- I changed the above REG_DWORD entries from 1 to 0
- Deleted this key: HKEY_CURRENT_USER\Software\Microsoft\MOCHA
- Deleted the above referenced ‘Sign In’ directory under my profile
- And, of course, deleted the Online Profile it created
Outlook and OCS are now happy!
Tags: autodiscover, bpos, ews, exchange web services, online, Outlook, sso
You can comment below, or link to this permanent URL from your own site.
December 10, 2010 at 10:13 am
Thanks for the info Jim! But can you please post the full path to the registry entries in your screenshot? I think This is exactly what I need to do to fix my issue after doing a BPOS trial.
December 10, 2010 at 10:19 am
Done, thanks!
December 10, 2010 at 10:30 am
Wow! instantaneous very impressive! Well…not expecting such a fast response I did some more googling after my post and found this technet article that may also help any other lost souls out there: http://technet.microsoft.com/en-us/library/dd940116.aspx
Anyway, my Outlook/Exchange & Autodiscover settings are all friends again! Thanks again Jim.