haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Added documentation for enabling unencrypted WinRM 

Per GH#4752, unencrypted WinRM access must be configured on the guest
machine before Vagrant can communicate with the box. This is sometimes
enabled by default on public boxes, but needs to be documented for
those of us that are using custom made boxes.
This commit is contained in:
Zane Mingee 2014-12-18 12:59:37 -05:00
parent c0db48b0ab
commit a11d776c8c
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
website/docs/source/v2/vagrantfile/winrm_settings.html.md
View File

@ -44,3 +44,17 @@ example, if this is set to 5985 (the default), and Vagrant detects a forwarded
port to port 5985 on the guest from port 4567 on the host, Vagrant will attempt port to port 5985 on the guest from port 4567 on the host, Vagrant will attempt
to use port 4567 to talk to the guest if there is no other option. to use port 4567 to talk to the guest if there is no other option.
<hr>
<strong>Warning:</strong> In order for Vagrant to communicate with a Windows
guest, you must allow unencrypted WinRM connections on the guest machine
itself. Some public boxes already have this configured, but if you are
attempting to `vagrant up` a Windows box and the command hangs at
`Waiting for WinRM to become available...`, then you will need to run the
commands below on the guest machine itself, at the box setup stage,
after provisioning, or through a start up script.
<pre class="prettyprint">
Set-Item WSMan:\localhost\Service\AllowUnencrypted -Value True
Set-Item WSMan:\localhost\Service\Auth\Basic -Value True
</pre>