17 Commits (b71a62283c80edf225b4876450aa8c17518e04c7)

Author	SHA1	Message	Date
Jordan Borean	719e1840da	Added info on ntlm and credssp, updated configure script for credssp (#21175)	8 years ago
Dag Wieers	6de1f22c15	Add missing support for -CertValidityDays (#21009) ... * Add missing support for -CertValidityDays For some reason the -CertValidityDays option was not being used in the certificates we created. This fixes #10439 * Possible fix * We cannot use New-SelfSignedCertificate on 2012R2 and earlier As suggested by @jhawkesworth	8 years ago
Dag Wieers	28060a4c47	Improve inline docs (#21029)	8 years ago
Dag Wieers	c94c53e8a4	Ensure that the script is run with elevated privileges (#20669) ... * Ensure that the script is run with elevated privileges This fixes #20654 * Implement our own check for elevated privileges	8 years ago
Dag Wieers	e64ef8b0ab	Small fix for running using Invoke-Expression ... A small fix suggested by a user for running ConfigureRemotingForAnsible. This fixes #20512	8 years ago
Dag Wieers	de21038feb	Enable -Verbose and log to EventLog (#19909) ... Instead of asking the user to type something prior to running the script, why not allow -Verbose on the command line directly. Also log important events to EventLog, so that it can be traced e.g. when running via RunOnce mechanism. The documentation is updated as well.	8 years ago
nitzmahone	ee080eddb5	adjust WinRM service configuration message text ... fixes #17478	8 years ago
jlehtniemi-broadsoft	5864ae50c6	Start WinRM service automatically on reboot	8 years ago
Cryptophobia	76a519fddc	Update to ConfigureRemotingForAnsible.ps1	9 years ago
Matt Davis	840cda741d	Merge pull request #12363 from breathe/devel ... allow ConfigureRemotingForAnsible.ps1 script from public zone	9 years ago
Michael Crilly	e9fe5f201f	$SubjectName variable unused; clean up ... Having used this script several times today, I came to notice the $SubjectName variable, being passed in via the CLI, is essentially ignored when generating the SSL certificates, rendering it useless. I believe it's a good idea to have it in place, so I've updated the script to reflect this. I also cleaned up some random new lines throughout the file, and expanded on a comment. It might be worth going a step further and commenting the file fully, as most people reviewing this file won't be familiar with PowerShell (like I wasn't unitl a few days ago). It could be helpful.	9 years ago
Nathaniel Cohen	8b6f8ff928	Document -SkipNetworkProfileCheck switch	9 years ago
Nathaniel Cohen	be452c1b27	allow ConfigureRemotingForAnsible.ps1 script to function from 'public' adapters ... The current script fails on machines which have network interfaces designated as connected to "Public" networks (choices for network designation being Private, Domain, Public). This commit changes the script to NOT prevent winrm initialization when device is connected to a "Public" network.	9 years ago
nitzmahone	74694b2b0d	moved WinRM setup script test after config	9 years ago
Willem Pienaar	ac28652602	Fixed error handling for the enabling of PS Remoting	10 years ago
Chris Church	2f7348fddf	Update firewall rules, error handling, other comment/whitespace cleanup.	10 years ago
Trond Hindenes	d568966e2c	Added script for configuring winrm for Ansible ... The script can be used to set up a windows host with WinRM with the least possible effort.	11 years ago