Policy Customization For Temporary Access

ginoconte

The Aim:

An admin will connect to the windows device using separate remote software, they will then open TeamViewer, and give the User ID and current password to the External team for temporary access.

(To clarify the admin user or external team will not have logins for TeamViewer they will simply be using the user ID and random passcode to connect adhoc)

Considerations:

• User ID to stay the same
• Randomly generated password to change every day
• Sessions are not to last longer than 24 hours

The Question:

Which Teamviewer deployment is best to use taking into account the considerations above?

Are there policies that can be changed to match the requirements?

jbush

Sounds like Teamviewer QuickSupport on all client machines. That is not a full or licensed installation. I'd put a copy of the QS file in their documents or somewhere, and shortcut it to their desktop. Network admin remotes into client with whatever remote software you are using. They launch QS, and it will generate a new password on open. The client ID never changes. That info is then given to your external team if I am understanding correctly.

If you have a lot of domain machines, you could push Teamviewer Host via group policy. Same process to share the ID and password.

Your clarification is confusing though. You mention that neither your admin or external team will have Teamviewer logins. At a minimum, your external team will need Teamviewer in order to access the Teamviewer clients. Why else would you want to use a Teamviewer ID & Password for a remote session?