------------------------------------------------------------------------ Plesk Migration Manager (PMM) build 060809.17 for Plesk 7.6 for Windows Release Notes ======================================================================== Contents ======== 1. Introduction 2. Installation Instructions 2.1. Before Installation 2.2. Software Requirements 2.3. Installation Steps 3. What's New 4. Known Problems and Limitations 5. Contact Information 1. Introduction =============== Thank you for downloading this release of Plesk Migration Manager (PMM) for Plesk 7.6 for Windows. This file contains information that supplements the PMM documentation such as 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 ============================ We strongly recommend that you refer to the product installation instructions and the product user manual. Visit the SWsoft, Inc. web site at http://www.swsoft.com for more information. PMM Plesk 7.6 for Windows documentation: http://www.swsoft.com/en/products/plesk76win/docs/ Plesk 7.6 for Windows FAQ: http://www.swsoft.com/en/products/plesk76win/faq/ 2.1. Before Installation ------------------------ Let us call the computer to which you want to migrate your data as "Plesk server", and the computer which has the data you want to migrate as "source server". Install Plesk 7.6 for Windows on Plesk server, if you have not done it yet. If previous version of Plesk Migration Manager is already installed on Plesk server and/or source server, uninstall it (in both locations). 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 Plesk Backup utility. There are two setup programs for carrying out the migration: pmm76_buildXXXX.XX.msi and pmm_agent_buildXXXX.XX.msi. Install pmm76_buildXXXX.XX.msi on Plesk server and pmm_agent_buildXXXX.XXmsi on source host. Important: When performing migration from Unix/Linux servers, you need to install only pmm76_buildXXXX.XX on the Plesk server. 2.2. Software Requirements -------------------------- Before starting the migration, the following requirements should be met: * Plesk 7.6 for Windows configured with at least one IP address * Installed Plesk license key with limits (on clients, domains etc) enough for adding all migrated objects to Plesk * Free disk space for storing the migration dump If you plan to use Microsoft SQL Server support in Plesk 7.6 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 and configured to use standard or mixed security mode. IMPORTANT: * Make sure that versions of migration agent (pmm_agent_buildXXXX.XX.msi) and migration manager (pmm76_buildXXXX.XX.msi) are the same (i.e. the part "XXXX.XX" are 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. * Migration Manager works only with Plesk 7.6 for Windows and higher. * All information about migration process is logged to the migration log file. The Plesk Migration Manager Administrator's Guide contains detailed information on its contents. 2.3. Installation Steps ----------------------- 1. Log in as "Administrator" or another user with Administrator's privileges. 2. Change your working directory to the directory where PMM for Plesk 7.6 for Windows distribution resides. 3. Run the installer. 4. Follow the on-screen instructions. 5. Now you can use Migration Manager. Note that it is available only to Plesk Administrator. 3. What's New ============= build060809.17 3.1 Plesk Migration Manager (PMM) build060809.17 for Plesk 7.6 1. Migration to Plesk 7.6 3.2 Plesk Migration Manager (PMM) build060712.14 for Plesk 7.5.6 1. Remote migration agent for cPanel for Unix 2. Remote migration agent for E-Mail Content Migration 3.3 Plesk Migration Manager (PMM) build 060516.19 for Plesk 7.5.6 1. Remote migration agent for IIS version 5 and 6 3.4 Plesk Migration Manager (PMM) build 060317.12 for Plesk 7.5.6 1. Remote migration agent for Plesk for Unix Version 2.5.x, 5.x, 6.x, 7.1 - 7.5.4 2. Remote migration agent for Ensim 3.6 3.5 Plesk Migration Manager (PMM) build 060203.12 for Plesk 7.5.6 1. Remote migration agent for Ensim 4.0 3.6 Plesk Migration Manager (PMM) build 051125.14 for Plesk 7.5.6 1. Remote migration module 2. Remote migration agent for Helm 3.1.x and 3.2.x 4. Known Problems and Limitations ================================= 1. You should use Migration Manager and Migration Agent with the same build number. Note: This is irrelevant to migrating data from Plesk for Unix. 2. You should have access with Administrator's privileges to source host. 3. You should have Plesk license key with limits enough for migrating all the necessary data from the source host. 4. During the migration process, some logins and passwords can be 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 . 5. User databases are successfully migrated only if they are located on the source server, not the remote one. 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 the source hosting panel is configured to use this local DBMS. Or, you can restore the database dump right to DBMS that is used by Plesk and installed on the Plesk server. Refer to the Plesk Migration Manager Administrator's Guide for additional information. 6. Only mail system configuration is migrated, without mailboxes content. If you migrate data from a mail server to the mail server of the same family, you can use the facilities offered by that mail server for mail content migration. Otherwise, ask your users to store the local copy of their mailboxes. 7. You should have enough free disk space for storing the dump of migration objects configuration, domains and databases content. 5. Contact Information ====================== SWsoft Headquarters 13755 Sunrise Valley Drive Suite 325 Herndon, VA 20171 USA Phone: +1.703.815.5670, Fax: +1.703.815.5675 Web: http://www.swsoft.com E-mail: For billing information, email accounting@swsoft.com For purchasing or partnering information, email sales@swsoft.com For technical support, use our Online Support Form. To report problems with Plesk software, email bugreport@swsoft.com For information on career opportunities with SWsoft, email careers@swsoft.com For press contact information, email press@swsoft.com For information about becoming a Partner, email partners@swsoft.com For information on translating Plesk into your language, email i18n@swsoft.com For general product information, email info@swsoft.com Copyright 1999, 2000, 2001, 2002, 2003, 2004, 2005 SWsoft, Inc. All rights reserved.