Difference between revisions of "ReactOS Terminal Services"

From ReactOS Wiki
Jump to: navigation, search
m (Features)
(Microsoft RDP Specification: add PDF about MS-TSSO)
 
(37 intermediate revisions by 11 users not shown)
Line 1: Line 1:
 
ReactOS Win32 personality a fully featured multi user operating system with possibilities to log in several users at the same time with an insulated environment for every login. Every login should be able to access the terminal services from any interface with many different protocolls enabling different possibilities depending on protocol, interface and connecton speed.
 
ReactOS Win32 personality a fully featured multi user operating system with possibilities to log in several users at the same time with an insulated environment for every login. Every login should be able to access the terminal services from any interface with many different protocolls enabling different possibilities depending on protocol, interface and connecton speed.
  
== Features ==
+
== Possible Features ==
  
 
* Multi user environment.
 
* Multi user environment.
* Possibility to log on remotely or locally via any interface.
+
* Possibility to log on remotely or locally via any interface (Serial, Parallell, USB, Firewire, Modem(Analog, Digital), Network).
* Possibility to log in several times from the same terminal.
+
* Possibility to log in several times from the same terminal + some type of fast switching like XP.
 
* Possibility to use two or more sets of keyboard, mouse and screen (Human Interface Device/HID) and associate a login to a certain set of HIDs.
 
* Possibility to use two or more sets of keyboard, mouse and screen (Human Interface Device/HID) and associate a login to a certain set of HIDs.
 +
* Possibility to split screen (Horizontal or Vertical) and use two sets of HID one associated to each split section (for computers connected to TV-set).
 
* Possibility to use RDP, Citrix, X-Windows client, Telnet or VNC as protocol/client.
 
