Search Engine: Elastic

Article ID: 116548, created on Jul 25, 2013, last review on May 6, 2014

  • Applies to:
  • Operations Automation


There is set of requirements to be satisfied to correctly add new physical or virtual Windows shared hosting server to POA.

The article provides a kind of checklist which allows to avoid most common mistakes during new host deployment in POA.


  1. Make sure OS version, edition and architecture of the host match requirements.

    Every single type of shared hosting service has own requirements to the servers where it may be running. Refer to the corresponding POA Deployment Guide for the official system requirements. E.g. system requirements for IIS 7.5 shared hosting server may be found in the Windows Shared Hosting Deployment Guide.

  2. Make sure the server is added to the correct Active Directory domain.

  3. If you register Virtuozzo for Windows VPS (virtual server) make sure that you follow the correct steps:

    1. Register the new virtual server as VPS, not as hardware node. To correctly register virtual server do this in POA Provider Control Panel at Service Director > Virtuozzo Manager > VPSs, not at Deployment Director > Server Manager > Hardware Nodes. If you register Virtuozzo VPS as hardware node POA will not be able to manage IP addresses on the host.

    2. Register the Virtuozzo VPS as 'Shared' one, not as 'Dedicated'. This means that you must use the resource based on the Virtual Private Servers (Shared) resource class to create new VPS-based Windows shared hosting server, not resource based on the VPS (dedicated) resource class.

    3. Make sure that correct BackNet IP address is assigned to the new VPS. This means that correct BackNet IP pool must be assigned to a Windows-based VPS Hardware Node during registration in POA. This BackNet IP pool is used during Shared VPSs provisioning - Shared VPS automatically obtains BackNet IP Address from it. BackNet IP Address is used by POA Agent installed on Shared VPS to communicate with POA Management Node.

  4. If you register physical Windows shared host and install POA Agent manually on it make sure that you assign BackNet IP address to POA Agent during installation.

  5. Make sure that firewall is correctly configured on a Windows shared hosting server. Correct firewall configuration depends on type of services which will be running on a host. Refer to the corresponding part of the Parallels Automation Firewall Configuration Guide for correct firewall configuration for a particular Windows hosting service.

  6. If POA package installation fails during host registration you may find reason of problem in two places in Control Panel:

    • System Director > Notification Manager > Notifications Log. Of course, corresponding HTTP notification subscription must be created first and the needed events must be added to it, like Package installation failed, Package installed and so on.
    • If you install POA package on the host manually using PPM Group Operations then POA creates corresponding background task and its status may be monitored in Task Manager.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF