Outlook 2016 with new Exchange account has autodiscover configured as IMAP rather than MAPI, ,
Hey all, I'm wondering whether somebody ultimately goofed. We've got a new Exchange server up ... running 2016 with Outlook 2016. On premise, and with autodiscover configured. When I opt to use my credentials, it behaves and everything like an Exchange server normally does ... but when I look in my accounts it shows as IMAP rather than Exchange ... I have all of my inbox and what not folders under an Outlook folder with the name of my email address like normal, but then there is this other set of folders under that with an empty inbox and outbox, but a full contacts,, calendars, and notes folder, under the name "My Outlook Datafile (1)". I can send,, receive, add events to the calendar, add contacts to the server, and everything, but it's bothering me that I've got a split configuration. Thought Exchange used MAPI by default? I'm definitely suspecting somebody goofed since my off premise other email account using Office 365 (this one) doesn't do this. Thoughts would be great. We do have full AD implemented as well, though my workstation doesn't have a current connection to it since we're still messing with domain structures if that matters. Needless to say, this is driving me five kinds of bonkers.
Hi, Yep it is wrong. You have an IMAP account and a second data file for calendars and the other stuff Outlook doesn't support on IMAP. I have seen this before when an external URL wasn't configured for the Outlook Anywhere. There is an autodiscover configuration test tool in Outlook actually, you can use it to verify settings. Andrew. ________________________________________ From: Blind-sysadmins [blind-sysadmins-bounces@lists.hodgsonfamily.org] on behalf of Katherine Moss [Katherine.Moss@gordon.edu] Sent: 08 February 2017 04:28 To: 'blind-sysadmins@lists.hodgsonfamily.org' Subject: [Blind-sysadmins] Outlook 2016 with new Exchange account has autodiscover configured as IMAP rather than MAPI, , Hey all, I'm wondering whether somebody ultimately goofed. We've got a new Exchange server up ... running 2016 with Outlook 2016. On premise, and with autodiscover configured. When I opt to use my credentials, it behaves and everything like an Exchange server normally does ... but when I look in my accounts it shows as IMAP rather than Exchange ... I have all of my inbox and what not folders under an Outlook folder with the name of my email address like normal, but then there is this other set of folders under that with an empty inbox and outbox, but a full contacts,, calendars, and notes folder, under the name "My Outlook Datafile (1)". I can send,, receive, add events to the calendar, add contacts to the server, and everything, but it's bothering me that I've got a split configuration. Thought Exchange used MAPI by default? I'm definitely suspecting somebody goofed since my off premise other email account using Office 365 (this one) doesn't do this. Thoughts would be great. We do have full AD implemented as well, though my workstation doesn't have a current connection to it since we're still messing with domain structures if that matters. Needless to say, this is driving me five kinds of bonkers. _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
As I thought ... I'll need to talk to my friend, then, for he's the one with full admin access to the server at the moment. Now ... when I tap into the autodiscover URL directly via firefox, I can login, and I get the 600 error code, and from what I can gather based on research and what not, that's actually a good thing, signaling that autodiscover is indeed working properly. We do have a self-signed cert (for now, until we get a certification authority up) If I run the autodiscover test tool, what am I looking for in order to get the root of the issue? I've never done Exchange testing before ... so this is going to be fun. Labs are awesome things. LOL, except when an issue eludes you.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson
Sent: Wednesday, February 08, 2017 4:51 AM
To: Blind sysadmins list
As I thought ... I'll need to talk to my friend, then, for he's the one with full admin access to the server at the moment. Now ... when I tap into the autodiscover URL directly via firefox, I can login, and I get the 600 error code, and from what I can gather based on research and what not, that's actually a good thing, signaling that autodiscover is indeed working properly. We do have a self-signed cert (for now, until we get a certification authority up) If I run the autodiscover test tool, what am I looking for in order to get the root of the issue? I've never done Exchange testing before ... so this is going to be fun. Labs are awesome things. LOL, except when an issue eludes you.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson
Sent: Wednesday, February 08, 2017 4:51 AM
To: Blind sysadmins list
Hi,
Right click the Outlook icon in the systray with left control key held down and choose Test Autoconfiguration settings. Follow the prompts in the Window provided (i.e, enter your email and password).
It comes back with the details obtained from the autodiscover server.
Andrew.
________________________________________
From: Blind-sysadmins [blind-sysadmins-bounces@lists.hodgsonfamily.org] on behalf of Katherine Moss [Katherine.Moss@gordon.edu]
Sent: 08 February 2017 13:18
To: Blind sysadmins list
Subject: Re: [Blind-sysadmins] Outlook 2016 with new Exchange account has autodiscover configured as IMAP rather than MAPI, ,
As I thought ... I'll need to talk to my friend, then, for he's the one with full admin access to the server at the moment. Now ... when I tap into the autodiscover URL directly via firefox, I can login, and I get the 600 error code, and from what I can gather based on research and what not, that's actually a good thing, signaling that autodiscover is indeed working properly. We do have a self-signed cert (for now, until we get a certification authority up) If I run the autodiscover test tool, what am I looking for in order to get the root of the issue? I've never done Exchange testing before ... so this is going to be fun. Labs are awesome things. LOL, except when an issue eludes you.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson
Sent: Wednesday, February 08, 2017 4:51 AM
To: Blind sysadmins list
Thanks. Hopefully I can find something. I'll have to do it though when I get home since for whatever reason, my company blocks our server. LOL I love adventures like this when the environment isn't time sensitive.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson
Sent: Wednesday, February 08, 2017 8:56 AM
To: Blind sysadmins list
Well? I was indeed correct ... I definitely think there is something wrong with our autodiscover implementation; when I access the url manually,, though, I get the right message; 600 http request code. So ... not sure why the test email auto configuration tool throws a http 401 unauthorized during the request. Though just before that throws a http 400. Looks like I'm going to need to get ahold of people, as I don't have access to the EAC at this point ... otherwise fixing this would have been done yesterday. Any more information I can possibly glean on my side to hand over? Thanks.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss
Sent: Wednesday, February 8, 2017 10:15
To: Blind sysadmins list
Well? I was indeed correct ... I definitely think there is something wrong with our autodiscover implementation; when I access the url manually,, though, I get the right message; 600 http request code. So ... not sure why the test email auto configuration tool throws a http 401 unauthorized during the request. Though just before that throws a http 400. Looks like I'm going to need to get ahold of people, as I don't have access to the EAC at this point ... otherwise fixing this would have been done yesterday. Any more information I can possibly glean on my side to hand over? Thanks.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss
Sent: Wednesday, February 8, 2017 10:15
To: Blind sysadmins list
Hi,
There are more comprehensive autodiscover test tools out there but don't use them on your live account, create another account on the server and use that.
Each time I used to configure autodiscover with Exchange 2010 and 2013, I had to change lots of the settings from Powershell.
Andrew.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss
Sent: 09 February 2017 21:34
To: Blind sysadmins list
I'll definitely let my friend know. Thanks.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson
Sent: Thursday, February 9, 2017 16:58
To: Blind sysadmins list
I'll definitely let my friend know. Thanks.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson
Sent: Thursday, February 9, 2017 16:58
To: Blind sysadmins list
Hi,
There are more comprehensive autodiscover test tools out there but don't use them on your live account, create another account on the server and use that.
Each time I used to configure autodiscover with Exchange 2010 and 2013, I had to change lots of the settings from Powershell.
Andrew.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss
Sent: 09 February 2017 21:34
To: Blind sysadmins list
Thanks. Hopefully I can find something. I'll have to do it though when I get home since for whatever reason, my company blocks our server. LOL I love adventures like this when the environment isn't time sensitive.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson
Sent: Wednesday, February 08, 2017 8:56 AM
To: Blind sysadmins list
Hi,
Right click the Outlook icon in the systray with left control key held down and choose Test Autoconfiguration settings. Follow the prompts in the Window provided (i.e, enter your email and password).
It comes back with the details obtained from the autodiscover server.
Andrew.
________________________________________
From: Blind-sysadmins [blind-sysadmins-bounces@lists.hodgsonfamily.org] on behalf of Katherine Moss [Katherine.Moss@gordon.edu]
Sent: 08 February 2017 13:18
To: Blind sysadmins list
Subject: Re: [Blind-sysadmins] Outlook 2016 with new Exchange account has autodiscover configured as IMAP rather than MAPI, ,
As I thought ... I'll need to talk to my friend, then, for he's the one with full admin access to the server at the moment. Now ... when I tap into the autodiscover URL directly via firefox, I can login, and I get the 600 error code, and from what I can gather based on research and what not, that's actually a good thing, signaling that autodiscover is indeed working properly. We do have a self-signed cert (for now, until we get a certification authority up) If I run the autodiscover test tool, what am I looking for in order to get the root of the issue? I've never done Exchange testing before ... so this is going to be fun. Labs are awesome things. LOL, except when an issue eludes you.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson
Sent: Wednesday, February 08, 2017 4:51 AM
To: Blind sysadmins list
Hi, Yep it is wrong. You have an IMAP account and a second data file for calendars and the other stuff Outlook doesn't support on IMAP. I have seen this before when an external URL wasn't configured for the Outlook Anywhere. There is an autodiscover configuration test tool in Outlook actually, you can use it to verify settings. Andrew. ________________________________________ From: Blind-sysadmins [blind-sysadmins-bounces@lists.hodgsonfamily.org] on behalf of Katherine Moss [Katherine.Moss@gordon.edu] Sent: 08 February 2017 04:28 To: 'blind-sysadmins@lists.hodgsonfamily.org' Subject: [Blind-sysadmins] Outlook 2016 with new Exchange account has autodiscover configured as IMAP rather than MAPI, , Hey all, I'm wondering whether somebody ultimately goofed. We've got a new Exchange server up ... running 2016 with Outlook 2016. On premise, and with autodiscover configured. When I opt to use my credentials, it behaves and everything like an Exchange server normally does ... but when I look in my accounts it shows as IMAP rather than Exchange ... I have all of my inbox and what not folders under an Outlook folder with the name of my email address like normal, but then there is this other set of folders under that with an empty inbox and outbox, but a full contacts,, calendars, and notes folder, under the name "My Outlook Datafile (1)". I can send,, receive, add events to the calendar, add contacts to the server, and everything, but it's bothering me that I've got a split configuration. Thought Exchange used MAPI by default? I'm definitely suspecting somebody goofed since my off premise other email account using Office 365 (this one) doesn't do this. Thoughts would be great. We do have full AD implemented as well, though my workstation doesn't have a current connection to it since we're still messing with domain structures if that matters. Needless to say, this is driving me five kinds of bonkers. _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
participants (2)
-
Andrew Hodgson -
Katherine Moss