Article ID: 115707, created on Mar 13, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo containers for Windows


This article describes important considerations for upgrading from Virtuozzo containers for Windows 4.0 and 4.5.

Important considerations

License key

The Virtuozzo containers 4.x family uses the same license key, so there is no need to upgrade the license when upgrading to version 4.6.

Compatibility with Parallels Automation software

All versions of Odin Service Automation software use API for manipulating the Virtuozzo containers node.

Current versions of the software completely support modern API versions supplied with the latest virtualization software.

Odin Business Automation Standard supports VA Agent starting from v. 4.1.6, so if you have an older version, please consider upgrading OBAS as well.

Management tools

Starting from Virtuozzo containers for Windows 4.6, there are no other supported management tools except for VA. Old tools should be able to manage all Virtuozzo containers for Windows 4.6 settings except for new features. VA versions supporting Virtuozzo containers for Windows 4.6 can be checked in the article "Virtual Automation builds, releases, and supported virtualization products".

Unlike Parallels Infrastructure Manager 4.0 (PIM 4.0, included into Virtuozzo containers for Windows 4.0 and 4.5), VA contains two parts:

  • VA Agent, to be installed on the host with a virtualization product installed;
  • VA MN (Management Node), to be installed into a separate environment to host the master server of the group.

For standalone nodes, the connection to the port 443 and 4643 on the node's IP address is no longer possible with VA Agent installed, the node should be registered in VA MN and managed by means of VA MN.

Upgrade to Virtuozzo containers 4.6


  • Seamless upgrade procedure
  • Most recent version of virtualization software
  • Highest density
  • Best performance
  • Latest version of VA Agent


  • No VZAgent 3.0 compatibility mode


Search Words

containers for windows upgrade

planning upgrade

d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 965b49118115a610e93635d21c5694a8

Email subscription for changes to this article
Save as PDF