New-PSSession : [exch-2013-01.chennai.com] Connecting to remote server exch-2013-01.chennai.com failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. 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], PSRemotingTransportException + FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionOpenFailed
VERBOSE: Connecting to EXCH-2013-01.CHENNAI.COM.
To fix the issue: Open the command prompt with elevated Administrative rights an d run the command "WinRM QuickConfig"
Once it is done, you will get the Message as mentioned below
C:\Users\administrator.CHENNAI>winrm quickconfig
WinRM service is already running on this machine.
WinRM is not set up to allow remote access to this machine for management.
The following changes must be made:
Create a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this
machine.
Enable the WinRM firewall exception.
Make these changes [y/n]? Y
WinRM has been updated for remote management.
Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this
machine.
WinRM firewall exception enabled.
Then close and re open the Exchange Management shell, issue will be resolved. Please inform if us if the issue is not resolved. Leave your comments if this solution works
I get the exact error message as described. I ran the command WinRM QuickConfig on powershell running as administrator. Got the message that WinRM was not configured as expected. Answered Y to the prompt. It ran ok. Then tried to open Exchange shell and got the same error again. Not sure what to do next.
ReplyDelete