IFsrmFileScreen interface
[This interface is supported for compatibility but it's recommended to use the FSRM WMI Classes to manage FSRM. Please see the MSFT_FSRMFileScreen class.]
Used to configure a file screen that blocks groups of files from being saved to the specified directory.
To create this interface, call the IFsrmFileScreenManager::CreateFileScreen method.
The following methods return this interface:
Members
The IFsrmFileScreen interface inherits from IFsrmFileScreenBase. IFsrmFileScreen also has these types of members:
Methods
The IFsrmFileScreen interface has these methods.
| Method | Description |
|---|---|
| ApplyTemplate |
Applies the property values of the specified file screen template to this file screen object. |
Properties
The IFsrmFileScreen interface has these properties.
| Property | Access type | Description |
|---|---|---|
| Read-only |
Retrieves a value that determines whether the property values of this file screen object match those values of the template from which the object was derived. | |
| Read-only |
Retrieves the path of the directory to which the file screen object applies. | |
| Read-only |
Retrieves the name of the template from which this file screen object was derived. | |
| Read-only |
The account name of the user whose files will be screened | |
| Read-only |
The SID of the user whose files will be screened |
Remarks
A file screen limits the types of files that the system or any user can store in a directory. When a restricted file is detected, the FSRM server performs the specified actions (see IFsrmFileScreenBase::CreateAction).
The file screen applies to future files—the screen is not applied retroactively. To list the files in the directory that violate the screen, create a report job that lists files by type.
Requirements
|
Minimum supported client | None supported |
|---|---|
|
Minimum supported server | Windows Server 2008 |
|
Header |
|
|
IDL |
|
|
DLL |
|
|
IID |
IID_IFsrmFileScreen is defined as 5f6325d3-ce88-4733-84c1-2d6aefc5ea07 |
See also
Send comments about this topic to Microsoft
Build date: 12/6/2012
