From a11d776c8c481b3c3429d9b2d00d4766a6c23fed Mon Sep 17 00:00:00 2001 From: Zane Mingee Date: Thu, 18 Dec 2014 12:59:37 -0500 Subject: [PATCH] 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. --- .../source/v2/vagrantfile/winrm_settings.html.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/website/docs/source/v2/vagrantfile/winrm_settings.html.md b/website/docs/source/v2/vagrantfile/winrm_settings.html.md index 462ccf56e..add316a40 100644 --- a/website/docs/source/v2/vagrantfile/winrm_settings.html.md +++ b/website/docs/source/v2/vagrantfile/winrm_settings.html.md @@ -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 to use port 4567 to talk to the guest if there is no other option. +
+ +Warning: 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. + +
+Set-Item WSMan:\localhost\Service\AllowUnencrypted -Value True
+Set-Item WSMan:\localhost\Service\Auth\Basic -Value True
+
\ No newline at end of file