Fields

Message

Remote Desktop Connection Broker Notify Events

Fields

Fields

Message

RD Connection Broker successfully added a target %1. 
Farm Name = %2.

Fields

Fields

Message

RD Connection Broker successfully removed target %1.
Farm Name = %2.

Fields

Message

RD Connection Broker failed while adding Target %1.
Farm Name = %2. 
Error: %3

Fields

Message

RD Connection Broker failed while removing Target %1. 
Farm Name = %2. 
Error: %3

Fields

Fields

Message

State of target %1 changed to: %2.

Fields

Fields

Message

Redirector/TS %1 successfully parked a call.

Fields

Fields

Message

Redirector/TS %1 failed to park a call. HRESULT = %2

Fields

Fields

Message

Redirector/TS %1 randown or ServerOffline was called. Parked call completed = %2

Fields

Message

RD Connection Broker successfully added an RD Session Host Server %1 to Farm %2. 
Server Capacity in Number of Sessions (Load Indicator) = %3 
Server In Drain = %4 
Server Online Flags = %5

Fields

Message

RD Connection Broker failed while adding session for user %1 (on target %2). Error: %3

Fields

Message

RD Connection Broker failed while changing session state for user %1 (on target %2). New State: %3
 Farm Name = %4 
Session ID = %5 
Error: %6

Fields

Fields

Message

Session state for user %2 changed to: %4. 
Target Name = %3 
Farm Name = %5 
Session ID = %1

Fields

Message

Session for user %2 successfully added to RD Connection Broker's database. 
Target Name = %3 
Session ID = %1 
Farm Name = %4

Fields

Message

RD Connection Broker received connection request for user %1. 
Hints in the RDP file (TSV URL) = %2 
Initial Application = %3 
Call came from Redirector Server = %4 
Redirector is configured as %5

Fields

Message

RD Connection Broker successfully processed the connection request for user %1. Redirection info: 
Target Name = %2 
Target IP Address = %3 
Target Netbios = %4 
Target FQDN = %5 
Disconnected Session Found = %6

Fields

Fields

Message

RD Connection Broker failed to process the connection request for user %1.%3
Error: %2

Fields

Fields

Message

RD Connection Broker has successfully determined the end point for this connection request. 
Endpoint name = %1 
Endpoint type = %2 
Resource plugin name = %3

Fields

Fields

Message

RD Connection Broker could not find an assigned Personal Virtual Desktop for user %1. HRESULT = %2

Fields

Message

Processing of the connection request is being paused for the previous request to finish.

Message

Processing of the connection request has been resumed.

Fields

Message

RD Connection Broker has found a disconnected session for user (%2) with session ID (%1) on end point (%3). Load balancing will be skipped.

Fields

Fields

Message

A disconnected session could not be found for this user. Error: %1

Fields

Fields

Message

(%1) Plugin successfully processed the connection request for Load Balancing. Target Name = %2.

Fields

Fields

Message

(%1) Plugin successfully placed the target.

Fields

Fields

Message

(%1) Plugin successfully orchestrated the target.

Fields

Fields

Message

Remote Desktop Connection Broker will monitor this connection request and send appropriate notification to the plugin. 
Sweep frequency = Once every %1 sec 
Connection request timeout = %2 sec

Fields

Message

Remote Desktop Connection Broker will not monitor this connection request. By default, only connection requests with farm type endpoints are monitored. To enable monitoring for a non farm type endpoint, add TargetClientConnectionMonitoring boolean property (value = true) to its target propertyset.

Fields

Message

RD Connection Broker received connection request for user %1. 
Hints in the RDP file (TSV URL) = %2 
Call came from Redirector Server = %3

Fields

Fields

Message

RD Connection Broker is about to call %1 for %2.

Fields

Message

RD Connection Broker has successfully determined the assigned personal virtual desktop for this user. 
User account: %1 
Pool name: %2 
Personal virtual desktop name: %3

Fields

Message

This connection request has resulted in a successful session logon (User successfully logged on to the end point). Remote Desktop Connection Broker will stop monitoring this connection request.

Message

This connection request has timed out. User could not log on to the end point within the alloted time. Remote Desktop Connection Broker will stop monitoring this connection request.

Message

This connection request has been cancelled due to Remote Desktop Connection Broker service stop. Remote Desktop Connection Broker will stop monitoring this connection request.

