Resources For IT Professionals
Post an article
Wikis - Page Details
  • First published by (Microsoft, Microsoft Partner)
  • When: 1 Mar 2010 4:27 PM
  • Last revision by (eMicrosoft Partne)
  • When: 24 May 2013 1:28 PM
  • Revisions: 11
  • Comments: 6
Options
RSSSubscribe to Article (RSS)
Can You Improve This Article?
Positively! Click Sign In to add the tip, solution, correction or comment that will help other users.

Report inappropriate content using these instructions.
Wiki  >  TechNet Articles  >  Troubleshooting Installers in Forefront Client Security

Troubleshooting Installers in Forefront Client Security

Troubleshooting Installers in Forefront Client Security

FCS uses the Microsoft Software Installer (MSI) for most of its components. MSI is built into the operating system, and the file name (used both by system service and installer executive) is MSIEXEC.EXE. When you run this program by itself in a command prompt, you’ll see the offering of parameters in a dialog box. It works primarily on files with a MSI extension, amongst others.

MSIEXEC has logging options that can be very useful when trying to troubleshoot installer issues. By appending  ‘/l*v install.log’ to the command line (or your log file name of choice), you will get a fully verbose output. The switches are:

  • /l - specifies that a log file should be created
  • * - specifies that all information should be logged (there are 12 other types of information that can be logged - * means log them all, except for v and x <extra debugging information>)
  • v - specifies that the output should be verbose
For example, one of the MSI specific steps for upgrading from FCS Eval to FCS 1.0 (see http://technet.microsoft.com/library/bb625082.aspx) is (without the quotes):
 
Msiexec.exe /package filelocation\FCScs-kb-939366-x86-enu.msi /qn REBOOT=ReallySuppress
 
To get a log file with this command line, you can specify the following (again, without the quotes):
 
Msiexec.exe /package filelocation\FCScs-kb-939366-x86-enu.msi REBOOT=ReallySuppress /l*v FCS939366.log
 
(Additional note here: eliminating the quiet '/qn’ option allows you to see all user interfaces.  It’s good to watch the installer show its progress when troubleshooting an issue.)
 
So how do you interpret that log.   Memorize this phrase:  ‘Return value 3’ (be sure to substitute for the language specific version of the phrase if you’re running on a non-English OS).  Searching for this phrase in your log will generally pinpoint the cause of any major issue.   Or, at least, it will put you near a section of the log where problems led up to this failure.   This works most of the time.   Otherwise, patience will prevail here.   Since all installer logs, however verbose, contain a similar set of internal ‘stages’, with experience you will gather a better feel for where the problem is rooted.   Other phrases might come in handy, such as ‘error’ or ‘fail’.  
 
Also, for FCS, during server installation, be sure to check for any other logs that get populated under ‘…\Program Files\Microsoft Forefront\...’, since these get embedded in deeper subdirectories depending on the sub system being installed.
, , , , , , [Edit tags]
Leave a Comment
  • Please add 3 and 1 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
  • 24 May 2013 1:28 PM

    Carsten Siemens edited Revision 9. Comment: Added tags: has comment

  • 3 Jan 2013 11:37 AM

    Richard Mueller edited Revision 8. Comment: Removed (en-US) from title

  • 22 Mar 2012 6:47 PM

    Jewel Lambert edited Revision 4. Comment: Corrected spelling typo

  • 2 Mar 2010 12:44 AM

    Pronichkin edited Revision 2. Comment: removed culture code from TN Library link.

  • 1 Mar 2010 4:28 PM

    Pronichkin edited Revision 1. Comment: light edit (changed legacy windows installer syntax to modern one, text formatting).

Page 1 of 1 (5 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
  • Posted by
    on 1 Mar 2010 4:28 PM

    Pronichkin edited Revision 1. Comment: light edit (changed legacy windows installer syntax to modern one, text formatting).

  • Posted by
    on 2 Mar 2010 12:44 AM

    Pronichkin edited Revision 2. Comment: removed culture code from TN Library link.

  • Posted by
    on 22 Mar 2012 6:47 PM

    Jewel Lambert edited Revision 4. Comment: Corrected spelling typo

  • Posted by
    on 24 Dec 2012 12:43 PM

    GREAT ARTICLE!!

  • Posted by
    on 3 Jan 2013 11:37 AM

    Richard Mueller edited Revision 8. Comment: Removed (en-US) from title

  • Posted by
    on 24 May 2013 1:28 PM

    Carsten Siemens edited Revision 9. Comment: Added tags: has comment

Page 1 of 1 (6 items)