Partilhar via


How To: Relocate the MIIS 2003 Database

Applies To: Forefront Identity Manager, Windows Server 2003 with SP1

This How To guide describes the process of relocating the MIIS 2003 database, named MicrosoftIdentityIntergrationServer from a computer that is running Microsoft® SQL Server™ 2000 to another computer that is running SQL Server 2000 with all critical data intact.

Specifically, you will perform the following tasks:

  • Stop the MIIS service, backup the MIIS 2003 encryption key and MIIS 2003 database.

  • Restore the MIIS 2003 database to another server hosting Microsoft SQL Server 2000 Enterprise Edition.

  • Uninstall and reinstall MIIS 2003 to point to the new server hosting the MIIS 2003 database.

    Note

    The information contained in this document refers to standalone SQL Server 2000 environments or SQL Server 2000 clustered environments.

Relocating the MIIS 2003 Database

You must complete the following steps to relocate the MIIS 2003 database:

Step 1: Stop the MIIS service

Step 2: Backup the MIIS 2003 encryption key

Step 3: Backup the MIIS 2003 SQL database

Step 4: Restore the MIIS 2003 database on the new SQL 2000 server

Step 5: Uninstall and reinstall MIIS 2003

Step 1: Stop the MIIS Service

For this procedure you will stop the MIIS 2003 service running on the server that hosts MIIS 2003. This prevents any management agents from running between the start of your database backup and when you uninstall MIIS 2003.

To stop the MIIS Service

  1. At the command prompt, type services.msc.

  2. In the Services window scroll down and right-click Microsoft Identity Integration Server.

  3. Click Stop.

  4. Close the Services window.

Step 2: Backup the MIIS 2003 Encryption Key

After stopping the MIIS service you will backup the MIIS 2003 encryption key. This is a precautionary measure to ensure accessibility to the MIIS 2003 database once it has been moved to the new SQL server.

To backup the encryption keys

  1. From the Command Prompt window, change the directory to MIIS 2003 InstallationDirectory\Bin folder.

  2. At the command prompt, type:

    • miiskmu /eFileName [/u:UserName {Password | *}]

      The parameters are explained as follows:

      /e Exports the key set to a file

      FileName Specifies the name of the file.

      /u Specifies the Microsoft Identity Integration Server 2003 service account credentials.

      Username The Microsoft Identity Integration Server 2003 service account name. Miiskmu supports the following formats:

      [Domainname\]UserName

      [Domainname.com\]UserName

      UserName@Domainname.com

      Password Specify the password for the Microsoft Identity Integration Server 2003 service account. Use * to prompt for the password.

      /? Displays help at the command prompt.

  3. Click OK on the message, "The operation has completed successfully. The encryption keys were successfully written to a specified file location. Please store this file in a secure location."

Step 3: Backup the MIIS 2003 Database

You can now backup the MIIS 2003 database. This database holds all the configuration information of your MIIS 2003 server. The configuration includes all of the management agents, run profiles, connector space and metaverse objects, and any rules extensions.

To backup the MIIS 2003 database

  1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.

  2. Expand Microsoft SQL Server, SQL Server Group, (local)(Windows NT), and Databases.

  3. Click MicrosoftIdentityIntegrationServer.

  4. From the SQL Server Enterprise Manager window, click Tools and Backup Database.

  5. In the SQL Server Backup - MicrosoftIdentityIntegrationServer window, under Destination, click Add.

  6. From the Select Backup Destination window specify the File name or Backup device that you choose to save the MicrosoftIdentityIntegrationServer database and click OK.

  7. Click OK to the message "The backup operation has been completed successfully" and exit the SQL Server Enterprise Manager window.

    Note

    For more information about backing up SQL Server 2000 databases, refer to the documentation that comes with the SQL Server 2000 product media.

Step 4: Restore the MIIS 2003 database on the new SQL 2000 Server

Following the backup of the MIIS 2003 database, you will restore the MIIS 2003 database to the new SQL Server 2000 server.

