Microsoft KB Archive/303533

= Recommended Practices for Upgrading to Microsoft Metadirectory Services 2.2 Service Pack 1 =

Article ID: 303533

Article Last Modified on 1/25/2006

-

APPLIES TO


 * Microsoft Metadirectory Services 2.2 Service Pack 1
 * Microsoft Metadirectory Services 2.2 Service Pack 1

-



This article was previously published under Q303533



SUMMARY
This article describes the recommended practices for upgrading from Microsoft Metadirectory Services (MMS) 2.2 to MMS 2.2 Service Pack 1 (SP1). For information about upgrading from earlier versions of MMS or Zoomit Via, refer to the release notes that are included on the MMS 2.2 or MMS 2.2 SP1 compact disk.

The following topics are described in this article:
 * Preparation for the upgrade
 * The upgrade process
 * Recommendations after the upgrade
 * Known upgrade issues

Due to the highly customizable nature of the MMS product, Microsoft strongly recommends that you first use this procedure to deploy and thoroughly test MMS 2.2 SP1 in a test environment prior to deploying it in a production environment.



Preparation for Upgrade
 Review the release notes. Create a backup of your MMS server.

You can either create a backup with MMS Online Backup Utility or you can copy the entire Zoomserv directory to another location. Copying the entire Zoomserv directory will allow a quick recover to the exact state of all files prior to the upgrade. You have to stop the MMS service before performing a backup. Back up your MMS server keys.

The MMS server Keys will be important if you have to restore the backup to another server.For additional information about backing up the server keys, click the article number below to view the article in the Microsoft Knowledge Base:

285980 How to Move an MMS 2.2 Database to Another Server

 Run a compaction of your database and verify that the Genlogs do not contain any errors.

Verify that there are no database errors prior to upgrading your system to minimize the possibility of bringing bad data into the newly upgraded system. It will also be easier to determine if an error was caused by the upgrade process or if it was in the old system prior to upgrade.

Upgrade Process
 When upgrading to MMS 2.2 SP1 make sure that the MMS service is stopped before installing. Not doing so can cause your MMS server upgrade to fail. It is highly recommended that you perform all MMS server upgrades from the system console as opposed to upgrading through a terminal server session. However, if you must perform an upgrade through a terminal server session, make sure that all other terminal server sessions to the system are closed before you attempt the upgrade.For additional information about the potential problem that may be encountered when installing MMS over Terminal Services, click the article number below to view the article in the Microsoft Knowledge Base:

299492 Difficulties When You Install MMS Server over a Terminal Server Session

</li> If you are running an upgrade, make sure to choose the correct drive when you are prompted. If you choose the correct drive, you will have the default selection of upgrading your system when that screen appears.</li> After the upgrade is complete, you are prompted with the MMS Compact Utility. It is required that you run the MMS Compact Utility to compact the database after upgrading to MMS 2.2 SP1.</li></ol>

Part I: Active Directory Templates Modified for SP1
The Active Directory Management Agents (ADMAs) that are created after the upgrade to SP1 are created by using the updated templates. Because most MAs are customized, the existing ADMAs are not automatically upgraded to avoid the overwriting of custom features. For this reason, you need to manually migrate each existing ADMA to the newer templates.

Note: Because most installations have customized templates, it is highly recommended that you use a product, such as Microsoft Visual SourceSafe, to keep track of progressive changes that can occur to the ADMA during the migration process.

To upgrade the templates after you upgrade
 Record the templates to the working directory of the ADMA. When you record the templates, select the Update this MA from its working directory templates located at check box so that you can use the templates in the working directory of the MA to update the MA when you perform this step later in this procedure.For additional information about recording templates, click the article number below to view the article in the Microsoft Knowledge Base:

250479 Recording Management Agent Templates in Microsoft Metadirectory Services

