FAQs Archive | Page 2 of 3 | VirtaMove
Home » FAQs

Frequently Asked Questions

No, VirtaMove does not migrate IIS binaries. When migrating IIS-based applications, VirtaMove leverages IIS itself and migrates configuration, web content, security, and 3rd-party plugins.

Encapsulating an application in a temporary VirtaMove container makes the application portable, because a container is essentially a directory of files that the VirtaMove runtime interprets. This makes it easy to provision additional cloud instances and to rehost a VirtaMove-prepared application. Scaling out a web-serving tier, for example, is as easy as provisioning new instances and makes it easy to spawn the hosting of the VirtaMove container multiple times.

VirtaMove is hypervisor agnostic and cloud independent. VirtaMove software has no ties to hypervisors or service APIs. This means that the VirtaMove migration solution works and is valuable anywhere the Windows Server operating system exists.

The temporary container houses the application and all associated data files. Therefore, all changes made by the application remain within the VirtaMove container.

Yes. You can create independent VirtaMove containers for each tier of an application set, allowing you to migrate applications to different destination servers. In addition, VirtaMove’s “Config-on-the-Fly” process ensures that identity-related application settings are resolved appropriately on each destination server.

All VirtaMove commands and functions are available from the CLI, making the creation and administration of VirtaMove containers fully scriptable. This allows VirtaMove to integrate with solutions for release and configuration management using any deployment.

VirtaMove understands fundamental windows application concepts like DCOM and Windows side-by-side, and knows how the implementation of these concepts varies for each Windows Server release. VirtaMove can discover, copy, and install an application component in the way that the destination OS expects.

Yes. VirtaMove can be used to migrate applications to new Citrix environments or to standalone servers, if the targeted applications have been traditionally installed and have not already been encapsulated in a virtualization or redirection layer.

By default, VirtaMove uses the SMB protocol (Windows File Sharing), which runs over port 445. The default port for migrations using VirtaMove Source Agent is port 9665; however, the port number is configurable. Any specific firewall or port requirements that the targeted application requires will need to be enabled or configured on the destination server.

The VirtaMove solution offers subscription-based, software products and services that help customers automate the movement and migration of applications from outdated servers to new Windows Server operating systems, servers, and VMs, in a datacenter or on the cloud.

Get a project proposal now Click here