Export (0) Print
Expand All

The FSC diagnostic tool for FSOCS

 

Applies to: Forefront Security for Office Communications Server

Topic Last Modified: 2008-11-14

To accurately diagnose a problem, support engineers typically need a variety of information about Microsoft Forefront Security for Office Communications Server (FSOCS) and the OCS 2007 or OCS 2007 R2 server it is running on. This information consists of FSOCS version information, third-party scan engine versions, the registry settings, and FSOCS databases. Gathering this configuration information is a major effort that can hinder the troubleshooting process.

To make it easier for you to collect this information, the Forefront Security Diagnostic tool (FSCDiag) automates the process, assembling all the necessary data in one file that can then be uploaded to Microsoft. When you contact Microsoft support, you will be told where to upload the file. For more information about support, see FSOCS troubleshooting.

The Forefront Security Diagnostic tool can collect any or all of the following information, based on your requests:

  • Forefront file versions (including scan engine file versions)
  • Forefront registry key
  • Forefront database (*.fdb) files
  • Forefront archive files
  • Forefront program log file
  • Windows event log files
  • Dr. Watson log file
  • User.dmp file
  • Forefront installation log file
  • OCS SIP application settings log
  • OCS SIP priority log
  • OCS file versions log
  • OCS role log
  • Forefront Hotfix installation log

The selected data is gathered and compressed into a single file in order to be uploaded to Microsoft.

To run the Forefront Security Diagnostic tool
  1. In Windows Explorer, navigate to the FSOCS installation folder. The following is the default location: C:\Program Files\Microsoft Forefront Security\Office Communications Server

  2. Double-click FSCDiag.exe. The tool runs in a command prompt window. FSCDiag normally runs silently, gathering all possible information.
    If you want to selectively gather information by running the program in interactive mode, in a command prompt window, entering the following:

    FSCDiag -i
    

    In this case, you are prompted for each item, as follows:

    • If you are in interactive mode, to select the information to be included, at each of the following prompts, type "yes" or "no", and then press ENTER.
    • Add Forefront file versions Yes(Y)/No(N) ?
    • Add IM versions Yes(Y)/No(N) ?
    • Add Forefront registry key Yes(Y)/No(N) ?
    • Add Forefront database files Yes(Y)/No(N) ?
    • Add Forefront archive files Yes(Y)/No(N) ?
    • Add Forefront program log Yes(Y)/No(N) ?
    • Add Windows Event log Yes(Y)/No(N) ?
    • Add Dr. Watson log Yes(Y)/No(N) ?
    • Add User.dmp Yes(Y)/No(N) ?
    • Add Forefront install.log Yes(Y)/No(N) ?
    • Add OCS SIP application settings log Yes(Y)/No(N) ?
    • Add OCS SIP priority log Yes(Y)/No(N) ?
    • Add OCS file versions log Yes(Y)/No(N) ?
    • Add OCS role log Yes(Y)/No(N) ?
    • Add Forefront Hotfix install log Yes(Y)/No(N) ?
  3. After you execute the command (or after the final prompt if you use interactive mode), the tool gathers the requested information and compresses the results into a new file in the Log\Diagnostics folder (in the FSOCS installation directory). The file name, constructed from the name of the server, the date, and the time, has the following format:

    ForefrontDiag-server name-date-time.zip

    where date has the format yyyymmdd and time has the format hh.mm.ss (where hh represents a 24-hour clock).

    The following is an example of the full path and file name:

    C:\Program Files\Microsoft Forefront Security\Office Communications Server\Log\Diagnostics\ForefrontDiag-Server1-20080210-17.50.27.zip

  4. Upload the compressed file to Microsoft.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft