Using Ansible on Windows and BSD
Making Open Source More Inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. We ask that you open an issue or pull request if you come upon a term that we have missed. For more details, see our CTO Chris Wright’s message.
Welcome to the Ansible guide for Microsoft Windows and BSD. Because Windows is not a POSIX-compliant operating system, Ansible interacts with Windows hosts differently to Linux/Unix hosts. Likewise managing hosts that run BSD is different to managing other Unix-like host operating systems. Find out everything you need to know about using Ansible on Windows and with BSD hosts.
- Setting up a Windows Host
- Using Ansible and Windows
- Windows Remote Management
- Desired State Configuration
- Windows performance
- Windows Frequently Asked Questions
- Does Ansible work with Windows XP or Server 2003?
- Are Server 2008, 2008 R2 and Windows 7 supported?
- Can I manage Windows Nano Server with Ansible?
- Can Ansible run on Windows?
- Can I use SSH keys to authenticate to Windows hosts?
- Why can I run a command locally that does not work under Ansible?
- This program won’t install on Windows with Ansible
- What Windows modules are available?
- Can I run Python modules on Windows hosts?
- Can I connect to Windows hosts over SSH?
- Why is connecting to a Windows host through SSH failing?
- Why are my credentials being rejected?
- Why am I getting an error SSL CERTIFICATE_VERIFY_FAILED?
- Managing BSD hosts with Ansible