Updating Viscosity on multiple devices

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

datevat

Posts: 10
Joined: Mon Jun 17, 2019 5:27 pm

Post by datevat » Mon Jun 17, 2019 5:51 pm
Hello,
how would I go about updating Viscosity on multiple devices (AD)?
I tried doing it with WSUS/WPP (WSUS Package Publisher), which we use to successfully roll out virtually anything (exe/msi), but with Viscosity I come into problems like that it says that service is not running, and it breaks Viscosity completely.
Thanks

Eric Online

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

Post by Eric » Tue Jun 18, 2019 10:20 am
Hi datevat,

This sounds like a permissions issue on the user running the installer. We have some information here that might help - https://sparklabs.com/support/kb/article/deploy-viscosity-windows-under-a-gpo-group-policy-environment/

Regards,
Eric
Eric Thorpe
Viscosity Developer

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

datevat

Posts: 10
Joined: Mon Jun 17, 2019 5:27 pm

Post by datevat » Tue Jun 18, 2019 4:20 pm
Yes, I know the page.
I don't want to deploy via GPO, if anyhow possible. I prefer to keep my deployments in one place, and for each package until now, this is working without problem. I'm doing it this way:
GPO rolls out a registry key (according to the Security Group).
WPP has the package ready for installation, and a conditional entry to install only if the key exists.
Additionally I can filter according to computers in WPP (same as WSUS).
That way I can simply assign users to groups/computers and what to install.

WPP doesn't have the ability to run a script before or after an update. After all, WPP basically puts the package into WSUS, and Windows Update installs it. There are no permissions needed, as all users can install Windows Updates when they are rolled out. However, I can specify the command line - and I do wonder, can I stop the service with the command line?

Eric Online

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

Post by Eric » Wed Jun 19, 2019 11:30 am
Hi datevat,

Please refer specifically to the following which has some general information on updating with package managers and also contains some information on how to stop/start the service using command line - https://sparklabs.com/support/kb/article/deploy-viscosity-windows-under-a-gpo-group-policy-environment/#updating-viscosity

Regards,
Eric
Eric Thorpe
Viscosity Developer

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

datevat

Posts: 10
Joined: Mon Jun 17, 2019 5:27 pm

Post by datevat » Wed Jun 19, 2019 5:24 pm
Yes, I have read that too. But still the same question:
Can I implement a service-stop command into the argument line of viscosity installer?
Currently I have this:
/SP- /verysilent /NORUN

Eric Online

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

Post by Eric » Thu Jun 20, 2019 12:00 pm
Hi datevat,

Viscosity's Installer is already trying to stop the service before replacing it and start the service again at the end of installation/update. There are no additional commands that need to be added.

Regards,
Eric
Eric Thorpe
Viscosity Developer

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