But I still had some trouble setting up WinRM. As a quick and dirty check before you go to the effort of creating the box, add a port forward in virtualbox for the winrm port 5985:
And try hitting this URL:
$ wget http://localhost:5985/wsman --2015-03-23 13:25:00-- http://localhost:5985/wsman Resolving localhost (localhost)... ::1, 127.0.0.1 Connecting to localhost (localhost)|::1|:5985... failed: Connection refused. Connecting to localhost (localhost)|127.0.0.1|:5985... connected. HTTP request sent, awaiting response... 405 2015-03-23 13:25:00 ERROR 405: (no description).You should get a successful connection, but an error as above because this isn't a valid winrm call. If that doesn't work make sure you followed the vagrant instructions for enabling winrm. Try running this inside the VM:
winrm quickconfig -qIn my case quickconfig complained that:
WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again.But when I looked at network connections in the network connection manager I couldn't change the VirtualBox host networking adapter type as advised. This is a known problem where Windows 7 network connections get stuck in public, I fixed it with this tool from Microsoft. You can verify your winrm configuration is functioning correctly by installing pywinrm and running a command:
In [33]: import winrm In [34]: s = winrm.Session('127.0.0.1', auth=('vagrant', 'vagrant')) In [35]: s.run_cmd('ver').std_out Out[35]: '\r\nMicrosoft Windows [Version 6.1.7601]\r\n'
No comments:
Post a Comment