8.6 Migrating to Exchange 2010

(1)

(2)

© 2010 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.

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.

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 e-mail: [email protected]

Refer to our Web site (www.quest.com) for regional and international office information.

TRADEMARKS

AccessManager, Active Administrator, ActiveDL, ActiveGroups, ActiveRoles, AKONIX, Benchmark Factory, Big Brother, BOX & WAVE Design, BridgeAccess, BridgeAutoEscalate, BridgeSearch, BridgeTrak,

ChangeAuditor, ChangeManager, CI Discovery, DataFactory, Defender, Deploy the Whole Desktop, Desktop Authority, Directory Analyzer, DirectoryExpert, DS Analyzer, DS Expert, Embargo, Enterprise Security Explorer, Enterprise Security Reporter, File System Auditor, Foglight, GPOAdmin, Help Desk Authority, InstantAssist , IntelliProfile, InTrust, iToken, J.CLASS and Design, JClass, Jint, JProbe, Kemma Software, Knowledge Xpert and Design, LiteSpeed, LiveReorg, LogAdmin, MessageStats, Move Mailbox Manager, MultSess, NBSpool, NetBase, NETPRO, PASSGO, PassGo Technologies (and design), Password Reset Manager, Patch Authority, PerformaSure, POINT, CLICK, DONE!, PowerGUI, Privilege Authority, Q.DESIGNER and Design, Quest, Quest Central, Quest Software, Quest Software and Design, Quest Software logo, ReportAdmin, RestoreAdmin, SCRIPTLOGIC, SCRIPTLOGIC (and Design), Secure Copy, Security Explorer, Security Lifecycle Map, SelfServiceAdmin, SharePlex, Spotlight, SQL Navigator, SQL TURBO, SQL TURBO and Design, SQL Watch, SQLAB, STAT, StealthCollect, T.O.A.D, Tag and Follow, TOAD, TOAD WORLD, vAutomator, vConverter, vEcoShell, VESI, vFoglight, VINTELA, VIZIONCORE, Vizioncore Automation Suite, Vizioncore vEssentials, vMigrator, vRanger, vSpotlight, vToad, WebDefender, Webthority, XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. 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.

(3)

C

ONTENTS

About This Guide ... 3

Overview ... 3

Conventions ... 3

Introduction... 4

Security Configuration... 5

Access to Exchange 2010 Mailboxes... 5

Running Cmdlets to Move Mailboxes... 6

Making Public Folders Mail-Enabled ... 7

Using the Exchange Processing Wizard ... 7

Processing Mailboxes and Public Folders... 7

Processing Mailbox and Public Folder Contents... 8

Before You Begin ... 9

Create Migration Administrator Mailboxes ... 9

Install the Microsoft Exchange Server Messaging API ... 9

Disable RPC Encryption on Exchange Servers ... 10

Avoid Incompatible Mailboxes... 10

Migration Steps... 11

Register Target Exchange 2010 Organization ... 11

Public Folder and Free/Busy Synchronization ... 12

Mailbox Migration and Calendar Synchronization... 12

About Quest Software, Inc. ... 13

Contacting Quest Software... 13

Contacting Quest Support ... 13

Third Party Contributions... 14

Boost 1.0 License Agreement ... 14

Loki 0.1.4 License Agreement... 14

Loki 0.1.6 License Agreement... 15

(4)

(5)

About This Guide

Overview

This document has been prepared to assist you in becoming familiar with Quest Migration Manager. This guide contains the information required for migration to an Exchange 2010 environment using 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 cross-references.

ELEMENT CONVENTION

Select This word refers to actions such as choosing or highlighting various interface elements, such as files and radio buttons.

Bolded text Interface elements that appear in Quest products, such as menus and commands.

Italic text Used for comments.

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.

(6)

Migration Manager 8.6

4

Introduction

This is a companion document for the Migration Manager for Exchange User Guide. It does not supplant or duplicate the User Guide, but contains information that applies specifically to projects involving migration to Exchange 2010.

The procedures described here are required for successful migration to an

(7)

Security Configuration

This section contains information about the rights and permissions necessary to perform mailbox migration to the target Exchange Server 2010 organization.

First of all, refer to the Quest Migration Manager System Requirements and Access

Rights document to make sure that your environment meets all the requirements to

perform the migration process.

Before you migrate mailboxes to Exchange Server 2010, ensure that the Exchange account (the account used for Exchange migration) has sufficient privileges to do the following:

• Access every mailbox within the Exchange 2010 organization • Run the cmdlets performing Move mailbox operations

• Run the Enable-MailPublicFolder cmdlet to make public folders mail-enabled

Access to Exchange 2010 Mailboxes

