When the Diagnostics Service is installed or upgraded it is only enabled for local machine access by default. In some cases, it may be necessary to include diagnostics information from remote machines.
CAUTION:
The data collected by the Diagnostics Service may contain sensitive system information. Enabling remote access can pose a security risk if your environment is not adequately configured to prevent unauthorized users from gaining access to the data received from remote Diagnostics Services.
CAUTION: Be very careful when updating the JSON
configuration files. If a copy exists with a similar naming scheme (for example,
appsettings.backup.json), and that copy is not deleted, the incorrect JSON configuration
file may be used. Configuration files are read in lexicographic order, or the order in
which they are loaded. This means that the last file saved is the first file loaded. The
order of precedence for the loading of the configuration sources is: 1) appsettings.json
file, 2) appsettings.{AltName}.json file, 3) Key-per-file directories, 4) Environment
variables, and 5) Command Line arguments. As a result, if a JSON configuration file is
configured with an alternate name, and is the most recently saved version of the JSON
configuration file, the file with the alternate name will take precedence, which causes
major errors during login.
To enable remote access for a Diagnostics Service: