<?xml version="1.0" encoding="UTF-16"?>
<SCWLocalization LocaleID="0409">
	<RoleLocalization>
		<Role Name="FSRM">
			<DisplayName>File Server Resource Manager server</DisplayName>
			<Description>A file server resource manager server provides a suite of tools that allows administrators to understand, control, and manage the quantity and type of data stored on their servers. </Description>
		</Role>
		<!-- Begin ADFS Roles-->
		<Role Name="ADFS_FS_AND_PROXY">
			<DisplayName>AD Federation Service Or AD Federation Service Proxy</DisplayName>
			<Description>The Federation Service functions as a security token service for federated identities. The Federation Service Proxy is setup in a perimeter network to to act as a proxy for federation requests.</Description>
		</Role>
		<Role Name="ADFS_WS">
			<DisplayName>ADFS Web Agent</DisplayName>
			<Description>Provides ADFS authentication for claims-aware or Windows NT token-based applications.</Description>
		</Role>
		<!-- End ADFS Roles-->
		<Role Name="WEC">
			<DisplayName>Event Collector</DisplayName>
			<Description>The Windows Event Collector Service logs events forwarded from remote computers or IPMI devices.</Description>
		</Role>
		<Role Name="SUA">
			<DisplayName>SUA Subsystem Startup</DisplayName>
			<Description>This service is used to bootstrap SUA</Description>
		</Role>
		<Role Name="SNIS">
			<DisplayName>Server for NIS</DisplayName>
			<Description> Server for NIS is an implementation of Sun Network Information System (NIS) server in a Windows server, which uses Active Directory to store NIS maps. It provides complete compatibility with the NIS specifications, and interoperates with other NIS servers and clients in the network. Server for NIS, running on a Windows-based server, can be used as an NIS server in place of a UNIX-based server.

