Movithere Server edition Guide. Guide to using Movithere to perform a Microsoft Windows Server data migration quickly and securely.

Size: px

Start display at page:

Download "Movithere Server edition Guide. Guide to using Movithere to perform a Microsoft Windows Server data migration quickly and securely."

Jessie Harris
5 years ago
Views:

1 Movithere Server edition Guide Guide to using Movithere to perform a Microsoft Windows Server data migration quickly and securely.

3 Contents Introduction to Movithere Server Edition Guide...1 About Movithere Server Edition...1 How Movithere migrates data...1 Supported servers...2 Before you begin...2 Prerequisites...2 Installation...4 The main Movithere screen...6 Using Movithere for your data migration...6 Configuring your projects...6 Starting the data migration Data Re-synchronization Movithere Tools Remote Service Control Remove Remote Projects Troubleshooting Index Movithere Server Edition Guide i

4 ii Movithere Server Edition Guide

5 Introduction to Movithere Server Edition Guide This guide is meant to help you use Movithere Server edition to implement a successful data migration. The first part of this guide describes the Movithere approach to a data migration and the preparations that will help you avoid known issues when migrating your data. The following section includes step-by-step procedures for using Movithere. Where screen captures are included in procedures, they follow the step. Troubleshooting tables are included in the last section. About Movithere Server Edition Movithere Server Edition is a migration tool that allows you to perform a Microsoft Windows Server data migration quickly and securely, while maintaining all ACL and Share permissions. Whether you are performing a data migration because of a failing server, a platform upgrade, a server consolidation or to prepare for the cloud, Movithere reduces risk, time and costs associated with moving data from one server to another. Movithere is designed to migrate data from server to server while maintaining ACL and Share permissions. It is not designed to migrate applications, as applications can contain dependencies in other folders and registered DLL s. You can use Movithere for the following types of data migration scenarios: Multi-domain data migration (Cross-forest migration) The source server is in one domain and the target server is in a different domain. Same domain data migration (single domain) Both the source server and the target server are in the same domain. Windows Workgroup Server data migration Both the source and the target server are in the same peer-to-peer local area network (LAN), rather than a domain. How Movithere migrates data Movithere migrates your data using a three-step approach that allows users to work and access their data on the source server during the migration process. Step 1 Stores the source information Information about users, passwords, rights, local groups, and file, folder and share permissions are collected and stored on the source server. This information is not translated to the target server until the data copy is complete. Step 2 Copies data Folders, Files and Shares are copied to the target server without permissions applied. The original data and shares are never modified. Movithere Server Edition Guide 1

6 Step 3 Source information translates to the target After the data is copied to the target server, the source information collected in step 1 is translated to the target server. Users, local groups or shares originally on the source server are recreated on the target server. The translated file, folder and share permissions are applied to the migrated data on the target server including Ownership, Primary groups and Inheritance. Note The entire migration process may take hours to complete. Users can continue to work and access their data on the source server. After the migration is complete, you can run a re-synchronization to ensure that any changes made on the source are transferred to the target server. Supported servers You can use Movithere on the following operating systems: Processor Operating System x-86-based Windows Server 2000, 2003, 2003 R2, 2008 x-64 based Windows Server 2003, 2003 R2, 2008 R2, 2012, 2016 You can migrate data between member servers and domain controllers in any combination including: Member server to member server Domain controller to domain controller Member server to domain controller Domain controller to member server Before you begin Movithere is project based. The project is a data migration between a pair of servers, where one is the source and one is the target. The terms source server and target server are used throughout this document. The source server is the server that the data is being migrated from. The target server is the server that the data is being migrated to (destination server). For example, if you are moving data from \\servera to \\serverb, then\\servera is the source and \\serverb is the target. If more than 2 servers are included in the data migration, then each pairing of a source server and target server is considered a separate project. Prerequisites Before beginning a data migration, a number of requirements need to be in place to complete the migration successfully. These prerequisites meet the standards for both Microsoft Windows migrations and Movithere. 2 Movithere Server Edition Guide

