Difference between revisions of "ReactOS Terminal Services"

From ReactOS Wiki
Jump to: navigation, search
(Microsoft RDP Specification: add PDF about MS-TSSO)
 
(One intermediate revision by the same user not shown)
Line 16: Line 16:
 
== Tasks need to be done ==
 
== Tasks need to be done ==
 
* Multi User Environment
 
* Multi User Environment
 +
** Shared Session Memory Space
 
** Winlogon+GINA
 
** Winlogon+GINA
 
** SAS: make win32k notify Winlogon
 
** SAS: make win32k notify Winlogon
Line 21: Line 22:
 
** csrss: make it support multiple Win sessions
 
** csrss: make it support multiple Win sessions
 
** logon/logoff procedures
 
** logon/logoff procedures
* One focus for every mouse & keyboard cursor.
+
* Win32k stuff (video / keyboard / mouse)
* Multi Display Adapters and Display support
+
** One focus for every mouse & keyboard cursor
** Multiple Hardware Displays
+
** Multi Display Adapters and Display support
** SplitScreen support for two sessions at the same Screen
+
*** Multiple Hardware Displays
** Multiple Virtual Display Drivers that can be associated to a login.
+
*** 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
 
* Creating support for different protocolls and inserting the different project into ROS
 
** UltraVNC
 
** UltraVNC
Line 59: Line 62:
  
 
* [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 95: Line 100:
  
 
* [http://msdn.microsoft.com/en-us/library/dd644643(v=PROT.10).aspx [MS-TSSO]: Terminal Services System Overview]
 
* [http://msdn.microsoft.com/en-us/library/dd644643(v=PROT.10).aspx [MS-TSSO]: Terminal Services System Overview]
 +
 +
* [https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/WinArchive/%5BMS-TSSO%5D.pdf [MS-TSSO]: Terminal Services System Overview (full PDF, archived)]
  
 
* [http://msdn.microsoft.com/en-us/library/cc248485(v=PROT.10).aspx  [MS-TSGU]: Terminal Services Gateway Server Protocol Specification]
 
* [http://msdn.microsoft.com/en-us/library/cc248485(v=PROT.10).aspx  [MS-TSGU]: Terminal Services Gateway Server Protocol Specification]

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