question

MichaelEriksson-2831 avatar image
0 Votes"
MichaelEriksson-2831 asked KaelYao-MSFT answered

Powershell and EAC still connects to old servers after migration

I just mygrated from Exchange 2013 to Exchange 2019 and everything went well. But one thing starts to annoy me. When I use EMS and/or EAC it still connects to the Exchange 2013 environment and the server on which my admin account "lived" before the migration.

I tried to logout and restart the computer from which I run the EMS from, I deleted the C:\Users\username\AppData\Roaming\Microsoft\Exchange\RemotePowerShell folder. I searched through the registry. Restarted the two powershell application pools on the old Exchange 2013 server etc...But no luck.

Anyone got Ideas?

Regards

Michael

office-exchange-server-administrationoffice-exchange-server-itpro
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AndyDavid avatar image
0 Votes"
AndyDavid answered MichaelEriksson-2831 commented

What does the connection string look like that you are using to connect? Did you update to point to the 2019 servers?

I assume you moved all the arbitration mailboxes to 2019 as well.

· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

Thanx for you reply.

Honestly I do not know how the connection string looks like, I just open the EMS and browse to the EAC using the EAC URL. I do not do a pssession. Can I check it?

Yes I moved all the arbitration mailboxes and the one connected to my Exchange Admin user.

Regards

Michael

0 Votes 0 ·
AndyDavid avatar image AndyDavid MichaelEriksson-2831 ·

Do you do this from the Exchange Server itself ? or a workstation?

Sounds like a workstation or something with the Exchange mgmt tools installed?

0 Votes 0 ·

I do it from something we call an Admin Server, so like a workstation. It's an ordinary Windows server 2019 with Exchange management tools, Skype for Business tools etc installed. We use it for daily management, running schedule tasks etc.

Regards

Michael

0 Votes 0 ·
AndyDavid avatar image AndyDavid MichaelEriksson-2831 ·

OK, thats normal then. As long as the 2013 server is avail and up and running, Powershell can connect to it.

If you dont want to use that server, remove Exchange from it or use a connection string that specifies the 2019 server when remoting

https://docs.microsoft.com/en-us/powershell/exchange/connect-to-exchange-servers-using-remote-powershell?view=exchange-ps

 $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://<ServerFQDNof2019Server>/PowerShell/ -Authentication Kerberos -Credential 
 $UserCredential
0 Votes 0 ·
KaelYao-MSFT avatar image
0 Votes"
KaelYao-MSFT answered

Hi, Michael.

To change the server EMS connects to, please follow these steps:
1.locate the path of EMS, by default it should be like C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Exchange Server 2019
2.right click on "Exchange Management Shell" and select "Properties"
3.in "Target", change the "Connect-ExchangeServer -auto" part to "Connect-ExchangeServer <FQDN of Exchange 2019 server>"
81765-03.png

Launch EMS and check if it connects to the Exchange 2019 server instead of the Exchange 2013 server.


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.


03.png (10.5 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.