Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Example Analysis of invalid windows remote Desktop function and RDS error report

2025-04-11 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)05/31 Report--

Today, I will talk to you about the example analysis of invalid windows remote Desktop function and RDS error report. Many people may not know much about it. In order to make you understand better, the editor summarized the following content for you. I hope you can get something according to this article.

Windows remote Desktop is a service that is widely used by everyone, and we often encounter some mistakes of one kind or another. Here are two typical cases.

1. Remote Desktop, authentication error: the required function is not supported

The error phenomenon is shown in the following figure:

Due to the update of windows10, recently, many friends will encounter the error of mstsc remote connection desktop. The flag provided by the function is invalid and has nothing to do with the network, and the feedback from ping and telnet does not have a problem with the network. So the problem lies with the local computer.

This is because there is a remote code execution vulnerability in the unpatched version of CredSSP, and those who successfully exploit this vulnerability can relay user credentials on the target system to execute code, and any application that relies on CredSSP for authentication may be vulnerable to this type of vulnerability.

Solution:

Microsoft's solution:

Https://support.microsoft.com/zh-cn/help/4093492/credssp-updates-for-cve-2018-0886-march-13-2018

Specific solutions:

Run gpedit.msc and find computer configuration > Administrative templates > system > credential assignment > encryption Oracle Correction

Select enable and select susceptibility.

Add: after the local group policy is configured, you also need to refresh the policy: select start and open the run window through search. Enter cmd, click OK, and run gpupdate in the command line dialog box.

After we set it up, we'll try to connect again.

If you are Win10 Home Edition, you need to uninstall this update, find "Uninstall programs" in the Control Panel, select "View installed updates", and uninstall the newly installed patch (with the security update KB410**** with Microsoft Windows).

The second update, released on May 8, 2018, changes the default behavior from "vulnerable" to "mitigation" option. The relevant Microsoft knowledge base number is listed in CVE-2018-0886.

Note: any changes to the encryption Oracle correction will need to be restarted.

2. RDS components cause failure to report errors remotely, as shown in the figure:

RDS is short for Remote Desktop Service, and remote Desktop Services accelerate and extend desktop and application deployment to any device. Remote Desktop Services enable virtual machine infrastructure (VDI), session-based desktops, and applications, allowing users to work wherever they want.

Because the remote desktop is inaccessible after the component is installed, uninstall the component first to confirm that it is caused.

After uninstalling, it is found that the remote Desktop can be accessed normally.

Specific analysis:

This is mainly because after installing RDS, RDS generates six role services:

1. Remote Desktop Web access: RD Web Access

Remote Desktop Web access (RD Web access) allows users to access RemoteApp and desktop connections through the start menu on the computer running Windows or through a web browser. RemoteApp and Desktop connections provide custom views of RemoteApp programs and session-based computers in the session collection, as well as custom views of RemoteApp programs and virtual machines in the virtual machine collection.

2. Remote Desktop Gateway: RD Gateway

The remote Desktop Gateway (RD Gateway) allows authorized users to connect to virtual machines, RemoteApp programs, and session-based computers in the enterprise's internal network from any device connected to Internet.

3. Remote Desktop Licensing: RD Licensing

Remote Desktop Licensing (RD Licensing) manages the licenses required to connect to a remote Desktop session host server or virtual machine. You can use RD licenses to install, issue, and track the availability of licenses.

4. Remote Desktop connection Agent: RD Connection Broker

Remote Desktop connection Agent (RD connection Agent): allows users to reconnect to their existing virtual machines, RemoteApp programs, and session-based computers. Allows you to distribute the load evenly among the RD session host servers in the session set or among the shared virtual machines in the shared virtual machine set. Provides access to virtual machines in the virtual machine collection.

5. Remote Desktop Virtualization Host: RD Virtualization Host

Remote Desktop Virtualization hosts (RD Virtualization hosts) integrate with Hyper-V to deploy virtual machine collection pools or personal virtual machine collections within the organization.

6. Remote Desktop session Host: RD Session Host

The remote desktop session host (RD session host) allows the server to host RemoteApp programs or session-based computers. Users can connect to the RD session host servers in the session collection to run programs, save files, and use resources on those servers.

Pay attention to the remote Desktop session host role, which is free for 120 days and will be paid later. If there is no payment, the remote connection will fail. Normally, the Windows server provides free remote desktop management authorization for two users by default. If there is a higher connection requirement, you need to configure the remote Desktop session Host server role and purchase and configure the appropriate authorization before you can use more remote Desktop to manage concurrency. After installing and configuring the remote Desktop session host role, the original default 2 free connection licenses will be cancelled at the same time. Therefore, when the relevant authorization is not configured correctly, it will cause the remote desktop to fail to connect, and the above error will appear. Solution: after installing the remote Desktop session host role, there are two solutions to the inability to remotely:

1. After configuring the remote desktop session host server, purchase and configure the corresponding certificate authorization on Microsoft's official website. For relevant operation methods, please refer to Microsoft's official documentation.

2. Delete the remote Desktop session host role and use the default 2 free connection authorizations.

Example:

Windows 2012 system operation method:

1. Log in to the Windows instance using the console remote connection feature.

2. Select start and open the running window through the search. Enter servermanager.msc and click OK. 3. In the upper right corner of the server manager page, select manage > Delete role.

4. In the remove functions and roles window, click next, and then click next. 5. In the third step of the wizard, uncheck the remote desktop service and other default configurations.

6. Restart the instance inside the instance. For other versions, please refer to the examples of the corresponding articles online. Add: another method: after the authorization of Windows_Server_2012_2016 remote Desktop expires in 120 days, it can be solved like this. 1. Try to delete the following registry, then uninstall and activate the remote Desktop service:

HKEY_LOCAL_MACHINE\ Software\ Microsoft\ MSLicensing

HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Control\ Terminal Server\ RCM\ Grace Period

If you encounter an error that cannot be deleted when deleting the registry, you can click Grace Period with the left mouse button, and then right-click "permissions" to add full control of Adminsitrator permissions, and then delete it. 2, there is also a delete registry will be denied access can be the left mouse click GracePeriod, and then right-click and select the "permissions" option, and in the "permissions" dialog box, click the "Advanced" button-click the "owner" tab, change the owner to the current user and check "replace the owner of child containers and objects" and click "OK" button. Then click GracePeriod with the left mouse button, right-click "permissions", add full control of everyone permissions, and then delete it after confirmation. After reading the above, do you have any further understanding of the example analysis of invalid windows remote Desktop function and RDS error? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report