Help & DocumentationCloud Virtual MachineTroubleshooting IssuesInstance Related FailuresAbout Windows InstancesProblems occurred when you tried to log in to a Windows CVM remotely on Mac

Problems occurred when you tried to log in to a Windows CVM remotely on Mac

Last updated: 2019-12-20 19:39:47


This document describes the common problems you may encounter when remotely logging in to a Windows CVM on Mac through Microsoft Remote Desktop and how to solve them.

Problem Description

  • When trying to remotely log in to a Windows CVM through Microsoft Remote Desktop, you get the message: “The certificate couldn't be verified back to a root certificate.”

  • When using Remote Desktop Connection on Mac, you get the message: “Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.”


The following operations take Windows Server 2016 as an example.

Logging in to the CVM using VNC

  1. Log in to the CVM Console.

  2. In the Instance page, find the CVM and click Log in as shown below:

  3. In the “Log into Windows Instance” window, select “Alternative login methods (VNC)”, click Log In Now to log in to the CVM.

  4. In the login window, select “Send CtrlAltDel” in the top left corner, and click Ctrl-Alt-Delete to enter the system login interface as shown below:

Modifying the local group policy of the instance

  1. In the operating system interface, click , enter gpedit.msc, and press Enter to open the Local Group Policy Editor.

    You can also use the shortcut “Win+R” to open the Run box.

  2. In the left navigation tree, select Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security, double click Require use of specific security layer for remote (RDP) connections as shown below:

  3. In the “Require use of specific security layer for remote (RDP) connections” window, select Enabled, and set the Security Layer to RDP as shown below:

  4. Click OK to complete the configuration.

  5. Restart the instance and try to make the connection again. If the connection fails again, please submit a ticket.