# Localized	02/22/2014 02:57 PM (GMT)	303:4.80.0411 	NFS.psd1
ConvertFrom-StringData @'

###PSLOC start localizing

    #check DFSN service status
DFSNServiceStatusCheck_Title=DFSN service should be started
DFSNServiceStatusCheck_Problem=DFSN service is not started
DFSNServiceStatusCheck_Impact=DFSN will be NOT available
DFSNServiceStatusCheck_Resolution=start DFSN service
DFSNServiceStatusCheck_Compliant=The FileServices Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check DFSN namespace has been created
DFSNNamespaceCreationCheck_Title=There should be DFS namespace created
DFSNNamespaceCreationCheck_Problem=You haven't created any DFS namespace
DFSNNamespaceCreationCheck_Impact=DFSN will be NOT available
DFSNNamespaceCreationCheck_Resolution=use DFS management snapin to create DFS namespace
DFSNNamespaceCreationCheck_Compliant=The FileServices Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check FSRM service status
FSRMServiceStatusCheck_Title=FSRM service should be started
FSRMServiceStatusCheck_Problem=FSRM service is not started
FSRMServiceStatusCheck_Impact=FSRM will be NOT available
FSRMServiceStatusCheck_Resolution=startFSRM service
FSRMServiceStatusCheck_Compliant=The FileServices Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check FSRM service status on cluster
FSRMServiceStatusCheckOnCluster_Title=FSRM service status should be the same on all cluster nodes
FSRMServiceStatusCheckOnCluster_Problem=FSRM service should be running on all cluster nodes or none of the cluster nodes.
FSRMServiceStatusCheckOnCluster_Impact=There will be issue in cluster if this rule is not compliant
FSRMServiceStatusCheckOnCluster_Resolution=install FSRM service on all cluster nodes or remove FSRM service from all cluster nodes if you don't want to use FSRM in cluster
FSRMServiceStatusCheckOnCluster_Compliant=The FileServices Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # check NFS service status
    #
NFSServiceStatusCheck_Title=NFS service should be started
NFSServiceStatusCheck_Problem=NFS service is not started.
NFSServiceStatusCheck_Impact=Client computers will not be able to connect to the shares on the server using the NFS protocol.
NFSServiceStatusCheck_Resolution=Start the NFS service.
NFSServiceStatusCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # NFS rule 1 (warning, security) - Check for anonymous access
    #
NfsServiceUsingAnonymousLogon_Title=Anonymous access should be disabled.
NfsServiceUsingAnonymousLogon_Problem=Anonymous access is enabled on a Network File System (NFS) share
NfsServiceUsingAnonymousLogon_Impact=Anonymous users can access the share, which could be a security risk because the users could view files they shouldn't have permission to view. If write access is enabled, anonymous users could place viruses or other malicious software on the share.
NfsServiceUsingAnonymousLogon_Resolution=Disable anonymous access and use an identity mapping solution such as Active Directory Domain Services (AD DS), Active Directory Lightweight Directory Services (AD LDS), User Name Mapping Service, or any RFC2307-based solution.
NfsServiceUsingAnonymousLogon_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # NFS rule 2 (error, configuration) - check for domain functional level
    #
NfsDomainFunctionalLevelSufficient_Title=The domain functional level should be Windows Server 2003 R2 or higher when using an identity mapping solution
NfsDomainFunctionalLevelSufficient_Problem=The domain functional level is lower than Windows Server 2003 R2.
NfsDomainFunctionalLevelSufficient_Impact=Users will not be properly authenticated.
NfsDomainFunctionalLevelSufficient_Resolution=Use Active Directory Domains and Trusts to increase the domain functional level to Windows Server 2003 R2 or higher.
NfsDomainFunctionalLevelSufficient_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # NFS rule 3 (error, configuration) - check for mapping solution when intersecting NFS and SMB shares
    #
NfsSharingWithSMBWithoutMapping_Title=Folders that are shared by using both the SMB and NFS protocols should use mapped accounts
NfsSharingWithSMBWithoutMapping_Problem=A folder that is shared by using both the Server Message Block (SMB) protocol and the Network File System (NFS) protocol has Anonymous logon or Unmapped Unix User Access (UUUA) enabled.
NfsSharingWithSMBWithoutMapping_Impact=Users might not be able to access the same files by using the SMB protocol as they can by using the NFS protocol.
NfsSharingWithSMBWithoutMapping_Resolution=Use the File and Storage Services page of Server Manager or Set-NfsMappingStore Windows Powershell cmdlet to configure Server for Network File System to use an appropriate identity mapping solution for mapping Windows accounts to non-Windows accounts.
NfsSharingWithSMBWithoutMapping_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # NFS rule 5 (warning, configuration) - check for use of client groups
    #
