Revision Summary Date Revision History Revision Class Comments 12/16/2011 1.0 New Released new document. 3/30/2012 2.0 Major Updated and revised the technical content. 7/12/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 3.0 Major Updated and revised the technical content. 11/14/2013 4.0 Major Updated and revised the technical content. 2/13/2014 4.0 None No changes to the meaning, language, or formatting of the
Dependencies on Systems/Components The File Management Services system depends on the following external systems and components: Object Used to store files and metadata. Active Directory system: Used to store Distributed File System (DFS) namespace metadata. If an Active Directory system is unavailable, an administrator cannot create a domain-based Distributed File System (DFS) namespace and cannot use the Distributed File System Replication (DFS-R) Services. Authentication Services system: Used to authenticate admin clients and the admin server. The Authentication services are described in the Authentication Services Protocols Overview . Assumptions and Preconditions The following assumptions and preconditions for the File Services Management system to operate successfully: System availability: The File Services Management system must be installed on all computers involved. Domain configuration: In a domain configuration, file clients and file services have access to that are provided by the domain. Authentication services: Authentication services, as described in , are available to all file clients and file services. RPC: Components of the file client and file services that use remote procedure call (RPC) interfaces have all prerequisites satisfied, as described in section 1.5. Network configuration: For system components that are running on different computers to communicate, the network services and infrastructure are functional and configured in such a way that required protocols, ports, and so on are remotely accessible. Domain functionality: For system functionality that requires a domain and directory services, as described in , at least one domain controller is configured and accessible. Some functionality could require an Active Directory domain as noted in individual technical documents. Use Share Management Use Cases Share Management use cases describe the management activities that the administrator performs to control a shared resource by using the admin tool. The share management activity includes the following share tasks: Creation Enumeration Getting and setting information Deletion The following diagram shows the Share Management use cases that are described in detail in the following sections.
A 55 15 9 17 C 54 75 71 55 17 17 17 17 9 Considerations 55 55 67 60 64 66 69 57 D 58 17 17 17 18 24 31 36 40 18 48 Dfs use cases 24 Dfs-r configuration and monitoring use cases 31 E 17 54 Examples 71 67 60 64 66 69 57 58 Extensibility ( 54, 73) 73 17 F 9 9 G 5 H 54 I 73 55 7 17 5 M 60 73 O Overview 15 9 P 17 73 R 7 Requirements 55 54 9 17 Resource management use cases 36 S 55 Server management use cases 40 Share management use cases 18 Smb redirector use cases 48 9 17 17