Allow PowerShell script execution

[dlukman]

Windows AMIs have the ExecutionPolicy set to Restricted and this breaks kitchen converge just before installing Chef Client because it does not allow PowerShell script execution. The added line fixes this issue.

Output:

$$$$$$ & : File C:\Users\Administrator\AppData\Local\Temp\kitchen\default-windows-2012
$$$$$$ r2-long_script.ps1 cannot be loaded because running scripts is disabled on
$$$$$$ this system. For more information, see about_Execution_Policies at
$$$$$$ http://go.microsoft.com/fwlink/?LinkID=135170.
$$$$$$ At line:1 char:42
$$$$$$ + $ProgressPreference='SilentlyContinue';&
$$$$$$ "$env:TEMP/kitchen/default-windows-2012 ...
$$$$$$ +
$$$$$$ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
$$$$$$     + CategoryInfo          : SecurityError: (:) [], PSSecurityException
>>>>>> Converge failed on instance <default-windows-2012r2>.
>>>>>> Please see .kitchen/logs/default-windows-2012r2.log for more details
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: WinRM exited (1) for command: [& "$env:TEMP/kitchen/default-windows-2012r2-long_script.ps1"]
>>>>>> ----------------------

[mwrock]

👍

[Dan-JoeLopez]

+1
For what its worth, I am implimenting this fix on my local machine to enable testing up to aws for my win 2012 instances.

[cheeseplus]

👍

[rveznaver]

Merge? Anyone?