The script relies on PowerShell module so make sure that’s installed in your Azure Automation account and is running at least module version 6.1907.1. Make a note of the token - however it can always be retrieved later by editing the token: Give the token a name, description and edit access to Computers: You have to create a token under a user account, rather than the company profile, because only user accounts have access to edit devices via the API.Įdit your account profile in the top right drop down menu:Ĭreate a new script token from the Apps menu: Login to the TeamViewer portal with an admin account that will remain active - maybe a generic super user? In my example I’m using an admin account with my name. To connect to the TeamViewer API and add the primary user to the existing device name, we need a token to authenticate. Generally, the end user will not know the name of their device and the IT Service Desk would prefer to search by the users’ name rather than device.īy scheduling an Azure Automation script that uses the TeamViewer and Intune Graph API, we can append a to the device so it looks like: Lap-Win10-1 TeamViewer Portalīy default, when a device is registered in the TeamViewer portal by deploying the msi (through Intune of course) it doesn’t contain any information regarding the primary (or any other) user of the device. PowerShell script with functions that append the devices’ (retrieved from Intune) to the device name in the Teamviewer portal.
0 kommentar(er)
