Skip to content

Application - script installer type behaviour

Featured Replies

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

 

 

Are you definitely using 'Install for system', not 'Install for system if resource is device; otherwise install for user'?

  • Author

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'.

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.

Join the conversation

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

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.