This command-line tool retrieves FRS-related state information
from the specified domain controller or server. It collects and
provides administrators with in-depth data that can be used to
monitor or troubleshoot an FRS system.
Health_Chk calls a series of tools for the output they produce.
It can be run against a remote server, however, running the script
directly on the server to be analyzed enables the tools to gather
additional useful data not available when the script is run
remotely.
For monitoring, Health_Chk should be run regularly against hub
servers and a small selection of spoke servers. Building a simple
script that invokes these health checks and collects them to a
single server for analysis is very valuable - especially when
scheduled to run on a daily basis.
For troubleshooting, Health_Chk should be run against the
server that shows the symptoms of replication failures, but also,
ideally, against all other related servers. It may not be possible
to collect data for all servers in a large enterprise, but
including direct replication partners or, if this is still too
much, a good sample set of them, will provide more complete
information about your topology.
Corresponding UI
There is no corresponding user interface for this tool.
The File Replication Service (FRS) is a multi-master file
replication service for NTFS that allows member machines to be
interconnected in an arbitrary topology and uses last-writer-wins
conflict resolution. It uses authenticated Remote Procedure Call
(RPC) with encryption as the communication protocol between
members, and can also support disconnected operation. FRS supports
multiple replication sets per computer, each with potentially
distinct topology.