For each file screen, FSRM sends only one notification within each notification interval. By default, the notification interval is 60 minutes. You can change this interval by using the Filescrn.exe utility together with configuration files.
Note If you set the notification interval to a period that is too short, FSRM may generate excessive events and e-mail messages. Therefore, you may experience performance reduction.
You can set the RunLimitInterval parameter in text-based configuration files to change the notification interval from the default of 60 minutes. This parameter value is the number of minutes that FSRM will wait until it sends another notification for the same file screen. When this value is set to 0 (zero), FSRM sends notifications every time that a user operation triggers a file screen.
FSRM sends only one notification within each notification interval for a file screen even though the file screen is triggered by different users, or by different file types, or by different file groups. All file screen triggers are ignored other than the first file screen trigger until the interval expires or until the interval is reset. Any of the following operations resets the interval:
- You restart the FSRM service.
- You restart the server that hosts the FSRM service.
- You open and close the properties for the file screen.
Create FSRM configuration files to change notification behaviorTo change the notification behavior, create files that have a .txt file name extension to use as configuration files, and then use the filescrn command to apply the configuration files. To do this, follow these steps:
- For e-mail notification, create a configuration file that has a .txt file name extension, and then include the parameters that you want to change. The following is an example file:Note You do not have to specify all parameters in the configuration file. For example, you can create a file that contains only one parameter, such as the RunLimitInterval parameter, if you want to change nothing but that parameter.
Subject=This is a mail subject
Message = This is a mail message body
- For event notification, create a .configuration file that has a .txt file name extension, and then include the parameters that you want to change. The following is an example file:
Message=Message For Event Log
- Run the following command at the command prompt to apply the configurations in the files that you created in step 1 and step 2:
Filescrn screen modify /path:<ScreenPath> /Modify-Notification:M,<c:\email.txt> /Modify-Notification:E,<c:\eventlog.txt>
The following definitions are for the placeholders that are used in step 3:
- <ScreenPath> is the path that the file screen is applied to.
- <c:\email.txt> is the configuration file that you created in step 1 to use for e-mail notifications.
- <c:\eventlog.txt> is the configuration file that you created in step 2 to use for event notifications.
Technical support for x64-based versions of Microsoft WindowsIf your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Microsoft Windows Server 2003 x64 edition separately, contact Microsoft for technical support.
For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site:
Article ID: 926092 - Last Review: Mar 10, 2009 - Revision: 1