dev-sec / ansible-windows-hardening Goto Github PK

Is your feature request related to a problem? Please describe.
Today only the Linux configurations are published to Ansible Galaxy under the dev-sec community provider: https://galaxy.ansible.com/dev-sec

Describe the solution you'd like
It would be good to see the Windows Hardening playbook published in Galaxy.

This isnt so much a "bug", I have a 2016 RDP host that will be used as a terminal server, but rather than logon with username password, users will be using their respective smart card. This works as expected prior to hardening, after hardening I get a prompt: the system administrator has restricted the types of logon (network or interactive) that you may use. I revert back to the snapshot taken prior to hardening and all is well.
I see you have have variables such as win_security_SeRemoteInteractiveLogonRight. I am listed in the local admins group prior to the change. Not sure after.
I tried with:
--extra-vars "win_security_SeNetworkLogonRight=S-1-1-0" and still had issues

Hello,

My apologies to resorting to using a GitHub Issue to ask this question, but I'm couldn't find another method to contact the maintainers.

I am trying to find out if the Ansible, Chef, or Puppet versions support Windows Server 2008 R2. I completely understand it's EOL, etc. but we have legacy software that requires that operating system.

Any help is appreciate.