7 Prerequisites for each type of data migration Type of data migration Multi-domain migration Source and target servers are in different domains. Same or single domain server migration Source and target servers are in the same domain. Windows Workgroup server migration Source and target server are in the same peer-to-peer LAN. Prerequisites Establish a two-way trust relationship between all domains. Verify the trust relationship - check that you can list accounts from each domain in each domain. Add the Domain Admins group to each domain s Administrators group. The account used to perform the migration must be a member of the Domain Admins Group that the target server is a member of. Verify or add the Domain Admins group to each server s Administrators group. The account used to perform the migration must be a member of the domain s Domain Admins group. The account used to perform the migration must be the Administrator account. If the Administrator account has been renamed the account must be changed back to Administrator on each server, and the Administrator s password on each server must be the same. Required server settings for all data migrations types Server setting Local server account password Requirements The Local Password Policy on the target server must be equal to or less restrictive than the source server s password policy. Password Migration registry requirements are automatically set when Movithere is installed. NETBIOS naming resolution NetBIOS browsing must be enabled to resolve computer names. On the WINS tab, Advanced TCP/IP options on both the source and the target servers must be set to: Enable LMHOSTS lookup Enable NetBIOS over TCP/IP If naming resolution is an issue and server names are not resolved create an LMHOSTS file. Group Policy The Windows Firewall must be disabled on both the source and target server. IP Filtering must be disabled for both the source and target servers in the Advanced TCP\IP Options Setting to Permit All. For Windows 2008, 2012 and 2016 servers, disable User Account Control (UAC) on both the source and the target. Movithere Server Edition Guide 3

Server setting Requirements Server There must be enough space on the target server to migrate the source data. The Windows directory must be shared as ADMIN$ on both the source and the target servers.

8 Server setting Requirements Server There must be enough space on the target server to migrate the source data. The Windows directory must be shared as ADMIN$ on both the source and the target servers. The drives must be shared as C$, D$ E$ etc. on both the source and the target servers. Remote Registry services must be running on both the source and the target servers, The RPC services must be running on both the source and the target servers. Installation You can install Movithere on the source server, the target server, or on any workstation or server that is on the same subnet. The computer that you install Movithere on is referred to as the console. You should be logged on to the console as a member of the domain s Domain Admins group, or the Administrator in a workgroup, before you install Movithere. Note Do not install Movithere using a virtual session. After Movithere is installed, you can log on to the console using remote desktop applications, such as mstsc (Microsoft Terminal Service Client), TeamViewer, Radmin, or VNC (Virtual Network Computing). To install Movithere 1. Double-click MovitherevXXX.zip, and then double-click Setup.exe. 2. Click I AGREE to agree to the end user license agreement (EULA). 3. Click Install to begin the installation. 4. Select the path where you want to install Movithere. 4 Movithere Server Edition Guide

9 5. Select the Windows bit version of the computer you are installing Movithere on. 6. Click OK. 7. Click AGREE. When you install Movithere, it is setup as a fully functional trial version that you can use up to 5 times. After the fifth time, you well be prompted to license the product. When you purchase Movithere, you will receive an that contains a license key to make the product fully functional. To License Movithere 1. Click License Current Movithere Package. 2. Click Next. 3. Type the address that you provided when you purchased Movithere in the Address box. 4. Copy the license key that you received in your License key , and then paste it in the License Key box. Movithere Server Edition Guide 5

5. Click OK. 6. Click Close to close the window. 7. Click Exit. The main Movithere screen The Movithere start screen opens each time you open Movithere.

10 5. Click OK. 6. Click Close to close the window. 7. Click Exit. The main Movithere screen The Movithere start screen opens each time you open Movithere. Project Options and Movithere Tools are located on the start screen. Under Movithere Projects, you can create a new migration project, open an existing migration project or synchronize an existing project. Under Movithere Tools, you can license Movithere, open Movithere Remote Service Controller scheduling service or remove the remote agents from the source and the target servers. Using Movithere for your data migration To use Movithere to migrate data, you create projects with a source and a target server, configure the project, and then start the data migration. Configuring your projects Each project that you configure must have: A unique name. A defined source server and a defined target server. Specified options for how the data will be transferred from the source server to the target server. 6 Movithere Server Edition Guide

The remote agent used to collect information about users, passwords, rights, local groups, and file and folder permissions installed on the source server.

