Check ur hosts file first. This error message is generally a good indication of a DNS problem… but if ur sure about DNS…
I can give you a workaround if you want one. But it’s a workaround, not a solution. From: [email protected] [mailto:[email protected]] On Behalf Of Graeme Carstairs Sent: Thursday, December 17, 2015 10:39 AM To: [email protected] Subject: [Exchange] Exchange 2013 Powershell cant connect to local server HI There, I am investigating an issue on an inherited Exchange 2013 set-up, with mismatched uri for internal outlook. I need to run powershell on the Exchange server but when I try to start Exchange Management Shell I get the following Error VERBOSE: Connecting to server server.domain.com<http://server.domain.com>. New-PSSession : [server.domain.com<http://server.domain.com>] Connecting to remote server server.domain.com<http://server.domain.com> failed with the following error message : The WinRM client cannot process the request because the server name cannot be resolved. 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 : ComputerNotFound,PSSessionOpenFailed When I try to google it this error is only referenced via Exchange online. All DNS is fully resolvable and pingable on IPv4 and IP v6. Any suggestions TIA Graeme -- Good news everyone, you have just received an e-mail from me!
