# Localized 02/22/2014 02:59 PM (GMT) 303:4.80.0411 FSRM.psd1 # Localized 02/29/2012 05:59 AM (GMT) 303:4.80.0411 FSRM.psd1 ConvertFrom-StringData @' ###PSLOC start localizing # check FSRM service status FSRMServiceStatusCheck_Title=The File Server Resource Manager service should be running FSRMServiceStatusCheck_Problem=The File Server Resource Manager service is not started. FSRMServiceStatusCheck_Impact=File Server Resource Manager features will not work. FSRMServiceStatusCheck_Resolution=Set the File Server Resource Manager service to start automatically. FSRMServiceStatusCheck_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice. # check FSRM service status on cluster FSRMServiceStatusCheckOnCluster_Title=File Server Resource Manager should be installed on all nodes of a failover cluster FSRMServiceStatusCheckOnCluster_Problem=File Server Resource Manager is not installed on all nodes of the failover cluster. FSRMServiceStatusCheckOnCluster_Impact=File Server Resource Manager (FSRM) will not function properly when resources fail over to nodes that do not have FSRM installed. FSRMServiceStatusCheckOnCluster_Resolution=Install the File Server Resource Manager role service on each node of the failover cluster. Alternatively, remove the role service from all nodes. FSRMServiceStatusCheckOnCluster_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice. # check FSRM service status on cluster: not all nodes are reachable FSRMServiceStatusCheckOnCluster_NotReachableNode_Title=All nodes in a failover cluster should be available on the network FSRMServiceStatusCheckOnCluster_NotReachableNode_Problem=The following nodes in a failover cluster cannot be verified because the nodes are not available on the network, or because the BPA scan was performed against a remote failover cluster: {0} FSRMServiceStatusCheckOnCluster_NotReachableNode_Impact=The Best Practices Analyzer will not be able to check the status of File Server Resource Manager on the following nodes: {0} FSRMServiceStatusCheckOnCluster_NotReachableNode_Resolution=Confirm that the nodes are online, log on to the nodes locally (or by using Remote Desktop), and then run the Best Practices Analyzer scan again. FSRMServiceStatusCheckOnCluster_NotReachableNode_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice. # check classification schedule present FSRMClassificationSchedulePresent_Title=Classification rules should have schedules FSRMClassificationSchedulePresent_Problem=One or more classification rules do not have schedules. FSRMClassificationSchedulePresent_Impact=Classification rules will only be applied to files when an application or a file management task queries the classification properties on a file. This may severely slow down the performance of the application or file management task. FSRMClassificationSchedulePresent_Resolution=Use File Server Resource Manager to set up a schedule for automatic classification that runs before applications or file management tasks need the information. FSRMClassificationSchedulePresent_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice. # check property definition count FSRMPropertyDefinitionCount_Title=There should be fewer than 200 classification properties FSRMPropertyDefinitionCount_Problem=There are more than 200 classification properties. FSRMPropertyDefinitionCount_Impact=File classification will consume more time and server resources. FSRMPropertyDefinitionCount_Resolution=Use File Server Resource Manager to delete all properties that are not used in any classification rules. FSRMPropertyDefinitionCount_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice. # check quota definition count FSRMQuotaCount_Title=There should be fewer than 10000 quotas configured on the server FSRMQuotaCount_Problem=There are more than 10000 quotas configured on the server. FSRMQuotaCount_Impact=The File Server Resource Manager user interface will perform slowly. FSRMQuotaCount_Resolution=Use File Server Resource Manager to delete unneeded quotas or to consolidate individual quotas. If this is not possible, use command-line tools or scripts to administer quotas. FSRMQuotaCount_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice. # check file screen count FSRMFileScreenCount_Title=There should be fewer than 1000 file screens configured on the server FSRMFileScreenCount_Problem=There are more than 1000 file screens configured on the server. FSRMFileScreenCount_Impact=The File Server Resource Manager user interface will perform slowly. FSRMFileScreenCount_Resolution=Use File Server Resource Manager to delete unneeded file screens or to consolidate individual file screens. If this is not possible, use command-line tools or scripts to administer file screens. FSRMFileScreenCount_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice. # check cache not active. FSRMCacheEnabled_Title=The cache for classification properties should be active FSRMCacheEnabled_Problem=The cache for classification properties is not active. FSRMCacheEnabled_Impact=File Server Resource Manager will reclassify files every time an application or Windows queries the classification of a file. This will result in reduced performance for applications, file management tasks, and reports that query classification properties for files. FSRMCacheEnabled_Resolution=Use a script to enable the system cache module. FSRMCacheEnabled_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice. # check for adequate cache size FSRMCacheSizeAdequate_Title=Alternate data streams should be large enough to store classification properties FSRMCacheSizeAdequate_Problem=The alternate data stream size is too small to store classification properties. FSRMCacheSizeAdequate_Impact=File Server Resource Manager will reclassify files every time Windows or an application queries the classification of a file. This will result in reduced performance for applications, file management tasks, and reports that query classification properties for files. FSRMCacheSizeAdequate_Resolution=Use Registry Editor to increase the size of the alternate data stream cache. FSRMCacheSizeAdequate_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice. # check for orpahned logs FSRMNoOrphanedLogs_Title=Log files for file management tasks should be properly deleted FSRMNoOrphanedLogs_Problem=A log file used to track which notifications were sent by a file management task was not deleted when the task was deleted. FSRMNoOrphanedLogs_Impact=The log files can consume a significant amount of disk space. FSRMNoOrphanedLogs_Resolution=Delete the log files. The following log files do not belong to an existing file management job:\n\n\tLogs: {0} FSRMNoOrphanedLogs_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice. # check for read only files FSRMFewReadOnlyFiles_Title=Classified files should have read and write attributes FSRMFewReadOnlyFiles_Problem=File Server Resource Manager is configured to classify read-only files, and cannot save classification properties for the files. FSRMFewReadOnlyFiles_Impact=File Server Resource Manager will reclassify the read-only files every time an application or Windows queries the classification of a file. This will reduce performance for applications, file management tasks, and reports that query classification properties for files. FSRMFewReadOnlyFiles_Resolution=Remove the read-only attribute from the files or exclude them from the classification rules. To view the affected files, see the following log file: {0} FSRMFewReadOnlyFiles_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice. # check for V2 schedules FSRMV2Schedules_Title=All file management jobs, reports, and the classification schedule should be compatible with the Task Scheduler 2.0 API on a non-clustered server FSRMV2Schedules_Problem=One or more file management jobs, reports, or classification schedules are not compatible with the Task Scheduler 2.0 API. FSRMV2Schedules_Impact=Version 1 schedules will continue to run, but cannot be updated, only replaced. FSRMV2Schedules_Resolution=Create new schedules for the following: \n\nFile Management Jobs:\n{0}\n\nStorage Reports:\n{1}\n\nClassification (if version = V1):\nVersion = {2} FSRMV2Schedules_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice. # check firewall FSRMFirewall_Title=Port 5985 must be allowed through the Windows Firewall for access-denied assistance FSRMFirewall_Problem=Access-denied assistance is enabled, but port 5985 is not open in the Windows Firewall. FSRMFirewall_Impact=Access-denied assistance is enabled on this server, but port 5985 must be allowed in the Windows Firewall to allow remote clients to interact with the server. FSRMFirewall_Resolution=Allow port 5985 through the Windows Firewall on this server or disable access-denied assistance. FSRMFirewall_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice. # check WinRm FSRMWinRm_Title=Windows Remote Management must be enabled for access-denied assistance FSRMWinRm_Problem=Windows Remote Management is not enabled. FSRMWinRm_Impact=Remote clients cannot use access-denied assistance. FSRMWinRm_Resolution=Ensure that Windows Remote Management is enabled or disable access-denied assistance. FSRMWinRm_Compliant=The File and Storage Services Best Practices Analyzer scan has determined that you are in compliance with this best practice. ###PSLOC '@