Fields

Message

RD Connection Broker could not find an assigned server for user %1 in collection %2. HRESULT = %3.

Fields

Fields

Message

Assigned server for user %1 in collection %2 is not currently running.

Fields

Fields

Message

There is no more server availabe to assign user %1 in collection %2.

Fields

Fields

Message

RD Connection Broker could not find a server for user %1 in collection %2 (Error = %3), please ensure user is assigned to a server, and server is avaiable and running

Fields

Message

The plugin loaded successfully. Following properties were loaded: 
Provider = %1 
CLSID = %2 
 IsEnabled = %3.

Fields

Fields

Message

The %1 plugin failed to load. Error: %2

Fields

Fields

Message

The %1 plugin has an invalid sub key in the registry. Sub key for this plugin should be a positive integer that determines priority for that plugin (order in which plugins are called by the RD Connection broker). Please check the registry value for this plugin.

Fields

Message

A Redirector (%1) successfully joined Remote Desktop Connection Broker.

Fields

Fields

Message

RD Connection Broker Server name changed from (%1) to (%2)

Fields

Fields

Message

RD Connection Broker service failed to start. HRESULT = %1.

Fields

Message

RD Connection Broker service failed to set the working directory retrieved from the registry.
Error code: %1.

Fields

Fields

Message

The %1 group is empty. For the Remote Desktop Connection Broker service to work correctly, you must add the computer accounts of Remote Desktop Session Host servers to this group.

Fields

Message

RD Connection Broker cluster initialization succeded. 
Cluster Network Name = %1 
Cluster Uses Shared Disk = %2.

Fields

Message

RD Connection Broker cluster initialization failed. 
HRESULT = %1.

Fields

Message

RD Connection Broker will not run as a part of cluster.

Message

RD Connection Broker service denied the remote procedure call (RPC) from an unauthorized computer %1.

Fields

Message

RD Connection Broker failed to find Personal Virtual Desktop (%1) assigned to user %2 in RD Connection Broker database. Hr=%3

Fields

Message

RD Connection Broker failed to find any available VM in the farm %1. 
User name = %2. Error: %3

Fields

Fields

Message

VM Type mismatch: User's TS Client is requesting VM (%1) as type (%4); this does not match the VM type in the system, which is type (%3). This may have been caused by configuring the VM as both types (%3) and (%4).  
User name = %2. Hr=%5

Fields

Fields

Message

Failed to find VM Host %1. Hr=%2

Fields

Fields

Message

Failed to find VM instance by name %1. Error: %2

Fields

Message

Failed to spin VM %1 on host %2. Error: %3

Fields

Fields

Message

Failed to find farm %1. Hr=%2

Fields

Fields

Message

Failed to add VM %1 to RD Connection Broker. Error: %2

Fields

Fields

Message

Failed to delete VM by ID %1 from RD Connection Broker. Error: %2

Fields

Fields

Message

Failed to update VM %1 in RD Connection Broker. Error: %2

Fields

Fields

Message

Failed to report session (ID=%3) of VM %1 (ID=%2) to RD Connection Broker. Error: %4

Fields

Fields

Message

Failed to report session (ID=%2) of VM ID=%1 (unable to retreive VM name) to RD Connection Broker. Error: %3

Fields

Message

Hyper-V Agent Service connected from host %1.

Fields

Message

Hyper-V Agent Service disconnected from host %1.

Fields

Message

Hyper-V Agent Service failed to connect from host %1.

Fields

Message

Hyper-V Agent Service failed to disconnect from host %1.

Fields

Message

VM Manager webservice failed to query the environment for the VM. Error code: %1 , Description: %2

Fields

Message

VM Manager webservice failed to create the environment for the VM. Error code: %1 , Description: %2

Fields

Message

VM Manager webservice failed to find a VM from FARM %1.

Fields

Message

VM Manager webservice failed to locate the FARM %1.

Fields

Message

VM Manager webservice failed to find a VM from FARM %1. Error code: %2, Description: %3

Fields

Fields

Message

VM Provisioning operation [%1] failed for pool [%2]. No VM Host is connected to broker.

Fields

Fields

Message

VM Provisioning operation [%1] failed for pool [%2]. Specified VM Host [%3] is either not added to Broker or it is currently not running.

