70-158 · Question #64
You administer a Forefront Identity Management (FIM) 2010 server in your company network. All client computers run Windows 7. Your company plans to automate the deployment of FIM client components…
The correct answer is B. From a command prompt, run msiexec.exe /i "\\DistributionServer\FIM\Add-ins and extensions.msi". Unattended installation of FIM client components requires using msiexec.exe with the correct silent installation switches against the Add-ins and extensions MSI package. The correct command must include the /quiet or equivalent silent flag to suppress user interaction.
Question
Options
- AFrom a command prompt, run msiexec.exe /i "\DistributionServer\FIM\Add-ins and extensions.msi"
- BFrom a command prompt, run msiexec.exe /i "\DistributionServer\FIM\Add-ins and extensions.msi"
- CFrom the Windows PowerShell console, run Get-WMIObject -ComputerName LONCL1 -List |
- DFrom the Windows PowerShell console, run Get-Object -ComputerName LONCL1 -List | Where-
How the community answered
(35 responses)- A6% (2)
- B74% (26)
- C6% (2)
- D14% (5)
Why each option
Unattended installation of FIM client components requires using msiexec.exe with the correct silent installation switches against the Add-ins and extensions MSI package. The correct command must include the /quiet or equivalent silent flag to suppress user interaction.
Although this command also uses msiexec.exe with the correct MSI path, it lacks the required silent installation switches (e.g., /quiet or /passive) needed to perform a truly unattended installation, which would result in interactive prompts appearing during deployment.
An unattended installation requires msiexec.exe with the /i flag to specify the MSI package path pointing to the FIM 'Add-ins and extensions.msi', which contains the Password and Authentication extension. The correct answer (B) includes the necessary silent/quiet installation switches (such as /quiet or ADDLOCAL parameters) that distinguish it from choice A, enabling fully automated deployment without user prompts.
Get-WMIObject is a PowerShell cmdlet used for querying WMI objects and system information, not for installing MSI packages or deploying FIM client components.
Get-Object is not a valid PowerShell cmdlet for software installation; PowerShell WMI-based approaches shown here are designed for querying system properties, not performing unattended MSI installations of FIM extensions.
Concept tested: Unattended MSI installation of FIM client components
Source: https://learn.microsoft.com/en-us/microsoft-identity-manager/microsoft-identity-manager-deploy
Topics
Community Discussion
No community discussion yet for this question.