8.8. Post-Migration Activities

Transcription

1 8.8 Post-Migration Activities

2 2011 Quest Software, Inc. ALL RIGHTS RESERVED. This document contains proprietary information protected by copyright. The software described in this document 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 legal@quest.com Refer to our website for regional and international office information. TRADEMARKS Quest, Quest Software and the Quest Software logo 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 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. Quest Migration Manager Version 8.8 Last updated 28 July, 2011

3 Contents About This Guide... 4 Overview... 4 Conventions... 4 Post-Migration Activities... 5 Overview... 5 Stop the Mailbox and Calendar Synchronization Jobs... 5 Stop the Public Folder Synchronization Jobs for Migrated Folders... 6 Stop the Free/Busy Synchronization Job... 6 Stop Directory Synchronization... 7 Disable Source Accounts... 7 Clean Up the Service Attributes Used for Migration... 7 Clean Up SIDHistory Attributes... 7 Clean Up Legacy Account Permissions... 8 Decommission Migrated Environments... 9 About Quest Software, Inc Contacting Quest Software Contacting Quest Support Third Party Contributions Boost : License Text Boost : License Text Loki 0.1.4: License Text Loki 0.1.6: License Text NABU-library 1.0: License Text Newtonsoft.Json.dll : License Text ZLib 1.1.4: License Text

4 Quest Migration Manager Post-Migration Activities 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 to configure and use 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 Select Bolded text Italic text Bold Italic text Blue text CONVENTION 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. Introduces a series of procedures. 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

5 Quest Migration Manager Post-Migration Activities Post-Migration Activities Overview After migration has come to an end and you are absolutely sure that all the objects have been successfully migrated to the target environment, you might want to perform the following activities: 1. Stop the mailbox and calendar synchronization jobs for migrated servers and uninstall the mail and calendar agents. 2. Stop the public folder synchronization jobs for migrated folders and uninstall the public folder synchronization agents. 3. Stop the Free/Busy synchronization and uninstall the Free/Busy Synchronization agent. 4. Stop directory synchronization. 5. Disable source accounts. 6. Clean up the service attributes used for migration. 7. Clean up SIDHistory attributes. 8. Clean up permissions for legacy accounts. 9. Decommission the migrated Exchange servers and collapse the source Exchange organizations. These steps are described in detail below. Stop the Mailbox and Calendar Synchronization Jobs When all the mail data from a server is migrated to the new Exchange servers, you can stop the mailbox synchronization job and uninstall the mail agents. By this time all the users who had mailboxes on the server should already use their target Exchange mailboxes. If you do not need to synchronize Calendar details (appointments and meetings), you can also stop the Calendar Synchronization Agent. 5

6 Quest Migration Manager Post-Migration Activities To stop and uninstall the agents, take the following steps from the Migration Manager console: 1. Right-click the source server and stop the Mail Source Agent, the Calendar Synchronization Agent (if running on the source server), and the Transmission Agent. Alternatively, you can right-click a job in the management tree and click Stop All Agents on the shortcut menu. Note that the Transmission Agent can also be involved in public folder synchronization; in this case you should not stop it. 2. If the target servers do not participate in any other mailbox synchronization jobs, stop the Mail Target Agent on each of the target servers. 3. Delete the mailbox and calendar synchronization jobs for the server. 4. Uninstall the stopped agents by clicking Install/Uninstall Agents on the Actions menu. Stop the Public Folder Synchronization Jobs for Migrated Folders After all the users have been switched to the target servers and are using the target public folders, you can stop the public folder synchronization jobs, as follows: 1. Right-click each of the source and target servers and stop the Public Folder Source Agent, the Public Folder Target Agent, and the Transmission Agents. Alternatively, you can right-click a job in the management tree and click Stop All Agents on the shortcut menu. Note that in this case you might occasionally stop an agent that is involved in other synchronization jobs, for example if public folders from different source servers are synchronized with the same target server. 2. Delete the public folder synchronization jobs. 3. Uninstall the stopped agents by clicking Install/Uninstall Agents on the Actions menu. Stop the Free/Busy Synchronization Job After all the users get switched to the target servers, you can stop the free/busy synchronization job and uninstall the Free/Busy Synchronization Agent, as follows: 1. Right-click each of the source and target servers and stop the Free/Busy Synchronization Agent. Alternatively, you can right-click a Free/Busy synchronization job in the management tree and click Stop All Agents on the shortcut menu. 2. Delete the Free/Busy synchronization job. 3. Uninstall the stopped agents by clicking Install/Uninstall Agents on the Actions menu. 6

7 Stop Directory Synchronization Quest Migration Manager Post-Migration Activities After all the objects have been successfully migrated to the target environment, the directory synchronization job can be stopped and the Directory Synchronization Agent uninstalled. Disable Source Accounts Once you are sure that the migration was indeed carried out smoothly, that access to resources has been preserved, and that your help desk is not experiencing a sharp increase in the number of calls, it is good practice at this stage to disable the source accounts and thus make sure that all users are logging on with their target accounts. We recommend that you wait some time after disabling the source accounts to make sure that all users are using their target accounts before beginning cleanup. Clean Up the Service Attributes Used for Migration To clean up the service attributes used by the Directory Synchronization Agent during migration and synchronization, you can use the Active Directory Cleanup Utility for Quest Migration Manager. The utility is available in the Migration Manager for Active Directory Resource Kit. The Directory Synchronization Agent adds to the proxy address list of each synchronized target user an x500 address that is equal to the legacyexchangedn attribute of the matching source user. Do not delete these x500 addresses unless you are certain they are no longer needed. The x500 addresses are used for the following purposes: If you migrated mailboxes in Remote Users Collections, preserving their OST files, these x500 addresses are used to link the original OST files with the target mailboxes. If an was received from a source recipient and delivered to the source mailbox before this was migrated to the target mailbox by the agents, the x500 address is used to reply to the . If you delete these x500 addresses from the proxy address list of the target mailbox later, the OST file associated with the mailbox will become inaccessible and other users will no longer be able to reply to old sent by users whose addresses have been deleted. Therefore, you should never delete auxiliary x500 addresses added by the Directory Synchronization Agent unless you are absolutely sure that the ability to reply to the old s is no longer needed and you want to rebuild the OST files. Clean Up SIDHistory Attributes After the distributed resources and BackOffice servers have been processed, we recommend you wait some time to ensure that everything is working right before cleaning up SIDHistory attributes from the target user accounts. SIDHistory cleanup is done by the Active Directory Processing Wizard. Choose the Cleanup objects SIDHistory option for Active Directory processing. Refer to the Active 7