Fields

Fields

Message

VM Provisioning operation [%1] failed for pool [%2]. Specified virtual machine [%3] could not be located in broker database.

Fields

Fields

Message

VM Provisioning operation [%1] failed for pool [%2]. Number of characters in the specified virtual machine name [%3] exceeds the maximum length supported for computer name.

Fields

Fields

Message

VM Provisioning operation [%1] failed for pool [%2]. The specified virtual machine [%3] already exists.

Fields

Fields

Message

VM Provisioning operation [%1] failed for pool [%2]. Connection Broker could not create the machine account [%3] in the specified OU [%4], error: [%5]

Fields

Fields

Message

Rpc call to VM host [%1] failed while executing VM Provisioning operation [%2] for virtual machine [%3] in pool [%4], error: [%5], RPC error [%6 %7]

Fields

Fields

Message

VM host [%1] failed to execute VM Provisioning operation [%2] for virtual machine [%3] in pool [%4], Error: [%5]

Fields

Fields

Message

VM Provisioning operation [Delete] failed for pool [%1]. Connection Broker could not delete the machine account for virtual machine[%2], error: [%3]

Fields

Fields

Message

VM Provisioning operation [%1] failed for pool [%2]. The WMI instance for the requested pool could not be found, error: [%3]

Fields

Fields

Message

The unattend answer file specified for the VM Provisioning job is not valid. Node [%1] must not be present [%2]

%3

Fields

Message

The Remote Desktop Virtualization Host server named %2 successfully created a virtual desktop named %3 in the pooled virtual desktop collection named %4.

OU: %5
Time taken: %1 seconds

Fields

Message

The provisioning job for the pooled virtual desktop collection named %1 completed. 

Job GUID: %2
Result: %3

Fields

Fields

Message

The XML input specified for the VM Provisioning job is not in a valid format. Error: %2
Input XML:
%1

Fields

Fields

Message

The provisioning job failed to customize the unattend xml for the virtual machine [%1]. Error: %2
Unattend xml:
%3

Fields

Message

VM Provisioning operation [%1] failed for pool [%2]. Connection Broker could not create the machine account [%3] in the specified OU [%4] due to network connectivity issues, error: [%5]

Fields

Message

The Remote Desktop Connection Broker server is configured in high availability mode.

Fields

Message

The Remote Desktop Connection Broker server could not be configured in high availability mode.

Error: %1

Fields

Message

The Remote Desktop Connection Broker server was configured in high availability mode successfully.

Message

The Remote Desktop Connection Broker server detected that the central publishing service is not available and will notify all Remote Desktop Connection Broker plug-ins.

Message

The Remote Desktop Connection Broker server detected that the central publishing service is available.

Message

The Remote Desktop Connection Broker server detected that the database is not available and will notify all Remote Desktop Connection Broker plug-ins.

Message

The Remote Desktop Connection Broker server detected that the database is available.

Fields

Message

The Remote Desktop Connection Broker server could not install the database named %1 by using the connection string:
%2.
The database name in the connection string is shown as [master] because in order to create a new database with admin specified name, a connection must be made to master database.
Please check that the broker server has access to the SQL server, the path for -DatabaseFilePath parameter exists and contains the SQL Server database file, the connection to SQL databse is correct and SQL database is online. See the SQL Server and broker eventlog for more details.

Error: %3

Fields

Fields

Message

The Remote Desktop Connection Broker server successfully installed the database named %1 by using the connection string:
%2.

Fields

Fields

Message

The Remote Desktop Connection Broker server could not migrate the database by using the new connection string:
%1.

Error: %2

Fields

Fields

Message

The Remote Desktop Connection Broker server successfully migrated the database by using the new connection string:
%1.

Fields

Message

The Remote Desktop Connection Broker server could not enumerate the environments for the provider named %1 from the database.

Error: %2

Fields

Message

The Remote Desktop Connection Broker server could not enumerate the pooled virtual desktop collections for the provider named %1 from the database.

Error: %2

Fields

Message

The Remote Desktop Connection Broker server could not enumerate the targets for the provider named %1 from the database.

Pooled virtual desktop collection name: %2
Error: %3

Fields

Message

Failed to cleanup VM %1 on host %2. Error: %3

Fields

Message

