Autodiscover issue
in [Microsoft Exchange]
|
From: Aurelius on 3 Mar 2008 14:29 Rollup1 for Exchange 2007 SP1 corrects this issue. "Andy David {MVP}" wrote: > On Tue, 29 Jan 2008 08:17:05 -0800, Maverick > <maverick(a)falsedomain.donotspam.com> wrote: > > >We finally found what broke it. I have tested this and know with 100 percent > >certainty that setting the msexchangequerybaseDN on a user breaks > >autodiscover. If I remove the attribute, autodiscover works fine. This is > >really bad as it completely breaks our Exchange infrastructure. We have use > >this attribute to set and restrict address lists in OWA. Big bug IMO. Have > >you heard of this? > > I woold open a case with PSS. Sounds like they need to get involved! > > > > >"Andy David {MVP}" wrote: > > > >> On Fri, 25 Jan 2008 14:31:01 -0800, Maverick > >> <maverick(a)falsedomain.donotspam.com> wrote: > >> > >> >Hi Andy, > >> > > >> >The uri points to https://mail.domain.com/autodiscover/autodiscover.xml > >> >where mail.domain.com is the name of my NLB. > >> > >> hmmm, well assuming DNS is correct, you may want to run Exbpa against > >> the org doing the permission check. Havent seen your error before. > >> > >> > > >> >Thanks for the reply. > >> > > >> >Maverick > >> > > >> >"Andy David {MVP}" wrote: > >> > > >> >> On Fri, 25 Jan 2008 14:06:01 -0800, Maverick > >> >> <maverick(a)falsedomain.donotspam.com> wrote: > >> >> > >> >> >I have an NLB CAS setup and have recently run into OOF and AS not working > >> >> >anymore via Outlook 2007. When I do a test-outlookwebservices -id user | fl, > >> >> >all tests come back fine on the CAS servers. However, when I run the > >> >> >autoconfiguration test via Outlook 2007, I fail to connect to the SCP. If > >> >> >find the SCP find but fails with an error of (0x800c8203). > >> >> > > >> >> >The funny thing is, I have temporarily mailbox-enabled a domain admin acct > >> >> >and the Outlook autoconfiguration test comes back fine and displays all the > >> >> >proper URLs (oab, UM, AS). Based on this, I figure it's got to be a > >> >> >permission issue but can't seem to find out where the permissions changed. I > >> >> >recently upgraded all of the mail servers to SP1 and this seems to be the > >> >> >time that AutoDiscover broke. This may just be a coincidence. Any thoughts > >> >> >would be great! Thanks. > >> >> > >> >> > >> >> If you do a Get-ClientAccessServer , what does the > >> >> AutoDiscoverServiceInternalUri point to? > >> >> > >> >> > >> >
From: Andy David {MVP} on 3 Mar 2008 17:31 On Mon, 3 Mar 2008 11:29:01 -0800, Aurelius <aureluis(a)falsedomain.donotspam.com> wrote: >Rollup1 for Exchange 2007 SP1 corrects this issue. Good to know! > >"Andy David {MVP}" wrote: > >> On Tue, 29 Jan 2008 08:17:05 -0800, Maverick >> <maverick(a)falsedomain.donotspam.com> wrote: >> >> >We finally found what broke it. I have tested this and know with 100 percent >> >certainty that setting the msexchangequerybaseDN on a user breaks >> >autodiscover. If I remove the attribute, autodiscover works fine. This is >> >really bad as it completely breaks our Exchange infrastructure. We have use >> >this attribute to set and restrict address lists in OWA. Big bug IMO. Have >> >you heard of this? >> >> I woold open a case with PSS. Sounds like they need to get involved! >> >> > >> >"Andy David {MVP}" wrote: >> > >> >> On Fri, 25 Jan 2008 14:31:01 -0800, Maverick >> >> <maverick(a)falsedomain.donotspam.com> wrote: >> >> >> >> >Hi Andy, >> >> > >> >> >The uri points to https://mail.domain.com/autodiscover/autodiscover.xml >> >> >where mail.domain.com is the name of my NLB. >> >> >> >> hmmm, well assuming DNS is correct, you may want to run Exbpa against >> >> the org doing the permission check. Havent seen your error before. >> >> >> >> > >> >> >Thanks for the reply. >> >> > >> >> >Maverick >> >> > >> >> >"Andy David {MVP}" wrote: >> >> > >> >> >> On Fri, 25 Jan 2008 14:06:01 -0800, Maverick >> >> >> <maverick(a)falsedomain.donotspam.com> wrote: >> >> >> >> >> >> >I have an NLB CAS setup and have recently run into OOF and AS not working >> >> >> >anymore via Outlook 2007. When I do a test-outlookwebservices -id user | fl, >> >> >> >all tests come back fine on the CAS servers. However, when I run the >> >> >> >autoconfiguration test via Outlook 2007, I fail to connect to the SCP. If >> >> >> >find the SCP find but fails with an error of (0x800c8203). >> >> >> > >> >> >> >The funny thing is, I have temporarily mailbox-enabled a domain admin acct >> >> >> >and the Outlook autoconfiguration test comes back fine and displays all the >> >> >> >proper URLs (oab, UM, AS). Based on this, I figure it's got to be a >> >> >> >permission issue but can't seem to find out where the permissions changed. I >> >> >> >recently upgraded all of the mail servers to SP1 and this seems to be the >> >> >> >time that AutoDiscover broke. This may just be a coincidence. Any thoughts >> >> >> >would be great! Thanks. >> >> >> >> >> >> >> >> >> If you do a Get-ClientAccessServer , what does the >> >> >> AutoDiscoverServiceInternalUri point to? >> >> >> >> >> >> >> >> >>
|
Pages: 1 Prev: Autodiscover issue Next: Error uninstalling exchange server 2003 |