11 The remote agent used to collect information about users, passwords, rights, local groups, and file and folder permissions installed on the source server. The remote agent used to translate the information about users, passwords, rights, local groups, and file, folder, and share permissions installed on the target server. After the project is configured, you can open it and verify the configuration, before migrating the data. To configure a new Movithere data project 1. Select Create New Migration Project on the main Movithere screen. 2. Click Next. 3. Type a name for your new project in the New Project Name text box. 4. Identify the project source server you are moving the data from Type the source domain or workgroup name that the project source server is a member of in NetBIOS format Type the name of the project source server in UNC format (\\servername) Type the IP Address of the project source server Click Next. 5. Define the project source server properties Select the Windows bit format of the project source server Select the project source server type Type the Administrative account name to use for the project source server in UNC format (domainname\accountname) Type the password for the Administrative account. Movithere Server Edition Guide 7

12 5.5. Click Next. 6. Identify the target project server to move the data to Type the target domain or workgroup name that the project target server is a member of in NetBIOS format Type the name of the project target server in UNC format (\\servername) Type the IP Address of the project target server Click Next. 7. Define the project target server properties Select the Windows bit format of the project target server Select the project target server type Type the Administrative account name to use for the project target server in UNC format (domainname\accountname) Type the password for the Administrative account. 8 Movithere Server Edition Guide

7.5. Click Next. 8. Select the data to migrate. 8.1. Click to expand the drive where the data is located. 8.2. Select the folders with the data to migrate. 8.3. Click Add.

13 7.5. Click Next. 8. Select the data to migrate Click to expand the drive where the data is located Select the folders with the data to migrate Click Add. The folder will be added to the Folder Trees to Migrate window Click Next. 9. Configure the data transfer Select the copy options Type the letter of the drive that you want to copy the data to on the target server followed by a colon. For example, D: Type the drive share of the source server that Movithere will install the remote agent that collects on followed by a $. For example, C$. Movithere Server Edition Guide 9

$Note Your project is saved on the console to driveletter:\movithere\projects\projectname\.$

14 9.4. Type the drive share of the target server that Movithere will install the remote agent on followed by a $. For example, C$. 10. Click OK. Note Your project is saved on the console to driveletter:\movithere\projects\projectname\. Starting the data migration After you have configured your new project, you can use the project file to start the data migration at any time. You can configure and save multiple project files to migrate later. Each project must have a unique name. To start the data migration 1. Select Open an Existing Migration Project. 2. Click Next. 3. Select the project to migrate. 10 Movithere Server Edition Guide

project. 6. Read the list to check the accuracy of all the project options, and then click Next. 7. Click Install.

the project. 8. Click Check to verify that all the prerequisites are installed and correctly configured. 9. Click Next.

15 4. Click Next. 5. Click Check in the Movithere Reporting window to view a summary of the options that you selected when you configured the project. 6. Read the list to check the accuracy of all the project options, and then click Next. 7. Click Install. Movithere will begin installing the remote agents on the source and the target servers that you specified when you configured the project. 8. Click Check to verify that all the prerequisites are installed and correctly configured. 9. Click Next. OR If any of the requirements fail verification, then click Cancel. The main screen will open. Refer to Troubleshooting on page 14 for information on possible issues and solutions. 10. Click Start to start the data migration. Movithere Server Edition Guide 11

As the data migration proceeds, information about the progress of the migration is listed in the Movithere Data Migration Window. The left panel lists the objects on the source server.

The center panel reports the progress of the migration. The message Migration Process has finished running listed in the center panel, indicates that the data migration is complete.

16 As the data migration proceeds, information about the progress of the migration is listed in the Movithere Data Migration Window. The left panel lists the objects on the source server. The right panel list the objects on the target server. You can use the information listed in the left and right panels to compare the objects on the source and the target server. The center panel reports the progress of the migration. The message Migration Process has finished running listed in the center panel, indicates that the data migration is complete. Data Re-synchronization Before you enable your target server and give users access to it, you should run a final data resynchronization to ensure that any changes made to files, folders, shares or permissions on the source while the migration was running are included in the final migration. 12 Movithere Server Edition Guide

