Enable WinRM Manually - Setup for Hyper-V, VMM, Exchange Targets

Document created by bsong Expert on Jun 7, 2016Last modified by praveen.vaddepally on Jul 18, 2018
Version 15Show Document
  • View in full screen mode

Enabling WinRM is required to connect to Hyper-V, VMM, or Exchange targets. To enable WinRM manually on a target, just run the following commands via PowerShell. To enable on multiple targets at once, see the posts below on how to do this via GPO or PsExec.


Set-WSManQuickConfig -Force

Set-Item WSMan:\localhost\Service\AllowUnencrypted -Value $True


Optional - the following command is only needed for local users:

Set-Item WSMan:\localhost\Service\Auth\Basic -Value $True



Enable multiple Hyper-V, VMM, Exchange targets via GPO:

WSMan service configuration using domain GPO or for HTTPS WSMan/WinRM over HTTPS service configuration


Enable multiple Hyper-V, VMM, Exchange targets via PsExec:

Enable/Disable WinRM on remote hosts



IMPORTANT: If you are adding a VMM target, you still need to enable WSMAN / WinRM on the underlying Hyper-V hosts and clusters as well. 





If targeting is still failing, it is good to confirm that "AllowUnencrypted" has been set to "true". Oftentimes, this setting is still set to "false" and will prevent targeting. You can run the following PowerShell command to confirm that in the Service category, AllowUnencrypted is set to "true":


winrm get winrm/config


3 people found this helpful