The easiest way to perform massive identical installations on web servers that are located on the same network (VLAN) is through a network map of the remote location. With only two steps you can perform remote installations.
Firstly select map a network drive and assign a drive letter to the remote location.
Select your preferred drive letter.
change directory to your remote location through a cmd or GUI and perform your installations.
Ansible is a very powerful automation tool that is developed from RedHat. Many large organizations rely on Ansible to automate tasks and procedures. In this article I will explain how one can use ansible to manage windows clients and servers.
In order to manage windows hosts ansible winrm plugin should be used to communicate with the client/server machine.
The first step is to verify that ansible is installed.
Alongside with ansible, on the control node the pywinrm module should be also installed. By default this one is not installed and one should do it manually.
The managed Windows client/server machines should be configured to allow remote connections. A very useful power shell script is already developed from other users and it needs only to be executed on the managed host.
If your execution policy is prohibiting this script to be executed, you should set-execution policy to RemoteSigned as shown below and then execute the powershell.
Control node should have network connectivity with the managed hosts.
Some environmental variables should be used, so that ansible knows how the connection will be performed (winrm). I included those variables in my inventory file as I created this lab just for demonstration. My inventory file looks like below:
Lastly make sure that the user that is used for the connection has administrative rights on the managed windows hosts. Otherwise some error codes will be returned.
Lastly confirm ansible on managed host is working by using win_ping module.
When the described in the title error appears for a windows server that belongs to a domain the issue could be the domain name that is registered to the domain controller as well as the netbios name that will be registered.
For example two computers with slightly different name are registered to the domain controller.
Their netbios name should be the same for those computers because the max characters allowed are 15, so the below message will appear when adding the second one to the domain.
Those two servers although they will have a different domain name registered on the domain controller, their netbios will be the same and on one of the two nodes you will get the below error when trying to login
In order to resolve this just shorten the name to something less than 15 characters and rejoin the computers to the domain.