For every mailbox database and its associated public folder database that is involved in migration, take the following steps:

1. In the ADSIEdit snap-in, open the Active Directory configuration partition and browse to CN=<DatabaseName>,CN=Databases,CN=Exchange

Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=<ExchangeOrganizationName>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<...>,DC=<...>

2. Add the Exchange account to the CN=<DatabaseName> object and give it the Receive as permission.

3. Click Advanced and make sure that the permissions are set to This object and all child (descendant) objects.

4. In the ADSIEdit snap-in, browse to CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=<ExchangeOrganizationName>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<…>,DC=<…>

(8)

6. Click Advanced and make sure that the permissions are set to This object and all child (descendant) objects.

7. Wait 2 hours, or restart the Information Store service twice on every target Exchange 2010 server that is involved in the migration and hosts the Mailbox role. The interval between restarts does not matter.

After that, your Exchange account will have access to every Exchange 2010 mailbox in every mailbox database in your organization.

You can grant the same permissions by running the following cmdlet in Exchange Management Shell:

Add-ADPermission -Identity "CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative

Groups,CN=<your_org_name>,CN=Microsoft

Exchange,CN=Services,CN=Configuration,DC=<your_domain>" -User

<user_name> -AccessRights GenericAll -ExtendedRights Send-As,Receive-As

In some cases, the inherited Receive as permission may not work. If the Exchange account is granted the Read and Receive as permissions on the

CN=Databases object and these permissions are set to This object and all child (descendant) objects, the Exchange account may not have full access to all

mailboxes in the organization. To resolve this problem, you should explicitly set the “Receive-as” permission in the properties of Mailbox Database.

Running Cmdlets to Move Mailboxes

To perform Move mailbox operations, your Exchange account needs to be assigned permissions to run the following cmdlets:

• New-MoveRequest • Get-MoveRequest • Remove-MoveRequest • Get-MoveRequestStatistics

To assign these permissions, add this account to the Recipient Management role group in the target Exchange 2010 organization, as follows:

1. Open the Active Directory Users and Computers MMC snap-in. 2. Select the Microsoft Exchange Security Groups node.

3. In the right pane, open the properties of the Recipient Management group. 4. On the Members tab, add the account.

(9)

Making Public Folders Mail-Enabled

If a public folder is mail-enabled in the source organization, the Public Folder Target Agent needs to be able to make it mail-enabled in the target organization as well. To achieve this, assign your Exchange account permissions to run the

Enable-MailPublicFolder cmdlet, as follows:

1. Add this account to the Public Folder Management role group in the target Exchange 2010 organization.

2. Give the account the Full Control permission on the CN=<ExchangeOrganizationName>,CN=Microsoft

Exchange,CN=Services,CN=Configuration,DC=<...>,DC=<...> container.

Using the Exchange Processing Wizard

This section is relevant only for scenarios where Exchange migration is part of Active Directory migration.

Processing Mailboxes and Public Folders

OPERATION RIGHTS AND PERMISSIONS WHERE SPECIFIED

Access to mailboxes and public folders

The account should be a member of the Domain Admins or Enterprise Admins group.

Alternatively, if you want to avoid granting such broad privileges, make the account a member of the Organization

Management and Public Folder Management roles.

To assign the roles to the account (<User>), run the following commands in the Exchange Management Shell:

Add-RoleGroupMember "Organization Management" -Member <User>

Add-RoleGroupMember "Public Folder Management" -Member <User>

Exchange impersonation (step 1)

The

ApplicationImpersonation

role enables the Exchange processing user account to impersonate other users.

To enable the account (<User>) to impersonate all users in an organization, run the following in the Exchange Management Shell:

New-ManagementRoleAssignment –Name <AssignmentName> -Role

ApplicationImpersonation –User <User>

See

(10)

8

Exchange impersonation (step 2)

In addition to enabling Exchange impersonation for an account, give it the necessary access privileges by granting the

ms-Exch-EPI-May-Impersonate

extended right.

To give the account (<User>) the right to impersonate all users on all Client Access Servers, run the following in the Exchange Management Shell:

