Plesk Migration Manager 1.12.2 for Windows Release Notes

Introduction
Installation Instructions
What's New
Known Problems and Limitations
Contact Information

1. Introduction

Thank you for downloading this release of Plesk Migration Manager (PMM) for Plesk for Windows. This file contains information that supplements the PMM documentation such as software requirements, information on new features, corrected bugs, known problems, etc. This file was updated with the latest information available at release time.

2. Installation Instructions

Refer to the product installation instructions and the product user manual.

Refer to the Parallels web site at http://www.parallels.com for more information.

2.1. Before Installation

The computer to which you want to migrate your data is referred to as "Plesk server", and the computer which has the data you want to migrate as "source server".

Install Plesk for Windows on the Plesk server, if you have not installed it yet.

If an older version of Plesk Migration Manager is installed on your Plesk server and/or source server, uninstall it (in both locations, if applicable).

We strongly recommend that you create a full system backup of the entire servers before you start the migration process. Also, you may want to back up your existing Plesk installation using the Plesk Backup utility.

There are two setup programs that you need to run to install programs for carrying out the migration (example for Plesk 8.2): pmm82_buildXXXXXX.XX.msi and pmm_agent_buildXXXXXX.XX.msi. Install pmm82_buildXXXXXX.XX.msi on Plesk server and pmm_agent_buildXXXXXX.XX.msi on source host.

Important: When performing migration from Unix/Linux servers, you need to install only pmm82_buildXXXXXX.XX on the Plesk server.

2.2. Software Requirements

Before starting the migration, the following requirements should be met:

Plesk for Windows configured with at least one IP address
Installed Plesk license key with limits (on clients, domains etc) sufficient for adding all migrated objects to Plesk
Enough free disk space for storing the migration dump

If you plan to use Microsoft SQL Server support in Plesk for Windows or if Microsoft SQL Server databases are used on the source server and should be migrated to Plesk server, Microsoft SQL Server should be installed on the Plesk server and configured to use standard or mixed security mode.

IMPORTANT:

Make sure that versions of Migration Agent (pmm_agent_buildXXXXXX.XX.msi) and Migration Manager (pmmxx_buildXXXXXX.XX.msi) are the same (i.e. the part "XXXXXX.XX" is the same in the names of both files).
You should have permission to open required TCP/IP ports in firewall.
You should have access to servers where user databases are installed.
Plesk Migration Manager 1.12.2 works only with Plesk 8.2 for Windows.
All information about migration process is logged to the migration log file. The Plesk Migration Manager Administrator's Guide contains detailed information on the file contents.

2.3. Installation Steps

Log in to Plesk server as "Administrator" or another user with Administrator's privileges.
Change your working directory to the directory where PMM for Plesk 8.2 for Windows distribution resides.
Run the installer.
Follow the on-screen instructions.
Migration Manager icon appears on the 'Server' page of the Plesk Control Panel. Note that when installed, it is available only to Plesk Administrator.

3. What's New

3.1 Plesk Migration Manager 1.12.2 build 080512.13 for Windows

[+] Migration agents updates for Plesk 8.2 - PMM for Plesk 8.2 for Windows now includes the following updated migration agents:
- Remote migration agent for Helm 4
- Remote migration agent for Ensim Pro for Linux
- Remote migration agent for cPanel 11
- FTP content Migration

Legend:

[+] new feature

4. Known Problems and Limitations

You should use Migration Manager and Migration Agent with the same build number. Note: This is not necessary when performing migration from Unix/Linux servers.
You should have access with Administrator's privileges to source host.
You should have Plesk license key with limits sufficient for migrating all the necessary data from the source host.
During the migration process, some logins and passwords can be automatically changed. Information about such changes is contained in the AdminMigration.log file. For details on working with the migration log, refer to the Plesk Migration Manager Administrator's Guide .
User databases are successfully migrated only if they are located on the source server, not on another remote server. If source hosting platform uses remote DBMS'es for storing user databases, you can do the following before the migration: Perform manual databases dump on that remote servers, and then restore the dump on the DBMS installed on the source server, providing that the source hosting panel is configured to use this local DBMS. Alternatively, you can restore the database dump right to the DBMS that is used by Plesk and installed on the Plesk server. Refer to the Plesk Migration Manager Administrator's Guide for additional information.
You should have enough free disk space for storing the dump of migration objects configuration, domains, and databases content.

5. Contact Information

Parallels Headquarters
13755 Sunrise Valley Drive Suite 600
Herndon, VA 20171 USA
Phone: +1.703.815.5670, Fax: +1.703.815.5675

Web: http://www.parallels.com

E-mail:
For billing information, email accounting@parallels.com
For purchasing or partnering information, email sales@parallels.com
For technical support, use our Online Support Form.
To report problems with Plesk software, email bugreport@parallels.com
For information on career opportunities with SWsoft, email careers@parallels.com
For press contact information, email press@parallels.com
For information about becoming a Partner, email partners@parallels.com
For information on translating Plesk into your language, email i18n@parallels.com
For general product information, email info@parallels.com

Patented hosting technology protected by U.S.Patents 7,099,948; 7,076,633.
Patents pending in the U.S.