+Make sure PowerShellGet version is newest, just overwrite install with
+`Install-Module PowerShellGet -AllowClobber -Force` from an admin powershell.
+
+
+Hey grim, before I forget or get sidetracked with other stuff here's the tldr of how I got a Windows VM to configure WinRM and what I had to add on the ansible side of things to be able to connect to it.
+
+To make things simpler, I just leveraged the `ConfigureRemotingForAnsible.ps1` script that the ansible team developed. It's not really what I'd use in a production environment (e.g. it uses self-signed certificates) but it's a good starting point when you just need to bootstrap a Windows VM from scratch to test configuring with Ansible.
+
+The script and instructions on how to use it can be downloaded from https://github.com/ansible/ansible/blob/devel/examples/scripts/ConfigureRemotingForAnsible.ps1#L17-L37. I always use `-EnableCredSSP` because that's what I use when connecting with ansible.
+
+Once you ran that script in your Windows machine you should have everything related to WinRM ready to go. Now on the Ansible side of things, you just need to make sure the following variables are defined (can be done in the inventory, in the playbook, wherever you prefer)