70-158 · Question #31
You use Forefront Identity Manager (FIM) 2010 in your company network. You install the FIM Service as a stand-alone server. During the creation process of the FIM Service Management Agent (MA), you…
The correct answer is B. Run the FIM Service and Portal program in Change mode. Configure Common Services to use a new. To resolve a SID mismatch preventing Windows integrated authentication for the FIM Service Management Agent without editing the registry, the FIM Service and Portal setup must be run in Change mode to reconfigure the common services.
Question
Options
- AReconnect to the FIM Service database by using the credentials associated with the FIM MA account
- BRun the FIM Service and Portal program in Change mode. Configure Common Services to use a new
- CAdd the FIM MA account to the Local Administrators group of the connected domain controller.
- DConnect to the FIM database by using SQL authentication mode.
How the community answered
(27 responses)- A11% (3)
- B67% (18)
- C7% (2)
- D15% (4)
Why each option
To resolve a SID mismatch preventing Windows integrated authentication for the FIM Service Management Agent without editing the registry, the FIM Service and Portal setup must be run in Change mode to reconfigure the common services.
Simply attempting to reconnect with the same credentials will not resolve the underlying SID mismatch between the account and the FIM Service's registry configuration.
Running the FIM Service and Portal program in Change mode allows the administrator to re-configure existing FIM components, including the FIM Service account settings. This process re-registers the service account's current SID within FIM's configuration and associated registry entries, resolving the mismatch without requiring manual registry edits and enabling Windows integrated authentication.
Concept tested: FIM Service account reconfiguration; resolving SID mismatches.
Topics
Community Discussion
No community discussion yet for this question.