Comments
-
The DeviceId must be the TeamViewer ID (your "TeamViewer number"). You can get this number for the current device by calling the Get-TeamViewerId PS cmdlet. Find the documentation about it here: https://github.com/teamviewer/TeamViewerPS/blob/main/docs/commands/Get-TeamViewerId.md So your overall call could look like this:…
-
Hi Ben, Yes this is possible. And we also have existing solutions that you can use: SCIM API: If you use Azure AD for example, you can enable user provisioning there to automatically create, update or deactivate TeamViewer accounts. The TeamViewer AD Connector: A simple Powershell based script that supports regular sync of…
-
Hi Dan, Thanks for posting this script. If you want, you can simplify this using our open-source TeamViewerPS Powershell module. It is possible to do all that in basically one line of Powershell 😉. However, I've split the line to make it better readable: # Install the module, if not already done Install-Module TeamViewerPS…
-
Hi all, This can be solved very easily using our TeamViewerPS Powershell module: # install the module if not already done: Install-Module TeamViewerPS # Store the API token in the current session Connect-TeamViewerApi # Get all devices, filter by "assigned" + "policy is not 'inherit'", change to 'inherit'…
-
Hi, The knowledge base article is still missing this part. The customeridentifier needs to be configured for the AzureAD integration, as well. You therefore need to add a custom SAML Token attribute: * On the settings page of the Single SIgn-On app in Azure AD, Check the "View and edit all other user attributes" checkbox…
-
Hi, Did you check the option "Include users of nested AD groups"? Also, the AD connector script filters out users that are disabled or do not have a primary email address set. You can try to execute the following Powershell snippet to see if users can be fetched properly. The AD connector script does a very similar call.…
