Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
VirtaMove Knowledge Center
/
Restrictions
Published Mar 02, 2022

    Restrictions

    Table of Contents

    • 1 Clean Destination Machine
    • 2 Driver Files
    • 3 Container Naming Conventions
    • 4 Start Windows "Server" Service
    • 5 Applications on a Remote or Removable Drive

    Clean Destination Machine

    For best possible results, VirtaMove requires a clean destination machine. This is typically a server where the operating system has the latest Windows updates and patches applied, and VirtaMove is the only software package installed.

    Driver Files

    VirtaMove does not support the migration of drivers. Drivers should be pre-installed on the destination machine.

    Container Naming Conventions

    VirtaMove uses Microsoft file naming conventions. You may use any character in a container name, including Unicode characters and characters in the extended character set (128–255), except for the following reserved characters:

    < (less than)
    > (greater than)
    : (colon)
    " (double quote)
    / (forward slash)
    \ (backslash)
    | (vertical bar or pipe)
    ? (question mark)
    * (asterisk)

    For Unicode characters, make sure that you select a font that can display the relevant characters. For example, change the font of the command prompt to Lucida Console.

    For more information, see: https://msdn.microsoft.com/en-ca/library/windows/desktop/aa365247(v=vs.85).aspx

    When choosing a container name, consider the following:

    • By default, the container name is the same as the name of the container folder, which contains VirtaMove runtime support files, the configurable container properties, file set, registry set, services, and other dependencies that are referenced in the template. Therefore, when choosing container names, avoid characters that cannot be used in a Windows folder name.

    • A name must have at least 1 character and a maximum of 63 characters.

    • Do not start or end the container name with a period (.) or use a reserved extension such as ".exe" or ".cap".

    • Do not use the name "hostid", "self”, or "sourceid".

    • Choose unique names for containers.

    • Choose a naming convention that will make containers easy to identify.

    • Do not use blank spaces in a container name. Microsoft Web Deploy and VirtaMove IIS migrations require that container names and paths do not contain blanks.

    Start Windows "Server" Service

    The Windows Server service supports file, print, and named-pipe sharing over the network for a computer. If this service is stopped, these functions will be unavailable. If this service is disabled, any services that depend on it will fail to start. The Server service must be started on the source machine before you start a migration.

    Applications on a Remote or Removable Drive

    The application that you want to include in the container must reside on the computer where VirtaMove is installed. It may not reside on a remote server and its components may not be accessed via mapped network drives, UNC locations, or removable drives.


    VirtaMove Documentation
    • VirtaMove Support Knowledge Base
      VirtaMove Support Knowledge Base
       This trigger is hidden
    Results will update as you type.
    • V-Migrate Documentation
      • 01. Managing Your VirtaMove Licensing
      • 02. Installation Guide
      • 03. Application Migration Guide
        • Environmental and Machine Requirements for Migration
        • Introduction to VirtaMove Application Migration
          • About Migrating Applications
          • The Application Migration Process
          • Network Latency and Migrations
          • Restrictions
          • 16-Bit Detection Utility
          • Source Information
          • Viewing Tether Messages and Errors
        • Activating Your VirtaMove License
        • Migrating an Application
        • Migrating an IIS Application
        • Using VirtaMove Source Monitor
        • Monitoring Migration
        • Running and Exercising Your Application
        • Dissolving Your Application
        • Advanced Application Migration
      • 04. Administration Guide
      • 05. CLI Guide
      • About VirtaMove V-Migrate Documentation
    • V-Maestro Documentation
    • VirtaLinux Documentation

      You‘re viewing this with anonymous access, so some content might be blocked.
      {"serverDuration": 10, "requestCorrelationId": "b4c1041423d7404e82d648e6b47c545f"}