This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 81%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGD%3C/text%3E%3C/svg%3E)
Hi Team,
I am trying to install Exchange Server 2016 in Lab environment for testing purposes. I have just one Exchange Server. When I am trying to connect to the Exchange Management Shell, I am getting the below error:
I am trying to run the Exchange Management Shell in the same server where Exchange is installed. I have checked the WinRM services and it is running. I have checked the configuration of WinRM as well, and it shows that it is already set fo remote management.
I am not sure of the issue. Please advise.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 80%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAL%3C/text%3E%3C/svg%3E)
Hi @Garima Das ,
Can you successfully connect to EMS after restarting the server?
If the Andy ‘s reply was helpful, you can click the "Accept Answer" button under his post so that others with similar question can benefit from this thread as well.
If you still have further questions or concerns, feel free to post back.
Hi @Garima Das,
Just checking in to see how things are going on with this thread.
If the reply was helpful, you can click the "Accept Answer" button under this post so that other's with similar question can benefit from this thread as well.
If you still have further questions or concerns, feel free to post back.
All services running? Sounds silly, but give the server a reboot and ensure everything is correctly started after that.