You need to (once only):
The office PC needs to be set up for RDP service: set to accept
connections for your login. This setup needs to be done as an
administrator: with your admin login if self-managed, or
ask Paul to do for you.
Reminder for Paul: log in as network admin pszwt, not as local admin.
The "standard" ssh client for Windows is putty, use latest
version from
http://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
To use putty, with WindowsExplorer (e.g. MyComputer) find putty.exe, double-click.
Run putty: with WindowsExplorer (e.g. MyComputer) find putty.exe, double-click. Set options as above, or Load your saved session settings, and click Open.
Follow the prompts: type your normal enna login name to login as, then when prompted type the words from your paper skey sheet for the line number shown, or the authenticator code, then your normal enna password. You will be logged in to enna.
The very first time you connect, you will be prompted about the as-yet unknown authenticity fingerprint: say yes.
Leave that enna window logged in, running; you may minimize/iconize its window. Keep that session running, do not allow to time out, do not allow your computer to go to sleep/hibernate e.g. as most laptops do with the lid closed.
Start the Remote Desktop Connection client: go to StartMenu and search for that, click it.
In the Remote Desktop Connection client:
When you connect, you may need to wait 30 seconds for the "normal" (local screen) user to be logged out; or if that other user is you, then you will see the desktop (open windows etc) as you left it.
When done, you can just disconnect; but you will still be logged on. Probably you should log out: click the StartMenu and choose LogOff. (Do not use Alt-Ctrl-Del as that does things on the laptop, not the RDP connection.)
After disconnecting your RDP session, you may close the putty window (log out the enna session): type exit at the enna prompt, or just close the window (click the top-right [X]).
This should not affect Maths Win7 PCs, but would probably affect most
other RDP services, including to MCS Win10 PCs.
(There may be settings to lengthen or remove RDP session timeout...
but they may be inaccessible.)
Setup
Within your RDP session (so with a browser running within the RDP
machine), go to the webpages
www.maths.usyd.edu.au/u/psz/pc/keepalive.bat
www.maths.usyd.edu.au/u/psz/pc/keepalivehelper.js
and save each on your Desktop (on the RDP machine), with their
"original" names (keepalive.bat and keepalivehelper.js).
To use
When logged into RDP, run the keepalive.bat command: double-click
keepalive on your Desktop.
There is no visible effect of having run that command. It works in the background, clicking and un-clicking the ScrollLock key every 5 minutes, so there is activity and no timeout.
Windows machines may (at some later time?) develop an error, with the RDP client showing
Your computer could no connect to another console session on the remote computer because you already have a console session in progress.If so, use 3391 instead of 3390 in both the putty settings (add that, can leave 3390 in place), and in typing localhost:3391 to the RDP client.
The remote "laptop" machine could be Linux or Mac: there are RDP clients for Linux (xfreerdp) and Mac (Microsoft Remote Desktop 10), and of course they have SSH; but we will not describe how to use such other machines.
Similar connection could be achieved with VNC. VNC would work for any
office machines not just Windows PCs, and there are many free VNC
software packages available. However that would need extra software on
both the office PC and the laptop, and would not provide file copy.
Apple Screen Sharing is based on
VNC
and is recommended for Macs.
Paul Szabo psz@maths.usyd.edu.au 14 Dec 23