(Exchange 2010 SP1) Autodiscover Configures for IMAP
After upgrading to Exchange 2010, our Outlook clients grab autodiscover settings perfectly. However, it is configuring our clients for IMAP instead of Exchange w/ RPC-HTTPs as we are accustomed to. How can I modify the autodiscover settings
to only configure to Exchange w/ RPC-HTTPS?Taylor
September 27th, 2010 3:46pm
Whether you set up mail profile inside the domain, or outside?
Can you provide the actual steps that set up the mail profile?
Could you provide the build number of the outlook client?
Please run “Test E-mail AutoConfiguration” on the outlook client, and then post the XML response
James Luo
TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
If you have any feedback on our support, please contact tngfb@microsoft.com
Free Windows Admin Tool Kit Click here and download it now
September 27th, 2010 11:13pm
Whether you set up mail profile inside the domain, or outside?
Only internally - we have IMAP & POP enabled for internal uses, but do not publish to the Internet.
Can you provide the actual steps that set up the mail profile?
Open Outlook -> Prompted with Setup Wizard -> Enter Name & Email and follow wizard.
Could you provide the build number of the outlook client?
14.0.476.1000
Please run “Test E-mail AutoConfiguration” on the outlook client, and then post the XML response
<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>Taylor Higley</DisplayName>
<LegacyDN>/o=AFGE/ou=First Administrative Group/cn=Recipients/cn=thigley</LegacyDN>
<AutoDiscoverSMTPAddress>Taylor.Higley@afge.org</AutoDiscoverSMTPAddress>
<DeploymentId>16da584b-481f-4ce3-9055-dd369fccb18f</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>EXCH</Type>
<Server>AFGE-MAIL03.afge.org</Server>
<ServerDN>/o=AFGE/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=AFGE-MAIL03</ServerDN>
<ServerVersion>738180DA</ServerVersion>
<MdbDN>/o=AFGE/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=AFGE-MAIL03/cn=Microsoft Private MDB</MdbDN>
<PublicFolderServer>AFGE-MAIL03.afge.org</PublicFolderServer>
<AD>AFGE-DC05.afge.org</AD>
<ASUrl>https://afge-mail03.afge.org/EWS/Exchange.asmx</ASUrl>
<EwsUrl>https://afge-mail03.afge.org/EWS/Exchange.asmx</EwsUrl>
<EcpUrl>https://afge-mail03.afge.org/ecp/</EcpUrl>
<EcpUrl-um>?p=customize/voicemail.aspx&exsvurl=1</EcpUrl-um>
<EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&exsvurl=1</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx></EcpUrl-mt>
<EcpUrl-ret>?p=organize/retentionpolicytags.slab&exsvurl=1</EcpUrl-ret>
<EcpUrl-sms>?p=sms/textmessaging.slab&exsvurl=1</EcpUrl-sms>
<OOFUrl>https://afge-mail03.afge.org/EWS/Exchange.asmx</OOFUrl>
<UMUrl>https://afge-mail03.afge.org/EWS/UM2007Legacy.asmx</UMUrl>
<OABUrl>https://afge-mail03.afge.org/OAB/8b3d512b-c6ec-4184-8b19-78970e8d4d6f/</OABUrl>
</Protocol>
<Protocol>
<Type>EXPR</Type>
<Server>mail.afge.org</Server>
<SSL>On</SSL>
<AuthPackage>Ntlm</AuthPackage>
<ASUrl>https://mail.afge.org/ews/exchange.asmx</ASUrl>
<EwsUrl>https://mail.afge.org/ews/exchange.asmx</EwsUrl>
<EcpUrl>https://mail.afge.org/ecp/</EcpUrl>
<EcpUrl-um>?p=customize/voicemail.aspx&exsvurl=1</EcpUrl-um>
<EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&exsvurl=1</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx></EcpUrl-mt>
<EcpUrl-ret>?p=organize/retentionpolicytags.slab&exsvurl=1</EcpUrl-ret>
<EcpUrl-sms>?p=sms/textmessaging.slab&exsvurl=1</EcpUrl-sms>
<OOFUrl>https://mail.afge.org/ews/exchange.asmx</OOFUrl>
<UMUrl>https://mail.afge.org/ews/UM2007Legacy.asmx</UMUrl>
<OABUrl>https://mail.afge.org/OAB/8b3d512b-c6ec-4184-8b19-78970e8d4d6f/</OABUrl>
<CertPrincipalName>msstd:mail.afge.org</CertPrincipalName>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Internal>
<OWAUrl AuthenticationMethod="Basic, Fba">https://afge-mail03.afge.org/owa/</OWAUrl>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://afge-mail03.afge.org/EWS/Exchange.asmx</ASUrl>
</Protocol>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba">https://mail.afge.org/owa/</OWAUrl>
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://mail.afge.org/ews/exchange.asmx</ASUrl>
</Protocol>
</External>
</Protocol>
<AlternativeMailbox>
<Type>Archive</Type>
<DisplayName>Online Archive - Taylor Higley</DisplayName>
<LegacyDN>/o=AFGE/ou=First Administrative Group/cn=Recipients/cn=thigley/guid=a3cd67b8-5d0d-45bb-9d69-9e075644f39d</LegacyDN>
<Server>AFGE-MAIL03.afge.org</Server>
</AlternativeMailbox>
<AlternativeMailbox>
<Type>Delegate</Type>
<DisplayName>Marona Griffin</DisplayName>
<LegacyDN>/o=AFGE/ou=First Administrative Group/cn=Recipients/cn=griffm</LegacyDN>
<Server>AFGE-MAIL03.afge.org</Server>
</AlternativeMailbox>
<AlternativeMailbox>
<Type>Delegate</Type>
<DisplayName>Online Archive - Marona Griffin</DisplayName>
<LegacyDN>/o=AFGE/ou=First Administrative Group/cn=Recipients/cn=griffm/guid=bbf93db4-c399-4ffa-bc62-705ab9ffe3c8</LegacyDN>
<Server>AFGE-MAIL03.afge.org</Server>
</AlternativeMailbox>
</Account>
</Response>
</Autodiscover>
Taylor
October 4th, 2010 2:11pm
I also not found any unusual traces in the output, only this user are migrated from exchange 2003. Does the issue also happen to the mailbox that
has created directly on the exchange 2010 server?James Luo
TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
If you have any feedback on our support, please contact tngfb@microsoft.com
Free Windows Admin Tool Kit Click here and download it now
October 4th, 2010 10:00pm
I will have one of our engineers test this scenario and post back to you today.Taylor
October 6th, 2010 7:40am
New users setup using Exchange RCP/HTTPs [as we desire]. Existing users setup using IMAP4. Any ideas?Taylor
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2010 9:44am
So, there’s something incorrect on the migrated users’ user object or their mailboxes. Please do a cross-check on the output of the
following cmdlets between the problematic user and working user:
Get-User | Fl
Get-Mailbox | Fl
Get-CasMailbox | Fl
Please also compare the attributes of the user objects via ADSI EditorJames Luo
TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
If you have any feedback on our support, please contact tngfb@microsoft.com
October 6th, 2010 9:32pm
How's the issue now?James Luo
TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
If you have any feedback on our support, please contact tngfb@microsoft.com
Free Windows Admin Tool Kit Click here and download it now
October 7th, 2010 10:05pm