![]() Applications/TeamViewerHost.app/Contents/Helpers/TeamViewer_Assignment -api-token $APITOKEN -group-id $GROUPID -alias "$(hostname -s)" -grant-easy-access -reassignĮcho "Waiting for TeamViewer to start. Process=$(ps aux | grep TeamViewerHost | grep -v grep | wc -l) Use the following script in Jamf Pro to ensure all processes are fully running: User 6879 0.0 0.1 4355920 15880 ? S 3:06pm 0:00.63 /Applications/TeamViewerHost.app/Contents/MacOS/TeamViewer_Desktop -RunAsAgent YES -Module Host This article applies to Corporate and Tensor license holders who want to deploy TeamViewer (version 15 or newer) on their Windows devices. Deploying it through your IT infrastructure will apply what you have defined in the previous steps. User 6881 0.0 0.3 4432632 47748 ? S 3:06pm 0:00.47 /Applications/TeamViewerHost.app/Contents/MacOS/TeamViewerHost -RunAsAgent YES The assignment command contains all parameters we have previously set up. ![]() Even with the correct share permissions in place. This issue was still present after completely uninstalling TeamViewer, rebooting the computer. Currently, moving computers that are assigned to one account, between shared Groups is not possible. ![]() $ ps aux | grep -i TeamView | grep -v grep When I tried to assign the computer, up popped the dialog to assign the computer to my account, I clicked OK as my account email was displayed as expected, but after a coupe of seconds, the dialog closed and nothing changed on the Assign Device line. All of the TeamViewer processes must be fully running, before an assignment will be successful. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |