7 Appendix B: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

• Windows Vista operating system

• Windows Server 2008 operating system

• Windows 7 operating system

• Windows Server 2008 R2 operating system

• Windows 8 operating system

• Windows Server 2012 operating system

• Windows 8.1 operating system

• Windows Server 2012 R2 operating system

• Windows 10 operating system

• Windows Server 2016 operating system

• Windows Server operating system

• Windows Server 2019 operating system

• Windows Server 2022 operating system

• Windows 11 operating system

• Windows Server 2025 operating system

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 1: The following table lists the interfaces common to all storage management modules by operating system version.

 The following table lists the Class IDs for interfaces common to all storage management by operating system version.

<2> Section 1.3: The FSRM server is implemented by the Windows File Server Resource Manager and File Server Storage Reports services. An FSRM client is implemented by a number of components, including the Windows File Server Resource Manager management console and the DIRQUOTA.EXE, FILESCRN.EXE, and STORREPT.EXE command–line tools [MSFT-WINCMD].

<3> Section 1.4: Windows 8 operating system and later, Windows Server 2012 operating system and later are the only versions of Windows that interact with Active Directory to synchronize the property definitions locally.

<4> Section 1.5: On Windows, the server for an FSRM classification module or storage module is registered as a COM server. See [MSDN-COMCLTSERVS] for more information.

<5> Section 1.6: Windows Server 2008 and Windows Server 2008 R2 operating system implement the File Server Resource Manager Protocol.

<6> Section 1.7: The following table lists the interfaces common to all storage management by operating system version.

 The following table lists the Class IDs for interfaces common to all storage management by operating system version.

The following table lists the interfaces common to all storage management by the Remote Server Administration Tools (RSAT) package for Windows client OS versions.

The following table lists the Class IDs for interfaces common to all storage management by the Remote Server Administration Tools (RSAT) package for Windows client OS versions.

<7> Section 2.1:

The authorization constraints in Windows do not vary by operating system release. All interfaces described in this document require a level of access corresponding to any of the following Windows security groups, excluding the interfaces that require only that the caller be an authenticated user:

• Administrators

• Backup Operators

• SYSTEM

The following interfaces require only that the caller be an authenticated user on the machine:

• IFsrmClassificationManager::EnumPropertyDefinitions

• IFsrmClassificationManager::GetPropertyDefinition

• IFsrmClassificationManager::EnumFileProperties

• IFsrmClassificationManager::GetFileProperty

• IFsrmClassificationManager::SetFileProperty

• IFsrmClassificationManager::ClearFileProperty

• IFsrmClassificationManager2::ClassifyFiles

• IFsrmCollection::*

• IFsrmMutableCollection::*

• IFsrmObject::*

• IFsrmPropertyDefinition::Name (get)

• IFsrmPropertyDefinition::Name (put)

• IFsrmPropertyDefinition::Type(get)

• IFsrmPropertyDefinition::Type(put)

• IFsrmPropertyDefinition::PossibleValues (get)

• IFsrmPropertyDefinition::PossibleValues (put)

• IFsrmPropertyDefinition::ValueDescriptions (get)

• IFsrmPropertyDefinition::ValueDescriptions (put)

• IFsrmPropertyDefinition::Parameters(get)

• IFsrmPropertyDefinition::Parameters (put)

• IFsrmPropertyDefinition2::DisplayName (get)

• IFsrmPropertyDefinition2::DisplayName (put)

• IFsrmPropertyDefinition2::AppliesTo (get)

• IFsrmPropertyDefinition2::AppliesTo (put)

• IFsrmPropertyDefinition2::PropertyDefinitionFlags

• IFsrmProperty::*

<8> Section 2.1:

Windows configures the underlying RPC transport with the following flags. The meanings of the following flags are specified in [C706] and [MS-RPCE]:

• RPC_C_AUTHN_LEVEL_PKT_PRIVACY

• RPC_C_IMP_LEVEL_IDENTIFY

• EOAC_SECURE_REFS | EOAC_NO_CUSTOM_MARSHAL

<9> Section 2.2: Unless otherwise stated, all FSRM data types and messages are supported in Windows Server 2008 and Windows Server 2008 R2.

