AutoDiscover for Exchange Hybrid

Namless Shelter 231

Hi I have been removing our Old Exchange server 2010 from our Hybrid Environment (Exchange 2010 & Exchange 2016 & Office 365) . Now if I turned off Exchange 2010 server, seems AutoDiscovery is very slow, took about 2 minutes to find the user profile when setting up Outlook. So what would be the best way to check and move Autodiscover to the new Exchange sever? DNS Autodiscover has been pointing to Exchange 2016 server already.

Thanks
ML

Joyce Shen - MSFT 16,671 Reputation points

2020-09-14T01:25:59.393+00:00

Hi @Namless Shelter , any update about your issue?

6 answers

Joyce Shen - MSFT 16,671 Reputation points

2020-10-07T02:58:58.403+00:00

Hi @Namless Shelter , in a Exchange 2010 and 2016 coexistence environment, we will make sure the DNS record point to the Exchange 2016 server, and set AutoDiscoverServiceInternalURI: https://autodiscover.domain.com/Autodiscover/Autodiscover.xml for both Exchange 2010 and 2016 server.
For the mailboxes on Exchange 2010 server, the requests will be proxyed by 2016 to them.

Internal DNS
webmail.domain.com Point to Exchange 2016 server
autodiscover.domain.com Point to Exchange 2016 server
External DNS
webmail.domain.com Point to Exchange 2016 server
autodiscover.domain.com Point to Exchange 2016 server

Referring to this link to get more information: Client Connectivity in an Exchange 2016 Coexistence Environment with Exchange 2010
Please sign in to rate this answer.
Namless Shelter 231 Reputation points

2020-10-07T03:03:01.447+00:00

Hi Thanks

Our Firewall system is pretty messy at the moment, there are lots legacy staff. Will take sometimes to clean up. I think all all DNS entries are pointing back to the new server.. So if I delete this SCP for old Exchange server, try Setting up a new profile on a PC. If it did not work, I can still add back the old SCP, like:
Set-ClientAccessServer -Identity ex2010 -AutodiscoverServiceInternalUri https://autodiscover.domainname.edu/Autodiscover/Autodiscover.xml

AM I correct?

Thanks
ML

Joyce Shen - MSFT 16,671 Reputation points

2020-10-07T05:06:56.167+00:00

Hi @Namless Shelter , that's right.

Namless Shelter 231 Reputation points

2020-10-07T23:42:14.743+00:00

When running: set-ClientAccessServer -identity EX01 -AutoDiscoverServiceInternalUri $null on Exchange 2016 server.

I got this error (mail01 is Exchange 2016):

You can't make this change because 'CN=EX01,CN=Servers,CN=Exchange Administrative Group
(FYDIBOHF23SPDLT),CN=Administrative Groupsxxxxx

=au' is read-only to the current version of
Exchange.

+ CategoryInfo : InvalidOperation: (:) [Set-ClientAccessServer], CannotModifyCrossVersionObjectException + FullyQualifiedErrorId : [Server=MAIL01,RequestId=09188cba-c798-42ed-8d28-a89f27ec9438,TimeStamp=7/10/2020 11:38:

08 PM] [FailureCategory=Cmdlet-CannotModifyCrossVersionObjectException] C84E4D3D,Microsoft.Exchange.Management.Sys
temConfigurationTasks.SetClientAccessServer
+ PSComputerName : mail01.domainname.edu

We are running a hybrid of Exchange 2010 and Exchange 2016.

So how do we delete this SCP for the old Exchange server? Should I run this command on old server itself?

Thanks

Namless Shelter 231 Reputation points

2020-10-08T03:39:35.127+00:00

Also, did a bit research, found out these:

Get-Mailbox -Arbitration

Name Alias ServerName ProhibitSendQuota

SystemMailbox{1f05a927... SystemMailbox{1f0... ex01 Unlimited
SystemMailbox{e0dc1c29... SystemMailbox{e0d... ex01 Unlimited
FederatedEmail.4c1f4d8... FederatedEmail.4c... ex01 1 MB (1,048,576 bytes)
SystemMailbox{bb558c35... SystemMailbox{bb5... mail01 Unlimited
Migration.8f3e7716-201... Migration.8f3e771... mail01 300 MB (314,572,800 bytes)
SystemMailbox{D0E409A0... SystemMailbox{D0E... mail01 Unlimited
SystemMailbox{2CE34405... SystemMailbox{2CE... mail01 Unlimited

Should I move all Three Arbitration mailboxes from Old exchange database to New Exchange database? so I can delete SCP connector?

Thanks
ML

Namless Shelter 231 Reputation points

2020-10-08T22:43:27.86+00:00

When running: set-ClientAccessServer -identity EX01 -AutoDiscoverServiceInternalUri $null on Exchange 2016 server.

I got this error (mail01 is Exchange 2016):

You can't make this change because 'CN=EX01,CN=Servers,CN=Exchange Administrative Group
(FYDIBOHF23SPDLT),CN=Administrative Groupsxxxxx

=au' is read-only to the current version of
Exchange.

CategoryInfo : InvalidOperation: (:) [Set-ClientAccessServer], CannotModifyCrossVersionObjectException

FullyQualifiedErrorId : [Server=MAIL01,RequestId=09188cba-c798-42ed-8d28-a89f27ec9438,TimeStamp=7/10/2020 11:38:
08 PM] [FailureCategory=Cmdlet-CannotModifyCrossVersionObjectException] C84E4D3D,Microsoft.Exchange.Management.Sys
temConfigurationTasks.SetClientAccessServer

PSComputerName : mail01.domainname.edu

We are running a hybrid of Exchange 2010 and Exchange 2016.

So how do we delete this SCP for the old Exchange server? Should I run this command on old server itself?

Thanks

Joyce Shen - MSFT 16,671 Reputation points

2020-10-09T01:22:28.313+00:00

Hi, don't set the -AutoDiscoverServiceInternalUri $null on Exchange 2016 server.

What's the result if you run Set-ClientAccessServer -Identity "ex2010 server" -AutodiscoverServiceInternalUri $null ?

And for the system mailboxes. Yes, we will need to migrate them to the new server. Don’t forget the System Mailboxes!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

AutoDiscover for Exchange Hybrid

6 answers

Your answer