The Remote Desktop Connection Broker server could not add a task for the virtual desktop named %1 because the limit of %2 tasks for this virtual desktop has been reached.
Error code: %3

Fields

Message

A SQL error has occurred
SQL state: %1

SQL Error message: %2

SQL Native Error: %3

Fields

Message

Failed to grant user %1 administrative access permission to server %2, error code %3

Fields

Message

Failed to grant user %1 TS access permission to server %2, error code %3

Fields

Message

Failed to resolve user connection, error code %1

Fields

Message

Failed to retrieve TARGET_GRANT_ADMIN_PRIVILEGE property for farm %1 on target server %2, error code %3

Fields

Message

The Remote Desktop Connection Broker server detected that the database is available, connecting using primary connection string.

Message

The Remote Desktop Connection Broker server detected that the database is not available using primary connection string. There is no secondary connection string specified. Please verify that the SQL server is available and update the primary connection string as soon as possible to reestablish connection and assure proper functionality.

Message

The Remote Desktop Connection Broker server detected that the database is not available using primary or secondary connection string. Contact the database administrator to identify the reason for failure. If the failure is due to changes to the connection string(s) (i.e. password expiration, user name changes, etc.) update the connection string(s) as soon as possible to reestablish connection and assure proper functionality. Use Set-RDDatabaseConnectionString with -RestoreDatabaseConnection parameter to ensure the connection string(s) are updated on all RD Connection Broker servers in the deployment. For any other reasons of failure (database server down, network connectivity, etc.) work with database administrator to get it solved. The deployment will be down until the database connectivity is reestablished.

Message

The Remote Desktop Connection Broker server detected that the database is not available using primary connection string. We have connected successfully using secondary connection string. Please update the primary connection string to assure continuity of service. We advise on updating secondary connection string at this time as well.

Fields

Message

Current database schema version: %1; current database plugin version: %2. Database schema upgrade required: %3.

Fields

Message

Database version mismatch detected; database schema upgrade is required. The service will not enter running state until database upgrade is complete.

Fields

Message

Database schema upgrade successful; database schema version: %1.

Fields

Fields

Message

Failed to upgrade database schema to version %1. Error code: %2.

Fields

Message

Connection Broker cannot connect to SQL database. Please ensure policy and firewall settings are properly configured to allow connections to the SQL Server. If the SQL Server is configured to listen on a dynamic port either change the port to a static TCP port or enable outgoing UDP traffic to port 1434 from the Connection Broker

Fields

Message

Connection Broker could not connect to the database and the issue was not resolved in the specified interval (%1 minutes). All RDS deployment services: RD Connection Broker (tssdis), RD Management (rdms) and RemoteApp and Desktop Connection (tscpubrpc) will be stopped. Please identify and fix the issue in order to restore connectivity to the database. After the database is online, please restart all RDS services manually or reboot the RD Connection Broker server(s).

Fields

Message

Connectivity to the database was restored. All RDS deployment services: RD Connection Broker (tssdis), RD Management (rdms) and  RemoteApp and Desktop Connection (tscpubrpc) are running and the deployment is functional.

Fields

Message

Failure to restart the following service: %1 as part of restoring database connectivity. Please restart the service manually or reboot the RD Connection Broker server. All RDS deployment services: RD Connection Broker (tssdis), RD Management (rdms) and  RemoteApp and Desktop Connection (tscpubrpc) should be running in order for the RDS deployment to be functional.

Fields

Message

High availability configuration failed. The Remote Desktop Connection Broker server failed to delete the database connection string registry values and the deployment will be unrecoverable if the registry values are not deleted. Please go to regedit.exe and delete manually DBConnString or DBSecondaryConnString values from HKLM\System\CurrentControlSet\Services\tssdis.

Message

The Remote Desktop Connection Broker server failed to create the secondary database connection string registry value. Please try to set the secondary database connection string again using the Deployment Properties in Server Manager.

Message

Desktop %1 from Collection %2 need to be started for connection request from user %3

Fields

Message

Desktop %1 from Collection %2 need to be started for connection request

Fields

Message

Desktop %1 from Collection %2 failed to start, error code %3

Fields

Message

Failed to notify status, Desktop %1, Collection %2, error code %3

Fields

Message

Failed to retrieve server status, Desktop %1, Collection %2, error code %3

Fields