workaround for dealing with WinRM 3.0 and newer #79
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for putting this together. |
sneal
added a commit
that referenced
this pull request
Aug 14, 2013
workaround for dealing with WinRM 3.0 and newer
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added a check to see what version of WinRM is in play and if the version is greater than 2, I added a powershell script to return the required data to match the original wmi query. The current winrm gem doesn't properly query all the WMI classes (API's changed some it appears).
This should add support for VMs running WMF3 and 4, Windows 8/8.1, Server 2012, and Server 2012 R2.