When Should You Restart FRS?

by [Published on 19 Nov. 2008 / Last Updated on 24 Aug. 2008]

This article discusses the Regsitry entries of File Replication Service and when should you restart the FRS service for the changes to take effect.

Almost every change in a registry requires you restart the Service for which you made the changes in the registry but there are few services for which you don't have to restart the Service for registry changes to take effect. As an example, FRS (File Replication Service) doesn't require you restart the service for the following changes made in the registry at: HKEY_LOCAL_MACHINE\CurrentControlSet\Services\Ntfrs\Parameters.

  • Debug Log Severity
  • Debug Log Files
  • Debug Maximum Log Messages
  • DS Polling Short Interval
  • DS Polling Long Interval
  • Staging Space Limit in KB
  • Working Directory
  • Ntfs Journal size in MB
  • Outlog Change History In Minutes
  • Compress Staging Files Value

Registry entries that require the FRS to be restarted are the followings:

  • BurFlags (also known as D4 and D2) 

and also if you make any changes to the registry located at the following location require the FRS to be restarted:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup

See Also

The Author — Nirmal Sharma

Nirmal Sharma avatar

Nirmal Sharma is a MCSEx3, MCITP and was awarded the Microsoft MVP award in Directory Services and Windows Networking. He specializes in Microsoft Azure, Office 365, Directory Services, Failover Clusters, Hyper-V, PowerShell Scripting and System Center products. Nirmal has been involved with Microsoft Technologies since 1994. In his spare time, he likes to help others and share some of his knowledge by writing tips and articles on various sites and contributing to PowerShell-based Dynamic Packs for www.ITDynamicPacks.Net solutions.

Featured Links