Author Topic: MSI Install - Account Assignment Prompt  (Read 9646 times)

generik99

  • Newbie
  • *
  • Posts: 2
MSI Install - Account Assignment Prompt
« on: June 03, 2014, 08:24:21 AM »
Hey folks, I already sent a ticket to Teamviewer Support, but figured I'd try here as well.

I'm looking to upgrade ~200 workstations from a mix of TeamViewer Host 6-8 to 9 using a customized MSI installer. Everything works so far accept for suppressing the 'Account Assignment' dialog that comes up when Host is first run on the workstation. I'm using vanilla group policy to do the package installation.

The MSI Manual has a section to create a Service Connection Point in Active Directory that I've followed and added the MSI code, but the package appears to be ignoring it as the new host installs fine, but doesn't suppress the prompt.

I've attached a screenshot of my object. Does anyone see any obvious problem with it? I had a couple questions in regards to the MSI manual which I sent to support, but feel free to jump in if you've already come across them:

- The MSI manual says the object can be named freely. I wonder if this is actually the case.
- One of the attributes to add is a GUID [B15CB251-377F-46FB-81E9-4B6F12D6A15F]. Is this correct for TV9? I haven't found what it's referencing, the Product, Update and Install GUIDs for the installed host do not match this value.

At any rate, if TV support gets back to me, I'll relay their advice here as well for future reference.

Cheers!
« Last Edit: June 03, 2014, 08:29:22 AM by generik99 »

generik99

  • Newbie
  • *
  • Posts: 2
Re: MSI Install - Account Assignment Prompt
« Reply #1 on: June 03, 2014, 09:03:55 AM »
Hey, so I heard back from Support. I was able to successfully suppress the prompt by doing two things:

1. The MSI Manual is incorrect -- It recommends you create the TeamViewer container under CN=System, where you actually need to create it in your DC root (up one level).

2. I still had the 'idc' prefix in my MSI code which didn't match. When you add the code in the object attribute, make sure 'idc' is omitted, even though you still need to include it in the filename of the MSI.