CallScriptAs

Run Windows script as different user

Definition

The new CallScriptAs eScript command is an enhanced version of CallScript.

It runs the script as a different user (like the RunAsEx command). Note that this command only works with Windows Vista or higher.

Settings

Options

• Script file
  Enter the name of the script file you want to run through a scripting engine here.
• Click the Edit button to open and edit the script in the Editor.
• Execution in a x64 environment
  For reasons of compatibilty, Ivanti DSM maps file and registry access to the default storage location for 32 bit applications (provided that the storage location differs from that of 64-bit applications). File access: whenever a 32-bit application attempts to access %windir%\System32, the access is redirected to %windir%\SysWOW64. Registry commands: when accessing HKEY_LOCAL_MACHINE\SOFTWARE the calls are redirected to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node. The x64-switch stops this redirection of file and registry accesses when running the script command on a x64 computer; the eScript command runs on the specified path. CallScript command: the script runs in a 64-bit process.
  

Account

• Use this account
  The application is executed using the account information entered.
  
  User name: The user account under which the application is to be executed.
  
  Data can be input as follows:
  
  <Username>
  
  <Domain>\<Username>
  
  Password: The password for the selected user account
• Use DSM account
  
  The application is executed using one of the configured DSM accounts. The account will be automatically determined according to the following rules:
  • If the option Log on for network only is selected (see below), the User Account for Depot Access will be used. If this account is not configured, the logged-in user's account is used instead.
  • In all other cases, the user account for the DSM Runtime Service will be used. If this account is not configured, the account is used instead under which the ServiceInstaller is running..
• Use local system account
  
  The application is executed under the local system account.
• Use the logged on user
  
  The application is executed under the account of the currently logged-on user.

  If this option is used in the context of the Service (i.e. a DSM service account is currently logged on), the execution is different from the interactive logon via the option Use DSM account: When running in the context of the Service the user always has full rights, while an interactive logon is controlled by the User Account Control (UAC).

Do not run as administrator 
With the User Account Control (UAC) activated, CallScriptAs always executes the application as an administrator.
Activating this option can be useful, for example, if a certain website is to be opened and you want to prevent that this happens with administrator privileges.

If this option is activated, it is always applied, even if the logged on user is actually an administrator. This behavior is different to previous versions of the command without this option.

Logon options

• Log on without profile
  
  The user profile is not loaded. No changes are written into the user profile after the application has been executed.
• Log on with profile
  
  The user profile is loaded. Changes are written into the user profile.
• Log on for network only
  The application is executed using the current user account. The specified user account will only be used for access to the network, i.e. a logon session is opened under the specified user account.