knife-winops 2.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 648376fc535d37911fdea961d4f4758a81ddf710
+  data.tar.gz: a32ca4bc1c8d4e5b6a270aeee69ab6ce984e7339
+SHA512:
+  metadata.gz: 706a95e9b891e3a4a106ba5ff3c679911401f64910908fb73de9675acb57a8e2c458cbcb3436b9916bb72b1360affb812f17d0b631af946ee5edcb68a2c6536c
+  data.tar.gz: 2dcd08392c81b238dc788ef989bb0c87d8205e3bed182448f88eedacb93305a5481cf09d044024ed4b398e1174e37bc35cfd2169d9a6b471ecf6b10aff75d029

data/.gitignore

@@ -0,0 +1,5 @@
+*.gem
+.bundle
+Gemfile.lock
+ci.gemfile.lock
+pkg/*

data/.rspec

@@ -0,0 +1,3 @@
+--color
+-fdocumentation
+

data/.travis.yml

@@ -0,0 +1,30 @@
+language: ruby
+cache: bundler
+dist: trusty
+sudo: false
+
+rvm:
+  - 2.2.7
+  - 2.3.4
+  - 2.4.1
+  - ruby-head
+
+before_install:
+  - gem install bundler
+
+gemfile: ci.gemfile
+
+env:
+  - CHEF_VERSION="master"
+  - CHEF_VERSION="~> 12.0"
+
+matrix:
+  exclude:
+  - rvm: 2.2.7
+    env: CHEF_VERSION="master"
+  allow_failures:
+    - rvm: ruby-head
+
+branches:
+  only:
+  - master

data/CHANGELOG.md

@@ -0,0 +1,147 @@
+# knife-winops Change Log
+
+## Release 1.9.0
+
+* [knife-winops #416](https://github.com/chef/knife-winops/pull/416) Add concurrency support via the `--concurrency` flag
+
+## Release 1.8.0
+
+* [knife-winops #407](https://github.com/chef/knife-winops/pull/407) Added value for config_log_level and config_log_location
+
+## Release 1.7.1
+
+* [knife-winops #409](https://github.com/chef/knife-winops/pull/409) Fix trusted_cert copy script generation on windows
+
+## Release 1.7.0
+
+* [knife-winops #400](https://github.com/chef/knife-winops/pull/400) Allow a custom codepage to be specified and passed to the cmd shell
+
+## Release 1.6.0
+
+* [knife-winops #393](https://github.com/chef/knife-winops/pull/393) Add documentation of the --msi-url option
+* [knife-winops #392](https://github.com/chef/knife-winops/pull/392) Use winrm v2 and allow users to pass a shell
+* [knife-winops #388](https://github.com/chef/knife-winops/pull/388) fix #386 swallowing node_ssl_verify_mode value
+* [knife-winops #385](https://github.com/chef/knife-winops/pull/385) Fixed win 2008 64bit ssh bootstrap command hanging
+* [knife-winops #384](https://github.com/chef/knife-winops/pull/384) Fix for architechture detection issue for 64 bit
+* [knife-winops #381](https://github.com/chef/knife-winops/pull/381) Add validation for FQDN value
+* [knife-winops #380](https://github.com/chef/knife-winops/pull/380) Fixing bootstrap via ssh regression
+
+## Release 1.5.0
+
+* [knife-winops #377](https://github.com/chef/knife-winops/pull/377) Added code and corresponding RSpecs to read the json attributes from the --json-attributes-file option.
+
+## Release 1.4.1
+
+* [knife-winops #362](https://github.com/chef/knife-winops/pull/362) Fix `knife windows bootstrap` chef client downloads over a proxy
+* [knife-winops #367](https://github.com/chef/knife-winops/pull/367) Honor chef's ssl_policy when making winrm calls
+
+## Release 1.4.0
+
+* [knife-winops #354](https://github.com/chef/knife-winops/pull/354) Allows the user to specify the architecture they want to install on the target system during `knife bootstrap windows`.  In your knife config specify `knife[:bootstrap_architecture]`.  Valid values are `:i386` for 32 bit or `:x86_64` for 64 bit.  By default the architecture will be whatever the target system is.  If you try to install a 64 bit package on a 32 bit system you will receive an error.
+* [knife-winops #352](https://github.com/chef/knife-winops/pull/352) Have client.rb verify that FIPS mode can be enforced
+
+## Release 1.3.0
+* [knife-winops #349](https://github.com/chef/knife-winops/pull/349) Pulls in Winrm 1.7.0 which now consumes rubyntlm 0.6.0 to support Extended Protection for Authentication (aka channel binding) for NTLM over TLS
+* [knife-winops #350](https://github.com/chef/knife-winops/pull/350) Adding a `--ssl-peer-fingerprint` option as an alternative to `--winrm-ssl-verify-mode verify_none` in self signed scenarios
+
+## Release 1.2.1
+* [knife-winops #341](https://github.com/chef/knife-winops/pull/341) Removes nokogiri dependency and adds UX fixes for `knife wsman test` when probing a SSL endpoint configured with a self signed certificate
+
+## Release 1.2.0
+* [knife-winops #334](https://github.com/chef/knife-winops/pull/334) Uses Negotiate authentication via winrm 1.6 on both windows and linux and drops winrm-s dependency
+
+## Release 1.1.4
+* Bumps winrm-s and winrm dependencies to address a winrm-s incompatibility bug with winrm 1.5
+
+## Release 1.1.3
+* [knife-winops #329](https://github.com/chef/knife-winops/pull/329) Pin to a minimum winrm-s of 0.3.2 addressing encoding issues in 0.3.1
+
+## Release 1.1.2
+* [knife-winops #317](https://github.com/chef/knife-winops/pull/317) Update Vault after client is created
+* [knife-winops #325](https://github.com/chef/knife-winops/pull/325) Fix proxy configuration to work with chef client 12.6.0
+* [knife-winops #326](https://github.com/chef/knife-winops/pull/326) Support new `ssh_identity_file` bootstrap argument
+
+## Release 1.1.1
+* [knife-winops #307](https://github.com/chef/knife-winops/pull/307) Ensure prompted password is passed to winrm session
+* [knife-winops #311](https://github.com/chef/knife-winops/issues/311) WinRM bootstrap silently fails
+
+## Release 1.1.0
+* [knife-winops #302](https://github.com/chef/knife-winops/pull/302) Address regression caused by chef client 12.5 environment argument
+* [knife-winops #295](https://github.com/chef/knife-winops/issues/295) Bootstrap missing policy_group, policy_name feature from Chef Client 12.5
+* [knife-winops #296](https://github.com/chef/knife-winops/issues/296) Installing knife-winops produces warning for _all_ knife commands in Mac OS X with ChefDK 0.8.0
+* [knife-winops #297](https://github.com/chef/knife-winops/pull/297) use configured proxy settings for all winrm sessions
+
+## Release 1.0.0
+
+* [knife-winops #281](https://github.com/chef/knife-winops/pull/281) Prevent unencrypted negotiate auth, automatically prefix local usernames with '.' for negotiate
+* [knife-winops #275](https://github.com/chef/knife-winops/pull/275) Added bootstrap\_install\_command option in parity with knife bootstrap
+* [knife-winops #240](https://github.com/chef/knife-winops/pull/240) Change kerberos keytab short option to -T to resolve conflict
+* [knife-winops #232](https://github.com/chef/knife-winops/pull/232) Adding --hint option to bootstrap
+* [knife-winops #227](https://github.com/chef/knife-winops/issues/227) Exception: NoMethodError: undefined method 'gsub' for false:FalseClass
+* [knife-winops #222](https://github.com/chef/knife-winops/issues/222) Validatorless bootstrap support
+* [knife-winops #202](https://github.com/chef/knife-winops/issues/202) knife bootstrap windows should support enabling the service
+* [knife-winops #213](https://github.com/chef/knife-winops/pull/213) Search possibilities of HOME for bootstrap templates
+* [knife-winops #206](https://github.com/chef/knife-winops/pull/206) Add a flag msi_url that allows one to fetch the Chef client msi from a non-chef.io path
+* [knife-winops #192](https://github.com/chef/knife-winops/issues/192) deprecate knife bootstrap --distro
+* [knife-winops #159](https://github.com/opscode/knife-winops/issues/159) `winrm_port` option should default to 5986 if `winrm_transport` option is `ssl`
+* [knife-winops #149](https://github.com/chef/knife-winops/pull/149) Adding knife wsman test to validate WSMAN/WinRM availability
+* [knife-winops #139](https://github.com/opscode/knife-winops/issues/139) Force dev dependency on Chef 11 for test scenarios to avoid Ohai 8 conflict on Ruby 1.9.x
+* [knife-winops #126](https://github.com/opscode/knife-winops/pull/126) Allow disabling of SSL peer verification in knife-winops for testing
+* [knife-winops #154](https://github.com/opscode/knife-winops/issues/154) Unreleased regression in master: NameError: undefined local variable or method `path_separator
+* [knife-winops #143](https://github.com/opscode/knife-winops/issues/143) Unreleased regression in master: WinRM::WinRMHTTPTransportError: Bad HTTP response returned from server (503) in the middle of bootstrap
+* [knife-winops #133](https://github.com/opscode/knife-winops/issues/133) Bootstrap failure -- unable to validate SSL chef server endpoints
+* [knife-winops #132](https://github.com/opscode/knife-winops/issues/132) New subcommands for WinRM: windows listener create, cert generate, and cert install
+* [knife-winops #129](https://github.com/opscode/knife-winops/issues/129) New --winrm-authentication-protocol option for explicit control of authentication
+* [knife-winops #125](https://github.com/opscode/knife-winops/issues/125) knife-winops should use PowerShell first before cscript to download the  Chef Client msi
+* [knife-winops #92](https://github.com/opscode/knife-winops/issues/92) EventMachine issue: knife bootstrap windows winrm error
+* [knife-winops #94](https://github.com/opscode/knife-winops/issues/94) Remove Eventmachine dependency
+* [knife-winops #252](https://github.com/chef/knife-winops/pull/252) Fail early on ECONNREFUSED, Closes #244.
+* [knife-winops #260](https://github.com/chef/knife-winops/pull/260) Fail quickly on invalid option combinations, Closes #259
+
+## Release: 0.8.5
+* [knife-winops #228](https://github.com/chef/knife-winops/pull/228) make winrm-s dep more strict on knife-winops 0.8.x
+
+## Release: 0.8.4
+* [knife-winops #133](https://github.com/opscode/knife-winops/issues/133) Bootstrap failure -- unable to validate SSL chef server endpoints
+
+## Release: 0.8.3
+* [knife-winops #131](https://github.com/opscode/knife-winops/issues/108) Issue #131: Windows should be bootstrapped using latest Chef Client version compatible with knife's version just like non-Windows systems
+* [knife-winops #139](https://github.com/opscode/knife-winops/issues/139) Force dev dependency on Chef 11 for test scenarios to avoid Ohai 8 conflict on Ruby 1.9.x
+
+## Release: 0.8.2
+* [knife-winops #108](https://github.com/opscode/knife-winops/issues/108) Error: Unencrypted communication not supported if remote server does not require encryption
+
+## Release: 0.8.0
+* [knife-winops #98](https://github.com/opscode/knife-winops/issues/98) Get winrm command exit code if it is not expected
+* [knife-winops #96](https://github.com/opscode/knife-winops/issues/96) Fix break from OS patch KB2918614
+* Remove the 'instance data' method of creating EC2 servers
+* Update winrm-s dependency along with em-winrm and winrm dependencies
+* Return failure codes from knife winrm even when `returns` is not set
+* Support Windows negotiate authentication protocol when running knife on Windows
+
+## Release: 0.6.0 (05/08/2014)
+
+* [KNIFE-386](https://tickets.opscode.com/browse/KNIFE-386) Wait for a valid command response before bootstrapping over WinRM
+* [KNIFE-394](https://tickets.opscode.com/browse/KNIFE-394) Update em-winrm dependency
+* [KNIFE-450](https://tickets.opscode.com/browse/KNIFE-450) Set knife winrm command exit status on exception and command failure
+
+**See source control commit history for earlier changes.**
+
+## Selected release notes
+These are release notes from very early releases of the plugin. For recent
+releases (2014 and later), see the RELEASE_NOTES.md file of each tagged release branch.
+
+Release Notes - Knife Windows Plugin - Version 0.5.6
+
+** New Feature
+    * new default bootstrap template that installs Chef using official chef-client MSI installer
+
+Release Notes - Knife Windows Plugin - Version 0.5.4
+
+** Bug
+    * [KNIFE\_WINDOWS-7] - Exception: NoMethodError: undefined method `env_namespace' for Savon:Module
+    * [KNIFE\_WINDOWS-8] - winrm based bootstrap fails with 'Bad HTTP response returned from server (500)'
+
+
+** New Feature
+    * [KNIFE\_WINDOWS-6] - default bootstrap template should support encrypted\_data\_bag\_secret

data/DOC_CHANGES.md

@@ -0,0 +1,22 @@
+<!---
+This file is reset every time a new release is done. This file describes changes that have not yet been released.
+
+Example Doc Change:
+### Headline for the required change
+Description of the required change.
+-->
+# knife-winops 1.6.0 doc changes
+
+### Choosing a winrm shell
+
+<!---
+This file is reset every time a new release is done. The contents of this file are for the currently unreleased version.
+
+Example Note:
+
+## Example Heading
+Details about the thing that changed that needs to get included in the Release Notes in markdown.
+-->
+# knife-winops 1.6.0 release notes:
+
+This release adds a `--winrm-shell` argument to `knife winrm`. This accepts one of three possible values: `cmd`, `powershell` or `elevated`. The default value is `cmd`. The `elevated` shell is similar to the `powershell` shell but runs the powershell command from a scheduled task.

data/Gemfile

@@ -0,0 +1,13 @@
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in knife-winops.gemspec
+gemspec
+
+gem 'rb-readline'
+group :test do
+  gem "chef"
+  gem "rspec", '~> 3.0'
+  gem "ruby-wmi"
+  gem "httpclient"
+  gem 'rake'
+end

data/LICENSE

@@ -0,0 +1,201 @@
+                              Apache License
+                        Version 2.0, January 2004
+                     http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don't include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+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

@@ -0,0 +1,430 @@
+Knife Windows Plugin
+====================
+[![Build Status Master](https://travis-ci.org/chef/knife-winops.svg?branch=master)](https://travis-ci.org/chef/knife-winops)
+[![Build Status Master](https://ci.appveyor.com/api/projects/status/github/chef/knife-winops?branch=master&svg=true&passingText=master%20-%20Ok&pendingText=master%20-%20Pending&failingText=master%20-%20Failing)](https://ci.appveyor.com/project/Chef/knife-winops/branch/master)
+[![Gem Version](https://badge.fury.io/rb/knife-winops.svg)](https://badge.fury.io/rb/knife-winops)
+
+This plugin adds additional functionality to the Chef Knife CLI tool for
+configuring / interacting with nodes running Microsoft Windows:
+
+* Bootstrap of nodes via the [Windows Remote Management (WinRM)](http://msdn.microsoft.com/en-us/library/aa384426\(v=VS.85\).aspx) or SSH protocols
+* Remote command execution using the WinRM protocol
+* Utilities to configure WinRM SSL endpoints on managed nodes
+
+## Subcommands
+
+This plugin provides the following Knife subcommands. Specific command options can be found by invoking the subcommand with a `--help` flag
+
+### knife winrm
+
+The `winrm` subcommand allows you to invoke commands in parallel on a subset of the nodes in your infrastructure. The `winrm` subcommand uses the same syntax as the [search subcommand](https://docs.chef.io/knife_search.html); you could find the uptime of all your web servers using the command:
+
+    knife winrm "role:web" "net stats srv" -x Administrator -P 'super_secret_password'
+
+_Please note that to run a single command against multiple nodes, each node must share the same username and password._
+
+Or force a chef run:
+
+    knife winrm "myserver.myorganization.net" "chef-client -c c:/chef/client.rb" -m -x Administrator -P "super_secret_password"
+    myserver.myorganization.net [Fri, 04 Mar 2011 22:00:49 +0000] INFO: Starting Chef Run (Version 0.9.12)
+    myserver.myorganization.net [Fri, 04 Mar 2011 22:00:50 +0000] WARN: Node ip-0A502FFB has an empty run list.
+    myserver.myorganization.net [Fri, 04 Mar 2011 22:00:53 +0000] INFO: Chef Run complete in 4.383966 seconds
+    myserver.myorganization.net [Fri, 04 Mar 2011 22:00:53 +0000] INFO: cleaning the checksum cache
+    myserver.myorganization.net [Fri, 04 Mar 2011 22:00:53 +0000] INFO: Running report handlers
+    myserver.myorganization.net [Fri, 04 Mar 2011 22:00:53 +0000] INFO: Report handlers complete
+
+This subcommand operates in a manner similar to [knife ssh](https://docs.chef.io/knife_ssh.html)...just leveraging the WinRM protocol for communication. It also includes `knife ssh`'s "[interactive session mode](https://docs.chef.io/knife_ssh.html#options)"
+
+#### winrm-shell
+
+By default, `knife winrm` runs in a `cmd.exe` shell. You can use the `--winrm-shell` argument to change the shell to `powershell` or `elevated`. An elevated shell is similar to the `powershell` shell but the powershell command is executed from a scheduled task using a local identity. This may be desirable for some operations such as running `chef-client` to converge recipes that work with windows updates, install sql server, etc.
+
+### knife bootstrap windows winrm
+
+Performs a Chef Bootstrap (via the WinRM protocol) on the target node. The goal of the bootstrap is to get Chef installed on the target system so it can run Chef Client with a Chef Server. The main assumption is a baseline OS installation exists. It is primarily intended for Chef Client systems that talk to a Chef server.
+
+This subcommand operates in a manner similar to [knife bootstrap](https://docs.chef.io/knife_bootstrap.html)...just leveraging the WinRM protocol for communication. An initial run_list for the node can also be passed to the subcommand. Example usage:
+
+    knife bootstrap windows winrm myserver.myorganization.net -r 'role[webserver],role[production]' -x Administrator -P 'super_secret_password'
+
+#### Tip: Use SSL for WinRM communication
+
+By default, the `knife winrm` and `knife bootstrap windows winrm` subcommands use a plaintext transport,
+but they support an option `--winrm-transport` (or `-t`) with the argument
+`ssl` that allows the SSL to secure the WinRM payload. Here's an example:
+
+    knife winrm -t ssl "role:web" "net stats srv" -x Administrator -P "super_secret_password" -f ~/server_public_cert.crt
+
+Use of SSL is strongly recommended, particularly when invoking `knife-winops` on non-Windows platforms, since
+without SSL there are limited options for ensuring the privacy of the
+plaintext transport. See the section on [Platform authentication
+support](#platform-winrm-authentication-support).
+
+SSL will become the default transport in future revisions of
+`knife-winops`.
+
+#### Specifying the package architecture
+
+You can configure which package architecture (32 bit or 64 bit) to install on the bootstrapped system.  In your knife config specify `knife[:bootstrap_architecture]`.  Valid values are `:i386` for 32 bit or `:x86_64` for 64 bit.  By default the architecture will be whatever the target system is.  If you try to install a 64 bit package on a 32 bit system you will receive an error, but installing a 32 bit package on a 64 bit system is supported.
+
+Currently (March 2016) the `stable` channel of omnibus (where downloads using the install script fetch) only has 32 bit packages but this will be updated soon to include both 32 and 64 bit packages.  Until then you will need to access the `current` channel by specifying `--prerelease` in your `knife bootstrap windows` if you want 64 bit packages.
+
+#### Using a custom install URL
+
+By default, the bootstrap command tries to download the latest `chef-client` installer from the Internet.  This may be a problem in the enterprise, for example if your node is behind a proxy or firewall.  In that case, you can specify a custom install URL with the `--msi-url` option.
+
+### knife wsman test
+
+Connects to the remote WSMan/WinRM endpoint and verifies the remote node is listening.  This is the equivalent of running Test-Wsman from PowerShell.  Endpoints to test can be specified manually, or be driven by search and use many of the same connection options as knife winrm.
+To test a single node using the default WinRM port (5985)
+
+    knife wsman test 192.168.1.10 -m
+
+or to test a single node with SSL enabled on the default port (5986)
+
+    knife wsman test 192.168.1.10 -m --winrm-transport ssl
+
+or to test all windows nodes registered with your Chef Server organization
+
+    knife wsman test platform:windows
+
+### knife bootstrap windows ssh
+
+Performs a Chef Bootstrap (via the SSH protocol) on the target node. The goal of the bootstrap is to get Chef installed on the target system so it can run Chef Client with a Chef Server. The main assumption is a baseline OS installation exists. It is primarily intended for Chef Client systems that talk to a Chef server.
+
+This subcommand assumes the SSH session will use the Windows native cmd.exe command shell vs a bash shell through an emulated cygwin layer. Most popular Windows based SSHd daemons like [freeSSHd](http://www.freesshd.com/) and [WinSSHD](http://www.bitvise.com/winsshd) behave this way.
+
+An initial run_list for the node can also be passed to the subcommand. Example usage:
+
+    knife bootstrap windows ssh myserver.myorganization.net -r "role[webserver],role[production]" -x Administrator -i ~/.ssh/id_rsa
+
+### knife windows cert generate
+
+Generates a certificate(x509) containing a public / private key pair for WinRM 'SSL' communication.
+The certificate will be generated in three different formats:
+* **.pem** - The *.pem is Base64 encoded public certificate only. One can use this file with the `-f` argument on `knife bootstrap windows winrm` and `knife winrm` commands.
+* **.pfx** - The PKCS12(i.e .pfx) contains both the public and private keys, usually used on the server. This can be added to a WinRM Server's Certificate Store using `knife windows cert install` (see command description below). **Note:** Do not use the *.pfx file with the `-f` argument on the `knife bootstrap windows winrm` and `knife winrm` commands. Use the *.pem file instead.
+* **.b64** - The *.b64 is Base64 PKCS12 key pair. Contains both the public and private keys, for upload to the Cloud REST API. e.g. Azure.
+
+This command also displays the thumbprint of the generated certificate.
+
+    knife windows cert generate --cert-passphrase "strong_passphrase" --hostname "myserver.myorganization.net" --output-file "~/server_cert.pfx"
+    # This command will generate certificates in the user's home directory with names server_cert.b64, server_cert.pfx and server_cert.pem.
+
+### knife windows cert install
+
+This command only functions on Windows and is intended to be run on a chef node. It adds the specified certificate to its certificate store. This command must include a valid PKCS12(i.e *.pfx) certificate file path such as the *.pfx file generated by `knife windows cert generate` described above.
+
+    knife windows cert install "~/server_cert.pfx" --cert-passphrase "strong_passphrase"
+
+### knife windows listener create
+This command only functions on Windows and is intended to be run on a chef node. It creates the winrm listener for SSL communication(i.e HTTPS).
+This command can also install certificate which is specified using --cert-install option and use the installed certificate thumbprint to create winrm listener.
+--hostname option is optional. Default value for hostname is *.
+
+    knife windows listener create --cert-passphrase "strong_passphrase" --hostname "myserver.mydomain.net" --cert-install "~/server_cert.pfx"
+
+The command also allows you to use existing certificates from local store to create winrm listener. Use --cert-thumbprint option to specify the certificate thumbprint.
+
+    knife windows listener create --cert-passphrase "strong_passphrase" --hostname "myserver.mydomain.net" --cert-thumbprint "bf0fef0bb41be40ceb66a3b38813ca489fe99746"
+
+You can get the thumbprint for existing certificates in the local store using the following PowerShell command:
+
+    ls cert:\LocalMachine\My
+
+## Bootstrap template
+
+This gem provides the bootstrap template `windows-chef-client-msi`,
+which does the following:
+
+* Installs the latest version of Chef Client (and all dependencies) using the `chef-client` msi.
+* Writes the validation.pem per the local knife configuration.
+* Writes a default config file for Chef (`C:\chef\client.rb`) using values from the `knife.rb`.
+* Creates a JSON attributes file containing the specified run list and run Chef.
+
+This template is used by both `knife bootstrap windows winrm` and `knife bootstrap windows ssh` subcommands.
+
+## Requirements / setup
+
+### Ruby
+
+Ruby 1.9.3+ is required.
+
+### Chef version
+
+This knife plugins requires >= Chef 11.0.0. More details about Knife plugins can be
+[found in the Chef documentation](https://docs.chef.io/plugin_knife.html).
+
+## Nodes
+
+### WinRM versions
+
+The node must be running Windows Remote Management (WinRM) 2.0+. WinRM
+allows you to call native objects in Windows. This includes, but is not
+limited to, running PowerShell scripts, batch scripts, and fetching WMI
+data. For more information on WinRM, please visit
+[Microsoft's WinRM site](http://msdn.microsoft.com/en-us/library/aa384426\(v=VS.85\).aspx).
+
+WinRM is built into Windows 7 and Windows Server 2008+. It can also [be installed](https://support.microsoft.com/en-us/kb/968929) on older version of Windows, including:
+
+* Windows Server 2003
+* Windows Vista
+
+### WinRM configuration
+
+**NOTE**: Before any WinRM related knife subcommands will function
+  a node's WinRM installation must be configured correctly.
+  The settings below must be added to your base server image or passed
+  in using some sort of user-data mechanism provided by your cloud
+  provider. Some cloud providers will set up the required WinRM
+  configuration through the cloud API for creating instances -- see
+  the documentation for the provider.
+
+A server running WinRM must also be configured properly to allow
+outside connections for the entire network path from the knife workstation to the server. The easiest way to accomplish this is to use [WinRM's quick configuration option](http://msdn.microsoft.com/en-us/library/aa384372\(v=vs.85\).aspx#quick_default_configuration):
+
+    winrm quickconfig -q
+
+This will set up an WinRM listener using the HTTP (plaintext)
+transport -- WinRM also supports the SSL transport for improved
+robustness against information disclosure and other threats.
+
+The chef-client installation and bootstrap may take more
+memory than the default 150MB WinRM allocates per shell on older versions of
+Windows (prior to Windows Server 2012) -- this can slow down
+bootstrap or cause it to fail. The memory limit was increased to 1GB with Windows Management Framework 3
+(and Server 2012). However, there is a bug in Windows Management Framework 3
+(and Server 2012) which requires a [hotfix from Microsoft](https://support.microsoft.com/en-us/kb/2842230/en-us).
+You can increase the memory limit to 1GB with the following PowerShell
+command:
+
+```powershell
+    set-item wsman:\localhost\shell\maxmemorypershellmb 1024
+```
+
+Bootstrap commands can take longer than the WinRM default 60 seconds to
+complete, optionally increase to 30 minutes if bootstrap terminates a command prematurely:
+
+```powershell
+    set-item wsman:\localhost\MaxTimeoutms 300000
+```
+
+Note that the `winrm` command itself supports the same configuration
+capabilities as the PowerShell commands given above -- if you need to
+configure WinRM without using PowerShell, use `winrm -?` to get help.
+
+WinRM supports both the HTTP and HTTPS (SSL) transports and the following
+authentication schemes: Kerberos, Digest, Certificate and Basic. The details
+of these authentication transports are outside of the scope of this
+README but details can be found on the
+[WinRM configuration guide](http://msdn.microsoft.com/en-us/library/aa384372\(v=vs.85\).aspx).
+
+### Working with legacy Windows versions
+
+If you are attempting to use `knife winrm` or `knife bootstrap windows winrm` with a version of windows that is older than server 2008 R2 or older than Windows 7 then you may need to alter the default UTF-8 codepage (65001) using the `--winrm-codepage` argument. You can use the codepage native to your locale but `437` is a safe codepage for older Windows versions.
+
+#### Configure SSL on a Windows node
+
+WinRM supports use of SSL to provide privacy and integrity of
+communication using the protocol and to prevent spoofing attacks.
+
+##### Configure SSL using `knife`
+
+`knife-winops` includes three commands to assist with SSL
+configuration -- these commands support all versions of Windows and do
+not rely on PowerShell:
+
+* `knife windows cert generate`: creates a certificate that may be used
+  to configure an SSL WinRM listener
+
+* `knife windows cert install`: Installs a certificate into the
+  Windows certificate store so it can be used to configure an SSL
+  WinRM listener.
+
+* `knife windows listener create`: Creates a WinRM listener on a
+  Windows node -- it can use either a certificate already installed in
+  the Windows certificate store, or one created by other tools
+  including the `knife windows cert generate` command.
+
+Here is an example that configures a listener on the node on which the
+commands are executed:
+
+    knife windows cert generate --domain myorg.org --output-file $env:userprofile/winrmcerts/winrm-ssl
+    knife windows listener create --hostname *.myorg.org --cert-install $env:userprofile/winrmcerts/winrm-ssl.pfx
+
+Note that the first command which generates the certificate for the
+listener could be executed from any system that can run `knife` as
+long as the certificate it generates is made available at a path at
+which the second command can access it.
+
+See previous sections for additional details of the `windows cert generate`, `windows cert install` and `windows listener create` subcommands.
+
+##### Configure SSL using *Windows Server 2012 or later*
+The following PowerShell commands may be used to create an SSL WinRM
+listener with a self-signed certificate on Windows 2012R2 or later systems:
+
+```powershell
+$cert = New-SelfSignedCertificate -DnsName 'myserver.mydomain.org' -CertStoreLocation Cert:\LocalMachine\My
+new-item -address * -force -path wsman:\localhost\listener -port 5986 -hostname ($cert.subject -split '=')[1] -transport https -certificatethumbprint $cert.Thumbprint
+# Open the firewall for 5986, the default WinRM SSL port
+netsh advfirewall firewall set rule name="Windows Remote Management (HTTPS-In)" profile=public protocol=tcp localport=5986 remoteip=localsubnet new remoteip=any
+
+```
+
+Note that the first command which uses the `New-SelfSignedCertificate`
+cmdlet is available only in PowerShell version 4.0 and later.
+
+##### Configure SSL using `winrm quickconfig`
+
+The following command can configure an SSL WinRM listener if the
+Windows certificate store's Local Machine store contains a certificate
+that meets certain criteria that are most likely to be met if the
+system is joined to a Windows Active Directory domain:
+
+    winrm quickconfig -transport:https -q
+
+If the criteria are not met, an error message will follow with
+guidance on the certificate requirements; you may need to obtain a
+certificate from the appropriate source or use the PowerShell or
+`knife` techniques given above to create the listener instead.
+
+##### Disabling peer verification
+In the SSL examples above, the `-f` parameter was used to supply a
+certificate that could validate the identity of the remote server.
+For debugging purposes, this validation may be skipped if you have not
+obtained a public certificate that can validate the server. Here is an
+example:
+
+    knife winrm -m 192.168.0.6 -x "mydomain\myuser" -P $PASSWD -t ssl --winrm-ssl-verify-mode verify_none ipconfig
+
+This option should be used carefully since disabling the verification of the
+remote system's certificate can subject knife commands to spoofing attacks.
+
+##### Connecting securely to self-signed certs
+If you generate a self-signed cert, the fqdn and ip may not match which will result in a certificate validation failure. In order to securely connect and reduce the risk of a "Man In The Middle" attack, you may use the certificate's fingerprint to precisely identify the known certificate on the WinRM endpoint.
+
+The fingerprint can be supplied to ```--ssl-peer-fingerprint``` and instead of using a certificate chain and comparing the CommonName, it will only verify that the fingerprint matches:
+
+    knife winrm --ssl-peer-fingerprint 89255929FB4B5E1BFABF7E7F01AFAFC5E7003C3F \
+		      -m $IP -x Administrator -P $PASSWD-t ssl --winrm-port 5986 hostname
+		10.113.4.54 ip-0A710436
+
+## WinRM authentication
+
+The default authentication protocol for `knife-winops` subcommands that use
+WinRM is the Negotiate protocol. The following commands show authentication for domain and local accounts respectively:
+
+    knife bootstrap windows winrm web1.cloudapp.net -r "server::web" -x "proddomain\webuser" -P "super_secret_password"
+    knife bootstrap windows winrm db1.cloudapp.net -r "server::db" -x "localadmin" -P "super_secret_password"
+
+The remote system may also be configured with an SSL WinRM listener instead of a
+plaintext listener. Then the above commands should be modified to use the SSL
+transport as follows using the `-t` (or `--winrm-transport`) option with the
+`ssl` argument:
+
+    knife bootstrap windows winrm -t ssl web1.cloudapp.net -r "server::web" -x "proddomain\webuser" -P "super_secret_password" -f ~/mycert.crt
+    knife bootstrap windows winrm -t ssl db1.cloudapp.net -r "server::db" -x "localadmin" -P "super_secret_password" ~/mycert.crt
+
+### Troubleshooting authentication
+
+Unencrypted traffic with Basic authentication should only be used for low level wire protocol debugging. The configuration for plain text connectivity to
+the remote system may be accomplished with the following PowerShell commands:
+
+```powershell
+set-item wsman:\localhost\service\allowunencrypted $true
+set-item wsman:\localhost\service\auth\basic $true
+```
+To use basic authentication connectivity via `knife-winops`, the default
+authentication protocol of Negotiate must be overridden using the
+`--winrm-authentication-protocol` option with the desired protocol, in this
+case Basic:
+
+    knife winrm -m web1.cloudapp.net --winrm-authentication-protocol basic ipconfig -x localadmin -P "super_secret_password"
+
+Note that when using Basic authentication, domain accounts may not be used for
+authentication; an account local to the remote system must be used.
+
+### Platform WinRM authentication support
+
+`knife-winops` supports `Kerberos`, `Negotiate`, and `Basic` authentication
+for WinRM communication.
+
+The following table shows the authentication protocols that can be used with
+`knife-winops` depending on whether the knife workstation is a Windows
+system, the transport, and whether or not the target user is a domain user or
+local to the target Windows system.
+
+> \* There is a known defect in the `knife winrm` and `knife bootstrap windows
+> winrm` subcommands invoked on any OS  platform when authenticating with the Negotiate protocol over
+> the SSL transport. The defect is tracked by
+> [knife-winops issue #176](https://github.com/chef/knife-winops/issues/176): If the remote system is
+> domain-joined, local accounts may not be used to authenticate via Negotiate
+> over SSL -- only domain accounts will work. Local accounts will only
+> successfully authenticate if the system is not joined to a domain.
+>
+> This is generally not an issue for bootstrap scenarios, where the
+> system has yet to be joined to any domain, but can be a problem for remote
+> management cases after the system is domain joined. Workarounds include using
+> a domain account instead or bypassing SSL and using Negotiate authentication.
+
+## General troubleshooting
+
+* Windows 2008R2 and earlier versions require an extra configuration
+  for MaxTimeoutms to avoid WinRM::WinRMHTTPTransportError: Bad HTTP
+  response error while bootstrapping. It should be at least 300000.
+
+  `set-item wsman:\\localhost\\MaxTimeoutms 300000`
+
+* 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 and you need to put the key/value pair in single quotes. For example:
+
+   `winrm set winrm/config/winrs '@{MaxMemoryPerShellMB="1024"}'`
+
+* If you receive a timeout when trying to connect to your instance for the first time, make sure your Firewall setting
+  is permissive enough.
+
+   `netsh advfirewall firewall set rule name="Windows Remote Management (HTTP-In)" profile=public protocol=tcp localport=5985 remoteip=localsubnet new remoteip=any`
+
+### AWS User Data
+
+If you are spinning up AWS instances to test against, you can use the following user data when spinning up your instances:
+
+```
+<powershell>
+$logfile="C:\\Program Files\\Amazon\\Ec2ConfigService\\Logs\\kitchen-ec2.log"
+# Allow script execution
+Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Force
+# PS Remoting and & winrm.cmd basic config
+Enable-PSRemoting -Force -SkipNetworkProfileCheck
+& winrm.cmd set winrm/config '@{MaxTimeoutms="1800000"}' >> $logfile
+& winrm.cmd set winrm/config/winrs '@{MaxMemoryPerShellMB="1024"}' >> $logfile
+& winrm.cmd set winrm/config/winrs '@{MaxShellsPerUser="50"}' >> $logfile
+#Server settings - support username/password login
+& winrm.cmd set winrm/config/winrs '@{MaxMemoryPerShellMB="1024"}' >> $logfile
+# Firewall Config
+& netsh advfirewall firewall set rule name="Windows Remote Management (HTTP-In)" profile=public protocol=tcp localport=5985 remoteip=localsubnet new remoteip=any  >> $logfile
+</powershell>
+```
+
+## CONTRIBUTING:
+
+Please file bugs against the KNIFE_WINDOWS project at https://github.com/chef/knife-winops/issues.
+
+More information on the contribution process for Chef projects can be found in the [Chef Contributions document](http://docs.chef.io/community_contributions.html).
+
+# LICENSE:
+
+Original knife-windows author:: Seth Chisamore (<schisamo@chef.io>)
+License:: Apache License, Version 2.0
+
+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.