/build/static/layout/Breadcrumb_cap_w.png

ClickShare Launcher - Avoid SYSTEM user error

It wasn't hard to figure out the answer file and /mode command.   But has anybody figured out how to avoid the installers error message "The Clickshare Launcher Application should not be run as SYSTEM user.  Exiting now." with a click OK dialog box. 

This is for deploying via MI or Software Library modes. 

1 Comment   [ + ] Show comment
  • did you ever manage to get this working? - chris.poston 8 years ago

Answers (3)

Posted by: JeremyN 10 years ago
White Belt
0
I still have to do some testing but i think i found a way around the SYSTEM only error but using a tool called RunAsCurrentUser.exe.  

It runs the installer as the logged in user.  
Posted by: dunnpy 10 years ago
Red Belt
0
This Barco KB article says that their installation should be run as a user, not system: http://www.barco.com/en/mybarco/mysupport/productsupport/product-support-files/knowledgebase?productid=b21eda55-0837-4478-87f6-68d51b71e405&kbid=1308

Which makes it difficult when using a deployment tool that runs installs as SYSTEM!
Is there a way with KACE to give it an alternative account to run with, and provide one with admin rights to install on the machine?
The example in the article shows installing to 'Program Files', so you'd think that there'd be a way around this, as you wouldn't normally have standard users with permission to do this.

Dunnpy
Posted by: tneubauer 9 years ago
Senior Yellow Belt
0

I am deploying this with SCCM 2012 and configured the Application deployment type as follows:

  • Installation behavior: Install for user

The System error does not occur with this configuration.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