1. Install the rdpwrap software
2. Set the rdpwrap software for related configuration
3. Modify the rdpwrap.ini file according to the current system version number
4. Set up the windows account and perform remote desktop testing
Obtain the RDP software and related configuration files
rdpwrap related compressed package and rdpwrap.ini configuration file with corresponding version number
Get RDP software and configuration file from Baidu Netdisk
https://pan.baidu.com/s/1EJQnfUMoJUOkPS4u3xp4Zw?pwd=8853
github to get the RDP software
https://github.com/stascorp/rdpwrap/releases
github to get the rdpwrap.ini configuration file
https://github.com/sebaxakerhtc/rdpwrap.ini
to install the rdpwrap software
1. Unzip the compressed file RDPWrap-v1.6.2.zip to get
2. Use the script to install the software, right click on install.bat, and run it as an administrator
3. Start the command window to install the program. In the command log, record
the location of the rdpwrap.dll file and the rdpwrap.ini file. Mine are all in the C:\Program Files\RDP Wrapper directory of the system c drive, and the relevant installation logs And my own understanding, the general Windows configuration file is in the C drive by default
4. Use the RDPConf.exe file to check whether the service is installed, or run it with administrator privileges, if your Windows version happens to be within the rdpwrap.ini configuration file , then there is a high probability to open
the configuration file and check that it is all green. If it is all green, restart the computer and it can be used normally. Find the corresponding rdpwrap.ini configuration to solve the problem that it is not all green
5. Find the rdpwrap.ini file, the log information in the above picture shows that C:\Program Files\RDP Wrapper\rdpwrap.ini is in this directory, we need to edit this file To edit, use Notepad to open this file, you can see two lines of eye-catching comments: Do not change without knowledge
6. We must modify, even if we have no knowledge, we must try, we need to find the configuration file of the corresponding version, here I searched directly on github, the address of the warehouse is, here is the accelerated connection of csdn, it is recommended to open the copy connection, the use of csdn may not be able to search
https://github.com/sebaxakerhtc/rdpwrap.ini because the synchronization is not timely
After entering the directory, search according to the win version information. My version information on the previous configuration page is 10.0.22621.608. Search, open the text on git to copy, and save it as a text file. 6. Open the copied version of rdpwrap.ini
and C:\Program Files\RDP Wrapper\rdpwrap.ini for comparison and modification
The [Main] part [SLPolicy] part [PatchCodes] part is basically the same thing, no need to modify. Copy and
insert the corresponding content of the version number before the old version number of rdpwrap.ini.
Search for the [SLInit] part, which is basically the same without modification
and save this modification A good configuration file, and then replace the configuration file under C:\Program Files\RDP Wrapper\rdpwrap.ini with administrator privileges. Use
RDPConf.exe again to check the configuration, and now it shows full support, and there is still one Listener state monitoring in red
The Listener state problem is solved. You can try to restart the computer. Restarting the computer will restart related services. You can also use relevant command information to open the cmd terminal in administrator mode, enter the command net stop termservice to stop the service, enter net start termservice to start the service, and complete the restart (The service here has been shutting down haha, I still use the restart method)
net stop termservice
net start termservice
Use RDPConf.exe again to check the configuration status. The current status is all green and the
current service is available. We can perform a remote connection test normally. Here we use the built-in test software to test. Double-click to open the RDPCheck.exe software, and click Connect to perform a remote connection. The test
found that there is only a blurry wallpaper, and there is no place to log in the account information. This is caused by the Windows Microsoft network login account.
Method 1: We can change the network account to a local account, which will also log out the current account and need to save the current work, otherwise it will be lost. Related Information
Method 2 We need to create a Windows local account, set the relevant pin code, and give this account administrator authority, so that when logging in to this account, a local user information will be assigned, which is equivalent to a new user's computer desktop information account
setting After success, we are going to connect to the network. At this time, relevant user login information appears.
Method 3:
Log in with a Microsoft network account Use RDPConf.exe, change the authentication method to network authentication, and use the Microsoft account to log in
after the application
The network user name and network user password are used to log in. Note that the pin code used for local login cannot be used. It is possible that the verification fails. At this point, the
function of network connection is basically completed. This method is very suitable for the intranet environment. If possible Using the extranet, you can also use remote software tools such as sunflower
Regarding the outbound rules of the firewall, the basic port used is 3389, and the software will help configure it here. If no inbound and outbound rules are configured, you can manually add relevant rules for port 3389 in the inbound and outbound rules of the firewall.
If you accidentally corrupt the rdpwrap.ini configuration file, you can use the uninstall.bat script to uninstall it, and then run install.bat again to install it.
Personal understanding of the content of the command window: after stopping the process service, the previous configuration will be killed File ini and dll libraries, modify the registry (resolve the startup of the service), set the firewall, and most likely set the inbound and outbound rules of port 3389
