|This article is of interest to the following WikiProjects:|
Terminal services is not only for MS windows , although MS-windows 2000 and 2003 provide this service , but its not limited to them , the Terminals concept is much older (probebly since the 1970s), and the service as a service is aslo available on systems like linux (look at www.ltsp.org for instance ) , and the concept of having the output of a some job displayed and interacted with is used on Unix systems for years , ie rsh and telnet , and the architecture of X server is desighned to be able to communicate with remote processes over the net easily!--22.214.171.124 14:35, 28 Apr 2005 (UTC)
I agree with above comment regarding the term "Terminal Services" being a bit too generic to assume that it is a Microsoft-only concept. It should be adapted to encompass the other terminal services (such as *nix), especially since the technology has been around much longer than MS terminal services. —Preceding unsigned comment added by 126.96.36.199 (talk) 20:29, 9 October 2008 (UTC)
- "Termninal Services" is a Microsoft product. If you want to talk about computer terminals as a concept then there are a variety of articles, please see terminal for a list. AlistairMcMillan (talk) 00:13, 10 October 2008 (UTC)
The Citrix connection is a little stronger than noted here. (a) The technology was licensed by MSoft from Citrix in ???? - they'd been working on this way back in the OS/s days, and (b) Citrix's products sit on top of Microsoft's TS Snori 01:32, 11 November 2005 (UTC).
Hi, I have already read all the rules and regulations regarding External linking on Wikipedia. This is why I would now like to put this forth for discussion here. I am the content manager for TechGenix Ltd. Previously there were two links added to the external links on this page directing to here and here. Since we have now started a web site which is dedicated completely to just Terminal Services and Citrix I decided to remove the two links to the separate articles and to just put the one link to our new webiste which is: MSTerminalServices.org. The site is completely free, there is no registration required and so on. However I realize that we are not linking directly to content but to a site, however is not the entire site made up of content related to the article in question? I would also like to point out that two of our websites have been added to the External Links section of Exchange Server and ISA Server. These links were added by a third party, ie not myself or anyone who works with TechGenix. Therefore I thought that adding the Terminal Services website would be OK. So what I would basically like to know is if it would be allowable to include the one external link to our web site. If this is not allowable I would like to have the previous two links re-added to the articles. I look forward to the discussion. Thanks --MikeVella 09:51, 3 May 2006 (UTC)
The port needed to be open to enable Remote Desktop is port 3389 TCP. --Geopgeop 01:32, 7 June 2006 (UTC)
The generic term for remote desktop services in OS such as XP, OS X, and Linux
Since Windows XP, Mac OS X, and Linux all support "remote desktops", is their a general name for this type of service or does it not have an official general name? I am looking to start an article the concept in general that would link to the particular implementations in XP, OS X, and Linux. --Cab88 15:50, 8 July 2006 (UTC)
- We already have such an article: Remote Desktop. -/- Warren 15:59, 8 July 2006 (UTC)
- That is just a disambiguation page, not a true article. If the term "remote desktop" is a suitable catchall term for this type of service then the page at Remote desktop, which redirects to Remote Desktop (a disambiguation page) should be rewritten into a article on the subject. We can leave the disambiguation page for those looking for Microsoft's and Apple's implementations of remote desktop services. --Cab88 09:27, 10 July 2006 (UTC)
- I think the term "Terminal Services" is a generic term. The opening paragraph should make some mention that the concept is not limited to the MS products only. With the concept of "Terminal Services" there are other concepts that fulfill various roles, e.g. the Terminal Server (Windows TSE, Sun Ray, X, VNC, etc), the Terminal Services Client (rdesktop, vncviewer, X terminals, Sun Rays, dedicated multi-protocol thin clients), the Terminal Services Protocol (RDP, RFB Protocol, ALP, X). I'm willing to make some edits, but would like some opinions first.
Windows 2003 server as TS Gateway
I'm pretty sure Windows 2003 server will NOT support the TS Gateway server. If anyone can find a source that refutes that, please state it now. Otherwise, I'll remove it in a few days. Z4ce 04:14, 16 October 2007 (UTC)
- I am not sure about the regular Server 2K3 editions. But Windows Home Server, which is based off Windows Server 2003, DOES act as TS Gateway Server. --soum talk 08:32, 16 October 2007 (UTC)
Types of network
From the opening paragraph:
- Terminal Services is one of the components of Microsoft Windows (both server and client versions) that allows a user to access applications and data on a remote computer over any type of network, although normally best used when dealing with either a Wide Area Network (WAN) or Local Area Network (LAN), as ease and compatibility with other types of networks may differ.
This is pure nonsense. What other types of network are there? MANs? Why would Terminal Services be any less suited to those than to LANs and WANs? There may be issues with specific technologies or network protocols but that is a different issue entirely. As such I've snipped out the second portion of that sentence. CrispMuncher (talk) 13:06, 8 July 2008 (UTC)
- Full access to the computer, basically. Same as any other RAT. —Preceding unsigned comment added by 188.8.131.52 (talk) 07:52, 22 March 2009 (UTC)
There is a Microsoft article (http://technet.microsoft.com/en-us/library/cc782610%28v=ws.10%29.aspx) talking about how the security is implemented and configured when Terminal Service(or RDP) is through TLS. The process of configuring this is fairly straightfoward. And I can see that the RDP is as secure as TLS (or SSL) if TLS is used for hand-shaking and communication encryption. However I sm still not clear about how secure communication is achieved if TLS is not used, perhaps in a way similar to NTLM. —Preceding unsigned comment added by 184.108.40.206 (talk) 18:01, 12 March 2011 (UTC)
Remote desktop availability on different versions.
I've reworked the section enumerating which Windows editions remote desktop is available on since it was inaccurate and incomplete, however a full listing is unwieldy so I have not included it in the main article in favour of a summary. From the research I have done the complete listing is: Windows NT 4.0 Terminal Server; Windows 2000 Server, Advanced Server and Datacenter Server; Windows XP Professional and Media Center Edition; Windows Server 2003 Standard, Enterprise and Datacenter; Windows Vista Business, Enterprise and Ultimate; and Windows Server 2008. CrispMuncher (talk) 17:58, 5 September 2008 (UTC)
RemoteApp - Terminal Services - Not Just 6.1
At present, the article says that
"RemoteApp (or TS RemoteApp) is a special mode .., available only in ... 6.1 ...2008 ..., where a remote session connects to a specific application only..."
All versions of Terminal Services can connect to a "specific application only" on all versions of Windows Server. You can do that connecting from Win2K to Win2K server. The new feature is automatic integration into the Windows 7 start menu. Integration into the Windows Start Menu only works on Windows 7, where it is also used for "XP Mode".
Before Windows 7, you had to create an MSI to "install" a shortcut into the start menu if you wanted to deploy a shortcut in the user start menu pointing to an application running as a RemoteApp (no remote desktop, just a remote application).
As noted here: http://technet.microsoft.com/en-us/library/cc759024%28WS.10%29.aspx, use Terminal Services extension (in AD) to "Specify a program to run when a user logs on." 220.127.116.11 (talk)
"With version 6.0, if the Desktop Experience component is plugged into the remote server, the chrome of the applications will resemble the local applications, rather than the remote one." Could someone who knows, write the sentence so that you can understand it without knowing what chrome is? (especially as the wiki link for it doesn't work user interface chrome) Talltim (talk) 15:40, 22 March 2011 (UTC)
- Agreed, I can't see that many people understanding what is meant by chrome here - I'll fix --SimonBramfitt (talk) 17:46, 15 January 2013 (UTC)
TS Gateway on other platforms
I'm on the iTap mobile team and we do support TS Gateway for other platforms including Mac, Linux, iOS and Android. What's the best way to correct the information in the article? Phoneder (talk) 06:15, 28 July 2011 (UTC)
We should probably be also referenced in wikipedia as our client for iOS was the leading RDP client (in sales) for most of the time during the last 1.5 years. E.g. the article Comparison_of_remote_desktop_software includes RDP clients with far less user base than ours and also far less platform importance. What's the best way to change this? Phoneder (talk) 06:15, 28 July 2011 (UTC)
Usage on server Core version
I'm personally chasing a confirmation if this role can be used on a Windows 2008 Core /2008 R2 Core. When I have it, I believe it would be an useful information to mention on the page.
Given the role that Citrix had in developing the core technology behind RDS and subsequently licensing it to Microsoft for inclusion in Win NT 4, I'm surprised that it does not get a mention--SimonBramfitt (talk) 17:42, 15 January 2013 (UTC)
Terminal Services - Remote Desktop Services - Remote Desktop Session Host
the introduction to this article included a link to terminal server when it was clearly meant to be "Terminal Services". There is no article for Terminal Services, only a redirect back to this article.
This begs the broader question "Is this, or perhaps should this be, an article about Terminal Services, Remote Desktop Services, or Remote Desktop Session Host?"
Virtual PC /XP Mode
Windows 7 "XP mode" is a RDC connection to a Virtual PC. It's basically the same as Remote App, but using a local Virtual PC running WinXP, instead of using a remote server. — Preceding unsigned comment added by 18.104.22.168 (talk) 05:54, 4 March 2014 (UTC)
- No, it isn't. It is a Windows XP, plus a license to use it, plus a virtual machine, plus a hypervisor, plus an installer and startup wizard. Its integration mode sometimes uses an RDP (not RDC) over TCP/IP but that's the extent of it. Best regards, Codename Lisa (talk) 04:46, 5 March 2014 (UTC)
*IT platform technology*
Personally I wouldn't mind an article about *IT platform technology* (or something like this), where all that fuss would be sorted out: fat client, thin client, app streaming, desktop streaming, app-v, vdi, xen[...], terminal server, citrix, terminal services, rds, cloud, only maybe hypervisor, etc. etc.
Browse for Terminal Servers, from Win7
Remote Desktop Services (RDS), known as Terminal Services in Windows Server 2008 and earlier is one of the components of Microsoft Windows. Earlier versions of this component, on Windows (XP and 2000) included the functionality to allow "browsing" to identify RDS servers. Later versions (Win 7) did not. I suggest that a discusion of this change, or of this functionality would be a valuable addition to this article.
Note: As per the Wikipedia Talk Page Guidelines, this is a suggestion for a change to the associated article. I believe that such suggestions are within the scope of the Wikipedia Talk Page Guidelines.
The Network Level Authentication topic doesn't really seem like an independently notable or broad enough topic for its own article. I think it would make more sense as a section of this article. --Chris | Crazycomputers (talk) 14:57, 4 March 2023 (UTC)