Set-ExchangeServer | where {$_.IsClientAccessServer -eq $TRUE} | ForEach-Object {Add-ADPermission -Identity

$_.distinguishedname -User (Get-User -Identity <(Get-User> | select-object).identity -extendedRight ms-Exch-EPI-Impersonation}

To give the account (<User>) permission to impersonate all accounts on an all

MailboxDatabases, run the following in the Exchange Management Shell:

Set-MailboxDatabase | ForEach-Object {Add-ADPermission -Identity $_.DistinguishedName -User <User> -ExtendedRights

ms-Exch-EPI-Impersonate}

See

http://msdn.microsoft.com/en-us/library/bb204095%28EXCHG.80%29.aspx

for more details related to granting Exchange impersonation rights, such as narrowing the scope of accounts, servers and databases.

Processing Mailbox and Public Folder Contents

Message

sending Send As extended right. Run the following in the Exchange Management Shell:

Add-ADPermission "Mailbox" -User <User> -Extendedrights "Send As" Message

processing in other users' mailboxes

Full mailbox access rights. Run the following in the Exchange Management Shell:

AddMailboxPermission "Mailbox" -User <-User> -AccessRights

(11)

Before You Begin

This section includes the steps you need to take to prepare for migration to an Exchange 2010 organization.

The Migration Manager console shows only those servers from the target Exchange 2010 organization that host the Mailbox role.

Create Migration Administrator Mailboxes

Migration administrator mailboxes are required for mailbox, calendar, public folder and free/busy synchronization.

The Migration Manager agents will access the migrated mailboxes and public folders through an administrator mailbox that you specify. The System Attendant mailbox, which Migration Manager uses for migration to Exchange versions up to 2007, was deprecated in Exchange 2010. This means that you should create the administrator mailbox manually for every Exchange Server 2010 and specify this mailbox in the Exchange Server properties in the Migration Manager console.

Synchronization of mailboxes that are hosted on Exchange 2010 servers uses the specialized Exchange Attendant component of the Migration Manager suite. During installation of shared components, Exchange Attendant is registered as a service that starts automatically.

Install the Microsoft Exchange Server Messaging API

Migration Manager also requires Microsoft Exchange Server Messaging API client and the latest version of Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 to be installed on the computers where Migration Manager agents will run. Since the MAPI CDO setup package is not available for distribution, you should

download it from the Microsoft Web site. For the download link, please see Microsoft Knowledge Base article 171440.

(12)

10

Disable RPC Encryption on Exchange Servers

The EncryptionRequired parameter specifies whether connections to the

Exchange 2010 are required to be encrypted. The Exchange RPC Client Access service rejects unencrypted connections if this parameter is set to $true.

During the migration, agents that are installed on source Exchange Server 2003 require connection to Exchange 2010 to perform some operations. Migration Manager agents create unencrypted connections, so you need to remove the RPC encryption

requirement to log on to the target Exchange Server 2010.

To disable the RPC encryption requirement, use the Exchange Management Shell to run the following command on all Exchange 2010 servers with mailbox databases and public folder databases that are associated with mailbox databases as well as on all Exchange 2010 servers with the Client Access Server (CAS) role installed:

Set-RpcClientAccess –Server <Exchange 2010 Server Name> – EncryptionRequired $false

Avoid Incompatible Mailboxes

Exchange 2010 may create unrequested empty mailboxes for mailbox-enabled users that have no mailboxes. This behavior was not present in previous Exchange versions. The resulting mailboxes are incompatible with Migration Manager and cannot be used by during Exchange migration. Instead of relying on Exchange to create mailboxes, you should delete such automatically created mailboxes and use mailbox creation settings in your migration project. Mailboxes created by Migration Manager are fully supported. However, new Exchange 2010 mailboxes should not be deleted indiscriminately, because valid target mailboxes might be deleted in the process. The

ForbidDelMailbox2010 parameter has been introduced to facilitate cleanup.

Previously, the ForbidDelMailbox parameter in the mail transfer agent's INI file was the only setting responsible for preserving or removing target mailboxes whose

MailboxInfo parameter did not match the same parameter in the source mailbox. The ForbidDelMailbox parameter is a precaution against the deletion of mailboxes that are in actual use in the target environment. By default, it is set to 1 so that non-matched target mailboxes are not deleted.

The additional ForbidDelMailbox2010 parameter affects only Exchange 2010 target mailboxes. This parameter can have one of the following values:

• 0

Delete the new mailbox, but only if it is empty. • 1

Let the ForbidDelMailbox parameter define what to do with the new mailbox, but only if the mailbox is empty. Otherwise, do not delete the mailbox.

(13)

Migration Steps

Currently, Exchange 2010 is supported only as the migration destination, not the source.

In this release, the implementation of Exchange Server 2010 support uses the same product architecture as for migration to previous versions of Exchange Server. The main difference in migration to an Exchange 2010 organization is support for the database availability group (DAG) feature implemented in Exchange Server 2010.

A database availability group is the base component of the high availability and site resilience framework built into Microsoft Exchange Server 2010. A DAG is a group of up to 16 Mailbox servers that host a set of databases and provide automatic database-level recovery from failures that affect individual servers or databases.

Migration Manager for Exchange Console and migration agents detect automatically if there are mailbox databases with copies on other Exchange servers included in a DAG. Procedures such as job creation, administrator mailbox selection for all types of

synchronization, and copying of mailbox content to the target mailbox database depend on the Exchange 2010 server (included in DAG) where the mailbox database is

mounted.

In an Exchange 2010 organization, the same set of recipients is displayed in the Migration Manager console for all active and passive database copies.

This chapter does not present the migration steps in a sequence. Instead, it contains Exchange 2010-specific additions to the Migration Manager for Exchange User Guide.

Register Target Exchange 2010 Organization

This section complements the Registering Source and Target Organizations section in the Migration Manager for Exchange User Guide.

If the target Exchange 2010 organization is added to the Migration Manager console, you can view all database copies for every Exchange Server 2010 in the tree-view irrespective of whether this server hosts an active or passive copy of the mailbox database. You can see the status (active or passive) for each copy.

(14)

Public Folder and Free/Busy Synchronization

This section complements the Public Folder Synchronization and Free/Busy

Synchronization sections in the Migration Manager for Exchange User Guide.

If you create a public folder or free/busy synchronization job, specify the administrator mailbox for the Exchange Server 2010. As an administrator mailbox you should specify the mailbox that is hosted on any mailbox database which has a copy on the target Exchange Server 2010. This mailbox database must be associated with the public folder database hosted on the target Exchange Server 2010.

During public folder migration, if there are identically named folders in the source and target Exchange environment, then a pair of folders with the same name will appear in the target environment. Such folders are not duplicates and should not be deleted. If you encounter identically named folders after migration, consider merging them.

Mailbox Migration and Calendar Synchronization

This section complements the Mailbox Migration and Calendar Synchronization sections in the Migration Manager for Exchange User Guide.

When you create the mailbox or calendar synchronization job with the target

Exchange 2010 server specified, you can select only mailbox database that has an active copy on this Exchange 2010 server. The information about active database copies is stored in the Migration Manager console and updated during every manual refresh of the Exchange 2010 server. If the collection is created within the Mailbox or Calendar Synchronization job with certain Mailbox Database, other collections with this Mailbox Database can be created only within this job even if the active copy of this database moves to another Exchange server after creation of the first collection.

By default, Mailbox Synchronization agents process mailboxes from the target Mailbox Database only if the active copy of this database is located on the target Exchange 2010 server. If the active copy of the Mailbox Database is moved to another Exchange 2010 server from the database availability group, agents stop processing mailboxes on the target server. To disable this default behavior, do either of the following:

• In the Migration Manager console, open the properties of the server, go to the Mail

Target Agent | General node, and enable the Process mailbox databases after their switchover to another server option.

• Specify the ProcessMailboxDBAfterSwitchover=1 parameter in the Config.ini file of the corresponding agent.

• After a mailbox move operation or the creation of a new Exchange 2010 mailbox during the migration process, the mailbox does not immediately become available for login. The Mail Target Agent will record login errors until the mailbox is ready (this can take up to 20 minutes). In these situations, login errors can be safely ignored. • If a mailbox move request completes with an error, delete this request before the

agent creates a new one.

• During mailbox migration, if there are identically named folders in the source mailbox and target mailbox, then a pair of folders with the same name will appear in the target mailboxes. Such folders are not duplicates and should not be deleted. If you encounter identically named folders after migration, consider merging them.

(15)

About Quest Software, Inc.

Now more than ever, organizations need to work smart and improve efficiency. Quest Software creates and supports smart systems management products—helping our customers solve everyday IT challenges faster and easier. Visit www.quest.com for more information.

Contacting Quest Software

Phone 949.754.8000 (United States and Canada) Email [email protected]

Mail Quest Software, Inc.

World Headquarters 5 Polaris Way

Aliso Viejo, CA 92656 USA Web site www.quest.com

Please 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 SupportLink, our self-service portal. Visit SupportLink at http://support.quest.com/

From SupportLink, you can do the following:

• Retrieve thousands of solutions from our online Knowledgebase • Download the latest releases and service packs

• Create, update and review Support cases

(16)

14

Third Party Contributions

Quest®_{Migration Manager, version 8.6 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.0 Loki 0.1.4 MIT Loki 0.1.6 MIT

TinyXml 2.2.1 This product contains portions of the PAWN scripting software (formerly known as SMALL).

Boost 1.0 License Agreement

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 machine-executable 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 Agreement

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

(17)

Loki 0.1.6 License Agreement

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 Agreement

/* zlib.h—interface of the 'zlib' general purpose compression library version 1.2.3, July 18th, 2005

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]