Messages

Thanks!  Will give this a try.

We have two TeamViewer Host audiences that have custom/different TVOPT configuration files. Is it possible to apply some type of condition check to apply tvopt#1 for audience#1 or tvopt#2 for audience#2? 

I'm working through Scenario #3 on https://patchmypc.com/how-to-customize-teamviewer but having difficulty determining how to configure pre/post settings for two different audiences.

Thanks in advance.

Looking at the OS Deployment and Content Sources tabs, I do not see any references to the install.wim or drivers.wim used by the task sequences.  When I look at the task sequence steps, I do see the task (i.e. Apply Operating System with min/max/avg timings) but not the details of the source/destination of the actual pkg/content.

Is there setting in application or IIS that will display this information?

It looks like our TV installations (full and host) load into the WOW6432Node in the registry (sample export below).  The custom msi we use is from 2018, created via the Design&Deploy node on TeamViewer.com, and deploys version 13.1.3629.  The first update to go out from PatchMyPC was v13.2.36218.  we will not be moving to 15x until the late fall.    I downloaded the v15 setup.exe from TV and it also installs to the WOW6432Node... is this maybe a result of residual files left behind?

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\TeamViewer]
"DisplayName"="TeamViewer 13 Host"
"DisplayIcon"="C:\\Program Files (x86)\\TeamViewer\\TeamViewer.exe"
"Publisher"="TeamViewer"
"HelpLink"="http://www.teamviewer.com"
"UninstallString"="\"C:\\Program Files (x86)\\TeamViewer\\uninstall.exe\""
"NoModify"=dword:00000001
"NoRepair"=dword:00000001
"VersionMajor"=dword:0000000d
"VersionMinor"=dword:00000002
"InstallLocation"="C:\\Program Files (x86)\\TeamViewer"
"DisplayVersion"="13.2.36217"

thanks.   Should add that we are on trial license until Accounting can process payment tomorrow.   

SCCM catalog

Have a situation where I enabled TeamViewer 13 and it updated the host installs to full client.   I have since disabled the update until I can get hosts back in place.  Not sure if others have seen this behavior?  Will you be offering security updates for the host instances?   Thanks in advance.