Terminal Services is missing and may be preventing an external Seagate Replica from working properly. ... actually a full version of Windows Sever (or a service of Windows Server), so it's not a feature that can be added to a client OS. Solution: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\ServersI guess you could always copy the key you need to the new user and that's it As an IT consultant, I remote into several dozen servers throughout my days for maintenance and support. Only the Remote Computer Name or it's IP address can be entered. Creating an MRU10 entry will not create an 11th history entry. I hope your future articles will explain in detailed about HKLM\software\microsoft\windows nt\currentversion\terminal server\ and everything under it. Servers – Contains a list of all the Remote Desktop connections … HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default Step 3: After navigating to this location, look for the registry string that is present in the right pane. HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client; There are two registry keys here that need to be cleared: Default – Has the history of the last 10 RDP Connections. HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client Name: RDGClientTransport Type: Dword Data: 1 Proposed as answer by Amy Wang_ Moderator Wednesday, August 26, 2015 1:51 AM Marked as answer by Amy Wang_ Moderator Tuesday, September 1, … The history items are stored in [HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default] as entries MRU0 through MRU9. To do this, add a DWORD value named FilterQueueType to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR and set its value data to FFFFFFFF. The name of the registry string may be MRU number where the number may be 0 , 1 , 2 …. Locate and then click the following key in the registry: When you finish the program installation, by clicking Finish or by typing change user /execute, the system returns to Execute mode.The registry information that was written to the HKEY_CURRENT_USER registry hive during installation is written to the HKEY_CURRENT_USER registry hive for each user when they log on to the Terminal Server. I've read a few books about TS registry but the authors don't seem willing to explain them in detail. Under CE.NET 6.0 devices, it is not possible to define a username, password and domain in a setup tab before the first connection is made. When users logon the first time the DomainName\UserName is cached in the current user hive on client machine (one for each terminal server) at HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Servers\{server}\UsernameHint In change user option subkey, what's the data value of 0 or 1 means. This really isn't a server setting. If you declined to install the add-on, refresh the page and install it when prompted. Thanks. When connecting to the computer for the first time, the RDP client will show a window in which the username and password can be entered. Registry Keys for Terminal Services . The history list size is capped at 10 entries.