Cannot deleting SCP on Hybrid Exchange 2010 & 2016

Question

Cannot deleting SCP on Hybrid Exchange 2010 & 2016

Namless Shelter 241

Hi I have been removing the Old AutoDiscover SCP on Exchange server 2010 from our Hybrid Environment (Exchange 2010 & Exchange 2016 & Office 365) .

Now if run: set-ClientAccessServer -identity ex2010 -AutoDiscoverServiceInternalUri $null on our new Server 2016 Server, it gave me this error:

You can't make this change because 'CN=EX2010,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=ex2016,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 : ex2016.domainname.edu

Did a bit research, it might be related to Mailbox Anchoring issue. Also someone suggested to move Administrator@keyman mailbox to the 2016 Server, as I checked, it is already on the new server..

Also, I noticed:

[PS] C:\Windows\system32>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

What else can I do? Move the three Arbitration mailboxes from Old exchange database to New Exchange Server database? Will it fix the issue of cannot delete SCP connector? Also, it would not have any impact on our hybrid Ex2010 and Ex2016 environment (There are still some disabled User mailboxes on Ex2010) ?

Thanks,
ML

3 answers

Your answer

Answer 1

Ashok M 6,846

Hi,

Can you try the below steps and see if that helps,

If admin mailbox is on Exchange 2016, are you able to see both the exchange servers listed in Get-ExchangeServer command from Exchange 2016 EMS
Can you try with a different administrator account by providing the necessary Exchange permissions
Try removing the powershell cookie and see if the resolves it
Move the arbitration mailboxes from Exchange 2010 to 2016

https://exchangemaster.wordpress.com/2016/01/06/mailbox-anchoring-affecting-new-deployments-upgrades/

https://blog.rmilne.ca/2016/09/15/when-to-move-arbitration-mailboxes/

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. Also, export the registry before making any changes and incorrect configuration may lead to other issues.

Namless Shelter 241 Reputation points

2020-10-08T22:32:49.67+00:00

Hi Thanks for that

What impact will arbitration mailboxes have if they are deleted or moved?

Thanks
ML
Namless Shelter 241 Reputation points

2020-10-08T23:48:09.437+00:00

Also, which command should I use on Server 2016 Exchange to delete old Ex2010 SCP connector:

Set-ClientAccessServer -AutoDiscoverServiceInternalUri $Null

or

Set-ClientAccessService -AutoDiscoverServiceInternalUri $Null

Maybe it is the command issue?

Thanks

Answer 2

Lydia Zhou - MSFT 2,386 Microsoft Employee

@Namless Shelter

Arbitration mailboxes are used for storing different types of system data and for managing messaging approval workflow. When we upgrade from Exchange 2010 to Exchange 2016, it's suggested to move all arbitration mailboxes to Exchange 2016 before moving user mailboxes. Otherwise, some action may not be taken from Exchange 2016.

As AshokM-8240 mentioned, please move arbitration mailboxes to Exchange 2016, then run the command again.

Here is a blog about arbitration mailboxes, you can check for more details: Arbitration Mailboxes – Lay of The Land.
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Namless Shelter 241 Reputation points

2020-10-09T02:27:01.847+00:00

Thanks for that. We are planning to decommission Ex2010 end of this year, there are some old users still existed. I just want to delete SCP connector for now. Not sure if it is worthy to move arbitration mailboxes to new Exchange 2016 server? As EX2010 is going. Or we have to move arbitration mailboxes to the new database on new 2016 server?

Also, can I safely run: Set-ClientAccessService -AutoDiscoverServiceInternalUri $Null on new Ex2016 to remove one SCP? There are currently two SCP connectors for autodiscover on Ex2016 at the moment.

Thanks
ML
Namless Shelter 241 Reputation points

2020-10-09T03:30:30.707+00:00

@Lydia Zhou - MSFT

Thanks for that. We are planning to decommission Ex2010 end of this year, there are some old users still existed. I just want to delete SCP connector for now. Not sure if it is worthy to move arbitration mailboxes to new Exchange 2016 server? As EX2010 is going. Or we have to move arbitration mailboxes to the new database on new 2016 server?

Also, can I safely run:

Set-ClientAccessService -AutoDiscoverServiceInternalUri $Null

on new Ex2016 to remove one SCP?

Maybe the previous command on Ex2016 is not working:

Set-ClientAccessServer -AutoDiscoverServiceInternalUri $Null

There are currently two SCP connectors for autodiscover on Ex2016 at the moment.

Thanks
ML
Ashok M 6,846 Reputation points

2020-10-09T06:44:52.943+00:00

