Chris Spera Contact Information - Per Gabe Aul Tweet

Unfortunately I can't find the prior post despite a thorough search - it may have been in one of the beta forums that have been cleared...or I assume it's been cleared as it just doesn't seem to be visible.  No matter, this link should basically explain it:

http://blogs.technet.com/b/kristinw/archive/2013/04/19/controlling-outlook-autodiscover-behavior.aspx

In short you need to go into the registry to tell outlook to use a local .xml as a base for when it searches for the exchange servers settings with autodiscover.  Then you need to create the .XML

In my simple terms, my one host is 1.exchange.1and1.eu where I have a custom domain of let's say ******@CustomDomain.Com.  When you try and set up a new exchange account with outlook it will use the CustomDomain.Com to try and find the Autodiscover settings.  If your DNS settings aren't done correctly for this, it gets into a flap and doesn't work.  In my instance, the correct DNS settings would have been to push the AutoDiscover instead pick up its settings from 1.exchange.1and1.eu....but I couldn't do this as I didn't have access. 

With the Registry Edit (make sure it's under the correct office version) and the XML, this short cuts the DNS settings and goes direct.  And it all worked.  I understand your frustration, there was much wailing and gnashing of teeth when I first tried to figure this out - I'm not a trained tecchie...I blunder along.  Anyway, the above got it sorted for me.

Let me know how you get along or if you need any more help...if I'm not already well beyond my skill-set, hey ho.

Digittt

thank you, Mavis. I appreciate the help.

Just so you know, this was done on an existing Build of 10074 with Office 365 2013 installed, and then on a clean install of Build 10074  with a clean install of Office 2016 Preview.  The wording for the error messages were different in both settings but pointed to the same problem - The credentials used were invalid, so the account could not be created.

The Exchange account in question, is a hosted Exchange account on Exchange Server 2010.

Chris - I'm dangerous with the little amount I know, but I have managed to set up 2 exchange accounts in all releases including the latest of 2016.  I think you're being a bit heavy handed in your response.

The key was figuring out how AutoDiscover works...or in my case didn't work with me having little access to the DNS side of things.  But, there is a solution - you can use an override to force it to use a local XML to follow the path to your correct AutoDiscover server.  There is a thread in the forums here somewhere that I wrote a very waffly reply outlining it....find that and hopefully it helps.

Sorry if I am telling you stuff you already know, but I didn't, and I fretted, and then I figured it out and haven't looked back since. 

I'm even loving the feature I've just discovered with Outlook when you insert an attachment - your most recently accessed / created files are automatically shown.  This may have been a feature in earlier versions  but I've just discovered it and hot dawggg it's awesome!

Digittt

Digitt,

You may be right. Perhaps I did vent a bit here. I apologize to all for that. I'd appreciate you pointing out the specific post you're referencing. I spent about 2 hours on the phone with my hosted Exchange provider last night trying to figure this out, and neither of us were able to get anything synchronizing.  Currently Outlook 2016 Preview only offers options for POP/iMAP or Outlook.com/EAS (which isn't Exchange, BTW, its Exchange Active Sync, which isn't quite the same in my experience, though you'd think it would be...)

Anyway, neither of us could find the magic words to get the account to register or sync, AND when I tried to upgrade from Office 2013 to Office 2016, with Outlook already configured and working prior to the upgrade attempt, Outlook would not open afterwards.  There's still something not implemented here, and it just seems silly not to have that baked in and working prior to a public beta release.

But again, if you can send me a link to the specific post you're referencing, I'd appreciate it.

I've been using Exchange with Outlook 2016 for a while now, and haven't had this problem. I'm forwarding your post to the Outlook team, so that they are aware of the difficulty.

Chris - I'm dangerous with the little amount I know, but I have managed to set up 2 exchange accounts in all releases including the latest of 2016.  I think you're being a bit heavy handed in your response.

The key was figuring out how AutoDiscover works...or in my case didn't work with me having little access to the DNS side of things.  But, there is a solution - you can use an override to force it to use a local XML to follow the path to your correct AutoDiscover server.  There is a thread in the forums here somewhere that I wrote a very waffly reply outlining it....find that and hopefully it helps.

Sorry if I am telling you stuff you already know, but I didn't, and I fretted, and then I figured it out and haven't looked back since. 

I'm even loving the feature I've just discovered with Outlook when you insert an attachment - your most recently accessed / created files are automatically shown.  This may have been a feature in earlier versions  but I've just discovered it and hot dawggg it's awesome!

Digittt

Digitt,

You may be right. Perhaps I did vent a bit here. I apologize to all for that. I'd appreciate you pointing out the specific post you're referencing. I spent about 2 hours on the phone with my hosted Exchange provider last night trying to figure this out, and neither of us were able to get anything synchronizing.  Currently Outlook 2016 Preview only offers options for POP/iMAP or Outlook.com/EAS (which isn't Exchange, BTW, its Exchange Active Sync, which isn't quite the same in my experience, though you'd think it would be...)

Anyway, neither of us could find the magic words to get the account to register or sync, AND when I tried to upgrade from Office 2013 to Office 2016, with Outlook already configured and working prior to the upgrade attempt, Outlook would not open afterwards.  There's still something not implemented here, and it just seems silly not to have that baked in and working prior to a public beta release.

But again, if you can send me a link to the specific post you're referencing, I'd appreciate it.

Chris - I'm dangerous with the little amount I know, but I have managed to set up 2 exchange accounts in all releases including the latest of 2016.  I think you're being a bit heavy handed in your response.

The key was figuring out how AutoDiscover works...or in my case didn't work with me having little access to the DNS side of things.  But, there is a solution - you can use an override to force it to use a local XML to follow the path to your correct AutoDiscover server.  There is a thread in the forums here somewhere that I wrote a very waffly reply outlining it....find that and hopefully it helps.

Sorry if I am telling you stuff you already know, but I didn't, and I fretted, and then I figured it out and haven't looked back since. 

I'm even loving the feature I've just discovered with Outlook when you insert an attachment - your most recently accessed / created files are automatically shown.  This may have been a feature in earlier versions  but I've just discovered it and hot dawggg it's awesome!

Digittt