<10> Section 2.2.1.2.8: This value corresponds to the predefined NetworkService account in Windows as described in [MSDN-NetworkSvcAcct].

<11> Section 2.2.1.2.8: This value corresponds to the predefined LocalService account in Windows as described in [MSDN-LocSvcAcct].

<12> Section 2.2.1.2.8: This value corresponds to the predefined LocalSystem account in Windows as described in [MSDN-LocSysAcct].

<13> Section 2.2.1.2.8: The COM module needs to be registered as an in-proc COM server. See [MSDN-COMCLTSERVS] for more information.

<14> Section 2.2.1.2.8: The actual account under which the module definition is running depends upon how the module definition was registered as an out-of-process COM server. See [MSDN-COMCLTSERVS] for more information.

<15> Section 2.2.1.2.8: Windows 8 operating system and later, Windows Server 2012 operating system and later are the only versions of Windows that use the FsrmAccountType_Automatic enumeration value.

<16> Section 2.2.1.2.10: In Microsoft Windows, duplicate files are files that have the same name and physical size.

<17> Section 2.2.1.2.18: Windows 8 operating system and later, Windows Server 2012 operating system and later will always set this flag while writing the FCIADS stream. Windows Server 2008 R2 will never set this flag.

<18> Section 2.2.2.3.1.1: FsrmPropertyDefinitionType_SingleChoiceList is not supported in Windows Vista operating system and later, and Windows Server 2008 operating system and later support FsrmPropertyDefinitionType_SingleChoiceList.

<19> Section 2.2.2.4: Windows 8 operating system and later, and Windows Server 2012 operating system and later are the only versions of Windows that implement the IFsrmPropertyDefinition2 data types.

<20> Section 2.3: Windows 8 operating system and later, and Windows Server 2012 operating system and later are the only versions of Windows that interact with Active Directory to synchronize property definitions locally.

<21> Section 3.1.1: Windows 8 and later populate the available Resource Property Lists using Group Policy from the domain. Group Policy updates the following registry key:

HKLM\SOFTWARE\Policies\Microsoft\Windows\FCI

If this key is not available, the ADSyncListName is set to "Global Resource Property List". If the key has more than one value available, the ADSyncListName can be set to the name of any of the lists that are to be synchronized.

<22> Section 3.1.4.1.5: The IFsrmStorageModuleDefinition::Commit method is supported only for local use on all Windows implementations. Remote operations are not advised.

<23> Section 3.2.1.5.1: Windows Server 2012 operating system and later, and Windows Server 2012 R2 operating system and later are the only versions of Windows that accept dynamic path entries.

<24> Section 3.2.1.5.2: Windows Server 2012 operating system and later, and Windows Server 2012 R2 operating system and later are the only versions of Windows that maintain deprecated state data for each report.

<25> Section 3.2.1.5.3: This property is initialized to "%SystemDrive%\StorageReports\Scheduled"".

<26> Section 3.2.1.5.3: This property is initialized to "%SystemDrive%\StorageReports\Interactive"".

<27> Section 3.2.1.5.3: This property is initialized to "%SystemDrive%\StorageReports\Incident"".

<28> Section 3.2.1.6.1: Windows Server 2012 operating system and later, and Windows Server 2012 R2 operating system and later are the only versions of Windows that maintain this data.

<29> Section 3.2.1.6.1: Windows Server 2012 operating system and later, and Windows Server 2012 R2 operating system and later are the only versions of Windows that maintain this data. Valid values are:

• Files

• Folders

• Files and Folders

<30> Section 3.2.1.6.1: Windows Server 2012 operating system and later, and Windows Server 2012 R2 operating system and later are the only versions of Windows that maintain this data.

<31> Section 3.2.1.6.1: Windows Server 2012 operating system and later, and Windows Server 2012 R2 operating system and later are the only versions of Windows that maintain this data.

<32> Section 3.2.1.6.1: Windows Server 2012 operating system and later, and Windows Server 2012 R2 operating system and later are the only versions of Windows that maintain this data.

<33> Section 3.2.1.6.1: Windows Server 2012 operating system and later, and Windows Server 2012 R2 operating system and later are the only versions of Windows that maintain this data.

