Welcome to our community!

Consent set by controlled syntax (Only these systems or by group)

RichardX720

9 years ago
updated 9 years ago
Completed

At the moment, I have client workstations I need to access that MUST have the consent popup however the servers should not. We have a few servers that must start up to a user account automatically for some archaic software and I am unable to log into these systems because there is no physical user ready to hit consent. If we could either apply an app.config by a group or allow "SC user John Doe" = allowwithoutconsent for systems LIKE... that would be great! Right now I must log out of my normal user and into the admin account to reach these servers.

Pinned replies

Tim@CCS

9 years ago
Answer

You could create a session group for these "unattended machines" and grant "host without consent" permission to just that group to do exactly what you want.

Reply Link

Replies 5

Oldest first
Newest first Oldest first

Tim@CCS

9 years ago
Answer

You could create a session group for these "unattended machines" and grant "host without consent" permission to just that group to do exactly what you want.

Reply Link

RichardX720

9 years ago

I know this is a feature. However, the issue is the amount of time it takes to reset consent. I have HIPPA clients who require the consent every time I must remotely log on. If I have a client who has me remote in at 8:00am for one issue and again at 2:30pm for a different issue, I need it to prompt again for consent.

Reply Link

anonymous

9 years ago

Quote from RichardX720

Richard,

We are currently working on a configurable option that would expire consent when a host has been disconnected for "x" amount of time.

Reply Link

RichardX720

9 years ago

That would be perfect.. :)

Reply Link

anonymous

9 years ago

The two issues are unrelated. Role based permission controls which machines have consent. We are putting in an option to make the consent reprompt after a host has been disconnected after "x" amount of time. It will be included in a 6.0 update to be released soon. This is the issue tied to it: http://product.screenconnect.com/topics/547-allow-for-a-choice-between-legacy-consent-method-and-the-newest-one-time-consent-until-restart/ . We'll update the post when it's ready.

Reply Link