Optimize Windows Server 2019 with file server best practices

Windows file servers remain a steadfast resident of the data center, despite the fact that many workloads have shifted to the cloud .
The advances in the late versions of Windows Server make on-premises file servers an attractive choice versus comparable cloud services. Organizations that use Windows Server 2019 file servers benefit from data deduplication for increase space savings, and higher levels of security and performance from refinements to the Server Message Block ( SMB ) protocol. When you deploy a new Windows Server, Microsoft ‘s guidelines steer you to the proper settings for better auspices, american samoa well as dependability to ensure the best possible end-user feel .

Keep the installation lean

As you deploy a Windows Server 2019 file server, it is likely that you will need to install extra components. however, it is important to avoid adding roles or features the server does n’t need to do its job. For exemplar, a dedicate Windows file server should have Hyper-V server function .
File and Storage Services role
When you install the File and Storage Services role, it installs just two out of the 12 features by default. You should not install additional features if you plan to use them on the file server.


When you install unnecessary features or multiple roles, it increases the waiter ‘s footprint, which can reduce file server performance. besides, when more code runs on a system, this increases the assail airfoil to make the waiter less batten. As a best practice, you should install only necessity components for a file server to operate .

Run a scan to maintain Windows Server 2019 file server best practices

You should sporadically run the Best Practices Analyzer on your Windows files servers. This tool, which has been separate of the OS since Windows Server 2008 R2, compares your file server ‘s shape against Microsoft ‘s established best practices .
There are two chief reasons why this routine checkup is significant. First, as Microsoft ‘s best practices for Windows servers evolve and the company updates the utility to reflect those changes. regular scans validate your charge server shape. not every publish is hard adequate to mandate a change but could show an sphere where an allowance might improve performance or dependability .
second, shape drift often occurs through the course of Windows Server management, peculiarly in environments with a big IT team. The Best Practices Analyzer detects modifications to settings that violate best practices .
To run a best practices scan on a Windows Server 2019 file waiter, open Server Manager and select the File and Storage Services yellow journalism. future, coil to the Best Practices Analyzer and choose the Start BPA Scan choice from the Tasks menu .
Best Practices Analyzer
Use the Best Practices Analyzer in Server Manager to scan the file server for any signs of trouble.


The Best Practices Analyzer will scrutinize the file waiter character and generate a number with a austereness level for each offspring that includes information and potential redress actions.

Consider the required versions of SMB

Consider which version of SMB needs to run on the Windows file server. There are three different versions of the SMB protocol, but most organizations wo n’t need to run all three versions .
There are times Microsoft ‘s Windows Server 2019 file server best practices recommendations are not accurate. This is when it helps to use your institutional cognition as a Windows administrator. For exercise, the Best Practices Analyzer might give you bad advice with the SMB shape. Windows Server 2019 disables SMB 1.0 by default, but the Best Practices Analyzer recommends you enable it, as shown in Figure 3 .
SMB 1.0 protocol
The Best Practices Analyzer recommends you enable SMB 1.0 on the file server, which goes against advice from Microsoft’s security and storage teams.


The SMB 1.0 protocol helps with older Windows systems ‘ backward compatibility, but SMB 1.0 is besides very insecure. That being the case, it ‘s best to ignore the Best Practices Analyzer ‘s advice and leave SMB 1.0 disabled, unless you have compelling reason to use it .

If possible, use the Resilient File System

many organizations have historically avoided the Resilient File System ( ReFS ) in favor of the NT File System ( NTFS ), and for well reason. The ReFS was developed for data resilience, but the 1.1 interpretation released with Windows Server 2012 was highly restrict in its capabilities compared to NTFS. many NTFS features did not exist in ReFS, such as the ability to boot the system .
Microsoft continues to develop ReFS and, now, most of the NTFS features exist in ReFS. ReFS version 3.4 in Windows Server 2019 is far more feature-rich than the 1.1 version, but there are still some areas where it is lacking. For example, ReFS does not support file system compression, encoding, disk quotas or DOS-compatible 8.3 filenames .
If you can live without these features, there are significant benefits to ReFS. It is army for the liberation of rwanda more scalable than NTFS and supports volume sizes up to 35 PB. ReFS includes respective features to protect the integrity of the data on the book. Windows waiter 2019 has a proactive error correction sport that sporadically scans ReFS volumes and mechanically repairs defile data .

Use Distributed File System in large organizations

The Distributed File System ( DFS ) in Windows gives a means to create a individual namespace that encompasses multiple charge servers. This makes it easier for users to find data without needing to know which server holds the files. DFS can make multiple data replica and mutely redirect drug user requests to the file server that is closest to the user.

A DFS namespace can incorporate more than just Windows file servers. You can add any file server that supports SMB file shares to a DFS namespace, which can be helpful in organizations with both Windows file servers and network-attached storage appliances .

Use the File Server Resource Manager to enforce compliance

last, you should use the File Server Resource Manager ( FSRM ) to control the file server. FSRM is a Windows Server function used to enforce quota on folders on the file server and beget reports on storehouse usage to name a few features .
FSRM besides has the add benefit of a file screening routine that prevents users from storing certain filetypes on the file server. You determine how the system responds when a exploiter tries to save a type of file, such as an feasible. In this senesce of ransomware, it ‘s another method at your disposal to prevent an attacker from encrypting all your files .

source : https://thefartiste.com
Category : Tech

About admin

I am the owner of the website thefartiste.com, my purpose is to bring all the most useful information to users.

Check Also

articlewriting1

Manage participants in a zoom meeting webinar

Call the people who attend the meet as follows Alternate host host Who scheduled the …

Leave a Reply

Your email address will not be published.