* Possibility to use RDP, Citrix, X-Windows client, Telnet or VNC as protocol/client.
* Possibility to give every login an insulated environment much like vmware.<br/>
+
* Possibility to give every login an insulated environment much like vmware.
: "Undo-Disks" -> ROS doesn't write do the real harddisk (in German this is called "Datenairbag")
+
: "Undo-Disks" -> ROS doesn't write do the real harddisk; Snapshot (in German this is called "Datenairbag")  
* Possibility to let a session log in to an emulation environment like [http://fabrice.bellard.free.fr/qemu/ QEmu], [http://www.classicgaming.com/mame32/ MAME]or [http://www.viceteam.org/ VICE] to run other Operating System then the Terminal Server or software not compiled for the CPU
+
* Possibility to let a session log in directly to an emulation environment like [http://fabrice.bellard.free.fr/qemu/ QEmu], [http://mamedev.org/ MAME] or [http://www.viceteam.org/ VICE]# to run other Operating System then the Terminal Server or software not compiled for the CPU.
 
* Easy management with possibility to take over, see and redirect a session directly from login screen.
 
* Easy management with possibility to take over, see and redirect a session directly from login screen.
 +
 +
== Tasks need to be done ==
 +
* Multi User Environment
 +
** Shared Session Memory Space
 +
** Winlogon+GINA
 +
** SAS: make win32k notify Winlogon
 +
** smss: move Kmode loading to csrss
 +
** csrss: make it support multiple Win sessions
 +
** logon/logoff procedures
 +
* Win32k stuff (video / keyboard / mouse)
 +
** One focus for every mouse & keyboard cursor
 +
** Multi Display Adapters and Display support
 +
*** Multiple Hardware Displays
 +
*** SplitScreen support for two sessions at the same Screen
 +
*** Multiple Virtual Display Drivers that can be associated to a login
 +
*** TSDDD Framebuffer Display Driver
 +
* Creating support for different protocolls and inserting the different project into ROS
 +
** UltraVNC
 +
** Telnet server daemon
 +
** xrdp project - simple RDP server
 +
 +
== Thoughts for hardware ==
 +
* If system revolves around VNC
 +
** Cheap dedicated hardware possible to build - cost of £20 possibly for a dedicated kit built VNC client
 +
 +
== Thoughts about VNC ==
 +
* Extend VNC protocol to allow access to local client's drives
 +
* Extend VNC protocol for print files to be sent across in standard format (possibly Postscript?), then at client converted to printer-specific format, to allow printing to client's preferred local printer
 +
* Possible addition of audio support to VNC?
 +
* Possible extention to VNC to allow it to operate through Proxy servers with Java/executable clients
 +
* ReactOS can detect "broken" sessions due to network disconnection, and retain session for client to reconnect from another computer/when network begins working again.
 +
* VNC is built into display Kernel of React, so all video messages are captured and quickly and efficiently sent across internet, reducing lag and server overhead.
 +
 +
Advantage being with VNC over X11 based systems, clients are readily available (down to Java), saving on coding. Protocol is fairly efficient and fast, and allows clients to use ReactOS based servers without installing software locally - locally installed software may not be allowed by client's computer administration policy.
  
 
== Links ==
 
== Links ==
 
* [http://www.microsoft.com/windowsserver2003/technologies/terminalservices/default.mspx Windows Terminal Services]
 
* [http://www.microsoft.com/windowsserver2003/technologies/terminalservices/default.mspx Windows Terminal Services]
  
* [http://sourceforge.net/projects/xrdp A simple RDP server for Linux and Windows]
+
* [http://sourceforge.net/projects/xrdp XRDP - A simple open source RDP server for Linux and Windows]
 +
 
 +
* [http://xrdp.sourceforge.net/ The homepage for XRDP with files released]
 +
 
 +
* [http://www.rdesktop.org/ rdesktop - A Remote Desktop Protocol Client]
 +
 
 +
* [http://www.atomice.com/blog/?page_id=9 The above Remote Desktop Client ported for windows]
  
* [http://www.rdesktop.org/ A Remote Desktop Protocol Client]
+
* [http://www.freerdp.com/ FreeRDP - A fork of the rdesktop project - with active development]
  
 
* [http://www.citrix.com/ Citrix (they made the first Windows Terminal Server)]
 
* [http://www.citrix.com/ Citrix (they made the first Windows Terminal Server)]
 +
 +
* [https://redcircle.blog/2006/10/15/citrix-and-microsoft-1989-1998/ Citrix and Microsoft (1989-1998)]
  
 
* [http://ultravnc.sourceforge.net/ UltraVNC Project]
 
* [http://ultravnc.sourceforge.net/ UltraVNC Project]
Line 30: Line 73:
 
* [http://telnetd.sourceforge.net/ Telnet Daemon]
 
* [http://telnetd.sourceforge.net/ Telnet Daemon]
  
== Tasks need to be done ==
+
* [http://www.pgina.org pgina (a GPL GINA)]
* Multi User Environment
+
 
** Winlogon+GINA
+
* [http://x.cygwin.com/ Cygwin X-Server]
** SAS: make win32k notify Winlogon
+
 
** smss: move Kmode loading to csrss
+
* [http://www.2x.com/ 2X Application Server for Linux (Free GPL)]
** csrss: make it support multiple Win sessions
+
 
** logon/logoff procedures
+
* [http://support.microsoft.com/kb/186572/en-us/ Microsoft Windows Terminal Server Walkthrough: Startup, Connection, and Application]
* Multi HID; key and mouse cursor
+
 
** Mouse drivers needs to support multi cursors
+
* [http://msdn.microsoft.com/en-us/library/ms811523.aspx Optimizing Applications for Microsoft Windows 2000 Terminal Services and Windows NT Server 4.0, Terminal Server Edition]
** Keyboard drivers needs to support multi cursors
+
 
** USB driver support to enable more then one set of HID
+
* [http://msdn.microsoft.com/en-us/library/dd644643(v=PROT.10).aspx Microsoft Windows Terminal Services System Overview]
* Multi Display Adapters and Display support
+
 
** Multiple Hardware Displays
+
* [http://support.microsoft.com/kb/186607/en-us/ Understanding the Remote Desktop Protocol (RDP)]
** Multiple Virtual Displays
+
 
* Creating support for different protocolls and inserting the different project into ROS
+
* [http://efod.se/media/thesis.pdf Reverse-Engineering and Implementation of the RDP 5 Protocol by Erik Forsberg, Linköpings universitet]
** UltraVNC
+
 
** Telnet server daemon
+
== Microsoft RDP Specification ==
** xrdp project - simple RDP server
+
 
** X-Server for ReactOS
+
* [http://www.itu.int/rec/T-REC-T.125-199802-I/en &#x5B;T.125&#x5D;: Multipoint communication service protocol specification]
 +
 
 +
* [http://www.itu.int/rec/T-REC-X.224-199511-I/en/ &#x5B;X.224&#x5D;: Information technology - Open Systems Interconnection - Protocol for providing the connection-mode transport service]
 +
 
 +
* [http://tools.ietf.org/html/rfc1006 &#x5B;RFC1006&#x5D;: ISO Transport Service on top of the TCP - Version: 3 (Updated-By RFC2126)]
 +
 
 +
* [http://tools.ietf.org/html/rfc2126 &#x5B;RFC2126&#x5D;: ISO Transport Service on top of TCP (ITOT)]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/dd644643(v=PROT.10).aspx &#x5B;MS-TSSO&#x5D;: Terminal Services System Overview]
 +
 
 +
* [https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/WinArchive/%5BMS-TSSO%5D.pdf &#x5B;MS-TSSO&#x5D;: Terminal Services System Overview (full PDF, archived)]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc248485(v=PROT.10).aspx  &#x5B;MS-TSGU&#x5D;: Terminal Services Gateway Server Protocol Specification]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc248570(v=PROT.10).aspx  &#x5B;MS-TSTS&#x5D;: Terminal Services Terminal Server Runtime Interface Protocol Specification]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/dd357079(v=PROT.10).aspx  &#x5B;MS-TSWP&#x5D;: Terminal Services Workspace Provisioning Protocol Specification]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc240445.aspx &#x5B;MS-RDPBCGR&#x5D;: Remote Desktop Protocol: Basic Connectivity and Graphics Remoting Specification]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc240933.aspx &#x5B;MS-RDPEA&#x5D;: Remote Desktop Protocol: Audio Output Virtual Channel Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc241066.aspx &#x5B;MS-RDPECLIP&#x5D;: Remote Desktop Protocol: Clipboard Virtual Channel Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc241215.aspx &#x5B;MS-RDPEDYC&#x5D;: Remote Desktop Protocol: Dynamic Channel Virtual Channel Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc241305.aspx &#x5B;MS-RDPEFS&#x5D;: Remote Desktop Protocol: File System Virtual Channel Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc241537.aspx &#x5B;MS-RDPEGDI&#x5D;: Remote Desktop Protocol: Graphics Device Interface (GDI) Acceleration Extensions]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc241880.aspx &#x5B;MS-RDPELE&#x5D;: Remote Desktop Protocol: Licensing Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc242017.aspx &#x5B;MS-RDPEMC&#x5D;: Remote Desktop Protocol: Multiparty Virtual Channel Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc242116.aspx &#x5B;MS-RDPEPC&#x5D;: Remote Desktop Protocol: Print Virtual Channel Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc242231.aspx &#x5B;MS-RDPEPNP&#x5D;: Remote Desktop Protocol: Plug and Play Devices Virtual Channel Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc242359.aspx &#x5B;MS-RDPEPS&#x5D;: Remote Desktop Protocol: Session Selection Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc242568.aspx &#x5B;MS-RDPERP&#x5D;: Remote Desktop Protocol: Remote Programs Virtual Channel Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc242596.aspx &#x5B;MS-RDPESC&#x5D;: Remote Desktop Protocol: Smart Card Virtual Channel Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/cc242856.aspx &#x5B;MS-RDPESP&#x5D;: Remote Desktop Protocol: Serial and Parallel Port Virtual Channel Extension]
 +
 
 +
* [http://msdn2.microsoft.com/en-us/library/cc242947.aspx &#x5B;MS-RDPEXPS&#x5D;: Remote Desktop Protocol: XML Paper Specification (XPS) Print Virtual Channel Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/dd302831(v=prot.10).aspx &#x5B;MS-RDPCR2&#x5D;: Remote Desktop Protocol: Composited Remoting V2 Specification]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/dd342521(v=prot.10).aspx &#x5B;MS-RDPEAI&#x5D;: Remote Desktop Protocol: Audio Input Redirection Virtual Channel Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/dd358323(v=prot.10).aspx &#x5B;MS-RDPEDC&#x5D;: Remote Desktop Protocol: Desktop Composition Virtual Channel Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/ff635589(v=prot.10).aspx &#x5B;MS-RDPEUSB&#x5D;: Remote Desktop Protocol: USB Devices Virtual Channel Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/dd342975(v=prot.10).aspx &#x5B;MS-RDPEV&#x5D;: Remote Desktop Protocol: Video Redirection Virtual Channel Extension]
 +
 
 +
* [http://msdn.microsoft.com/en-us/library/ff635378(v=prot.10).aspx &#x5B;MS-RDPNSC&#x5D;: Remote Desktop Protocol: NSCodec Extension]
  
== People who like to help ==
+
* [http://msdn.microsoft.com/en-us/library/ff635423(v=prot.10).aspx &#x5B;MS-RDPRFX&#x5D;: Remote Desktop Protocol: RemoteFX Codec Extension]
[http://reactos.com/wiki/index.php/Emanuele_Aliberti Emanuele Aliberti Developer of the multiuser CSRSS] [http://www.reactos.com/forum/profile.php?mode=viewprofile&u=39 Profile]
 
  
[http://www.reactos.com/forum/profile.php?mode=viewprofile&u=45 Jaix Bly visionary]
+
[[Category:Ideas]]

Latest revision as of 15:22, 14 November 2017

ReactOS Win32 personality a fully featured multi user operating system with possibilities to log in several users at the same time with an insulated environment for every login. Every login should be able to access the terminal services from any interface with many different protocolls enabling different possibilities depending on protocol, interface and connecton speed.

Possible Features

  • Multi user environment.
  • Possibility to log on remotely or locally via any interface (Serial, Parallell, USB, Firewire, Modem(Analog, Digital), Network).
  • Possibility to log in several times from the same terminal + some type of fast switching like XP.
  • Possibility to use two or more sets of keyboard, mouse and screen (Human Interface Device/HID) and associate a login to a certain set of HIDs.
  • Possibility to split screen (Horizontal or Vertical) and use two sets of HID one associated to each split section (for computers connected to TV-set).
  • Possibility to use RDP, Citrix, X-Windows client, Telnet or VNC as protocol/client.
  • Possibility to give every login an insulated environment much like vmware.
"Undo-Disks" -> ROS doesn't write do the real harddisk; Snapshot (in German this is called "Datenairbag")
  • Possibility to let a session log in directly to an emulation environment like QEmu, MAME or VICE# to run other Operating System then the Terminal Server or software not compiled for the CPU.
  • Easy management with possibility to take over, see and redirect a session directly from login screen.

Tasks need to be done

  • Multi User Environment
    • Shared Session Memory Space
    • Winlogon+GINA
    • SAS: make win32k notify Winlogon
    • smss: move Kmode loading to csrss
    • csrss: make it support multiple Win sessions
    • logon/logoff procedures
  • Win32k stuff (video / keyboard / mouse)
    • One focus for every mouse & keyboard cursor
    • Multi Display Adapters and Display support
      • Multiple Hardware Displays
      • SplitScreen support for two sessions at the same Screen
      • Multiple Virtual Display Drivers that can be associated to a login
      • TSDDD Framebuffer Display Driver
  • Creating support for different protocolls and inserting the different project into ROS
    • UltraVNC
    • Telnet server daemon
    • xrdp project - simple RDP server

Thoughts for hardware

  • If system revolves around VNC
    • Cheap dedicated hardware possible to build - cost of £20 possibly for a dedicated kit built VNC client

Thoughts about VNC

  • Extend VNC protocol to allow access to local client's drives
  • Extend VNC protocol for print files to be sent across in standard format (possibly Postscript?), then at client converted to printer-specific format, to allow printing to client's preferred local printer
  • Possible addition of audio support to VNC?
  • Possible extention to VNC to allow it to operate through Proxy servers with Java/executable clients
  • ReactOS can detect "broken" sessions due to network disconnection, and retain session for client to reconnect from another computer/when network begins working again.
  • VNC is built into display Kernel of React, so all video messages are captured and quickly and efficiently sent across internet, reducing lag and server overhead.

Advantage being with VNC over X11 based systems, clients are readily available (down to Java), saving on coding. Protocol is fairly efficient and fast, and allows clients to use ReactOS based servers without installing software locally - locally installed software may not be allowed by client's computer administration policy.

Links

Microsoft RDP Specification