This list server has an Exchange list as well.
> On Mar 7, 2015, at 16:15, "Kennedy, Jim" <[email protected]> wrote: > > Thanks bunch's sir. At least we know autodiscover and everything is ok > now..no lingering doubts. We will be fine with the script I made from > Aakash's post. We had an open house kind of thing today..so there were a lot > of people I could get to test it for me. > > JK > > > From: [email protected] [[email protected]] on > behalf of Michael B. Smith [[email protected]] > Sent: Saturday, March 07, 2015 1:52 PM > To: [email protected] > Subject: [NTSysADM] RE: OT Exchange issues. > > Turn off the old server or rename it, I don’t care. Get that old name off the > network. > > Delete the old name from DNS and flush all your DNS caches. Delete the old > name from WINS (if you have WINS) and get it tombstoned. > > Ensure that a lookup for that name on a client workstation FAILS. > > Then try Outlook again. The lack of the old name should force a full > autodiscover. > > This is my last suggestion. If it doesn’t work, you need to go Aakash’s > approach. > > From: [email protected] [mailto:[email protected]] > On Behalf Of Kennedy, Jim > Sent: Saturday, March 7, 2015 12:09 PM > To: [email protected] > Subject: [NTSysADM] RE: OT Exchange issues. > > The legacy part is from the 2003 to 2010 upgrade when you had to have dual > OWA url’s to support co-existence of both types of mailbox servers as you > migrated. Not sure how it got there, certainly don’t need that anymore. It > does resolve to the regular owa.elyriaschools.org IP. I will fix that…is it > right other than the ‘legacy’ part? That url triggers a bad response. I have > no idea what that one is for. > > In the mean time I have a script ready and tested using Aakash’s approach. > That is plan B if I don’t nail this, and I agree with you, auto discover > seems to be working. New images find it fine…delete the profile Aakash’s way > and it finds it fine. I blew out the old CAS too soon and Outlook isn’t going > to recover on it’s own, I know better. > > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Michael B. Smith > Sent: Saturday, March 7, 2015 11:56 AM > To: [email protected] > Subject: [NTSysADM] RE: OT Exchange issues. > > Then change autodiscoverinternaluri back. You have designed support for it. J > > Tell me about this: > > <Protocol> > <Type>WEB</Type> > <Internal> > <OWAUrl > AuthenticationMethod="Basic">https://legacy.elyriaschools.org/owa/</OWAUrl> > <Protocol> > <Type>EXCH</Type> > <ASUrl>https://owa.elyriaschools.org/ews/exchange.asmx</ASUrl> > </Protocol> > </Internal> > > Other than that, your AutoD response is picture-perfect. > > From: [email protected] [mailto:[email protected]] > On Behalf Of Kennedy, Jim > Sent: Saturday, March 7, 2015 11:02 AM > To: [email protected] > Subject: [NTSysADM] RE: OT Exchange issues. > > Internal autodiscover was always the way it is now > owa.elyriaschools.org……. and I used our elyriaschools.org wildcard cert > for it Perhaps I got away because the host was also owa, but it was the > .local domain. > > owa.elyriaschools.org does resolve in dns to owa001.edunet.local’s ip addy. > > Switching to https://OWA001.EDUNET.LOCAL/autodiscover/autodiscover.xml and > starting a working client I get the certificate mismatch error from Outlook > and it does not fix the broken profiles/clients. > > Below is all the Outlook xml for connectivity checks from a working client > and the internal changed to > https://OWA001.EDUNET.LOCAL/autodiscover/autodiscover.xml Can’t test from > a nonworking one of course. I will get to work on those two scripts. > > <?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>Kennedy, Jim</DisplayName> > <LegacyDN>/O=ECSD/OU=ECSDNET/CN=RECIPIENTS/CN=KENNEDYJIM</LegacyDN> > > <AutoDiscoverSMTPAddress>[email protected]</AutoDiscoverSMTPAddress> > <DeploymentId>8453f987-0a83-4a75-8374-e0a20fa2d410</DeploymentId> > </User> > <Account> > <AccountType>email</AccountType> > <Action>settings</Action> > <Protocol> > <Type>EXCH</Type> > <Server>OWA001.EDUNET.LOCAL</Server> > <ServerDN>/o=ECSD/ou=Exchange Administrative Group > (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=OWA001</ServerDN> > <ServerVersion>7383807B</ServerVersion> > <MdbDN>/o=ECSD/ou=Exchange Administrative Group > (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=OWA001/cn=Microsoft Private > MDB</MdbDN> > <PublicFolderServer>MBX002.EDUNET.LOCAL</PublicFolderServer> > <AD>NORTHWOOD.EDUNET.LOCAL</AD> > <ASUrl>https://owa.elyriaschools.org/ews/exchange.asmx</ASUrl> > <EwsUrl>https://owa.elyriaschools.org/ews/exchange.asmx</EwsUrl> > <EcpUrl>https://owa.edunet.local/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://owa.elyriaschools.org/ews/exchange.asmx</OOFUrl> > <UMUrl>https://owa.elyriaschools.org/ews/UM2007Legacy.asmx</UMUrl> > > <OABUrl>https://owa.elyriaschools.org/oab/573fb45a-5b62-4b5a-b27f-f7eef3aa5303/</OABUrl> > </Protocol> > <Protocol> > <Type>EXPR</Type> > <Server>owa.elyriaschools.org</Server> > <SSL>On</SSL> > <AuthPackage>Basic</AuthPackage> > <ASUrl>https://owa.elyriaschools.org/ews/exchange.asmx</ASUrl> > <EwsUrl>https://owa.elyriaschools.org/ews/exchange.asmx</EwsUrl> > <EcpUrl>https://owa.elyriaschools.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://owa.elyriaschools.org/ews/exchange.asmx</OOFUrl> > <UMUrl>https://owa.elyriaschools.org/ews/UM2007Legacy.asmx</UMUrl> > > <OABUrl>https://owa.elyriaschools.org/OAB/573fb45a-5b62-4b5a-b27f-f7eef3aa5303/</OABUrl> > </Protocol> > <Protocol> > <Type>WEB</Type> > <Internal> > <OWAUrl > AuthenticationMethod="Basic">https://legacy.elyriaschools.org/owa/</OWAUrl> > <Protocol> > <Type>EXCH</Type> > <ASUrl>https://owa.elyriaschools.org/ews/exchange.asmx</ASUrl> > </Protocol> > </Internal> > <External> > <OWAUrl > AuthenticationMethod="Fba">https://owa.elyriaschools.org/owa/</OWAUrl> > <Protocol> > <Type>EXPR</Type> > <ASUrl>https://owa.elyriaschools.org/ews/exchange.asmx</ASUrl> > </Protocol> > </External> > </Protocol> > </Account> > </Response> > </Autodiscover> > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Michael B. Smith > Sent: Saturday, March 07, 2015 10:36 AM > To: [email protected] > Subject: [NTSysADM] RE: OT Exchange issues. > > Given your message headers, I will guarantee you that that > AutoDiscoverServiceInternalUri isn’t correct. The parameter is _INTERNAL_. > > You probably want https://OWA001.EDUNET.LOCAL/autodiscover/autodiscover.xml > > To generate the XML file, you have to run the configuration test within > Outlook. > > The SSL error may be specious. I’d want to see the output from the scripts > here: > > > http://theessentialexchange.com/blogs/michael/archive/2014/10/01/testing-exchange-autodiscover-with-powershell.aspx > and > > http://theessentialexchange.com/blogs/michael/archive/2014/09/09/reporting-on-client-access-server-configurations.aspx > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Kennedy, Jim > Sent: Saturday, March 7, 2015 10:13 AM > To: [email protected] > Subject: [NTSysADM] RE: OT Exchange issues. > Importance: High > > Ok, I am here and back at it. > > Autodisoverinternalurl: > > [PS] C:\Windows\system32>Get-ClientAccessServer |fl > identity,autodiscoverserviceinternaluri > > Identity : OWA001 > AutoDiscoverServiceInternalUri : > https://owa.elyriaschools.org/autodiscover/autodiscover.xml > > This XML file does not appear to have any style information associated with > it. The document tree is shown below. > <Autodiscover > xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"> > <Response> > <Error Time="10:05:13.1144637" Id="946717530"> > <ErrorCode>600</ErrorCode> > <Message>Invalid Request</Message> > <DebugData/> > </Error> > </Response> > </Autodiscover> > > > Might be something here, about halfway down it switches to my internal domain > on Autodiscover. Not sure why that is happening. > > PS] C:\Windows\system32>Test-OutlookWebServices -ClientAccessServer "owa001" > > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1019 > ype : Information > essage : A valid Autodiscover service connection point was found. The > Autodiscover URL on this object is https://ow > a.elyriaschools.org/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1006 > ype : Information > essage : Contacted the Autodiscover service at > https://owa.elyriaschools.org/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1016 > ype : Information > essage : [EXCH] The AS service is configured for this user in the > Autodiscover response received from https://owa.e > lyriaschools.org/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1015 > ype : Information > essage : [EXCH] The OAB service is configured for this user in the > Autodiscover response received from https://owa. > elyriaschools.org/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1014 > ype : Information > essage : [EXCH] The UM service is configured for this user in the > Autodiscover response received from https://owa.e > lyriaschools.org/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1016 > ype : Information > essage : [EXPR] The AS service is configured for this user in the > Autodiscover response received from https://owa.e > lyriaschools.org/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1015 > ype : Information > essage : [EXPR] The OAB service is configured for this user in the > Autodiscover response received from https://owa. > elyriaschools.org/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1014 > ype : Information > essage : [EXPR] The UM service is configured for this user in the > Autodiscover response received from https://owa.e > lyriaschools.org/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1022 > ype : Success > essage : Autodiscover was tested successfully. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1104 > ype : Error > essage : The certificate for the URL > https://owa001.edunet.local/autodiscover/autodiscover.xml is incorrect. For SS > L to work, the certificate needs to have a subject of > owa001.edunet.local, but the subject that was found > is *.elyriaschools.org. Consider correcting service discovery, or > installing a correct SSL certificate. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1106 > ype : Information > essage : Contacted the Autodiscover service at > https://OWA001.EDUNET.LOCAL:443/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1116 > ype : Information > essage : [EXCH] The AS service is configured for this user in the > Autodiscover response received from https://OWA00 > 1.EDUNET.LOCAL:443/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1115 > ype : Information > essage : [EXCH] The OAB service is configured for this user in the > Autodiscover response received from https://OWA0 > 01.EDUNET.LOCAL:443/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1114 > ype : Information > essage : [EXCH] The UM service is configured for this user in the > Autodiscover response received from https://OWA00 > 1.EDUNET.LOCAL:443/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1116 > ype : Information > essage : [EXPR] The AS service is configured for this user in the > Autodiscover response received from https://OWA00 > 1.EDUNET.LOCAL:443/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1115 > ype : Information > essage : [EXPR] The OAB service is configured for this user in the > Autodiscover response received from https://OWA0 > 01.EDUNET.LOCAL:443/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1114 > ype : Information > essage : [EXPR] The UM service is configured for this user in the > Autodiscover response received from https://OWA00 > 1.EDUNET.LOCAL:443/autodiscover/autodiscover.xml. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1122 > ype : Success > essage : Autodiscover was tested successfully. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1024 > ype : Success > essage : [EXCH] Successfully contacted the AS service at > https://owa.elyriaschools.org/ews/exchange.asmx. The elaps > ed time was 78 milliseconds. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1026 > ype : Success > essage : [EXCH] Successfully contacted the UM service at > https://owa.elyriaschools.org/ews/exchange.asmx. The elaps > ed time was 0 milliseconds. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1124 > ype : Success > essage : [Server] Successfully contacted the AS service at > https://owa001.edunet.local/ews/exchange.asmx. The elaps > ed time was 390 milliseconds. > unspaceId : ab3cd744-d27a-481d-a623-b48cbcc76bcb > d : 1126 > ype : Success > essage : [Server] Successfully contacted the UM service at > https://owa001.edunet.local/ews/exchange.asmx. The elaps > ed time was 15 milliseconds. > > > > > > > > > > > > From: [email protected] [[email protected]] on > behalf of Michael B. Smith [[email protected]] > Sent: Friday, March 06, 2015 8:07 PM > To: [email protected] > Subject: [NTSysADM] RE: OT Exchange issues. > > Being very specific: > > Are you certain you remembered to set AutodiscoverInternalUri? Lots of folks > miss that one. > > From a failing client, run an email configuration test (just on > autodiscover). What is the XML that gets returned? > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Kennedy, Jim > Sent: Friday, March 6, 2015 8:02 PM > To: [email protected] > Subject: [NTSysADM] RE: OT Exchange issues. > > Dang, hope you are better. > > AutoDiscover is fine, test passes. Set up a profile on a new machine it is > fine....the Outlook self discovery auto set up is working. > > Going home, will check back in later. Need some sleep and will come back > tomorrow. > > From: [email protected] [[email protected]] on > behalf of Michael B. Smith [[email protected]] > Sent: Friday, March 06, 2015 7:45 PM > To: [email protected] > Subject: [NTSysADM] RE: OT Exchange issues. > > I’ve been in the hospital for almost 2 weeks. I haven’t caught up. Sorry. > > Are you certain you remembered to set AutodiscoverInternalUri? Lots of folks > miss that one. > > From a failing client, run an email configuration test (just on > autodiscover). What is the XML that gets returned? > > From: [email protected] [mailto:[email protected]] > On Behalf Of Kennedy, Jim > Sent: Friday, March 6, 2015 7:12 PM > To: [email protected] > Subject: [NTSysADM] OT Exchange issues. > > Exchange list is really quiet, struggling with an issue here. Sorry. > > I rolled up a new Exchange 2010 CAS/Hub and decommissioned the old one. > Transferred all the URL's, and swapped IP's. Internal and external flow is > great, OWA is fine, external OWA and Active Sync is fine. Internal existing > Outlook users are broke. A regular user cannot find the new server when they > start up, and domain admin with an email box can. > > Feels like permissions on Autodiscover.xml or auth on Autodiscover but I have > check that a million times.

