nerdexam

70-158 · Question #62

Your company network includes Microsoft Identity Lifecycle Manager (ILM) 2007 and Microsoft SQL Server 2005. You need to perform a platform upgrade from ILM to Forefront Identity Manager (FIM) 2010…

The correct answer is B. Rename the ILM database to FIMSynchronizationService. C. Set the compatibility level on the ILM database to SQL Server 2005 (90). E. Copy the existing ILM database in SQL Server 2005 to a server that runs a 64-bit version of. Upgrading from ILM 2007 to FIM 2010 requires specific database renaming, compatibility settings, and a 64-bit SQL Server 2008 environment. All three steps must be performed in the correct order to ensure a successful platform migration.

Submitted by jaden.t· Mar 4, 2026Install and upgrade Forefront Identity Manager (FIM) 2010

Question

Your company network includes Microsoft Identity Lifecycle Manager (ILM) 2007 and Microsoft SQL Server 2005. You need to perform a platform upgrade from ILM to Forefront Identity Manager (FIM) 2010. You also need to upgrade SQL Server 2005 to SQL Server 2008. What should you do? (Choose all that apply.)

Options

  • ARename the ILM database to FIMSynchronizationManagement.
  • BRename the ILM database to FIMSynchronizationService.
  • CSet the compatibility level on the ILM database to SQL Server 2005 (90).
  • DCopy the existing ILM database in SQL Server 2005 to a server that runs a 32-bit version of
  • ECopy the existing ILM database in SQL Server 2005 to a server that runs a 64-bit version of

How the community answered

(33 responses)
  • A
    18% (6)
  • B
    73% (24)
  • D
    9% (3)

Why each option

Upgrading from ILM 2007 to FIM 2010 requires specific database renaming, compatibility settings, and a 64-bit SQL Server 2008 environment. All three steps must be performed in the correct order to ensure a successful platform migration.

ARename the ILM database to FIMSynchronizationManagement.

The correct target database name required by FIM 2010 is 'FIMSynchronizationService', not 'FIMSynchronizationManagement'; using the wrong name would cause FIM 2010 setup to fail to locate the database.

BRename the ILM database to FIMSynchronizationService.Correct

FIM 2010 expects the synchronization service database to be named 'FIMSynchronizationService'; renaming the ILM database to this name ensures FIM 2010 can locate and attach to the existing database during the upgrade process.

CSet the compatibility level on the ILM database to SQL Server 2005 (90).Correct

Setting the database compatibility level to SQL Server 2005 (level 90) before upgrading to SQL Server 2008 preserves backward-compatible behavior during the migration, preventing breaking changes that could corrupt or invalidate the ILM data structures during the upgrade.

DCopy the existing ILM database in SQL Server 2005 to a server that runs a 32-bit version of

FIM 2010 does not support 32-bit SQL Server installations; copying the database to a 32-bit SQL Server 2008 instance would be incompatible with FIM 2010's 64-bit architecture requirement.

ECopy the existing ILM database in SQL Server 2005 to a server that runs a 64-bit version ofCorrect

FIM 2010 is a 64-bit application and requires a 64-bit version of SQL Server 2008; copying the database to a server running the 64-bit edition satisfies FIM 2010's platform requirements and enables the upgrade to proceed correctly.

Concept tested: ILM to FIM 2010 upgrade database migration steps

Source: https://learn.microsoft.com/en-us/previous-versions/mim/ee534962(v=ws.10)

Topics

#FIM 2010 Upgrade#ILM Migration#FIMSynchronizationService#SQL Server Compatibility

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-158 Practice