8 Quest Migration Manager Post-Migration Activities Directory Processing section of the Migration Manager for Active Directory User Guide for more details. If after SIDHistory cleanup some users cannot access resources, SIDHistory can be reapplied back to the accounts that lost access only by re-migrating these accounts (with the merge option). This will give you time to check whether the resources were processed correctly for these accounts, fix the problem, and clean up SIDHistory again. After SIDHistory is cleaned up, wait some time to ensure that all target users can access the resources they used before the migration. Clean Up Legacy Account Permissions Once your users have started to log on under their new accounts in the target domain and are not experiencing any problems with access to resources, you may want to remove unnecessary references to the original source accounts in groups, user rights, and object security descriptors. Cleanup is hard to undo, so it is recommended that you clean up permissions only when you are sure that all users are using their target accounts for all applications and have no problems accessing resources. Cleanup of legacy account permissions is performed by the same wizards used to update resources. Refer to the table below to choose the resource updating tool and the right option to cleanup legacy account permissions from distributed resources, Active Directory, and BackOffice servers. TO CLEAN UP LEGACY ACCOUNT PERMISSIONS FOR TOOL TO USE RE-PERMISSIONING OPTION TO CHOOSE REFERENCES Distributed resources Resource Updating Manager Clean up legacy local group membership, user rights and permissions of migrated users. This option is available when you create a processing task in Resource Updating Manager. See the Resource Updating Manager section of the Migration Manager for Active Directory User Guide. Active Directory Active Directory Processing Wizard Clean up group membership and permissions of migrated users See the Active Directory Processing section of the Migration Manager for Active Directory User Guide. Exchange servers Exchange 5.5 Processing Wizard Exchange Processing Wizard Clean up legacy object ownership and permissions of migrated users See the Exchange Processing section of the Migration Manager for Active Directory User Guide. 8

9 Quest Migration Manager Post-Migration Activities TO CLEAN UP LEGACY ACCOUNT PERMISSIONS FOR TOOL TO USE RE-PERMISSIONING OPTION TO CHOOSE REFERENCES Systems Management servers SMS Processing Wizard Clean up object ownership and permissions of migrated users See the SMS Processing section of the Migration Manager for Active Directory User Guide. After the cleanup, users from the source domain will lose their access rights. If cleanup is done before running Resource Updating Manager with the Reassign local group membership, user rights, and object permissions to target users option selected, there will be no way to get these permissions back, nor will there be a way to reassign permissions to target users by Resource Updating Manager. You will have to restore resources from a backup. Decommission Migrated Environments In an Exchange migration, after mailbox migration is completed, you can clean the source mailboxes and move them to another server in the same administrative group. This ensures the uninterrupted collaboration for the other users of source organization and frees up hardware. The last server of the source administrative group should be kept and maintained until the whole Exchange migration is completed. 9

10 Quest Migration Manager Post-Migration Activities About Quest Software, Inc. Quest simplifies and reduces the cost of managing IT for more than 100,000 customers worldwide. Our innovative solutions make solving the toughest IT management problems easier, enabling customers to save time and money across physical, virtual and cloud environments. For more information about Quest go to Contacting Quest Software Mail Web site info@quest.com Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA USA 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 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 View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies and procedures. The guide is available at: 10

11 Third Party Contributions Quest Migration Manager Post-Migration Activities Quest Migration Manager, version 8.8 contains some third party components (listed below). Copies of their licenses may be found at COMPONENT LICENSE OR ACKNOWLEDGEMENT Boost Boost 1.0 Boost Boost 1.0 HTMLayout 1.0 Loki Loki This Application (or Component) uses HTMLayout Component, copyright Terra Informatica Software, Inc. ( MIT MIT NABU-library 1.0* GNU LGPL Version 3, 29 June 2007 Newtonsoft.Json.dll MIT ZLib zlib TinyXml This product contains portions of the PAWN scripting software (formerly known as SMALL). * a copy of the source code for this component is available at Boost : License Text Boost Software License - Version 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. Boost : License Text Boost Software License - Version 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: 11

12 Quest Migration Manager Post-Migration Activities 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. NABU-library 1.0: License Text GNU LESSER GENERAL PUBLIC LICENSE Version 3, 29 June

13 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. Quest Migration Manager Post-Migration Activities 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. 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 13

14 (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. Quest Migration Manager Post-Migration Activities 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 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: 14

15 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. Quest Migration Manager Post-Migration Activities Newtonsoft.Json.dll : 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) Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied 15

16 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 jloup@gzip.org Mark Adler madler@alumni.caltech.edu */ Quest Migration Manager Post-Migration Activities 16