<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Windows on R15Cookie Notes</title><link>https://r15cookie.com/tags/windows/</link><description>Recent content in Windows on R15Cookie Notes</description><generator>Hugo</generator><language>en-us</language><copyright>Steve Miller [BY-NC 4.0](http://creativecommons.org/licenses/by-nc/4.0/)</copyright><atom:link href="https://r15cookie.com/tags/windows/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows Cheatsheet</title><link>https://r15cookie.com/info/win-cheatsheet/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://r15cookie.com/info/win-cheatsheet/</guid><description>Every now and then we do have to use windows. So let&amp;rsquo;s try to make it as Linux like as possible
Enabling WinRM As Ansible leverages WinRM for managing Windows servers, it&amp;rsquo;s guide below provides a lot of helpful guidance:
https://docs.ansible.com/ansible/latest/user_guide/windows_setup.html
The TL;DR is to use the following snippet below to run a powershell script that will correctly enable WinRM for the system:
$url = &amp;#34;https://raw.githubusercontent.com/ansible/ansible/devel/examples/scripts/ConfigureRemotingForAnsible.ps1&amp;#34; $file = &amp;#34;$env:temp\ConfigureRemotingForAnsible.ps1&amp;#34; (New-Object -TypeName System.</description></item></channel></rss>