</li> If you use Visual SourceSafe, make sure that the computer has the latest templates.</li> Copy the working directory for the ADMA to another location, and then name it location1. Verify that the templates match the current version that is stored in Visual SourceSafe if you are using Visual SourceSafe.</li> Use either Visual SourceSafe or Windiff to compare the files for differences in the templates between the original MMS 2.2 templates and the templates that are in location1. (You can use this information to move the custom settings to the new templates or other templates.)</li> Assuming the MMS installation is on the C drive of the computer, copy all of the templates from the C:\Zoomserv\Data\DSGates folder for the ADMA to another location, location2. If MMS is installed to another drive, adjust the drive letter as necessary.</li> Copy the Advanced.st and Simple.st files from location1, and then place them into location2.</li> Use the information that you obtained and then check the differences of the files in step 4 and make any necessary adjustments to your template files in location2. Whenever possible, make all changes in the Advanced.st file. It is not recommended to change the other templates. This precaution can help you with the troubleshooting process.</li> Copy all of the files in location2 into the working directory for the ADMA.</li> On the Action panel, click Update Management Agent.</li> Run the MA to verify that the templates work as designed.</li></ol>

Part II: SP1 Database Files Allow up to 511-Byte Domain Names
The Database files will differ depending on if you upgrade your existing system or perform a new installation. Upgraded systems use the same database file structure as MMS 2.2 and thus only support 255 byte Domain Names. You will notice from the files that are listed below that db500.p appears both in the &quot;Upgrade Files&quot; and the &quot;New Installation Files&quot;. However, the files are different even though their names are the same. These differences will allow the &quot;New Installation Files&quot; the ability to store the larger Domain Name size of 511 bytes.

Upgrade files
DB500.dat

DB500.p

DB500.lok

DB500.NDX

New installation files
DB500.dat

DB500.p

DB5LEV.nxd

DB5DN.nxd

DB5MISC.nxd

If you require the storage of Domain Names larger than 255 bytes and you are upgrading your existing MMS Server, use the following steps to manually upgrade to the newer files:

Note: Perform these steps on a test server.  Perform a clean installation of MMS to a test server.</li> <li>Locate the Db500.p file in the \Zoomserv\Data\DB folder.</li> <li>Copy the Db500.p file to a share on the root of the Upgrade system, name it &quot;Share&quot;, and have it located in C:\share on the upgraded MMS server.Note: Perform the following steps on the upgraded MMS Server:</li> <li>Open a command prompt in Windows 2000.</li> <li>Stop the MMS Server Service on the upgraded machine by typing the following command:

net stop &quot;MMS Server&quot;

</li> <li>Change the directory to the following by typing at the root drive where the MMS database files are located:

cd \zoomserv\data\db

</li> <li>Rename the following files:

Db500.p

DB500.DAT

DB500.LOK

DB500.NDX

To rename these files, type each of the following lines at the command prompt one at a time:

Rename db500.p db500.p.old

Rename DB500.DAT DB500.DAT.old

Rename DB500.LOK DB500.LOK.old

Rename DB500.NDX DB500.NDX.old

</li> <li>Copy the new version of Db500.p file to this location copied to the c:\share location in Step 3, by typing the following command:

copy c:\share\db500.p

</li> <li> Type the following command

\zoomserv\bin\ctexmc db500.p

to generate the following output: <pre class="fixed_text">  Creating MMS Datastore Successful Creation </li> <li>Run the MMS Compaction Utility without the Verify ASN Database option: <ol style="list-style-type: lower-alpha;"> <li>Open MMS Compaction Utility (click Start, point to Programs, point to Microsoft Metadirectory Services, and then click MMS Compaction Utility.</li> <li>Click the Advanced button.</li> <li>On the Actions tab, click to clear the Verify ASN Database check box.</li> <li>Click OK.</li> <li>Click the Start button.</li></ol> </li> <li>After the compaction process has completed, restart the MMS server service.</li></ol>

Known Issues
The upgraded system may have the db5_max_tran_file_size parameter set too low, which causes error 19118 and mismatched watermarks messages. For additional information about this behavior, click the article number below to view the article in the Microsoft Knowledge Base:

300259 Mismatch Watermark and 19118 Error Messages Occur Due to Loss of Transactions

User accounts may be disassociated with their mailboxes in Exchange 2000. For additional information about this behavior, click the article number below to view the article in the Microsoft Knowledge Base:

286190 The Active Directory Management Agent May Inadvertently Change the User Attributes That Are Related to the User Mailbox

After converting the XML and file Toolkit MAs, the Configuration tabs may be missing. For additional information about this behavior, click the article number below to view the article in the Microsoft Knowledge Base:

292603 Missing Tabs on the Configure MA Form After You Convert an XML Management Agent

Additional query words: mms metadirectory zoomit

Keywords: kbinfo KB303533

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.