17 Note The re-synchronization does not delete any project data previously migrated to the target server. The synchronization is from the source server to the target server, not from the target to the source. To run a re-synchronization of the data 1. Open Movithere. 2. Click Synchronize an Existing Project. 3. Click Next. 4. Select the project you want to re-synchronize. 5. Click Next 6. Click Start in the Movithere Data Migration Window. The message Migration Process has finished running is listed as the first item in the center panel of the Movithere Data Migration window when the re-synchronization is complete. Movithere Tools Movithere includes several tools that you can use to manage Movithere remote services and agents. These tools can be accessed through the Movithere main screen. Remote Service Control Manages the remote scheduling service that Movithere uses to launch remote agents on the servers. You can use it to install, start, stop, change accounts, and report on the status of the remote scheduling services. Remove Remote Projects Removes selected projects on the console. Removes the remote agent from both the source and the target servers. Uninstalls the Movithere scheduling service. There is no uninstall for the Movithere application. Movithere does not embed any entries in the server registry. To remove Movithere from the console delete the following 2 folders: MOVIT Movithere Movithere Server Edition Guide 13

18 Troubleshooting Issue Movithere only opens the licensing screen. The remote agent scheduling service does not start. Solution Movithere installs as a trial version. You may have exceeded your free trial limit. If you have purchased Movithere, you should have received an containing your license key. See: To License Movithere on page 5. Click Close to connect to shop.html to purchase Movithere. If you have purchased Movithere and your license key is not working, go to: to submit a support ticket. The remote scheduling service is not accepting the credentials for the account that is being used to start the service. Check that the credentials of the service account used to install Movithere meet the following criteria: is an administrative account on the server has rights to Log on locally has rights to Log on as a service the password does not begin with a special character Manually start the schedule service. 1. Connect to the server(s) that the Scheduling service is not running on. 2. Start the services MMC. OR Run RSControl.exe. 3. Navigate to the Schedule service or FSTScheduler. 4. Click the Log On tab. 5. Click This account. 6. Type the service account name and password. 7. Click Apply. 8. Click the General tab. 9. Click Start in the Server status area. 10. Click OK. 14 Movithere Server Edition Guide

19 Issues Unable to Verify Source or Target Server Names Passwords did not copy to the target server. Solution The console server is unable to resolve NetBIOS Names. Adapter options under Advanced TCP/IP Settings must be set to: Enable LMHOSTS lookup Enable NetBIOS over TCP/IP If the above settings are enabled, and you still are not able to resolve NetBIOS Names, use a text editor, for example Notepad, to create an LMHOSTS file. 1. Create the LMHOSTS file. 2. Add the IP Address and the name of the source domain server. 3. Add the IP address and the name of the target server. 4. Add the IP Address of the domain controller and the domain name, if required in a domain scenario. 5. Save the new LMHOSTS file without an extension. 6. Run cmd. 7. Type nbtstat -R. to Register the LMHOSTS file to cache. 8. Type nbtstat -c to verify that all entries are in the cache table. For more information on LMHOSTS files see: The password export/import may be restricted. Check the Lsa setting in the registry on both the source and the target servers. Under HKLM\SYSTEM\Current\ControlSet\Control\Lsa, remove any PKU2U entries from the Security Packages key. Virus software may have falsely identified Movithere password copy.dll as a Trojan and marked, identified, or quarantined the.dll. Temporarily disable all anti-virus software and remove copypwd.dll from quarantine. Remember to enable your virus protection after the migration is complete! Movithere Server Edition Guide 15

21 Index C cross-forest migration. See multi-domain migration D domain controller, 2 I installation, 3, 4 L license, 5, 14 LMHOSTS, 15 local server account password, 3 M member server, 2 multi-domain migration, 1, 2 N NetBIOS naming resolution, 3, 15 P permissions, 1, 7 prequisites, 2 project configuration, 6 location saved to, 10 requirements, 6 servers, 2 R remote agent, 14 requirements, 3 Group policy, 3 local server account password, 3 NetBIOS, 3 server, 3 S same domain migration, 1, 2 scheduling service, 14 source, 2 supported servers, 2 synchronization, 12, 13 T target, 2 TCP\IP options, 3 tools, 13 troubleshooting, 14 license, 14 passwords, 15 source name, 15 target name, 15 U uninstall, 13 W Windows Workgroup migration, 1, 3 Movithere Server Edition Guide 17

MOVITHERE USB OVERVIEW

MOVITHERE USB OVERVIEW Movithere-USB version was designed to move server or workstation objects, files, folders, shares and security between unconnected Windows servers or workstations. Movithere USB is