<34> Section 3.2.1.6.1.3: The Property Value Definition.Display Name, Property Value Definition.Description, and Property Value Definition.UniqueId configuration items are maintained only by Windows 8 and later.

<35> Section 3.2.1.6.2: The COM class has to be registered before the module definition can be committed with its class identifier. See [MSDN-COMCLTSERVS] for details.

<36> Section 3.2.1.6.3: Windows Server 2012 operating system and later, and Windows Server 2012 R2 operating system and later are the only versions of Windows that accept dynamic path entries.

<37> Section 3.2.1.6.3: Only Windows 8.1 operating system and later, and Windows Server 2012 R2 operating system and later maintain this data.

<38> Section 3.2.1.6.3: Windows Server 2012 operating system and later are the only versions of Windows that maintain this data.

<39> Section 3.2.1.6.3: Only Windows 8.1 operating system and later, and Windows Server 2012 R2 operating system and later maintain this data.

<40> Section 3.2.1.6.3: Only Windows 8.1 operating system and later, and Windows Server 2012 R2 operating system and later maintain this data.

<41> Section 3.2.1.6.4: Windows Server 2008 and Windows Server 2008 R2 maintain a single classification job.

<42> Section 3.2.1.6.4: Windows Server 2012 operating system and later are the only versions of Windows that maintain this data.

<43> Section 3.2.1.7.1: In Windows, the file management job name is used as a foreign key to associate the file management job with a Windows Task Scheduler scheduled task.

<44> Section 3.2.1.7.1: Windows Server 2012 operating system and later are the only versions of Windows that accept dynamic path entries.

<45> Section 3.2.1.7.1: If a file management job is set to generate a report and the report job fails, then the server will set the last report without extension property to the location where the reports would have been located had the job succeeded.

<46> Section 3.2.1.7.1: Windows Server 2012 operating system and later are the only versions of Windows that maintain this data.

<47> Section 3.2.1.8: Windows Server 2012 operating system and later are the only versions of Windows that maintain the FolderUsage list. The value is synchronized with the msDS-ClaimPossibleValues of the Active Directory property definition during Active Directory synchronization (section 3.2.1.12.5).

<48> Section 3.2.1.8: Windows Server 2012 operating system and later are the only versions of Windows that maintain the FolderUsage mapping.

<49> Section 3.2.1.12.1: Windows Server 2012 operating system and later are the only versions of Windows that skip the remaining report formats when the Report Job is deprecated.

<50> Section 3.2.1.12.1: In Windows, duplicate files are files that have the same name and physical size.

<51> Section 3.2.1.12.5: Windows 8 operating system and later synchronize when the client joins a domain. Windows Server 2012 operating system and later synchronize every 15 minutes if an error occurs; otherwise, once every hour.

<52> Section 3.2.3: Only Windows 8.1, Windows Server 2012 R2 operating system and later support this behavior.

<53> Section 3.2.4.2.1.5: This method is not supported and always returns S_OK.

<54> Section 3.2.4.2.1.6: This method is not supported.

<55> Section 3.2.4.2.11.13: If the Run limit interval is not present for actionType, the server uses 60 minutes for delayTimeMinutes.

<56> Section 3.2.4.2.15.3: This method is not supported.

<57> Section 3.2.4.2.15.4: This method is not supported.

<58> Section 3.2.4.2.17.3: Windows will only exclude subdirectories that exist at the time when the IFsrmAutoApplyQuota object is committed. Folders that are created after the commit that match an entry of the exclude folder array are not excluded.

<59> Section 3.2.4.2.17.4: When this method is called, the IFsrmAutoApplyQuota (section 3.2.4.2.17) object is committed. However, only changes made using the IFsrmQuotaObject::ApplyTemplate (section 3.2.4.2.15.7)  method  are applied to quota objects derived from this IFsrmAutoApplyQuota object, based on the value of applyOptions supplied by the client.

<60> Section 3.2.4.2.33.2: Windows-based servers use "01/01/1900 12:00AM" for this value.

