Hi Chris

Have a look at this thread ...
http://www.radmin.com/support/forum/read.php?FID=30&TID=13800

... I don't know if that change would be in the next release ... ?

Furthermore, I presume the second part of your question means the refusal of a Radmin connection if there is already a user logged on locally? If that's the case I doubt if Radmin will specifically take account of that.

That was kind of what I wa

Quote

Paul B wrote: As an afterthought, as far as local logons go there are probably a few workarounds you could employ. For example you could have policy-driven logon/logoff script which turn the Radmin Server service off/on respectively. This would stop Radmin access while a user was logged on and restore that capability when they logged off. That wouldn't solve all of your problems by any means, but it may help to form one part of a workable solution.

That's kind of where I was headed with my question.

Another one:

With the option to have the locally logged in user click a prompt to accept an incoming connection turned on, what happens if nobody is logged into the machine to accept the incoming connection?

Paul, the problem with your idea of a logon/logoff script would be that RAdmin gives you control of the console session. This means you still would have to log into the console (assuming you're connecting for Full Control) after connecting with RAdmin, whereupon the logon script would terminate your RAdmin connection!

A better (and simpler) solution might be to configure RAdmin to use Windows Security, and assign permissions to user accounts that have rights locally on the workstation, so that only users who can sit down at that workstation and log on have permission to log on via RAdmin. (You could lock it down further as needed.)

This wouldn't address the possibility of denying an RAdmin connection when someone is already logged on, though. To do that, you could possibly do something fancy with a logon script, where the logon script altered the RAdmin server settings (via a registry patch, probably) to require the local user's permission for incoming connections and deny after the timeout. Then a logoff script could change the RAdmin server settings back to allowing incoming connections with no requirement of a local user's permission.

Just my thoughts ...

A hammer is never really elegant ... but sometimes it IS the right tool for the job.

BTW, kudos on how busy you've been - it didn't take you long to surpass my total message count!

Quote
chris forrest wrote: ... what happens if it is set to auto deny and nobody is around the machine to accept?

Then the remote user cannot access the machine. There is no point in using an "ask user" and "auto deny" policy if you expect or require people to access an unattended machine.

Quote
Next, where can I set the number of concurrent Radmin connections to 1?

Currently, you can't. See this thread ...
http://www.radmin.com/support/forum/read.php?FID=30&TID=13800

Quote
Eugene Idzikovsky wrote: Probably feature of limiting connections amount won't be implemented.

I think it would be a good idea to implement this. It's up to the people administering the server to decide whether reducing the number of concurrent users to 1 is acceptable (for example on the basis that log on locally is available). You could also enforce a inactive session timeout after so many minutes _if_ the number of concurrent users is set to 1. So after say, 15 minutes of inactivity Radmiin Server drops the connection and Locks or Logs Off the server.

It's just a question of additional flexibility. The more flexible the product is the more people will buy it. No-one would be forced to set a connection limit of one would they - it's a decision individual users would have to take responsibility for.

And maybe this also ties in with other discussions about protecting Radmin settings to stop _any_ user with a full connection changing the settings - the idea of another permissions level like "Radmin Admin " who _is_ allowed to change settings.