Versions Compared

Old Version 2

changes.mady.by.user IT Stonebranch

Saved on

compared with

New Version Current

changes.mady.by.user Stonebranch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

<ul> <li>
  • Leaving
  • this
  • option
  • unchecked
  • causes
  • user
  • processes
  • to
  • execute
  • in
  • a
  • context
  • that
  • isolates
  • them
  • from
  • the
  • current
  • interactive
  • logon
  • session.
  • Unless
  • processes
  • that
  • require
  • user
  • interaction
  • are
  • executed,
  • this
  • is
  • the
  • recommended
  • setting.
<li>
  • This
  • option
  • only
  • applies
  • if
  • a
  • user
  • account
  • (in
  • whose
  • security
  • context
  • a
  • process
  • is
  • executed)
  • is
  • authenticated
  • via
  • an
  • interactive
  • logon.
  • If
  • the
  • User
  • must
  • have
  • batch
  • logon
  • right
  • option
  • is
  • checked,
  • a
  • batch
  • logon
  • is
  • done
  • to
  • establish
  • the
  • process's
  • security
  • context.
  • This
  • logon
  • method
  • requires
  • additional
  • privileges,
  • but
  • disallows
  • all
  • interaction
  • with
  • the
  • desktop.
</ul>

User must have batch logon rights
When this option is checked, the Log on as a batch job user right must be granted to the user ID passed to Universal Command before the process will run. This is an advanced user right that must be set using the NT User Manager.
 
Execute process with highest privileges
When this option is checked, user processes that UCMD Server executes receive an elevated access token. This gives the account used to execute the process the highest privileges available to it. Note that the account is not granted any new privileges, it simply receives the privileges necessary to execute tasks under User Account Control (UAC) restrictions.
 
Note that this option is only recognized for Windows platforms starting with Windows Vista. It is ignored for Windows XP and Server 2003.

Field

Description

User Security Options

Require User ID and password to start process
When this option is checked, Universal Command will require a valid user ID and password to start a process.
 
Load the user’s environment
When checked, causes Universal Command Server to load the profile and the environment settings for the user account being used to execute the requested process. This is necessary only if the process requires access to user-specific environment variables, or registry values that are only stored under the HKEY_CURRENT_USER key.
 
Allow process to interact with desktop
When this option is checked, processes are run in a context that permits the current console logon session to interact with them. This also allows the process to invoke system functions that access desktop elements (for example, Windows, menus, buttons) associated with that session. Accordingly, this exposes a risk whereby a process could hijack the desktop and invoke malicious code using a (potentially) elevated security context.

Html bobswift

Standard I/O redirection timeout

Specifies the length of time, in seconds, that a Universal Command Server will wait for stdin, stdout and stderr files of the process it starts to close. If the closure of those files is not detected within the time limit set by this value, the Universal Command Server will end, even if the process it started has not ended.

...

<ul> <li>x*<br> Do not generate any events (this is the default) <li>*<br> Generate all event types <li>100<br> Generate all event types except 100 <li>100,200-205<br> Generate event type 100 and 200 through 205 <li>100,200-205,x202<br> Generate event types 100 and 200 thru 205, excluding event type 202 </ul>
  • x*
    Do not generate any events (this is the default)
  • *
    Generate all event types
  • 100
    Generate all event types except 100
  • 100,200-205
    Generate event type 100 and 200 through 205
  • 100,200-205,x202
    Generate event types 100 and 200 thru 205, excluding event type 202

Entries are processed from left to right, and the list is order dependent. For example, an entry of x*,100 prevents generation of all event types except 100, while an entry of 100,x* prevents generation of all event types (the right-most entry takes precedence).

Field

Description

Event Generation Options

Generate activity monitoring events
When this option is selected, the Universal Command Server will generate events that monitor product activity.
 
Persistent event list
Specifies which events are to be generated and processed as persistent events. A persistent event is saved in a Universal Enterprise Controller (UEC) event database for long-term storage.
 
Enter a list and/or range of numeric event types, separated by a comma. To exclude an event or range of events, precede the entry with an upper- or lower-case 'X'. Use an asterisk (star) to specify all event types.
 
For example:

Html bobswift

...