About resolving problems with Windows Server system users that cannot be remote

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M01/7A/1C/wKiom1aiIi-wG_lyAAEMW7Oky54349.png "title=" Qq20160122203445.png "alt=" Wkiom1aiii-wg_lyaaemw7oky54349.png "/>

Sometimes, when we remote a machine when the Remote Desktop users do not have Telnet permissions, then how to solve this problem?

First, we open the Run window by using the shortcut key win+r on a remote Windows computer. Enter CMD in the Run window to open the Command Prompt window. Open the Local Group Policy Editor by entering the Gpedit.msc command directly in the Command Prompt window. If a prompt like "MMC Cannot create management" pops up, then we need to modify the registry.

Modify the registry. Click "Run" and enter "regedit" to open the registry. Modify the value of a variable in the registry: similar to Hkey_current_user\software\policies\microsoft\mmc\{8fc0b734-a0e1-11d1-a7d3-0000f87571e3}, Change the Restrict_Run value to 0. Exit reopen the Group Policy Editor we can see that the popup box will not pop up again.

After entering the Group Policy Editor, we may find that in "Local Computer Policy", the "MMC Cannot create snap-in" is displayed, "MMC Failed to create snap-in, the snap-in may not be installed correctly".

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M01/7A/1C/wKiom1aiJQTx36uFAACUyS-rUjo176.png "title=" Qq20160122204717.png "alt=" Wkiom1aijqtx36ufaacuys-rujo176.png "/>

So, if this is the case, we need to test the following methods:

Method One:

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M02/7A/1B/wKioL1aiJw-DKNY2AACMC6ve_MY861.png "title=" Qq20160122205519.png "alt=" Wkiol1aijw-dkny2aacmc6ve_my861.png "/>

Right-click My computer → properties → advanced tab → environment variables → system variables → double-click PATH environment variable → Check that the variable value contains the%systemroot%\system32;%systemroot%;%systemroot %\system32\wbem ", if not included then add, note if other system variables appear, do not delete, but to the half-width semicolon"; " Split, all the way "OK". If you do not resolve the issue after you add it, try method two.

Method Two:

Start menu → run → input regsvr32 gpedit.dll wsecedit.dll Enter, if "LoadLibrary (" Gpedit.dll ") failed-the specified module could not be found. The following actions are performed.

Locate the "Framedyn.dll" file in the C:\windows\system32\wbem directory and copy it to the C:\windows\system32 directory.

Start menu → run → input regsvr32 gpedit.dll wsecedit.dll, this will prompt DllRegisterServer success in Gpedit.dll Wsecedit.dll Success.

At this point, start menu → run → enter gpedit.msc to open the Group Policy Editor "Gpedit.msc".

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M02/7A/1B/wKioL1aiKbWyo07IAABZN5iAekg580.png "title=" 2.png " alt= "Wkiol1aikbwyo07iaabzn5iaekg580.png"/>

When you get to the Group Policy Editor, Tap Computer Configuration--Windows Settings--Security settings--User rights assignment, local policies.

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M01/7A/1B/wKioL1aiKiKiLTa4AACFxrWlI0g257.png "title=" 3.png " alt= "Wkiol1aikikilta4aacfxrwli0g257.png"/>

Look for "Deny login via Terminal Services" to see if there are Remote Desktop users and the domain user account that needs to be logged in, such as please delete. In the Allow log on through Remote Desktop Services Property window, see if there are Remote Desktop users and the domain user account that needs to be logged in, such as no Add. Save exit.

Retry the Remote Desktop and discover that the remote is successful.

This article from "Dream Awake" blog, declined reprint!

About resolving problems with Windows Server system users that cannot be remote