NfsClientGroupsDefinedOrInUse_Title=Server for NFS should be configured to use Netgroups
NfsClientGroupsDefinedOrInUse_Problem=Server for Network File System (NFS) is configured to use ClientGroups instead of Netgroups.
NfsClientGroupsDefinedOrInUse_Impact=Client-based fencing (access control) for clients is performed by using a deprecated, proprietary technology instead of an industry standard that provides centralized client-based fencing for Server for NFS.
NfsClientGroupsDefinedOrInUse_Resolution=Use the appropriate centralized configuration, such as Active Directory Domain Services (AD DS) or Network Information Service (NIS), to enable Netgroups.
NfsClientGroupsDefinedOrInUse_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # NFS rule 6 (warning, configuration) - check for legacy User Name Mapping Service with or without an RFC2307 based identity mapping solution
    #
NfsUsingUnmpWithOrWithoutRfc2307_Title=Server for Network File System should use an RFC2307-based identity mapping solution
NfsUsingUnmpWithOrWithoutRfc2307_Problem=Server for Network File System is configured to use the User Name Mapping Service.
NfsUsingUnmpWithOrWithoutRfc2307_Impact=The compatibility of Server for Network File System is limited because it performs identity mapping by using a deprecated, proprietary technology instead of by using an identity mapping solution based on the RFC2307 industry standard.
NfsUsingUnmpWithOrWithoutRfc2307_Resolution=Implement an RFC2307-based identity mapping solution such as Active Directory Domain Services (AD DS), Active Directory Lightweight Domain Services (AD LDS), or other compliant Lightweight Directory Access Protocol (LDAP) stores.
NfsUsingUnmpWithOrWithoutRfc2307_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # NFS rule 8 (warning, configuration) - Check for Case sensitivity setting when also running SMB
    #
NfsUsingCaseSensitiveWithSmbAndNfs_Title=Operating system case sensitivity should be disabled for file servers that support the NFS and SMB protocols
NfsUsingCaseSensitiveWithSmbAndNfs_Problem=Case sensitivity is enabled in the operating system for a file server that supports the Network File System (NFS) and Server Message Block (SMB) protocols.
NfsUsingCaseSensitiveWithSmbAndNfs_Impact=File names may appear and be accessed differently depending on whether the user is using the NFS or SMB protocol to access the files. Object names may also appear differently for some applications, potentially leading to compatibility problems.
NfsUsingCaseSensitiveWithSmbAndNfs_Resolution=Use Registry Editor to disable case sensitivity in the operating system, or dedicate the server to hosting NFS resources.
NfsUsingCaseSensitiveWithSmbAndNfs_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # NFS rule 9 (error, configuration) - Check necessary firewall ports open
    #
NfsAllFirewallPortsOpen_Title=Windows Firewall should open all ports used by Server for Network File System
NfsAllFirewallPortsOpen_Problem=Some ports used for Server for Network File System are closed in Windows Firewall.
NfsAllFirewallPortsOpen_Impact=Users will not have predictable access to shares when using the Network File System (NFS) protocol.
NfsAllFirewallPortsOpen_Resolution=Use Windows Firewall to open the appropriate ports.
NfsAllFirewallPortsOpen_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.


    # NFS rule 10 (warning, configuration) - check that NFS server is being used.
    #
NfsServerServiceInUse_Title=Server for Network File System should be used or uninstalled
NfsServerServiceInUse_Problem=No Network File System (NFS) shares (exports) are configured for Server for Network File System.
NfsServerServiceInUse_Impact=Users will not be able to access shared folders by using the NFS protocol. The unused service will consume system resources and increase the surface area for malicious users to attack without providing any functionality to users.
NfsServerServiceInUse_Resolution=Use the File and Storage Services page of Server Manager or New-NfsShare Windows Powershell cmdlet to provision one or more NFS shares, or uninstall Server for Network File System if it is not being used.
NfsServerServiceInUse_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

###PSLOC

'@