MSI Install Still Prompts for Driver After Cert Installed

Got a problem with Viscosity or need help? Ask here!

ywseait

Posts: 5
Joined: Thu Mar 30, 2017 5:00 am

Post by ywseait » Thu Mar 30, 2017 5:30 am
Hello, I'm trying to get a seamless install process down for our users using System Center's Software Center. So far I've followed the great instructions to create an MSI. I chose to make a packaged installation and based the MSI off of that. In Group Policy the only thing I'm pushing out is the certificate to Trusted Publishers. The certificate is installed on the machine I'm testing on but the MSI install still prompts for the driver install.

It does work if you choose "Install" but I don't want my users to have to make that decision so I'm trying to make it continue without any interaction. I've attached a screenshot of this happening. Can I make this automated?

Image

Eric

User avatar
Posts: 1146
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Thu Mar 30, 2017 12:33 pm
Hi ywseait,

Are you running the installer as a local user or domain/network user? If it's run as a network user, sadly, I think Windows ignores the local Machine store, meaning it will need to be run as a user with a store on the PC that the certificate can be installed to.

Regards,
Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs

ywseait

Posts: 5
Joined: Thu Mar 30, 2017 5:00 am

Post by ywseait » Fri Mar 31, 2017 2:58 am
None of the users are administrators on their own machines so the installer process for SCCM uses an AD account with admin rights on the workstations. I think that's probably why clicking "Install" still works.

If it's not going to work during the MSI install do you know of any other way to get the driver loaded silently in the background?

Eric

User avatar
Posts: 1146
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Fri Mar 31, 2017 9:26 am
Hi ywseait,

The only thing I can think of is to install the certificate as part of a script that also installs Viscosity so the driver is installed to a certificate store that the installing user can use, even if that store is destroyed once the installation is finished.

Otherwise I'd recommend asking SCCM if they know of a way.

Regards,
Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
4 posts Page 1 of 1