SHARE - Connecting to a shared environment¶
Active sessions are displayed in SHARE as follows:
This provides the RDP connection information:
- the address of the server that hosts the shared environment,
- the port where the RDP server dedicated to this environment is listening.
Moreover, the user can abort the active session. By default, SHARE sessions are stateless. All changes on the hard disk of the remote environment are flushed after each session.
Remark: see version issues.
Standard use of a Windows RDP client¶
A SHARE user can copy the RDP information to for example the Windows RDP client:
For some RDP clients (also see version issues), you then need to click "yes" on the following menu:
Remark that the size of the remote terminal window can be adjusted. In several cases, this synchronizes automatically with the screen resolution of the remote environment. Usually, you can simply maximize the RDP window to full-screen and the remote session will then work in full-screen mode. If this is not the case, a user can adjust that resolution manually using the facilities of the remote operating system (tutorial windows, Linux provides similar facilities).
RDP detail: platform independence¶
SHARE is not restricted to a particular operating system (neither on the side user of the system, nor on the side of the demonstrated environments). Moreover, users can use more than one remote environment at the same time. The following screenshot for example illustrates how a Linux user is using the rdesktop client to work on three remote environments at the same time:
- the window on the lower left corner of the screenshot displays a remote Windows session with the GrGen.NET graph transformation tool,
- the window stacked on top of that displays a remote session based on the DSL OS and demonstrates the AGG tool,
- finally, the next window (displayed on the upper left corner of the screenshot) displays a remote session based on the Ubuntu OS and demonstrates the MagicDraw UML tool in the context of the MoTMoT graph transformation approach.
RDP Client: Version Issues¶
- Macintosh users should use MS Remote Desktop Connection Client 1.0.3 for Mac whereas * Windows users should use MS RDP Client v5.2
- Windows users sometimes need to indicate explicitly some details concerning the authentication mechanism. The following screenshot displays how the right-most tab from the Windows XP RDP client should be configured (it used attempt authentication but anything besides no authentication will work):
- For some Windows RDP clients you also need to enable the option "allow me to save credential" when using the client for the first time.