Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Windows Server » How to configure a remote Windows Server to Support Ansible

How to configure a remote Windows Server to Support Ansible

Posted on 17/04/202012/03/2024 Christian By Christian No Comments on How to configure a remote Windows Server to Support Ansible
configure remote server

In this artile, you will learn how to configure a remote Windows Server to Support Ansible. Ansible works against multiple systems in your infrastructure at the same time. It does this by selecting portions of systems listed in the Ansible inventory file. This file can be found in this location /etc/ansible/hosts. You can specify a different inventory file using the -i <path> option on the command line Since Windows Server 2012. Please see how to install and configure Ansible on Ubuntu.

Note: WinRM is enabled by default, but in most cases extra configuration is required to use WinRM with Ansible. Below are the steps to configure Windows hosts to be supported by Ansible.

Also, see how to Install and configure Ansible on Azure Virtual Machine, and how to fix “WinRM cannot complete the operation, verify that the specified computer name is valid“.

Prerequisites for managing Server with Ansible

Ensure you have the right version of PowerShell and .NET Framework.

Here is the Concept of Ansible on Windows using Cygwin, how to automate Infrastructure Deployments in the Cloud with Ansible and Azure Pipelines, and how to fix “WinRM cannot complete the operation, verify that the specified computer name is valid“

Ansible WinRM Connectivity setup for Ansible

The default ports for WinRM 2.x are HTTP port 5985 and HTTPS port 5986.

Method 1

This is my recommended method. Right-click on the content and copy the entire content into Notepad ++

The file type and extension (.ps1) must be appended as shown below. Select the location to want to have the WinRM script saved.

In my case, I have saved the file on the Desktop under the name ConfigureRemotingForAnsible.ps1

Windows
Script Source: RAW GitHub

Next, Then run the PowerShell script. as shown below. Ensure to launch PowerShell as an Administrator

Support Ansible

Navigate to the script location and run it. In this case, we have navigated to the Desktop location where we saved the script. Next, proceed and execute the WinRM script on the Windows host.

Ansible configuration

The output signifies that WinRM has successfully been installed.

This will set the basic settings. The ConfigureRemotingForAnsible.ps1 script is intended for training and development purposes only and should not be used in a production environment since it enables settings (like Basic authentication) that can be inherently insecure.

When this step is complete and the host inventory file is configured correctly as described in this IP Address UNREACHABLE: HTTP connection pool Max exceeded. Then you should be able to ping the remote host successfully as shown below.

Note: You may need to configure the Execution Policy in PowerShell in order to allow scripts to run. See the following link for more information on setting up a Windows host.

Method 2

Use this method before if you will like to run the script locally without an internet connection. To run this command remotely, use the PSEXEC command to do this

psexec \\myserver -accepteula -nobanner -s -u DOMAIN\Administrator powershell -ExecutionPolicy Bypass -Command "iwr https://raw.githubusercontent.com/ansible/ansible/devel/examples/scripts/ConfigureRemotingForAnsible.ps1 -UseBasicParsing | iex"

There is also a free utility on enabling WinRM on Windows Machine locally and remotely

I hope you found this guide on how to configure a remote Windows Server to Support Ansible very useful. Please feel free to leave a comment below.

Rate this post

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Windows Server Tags:Configuration Management Tool, RemoteConnection

Post navigation

Previous Post: IP Address UNREACHABLE: HTTP connection pool Max exceeded
Next Post: Ansible error: Server unreachable, ssl: auth method ssl requires a password

Related Posts

  • active directory faq 2016 1
    How to detect who disabled a user in Active Directory Windows Server
  • ADBA for Windows
    Configure Active Directory-Based Activation (ADBA) for Windows Windows Server
  • Object Firt OOTBI offline and online cluster update
    Offline and Online Update for Object First Out-of-the-Box Cluster Windows Server
  • update
    Client Visibility Issues: Fix WSUS Clients appear then disappear in the console Windows Server
  • Windows Deployment Services
    How to migrate WDS and MDT to a new Windows Server Windows Server
  • Microsoft Enterprise Root Certification Authority and Forest Domain to Azure migration
    Migrate Microsoft Enterprise Root Certification Authority and Forest Domain to Azure AWS/Azure/OpenShift

More Related Articles

active directory faq 2016 1 How to detect who disabled a user in Active Directory Windows Server
ADBA for Windows Configure Active Directory-Based Activation (ADBA) for Windows Windows Server
Object Firt OOTBI offline and online cluster update Offline and Online Update for Object First Out-of-the-Box Cluster Windows Server
update Client Visibility Issues: Fix WSUS Clients appear then disappear in the console Windows Server
Windows Deployment Services How to migrate WDS and MDT to a new Windows Server Windows Server
Microsoft Enterprise Root Certification Authority and Forest Domain to Azure migration Migrate Microsoft Enterprise Root Certification Authority and Forest Domain to Azure AWS/Azure/OpenShift

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • trelloplan
    How to change or cancel your Trello plan JIRA|Confluence|Apps
  • image 42
    How to Install and Setup WordPress into a cPanel and Configure Your First WordPress Theme Configuration Management Tool
  • cisco catalyst switch 1
    How to Reset a Cisco 3650 Catalyst Switch Network | Monitoring
  • images
    Query MBAM to display the BitLocker Recovery report Network | Monitoring
  • Downgrade
    Downgrade VMware Workstation: Fix the Processor does not support xsave on VMware Workstation Virtualization
  • feature image app services
    How to Migrate Azure Web Apps AWS/Azure/OpenShift
  • Featured image Two Factor Authentication
    Change Two-Factor Authentication in Microsoft 365/Office 365 Network | Monitoring
  • FileZilla
    Access FTP Server from your browser: How to create a shortcut and access Filezilla from Windows Explorer Windows Server

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,813 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.