Critical Non Impact


Remote Desktop Clients Cannot Connect To Terminal Server

This alert condition indicates that Remote Desktop Clients cannot connect to Terminal Server. This indicates that the port and the service are not running on the Terminal Server. This will cause connectivity issue for clients. Terminal Server Clients use TCP port 3389 to communicate with Terminal Server. Terminal Services clients may be unable to connect to a Windows-based computer that is running Terminal Services.

Remote Desktop Configuration Not In Running State

This alert condition indicates that the Remote Desktop Configuration service is not running.

Remote Desktop Configuration Not In Running State [Unexpected]

This alert condition indicates that the Remote Desktop Configuration service terminated unexpectedly.

Remote Desktop Connection Broker Not In Running State

This alert condition indicates that the Remote Desktop Connection Broker service is not running.

Remote Desktop Connection Broker Not In Running State [Unexpected]

This alert condition indicates that the Remote Desktop Connection Broker service terminated unexpectedly.

Remote Desktop Gateway Not In Running State

This alert condition indicates that the Remote Desktop Gateway service is not running.

Remote Desktop Gateway Not In Running State [Unexpected]

This alert condition indicates that the Remote Desktop Gateway service terminated unexpectedly.

Remote Desktop Licensing Not In Running State

This alert condition indicates that the Remote Desktop Licensing service is not running.

Remote Desktop Licensing Not In Running State [Unexpected]

This alert condition indicates that the Remote Desktop Licensing service terminated unexpectedly.

Remote Desktop Management Not In Running State

This alert condition indicates that the Remote Desktop Management service is not running.

Remote Desktop Management Not In Running State [Unexpected]

This alert condition indicates that the Remote Desktop Management service terminated unexpectedly.

Remote Desktop Services Failed To Connect To RD Connection Broker Verify Server Address And Permissions

This alert condition indicates a communication issue between the RD Connection Broker server and the RD Virtualization Host server when a user requests a connection to a virtual desktop.

Remote Desktop Services RD Licensing Grace Period Is About To Expire Or Already Expired

AIS Monitoring agent has detected the RD Licensing grace period is about to expire or already expired. Impact: User will not be able to login to RDS if grace period expire license is not installed on server.

Remote Desktop Services RD Licensing Mode Has Not Been Configured

AIS Monitoring agent detected RD Licensing mode has not been configured. Impact: If RD licensing mode is not configured then user will connect to RDS server using temporary licenses which will work for 120 days. Post that user will failed to connect RDS server.

Remote Desktop Services Remote Desktop Services Failed To Join The Connection Broker On Server

This alert condition indicates that Remote Desktop Services failed to join the Connection Broker on a server.

Remote Desktop Services The RDS Host Server Could Not Contact The Remote Desktop License Server

This alert condition indicates that the Remote Desktop Services Host server could not contact the Remote Desktop license server.

Remote Desktop Services The User Authorized To Access The TS Gateway Server, But Could Not Connect To Resource With Error

This alert condition indicates that the user is authorized to access the TS Gateway server, but encountered an error trying to connect to the resource.

Remote Desktop Services The User Not Authorized To Access The TS Gateway Server As Per Authorization Policy Requirements

This alert condition indicates that the user is not authorized to access the TS Gateway server as per authorization policy requirements.

Remote Desktop Services The User Not Authorized To Access The TS Gateway Server Because A Tunnel Could Not Be Created

This alert condition indicates that the user is not authorized to access the TS Gateway server because a tunnel could not be created.

Remote Desktop Services Not In Running State

This alert condition indicates that the Remote Desktop Services service is not running.

Remote Desktop Services Not In Running State [Unexpected]

This alert condition indicates that the Remote Desktop Services service terminated unexpectedly.

Remote Desktop Services UserMode Port Redirector Not In Running State

This alert condition indicates that the Remote Desktop Services UserMode Port Redirector service is not running.

Remote Desktop Services UserMode Port Redirector Not In Running State [Unexpected]

This alert condition indicates that the Remote Desktop Services UserMode Port Redirector service terminated unexpectedly.

RemoteApp And Desktop Connection Management Not In Running State

This alert condition indicates that the RemoteApp and Desktop Connection Management service is not running.

RemoteApp And Desktop Connection Management Not In Running State [Unexpected]

This alert condition indicates that the RemoteApp and Desktop Connection Management service terminated unexpectedly.

Routing And Remote Access Not In Running State

This alert condition indicates that the Routing and Remote Access service is not running.

Routing And Remote Access Not In Running State [Unexpected]

This alert condition indicates that the Routing and Remote Access service terminated unexpectedly.

Terminal Server All Network Adapters Are Not Configured For TS Protocol

This alert condition indicates that all network adapters are not configured for TS protocol. It is recommended to configure all adapters for TS protocol for proper load balancing.

Terminal Server General Database Error

This alert condition indicates a Terminal Server General Database error. Incorrectly configured NTFS permissions for logical drives can cause issues with system services and programs. This issue can occur if an administrator modifies permissions in an attempt to strengthen the default Windows security, but does not set the proper permissions at all levels.

Terminal Server Running On Trial Mode

This alert condition indicates that the Terminal Server is running in Trial Mode and the grace period is about to expire. In Terminal Server environments, you must have account for both OS licenses and application licenses. Licensing is no different from non-Terminal Server environments, except that Windows Server 2003 has technical components that force you to comply with your licenses. If you decide to ignore this condition, you will most likely revisit licensing in 120 days when your Terminal Servers stop functioning because they weren’t properly licensed. Terminal Servers running on Windows 2000 were the first to use Microsoft’s new licensing enforcement technology, and Windows 2003 builds on that.

Terminal Server Trial Period Expired

This alert condition indicates that the Terminal Server’s trial period has expired and will not accept connections. In Terminal Server environments, you must account for both OS licenses and application licenses. Licensing is no different from non-Terminal Server environments, except that Windows Server 2003 has technical components that force you to comply with your licenses. If you decide to ignore this condition, you will most likely revisit licensing in 120 days when your Terminal Servers stop functioning because they were not properly licensed. Terminal Servers running on Windows 2000 were the first to use Microsoft’s new licensing enforcement technology. Windows 2003 builds on this licensing enforcement.

Last modified April 17, 2020