Article ID: 126432, created on Aug 4, 2015, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo containers for Windows


Due to the nature of Containers for Windows there are limitations for container migration.

This article accumulates Windows containers migration requirements, best practices and troubleshooting steps.

Table of contents

OS version compatibility for container migration

Windows 2012 Family

Windows 2012 is supported since Containers for Windows 6.0.

Windows 2012 R2 is not supported.

SourceW2K12W2K12 R2
W2K12 R2N/AN/A

*Migration is allowed between hosts with the same language only.

Windows 2008 and Windows 2008 R2 Family

Windows 2008 is supported since Parallels Virtuozzo Containers for Windows 4.5.

Windows 2008 R2 is supported since Parallels Virtuozzo Containers for Windows 4.6.

SourceW2K8 SP1W2K8 SP2W2K8 R2W2K8 R2 SP1

*Not all Windows 2008R2 SP1 editions and locales are supported by Containers for Windows. For more information, refer to this article:

113610 Windows 2008R2 SP1 locales and editions supported by Containers for Windows

Windows patch level requirements

  • The source and the destination nodes should be configured to be as similar as is possible. Ideally, identical Microsoft update sets should be installed on both nodes.

  • Make sure that the destination node has all updates installed on the source. If one node is missing a package (MS update, IE version, etc.), it is better to install it on the node rather than removing it from the other node.

  • It is necessary to obtain updates from VZ WSUS or from its local proxy

Keep in mind the following migration requirements:

  • Architectures must be the same. Migration from x86 to x64 and vice versa is not supported.
  • No migration is possible between Windows Server 2003 Windows Server 2008 and Windows Server 2012.
  • The same Service Pack shall be installed on both source and destination nodes. Note that Service Pack 1 for 2008 R2 is supported only if it is Integrated.
  • Host OS localization versions must be the same.
  • Hosts must be the same product type, i.e., migration between Enterprise and Datacenter editions is not supported. (The only exception is migration between Windows 2003 Standard and Enterprise editions, which is supported.)
  • For Windows 2008 and Windows 2008 R2, the source host and destination host must either both have Hyper-V enabled or neither have it enabled. If one of the hosts has Hyper-V enabled and the other does not, the migration will result in an error.
  • The same .NET versions should be installed on both nodes.
  • The same Internet Explorer versions should be installed on both nodes.

How to migrate a container

To migrate container 101 to hardware node and preserve source data

vzmigrate --remove-area no 101

*If container was running, online migration will be performed. Container's private folder on source server will be saved in CTID.migrated folder in vz\private folder.

To migrate container 101 to hardware node and assign a new ID(102) to container

vzmigrate --remove-area no 101:102

More details are available in the User's Guide.

Container migration troubleshooting

There is a known issue where update removal is handled incorrectly by Containers for Windows. If several updates that patch the same file are installed on the source node and some of these are not installed on the destination node, Virtuozzo containers will remove the update from the container. The hardlink attribute to the WinSxS location will also be removed from the respective file. Since other updates are listed as installed in the container, the hardlink will not be recreated.

In result some files (mostly libraries with a .dll extension or drivers with the .sys extension) will appear to have a size of zero, as seen inside the container, in it turn migrated container may not start or some of it functionality will be corrupted.

If MMC could not create the snap-in in container after migration, this indicate .NetFramework inconsistency in container.

C2V migration

Another possible migration scenario of Windows containers is a C2V migration, when a container is tranformed into a Vituozzo virtual machine. The detailed instructions on such kind of migration can be found in the articles below:

  • 117955 How to migrate a container to a virtual machine?
  • 125000 Best practices and known limitations of container to virtual machine (c2v) migration from Virtuozzo containers for Windows to Virtuzzo (Parallels Cloud Server).

Search Words

windows updates



best practices

How to migrate windows container

migration to sp1

Broken links

У меня есть вопрос по поводу online migration.


Migration successful but no RDP




2897d76d56d2010f4e3a28f864d69223 965b49118115a610e93635d21c5694a8 d02f9caf3e11b191a38179103495106f

Email subscription for changes to this article
Save as PDF