Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

modernize winrm setup and fix for 2008r2 #304

Merged
merged 1 commit into from
Mar 7, 2017
Merged

modernize winrm setup and fix for 2008r2 #304

merged 1 commit into from
Mar 7, 2017

Conversation

mwrock
Copy link
Member

@mwrock mwrock commented Mar 1, 2017

The default user_data is broken on 2008R2. It currently runs:

Enable-PSRemoting -Force -SkipNetworkProfileCheck

The SkipNetworkProfileCheck argument is not available on powershell versions prior to 3.0. Windows 2008R2 ships with 2.0 by default. On 2008R2, this command returns:

PS C:\Users\Administrator> Enable-PSRemoting -Force -SkipNetworkProfileCheck
Enable-PSRemoting : A parameter cannot be found that matches parameter name 'SkipNetworkProfileCheck'.
At line:1 char:50
+ Enable-PSRemoting -Force -SkipNetworkProfileCheck <<<<
    + CategoryInfo          : InvalidArgument: (:) [Enable-PSRemoting], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.EnablePSRemotingCommand

This PR also removes the insecure configuration settings of allowing basic auth and unencrypted traffic. The winrm gem has been using NTLM auth by default for over a year and these settings are no longer necessary and unwanted.

fixes #303

Signed-off-by: Matt Wrock matt@mattwrock.com

Signed-off-by: Matt Wrock <matt@mattwrock.com>
@mwrock mwrock merged commit 068b4c1 into master Mar 7, 2017
@mwrock mwrock deleted the winrm_fix branch March 7, 2017 17:46
@fnichol fnichol removed the Developing label Mar 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[WinRM] 500 returned in cleanup with error: Bad HTTP response returned from server
3 participants