<61> Section 3.2.4.2.34.15: Windows Server 2008 is the only version of Windows that does not implement the FsrmReportType_FilesByProperty value of FsrmReportType (section 2.2.1.2.10).

<62> Section 3.2.4.2.34.15: Windows Server 2008 is the only version of Windows that does not implement the FsrmReportType_FilesByProperty value of FsrmReportType.

<63> Section 3.2.4.2.36.2: The XML schema for the task that is used in the Windows implementation of this protocol is the Task Scheduler task XML schema. For more information, see [MS-TSCH].

<64> Section 3.2.4.2.36.3: The XML schema for the task that is used in the Windows implementation of this protocol is the Task Scheduler task XML schema. For more information, see [MS-TSCH].

<65> Section 3.2.4.2.37.1: FsrmPropertyDefinitionType_SingleChoiceList is not supported in Windows Vista operating system and later, and Windows Server 2008 operating system and later support FsrmPropertyDefinitionType_SingleChoiceList.

<66> Section 3.2.4.2.37.5: FsrmPropertyDefinitionType_SingleChoiceList is not supported in Windows Vista operating system and later, and Windows Server 2008 operating system and later support FsrmPropertyDefinitionType_SingleChoiceList.

<67> Section 3.2.4.2.45.12: Windows Server 2012 operating system and later, Windows Server 2012 R2 operating system and later are the only versions of Windows that implement IFsrmPropertyDefinition2.

<68> Section 3.2.4.2.45.14: Windows 8 operating system and later, and Windows Server 2012 operating system and later are the only versions of Windows that implement IFsrmPropertyDefinition2.

<69> Section 3.2.4.2.45.16: Only Windows 8.1 operating system and later, and Windows Server 2012 R2 operating system and later support this behavior.

<70> Section 3.2.4.2.45.16: Only Windows 8.1 operating system and later, and Windows Server 2012 R2 operating system and later support this behavior.

<71> Section 3.2.4.2.45.24: This behavior is supported only on Windows 8 and later.

<72> Section 3.2.4.2.47.1: The IFsrmStorageModuleDefinition::Commit method is supported only for local use on all Windows implementations. Remote operations are not advised.

<73> Section 3.2.4.2.47.2: The Capabilities (get) method is supported only for local use on all Windows implementations. Remote operations are not advised.

<74> Section 3.2.4.2.47.3: The Capabilities (put) method is supported only for local use on all Windows implementations. Remote operations are not advised.

<75> Section 3.2.4.2.47.4: The StorageType (get) method is supported only for local use on all Windows implementations. Remote operations are not advised.

<76> Section 3.2.4.2.47.5: The StorageType (put) method is supported only for local use on all Windows implementations. Remote operations are not advised.

<77> Section 3.2.4.2.47.6: The UpdatesFileContent (get) method is supported only for local use on all Windows implementations. Remote operations are not advised.

<78> Section 3.2.4.2.47.7: The UpdatesFileContent (put) method is supported only for local use on all Windows implementations. Remote operations are not advised.

<79> Section 3.2.4.2.48.47: Windows-based servers use "01/01/1900 12:00AM" for this value.

<80> Section 3.2.5.2: If the relevant classification module has a value in its Module Definition.Parameters containing "StaticModuleName=Content Classifier", Windows can also process values in the relevant classification module's Module Definition.Parameters that start with "IFilterInitFlags", "MaxTokenSize", "ReadBufferSize", "ChunkBreakType", "RegexOptions", or "AppDomain" for performance purposes. However, these have no impact on functionality.

<81> Section 3.2.5.2: Only Windows 8.1 operating system and later, and Windows Server 2012 R2 operating system and later support the ClearProperty.

<82> Section 3.2.5.2: Only Windows 8.1 operating system and later, and Windows Server 2012 R2 operating system and later support the ClearProperty.

<83> Section 3.2.5.2: Only Windows 8.1 operating system and later, and Windows Server 2012 R2 operating system and later support the ClearProperty.

<84> Section 3.2.5.2: Only Windows 8.1 operating system and later, and Windows Server 2012 R2 operating system and later support the ClearProperty.

<85> Section 3.2.7.10: In Windows, the FCI Alternate Data Stream is supported for the files on a fixed NTFS volume.