Hello to all,
Is there a way to influence the order of the SCP entries in AD for Autodiscover?
We have 2 Exchage in use.
"Exchange_old" is always addressed first during autodiscover and is then redirected to "Exchange_not_quite_so_old".
It's not dramatic, but it would be nice if that could be changed.
Unfortunately I have not found anything on the net.
Best regards
Stefan
It makes sense not to enter exchange_alt or Exchange_nicht_so_alt there, but the autodiscover.domain.tld (or an internal name for non-split DNS).
Okay...
perhaps expressed somewhat unclearly.
Let's say the old server is called "alt.localdomain.local" and the newer server is called "derneuere.localdomain.local".
Then, of course, the host name of both incl "/Autodiscover/Autodiscover.xml" is in the AD as SCP.
The question is can I change the order in which the SCP's are addressed by the client.
The client always requests the "alt.localdomain.local" first.
VG
Stefan
You should not enter the host name, but only one for all. For example, Autodiscover which then refers to both via roundrobin (if they are the same version), or only to the new one.
Hi @norbertfe,
I have the same issue somehow. And it still doesn't tell me anything about entering Roundrobin?
1 Excange-2013, 1 Exchange 2019
The Exch2019 was installed more out of interest than anything else, without any function. All URLs are stored on real URLs with a valid public certificate.
In Exch2019 I can see the connections of the clients and Outlook connection status also shows me connections to Exch2019. Although there is actually nothing there? Except perhaps a redirection to the Exch2013?
If the Exch2019 is not started (which actually has no function yet, holds no mailboxes and nothing), the Outlook clients no longer start.
I think that's down to the SCP:
Exch2019:
AutoDiscoverServiceInternalUri : https ://autodiscover. Domain .at/ Autodiscover/ Autodiscover.xml
AutoDiscoverServiceGuid : same-ID
AutoDiscoverSiteScope : {Default- First-Site -Name}
Exch2013 (main server):
AutoDiscoverServiceInternalUri : https ://m. Domain .at/ AutoDiscover/ AutoDiscover.xml
AutoDiscoverServiceGuid : same-ID
AutoDiscoverSiteScope : {Default- First-Site -Name}
On both servers, both domains/URLs are included in the certificate (a list of 5 domains/subdomains) via Letsencrypt/Certifytheweb.
Using the internal DNS server, I would have directed both urls autodiscover. domain. at + m. domain. at to the old Exchange2013.
Nevertheless, the clients do not start when the Exch2019 is offline. If the clients are started and I switch off the Exch2019 in the meantime, there is still a connection to the server and email browsing works, but sending emails no longer works. and the send connector on the Exch2013 is not working. There is no Sendconnector on the Exch2019.
Nevertheless, the infrastructure now only works when the Exch2019 is running, which actually has no function.
How does this work or what needs to be changed here? Hopefully not delete the Exch2019 right away so that it works again without it?
Thank you for your answer and your time,
lg Roman
PS: had to adjust it a bit because the forum thinks I'm posting spam here.
How does this work or what needs to be changed here? Hopefully not delete the Exch2019 right away so that it works again without it?
Just enter the value of the old server in both SCPs. Alternatively, let autodiscover.domain.tld point to the old Exchange 2013. My description above is not that difficult to understand ;)
PS: had to adjust it a bit because the forum thinks I'm posting spam here
Hmm, the forum is currently filtering a bit too sharply. Had the same issue with the customer earlier ;)
Bye
Norbert
How does this work or what needs to be changed here? Hopefully not delete the Exch2019 right away so that it works again without it?
Just enter the value of the old server in both SCPs. Alternatively, let autodiscover.domain.tld point to the old Exchange 2013. My description above is not that difficult to understand ;)
PS: had to adjust it a bit because the forum thinks I'm posting spam here
Hmm, the forum is currently filtering a bit too sharply. Had the same issue with the customer earlier ;)
Thanks Norbert, I have put all entries on Mx1, there all domains in the certificate and now the Exch2019 can be switched off and everything works as usual. In the Outlook connection display I now see both entries for Mx1 and Mx2, but both lead to Exch2013, Outlook does not complain, mailboxes are all present, no problems in sight.
Perfect. Thanks, I now have a Sleeping-Exch2019 that I can switch on and transfer mailboxes as required.
Top!
AutoDiscoverSiteScope : {Default- First-Site -Name}
How many sites do you have? Usually you just leave the value blank ;)
AutoDiscoverSiteScope : {Default- First-Site -Name}
How many sites do you have? Usually you just leave the value blank ;)
thanks, I'll try it out - I haven't changed anything here, there's only one site, this "default-first-site-name" that the Exch installation specified back then and I haven't changed. Using Dns records it works anyway, I'll just delete the sitescope and see if anything changes.
Thank you
this "default-first-site-name" that the Exch installation
That was not Exchange but dcpromo. ;)
