Windows 8

  1. The remediation server group that is selected is not valid. You cannot save this policy until you configure it with a valid ...
  2. The Remote Access and Routing service did not start because of the following error. Check the event log for more information: ...
  3. The Remote Access cluster server is deployed with a single network adapter. Specify the same settings for both the internal ...
  4. The remote access connection completed, but authentication failed because a certificate that validates the server certificate ...
  5. The remote access connection completed, but authentication failed because a trusted root certificate that validates the user ...
  6. The remote access connection completed, but authentication failed because of an error in the certificate that authenticates ...
  7. The remote access connection completed, but authentication failed because of an error in the certificate that the client ...
  8. The remote access connection completed, but authentication failed because the certificate in the Trusted Root Certification ...
  9. The remote access connection completed, but authentication failed because the certificate on the server computer does not ...
  10. The remote access connection completed, but authentication failed because the certificate that authenticates the client to ...
  11. The remote access connection completed, but authentication failed because the certificate that authenticates the client to ...
  12. The remote access connection completed, but authentication failed because the certificate that authenticates the client to ...
  13. The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate ...
  14. The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate ...
  15. The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate ...
  16. The remote access connection completed, but authentication failed because the trusted root certificate that is used to validate ...
  17. The remote access connection with the correlation ID %1 has Network Access Protection (NAP)-Enforcement enabled on it. The ...
  18. The remote access connection with the correlation ID %1 received an unexpected/mismatched response to its Statement of Health ...
  19. The Remote Access Management service cannot be started on %1!s!. Modify the service startup setting to Automatic (Delayed ...
  20. The Remote Access server being added is configured with both IPv4 and IPv6 addresses. This is an IPv4 only deployment, and ...
  21. The Remote Access server cannot allocate a route for the user connected on port %1 because of the following error: %2 The ...
  22. The Remote Access Server was unable to acquire an IP Address from the DHCP Server to be used on the Server Adapter. Incoming ...
  23. The Remote Access Server was unable to renew the lease for IP Address %1 from the DHCP Server. The user assigned with this ...
  24. The Remote Access Server will stop using IP Address %1 (either because it was unable to renew the lease from the DHCP Server, ...
  25. The Remote Access Service is not configured to receive calls or all ports configured for receiving calls are in use by other ...
  26. The Remote Assistance password provided was incorrect. The RDP session was terminated, IP address of the connecting machine ...
  27. The remote client and the server are running different versions of RemoteFX. The system may not work correctly. VM Name: ...
  28. The remote computer cannot be authenticated due to problems with its security certificate. Security certificate problems ...
  29. The remote computer cannot be authenticated due to problems with its security certificate. Security certificate problems ...
  30. The remote computer could not be authenticated due to problems with its security certificate. It may be unsafe to proceed. ...
  31. The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the ...
  32. The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact ...
  33. The remote computer that you are trying to connect to requires Network Level Authentication (NLA), but your Windows domain ...
  34. The remote connection was denied because the user name and password combination you provided is not recognized, or the selected ...
  35. The remote connection was not made because Point-to-Point Tunneling Protocol (PPTP) is incompatible with IPv6. Use any other ...
  36. The remote connection was not made because the attempted VPN tunnels failed. The VPN server might be unreachable. If this ...
  37. The remote content you are attempting to access is copy protected. If you do not have a license for this content on your ...
  38. The remote control of the console was terminated because the display mode was changed. Changing the display mode in a remote ...
  39. The remote create cross reference operation failed on the Domain Naming Master FSMO. The operation's error is in the extended ...
  40. The remote DCOM server on %1 cannot be found. Make sure that the DCOM server on %1 is registered. Run "regsvr32 Rrasprxy.dll" ...
  41. The Remote Desktop connection authorization policies (RD CAPs) cannot be read because a custom authorization plug-in is in ...
  42. The Remote Desktop connection authorization policies (RD CAPs) cannot be read because central cap is enabled. Please do refresh ...
  43. The Remote Desktop connection authorization policies (RD CAPs) cannot be read. This problem might be due to a corrupted store ...
  44. The Remote Desktop connection authorization policy (with Name[s {0}) stored on the server running Network Policy Server (NPS) ...
  45. The Remote Desktop Connection Broker server could not add a task for the virtual desktop named %1 because the limit of %2 ...
  46. The Remote Desktop Connection Broker server could not enumerate the environments for the provider named %1 from the database. ...
  47. The Remote Desktop Connection Broker server could not enumerate the pooled virtual desktop collections for the provider named ...
  48. The Remote Desktop Connection Broker server could not enumerate the targets for the provider named %1 from the database. ...
  49. The Remote Desktop Connection Broker server could not install the database named %1 by using the connection string: %2. The ...
  50. The Remote Desktop Connection Broker server could not migrate the database by using the new connection string: %1. Error: ...
  51. The Remote Desktop Connection Broker server detected that the central publishing service is not available and will notify ...
  52. The Remote Desktop Connection Broker server detected that the database is not available and will notify all Remote Desktop ...
  53. The Remote Desktop Connection Broker server successfully installed the database named %1 by using the connection string: ...
  54. The Remote Desktop Connection Broker service is not running on the Remote Desktop Connection Broker (RD Connection Broker) ...
  55. The Remote Desktop Gateway (RD Gateway) server does not have a Remote Desktop connection authorization policy (RD CAP) enabled. ...
  56. The Remote Desktop Gateway (RD Gateway) server does not have a Remote Desktop resource authorization policy (RD RAP) enabled. ...
  57. The Remote Desktop Gateway (RD Gateway) server has reached the limit on the maximum number of simultaneous connections allowed. ...
  58. The Remote Desktop Gateway (RD Gateway) server is configured to accept only connections from clients using the latest version ...
  59. The Remote Desktop Gateway (RD Gateway) server is configured to use a self-signed certificate. By default, a self-signed ...
  60. The Remote Desktop Gateway (RD Gateway) server is unable to contact the server running Network Policy Server (NPS) that contains ...
  61. The Remote Desktop Gateway (RD Gateway) server Secure Sockets Layer (SSL) certificate may not have a valid certificate subject ...
  62. The Remote Desktop Gateway server administrator has ended the connection. Try reconnecting later or contact your network ...
  63. The Remote Desktop Gateway server has ended the connection. Try reconnecting later or contact your network administrator ...
  64. The Remote Desktop Gateway service cannot determine the version of Windows that this computer is running. Therefore, users ...
  65. The Remote Desktop Gateway service does not have sufficient permissions to access the Secure Sockets Layer (SSL) certificate ...
  66. The Remote Desktop Gateway service requires a valid Secure Sockets Layer (SSL) certificate to accept connections. Ensure ...
  67. The Remote Desktop license server "%1" does not have a sufficient number of permanent licenses for product "%3". Only %2 ...
  68. The Remote Desktop license server "%1" does not have any licenses installed and registered with the Microsoft Clearinghouse ...
  69. The Remote Desktop license server "%1" does not have any remaining permanent licenses of the type "%2". As a result, the ...
  70. The Remote Desktop license server "%1" has not been activated and therefore will only issue temporary licenses. To issue ...
  71. The Remote Desktop license server %1 does not support the version of the operating system running on the Remote Desktop Session ...
  72. The Remote Desktop license server %1 does not support the version of the operating system running on the Remote Desktop Virtualization ...
  73. The Remote Desktop license server cannot communicate with another Remote Desktop license server because of the following ...
  74. The Remote Desktop license server cannot detect locally installed licenses or communicate with other Remote Desktop license ...
  75. The Remote Desktop license server cannot update the license attributes for user "%1!s!" in the Active Directory Domain "%2!s!". ...