TeamViewer 10 deployment not adding registry settings?
Hi,
I am trying to deploy teamviewer 10 with custom registry settings so that the outlook add-in is disabled. So I have included the "TeamViewer_Settings.reg" file in the same source directory as the TeamViewer.msi. Is there something else I need to
do so that the registry settings are applied from this file when it is installed on the client?
January 30th, 2015 7:27pm
Since this is an application, I cannot create a program. I was told by my colleague that
For new installations (since the distribution
point is updated) this reg-file will automatically import during the
installation process" ?
-
Edited by
GibsonLP2012
Friday, January 30, 2015 8:14 PM
January 30th, 2015 8:14pm
In the task sequence, right after you install the package, you can add a run command line, and use
cmd /c regedit /s "C:\_SMSTASKSEQUENCE\OSD\PACKAGE_ID\your filename.reg", so if your package id is xxx000123, it will be "C:\_SMSTASKSEQUENCE\OSD\xxx000123\your filename.reg"
You can also copy the key to a local directory during the TS and do same from that local directory.
-
Marked as answer by
GibsonLP2012
Wednesday, February 04, 2015 2:18 PM
January 30th, 2015 8:36pm
Is this something I can do from the SCCM side? So I don't have to go to each client individually?
January 30th, 2015 8:37pm
Exactly what Jeff said in his first sentence above, use reg to import the file. You can do this is a variety of ways but using a package and program will work fine.
January 30th, 2015 9:07pm
So can I add the reg import to the command line:
msiexec /i TeamViewer.msi ALLUSERS=1 /qb- /norestart
January 30th, 2015 9:32pm
Since this is an application, I cannot create a program. I was told by my colleague that
For new installations (since the distribution
point is updated) this reg-file will automatically import during the
installation process" ?
-
Edited by
mkozz28
Friday, January 30, 2015 8:14 PM
January 30th, 2015 11:14pm
For new installations (since the distribution point is updated) this reg-file will automatically import during the installation process" ?
Unless this is how the TeamViewer installer works, the app model will not do that automatically. The same rules applies to the app model, if you need to run both commands, put it in a seperate script and reference that script in your script installer deployment
type.
January 30th, 2015 11:32pm
In the task sequence, right after you install the package, you can add a run command line, and use
cmd /c regedit /s "C:\_SMSTASKSEQUENCE\OSD\PACKAGE_ID\your filename.reg", so if your package id is xxx000123, it will be "C:\_SMSTASKSEQUENCE\OSD\xxx000123\your filename.reg"
You can also copy the key to a local directory during the TS and do same from that local directory.
January 30th, 2015 11:36pm
In the task sequence, right after you install the package, you can add a run command line, and use
cmd /c regedit /s "C:\_SMSTASKSEQUENCE\OSD\PACKAGE_ID\your filename.reg", so if your package id is xxx000123, it will be "C:\_SMSTASKSEQUENCE\OSD\xxx000123\your filename.reg"
You can also copy the key to a local directory during the TS and do same from that local directory.
-
Marked as answer by
mkozz28
Wednesday, February 04, 2015 2:18 PM
January 30th, 2015 11:36pm
Teamviewer 10 seems to be broken. We can not export and then Import registry settings. No Matter what they don't work. The Idiots at Team Viewer screwed this up!!!
February 9th, 2015 5:38pm
I noticed that the exported registry creates a 32 bit registry file only. In case of 64 bit you would have to duplicate the entries to match the ...\Software\Wow6432Node\... instead of ....\Software\....
-
Marked as answer by
GibsonLP2012
16 hours 27 minutes ago
May 20th, 2015 10:55am