basdear.blogg.se

1. #ADD TEAMVIEWER 13 ON STARTING WINDOWS 10 HOW TO#
2. #ADD TEAMVIEWER 13 ON STARTING WINDOWS 10 SERIAL NUMBER#
3. #ADD TEAMVIEWER 13 ON STARTING WINDOWS 10 INSTALL#

If you want you can add lines where you check for $Is64Bit is true or false, and modify the path, but in my case we only install 64Bit Windows 10.Įxecute-Process -Path ‘C:\Program Files (x86)\TeamViewer\TeamViewer.exe’ -Parameters “assign –api-token xxxxx-xxxxxxxxxxxx –group-id gXXXXXX –grant-easy-access –alias “”%computername% – %username%”””

The 2nd line is where we use the assignment tool to add device to group and configure the alias configuration This will configure the custom config you have already defined in Teamviewer Console, with logo etc, and you can choose if you want desktop shortcuts to be visible to users or not. The first line is where you run the Execute-MSI process with your parameters.Įxecute-MSI -Action ‘Install’ -Path ‘TeamViewer_Host.msi’ -AddParameters “CUSTOMCONFIGID=””xxxxxx”” DESKTOPSHORTCUTS=””0″” IMPORTREGFILE=””1″” /QN” (dont forget to remark out the Zero-Config MSI lines) Open the Deploy-Application.ps1 file in your favourite editor and we can start editing. (Se teamviewer documentation for this registry file) You can choose to do this /QN or not, that is up to you.Īdd Teamviewer_Host.msi file and the Teamviewer_Settings.reg file that you created from your template into the “Files” folder under the PSADT folder structure.

#ADD TEAMVIEWER 13 ON STARTING WINDOWS 10 HOW TO#

I wont get into how to deploy the applications within ConfigMgr, but look more at the specific lines in PSADT that you will add to help you in your way. This process is a 2 step job, first we need to install the msi as a system user, then we need to run the assignment tool so we can get the username currently using the computer. Awesome kit, so i do highly recommend it. Wasn’t very helpful, as the msi is install in system context, and the username showing is “System”, so the best way that i could think of this with good control of parameters was using PSADT ( Powershell Application Deployment Toolkit). –alias “”%computername% – %username%”” IMPORTREGFILE=1 Msiexec.exe /i “TeamViewer_Host.msi” CUSTOMCONFIGID=xxxxx DESKTOPSHORTCUTS=0ĪPITOKEN=xxxxxx-xxxxx ASSIGNMENTOPTIONS=”–grant-easy-access –group-id gXXXXXX

#ADD TEAMVIEWER 13 ON STARTING WINDOWS 10 SERIAL NUMBER#

Our pc names are defined based on the serial number of the pc itself, so asking users for the name of the pc was complicated enough, and we wanted to make it as simple as possible for them to accept a remote session.ĭoing a simple msi install deployment with custom settings like below: Now im not saying it cant be done easier, but i wanted –alias to show both %computername% and %username% when added to the group so its easier to find the users requiring support when they call helpdesk. Here is the link to their Mass Deployment Readme. When they did that all my work in previous version had to be redone, since the Assignment tool had changed. Teamviewer decided to change their deployment methods after version 13.2.