Jump to content


Application - script installer type behaviour

Recommended Posts

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.




Share this post

Link to post
Share on other sites

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.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...