Talk:Remote Desktop Services

message: 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!--213.244.127.2 14:35, 28 Apr 2005 (UTC)
replies: text: "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)
thread_title: Article focus

message: Should the command line for Remote Desktop (mstsc) and/or the usage of the program be mentioned somewhere? --AySz88^-^ 15:25, 11 December 2005 (UTC)
thread_title: Usage?

message: 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)
thread_title: External Link

message: The port needed to be open to enable Remote Desktop is port 3389 TCP.  --Geopgeop 01:32, 7 June 2006 (UTC)
thread_title:  Port number 

message: 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)
replies: text: 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)
thread_title:  Windows 2003 server as TS Gateway 

message: 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)
thread_title:  Types of network 

message: Is there anyone who can add to this article, commenting on the security concerns? WDavis1911 (talk) 18:40, 10 July 2008 (UTC)
replies: text: Full access to the computer, basically. Same as any other RAT.  —Preceding unsigned comment added by 67.53.37.221 (talk) 07:52, 22 March 2009 (UTC)
thread_title: Security Concerns

message: 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)
thread_title:  Remote desktop availability on different versions. 

message: Shouldn't there be some discussion of the licensing modes on the server? --DanielRigal (talk) 09:03, 14 July 2009 (UTC)
replies: text: probably--SimonBramfitt (talk) 01:10, 16 January 2013 (UTC)
thread_title:  licensing  

message: 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).
I'm not sure where the confusion crept in: MS documentation always reports any new feature of an old service as if it were entirely ex-nova.203.206.162.148 (talk) 08:50, 22 November 2010 (UTC)
thread_title:  RemoteApp - Terminal Services - Not Just 6.1 

message: "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)
replies: text: 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)
thread_title:  Chrome? 

message: 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)
thread_title:  TS Gateway on other platforms 

message: 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)
thread_title:  No Citrix? 

message: 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?"
--SimonBramfitt (talk) 01:04, 16 January 2013 (UTC)
thread_title:  Terminal Services - Remote Desktop Services - Remote Desktop Session Host 

message: 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 203.206.162.148 (talk) 05:54, 4 March 2014 (UTC)
replies: text: 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)
replies: text: "XP Mode" is the same thing as "Remote APP". Only not Remote. Same technology. Same software. Same bugs, same patches. Same problems, same fixes.  — Preceding unsigned comment added by 203.206.162.148 (talk) 06:29, 14 March 2014 (UTC)
thread_title:  Virtual PC /XP Mode 

message: 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.
(If one already exists, I wouldn't mind you pointing my nose to it.) --Alien4 (talk) 09:09, 8 May 2014 (UTC)
thread_title:  *IT platform technology* 

message: 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)
replies: text: Klbrain (talk) 12:02, 16 December 2023 (UTC)
thread_title:  Suggest merging [[Network Level Authentication]] into this article