raestoz Posted July 16, 2015 Report post Posted July 16, 2015 Hi everyone, Having a bit of trouble trying to find a concrete answer on this with my Googlefu. We've got a handful of applications that are using .vbs or .bat files for installs. What we're finding is that using the "script installer" deployment type appears to run everything in user context - regardless of whether or not 'install for system' is used. Is this the usual behaviour for the script installer deployment type? Some of the installs are failing as they are running under user context and don't have the rights to do what's needed. Our mandate is to have everything loaded as an application so creating a package is not an option. Thanks Quote Share this post Link to post Share on other sites More sharing options...
JTPort Posted July 17, 2015 Report post Posted July 17, 2015 Are you definitely using 'Install for system', not 'Install for system if resource is device; otherwise install for user'? Quote Share this post Link to post Share on other sites More sharing options...
raestoz Posted July 20, 2015 Report post Posted July 20, 2015 Yep definitely install for system. Starting to put this down as a bug - as you can see in task manager it's actually running under System yet the log file still states 'user context'. Quote Share this post Link to post Share on other sites More sharing options...
Adam Bise Posted July 22, 2015 Report post Posted July 22, 2015 I have several applications are using script installer deployment types. The appenforce.log always says running command line in user context, but I think they are actually running in the system context because they all work when non admin users are logged on. BTW I normally choose "Install for system" and "whether or not a user is logged on" Also these are device deployments, not user. Quote Share this post Link to post Share on other sites More sharing options...
