After just a little back and forth, we were able to nail this down pretty easily.
...and here is the answer. >From Get-OutlookProvider we have (selected fields): CertPrincipalName : msstd:telstarcaa.scvl.com Server : TTL : 1 OutlookProviderFlags : None Name : EXPR And from Dump-CasInformation.ps1 we have (OutlookAnywhere selected fields): Server : TELSTAR1 Identity : TELSTAR1\Rpc (Default Web Site) MetabasePath : IIS://TELSTAR1.scvl.com/W3SVC/1/ROOT/Rpc SSLOffloading : False ExternalHostname : telstar.scvl.com IISAuthenticationMethods : {Basic} The OutlookAnywhere ExternalHostname should be changed to telstarcaa.scvl.com and the OutlookProvider EXPR CertPrincipalName should be set to null. The reason why the configuration was working is because the OutlookProvider EXPR configuration overrides the OutlookAnywhere configuration. However, best practice says NEVER to modify the OutlookAnywhere EXPR configuration EXCEPT when you have a wild-card certificate. VoilĂ . Or Viola, if you are southern, as I am. :) From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Sunday, August 13, 2017 6:17 PM To: exchange@lists.myitforum.com Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect Please send (off list if you prefer) a complete "Get-OutlookProvider | format-list *". Save the attached file as Get-ServiceConnectionPoint.ps1, run in an elevated PowerShell session: .\Get-ServiceConnectionPoint.ps1 -Verbose Please send me all the output, including the verbose output. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Maglinger, Paul Sent: Saturday, August 12, 2017 12:19 PM To: 'exchange@lists.myitforum.com' Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect When I use aka.ms/exrca it comes back with this in the results: <Type>EXPR</Type> <Server>telstar.scvl.com</Server> <ASUrl>https://telstarcaa.scvl.com/EWS/Exchange.asmx</ASUrl<https://telstarcaa.scvl.com/EWS/Exchange.asmx%3c/ASUrl>> <OOFUrl>https://telstarcaa.scvl.com/EWS/Exchange.asmx</OOFUrl<https://telstarcaa.scvl.com/EWS/Exchange.asmx%3c/OOFUrl>> <OABUrl>https://telstarcaa.scvl.com/OAB/a49ee13a-fc45-432e-9bfc-5ba79242dd72/</OABUrl<https://telstarcaa.scvl.com/OAB/a49ee13a-fc45-432e-9bfc-5ba79242dd72/%3c/OABUrl>> <UMUrl>https://telstarcaa.scvl.com/EWS/UM2007Legacy.asmx</UMUrl<https://telstarcaa.scvl.com/EWS/UM2007Legacy.asmx%3c/UMUrl>> <Port>0</Port> <DirectoryPort>0</DirectoryPort> <ReferralPort>0</ReferralPort> <SSL>On</SSL> <AuthPackage>Basic</AuthPackage> <CertPrincipalName>msstd:telstarcaa.scvl.com</CertPrincipalName> <EwsUrl>https://telstarcaa.scvl.com/EWS/Exchange.asmx</EwsUrl<https://telstarcaa.scvl.com/EWS/Exchange.asmx%3c/EwsUrl>> <EcpUrl>https://telstarcaa.scvl.com/ecp/</EcpUrl<https://telstarcaa.scvl.com/ecp/%3c/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> </Protocol> <Protocol> And the entry for the <server> is incorrect. However when I run #Get-OutlookProvider -Identity EXPR | fl that section is blank. I found something that said if it wasn't blank to run #Set-OutlookProvider -id EXPR -server $null I'm not sure if running it would fix it or not. Also not sure it should be null. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Friday, August 11, 2017 4:55 PM To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com> Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect Does it happen with aka.ms/exrca ? From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Maglinger, Paul Sent: Friday, August 11, 2017 4:15 PM To: 'exchange@lists.myitforum.com' Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect Okay, that made a difference. It's showing all 10 servers and not the 2 ghost servers. I'm still seeing the old server when I test e-mail autoconfiguration. See screenshot. [cid:image001.png@01D31502.5AA3ABB0] Paul -----Original Message----- From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Thursday, August 10, 2017 7:57 PM To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com> Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect Duh My bad. Yes, specify -allServers -----Original Message----- From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Maglinger, Paul Sent: Thursday, August 10, 2017 4:55 PM To: 'exchange@lists.myitforum.com' Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect I'm looking over your script and see at the top where if I wanted to see all servers that I should add an allServers parameter. This parameter appears to be there as [Parameter( Mandatory = $false )] [switch] $allServers = $false Do I need to make a change in the script? What's odd is that it pulled down all the servers the very first time I ran it - now it just pulls down the server it runs on. -----Original Message----- From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Thursday, August 10, 2017 11:13 AM To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com> Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect Curiouser and curiouser. Then I have no explanation. I'm sorry. -----Original Message----- From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Maglinger, Paul Sent: Thursday, August 10, 2017 12:04 PM To: 'exchange@lists.myitforum.com' Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect Nice. All DCs came back with all of the existing Exchange servers and none of the "ghosts". -----Original Message----- From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Thursday, August 10, 2017 10:42 AM To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com> Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect IsValid means that the object passes AD validation. Whenever you assign a value to an object attribute in AD it goes through a validation routine based on the OID of the attribute type. IsValid means that all attribute values pass those validation routines on an object. To answer your specific question: no. But there is a potentially interesting experiment to try. Let's assume you have a list, $dcs, of the fqdn's of your domain controllers. $dcs = 'dc1.scvl.com', 'dc2.scvl.com', 'dc3.scvl.com' foreach( $dc in $dcs ) { "*** $dc ***" Get-ExchangeServer -Status -DomainController $dc } Does the output change based on the DC specified? -----Original Message----- From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Maglinger, Paul Sent: Thursday, August 10, 2017 11:07 AM To: 'exchange@lists.myitforum.com' Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect I tried the script on one of the mailbox servers and it only came back with the server I ran it on. For some reason when I ran your script the first time it came back with everything. Since that it's only coming back with the server I run the script on. And again, when I run Get-ExchangeServer on the EMS it comes back with all the CAS/HUB and mailbox servers and not the 2 I saw on the first run. I'm intrigued by that first listing showing the decommissioned servers where IsValid was marked as True. Does that give a clue where these 2 servers are hiding? Paul -----Original Message----- From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Wednesday, August 09, 2017 5:10 PM To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com> Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect That begins to sound like AD DS weirdness. -----Original Message----- From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Maglinger, Paul Sent: Wednesday, August 9, 2017 5:56 PM To: 'exchange@lists.myitforum.com' Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect Okay, this is weird. When I ran the script the first time there were 12 servers listed under the ExchangeServer header - including 2 that were decommissioned. Now when I run it there is only one - and it's the one I ran the script from and should be there but I don't see the other 9. -----Original Message----- From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Wednesday, August 09, 2017 4:31 PM To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com> Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect That doesn't make any sense. That's exactly what the script does: $parameters = @{ 'Status' = $true } if( -not $allServers ) { $parameters += @{ 'Identity' = $env:ComputerName } } $r = Get-ExchangeServer @parameters $r | fl Name, Identity, Fqdn, Edition, Site, OrganizationalUnit, ServerRole, AdminDisplayVersion, ExchangeVersion, Static*, Current*, Is* -----Original Message----- From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Maglinger, Paul Sent: Wednesday, August 9, 2017 5:22 PM To: 'exchange@lists.myitforum.com' Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect No, they do not show up. -----Original Message----- From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Wednesday, August 09, 2017 4:10 PM To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com> Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect Does "Get-ExchangeServer -Status" find the old servers? I bet it does... -----Original Message----- From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Maglinger, Paul Sent: Wednesday, August 9, 2017 5:00 PM To: 'exchange@lists.myitforum.com' Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect Interesting. When I run your script 2 decommissioned Exchange servers show up under the ExchangeServer header. When I run a Get-ExchangeServer command alone they do not. So what information are you pulling down that the Get-ExchangeServer alone isn't? Additionally, everything listed under those 2 servers is either null or "False" except for "IsValid" which is "True" Paul -----Original Message----- From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Wednesday, August 09, 2017 3:28 PM To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com> Subject: [Exchange] RE: Test E-mail AutoConfiguration HTTP protocol server name incorrect Run this. (Save as ps1, run in Exchange Management Shell, the output is rather voluminous, so you should probably redirect to a file.) This should tell you where the old server name is referred to. I haven't tested this on Exchange 2010 in a while, but I think it should still work. -----Original Message----- From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Maglinger, Paul Sent: Wednesday, August 9, 2017 3:48 PM To: 'exchange@lists.myitforum.com' Subject: [Exchange] Test E-mail AutoConfiguration HTTP protocol server name incorrect Exchange 2010 SP3 UR17 When I run Test E-mail Autoconfiguration on my workstation everything looks good except under the Exchange HTTP protocol heading where it has the server name. The server listed was one that we decommissioned a while back. I have Googled and searched for where this is coming from and I can't find it. Can someone tell me where this can be changed? TIA, Paul PS - Apologies if this is a multiple post - our spam filter seems to have acquired a dislike for the list's messages and I'm working on that.