Windows 8

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