Please move the arbitration mailboxes to Exchange 2016 . As LydiaZhou-MSFT stated, arbitration mailboxes are used for various functions and follow the link for more information.

Also, set AutoDiscoverServiceInternalUri to Null only for Exchange 2010 and not for Exchange 2016. Incorrect configuration will lead to issues with internal outlook autodiscover as the first method is to connect via SCP.

Answer 3

Namless Shelter 241

Hi @Lydia Zhou - MSFT

After moved all three Arbitration Mailboxes to the new database on ex2016, I am still getting this error when I was running: Set-ClientAccessService -identity EX01 -AutoDiscoverServiceInternalUri $null on Ex2016:

You can't make this change because 'CN=ex2010,CN=Servers,CN=Exchange Administrative Group
(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Mercedes,CN=Microsoft
Exchange,CN=Services,CN=Configuration' is read-only to the current version of
Exchange.
+ CategoryInfo : InvalidOperation: (:) [Set-ClientAccessService], CannotModifyCrossVersionObjectException
+ FullyQualifiedErrorId : [Server=MAIL01,RequestId=09188cba-c798-42ed-8d28-a89f27ec9438,TimeStamp=9/10/2020 5:28:1
7 AM] [FailureCategory=Cmdlet-CannotModifyCrossVersionObjectException] C84E4D3D,Microsoft.Exchange.Management.Syst
emConfigurationTasks.SetClientAccessService
+ PSComputerName : ex2016.domainname.edu etc

What else should I try? Run the command on Ex2010?

ML

Ashok M 6,846 Reputation points

2020-10-09T06:40:26.26+00:00

Hi,

Are you able to see the Exchange 2010 servers when you run Get-ExchangeServer from Exchange 2016 EMS?
Open the Windows Powershell as Run as administrator and add the snapin,

Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn

Then try Set-ClientAccessService -identity EX01 -AutoDiscoverServiceInternalUri $null

If the Exchange 2010 is still powered on, better to try from that as well by running Set-ClientAccessServer

If still not working, remove the powershell cookie and try again

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WSMAN\Client\ConnectionCookies

https://exchangemaster.wordpress.com/2016/01/06/mailbox-anchoring-affecting-new-deployments-upgrades/

Please note: Export the registry before making any changes and incorrect configuration may lead to other issues.
Lydia Zhou - MSFT 2,386 Reputation points Microsoft Employee

2020-10-09T06:48:00.933+00:00

Yes, you have to run the command on Exchange 2010. I test in my Exchange 2010, 2013 and 2016 coexisting environment, your issue can be reproduced and the AutoDiscoverServiceInternalUri of Exchange 2010 can be modified successfully on Exchange 2010.
When Exchange 2010 coexists with higher Exchange versions, some configuration have to be set from Exchange 2010. This should be the reason for this issue as well.

Additionally, on Exchange 2010, you have to use "Set-ClientAccessServer":

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Lydia Zhou - MSFT 2,386 Reputation points Microsoft Employee

2020-10-13T01:32:27.043+00:00

@Namless Shelter

Is there any update on this thread?
Did you modify the autodiscover internal Uri successfully from Exchange 2010?

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Namless Shelter 241 Reputation points

2020-10-13T05:31:25.42+00:00

Hi Thanks a lot for that. I am planning to run this during the school holiday. Now we are in production period, do not wanna have any outages.

I will accept this answer for now.

Thanks hips.

Mang
Lydia Zhou - MSFT 2,386 Reputation points Microsoft Employee

2020-10-14T01:07:38.907+00:00

That's OK. Hope everything works well on your side. You're welcomed to post back if you have something to share.

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Lydia Zhou - MSFT 2,386 Reputation points Microsoft Employee

2020-10-20T06:08:09.047+00:00

Just checking in to see if above information was helpful. Please let us know if you would like further assistance.

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Namless Shelter 241 Reputation points

2021-05-31T05:35:43.897+00:00

Hi Lydias,

Sorry about the late response.

Now I am back to this job. I can see on two servers:

On Exchange 2016 server:

It has two SCP connectors: ex2010 and ex2016.

On Exchange 2010 server:

It has only one SCP connectors ex2010 .

If I want to decommission Exchange 2010 server only for now .

Should I run this command only on Exchange server 2010:

set-ClientAccessServer -identity EX2010 -AutoDiscoverServiceInternalUri $null

?

Or I have run:

set-ClientAccessService -identity EX01 -AutoDiscoverServiceInternalUri $null

on Exchange 2016 server?

Thanks a lot
ML

Share via

Cannot deleting SCP on Hybrid Exchange 2010 & 2016

3 answers

Your answer