?
Solved

Exchange 2010 EMC/Powershell error connecting to DAG member

Posted on 2016-07-31
4
Medium Priority
?
52 Views
Last Modified: 2016-08-25
Exchange 2010 SP3 with UR14 on all members.

Pre-question question: should the EMC and EMS be able to connect to Exchange servers with only the Mailbox role installed?

2 servers with HT/CAS roles (not a CAS array)
2 servers with mailbox role only - DAG, failover cluster

The Exchange Management Console will connect to the HT/CAS servers from the console on any of the Exchange servers.

None of the servers will connect to the 2 servers with only the Mailbox role.  The error in the EMC is:

The attempt to connect to http://<fqdn-of-mbx-server>/PowerShell using "Kerberos" authentication failed: Conecting to the remote server <fqdn-of-mbx-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 accepting requests.  Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM.

I've checked dozens of similar messages and solutions, ranging from time sync issues to incorrect settings on the PowerShell virtual directory on the affected servers.
0
Comment
Question by:snowdog_2112
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 27

Assisted Solution

by:☠MAS☠
☠MAS☠ earned 2000 total points
ID: 41737493
0
 

Accepted Solution

by:
snowdog_2112 earned 0 total points
ID: 41763558
Sorry for the delay.

I found the answer - too obvious:  "unsupported OS"

The server was originally provisioned with 2012r2.
Oddly, it had been working for well over a year aside from the EMC issue.  The EMC issue was only discovered in trying to resolve an issue on the CAS.

Thanks.
0
 
LVL 27

Expert Comment

by:☠MAS☠
ID: 41763614
Glad to know you fixed it and thanks for sharing.

Thanks
MAS
0
 

Author Closing Comment

by:snowdog_2112
ID: 41769949
I didn't run the troubleshooting tool - I assume it would check OS version and likely would have told me it was unsupported.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
New style of hardware planning for Microsoft Exchange server.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
This video discusses moving either the default database or any database to a new volume.
Suggested Courses
Course of the Month14 days, 16 hours left to enroll

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question