Hi

I am having trouble deploying the Teamviewer 11 host MSI file. I am running Kace k1000 6.4.120756.

When I deploy without options the install starts and I can interact with it but when I use options for example:

msiexec.exe /qn /i "TeamViewer_Host.msi" /norestart I only get the msiexec help window like as if I did, msiexec /?


Since I have all settings in a .req file I zip the MSI and .req file and upload to Kace and as I said if I do default installation with user interaction(no switches) the setup it is OK but with the msiexex switches it fails.


Has anyone been successful in deploying this? All help much appreciated.


Best Regards

Jakob

1 Comment   [ + ] Show Comment

Comments

  • For the record it is Teamviever 11
Please log in to comment

Answers

0
Hi,
your command line seems a bit weird...
try:
msiexec /i "TeamViewer_Host.msi" /qn

If you want to ensure that no reboots etc. are shown / carried out, then create a transform setting the properties accordingly.
If you have settings that need to be applied (this includes the license key) then install it normally, and under settings make the changes you need, add the license information and export the settings to a registry file (this is also available in the settings). This needs to be called "TeamViewer_Settings.reg" and must reside beside the main msi file.

Cheers
Phil
Answered 04/28/2016 by: Pressanykey
Red Belt

Please log in to comment
0

Hi Phil

Many thanks for this. I tried the msiexec switches you suggested but still the same, it pop's up with the msiexec help window. I have extracted the settings to a .req file as you mention and gave it the correct name, this I zip together with the MSI host file and upload to Kace.

I have tried many variations of the msiexec switches without luck (the help windows always pops up) so I have started to wonder if there is something else I am doing wrong as the msiexec should be pretty standard right?


Many thanks!


Cheers

Jakob

Answered 04/28/2016 by: jorundsson
White Belt

  • Hi,
    that's about as easy as it gets... could you post your EXACT command line that you are using? I know it might sound strange, but are you using the extracted msi (usually it is contained in a self-extracting executable)...

    Phil
    • Hi Phil
      Here is the exact command I use: msiexec /i "TeamViewer_Host-idc5euzw2y.msi" /qn

      This is the associated file:TeamViewer_Host-idcc5euzw2y.zip

      And it contains the msi and .req file.

      Many thanks
      Jakob
      • The only thing that springs to mind is that the msi that you pass in the command line does not exist...
Please log in to comment
0
> the msi that you pass in the command line does not exist...
You get a different dialog, then - "This application package could not be opened [blah, blah, blah]"
Answered 04/28/2016 by: VBScab
Red Belt

  • true... can you think of anything else then?
Please log in to comment
0

>can you think of anything else then
Nope! Stumped! The only thing I can think of is perhaps, somehow, the backslash character is not being handled as the correct character. Unusual but I've seen a similar situation before with quote marks.

@OP, you can test this by copying and pasting a command line from a web page.

Answered 04/29/2016 by: VBScab
Red Belt

Please log in to comment
0
I tried removing the quotation marks but still the same, maybe it is time to try to do this using a .bat file and call the MSI from there?
Answered 04/29/2016 by: jorundsson
White Belt

Please log in to comment
0

It wasn't the quote marks I was concerned with but the backslash.

Try copying and pasting this. Use the 'Run' dialog rather than a command prompt, so we can eliminate any odd/dodgy DOS code pages. Hopefully, it's obvious that you need to substitute '[path_to_the_MSI]' with the actual path where the MSI is located.

msiexec /i "[path_to_the_MSI]\TeamViewer_Host-idc5euzw2y.msi" /qn
Answered 04/29/2016 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity