Terminal/remote access to a computer?

igolovin2011-02-09 09:56:30

Remote access

igolovin, 2011-02-09 09:56:30

I will try to formulate the question as precisely as possible. There is a computer with XP. Very rare and expensive software is installed on it. In a single copy, of course. It was decided to protect the computer from the maximum number of influences, put the system unit in a safe (well, or something like a safe). Now we need to make it so that users can work with it, but at the same time they cannot make any changes to the system, they cannot delete anything. Roughly speaking, read-only rights.
Can anyone suggest the best way to organize this?

Answer the question

In order to leave comments, you need to log in

9 answer(s)

lhav, 2011-02-09
@lhav

It is better to put Server 2008 there, and organize work with the program through RemoteApp.

Skunk, 2011-02-09
@Skunk

Put vncserver on the computer in a safe, to which you can set all the necessary settings. There are many such programs.
Let's say:
UltraVNC: www.uvnc.com/

olololog, 2011-02-09
@olololog

Look towards steadystate from finely soft. It allows you to freeze the contents of partitions by caching changes in RAM. After the reboot, the changes are rolled back, and the config is saved on another partition.

Alexander Baumgertner, 2011-02-09
@alexbaum

If it is important to leave XP and some license violation is not scary, you can use the modified termserv.dll sig9.com/articles/concurrent-remote-desktop

mikes, 2011-02-09
@mikes

perhaps a simple backup is enough ... buy yourself a thread from acronis and you will be happy.
but to make it so that the user does not have write permissions and at the same time ensure normal operation ... this is nonsense, however.

RuJet, 2011-02-09
@RuJet

The easiest option is to give Guest rights.
But it won't solve all problems.
If everything is really that expensive and important there are hardware solutions.

Anastasia_K, 2011-02-09
@Anastasia_K

Try creating a user with a limited account on the server and configure NTFS rights so that all files related to your program have this user read-only rights. Do not forget about the rights to the corresponding branches of the registry. As far as I remember, on Windows XP, the standard regedit does not allow changing permissions, so use regedt32. This solution will work for any connection method (radmin, RDP, VNC), provided that the user logs in with his account.

Odinokij_Kot, 2011-02-11
@Odinokij_Kot

radmin + special driver from melkosoft to disable writing to disk after the system is configured.
As a result, a simple reboot of the machine brings it back to its original state.
www.flashboot.ru/News-article-25.html

omnimod, 2011-02-11
@omnimod

In Windows XP, Windows Vista and Windows 7, it is possible to publish a separate application (similar to seamless mode or remoteapp), the so-called. RemoteApp for Hyper-V (although it is indirectly related to Hyper-V). You can use software restriction policy to enforce restrictions on running programs.
Of the limitations of this solution - no more than one remote connection.