nerdexam

70-158 · Question #63

Your company network includes Forefront Identity Manager (FIM) 2010 and Active Directory Domain Services (AD DS). AD DS is configured as a single domain. The domain functional level is set to…

The correct answer is C. Add the ForefrontIdentityManager.admx file and the regional .adml file to the PolicyDefinitions folder. The company needs to manage FIM client components using Group Policy, but the existing GPO lacks relevant settings. To make FIM client configuration settings available for Group Policy management, the ForefrontIdentityManager.admx and its regional .adml files must be added to…

Submitted by naveen.iyer· Mar 4, 2026Configure the FIM Portal and FIM Clients

Question

Your company network includes Forefront Identity Manager (FIM) 2010 and Active Directory Domain Services (AD DS). AD DS is configured as a single domain. The domain functional level is set to Windows Server 2008. Your company plans to use the FIM Add-in for Microsoft Outlook 2007 feature. You create and edit a Group Policy Object (GPO) for FIM Outlook 2007 settings. The GPO does not contain settings for FIM client configuration. You need to be able to manage FIM client components by using Group Policy. What should you do?

Options

  • ARaise the domain functional level to Windows Server 2008 R2.
  • BCreate the Central Store for Group Policy Administrative Templates on the PDC Emulator.
  • CAdd the ForefrontIdentityManager.admx file and the regional .adml file to the PolicyDefinitions folder.
  • DUpdate the client registry entries located in

How the community answered

(33 responses)
  • A
    6% (2)
  • B
    3% (1)
  • C
    76% (25)
  • D
    15% (5)

Why each option

The company needs to manage FIM client components using Group Policy, but the existing GPO lacks relevant settings. To make FIM client configuration settings available for Group Policy management, the ForefrontIdentityManager.admx and its regional .adml files must be added to the PolicyDefinitions folder.

ARaise the domain functional level to Windows Server 2008 R2.

Raising the domain functional level is not required for adding Group Policy administrative templates and does not address the issue of missing FIM client configuration settings in the GPO.

BCreate the Central Store for Group Policy Administrative Templates on the PDC Emulator.

While a Central Store is best practice, the problem states the GPO does not *contain* settings, implying the templates themselves are missing, not that the store doesn't exist or is improperly located.

CAdd the ForefrontIdentityManager.admx file and the regional .adml file to the PolicyDefinitions folder.Correct

To enable management of FIM client components through Group Policy, the necessary administrative template files (.admx for language-neutral settings and .adml for language-specific resources) must be present. Placing these files into the domain's central store (located in the 'PolicyDefinitions' folder within SYSVOL) makes the FIM client configuration settings available for selection and configuration within the Group Policy Management Editor.

DUpdate the client registry entries located in

Manually updating client registry entries bypasses Group Policy and does not fulfill the requirement to manage FIM client components *by using Group Policy*.

Concept tested: Group Policy Administrative Templates (ADMX/ADML) management

Source: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc709647(v=ws.10)

Topics

#ADMX Templates#FIM Client Configuration#Group Policy Management#FIM Outlook Add-in

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-158 Practice