[Application - script installer type behaviour]

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

[Application - script installer type behaviour]

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