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

###PSLOC start localizing

    # check DFS Namespace service status
DFSNServiceStatusCheck_Title=The DFS Namespace service should be started
DFSNServiceStatusCheck_Problem=The DFS Namespace service is not started.
DFSNServiceStatusCheck_Impact=The namespace server is unavailable to clients and no further diagnostic information can be gathered. If the server is a domain controller, domain referral and domain controller referral requests to the domain controller will fail.
DFSNServiceStatusCheck_Resolution=Start the DFS Namespace service.
DFSNServiceStatusCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.
    
    # check DFS Namespace service start type
DFSNServiceStartupTypeCheck_Title=The DFS Namespace service startup type should be set to Automatic
DFSNServiceStartupTypeCheck_Problem=The DFS Namespace service startup type is not set to Automatic.
DFSNServiceStartupTypeCheck_Impact=After restarting the server, the namespace server will be offline until you manually start the DFS Namespace service. If the server is a domain controller, domain referral and domain controller referral requests to the domain controller will fail.
DFSNServiceStartupTypeCheck_Resolution=Set the DFS Namespace service to start automatically.
DFSNServiceStartupTypeCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check IP address to site mapping
IPAddressToSiteMappingCheck_Title=All IP addresses for the server should map to the same AD DS site
IPAddressToSiteMappingCheck_Problem=Not all network adapters are configured with the same Active Directory Domain Services (AD DS) site.
IPAddressToSiteMappingCheck_Impact=DFS Namespaces site awareness will behave incorrectly, with the namespace server potentially providing referrals to client computers at a site that is not local to the server.
IPAddressToSiteMappingCheck_Resolution=Configure all network adapters to use IP addresses from subnets that belong to the same AD DS site.
IPAddressToSiteMappingCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check LdapTimeoutValue has been set to 30 seconds
LdapTimeoutValueCheck_Title=The LDAP timeout value should be set to the default value of 30 seconds
LdapTimeoutValueCheck_Problem=The Lightweight Directory Access Protocol (LDAP) timeout value is different from the default, which is 30 seconds.
LdapTimeoutValueCheck_Impact=The DFS Namespace service may not be able to query or recover from a temporary failure of Active Directory Domain Services (AD DS).
LdapTimeoutValueCheck_Resolution=Use the Set-DfsnServerConfiguration Windows PowerShell cmdlet or the Dfsutil command-line tool to set the LDAPTimeoutValueInSeconds registry value on this namespace server to 30.
LdapTimeoutValueCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check SyncIntervalInSeconds has been set to 3600 seconds
SyncIntervalInSecondsCheck_Title=The DFS Namespaces sync interval should be set to the default value of 1 hour
SyncIntervalInSecondsCheck_Problem=The sync interval value is different from the default, which is 1 hour (3600 seconds).
SyncIntervalInSecondsCheck_Impact=The DFS Namespace service may put more load than necessary on Active Directory Domain Services (AD DS), or be unable to recover from temporary failures to update AD DS.
SyncIntervalInSecondsCheck_Resolution=Use the Set-DfsnServerConfiguration Windows PowerShell cmdlet or the Dfsutil command-line tool to set the sync interval on this namespace server to the default value of 1 hour.
SyncIntervalInSecondsCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check SiteCostedReferral has been enabled
SiteCostedReferralCheck_Title=Site-costed referrals should be enabled on domain controllers
SiteCostedReferralCheck_Problem=Site-costed referrals are disabled on a domain controller.
SiteCostedReferralCheck_Impact=If a domain controller becomes unavailable, client computers that are using the SYSVOL folder of the domain controller might fail over to a distant domain controller instead of a closer domain controller.
SiteCostedReferralCheck_Resolution=Use the Set-DfsnServerConfiguration Windows PowerShell cmdlet or the Dfsutil command-line tool to enable site-costed referrals on this domain controller.
SiteCostedReferralCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check SysvolNetlogonTargetFailback has been enabled
SysvolNetlogonTargetFailbackCheck_Title=Client failback should be enabled for the Netlogon and SYSVOL folders on domain controllers
SysvolNetlogonTargetFailbackCheck_Problem=Client failback is disabled for the Netlogon and SYSVOL folders on a domain controller.
SysvolNetlogonTargetFailbackCheck_Impact=Client computers could experience slower response times if they fail over to a remote domain controller and do not fail back to the local domain controller when it comes back online.
SysvolNetlogonTargetFailbackCheck_Resolution=Use Registry Editor to enable client failback for the Netlogon and SYSVOL folders on each domain controller in this domain.
SysvolNetlogonTargetFailbackCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check if standalone root is clustered
IsStandaloneClusterCheck_Title=Failover Clustering should be enabled on the server hosting the following standalone namespace: {0}
IsStandaloneClusterCheck_Problem=Failover Clustering is not enabled on the server hosting the following standalone namespace: {0}
IsStandaloneClusterCheck_Impact=If the namespace server fails, client computers will not be able to receive new referrals to folder targets, which limits their ability to use the following namespace: {0}
IsStandaloneClusterCheck_Resolution=Enable Failover Clustering on the server that is hosting the following standalone namespace: {0}
IsStandaloneClusterCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # Domain namespace should have at least two root targets
RootTargetsCountCheck_Title=Additional namespace servers should be added to the following domain-based namespace: {0}
RootTargetsCountCheck_Problem=The following domain-based namespace has only a single namespace server (root target): {0}
RootTargetsCountCheck_Impact=If the namespace server fails, client computers will not be able to receive new referrals to folder targets, which limits their ability to use the following namespace: {0}
RootTargetsCountCheck_Resolution=Add one or more namespace servers to the following domain-based namespace: {0}
RootTargetsCountCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check SiteCosting has been enabled
SiteCostingCheck_Title=Namespace root referrals should use the Lowest Cost ordering method on the following DFS namespace: {0}
SiteCostingCheck_Problem=Site-costed referrals are disabled on the following DFS namespace: {0}
SiteCostingCheck_Impact=If a namespace server or folder target becomes unavailable, client computers might fail over to a distant namespace server or folder target instead of a closer server.
SiteCostingCheck_Resolution=Use DFS Management to set the ordering method for namespace root referrals to Lowest Cost on the following namespace: {0}
SiteCostingCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check ABDE settings
ABDECheck_Title=The access-based enumeration setting should be identical in the DFS namespace database and on the shared folder hosting the namespace root for the following namespace: {0}
ABDECheck_Problem=Access-based enumeration is enabled on a DFS namespace, but not on the shared folder hosting the namespace root. Namespace: {0}
ABDECheck_Impact=Access-based enumeration will not work, resulting in DFS folders being visible to users who do not have permission to view the folders.
ABDECheck_Resolution=Use DFS Management, the Set-DfsnRoot Windows PowerShell cmdlet, or the Dfsutil command-line tool to disable and then enable access-based enumeration on the namespace, and then do not use other tools to modify this setting.
ABDECheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check FFL and DFL settings
FFLDFLCheck_Title=Windows Server 2008 mode can be used on the following domain-based namespace: {0}
FFLDFLCheck_Problem=The following domain-based namespace meets the prerequisites for using the Windows Server 2008 mode, but is instead using the Windows 2000 Server mode. Namespace: {0}
FFLDFLCheck_Impact=The namespace administrator cannot enable access-based enumeration of DFS folders or expand the namespace to more than 5,000 folders with targets (links). Additionally, the DFS Namespace service takes longer to start when hosting namespaces with thousands of folders with targets.
FFLDFLCheck_Resolution=Migrate the following domain-based namespace from Windows 2000 Server mode to Windows Server 2008 mode: {0}
FFLDFLCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check TargetFailback has been enabled
TargetFailbackCheck_Title=Client failback should be enabled on the following namespace: {0}
TargetFailbackCheck_Problem=Client failback is disabled on the following namespace: {0}
TargetFailbackCheck_Impact=Client computers could experience slower response times if they fail over to a remote folder target and do not fail back to the local folder target when it comes back online.
TargetFailbackCheck_Resolution=Use DFS Management to enable client failback on the following namespace: {0}
TargetFailbackCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.

    # check RootTargetState has been enabled
RootTargetStateCheck_Title=The namespace server should be enabled on the following namespace: {0}
RootTargetStateCheck_Problem=The server is a namespace server for the following namespace, but is not enabled. Namespace: {0}
RootTargetStateCheck_Impact=If no other namespace servers are available, client computers will not be able to access the following namespace: {0}
RootTargetStateCheck_Resolution=Remove all namespace servers that have been permanently disabled and then enable all remaining namespace servers. To do so, use DFS Management, the Remove-DfsnRootTarget and Set-DfsnRootTarget Windows PowerShell cmdlets, or the Dfsutil command-line tool.
RootTargetStateCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice.
    
###PSLOC

'@