To restore the MIIS 2003 database

  1. On the new SQL Server 2000 sever that will host the MIIS 2003 database, click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.

  2. Expand Microsoft SQL Server, SQL Server Group, (local)(Windows NT), and Databases.

  3. Click Databases.

  4. From the SQL Server Enterprise Manager window, click Tools and Restore Database.

  5. In the window Restore database, type MicrosoftIdentityIntergrationServer in the box Restore as database:.

  6. For the Restore: option, choose From device and then click Select Devices.

  7. In the Choose Restore Devices window choose Disk for the Restore from: option.

  8. Click the Add button and navigate to the file you saved as the backup database, and click OK and OK again to close the Choose Restore Destination window.

  9. Click OK to the message "Restore of database 'MicrosoftIdentityIntegrationServer' completed successfully".

    Note

    For more information about restoring SQL Server 2000 databases refer to the documentation that comes with the SQL Server 2000 product media.

Step 5: Uninstall and Reinstall MIIS 2003

In this last procedure, you will uninstall and reinstall MIIS 2003. This will enable you to point the MIIS 2003 installation to the new computer that is running SQL Server 2000.

Note

You should not be concerned about losing any of your identity management data because it is stored in the MIIS 2003 database. All data, management agents and run profiles and rules extensions will remain intact after uninstalling and re-installing MIIS 2003.

To uninstall MIIS 2003

  1. Click Start, point to All Programs, Add or Remove Programs and click Microsoft Identity Integration Server.

  2. Click Remove.

  3. Click Yes to the message, "Are you sure you want to remove Microsoft Identity Integration Server from your computer".

To install MIIS 2003

  1. Insert the MIIS 2003 SP 1 CD-ROM into your CD-ROM drive, browse to the Enterprise folder and click Setup.exe.

  2. After accepting the license agreement, choose Complete on the Type of Installation page.

  3. On the Store Information page, specify the location of the new server that is running SQL Server 2000 and the location of where the MIIS 2003 database (MicrosoftIdentityIntegrationServer) is now hosted. Click Next.

  4. On the Service Account Information page, enter the service account name and password that you created for your MIIS 2003 installation. Populate the Domain or local computer name box with the appropriate values. Click Next.

  5. On the Group Information page, ensure that all the MIIS groups reflect the correct values and then click Next.

  6. Click the Start button to begin installing the MIIS 2003 program files.

    Note

       A warning message may or may not appear that states the MIIS account is not secure in its current configuration. If this warning message appears you can find the complete list of best practice recommendations for creating a secure MIIS 2003 installation in the "Best Practices For Security" topic in the MIIS 2003 Online Help collection.

  7. Click Yes to the message that states, "A Microsoft Identity Integration Server database already exists." MIIS 2003 uses the database from the server that you specified that now contains your MIIS 2003 data.

    Note

    The prompt for the key file name does not occur if Setup detects that a valid key set exists on the system. If you delete the user profile of the service account, the encryption keys get deleted and the prompt occurs.

  8. The final page indicates that you have successfully completed the Microsoft Identity Integration Server setup. Click Finish to complete the installation and close the setup window.

Verification Steps

To ensure the MIIS 2003 database move was successful with all data intact, search the connector space using the Search connector Space option located within MIIS 2003. You can view properties of a search result, or use Preview to test the effects of synchronization of an object with the metaverse and other connector spaces.

To search for a connector space object

  1. Click Start, point to All Programs, point to Microsoft Identity Integration Server, and then click Identity Manager.

  2. On the Tools menu, click Management Agents.

  3. In Management Agents, click a management agent with an associated connector space.

  4. On the Actions menu, click Search Connector Space.

  5. In Scope, perform one the of tasks listed below:

    1. To search the connector space for an object with a specific distinguished name or anchor:

      Click DN or Anchor, and then, in Specify distinguished name (DN) or anchor value, type all or the first part of the name of the object to search for. For directory-based management agents, you can search by distinguished name. For management agent types that do not have a distinguished name (for example, a database or nonhierarchical file-based management agent), you can search by anchor attribute because, in the metadirectory, the anchor attribute is treated as a distinguished name. This search will also be applied to RDN.

    2. To search the connector space for an object within a specific subtree:

      Click Sub-Tree, and then, in Specify distinguished name (DN) for sub-tree, type all or the first part of the distinguished name of the subtree to search for. This option returns all objects within the subtree.

  6. Click Search. This should return all the associated objects in the connector space specified by the search parameters above. You can now safely assume that all the information from the previous MIIS 2003 database was successfully relocated and restored to your new computer that is running SQL Server 2000 and that is hosting the MIIS 2003 database.