EMS (Exchange management sheel) connection Issue.

I have two exchange server 2013 installed. both are the member of DAG with single site environment.
When i connect EMS on Exch-A , it will connect with no issue , but when i on EXCH-B and try to connect EMS it will connect with EXCH-A instead EXCH-B. I search on google and got few thing to fix like on IIS  go to  -  Application pool (MSExchangepowershell AappPool) Recycling. i did but no luck , i also checked the certification binding with IIS with no issue. Please see the attached Error snapshoot.
EMS1.PNG
Muhammad AliAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Amit KumarCommented:
Please follow this article. This article suggests to run Exchange Management troubleshooter, which will find issues and suggestion fix as well.

Error Message 7
Connecting to remote server failed with the following error message: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service:
0
Muhammad AliAuthor Commented:
I run the EMT shooter, i showing some installation path error. Error snap shoot is attached. Please describe the steps to fix the issue. ?
EMTshooter-error.png
0
Amit KumarCommented:
Change installation path in EMTshooter.ps1 by default it is V14 change it to v15.

I am attaching updated one here in this post. Please remove .txt extension from script files for all. all are related to each other.

Existing
############ Exchange Install Path function ##################################
function DisplayPathError {
$global:exinstall = (get-itemproperty HKLM:\SOFTWARE\Microsoft\ExchangeServer\v14\Setup).MsiInstallPath
$eip = $env:ExchangeInstallPath

to be changed
############ Exchange Install Path function ##################################
function DisplayPathError {
$global:exinstall = (get-itemproperty HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\Setup).MsiInstallPath
$eip = $env:ExchangeInstallPath
EMTshooterNew-.zip
0
Muhammad AliAuthor Commented:
I run the EMT shooter. I got the error message is attached.
EMT-error1.png
0
Amit KumarCommented:
Please try following this article may help you.

winrm quickconfig is the command.

Also verify Windows Remote Management should be running on Exchange B Server. above thing you will have to only on Exchange B Server.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.