Score:0

Exchange 2013 PowerShell EMS not working

us flag

I get the following error when opening EMS on my local 2013 server (or remotely). EMS has worked fine up until recently and I'm not sure what caused the issue. I've read many articles and forum posts and none of the suggestions have worked.

Thanks,

Travis

Error:

 New-PSSession : [servername] Connecting to remote server servername failed with the
following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested
HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management
protocol. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : URLNotAvailable,PSSessionOpenFailed
Score:1
cn flag

The issue has been documented in this link https://docs.microsoft.com/en-us/exchange/troubleshoot/administration/connecting-remote-server-failed enter image description here Try following the steps to run EMTshoote

us flag
Thanks for this. I was looking for this utility yesterday and somehow couldn't find it. Now, when I run it, it says that the user isnt PSremote enabled. This user has always been able to user PSRemote. All my other admins get the same message. Is there a way to check to see what users are remote PS enabled without running a script from a remote PS enabled account? Is there a way to turn it on for all users without being logged in as a remote PS enabled user?
cn flag
Sorry,I don’t think that you could enable the PSremote without being logged in as a remote PS enabled user. And you may need to re-enable the Psmore manully.
us flag
I re-enabled psremote through regular PS, just in case it was turned off but it was not. Do you have any thoughts on what would return this error if users really were still enabled?
Score:0
us flag

I have figured this out. A binding got wiped out on IIS. I don't know why it didn't occur to me, but our internal DNS scheme is different than our external. I had to re-add the binding for the internal servername.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.