Quest 8.10 Migration Manager Installation Guide
โฆษณา
โฆษณา
8.10
Installation Guide
© 2015 Quest Software, Inc.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.
If you have any questions regarding your potential use of this material, contact:
Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656 www.quest.com
Email: [email protected]
Refer to our Web site ( www.quest.com
) for regional and international office information.
TRADEMARKS
Quest, Quest Software, the Quest Software logo, Simplicity at Work are trademarks and registered trademarks of Quest Software, Inc. For a complete list of Quest Software's trademarks, please see http://www.quest.com/legal/trademark-information.aspx
. Other trademarks and registered trademarks are property of their respective owners.
DISCLAIMER
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED
IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER
AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY
DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING,
WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF
INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST
HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.
This documentation is also available online at http://documents.quest.com
. This site provides robust search capabilities that allow you to search across all related documents.
Quest Migration Manager
Version 8.10
Last updated
– March 11, 2015
Contents
Preparing the Source and Target Environments for Active Directory Migration15
Opening the Required Ports on Servers, Routers, and Firewalls ................................... 17
Number of NSPI Connections to a Windows 2008-based Domain Controller ................ 18
3
Quest Migration Manager 8.10 - Installation Guide
About This Guide
Overview
This guide contains the information required to install and configure Quest Migration
Manager. It is intended for network administrators, consultants, analysts, and any other IT professionals using the product.
Conventions
In order to help you get the most out of this guide, we have used specific formatting conventions. These conventions apply to procedures, icons, keystrokes and crossreferences.
ELEMENT CONVENTION
Select
Bolded text
This word refers to actions such as choosing or highlighting various interface elements, such as files and radio buttons.
Interface elements that appear in Quest products, such as menus and commands.
Used for comments.
Italic text
Bold Italic text
Introduces a series of procedures.
Blue text Indicates a cross-reference.
When viewed in Adobe® Acrobat®, this format can be used as a hyperlink.
Used to highlight additional information pertinent to the process being described.
Used to provide Best Practice information. A best practice details the recommended course of action for the best result.
Used to highlight processes that should be performed with care.
+
|
A plus sign between two keystrokes means that you must press them at the same time.
A pipe sign between elements means that you must select the elements in that particular sequence.
4
Quest Migration Manager 8.10 - Installation Guide
What Is Quest Migration Manager?
Quest
® Migration Manager for Active Directory is an efficient, flexible, and comprehensive solution for restructuring your Active Directory. Migration Manager for
Active Directory includes cap abilities for “pruning and grafting,” directory redesign, and
Active Directory-to-Active Directory migration. In addition, Migration Manager for Active
Directory allows migrating user accounts from Active Directory to Microsoft Office 365.
With Migration Manager for Active Directory, major changes to your directory structure can be safely managed with no disruption to daily activities.
Quest
® Migration Manager for Exchange, a companion application to Migration
Manager for Active Directory, allows administrators to migrate user mailboxes, public folders, and other Exchange data from one Exchange 2000/2003/2007/2010 organization to another Exchange 2000/2003/2007/2010/2013 organization in a way that is transparent to the end-users and does not impact user productivity. In addition, Migration Manager for
Exchange allows migrating user mailboxes from an on-premises Exchange organization to
Microsoft Office 365. Migration Manager for Active Directory and Migration Manager for
Exchange are designed to be used together.
Throughout this document, “Migration Manager” applies to both Migration Manager for
Active Directory and Migration Manager for Exchange. When a particular component is referenced individually, the information applies only to that component. Unless a specific
Exchange version is meant, "Exchange" denotes Exchange 2000, Exchange 2003,
Exchange 2007, Exchange 2010, and Exchange 2013 organizations, servers, mailboxes, etc.
This guide will help you in deploying Quest Migration Manager, including planning, environment preparation and product setup.
A list of terms and product components named in this document is provided in the
Glossary.
Architecture
Migration Manager consists of several components that work together as shown in the figure below:
5
Quest Migration Manager 8.10 - Installation Guide
Active Directory Lightweight Directory Service Database
The Active Directory Lightweight Directory Service (AD LDS) or Active Directory
Application Mode (ADAM) database instance is used to store the migration project information, such as the domain pair configuration, migration and synchronization job configuration, resource processing tasks, and delegation information.
SQL Configuration Database
The SQL configuration database is used to store Exchange migration project information, such as the source and target Exchange organizations and the agent and job configuration.
6
Quest Migration Manager 8.10 - Installation Guide
Console
Migration Manager is usually installed on a separate computer (server or workstation) that is referred to as a console. Depending on your environment and requirements, you can manage your migration project using one or multiple consoles. For more information on how many consoles to have, Migration Manager for Active Directory User Guide.
When you install Migration Manager for Active Directory, the following program components are available:
Pre-migration tools, such as Trust Migration Wizard and Site Migration
Wizard
Directory Synchronization Agent, which allows for both synchronization and migration sessions
Resource processing components, including Resource Updating Manager and multiple processing wizards
When you install Migration Manager for Exchange, you get the following program components:
Directory Synchronization Agent which will allow for synchronization only. Active
Directory migration capabilities are disabled if you do not have Migration
Manager for Active Directory installed.
Exchange data synchronization and migration components, including public folder, calendar, free/busy, and mailbox synchronization agents.
If you are migrating both Active Directory and Exchange, you should install both
Migration Manager for Active Directory and Migration Manager for Exchange and thus will have both sets of components on your console.
A useful additional component is the Client Profile Updating Utility (EMWProf), which redirects Outlook profiles to the new Exchange mailboxes after the migration. This utility is installed separately.
Agents
All migration tasks are handled by agents. Agents run on remote servers and are managed from the console.
Directory synchronization and accounts migration is performed by the Directory
Synchronization Agent (DSA). The agent connects to both the source and the target domains when processing directory synchronization and migration jobs.
The DSA can run either on a separate server or on the console machine.
Depending on your environment, you can use one or several DSAs to migrate
Active Directory.
DSA configuration and activity is controlled through AD LDS or ADAM.
To avoid possible performance and synchronization speed degradation, we do not recommend you install the Directory Synchronization Agents on Exchange servers and domain controllers.
Exchange data is migrated by mailbox, public folder, calendar, and free/busy synchronization jobs. Each job involves one or more Migration Manager for
7
Quest Migration Manager 8.10 - Installation Guide
Exchange agents. Agents run on agent hosts and are controlled from the console. (For details about using agent hosts, see the Migration Manager for
Exchange User Guide.) The configuration of agents and jobs is stored in the
SQL configuration database.
Resource Updating Manager
To update distributed resources, such as end-user workstations and file and print servers,
Migration Manager uses Resource Updating Agents, which are installed either from
Resource Updating Manager or using Group Policy or SMS, or manually on each computer to be updated. The Resource Updating Agents run as services.
Resource Updating Manager uses its own service account to access computers and install or uninstall the Resource Updating Agents. This is called the Migration Manager RUM
Controller service account.
When using Resource Updating Manager, for every domain you can specify another account which will be used to set up the Resource Updating Agents to the computers of this domain and to run Resource Updating Agent service.
Statistics Portal
The Statistics Portal is an optional but extremely useful component for both Migration
Manager for Exchange and Migration Manager for Active Directory. The Statistics Portal provides statistics and reports about the progress and status of your migration project. You connect to the portal that retrieves information from the AD LDS or ADAM project partition and from the SQL configuration database.
Statistics Collection Agent
The Statistics Collection Agent is an optional Migration Manager for Exchange component used to collect statistical data on Exchange data migration progress.
Licensing
Migration Manager for Active Directory
The Migration Manager for Active Directory license specifies the maximum number of user accounts you can migrate and the maximum number of user accounts you can synchronize.
Directory synchronization agents obtain license information from the migration project partition stored in Active Directory Lightweight Directory Service (AD LDS) or Active
Directory Application Mode (ADAM). Therefore, the agents must have access to the AD
LDS or ADAM server and migration project partition. For more information, refer to the
System Requirements and Access Rights document.
Migration Manager for Exchange
The Migration Manager for Exchange license specifies the maximum number of mailboxes that you can migrate.
8
Quest Migration Manager 8.10 - Installation Guide
Because Migration Manager for Exchange uses a distributed architecture, its agents obtain all license information from a single license server. By default, a server on which the
Migration Manager is installed is used as the license server. Later you can change the license server using the Migration Manager for Exchange Options. Note that the agents must have access to the license server. For more information, refer to the System
Requirements and Access Rights document.
9
Quest Migration Manager 8.10 - Installation Guide
Preparation Checklist
The following table lists the preparation tasks for the migration process and where to find detailed information about each.
TASK DETAILS REFER TO
Check the system requirements
Prepare the source and target environments for
Active Directory migration
Before installing Migration Manager, make sure that the following servers meet the system requirements:
Source and target servers
Console
AD LDS or ADAM server
Configuration database for Exchange migration
Directory Synchronization Agent server
Migration Manager Statistics server
Any computer that does not meet the requirements should be upgraded before installing Migration Manager components.
Establish trusts
Disable SID filtering
Check host name resolution
Verify that the required ports are open on servers, routers, and firewalls
Configure Windows Server 2008/
2008 R2/2012 firewall
The System
Requirements and
Access Rights document
of this guide
Dedicated Exchange environment preparation documents.
Prepare the source and target environment for
Exchange migration
Set the required permissions
Set the required permissions for Migration
Manager accounts
The Migration Manager
Operation Accounts section of the System
Requirements and
Access Rights document
10
TASK
Make other preparations (if applicable)
Set the required permissions for Exchange migration
Quest Migration Manager 8.10 - Installation Guide
DETAILS
Set the required permissions for Active
Directory migration
REFER TO
The following sections of the System
Requirements and
Access Rights document:
Accounts and
Rights Required for Active
Directory
Migration Tasks
Appendix A: How to Set the
Required
Permissions for
Active Directory
Migration
The Accounts and Rights
Required for Exchange
Migration Tasks section of the System
Requirements and
Access Rights document
this guide
11
Quest Migration Manager 8.10 - Installation Guide
Pre-Requisites
Before installing Migration Manager, make sure your environment meets the system requirements listed in the System Requirements and Access Rights document. In particular, check the requirements for the following computers:
Migration Manager console
Domain controllers (source and target)
Source and target Exchange servers (for Migration Manager for Exchange)
Migration Manager database servers
Active Directory Application Mode server
Migration Manager for Exchange database server
Migration Manager agents’ servers
Directory Synchronization Agent server
Statistics Collection Agent server
Statistics Portal server
Migration Manager Components and Service
Accounts
As described in this guide, Migration Manager consists of several components, including:
Migration Manager console
Directory Synchronization Agent
Migration Manager for Exchange agents
Statistics Collection Agent
Statistics Portal
To perform their tasks, these components use several accounts, called service accounts or administrative accounts. Access rights and permissions required for these accounts are described in the System Requirements and Access Rights document.
12
Quest Migration Manager 8.10 - Installation Guide
Providing for Resources Availability (Active
Directory Migration)
To ensure that resources will still be available to users when they start using their target accounts and when you have cleaned up SIDHistory, permissions granted to source accounts to access the resources must be reassigned to the target accounts.
Service accounts and accounts used to run scheduled tasks must also be changed to the corresponding target accounts to ensure that services and scheduled tasks will run correctly after the source accounts are disabled.
The resources can be divided into two groups:
Distributed resources, such as end-user workstations, file and print servers, servers running IIS, scheduled tasks, and other services and applications
BackOffice servers, such as Exchange, SQL, and SMS
To make the migration transparent to users, Migration Manager for Active Directory uses a set of utilities that provide for automated resource processing to reflect the domain reconfiguration.
Administrative Access to Distributed Resources
Administrative rights over the resources are required for successful resource updating. To obtain administrative rights, do either of the following:
Add the account you are currently logged on to the console to the local
Administrators group on each computer to be updated.
By default, the Domain Admins group of the domain that the computer is a member of is a member of a computer’s local Administrators group. You will get administrative access to the computer if the account you are using to use to log on to the console is a member of the source Domain Admins group.
Use another account that is a member of a computer’s local Administrators group to connect to the computer. Establish the connection to the machine’s administrative share using a standard net use command, as follows: net use \\MachineName\Admin$ /u:DomainName\Admin_Account net use \\MachineName\C$ /u:DomainName\Admin_Account where the Admin_Account is the account that is a member of a computer’s local Administrators group.
Server Service
Server service is automatically installed when you install the File and Printer Sharing service on the computer.
Server service must be running on a computer to be updated from either Resource
Updating Manager or the command-line updating tool VMover.exe. If for some reason
(for example, due to your corporate policy), Server service is not allowed to run on the computers, you need to install or enable Server service temporarily, update the computers, and then disable or uninstall the service.
13
Quest Migration Manager 8.10 - Installation Guide
Administrative Access to BackOffice Servers
For information about the permissions required for successful Exchange, SMS, and SQL server update, please refer to Appendix A. How to Set the Required Permissions for Active
Directory Migration of the System Requirements and Access Rights document.
To learn how to set the required permissions for Microsoft BackOffice products, refer to their documentation.
Additional Pre-Installation Considerations
This section describes environment peculiarities you may need to consider before deploying Migration Manager and starting your migration project.
Active Directory Connector
If you have already started Exchange migration with the Active Directory Connector (ADC), note that Migration Manager and ADC use different object matching criteria, so ADC should be completely replaced with Migration Manager directory synchronization in the inter-org migration scenario.
Migration Manager and Microsoft Outlook
Microsoft does not recommend installing Outlook on Exchange Server, because its security extension is low for the server side. For more information, please refer to
Microsoft does not support installing Exchange Server components and Outlook on the same computer Microsoft Knowledge Base article.
Migration Manager and Backup Utilities
If any backup tools are installed on the servers where Migration Manager agents are to run, the schedule for these tools and the agents should not overlap; that is, the backup utility and the agents should be scheduled to work during different hours. In any case, the use of any backup utility together with Migration Manager should be tested in the lab before deployment in the production environment.
Providing Communication Using IP version 4 for Exchange Migration
TCP/IP version 4 (IPv4) must be installed and configured on all servers on which you are going to install Migration Manager for Exchange agents.
14
Quest Migration Manager 8.10 - Installation Guide
Preparing the Source and Target
Environments for Active Directory
Migration
The suggested preparation steps as follows:
Configuring Windows 2008/2008 R2/2012 Firewall
Number of NSPI Connections to a Windows 2008-based Domain Controller
Establishing Trusts
Trusts between the source and target domains are not required for Active Directory or
Exchange migration with Migration Manager. However, we recommend that you establish
two-way trusts between each source and target domain that will participate in migration.
If the forest functional level in both source and target forests is set to Windows 2003 or higher, you can establish forest trust between the forest root domains.
Trusts m ake it possible to resolve objects’ security identifiers (SIDs), which in turn helps to distinguish objects and check that everything is going right. Trusts also help provide coexistence of two environments, including uninterrupted access to the resources for both switched users and users not yet switched.
For more information about the restrictions that apply and possible migration scenarios without having trusts established, refer to the Migration Manager Best Practices document.
Disabling SID Filtering
By default, SID filtering is turned on.
You do not need to disable SID filtering if you have established a forest trust between source and target forest.
15
Quest Migration Manager 8.10 - Installation Guide
SID filtering for each source domain to be migrated should be turned OFF in any of the following cases:
If you have established external trusts between each source and target domain
If source accounts were previously migrated and contain SIDs from other domains in their SID history
To disable SID filtering, you must be a domain administrator.
For external trusts, use the Netdom.exe utility from Windows Server Support Tools with the following syntax:
Netdom trust TrustingDomainName /domain:TrustedDomainName /quarantine:No
/usero:domainadministratorAcct /passwordo:domainadminpwd
To enable SID filtering, set the /quarantine: command-line option to Yes.
For more information about external trusts, SID filtering, and the Netdom utility, refer to the
Microsoft article available at http://technet.microsoft.com/enus/library/cc772816(WS.10).aspx
.
Checking Host Name Resolution
DNS Name Resolution
Make sure that DNS is configured and functioning properly in your environment.
The following computers' DNS names must be successfully resolved to IP addresses from the servers running the Directory Synchronization Agents and Migration Manager console:
Source and target servers
Server on which the AD LDS or ADAM project partition is located
Server hosting the SQL configuration database
NetBIOS Name Resolution
Since the agents installed on agent hosts communicate with Exchange servers and with each other, agent hosts and Exchange servers must be able to resolve each other’s
NetBIOS names to IPv4 addresses.
In other words, each server must be able to “see” the other servers by NetBIOS.
Windows Internet Naming Service (WINS) is usually used to resolve servers’ NetBIOS names to IP addresses. If WINS is not configured in your environment, host files can be used instead.
Check the host NetBIOS name resolution and make sure that the servers’ NetBIOS names can be resolved from the console as well.
16
Quest Migration Manager 8.10 - Installation Guide
Opening the Required Ports on Servers, Routers, and Firewalls
Since the Migration Manager agents are installed and updated from the console over RPC and the agents transfer data directly between source and target servers over RPC as well,
RPC traffic must be allowed over the routers separating the subnets.
Make sure that ports 135, 137, 138, and 139 are open on the following machines:
Source and target servers
Routers separating the subnets
Firewalls
For the comprehensive list of port requirements for most of the Quest Migration
Manager components, refer to the Migration Manager
–Required Ports document.
Configuring Windows Server 2008/2008 R2/2012
Firewall
Windows Server 2008, Windows Server 2008 R2 and Windows Server 2012 have built-in firewall that is enabled by default. To migrate passwords and SIDHistory, you need to modify the firewall settings on a target domain controller and create a new inbound rule.
This is also required for proper operation of the Undo Wizard.
To create a new rule on an x86 target domain controller, run the following command (Windows Server 2008 only): netsh advfirewall firewall add rule name="Quest Migration Manager Agent" dir=in action=allow program="%SystemRoot%\System32\AelAgentMS.exe"
To create a new rule on an x64 target domain controller, run the following command: netsh advfirewall firewall add rule name="Quest Migration Manager Agent" dir=in action=allow program="%SystemRoot%\System32\AelAgentMS64.exe"
Alternatively, you can create a new rule using the New Inbound Rule Wizard. To run the wizard:
1. Open the Server Manager console on a target domain controller.
2. Navigate to Configuration | Windows Firewall with Advanced security |
Inbound Rules in the console tree.
3. Click
New Rule…
In case of two-way directory synchronization, you should perform the same actions on the source domain controller.
17
Quest Migration Manager 8.10 - Installation Guide
Number of NSPI Connections to a Windows 2008based Domain Controller
A Name Service Provider Interface (NSPI) connection from a MAPI client to a Windows
Server 2008-based domain controller may fail with the following error code that is returned from the server: «MAPI_E_LOGON_FAILED».
This behavior occurs because Windows Server 2008 only allows for a default maximum of
50 concurrent NSPI connections per user to any domain controller. Additional NSPI connections are rejected with a MAPI_E_LOGON_FAILED error code.
Note Windows Server 2003 and earlier versions of Microsoft Windows operating systems do not exhibit this behavior. The change of behavior in Windows Server 2008 is intended to protect domain controllers against clients that open too many NSPI connections without then closing the connections. Too many connections such as these can result in resource depletion.
For more information about how to modify registry settings to allow for additional NSPI connections, see the following Microsoft KB article: http://support.microsoft.com/kb/949469.
18
Quest Migration Manager 8.10 - Installation Guide
Installing Migration Manager
To install Migration Manager, either click Quest Migration Manager and its components on the CD menu or start the Suite\AeCDSuiteLauncher.exe setup program, and then follow the wizard’s instructions.
To install Migration Manager:
1. When prompted, specify your name and company. Click Licenses to verify your license information in the dialog displayed: browse for a valid license file, and then click Close.
2. Next, on the Select Features step, select the components you want to install and specify the installation folder.
3. On the next step, you are prompted to select the product installation scenario.
Possible options are Express or Advanced.
Express means that setup will do the following:
Install all the components that are permitted by the license file.
Install all other required components, such as the AD LDS or ADAM instance, SQL Server or SQL Server Express instance (for Exchange migrations only), and the Directory Synchronization Agent.
Configure the project.
If IIS is installed on the computer, Statistics Portal will be automatically installed and configured as well.
Advanced is recommended if you plan to manually install AD LDS or ADAM,
SQL Server or SQL Server Express (for Exchange migrations only), and the
Directory Synchronization Agent, as well as configure the project by running the
Open Project Wizard (described in the Opening a Migration Project topic). Only
the basic product components (selected in Select Features step) will be installed automatically.
When selecting the setup scenario, consider the following:
By default, SQL Server Express is installed with only Windows (AD-integrated) authentication allowed; however, Statistics Portal required basic SQL authentication. To provide for SQL authentication method, you can do either of the following:
Use the Express setup scenario (proper configuration will be applied automatically).
After running the Advanced setup, install SQL Server Express using the special installation wizard from Migration Manager CD Autorun, and then use the
Microsoft SQL Server Management tools (Enterprise Manager), or edit the registry as described in Microsoft Knowledge Base article 319930 at http://support.microsoft.com/kb/319930/.
If you select the Advanced setup scenario, you will be taken to step 7 of this procedure.
19
Quest Migration Manager 8.10 - Installation Guide
4. On the Set Account for ADAM Access step, specify the auxiliary account that various Migration Manager components will use to access the AD LDS or ADAM database.
This account does not require any particular rights in the domain; ordinary domain user rights are sufficient. However, this account must be a member of the computer local Administrators group on the computer running the Migration
Manager console. Note that this account will be granted Full Admin rights in the project database.
5. On the MSDE setup step, specify the password for the sa account that will be used to install and configure the local SQL Server database.
6. Next, the setup checks for third-party software required for Migration Manager
(for example, Microsoft Message Queuing). If some required components are missing, setup will notify you and attempt to install these components from the installation CD. To install these components automatically, click Next; alternatively, you can install them manually and after that restart the setup program.
7. After all the required components are installed, the setup wizard is ready to install the features you have selected (and configure the product if the Express setup scenario is running). Click Next and wait for the installation to complete.
Downloading MAPI CDO
Migration Manager also requires version 08.03.0.8309.000 or later of Microsoft Exchange
Server MAPI Client and Collaboration Data Objects 1.2.1 to be installed on the following computers:
Where Migration Manager agents will run (that is, Exchange 2007 and 2010
Servers and agent hosts)
Where the Migration Manager console is installed
Since the MAPI CDO setup package is not available for distribution, you should download it from the Microsoft Web site. At the moment of the last document update, the download link is http://www.microsoft.com/en-us/download/details.aspx?id=36771 .
This package cannot be installed on a system on which any version of Microsoft
Outlook or Microsoft Exchange Server 2003 or earlier is installed.
20
Quest Migration Manager 8.10 - Installation Guide
Opening a Migration Project
In most cases you will need just one Migration Manager project for your whole migration, no matter how many domains you have. Normally, you would use a separate project only for lab testing before you start migration in the production environment.
If you plan to migrate objects from Active Directory to Microsoft Office 365 using
Migration Manager, you need to create a separate migration project in Migration
Manager for Active Directory (Microsoft Office 365) console. You will be prompted for a name for the project and AD LDS instance to store its data. For more information on migration to Microsoft Office 365 scenario, refer to the Migrating To Microsoft Office 365 document included in the Migration Manager documentation set.
The Open Project Wizard will help you with configuring the migration project and all its components: the AD LDS or ADAM database, the SQL Server database (for Exchange migrations only), and Statistics Portal.
These configuration steps are required if you installed Migration Manager using
Advanced mode.
If you used Express setup mode, AD LDS or ADAM was installed and configured automatically.
The wizard can be used to start a new project, connect to an existing project, or change any settings of the current project.
When you run Migration Manager for the very first time, the Open Project Wizard is started automatically. To start the Open Project Wizard for subsequent uses, in Migration
Manager console, select File | Open Project.
The following steps are presented in the Open Project Wizard to help you configure your migration project.
Configuring AD LDS or ADAM Database
If you installed Migration Manager using Advanced mode, you need to install and configure Active Directory Lightweight Directory Service (AD LDS) or Active Directory
Application Mode (ADAM) manually. AD LDS and ADAM can be found on the Migration
Manager CD and on Microsoft’s Web site
If Express setup mode was used, AD LDS or ADAM was installed and configured automatically.
21
Quest Migration Manager 8.10 - Installation Guide
Migration Manager uses Microsoft Active Directory Lightweight Directory Service (AD LDS) or Active Directory Application Mode (ADAM) to store its project data.
On the Select Project | Configure ADAM/ADLDS Project page of the wizard, configure the following settings:
ADAM or ADLDS server
—Specify the name of the server on which AD LDS or ADAM is installed. Migration Manager will try to connect to the server by LDAP and locate the AD
LDS or ADAM instance.
Port
—The port number of the AD LDS or ADAM instance. By default, AD LDS or ADAM uses port 389. The port number might be different if AD LDS or ADAM is installed on a domain controller or this is not the first AD LDS or ADAM instance on the server.
Select a project
—For each new project, Migration Manager automatically creates a partition in the AD LDS or ADAM instance you specify. You can either connect to the existing project or create a new one:
To create a new project, select the Create a new project option and type a name for the project. Migration Manager will create an AD LDS or ADAM partition for the new project and, if required, extend the AD LDS or ADAM schema.
To connect to an existing project, select the Use existing project option. If the
AD LDS or ADAM database already has Migration Manager projects in it, select the necessary project from the Use existing project dropdown list. Alternatively, click the Retrieve Projects button. Migration Manager will connect to AD LDS or
ADAM and retrieve the list of its projects already in the database.
Setting Auxiliary Account
The AD LDS or ADAM database is the central configuration storage for the migration project. On this step of the wizard, you can specify the auxiliary account that various
Migration Manager components will use to access the AD LDS or ADAM database.
Username
—Specify the username for AD LDS or ADAM access. This can be any account that can be successfully resolved on the console, AD LDS or ADAM server, computers from which the resource updating will be performed, and other computers on which
Migration Manager components will run.
Password
—Type the password for the account.
This account must be a member of the computer local Administrators group on the computer running the Migration Manager console. No particular rights in the domain are required; ordinary domain user rights are sufficient.
Consider that the account will be granted Full Admin rights in the project database.
Configuring SQL/MSDE Database
This step applies to Migration Manager for Exchange only.
22
Quest Migration Manager 8.10 - Installation Guide
An SQL Server database is required to store information related to Exchange migration.
SQL server
—Specify the name of the SQL server and instance to be used to store the
Exchange migration information, for example: SQLSERVER\QMMINSTANCE.
Authentication
—Specify the authentication type and credentials to access the server:
Use Windows authentication
—If this option is selected, Migration Manager will use the logged-in user credentials to connect to the database.
Use SQL Server authentication
—If this option is selected, Migration Manager will use a SQL Server account to connect to the database. Specify the SQL
Server account and password to be used to access the database.
Select database
—You can either connect to an existing database or create a new one:
If the SQL Server or SQL Server Express installation already has a database containing the Exchange migration project data, you can select the Use existing
database option. Select the database from the list, or click the Retrieve
Database List button to have Migration Manager connect to the server and retrieve the list of databases.
You should not share the Migration Manager database with other applications or between different projects.
Alternatively, select the Create a new database option and type the database name. Migration Manager will connect to the SQL Server you specified and create the database.
Backing Up Transaction Log
The SQL configuration database for Migration Manager for Exchange projects uses the
full recovery model. It causes transaction log file to eventually grow in size. To limit that growth, you need to periodically backup transaction log which also results in log file truncation. Prior to making a first log backup, you must perform at least one full database backup.
The recommended approach to backing up a transaction log is to configure an SQL Server
Agent job which automatically performs scheduled log backup. It should use the following
Transact-SQL query where database name and target paths are changed according to your environment:
BACKUP DATABASE [qmmexcfgdb]
TO DISK='C:\mydbbackups\qmmexcfgdb.bak'
GO
BACKUP LOG [qmmexcfgdb]
TO DISK='C:\mydbbackups\qmmexcfgdb.trn'
GO
For more information on transaction log backup, refer to http://social.technet.microsoft.com/Search/en-
23
Quest Migration Manager 8.10 - Installation Guide
US/sqlserver?query=BACKUP%20(Transact-
SQL)%20log_Truncation&Refinement=30&ac=4 .
Configuring Statistics Portal
Statistics Portal is the Migration Manager component that provides online migration statistics and reporting. Once you have installed Statistics Portal on an IIS server in your network, you should configure it as described below.
Configure Statistics Portal
—Select this option to make the Open Project Wizard connect to the portal and configure it to be used with the migration project. Type the URL to the portal in the URL field. In most cases (if the portal is installed in the same forest as the console), the wizard is able to retrieve the URL from the Active Directory. The URL might look like the following: http://IISSERVER:80/Migration.
Use these credentials for portal configuration
—Specify the credentials that the wizard will use to configure the portal. The account should be a member of local Administrators group on the IIS server on which the portal is installed.
Credentials for Exchange statistics retrieval
—Specify the SQL username and password that the portal will use to retrieve the Exchange migration data for the project from the SQL configuration database. The SQL login you specify to connect to the configuration database must at least have the db_datareader role on the database.
If you need to enable SQL authentication after installation, use the Microsoft SQL
Server Management tools (Enterprise Manager) or edit the registry as described in
Microsoft Knowledge Base article 319930 at http://support.microsoft.com/kb/319930/.
To learn about required Statistics Portal settings, refer to the System Requirements and
Access Rights document.
For security reasons, all network protocols may be disabled by default in SQL Server
2005 and SQL Server Express 2005 or later, which causes trouble with connecting to a project. For details on enabling the network protocols, refer to SQL Server documentation.
Do not configure statistics portal
—Select this option if you do not need reporting.
24
Quest Migration Manager 8.10 - Installation Guide
Analyzing the Environment
Before you start directory migration, you should analyze the existing directory environment. This includes identifying required hardware and software upgrades, possible naming conflicts in the case of directory merges, and for an inter-forest migration, comparing and unifying the source and target forest schemas. You can use Quest
Reporter to obtain detailed information about the existing Active Directory configuration, hardware and software inventory, etc.
Prior to starting Exchange migration, you should analyze the existing Exchange organizations, checking whether the source and target objects and accounts involved in migration process meet the requirements stated by the System Requirements and Access
Rights document. In particular, appropriate accounts must have sufficient rights to access servers and other objects involved in migration; the software required for agents' operation must be installed on those servers, and so on. You can use Migration Configuration
Analyzer, which is shipped within Migration Manager for Exchange Resource Kit, to perform some of these checks automatically and to create a detailed report on check result. Note, however, that current version of this tool allows you to perform automatically the most operation-critical checks only (i.e., those listed in the Migration Configuration
Analyzer section of the Migration Manager for Exchange Resource Kit User Guide); when the automatic check is successfully completed, the rest of requirements must be checked manually. For details, refer to the System Requirements and Access Rights document and the Migration Manager for Exchange Resource Kit User Guide.
25
Quest Migration Manager 8.10 - Installation Guide
Glossary
The following terms related to migration process are used throughout this document:
Migration: The common term used to describe the following types of migration activities:
Account migration: When user accounts and other Active Directory objects such as groups, contacts, and computers in the source domain are created in the target domain. Account migration is usually performed in portions, by migration sessions. During a migration session you can specify to create an organizational unit (OU) structure on target similar to that on the source and place the migrated objects there. You also can delegate rights to perform account migration from certain organizational units to other administrators.
Exchange data migration: When public folder and mailbox contents are transferred from the source to the target environment and synchronized during the co-existence period. Calendar and free/busy information is also synchronized to provide for transparent user collaboration.
Source servers: The domain controllers or Exchange servers from which the Active
Directory objects or messaging system are migrated.
Target servers: The domain controllers or Exchange servers to which the Active Directory objects or messaging system are migrated.
Directory synchronization: The o ngoing synchronization of objects’ properties (such as passwords and memberships) during the co-existence period of source and target environments. Directory synchronization is handled by the Directory Synchronization
Agent. Although it is possible to make the Directory Synchronization Agent create accounts on the target, this option is normally used to populate the source and target
Global Address Lists when two or more organizations are merged. In this case the
Directory Synchronization Agent is configured to create disabled mailbox-enabled accounts on target and store them in the specified staging OUs, which are temporary.
Migration sessions are later used to migrate source accounts, merge them with DSAcreated accounts on the target, and move them from the staging OUs to the destination
OUs.
Resources or distributed resources: User workstations and servers.
Resource update (resource processing): To ensure that resources will still be available to users when they start using their target accounts and after you have cleaned up
SIDHistory, the permissions granted to source accounts for access to the resources must be re-assigned to the target accounts. This means that the ACLs of all the resources in the network need to be processed to refer to the new SIDs. Resource update (also referred to as resource processing) is the process of re-assigning rights and permissions from source
26
Quest Migration Manager 8.10 - Installation Guide to target accounts. Resource update is also referred to as translation or re-ACLing by the industry.
User switch: This is when a user starts authenticating in the target domain (logs on to the target domain). Usually, this happens right after the user's workstation is moved to the target domain.
Mailbox switch: Before a mailbox switch, all new mail is delivered to the source user mailbox and redirection is configured for the corresponding target mailbox. After the mailbox switch, all new mail is delivered to the target mailbox, redirection on target mailbox is disabled, and redirection is configured on the source mailbox using the Migration
Manager redirection technology.
Cleanup: This is a post-migration activity. After you have successfully migrated Active
Directory and Exchange data, switched users to log on to the target domain, and updated all resources for them, you can safely clean up legacy account permissions from resources and SIDHistory attributes of the migrated objects, disable source accounts, and decommission the source environment.
27
Quest Migration Manager 8.10 - Installation Guide
About Quest Software, Inc.
Established in 1987, Quest Software (Nasdaq: QSFT) provides simple and innovative IT management solutions that enable more than 100,000 global customers to save time and money across physical and virtual environments. Quest products solve complex IT challenges ranging from database management , data protection , identity and access management , monitoring , user workspace management to Windows management . For more information, visit www.quest.com
.
Contacting Quest Software
Email [email protected]
Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web site www.quest.com
Refer to our Web site for regional and international office information.
Contacting Quest Support
Quest Support is available to customers who have a trial version of a Quest product or who have purchased a
Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to our
Support Portal at www.quest.com/support
From our Support Portal, you can do the following:
Retrieve thousands of solutions from our online Knowledge Base
Download the latest releases and service packs
Create, update and review Support cases
View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies and procedures. The guide is available at: www.quest.com/support .
28
Quest Migration Manager 8.10 - Installation Guide
Third Party Contributions
Quest
® Migration Manager version 8.10 contains some third party components (listed below). Copies of their licenses may be found at http://www.quest.com/legal/third-party-licenses.aspx
.
COMPONENT LICENSE OR ACKNOWLEDGEMENT
Boost 1.34.1
Boost 1.46.1
HTMLayout 1.0
Loki 0.1.4
Loki 0.1.6
NABU-library 1.0*
Boost 1.0
Boost 1.0
This Application (or Component) uses HTMLayout Component, copyright
Terra Informatica Software, Inc. (http://terrainformatica.com).
MIT
MIT
GNU LGPL Version 3, 29 June 2007
Newtonsoft.Json.dll 3.5.0.0 MIT
ZLib 1.1.4 zlib 1.2.3 zlib 1.2.7 Portions copyright 1995-2012 Jean-loup Gailly and Mark Adler
TinyXml 2.2.1
7-ZIP 9.20
This product contains portions of the PAWN scripting software (formerly known as SMALL).
7-ZIP 9.20
* a copy of the source code for this component is available at http://rc.quest.com
.
Boost 1.34.1: License Text
Boost Software License - Version 1.0 - August 17th, 2003
Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:
The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machineexecutable object code generated by a source language processor.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT
HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER
29
Quest Migration Manager 8.10 - Installation Guide
LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Boost 1.46.1: License Text
Boost Software License - Version 1.0 - August 17th, 2003
Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:
The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machineexecutable object code generated by a source language processor.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT
HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER
LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Loki 0.1.4: License Text
Copyright (c)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Loki 0.1.6: License Text
Copyright (c)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
30
Quest Migration Manager 8.10 - Installation Guide
NABU-library 1.0: License Text
GNU LESSER GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc.
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public
License, supplemented by the additional permissions listed below.
0. Additional Definitions.
As used herein, "this License" refers to version 3 of the GNU Lesser
General Public License, and the "GNU GPL" refers to version 3 of the GNU
General Public License.
"The Library" refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.
An "Application" is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library.
Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.
A "Combined Work" is a work produced by combining or linking an
Application with the Library. The particular version of the Library with which the Combined Work was made is also called the "Linked
Version".
The "Minimal Corresponding Source" for a Combined Work means the
Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.
The "Corresponding Application Code" for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the
Application, but excluding the System Libraries of the Combined Work.
1. Exception to Section 3 of the GNU GPL.
You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.
2. Conveying Modified Versions.
If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version: a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.
3. Object Code Incorporating Material from Library Header Files.
31
Quest Migration Manager 8.10 - Installation Guide
The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates
(ten or fewer lines in length), you do both of the following: a) Give prominent notice with each copy of the object code that the
Library is used in it and that the Library and its use are covered by this License. b) Accompany the object code with a copy of the GNU GPL and this license document.
4. Combined Works.
You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following: a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the Combined Work with a copy of the GNU GPL and this license document. c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document. d) Do one of the following:
0) Convey the Minimal Corresponding Source under the terms of this
License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying
Corresponding Source.
1) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked
Version. e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the
GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the
Combined Work produced by recombining or relinking the
Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application
Code. If you use option 4d1, you must provide the Installation
Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.)
5. Combined Libraries.
You may place library facilities that are a work based on the
32
Quest Migration Manager 8.10 - Installation Guide
Library side by side in a single library together with other library facilities that are not Applications and are not covered by this
License, and convey such a combined library under terms of your choice, if you do both of the following: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License. b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
6. Revised Versions of the GNU Lesser General Public License.
The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the
Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser
General Public License, you may choose any version of the GNU Lesser
General Public License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the
Library.
Newtonsoft.Json.dll 3.5.0.0: License Text
Copyright (c)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
ZLib 1.1.4: License Text
License
/* zlib.h -- interface of the 'zlib' general purpose compression library version 1.2.3, July 18th, 2005
Copyright (C) 1995-2005 Jean-loup Gailly and Mark Adler
33
Quest Migration Manager 8.10 - Installation Guide
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.
Jean-loup Gailly [email protected]
Mark Adler [email protected]
*/
7-ZIP 9.20: License Text
Licenses for files are:
1) 7z.dll: GNU LGPL + unRAR restriction
2) All other files: GNU LGPL
The GNU LGPL + unRAR restriction means that you must follow both
GNU LGPL rules and unRAR restriction rules.
Note:
You can use 7-Zip on any computer, including a computer in a commercial organization. You don't need to register or pay for 7-Zip.
GNU LGPL information
--------------------
This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You can receive a copy of the GNU Lesser General Public License from http://www.gnu.org/ unRAR restriction
-----------------
The decompression engine for RAR archives was developed using source code of unRAR program.
All copyrights to original unRAR code are owned by Alexander Roshal.
The license for original unRAR code has the following restriction:
The unRAR sources cannot be used to re-create the RAR compression algorithm, which is proprietary. Distribution of modified unRAR sources in separate form or as a part of other software is permitted, provided that it is clearly stated in the documentation and source comments that the code may not be used to develop a RAR (WinRAR) compatible archiver.
--
Igor Pavlov
34
ดาวน์โหลด
ลิงก์สาธารณะได้รับการอัปเดตแล้ว
ลิงก์สาธารณะไปยังแชทของคุณได้รับการอัปเดตแล้ว You may view and manage your chat links after registration here.
ลิงก์สาธารณะของเอกสาร
โฆษณา
