In working with many who use remote desktop to connect to servers, workstations, etc, the question has been asked – How can you increase the number of remembered servers in the remote desktop connection list? Of course for true administrative use, we highly recommend the use of the remote desktop connection manager which provides a powerful interface for grouping, saving, and connecting to RDP resources. However, if one simply wants to continue using the builtin RDP tool provided with Windows and wants to increase the number of servers listed, this can be achieved not by a registry tweak or even an option in your Remote Desktop connection properties, but by increasing the size of your Jump Lists value.
In order to increase this value:
***Update*** Windows 10
The method listed above doesn’t work for Windows 10 as there is no “Start Menu” tab in the final release of Windows 10 to modify settings for. There is however, a way to do this from the registry. There are two DWORD value keys that need to be added to the registry of the Windows 10 machine here:
Change the BASE of the DWORD value you are adding to Decimal and enter the Value Data as the number of items you want to be show
After you reboot, you can right click on the open program in the Task bar and you should have the new number of recent items listed. ***NOTE***, in my testing, the change didn’t affect the drop down box in the remote desktop connection box when launched, only the task bar program recent items objects.
-->
When a user logs on to a Remote Desktop Services–enabled computer, a session is started for the user. Each session is identified by a unique session ID. Fallout 4 ps4 code. Because each logon to a Remote Desktop Connection (RDC) client receives a separate session ID, the user-experience is similar to being logged on to multiple computers at the same time; for example, an office computer and a home computer.
Each remote desktop session is associated with an interactive window station. The only supported window station name for an interactive window station is 'WinSta0'; therefore each session is associated with its own 'WinSta0' window station. There are three standard desktops for each window station: the Winlogon desktop, the screen saver desktop, and the interactive desktop.
The user associated with the interactive window station for a session is known as the interactive user. On a Remote Desktop Connection (RDC) client there can be multiple interactive users in addition to the interactive user on the Remote Desktop Services console. To retrieve the identifier of the session currently attached to the console, use the WTSGetActiveConsoleSessionId function.
When a user logs off from a Remote Desktop Connection (RDC) client, the session that the client has on the Remote Desktop Session Host (RD Session Host) server (formerly known as a terminal server) is deleted and the window stations and desktops associated with that session are removed. However, because the Remote Desktop Services console session is never deleted, the window stations associated with the console session are not deleted. This affects how applications behave in a Remote Desktop Services environment when they are configured to run in the security context of the interactive user, also known as the 'RunAs Interactive User' object activation mode.
For more information about starting a local server process on a specified session, see Session-to-Session Activation with a Session Moniker and Using a Session Moniker. For more information about security contexts, see The Client's Security Context.
Related topics
Remote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft, which provides a user with a graphical interface to connect to another computer over a network connection. The user employs RDP client software for this purpose, while the other computer must run RDP server software.
Clients exist for most versions of Microsoft Windows (including Windows Mobile), Linux, Unix, macOS, iOS, Android, and other operating systems. RDP servers are built into Windows operating systems; an RDP server for Unix and OS X also exists. By default, the server listens on TCPport 3389[1] and UDP port 3389.[2]
Microsoft currently refers to their official RDP client software as Remote Desktop Connection, formerly 'Terminal Services Client'.
The protocol is an extension of the ITU-TT.128 application sharing protocol.[3]
History[edit]
Every version of Microsoft Windows from Windows XP onwards[4] includes an installed Remote Desktop Connection (RDC) ('Terminal Services') client (mstsc.exe) whose version is determined by that of the operating system or by the last applied Windows Service Pack. The Terminal Services server is supported as an official feature on Windows NT 4.0 Terminal Server Edition, Windows 2000 Server, all editions of Windows XP except Windows XP Home Edition, Windows Server 2003, Windows Home Server, on Windows Fundamentals for Legacy PCs, in Windows Vista Ultimate, Enterprise and Business editions, Windows Server 2008 and Windows Server 2008 R2 and on Windows 7 Professional and above.[citation needed]
Microsoft provides the client required for connecting to newer RDP versions for downlevel operating systems. Since the server improvements are not available downlevel, the features introduced with each newer RDP version only work on downlevel operating systems when connecting to a higher version RDP server from these older operating systems, and not when using the RDP server in the older operating system.[clarification needed]
Version 4.0[edit]
Based on the ITU-T T.128 application sharing protocol (during draft also known as 'T.share') from the T.120 recommendation series, the first version of RDP (named version 4.0) was introduced by Microsoft with 'Terminal Services', as a part of their product Windows NT 4.0 Server, Terminal Server Edition. The Terminal Services Edition of NT 4.0 relied on Citrix's MultiWin technology, previously provided as a part of Citrix WinFrame atop Windows NT 3.51, in order to support multiple users and login sessions simultaneously. Microsoft required Citrix to license their MultiWin technology to Microsoft in order to be allowed to continue offering their own terminal-services product, then named Citrix MetaFrame, atop Windows NT 4.0. The Citrix-provided DLLs included in Windows NT 4.0 Terminal Services Edition still carry a Citrix copyright rather than a Microsoft copyright. Later versions of Windows integrated the necessary support directly. The T.128 application sharing technology was acquired by Microsoft from UK software developer Data Connection Limited.[5][6]
Version 5.0[edit]
This version was introduced with Windows 2000 Server, added support for a number of features, including printing to local printers, and aimed to improve network bandwidth usage.
Version 5.1[edit]
This version was introduced with Windows XP Professional and included support for 24-bit color and sound. The client is available for Windows 2000, Windows 9x, Windows NT 4.0.[7] With this version, the name of the client was changed from Terminal Services Client to Remote Desktop Connection; the heritage remains to this day, however, as the underlying executable is still named mstsc.exe.
Version 5.2[edit]
This version was introduced with Windows Server 2003, included support for console mode connections, a session directory, and local resource mapping. It also introduces Transport Layer Security (TLS) 1.0 for server authentication, and to encrypt terminal server communications.[8] This version is built into Windows XP Professional x64 Edition and Windows Server 2003 x64 & x86 Editions.
Version 6.0[edit]
This version was introduced with Windows Vista and incorporated support for Windows Presentation Foundation applications, Network Level Authentication, multi-monitor spanning and large desktop support, and TLS 1.0 connections.[9] Version 6.0 client is available for Windows XP SP2, Windows Server 2003 SP1/SP2 (x86 and x64 editions) and Windows XP Professional x64 Edition. Microsoft Remote Desktop Connection Client for Macintosh OS X is also available with support for Intel and PowerPC Mac OS versions 10.4.9 and greater.
Server 2012 can support RDC 6.0 or later.
Version 6.1[edit]
This version was released in February 2008 and is included with Windows Server 2008, as well as with Windows Vista Service Pack 1. The client is included with Windows XP SP3.[10] In addition to changes related to how a remote administrator connects to the 'console',[11] this version has new functionality introduced in Windows Server 2008, such as connecting remotely to individual programs and a new client-side printer redirection system that makes the client's print capabilities available to applications running on the server, without having to install print drivers on the server.[12][13]
Version 7.0[edit]
This version was released to manufacturing in July 2009 and is included with Windows Server 2008 R2, as well as with Windows 7.[14] With this release, also changed from Terminal Services to Remote Desktop Services. This version has new functions such as Windows Media Player redirection, bidirectional audio, multi-monitor support, Aero glass support, enhanced bitmap acceleration, Easy Print redirection,[15]Language Bar docking. The RDP 7.0 client is available on Windows XP SP3 and Windows Vista SP1/SP2 through KB969084.[16] RDP 6.1 client and RDP 7.0 client are not supported on Windows Server 2003 x86 and Windows Server 2003 / Windows XP Professional x64 editions. RDP 7.0 is also not supported on Windows Server 2008. RDP 7.0 clients also do not support connecting to terminal servers running Windows 2000 Server.[17]
Most RDP 7.0 features like Aero glass remote use, bidirectional audio, Windows Media Player redirection, multiple monitor support and Remote Desktop Easy Print are only available in Windows 7 Enterprise or Ultimate editions.[18][19]
Version 7.1[edit]
Release 7.1 of RDP was included with Windows 7 Service Pack 1 and Windows Server 2008 R2 SP1 in 2010. It introduced RemoteFX, which provides virtualized GPU support and host-side encoding.
![]() Version 8.0[edit]
This version was released in Windows 8 and Windows Server 2012. This version has new functions such as Adaptive Graphics (progressive rendering and related techniques), automatic selection of TCP or UDP as transport protocol, multi touch support, DirectX 11 support for vGPU, USB redirection supported independently of vGPU support, etc.[20][21] A 'connection quality' button is displayed in the RDP client connection bar for RDP 8.0 connections; clicking on it provides further information about connection, including whether UDP is in use or not.[22]
The RDP 8.0 client and server components are also available as an add-on for Windows 7 SP1. The RDP 8.0 client is also available for Windows Server 2008 R2 SP1, but the server components are not. The add-on requires the DTLS protocol to be installed as prerequisite.[22] After installing the updates, for the RDP 8.0 protocol to be enabled between Windows 7 machines, an extra configuration step is needed using the Group Policy editor.[23]
A new feature in RDP 8.0 is limited support for RDP session nesting; it only works for Windows 8 and Server 2012 though, Windows 7 and Server 2008 R2 (even with the RDP 8.0 update) do not support this feature.[24]
The 'shadow' feature from RDP 7, which allowed an administrator to monitor (snoop) on a RDP connection has been removed in RDP 8. The Aero Glass remoting feature (applicable to Windows 7 machines connecting to each other) has also been removed in RDP 8.[21][22]
Version 8.1[edit]
This version was released with Windows 8.1 and Windows Server 2012 R2. A RDP 8.1 client update exists for Windows 7 SP1 as well, but unlike the RDP 8.0 update for Windows 7, it does not add a RDP 8.1 server component to Windows 7. Furthermore, if RDP 8.0 server function is desired on Windows 7, the KB 2592687 (RDP 8.0 client and server components) update must be installed before installing the RDP 8.1 update.[25][26]
Harvest Moon Light of Hope Apps Latest Download For PC Windows Full Version. ABOUT USPcappsdownload.com is one of the best places on the Web to play new PC/Laptop games or apps for free!Just download apps for pc such as:Cmovies Apps,Fortcraft apps,Xhubs apps,aio downloader apps,repelisplus apps,mobdro apps,onhax apps,kissasian apps,fetlife apps,playview apps,dnvod apps,oklivetv apps.Download free apps online.Apps for PC free and safe download.Download the latest version apps apk games for PC.Download and play top free PC Games,Laptop Games,Desktop Games,Tablet Games.Also you can download free apks and apps for PC (Windows 7,8,10,XP,Vista).
![]()
Support for session shadowing was added back in RDP version 8.1. This version also fixes some visual glitches with Microsoft Office 2013 when running as a RemoteApp.[25]
Version 8.1 of the RDP also enables a 'restricted admin' mode. Logging into this mode only requires knowledge of the hashed password, rather than of its plaintext, therefore making a pass the hash attack possible.[27] Microsoft has released an 82-page document explaining how to mitigate this type of attack.[28]
Version 10.0[edit]
Version 10.0 of the RDP includes the following new features: AutoSize zoom (useful for HiDPI clients).[29]In addition graphics compression improvements were included utilizing H.264/AVC.[30]
Features[edit]
Microsoft introduced the following features with the release of RDP 6.0 in 2006:
Release 7.1 of RDP in 2010 introduced the following feature:
Security issues[edit]
Version 5.2 of the RDP in its default configuration is vulnerable to a man-in-the-middle attack. Administrators can enable transport layer encryption to mitigate this risk.[33][34]
RDP sessions are also susceptible to in-memory credential harvesting, which can be used to launch pass the hash attacks.[citation needed]
In March 2012, Microsoft released an update for a critical security vulnerability in the RDP. The vulnerability allowed a Windows computer to be compromised by unauthenticated clients and computer worms.[35]
RDP client version 6.1 can be used to reveal the names and pictures of all users on the RDP Server (no matter which Windows version) in order to pick one, if no username is specified for the RDP connection.[citation needed]
In March 2018 Microsoft released a patch for CVE-2018-0886, a remote code execution vulnerability in CredSSP, which is a Security Support Provider involved in the Microsoft Remote Desktop and Windows Remote Management, discovered by Preempt.[36][37]
Non-Microsoft implementations[edit]
There are numerous non-Microsoft implementations of RDP clients and servers that implement subsets of the Microsoft functionality. For instance, the open-source command-line client rdesktop is available for Linux/Unix and Microsoft Windows operating systems. There are many GUI clients, like tsclient and KRDC, that are built on top of rdesktop; CoRD is such a client for the Macintosh.
In 2009, rdesktop was forked as FreeRDP, a new project aiming at modularizing the code, addressing various issues, and implementing new features.[38] FreeRDP comes with its own command-line-client xfreerdp, which supports Seamless Windows in RDP6. There’s also a GTK-Application named Remmina.
An open-source implementation of a Remote Desktop Protocol server on Unix is FreeRDP and xrdp. The Windows' Remote Desktop Connection client can be used to connect to a server. Proprietary RDP client solutions such as rdpclient are available as a stand-alone application or embedded with client hardware.
A new access paradigm, browser-based access, has enabled users to access Windows desktops and applications on any RDP hosts, such as Microsoft Remote Desktop (RDS) Session Hosts (Terminal Services) and virtual desktops, as well as remote physical PCs.
There is also a so-called VRDP used in the VirtualBox virtual machine implementation by Oracle. This protocol is compatible with all RDP clients, such as that provided with Windows but, unlike the original RDP, can be configured to accept unencrypted and password unprotected connections, which may be useful in secure and trusted networks, such as home or office LANs. By default, Microsoft's RDP server refuses connections to user accounts with empty passwords (but this can be changed with the Group Policy Editor[39]). External and guest authorization options are provided by VRDP as well. It does not matter which operating system is installed as a guest because VRDP is implemented on the virtual machine (host) level, not in the guest system. The proprietary VirtualBox Extension Pack is required.
Patents[edit]
Microsoft requires third-party implementations to license the relevant RDP patents.[40] As of February 2014, the extent to which open-source clients meet this requirement remains unknown.
The story of the game is that when the prince away from war his vazir imprisoned the Princess and order her to marry him or choose death. You can also check another Prince of Persia game from here Prince of Persia Classic Game Download For PC ScreenshotsHow To Download Prince of Persia Classic Game For PCThis is a torrent game contains download link, so you need a Torrent software to download this game, use Bit Torrent because it is the best software to get Torrent files at any time you want. Prince of persia classic game free download. Then your mission is that you have only 60 minutes to save the princess from vazir. I am also a game lover and always taste new games but never play with this type of interesting story, I think its amazing and more entertainable. How To Install This Game?The Installation of this game is very easy.
Use in cybercrime[edit]
Security researchers have reported that cybercriminals are selling compromised RDP servers on underground forums as well as specialized illicit RDP shops.[41][42] These compromised RDPs may be used as a 'staging ground' for conducting other types of fraud or to access sensitive personal or corporate data.[43] Researchers further report instances of cybercriminals using RDPs to directly drop malware on computers.[44]
See also[edit]![]()
References[edit]
Increase Number Of Rdp Sessions Server 2012External links[edit]
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Remote_Desktop_Protocol&oldid=904603979'
We are using remote desktop to log in to a Windows 2012 server with a limit for two simultaneously users only. Sometimes, however, we need to be more.
We've discussed that with our server guys who claimed that this is only possible if the server will be reinstalled. Somehow I find this hard to believe, but being a novice I have no arguments to come with.
So - is it true or false? Is there any configuration in the server I could to check to confirm that this is the case? Please help a noob mixed up in a bureaucracy.
uzilanuzilan
6 Answers
To allow more remote users on your MS Windows server you need to install the terminal services role. Microsoft calls those Remote Desktop Services since MS Windows Server 2008. This does not require reinstallation but probably one or more restarts.
You need client access licenses and a license manager to use this feature. The following links will give you more insight:
bjanssenbjanssen
It doesn't require reinstallation, it requires the installation of a the remote desktop services role and the purchase of licenses to enable additional RDP connections. Why do you need so many RDP connections, is this just to manage Microsoft services on the server? Management tools can be installed on client computers to manage many of Microsoft's products remotely, without having to RDP in. It's called RSAT: http://www.microsoft.com/en-gb/download/details.aspx?id=28972
Alex BerryAlex Berry
Windows Key + R >> Type MMC.exe >> then Control + M >> Select Group Policy Object >> then Add >> then finish >> then OK
Double click on Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.Limit Number of Connections = 999999.Restrict Remote Desktop Services users to a single Remote Desktop Services session = DISABLED.
Anthony StarlingAnthony Starling
An alternative I haven't seen covered here so far: on your local desktop (assuming it's Windows) open Start then Run and type mstsc /admin
This will launch the remote desktop client in admin mode. You may need to enter elevated credentials to use it, but it will override the two user limit. It makes sense to do this instead of making configuration changes if you only occasionally need to have more than two people logged in.
KateKate
'It is recommended that you install Remote Desktop Session Host before you install any applications that you want to make available to users.If you install RD Session Host on a computer that already has applications installed, som of the existing applications may not work correctly in a multiple user environment.'
This is the text you get presented with when adding the RD Session host role on a server.So Microsoft is clearly advising against doing it after applications have been installed.
I have also tried this on servers in the past and have run into all sorts of strange issues.Specially finance applications seems to break if added before RD Session Host.
The GPO hack suggested is a clear violation of Microsofts TS licensing and should never be used!
I would say, ALWAYS use MS best practice. Then you know you get their support if needed in the future, especially in a production environment!
MrVistaMrVista
Strictly from a server perspective and enabling more than two users, no it does not require reinstalling the server operating system.
If there are applications installed that would function differently on an application terminal server/change user install, then the applications may need to be uninstalled/reinstalled.
Greg Askew
Windows Server Multiple Rdp SessionsGreg Askew
29.5k33 gold badges3838 silver badges7070 bronze badges
Not the answer you're looking for? Browse other questions tagged windows-server-2012remote-desktop or ask your own question.Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |