Revision Summary Date Revision History Revision Class Comments 12/16/2011 1.0 New Released new document. 3/30/2012 2.0 Updated and revised the technical content. 7/12/2012 3.0 Major Updated and revised the technical content. 10/25/2012 3.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 3.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 4.0 Major Updated and revised the technical content. 11/14/2013 4.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 4.0 None No changes to the meaning, language, or formatting of the
technical content. 5/15/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 5.0 Major Significantly changed the technical content. 9/24/2015 5.1 Minor Clarified the meaning of the technical content. 10/16/2015 5.1 None No changes to the meaning, language, or formatting of the technical content. 9/26/2016 5.2 Minor Clarified the meaning of the technical content.
Stakeholders File owner: The user who is the owner of the file that needs to be encrypted. Preconditions The file owner user has identified the file that needs to be encrypted. The file user has the required EFS certificates. Main success scenario Trigger: The file requests to encrypt a file by using the Admin Tool. The Admin Tool requests that the Admin Client establish a communication channel to the EFS service of the Storage Services protocols. The Admin Client contacts the EFS service to query information about the keys that are used to encrypt the file by using the EfsRpcFileKeyInfo method, as described in [MS-EFSR] section 3.1.4.2.12. The EFS service responds with the required keys information. The Client contacts the EFS service to encrypt the file by using the EfsRpcEncryptFileSrv or EfsRpcEncryptFileExSrv method, as described in [MS-EFSR] sections 3.1.4.2.5 and 3.1.4.2.19. The EFS service encrypts the requested file. Postcondition The required encryption of the file has finished successfully. Extensions If the communication channel for the Encrypting File System Remote (EFSRPC) Protocol cannot be established, or it becomes disconnected, the Admin Client attempts to establish a connection multiple times until it fails. Whether the required encryption of the file has finished or not depends on when the connection failed. Decrypt an Encrypted File Goals Decrypt a file. Context of Use The file owner is decrypting a file. Actors Admin Tool: A Microsoft Management Console (MMC) component, which is used by the administrator to configure the storage on the server. Admin Client: The Admin Client is the primary actor. The Admin Client is code that is running on the administrator's computer. The Admin Client implements client-side protocol components and consumes the storage services that are offered by the storage server. The Admin Client's interest is to correctly interpret, execute, and display the results of the commands that are issued by administrator.
Storage Services protocols 3.0 RSMP, DMRP, EFSR, VDS, SCMP VDS is a preferred protocol over DMRP.<9> Storage Services protocols 4.0 VDS, SCMP Storage Services protocols 5.0 RSMP, EFSR, VDS Storage Services protocols 6.0 EFSR, VDS Storage Services protocols 7.0 RSMP, EFSR, VDS, SCMP Storage Services protocols 8.0 EFSR, VDS, SCMP Storage Services protocols 9.0 EFSR, VDS, FSRVP Storage Services protocols 10.0 EFSR, VDS, SCMP, FSRVP Any deviations from a specific version's implementation of these protocol specifications are documented in the respective protocol documents. Capability negotiations between client and server implementations of these protocols are described in the Versioning and Capability Negotiation sections in the respective protocol specifications. There are no extensions of the Storage Services protocols other than the extensions that are described in the respective protocols. Error Handling The Storage Services protocols do not define any error handling requirements beyond those that are described in the specifications of the protocols that are supported by the Storage Services system, as listed in section .
Index A 5 13 35 14 9 15 B Back Up and Restore Data use case 23 22 22 Backup and restore data 22 C Capabilities 12 13 12 13 12 34 48 35 15 15 15 15 15 9 37 Considerations 35 35 40 38 D 42 40 Dependencies 15 15 15 Design intent 22 22 30 30 16 16 26 26 16 E Encrypted file access control and encryption 30 Encrypted File Access Control and Encryption use case group 33 32 30 31 41 13 15 35 Examples 37 40 38 42 41 36 36 Extensibility 46 34 15 F 13 9 9 G 6 H 35 I 46 35 8 15 5 M 36 Manage disks and volumes 16 Manage and Volumes use case group 21 18 17 19 16 Manage removable media