Article ID: 118043, created on Oct 18, 2013, last review on Feb 9, 2015

  • Applies to:
  • Operations Automation 5.5

Symptoms

During the installation of a new Windows hardware node, the following error appears in the dialog:

Automated WinRM Enabling Failed
Error during WinRM enabling on '<IP>'. Script exit code is -1. Script output (stdout/stderr): Operation timed out/
Repair Connectivity
To make automated deployment possible please try to check network communications between Management and target nodes. Ensure that WMI is not blocked on a target node. Or copy, paste and invoke the following script on a target node.

netsh advfirewall firewall add rule name="WinRM in" protocol=TCP dir=in profile=any localport=5985 remoteip=any localip=any action=allow
netsh advfirewall firewall add rule name="POA in" protocol=TCP dir=in profile=any localport=8352 remoteip=any localip=any action=allow
netsh advfirewall firewall add rule name="POA in 2" protocol=TCP dir=in profile=any localport=8354 remoteip=any localip=any action=allow
netsh firewall add portopening TCP 5985 WinRM enable SUBNET
netsh firewall add portopening TCP 8352 POA enable SUBNET
netsh firewall add portopening TCP 8354 POA2 enable SUBNET
sc config winrm start= auto
sc start winrm
%windir%\system32\timeout /t 5
cmd /c winrm put winrm/config/service @{AllowUnencrypted = "true"}
%windir%\system32\timeout /t 2
cmd /c winrm put winrm/config/service/Auth @{Basic = "true"}
%windir%\system32\timeout /t 2
cmd /c winrm create winrm/config/Listener?Address=*+Transport=http @{Port="5985"}

Cause

Ports 5985, 135 and 445 are not accessible from POA management node

Resolution

Configure the firewall according to Firewall configuration guide: http://download.pa.parallels.com/poa/5.5/doc/pdf/Installation/pa_5.5_firewall_configuration_guide.pdf

And ensure that the procedure from http://download.pa.parallels.com/poa/5.5/doc/pdf/Installation/poa_5.5_windows_shared_hosting_deployment_guide.pdf page 141 Is followed.

Search Words

can add hardware node

error when adding the hardware node

Automated WinRM Enabling Failed

5b048d9bddf8048a00aba7e0bdadef37 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF