Deploying the FIM Add-In components
One of the components in the deployment of FIM 2010 SSPR is the client roll-out of the Add-ins and Extensions for FIM 2010. There are a few ways of achieving this but the following is a simple batch file that will detect the client OS version and deploy the appropriate components.
Thank you to Craig Eldridge for the script.
if %PROCESSOR_ARCHITECTURE% == AMD64 goto AMD64
if %PROCESSOR_ARCHITECTURE% == x86 goto x86
GOTO EXIT
:AMD64
msiexec /i \\servername\sharename\FIM\addins\x64\Add-insetc.msi /quiet ADDLOCAL=PasswordClient RMS_LOCATION=<portal server> PORTAL_LOCATION=<portal server> PORTAL_PREFIX=https SITELOCK_DOMAIN="<servername>/<FQDN Name>" /log fim.log goto EXIT
86
msiexec /i \\servername\sharename\FIM\addins\x86\Add-insetc.msi /quiet ADDLOCAL=PasswordClient RMS_LOCATION=<portal server> PORTAL_LOCATION=<portal server> PORTAL_PREFIX=https SITELOCK_DOMAIN="<servername>/<FQDN Name>" /log fim.log
goto EXIT
:EXIT
Check out the following additional resource for more information on the options available with the unattended installation. TechNet – Unattended Installation of FIM 2010
To troubleshooting the client installation you can check the “fim.log” that was created and search for “Return Value 3” which signifies a Windows Installer Error.
One last thing: The script above would install the client components and force a restart of the client machine. To ignore the restart you can add the “/norestart” option just before of after the “/quite” option.
Hi, i feel that i saw you visited my web site thus i came to “go back the prefer”.I am trying to in finding things to improve my website!I guess its ok to make use of some of your ideas!!
Greeting from over the world. detailed blog I shall return for more.