I am having a similar issue to those stated here, though not 100%, hoping someone can help. I downloaded the .msi and installed it with the appropriate command line properties, and it worked beautifully. Installed the Host, and assigned to my account. Using the same command line in an MDT Application, it installs the Host, but no assignment to my account. I then downloaded the Customised exe and installed with only the /S switch. Again, it installed perfectly and assigned to my account with no interaction. Changed my MDT application to use the .exe installer, and once again it installs the application, but no assignment to my account. * No Outgoing ports are blocked during deployment. * Application installed on non-domain joined workstation by Administrator Anyone have any suggestions?
... View more
@MortenS wrote: Anyway, just to let you know, we solved/did a workaround on the issue with the TeamViewer.reg file not beeing applied by editing the msi with good old fashion Orca, setting both the CUSTOMCONFIGID and IMPORTREGFILE variables in the Property table. Tested and working on Win 10 Ent Build 1803 and 1809. Not happy with this, but working. I find that when deploying any application that requires the application install plus additional registry settings that editing the MSI is cleaner. However, I would suggest exporting your changes as a transform (MST) so you aren't actually changing the original MSI. You may have done this, but it's not clear. Just my 2 cents.
... View more