70-158 · Question #90
Your company network includes Forefront Identity Manager (FIM) 2010. You are performing the migration of FIM from the test environment to the production environment. After you run the…
The correct answer is B. Review the undone.xml file. To understand why the UndoneImports count is non-zero after running CommitChanges.ps1 in FIM 2010, you should review the undone.xml file, which explicitly lists the imports that failed to commit.
Question
Options
- AReview the changes.xml file.
- BReview the undone.xml file.
- CRun the ResumeUndoneImports.ps1 PowerShell script.
- DReview the Application log for FIM in the Event Log Viewer.
How the community answered
(34 responses)- A6% (2)
- B56% (19)
- C12% (4)
- D26% (9)
Why each option
To understand why the UndoneImports count is non-zero after running CommitChanges.ps1 in FIM 2010, you should review the `undone.xml` file, which explicitly lists the imports that failed to commit.
The `changes.xml` file typically contains the intended changes that were processed or committed, not the ones that failed or were undone.
The `undone.xml` file is specifically generated by the FIM 2010 migration toolkit (often in conjunction with `CommitChanges.ps1`) to record any changes that could not be successfully committed or imported into the new environment. Reviewing this file will provide the detailed list of undone imports, directly explaining why the count is not zero.
Running the `ResumeUndoneImports.ps1` script attempts to re-process the undone imports, but it does not provide diagnostic information about *why* they failed initially.
While the Application log might contain general errors, the `undone.xml` file is the specific and direct output for listing the details of uncommitted FIM migration imports.
Concept tested: FIM 2010 migration troubleshooting and log file analysis
Source: https://social.technet.microsoft.com/wiki/contents/articles/1230.fim-2010-migration-tool-usage.aspx
Topics
Community Discussion
No community discussion yet for this question.