</Description>
		</Role>
		<Role Name="UNMServer">
			<DisplayName>User Name Mapping</DisplayName>
			<Description>User Name Mapping, a component of Microsoft Services for NFS, associates UNIX users and groups with their corresponding Windows users and groups.  This allows other components of Microsoft Services for NFS, such as Server for NFS, to automatically authenticate a UNIX user attempting to access a file as their corresponding Windows user.</Description>
		</Role>
		<Role Name="NFSServer">
			<DisplayName>Server for NFS</DisplayName>
			<Description>Server for NFS, a component of Microsoft Services for NFS, shares folders and files on a Windows computer with UNIX computers via the Network File System (NFS) protocol.</Description>
		</Role>
		<Role Name="NFSClient">
			<DisplayName>Client for NFS</DisplayName>
			<Description>Client for NFS, a component of Microsoft Services for NFS, allows Windows users to access files and folders on UNIX computers via the Network File System (NFS) protocol.</Description>
		</Role>
		<Role Name="DFSR">
			<DisplayName>DFS Replication</DisplayName>
			<Description>Replicates files among multiple servers to provide high availability and local access across a wide area network (WAN). If the service is stopped, file replication does not occur, and the files on the server become out-of-date. If the service is disabled, any services that explicitly depend upon it will not start.</Description>
		</Role>
	</RoleLocalization>
	<TaskLocalization>
		<Task Name="FSRMRemoteAdmin">
			<DisplayName>Remote File Server Resource Manager administration</DisplayName>
			<Description>The File Server Resource Manager server is managed remotely using the File Server Resource Manager snap-in or the dirquota.exe, filescrn.exe, and storrept.exe command line tools.</Description>
			<Details>This option does not need to be selected if you remotely manage this server using Terminal Server for Remote Desktop Administration.</Details>
			<SCWDetails>Enabling or disabling this option has no effect unless you also plan on configuring the Windows Firewall.</SCWDetails>
		</Task>
		<Task Name="DFSAdministration">
			<DisplayName>DFS remote administration</DisplayName>
			<Description>Allows administration and reporting of DFS replication and DFS namespaces.</Description>
			<Details>Select this option if the server will host replication groups or namespaces and administration will be performed from a remote computer.</Details>
			<SCWDetails>Enabling or disabling this option has no effect unless you also plan on configuring the Windows Firewall.</SCWDetails>
		</Task>
		<Task Name="WinRM">
			<DisplayName>Windows Remote Management (WS-Management)</DisplayName>
			<Description>The Windows Remote Management Service provides firewall-friendly remote administration using Web Services.</Description>
			<SCWDetails>The Remote Management Service must be enabled to listen on one or more network ports using HTTP and HTTPS. Ports 80 and 443 are enabled by default, and should be disabled if not being used. Other ports must be added manually with the Security Configuration Wizard tool.</SCWDetails>
		</Task>
		<Task Name="RemoteNFSAdmin">
			<DisplayName>Remote NFS administration</DisplayName>
			<Description>Administrators can manage components of Microsoft Services for NFS, such as Server for NFS, remotely.</Description>
			<Details>You do not need to select this task if you use Remote Desktop or Terminal Server to remotely manage this server.</Details>
		</Task>
	</TaskLocalization>
	<ServiceLocalization>
		<Service Name="SrmSvc">
			<DisplayName>File Server Resource Manager</DisplayName>
		</Service>
		<Service Name="SrmReports">
			<DisplayName>File Server Storage Reports Manager</DisplayName>
		</Service>
		<!-- Begin ADFS Services-->
		<Service Name="IFSSVC">
			<DisplayName>ADFS Web Agent Authentication Service</DisplayName>
		</Service>
		<!-- End ADFS Services-->
		<Service Name="WinRM">
			<DisplayName>Windows Remote Management Service</DisplayName>
		</Service>
		<Service Name="WECSVC">
			<DisplayName>Windows Event Collector Service</DisplayName>
		</Service>
		<Service Name="zzSUA">
			<DisplayName>Subsystem for UNIX-based Applications</DisplayName>
		</Service>
		<Service Name="SSNIS">
			<DisplayName>Server for NIS Service</DisplayName>
		</Service>
		<Service Name="mapsvc">
			<DisplayName>User Name Mapping</DisplayName>
		</Service>
		<Service Name="nfssvc">
			<DisplayName>Server for NFS</DisplayName>
		</Service>
		<Service Name="Client for NFS">
			<DisplayName>Client for NFS</DisplayName>
		</Service>
		<Service Name="DFSR">
			<DisplayName>DFS Replication</DisplayName>
		</Service>
	</ServiceLocalization>
	<PortLocalization>
		<Port Name="FSRMReportsHost">
			<DisplayName>Remote administration for File Server Resource Manager reports</DisplayName>
			<Description>Used for remote administration of a File Server Resource Manager reports service.</Description>
		</Port>
		<Port Name="portmap">
			<DisplayName>RPC Port Mapper</DisplayName>
			<Description>Network services, such as Server for NFS and User Name Mapping, register their port numbers with RPC Port Mapper.  Clients needing to connect to such services, can query RPC Port Mapper, which listens on a well-known port, to discover which ports to which the network services listen.</Description>
			<Details>You must open this port for Server for NFS and User Name Mapping to function correctly.</Details>
		</Port>
		<Port Name="UNM">
			<DisplayName>User Name Mapping</DisplayName>
			<Description>User Name Mapping, a component of Microsoft Services for NFS, associates UNIX users and groups with their corresponding Windows users and groups.  This allows other components of Microsoft Services for NFS, such as Server for NFS, to automatically authenticate a UNIX user attempting to access a file as their corresponding Windows user.</Description>
		</Port>
		<Port Name="mount">
			<DisplayName>NFS Mount</DisplayName>
			<Description>Server for NFS uses the NFS mount protocol to allow NFS clients to connect to NFS shares on this computer.</Description>
			<Details>The Windows registry stores the port number on which the NFS mount protocol resides.  If the registry stores a zero for this protocol, then Server for NFS defaults to port number 1048.</Details>
		</Port>
		<Port Name="NFS-Server">
			<DisplayName>NFS Server</DisplayName>
			<Description>Server for NFS uses the NFS server protocol to allow NFS clients to access files and folders on NFS shares.</Description>
			<Details>The Windows registry stores the port number on which the NFS server protocol resides.  If the registry stores a zero for this protocol, then Server for NFS defaults to port number 2049.</Details>
		</Port>
		<Port Name="NLM">
			<DisplayName>NFS Network Lock Manager</DisplayName>
			<Description>Server for NFS uses the Network Lock Manager protocol to allow NFS clients to lock and unlock files on NFS shares.</Description>
			<Details>The Windows registry stores the port number on which the Network Lock Manager protocol resides.  If the registry stores a zero for this protocol, then Server for NFS defaults to port number 1047.</Details>
		</Port>
		<Port Name="NSM">
			<DisplayName>NFS Network Status Manager</DisplayName>
			<Description>Server for NFS uses the Network Status Manager protocol to allow NFS clients to discover NFS server status.</Description>
			<Details>The Windows registry stores the port number on which the Network Status Manager protocol resides.  If the registry stores a zero for this protocol, then Server for NFS defaults to port number 1039.</Details>
		</Port>
		<Port Name="NFS-Client">
			<DisplayName>NFS Client</DisplayName>
			<Description>Client for NFS, a component of Microsoft Services for NFS, allows Windows users to access file and folders on UNIX computers via the Network File System (NFS) protocol.</Description>
			<Details>NFS details.</Details>
		</Port>
		<Port Name="DFSR">
			<DisplayName>DFS Replication</DisplayName>
			<Description>DFS Replication replicates files among multiple servers to provide high availability and local access across a wide area network (WAN).</Description>
			<Details>This port must be open for file replication to occur with DFS Replication.</Details>
		</Port>
	</PortLocalization>
</SCWLocalization>
