Number of DirSync requests that User Replicator executed and failed to get responses for. One common reason for DirSync requests to fail is that the account User Replicator runs under does not have replication rights on a domain.
Note: The option you select below applies only to the new SQL databases that are being installed. If a database is already ...
Note: This wizard takes a snapshot of only the current configuration. If you add components to, or remove them from, your ...
Note: User store for this pool cannot be moved since this pool also hosts Central Management Server. To move the user store ...
Number of calls that were transferred on queue timeout or queue overflow, across all RGS service instances in the deployment. ...
Number of DirSync requests that User Replicator executed and failed to get responses for. One common reason for DirSync requests ...
Number of DirSync requests that User Replicator has executed since starting up. User Replicator uses DirSync to track changes ...
Number of DirSync responses that were successfully processed. No errors occurred during processing that aborted synchronization. ...
Number of DirSync responses that were unsuccessfully processed. One or more errors occurred while processing the response ...
Number of HTTPS requests that have been initiated from the conferencing pool to other entities. This counter includes both ...