Windows 8
- The rate at which the process is writing bytes to I/O operations. This counter counts all I/O activity generated by the process ...
- The rate at which the Server is receiving bytes from the network clients on this CPU. This value is a measure of how busy ...
- The rate at which the Server is sending and receiving bytes with the network clients on this CPU. This value is a measure ...
- The rate at which the Server is sending bytes to the network clients on this CPU. This value is a measure of how busy the ...
- The rate, in seconds, at which bytes are being sent from the SMB File Server in this session to the client. This value includes ...
- The rate, in seconds, at which bytes are being sent from the SMB File Server related to this share to its clients. This value ...
- The RD Connection Broker server cannot communicate with the Hyper-V server. Ensure that there are no network issues, and ...
- The RD Connection Broker server could not be added to the deployment because the following deployment servers were not reachable: ...
- The RD Connection Broker server could not be removed from the deployment because the following deployment servers were not ...
- The RD Connection Broker server does not have access to add the virtual desktops to the Active Directory domain. Configure ...
- The RD Connection Broker server must have permissions to join virtual desktops to the domain. Choose the organizational unit ...
- The RD Connection Broker server {0} could not be added. At least one of the required services is not running on the RD Connection ...
- The RD Connection Broker server {0} is not available on the network or a dependent service is not running. Select a different ...
- The RD Connection Broker server's status is not active for management. The current active server is {0}. Refer to the active ...
- The RD Gateway connection ended because periodic user authentication failed. Try reconnecting with a correct user name and ...
- The RD Gateway connection ended because periodic user authorization failed. Try reconnecting with a correct user name and ...
- The RD Gateway connection ended because periodic user authorization failed. Your computer or device didn't pass the Network ...
- The RD Gateway connection ended because periodic user authorization failed. Your PC or device didn't pass the Network Access ...
- The RD Gateway Management snap-in console cannot connect to the server "{0}". To connect to this server, you must be a member ...
- The RD Gateway Manager snap-in console cannot connect to the server "{0}". Ensure that you have typed the name or IP address ...
- The RD Gateway server "%1" could not be deleted from the list of servers in the RD Gateway server farm. The following error ...
- The RD Gateway server "%1" is not a member of a domain and therefore cannot be added to the RD Gateway server farm. To add ...
- The RD Gateway server cannot open the resource authorization policy store on Authorization Manager (Azman). The following ...
- The RD Gateway server certificate cannot be changed. The following error occurred: "%2". Verify the certificate and try changing ...
- The RD Gateway servers "%1" could not be added to the Remote Desktop Gateway managed group. The following error occurred: ...
- The RD Gateway service cannot determine the version of Windows that this computer is running. Therefore, users cannot connect ...
- The RD Gateway service could not be initialized. The following error occurred: "%2". To diagnose possible causes for this ...
- The RD Gateway service is shutting down. This maybe voluntary administrator restart or a configuration driven restart due ...
- The RD Gateway-managed computer groups cannot be read. This problem might be due to a corrupted store for the RD RAP. Alternatively, ...
- The RD Licensing database does not belong to this Remote Desktop license server. The Remote Desktop license server will update ...
- The RD Licensing database file is not valid. This file has been renamed to "%1!s!", and the license server will start up ...
- The RD Licensing database is corrupt. RD Licensing could not rename the RD Licensing database file "%1!s!" to create a backup. ...
- The RD Licensing database is not consistent. All licenses will be removed. To resolve this issue, rebuild the RD Licensing ...
- The RD Licensing database might be corrupted. To resolve this issue, ensure that the required groups are granted the correct ...
- The RD Licensing database path could not be set to "%1!s!" during the installation of RD Licensing. Win32 error code: %2!s! ...
- The RD Licensing Diagnoser tool is running with local account credentials. The Total Number of licenses Available value may ...
- The RD Licensing grace period has expired and Licensing mode for the Remote Desktop Session Host server has not been configured. ...
- The RD Licensing grace period has expired and Licensing mode for the Remote Desktop Virtualization Host server has not been ...
- The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. ...
- The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. ...
- The RD Licensing grace period is about to expire on %1 and the service has not registered with a license server with installed ...
- The RD Licensing grace period is about to expire on %1 and the service has not registered with a license server with installed ...
- The RD Licensing Manager cannot access the system registry. Ensure that you have administrator privileges on the system, ...
- The RD Licensing Manager cannot complete the activation process. Ensure that the PIN is entered correctly, and then retry ...
- The RD Licensing Manager cannot complete the license server activation process. The PIN is not valid for the license server. ...
- The RD Licensing Manager cannot connect to the registry of the license server. Check your network connections, and then retry ...
- The RD Licensing Manager cannot connect to the selected license server. Ensure that the license server is installed and running. ...
- The RD Licensing Manager cannot obtain the activation information from the license server. Check connectivity with the license ...
- The RD Licensing Manager cannot read the registry entries needed to connect to the Microsoft Clearinghouse. Reinstall RD ...
- The RD Licensing Manager cannot read the response from the Microsoft Clearinghouse. The site may have become unavailable ...
- The RD Licensing Manager cannot retrieve cryptography keys from the license server. Check your network connections, and then ...
- The RD Licensing Manager encountered a remote procedure call (RPC) error. Check your network connections, and then retry ...
- The RD Licensing Manager encountered an error while installing the client license key pack. Check your network connections, ...
- The RD Licensing Manager is unable to verify the license server ID. Ensure that the license server ID is entered correctly, ...
- The RD Licensing Manager received an unrecognized response from the Microsoft Clearinghouse. The site may be experiencing ...
- The RD Licensing Manager was not able to install the client license key pack. Ensure that the correct information is entered, ...
- The RD RAP "{0}" could not be created because creation of RD Gateway managed computer group failed for the following reason: ...
- The RD Session Host Server authentication certificate configuration data was invalid and the service reset it. If the computer ...
- The RD Session Host server cannot install a new template-based certificate to be used for Transport Layer Security (TLS) ...
- The RD Session Host server cannot register 'TERMSRV' Service Principal Name to be used for server authentication. The following ...
- The RD Session Host server could not be added to the deployment because the following Remote Desktop Connection Brokers were ...
- The RD Session Host Server has failed to create a new self signed certificate to be used for RD Session Host Server authentication ...
- The RD Session Host Server has failed to replace the expired self signed certificate used for RD Session Host Server authentication ...
- The RD Session Host Server is configured to use a certificate but is unable to access the private key associated with this ...
- The RD Session Host Server is configured to use a certificate that does not contain an Enhanced Key Usage attribute of Server ...
- The RD Session Host Server is configured to use a certificate that is expired. %1 The SHA1 hash of the certificate is in ...
- The RD Session Host Server is configured to use a certificate that will expire in %2 days. %1 The SHA1 hash of the certificate ...
- The RD Session Host server is configured to use a template-based certificate for Transport Layer Security (TLS) 1.0\Secure ...
- The RD Session Host Server is configured to use SSL with user selected certificate, however, no usable certificate was found ...
- The RD Session Host Server listener %1 is configured with inconsistent authentication and encryption settings. The Encryption ...
- The RD Session Host server {0} is not available on the network. To update the collection properties, all servers in the collection ...
- The RD Session Host servers {0} are not available on the network. To update the collection properties, all servers in the ...
- The RD Virtualization Host server could not add the virtual desktop, %1, to the farm, %2, because the virtual desktop does ...
- The RD Virtualization Host server could not be added to the deployment because the following RD Connection Broker servers ...
- The RD Web Access server could not be added to the deployment because the following RD Connection Broker servers are not ...