TeamViewer option "dynamic password" system-wide

NeturiusGmbH

Hello,

i try to create a deployment of TeamViewer Host 15 (15.22.3) as we want.

MSI package, unattended CLI installation and assignment works like a charm.

Only the configuration drives me crazy. Or better two special points:

1. "DeactivatedDynamicPassword" under HKEY_CURRENT_USER
2. absolute path to ".tvopt" file

Let's focus on the first point:

Is it or will it be possible to set these configuration for the whole system without GPO?

Thank you.

NeturiusGmbH

JeanK

Hello @NeturiusGmbH,

Please correct me if not, but as far as I understand your post: you want to disable the random password on all your deployed clients.

If this is the case, you can do this via TeamViewer policy:

https://community.teamviewer.com/English/kb/articles/4860-how-to-add-a-new-settings-policy

The parameter is called Password strength. Make sure to Enforce it as well, so it can't be enabled manually by the users.

Did this answer the first point? 🤓

JeanK

Hello @NeturiusGmbH,

Please correct me if not, but as far as I understand your post: you want to disable the random password on all your deployed clients.

If this is the case, you can do this via TeamViewer policy:

https://community.teamviewer.com/English/kb/articles/4860-how-to-add-a-new-settings-policy

The parameter is called Password strength. Make sure to Enforce it as well, so it can't be enabled manually by the users.

Did this answer the first point? 🤓

NeturiusGmbH

Yes, it does, thank you :)

To the second:

We start the MSI installation by a script where the parameters are given (API-Token, CustomConfig-ID, Assignment and Configuration).

Before V15 we used the "importregfile=1" parameter. And now i try to switch to "settingsfile=".

What i have tried so far:

settingsfile="config.tvopt"

settingsfile="/config.tvopt"

settingsfile="%CD%\config.tvopt"

settingsfile="%~dp0config.tvopt"

Everytime, no settings (of the file) can be found in registry after installation finished. So, i guess, the file is not processed.

A manual import of the tvopt file or an execution of the reg file does change the registry.

The last test was:

start /wait msiexec.exe /i "%~dp0TeamViewer_Host.msi" /qn APITOKEN=XXXXXXXXXXX CUSTOMCONFIGID=XXXX SETTINGSFILE="%~dp0TeamViewerSettings.tvopt" ASSIGNMENTOPTIONS="--reassign --alias %COMPUTERNAME% --group _Neu --grant-easy-access"

JeanK

Good 👍 let's tackle point 2 together now...

If it's a local file, I recommend testing this:

SETTINGSFILE="C:/my_settingsfile.tvopt"

If it's a shared file, I recommend testing this:

SETTINGSFILE="\\share\my_settingsfile.tvopt"

⚠Important is to make sure to use the exact name of the .tvopt file in your command line.

Let me know how your testing goes!

NeturiusGmbH

Hi,

thanks for response. And, please apologize my late response.

Nice, but this is just a reply from documentation. May i wasn't clear. If so please excuse.

I neither have a local absolute path nor a smb-share.

We use the potential of MSI and the internal workspace. So, my file is stored by MSI in a temporary folder, which will be cleaned up by MSI after installation.

Why do i need an absolute path in a mass deployment where i can deliver an "all in one, simple double-click" package?

The requirement kills this possibility :(

Any workarounds?

Thanks,

Rene

JeanK

Hello @NeturiusGmbH,

Unfortunately, I don't have any woraround to provide...

I recommend opening a ticket via the link below:

➡Open a ticket

Our engineers will take a closer look at your issue...🔍👀

All the best,

JeanK