vagrant-windows 1.2.0 → 1.3.1

data/CHANGELOG.md

@@ -0,0 +1,38 @@
+## Changelog
+
+0.1.1
+
+- Remove extra debug information from command output.
+
+0.1.2
+
+- Added virtual box 4.2 support.
+
+0.1.3 
+
+- Added puppet provisioner.
+
+1.0.0 
+
+- Converted to Vagrant 1.1.x plugin architecture.
+
+1.0.1 
+
+- Fix #29 Monkey Patch the 4.2 driver to include read_mac_addresses. 
+  - use read_mac_addresses in all cases.
+
+1.0.3 
+
+- Added vagrant shell provisioner. The built-in shell provisioner tried to chmod the target script which doesn't make sense on windows.
+- Can now run the vagrant-windows plugin via bundle exec instead of vagrant plugin install (for plugin dev).The vagrant src root finding logic didn't work from a bundle, but the native Vagrant src root does.
+- Readme fixes/updates.
+
+1.2.0
+
+- Converted to Vagrant 1.2.x plugin architecture.
+- Various networking fixes.
+- Chef provisioner runs through the Windows task scheduler instead of ps_runas power shell script.
+
+1.2.1
+
+- Fixed issue 91, drive mapping was failing on Vagrant 1.1.

data/Gemfile

@@ -7,5 +7,6 @@ group :development do
   # We depend on Vagrant for development, but we don't add it as a
   # gem dependency because we expect to be installed within the
   # Vagrant environment itself using `vagrant plugin`.
-  gem "vagrant", :git => "git://github.com/mitchellh/vagrant.git", :tag => 'v1.2.2'
+  gem "vagrant", :git => "git://github.com/mitchellh/vagrant.git", :tag => 'v1.3.5'
+  gem "mocha", :require => false
 end

data/LICENSE

@@ -0,0 +1,13 @@
+Copyright (c) 2013 Paul Morton, Shawn Neal
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/README.md

@@ -1,80 +1,77 @@
-Installing Vagrant-Windows
-==========================
+# Vagrant-Windows
+[![Build Status](https://travis-ci.org/WinRb/vagrant-windows.png)](https://travis-ci.org/WinRb/vagrant-windows)
+[![Code Climate](https://codeclimate.com/github/WinRb/vagrant-windows.png)](https://codeclimate.com/github/WinRb/vagrant-windows)
+[![Gem Version](https://badge.fury.io/rb/vagrant-windows.png)](http://badge.fury.io/rb/vagrant-windows)
 
-For Vagrant 1.1.x and 1.2.x execute `vagrant plugin install vagrant-windows`.
-For Vagrant 1.0.x execute `vagrant plugin install vagrant-windows --plugin-version 0.1.2`.
+Use Windows guests with Vagrant
 
-### Installing Vagrant-Windows From Source
-If you want to install from source, use the following method (this would be for 1.2.0):
+## Getting Started
+1. Install the vagrant-windows plugin.
+2. Create and configure a Windows guest base box.
+3. Create a Vagrantfile.
+4. vagrant up
 
-```
- bundle install
- bundle exec rake
- vagrant plugin install pkg/vagrant-windows-1.2.0.gem
-```
+## Installation
 
-Keep in mind you should have Ruby 1.9.3 and Ruby DevKit installed. Check out the following gist that can get you what you need (from blank system to fully ready): [Install Vagrant Windows Plugin From Source Gist](https://gist.github.com/ferventcoder/6251225).
+- For Vagrant 1.1 and above execute `vagrant plugin install vagrant-windows`.
+- For Vagrant 1.0 execute `vagrant plugin install vagrant-windows --plugin-version 0.1.2`.
 
-Supported Guest Operating Systems (Your VM)
-===========================================
-_Does NOT work with Windows 2003 or XP_
+## Creating a Base Box
 
+Supported Guest Operating Systems:
 - Windows 7
-- Windows 2008
-- Windows 2008 R2
-- Windows 2012
 - Windows 8
+- Windows Server 2008
+- Windows Server 2008 R2
+- Windows Server 2012
 
-Building a Base Box
-===================
-
-All Windows Machines
--------------------- 
-#### Prerequisites
+Windows Server 2003 and Windows XP are not supported by the maintainers of this project. Any issues regarding any unsupported guest OS will be closed. If you still insist on using XP or Server 2003, [this](http://stackoverflow.com/a/18593425/18475) may help.
 
-Box setup:
+You'll need to create a new Vagrant base box. Create a new Windows VM in VirtualBox, configure some Windows settings (see below) then follow the [Vagrant packaging instructions](http://docs.vagrantup.com/v2/cli/package.html).
 
   - Create a vagrant user, for things to work out of the box username and password should both be "vagrant".
   - Turn off UAC (Msconfig)
   - Disable complex passwords
+  - [Disable Shutdown Tracker](http://www.jppinto.com/2010/01/how-to-disable-the-shutdown-event-tracker-in-server-20032008/) on Windows 2008/2012 Servers (except Core).
+  - [Disable "Server Manager" Starting at login](http://www.elmajdal.net/win2k8/How_to_Turn_Off_The_Automatic_Display_of_Server_Manager_At_logon.aspx) on Windows 2008/2012 Servers (except Core).
+  - Enable and configure WinRM (see below)
 
-Prior to enabling WinRM, you must ensure the following services are enabled:
+### WinRM Configuration
 
-  - Base Filtering Engine
-    - Remote Procedure Call (RPC)
-      - DCOM Server Process Launcher
-      - RPC Endpoint Mapper
-  - Windows Firewall
-  - Windows Remote Management (WS-Management)
-
-#### Enable WinRM
+These commands assume you're running from a regular command window and not PowerShell.
 ```
    winrm quickconfig -q
    winrm set winrm/config/winrs @{MaxMemoryPerShellMB="512"}
    winrm set winrm/config @{MaxTimeoutms="1800000"}
    winrm set winrm/config/service @{AllowUnencrypted="true"}
    winrm set winrm/config/service/auth @{Basic="true"}
+   sc config WinRM start= auto
 ```
-* note
-If you want to run the winrm commands from PowerShell you need to put ```@{MaxMemoryPerShellMB="512"}``` etc in single quotes:
+
+#### Additional WinRM 1.1 Configuration
+
+These additional configuration steps are specific to Windows Server 2008 (WinRM 1.1). For Windows Server 2008 R2, Windows 7 and later versions of Windows you can ignore this section.
+
+1. Ensure the Windows PowerShell feature is installed
+2. [Change the default WinRM port](http://technet.microsoft.com/en-us/library/ff520073\(v=ws.10\).aspx) (see below) or [upgrade to WinRM 2.0](http://www.microsoft.com/en-us/download/details.aspx?id=20430).
 
 ```
-   winrm set winrm/config/winrs '@{MaxMemoryPerShellMB="512"}'
+netsh firewall add portopening TCP 5985 "Port 5985"
+winrm set winrm/config/listener?Address=*+Transport=HTTP @{Port="5985"}
 ```
 
-#### Last steps 
+### Required Windows Services
 
-  - Optional: Start WinRM a few minutes faster by running: "sc config WinRM start= auto" (default is delayed-auto)
-    - _Note:_ When you use the `winrm` command line tool it will always ask to set the startup to Delayed, so you may find yourself performing this a few times.
+If you like to turn off optional Windows services you'll need to ensure you leave these services enabled for vagrant-windows to continue to work:
 
+  - Base Filtering Engine
+  - Remote Procedure Call (RPC)
+  - DCOM Server Process Launcher
+  - RPC Endpoint Mapper
+  - Windows Firewall
+  - Windows Remote Management (WS-Management)
   
-Windows 2008/2012 Servers (except Core)
----------------------------------------
-  - [Disable Shutdown Tracker](http://www.jppinto.com/2010/01/how-to-disable-the-shutdown-event-tracker-in-server-20032008/)
-  - [Disable "Server Manager" Starting at login](http://www.elmajdal.net/win2k8/How_to_Turn_Off_The_Automatic_Display_of_Server_Manager_At_logon.aspx)
-  
-The Vagrant File
-================
+## The Vagrant File
 
 Add the following to your Vagrantfile
 
@@ -122,41 +119,39 @@ Available Config Parameters:
 * ```config.winrm.max_tries``` - The number of retries to connect to WinRM, defaults to 20.
 * ```config.winrm.timeout``` - The max number of seconds to wait for a WinRM response, defaults to 1800 seconds.
 
-Note - You need to ensure you specify a config.windows and a config.winrm in your Vagrantfile. Currently there's a problem where
-Vagrant will not load the plugin config even with defaults if at least one of its values doesn't exist in the Vagrantfile.
+Note - You need to ensure you specify a config.windows and a config.winrm in your Vagrantfile. Currently there's a problem where Vagrant will not load the plugin config even with defaults if at least one of its values doesn't exist in the Vagrantfile.
+
 
 
-What Works?
-===========
+------------------------------------------------------------
+
+## What Works?
+
 - vagrant up|halt|reload|provision
 - Chef Vagrant Provisioner
 - Puppet Vagrant Provisioner
 - Shell Vagrant provisioner. Batch files or PowerShell (ps1) scripts are supported as well as inline scripts.
 
-TODOs
-=========
-1. Test it! We need to test on more hosts, guests, and VBox versions. Help wanted.
-2. Chef-Client support.
-3. Unit tests. 
-4. Better docs.
 
-Troubleshooting
-===============
+## Troubleshooting
+
+#### When I run the winrm command I get: "Error: Invalid use of command line. Type "winrm -?" for help."
+- You're running the winrm command from powershell. You need to put ```@{MaxMemoryPerShellMB="512"}``` etc in single quotes:
+```
+   winrm set winrm/config/winrs '@{MaxMemoryPerShellMB="512"}'
+```
 
-I get a 401 auth error from WinRM
----------------------------------
+#### I get a 401 auth error from WinRM
 - Ensure you've followed the WinRM configuration instructions above.
 - Ensure you can manually login using the specified config.winrm.username you've specified in your Vagrantfile.
 - Ensure your password hasn't expired.
 - Ensure your password doesn't need to be changed because of policy.
 
-I get a non-401 error from WinRM waiting for the VM to boot
------------------------------------------------------------
+#### I get a non-401 error from WinRM waiting for the VM to boot
 - Ensure you've properly setup port forwarding of WinRM
 - Make sure your VM can boot manually through VBox.
 
-SQL Server cookbook fails to install through Vagrant
-----------------------------------------------------
+#### SQL Server cookbook fails to install through Vagrant
 - Ensure UAC is turned off
 - Ensure your vagrant user is an admin on the guest
 - The SQL Server installer uses a lot of resources, ensure WinRM Quota Management is properly configured to give it enough resources.
@@ -165,21 +160,17 @@ SQL Server cookbook fails to install through Vagrant
 If all else fails try running [vagrant with debug logging](http://docs.vagrantup.com/v2/debugging.html), perhaps that will give
 you enough insight to fix the problem or file an issue.
 
-What Can I do to help?
-======================
-1. Contribute Code (See Below)
-2. Test Various Scenarios and file bugs for things that dont work
 
-Contributing
-============
+## Contributing
+
 1. Fork it.
 2. Create a branch (git checkout -b my_feature_branch)
 3. Commit your changes (git commit -am "Added a sweet feature")
 4. Push to the branch (git push origin my_feature_branch)
 5. Create a pull requst from your branch into master (Please be sure to provide enough detail for us to cipher what this change is doing)
 
-Development
-=============
+### Development
+
 Clone this repository and use [Bundler](http://gembundler.com) to get the dependencies:
 
 ```
@@ -202,9 +193,20 @@ use bundler to execute Vagrant:
 $ bundle exec vagrant up
 ```
 
+### Installing Vagrant-Windows From Source
+
+If you want to globally install your locally built plugin from source, use the following method (this would be for 1.2.0):
+
+```
+ bundle install
+ bundle exec rake build
+ vagrant plugin install pkg/vagrant-windows-1.2.0.gem
+```
+
+Keep in mind you should have Ruby 1.9.3 and Ruby DevKit installed. Check out the following gist that can get you what you need (from blank system to fully ready): [Install Vagrant Windows Plugin From Source Gist](https://gist.github.com/ferventcoder/6251225).
+
+## References and Shout Outs
 
-References and Shout Outs
-=========================
 - Chris McClimans - Vagrant Branch (https://github.com/hh/vagrant/blob/feature/winrm/)
 - Dan Wanek - WinRM GEM (https://github.com/zenchild/WinRM)
   - +1 For being super responsive to pull requests.
@@ -215,38 +217,4 @@ References and Shout Outs
 - Rob Reynolds - Updated readme installation and box configuration notes
 - stonith - Updated readme winrm config notes
 - wenns - Updated readme to advise against forwarding RDP
-
-Changelog
-=========
-0.1.1
-
-- Remove extra debug information from command output.
-
-0.1.2
-
-- Added virtual box 4.2 support.
-
-0.1.3 
-
-- Added puppet provisioner.
-
-1.0.0 
-
-- Converted to Vagrant 1.1.x plugin architecture.
-
-1.0.1 
-
-- Fix #29 Monkey Patch the 4.2 driver to include read_mac_addresses. 
-  - use read_mac_addresses in all cases.
-
-1.0.3 
-
-- Added vagrant shell provisioner. The built-in shell provisioner tried to chmod the target script which doesn't make sense on windows.
-- Can now run the vagrant-windows plugin via bundle exec instead of vagrant plugin install (for plugin dev).The vagrant src root finding logic didn't work from a bundle, but the native Vagrant src root does.
-- Readme fixes/updates.
-
-1.2.0
-
-- Converted to Vagrant 1.2.x plugin architecture.
-- Various networking fixes.
-- Chef provisioner runs through the Windows task scheduler instead of ps_runas power shell script.
+- Joe Fitzgerald - Added VMWare support and improved retry logic.

data/coverage/.last_run.json

@@ -1,5 +1,5 @@
 {
   "result": {
-    "covered_percent": 65.11
+    "covered_percent": 57.79
   }
 }