Scense Administrator Guide

⌘K
  1. Home
  2. Docs
  3. Scense Administrator Guid...
  4. Exploring the Scense Syst...
  5. Scense System Folders

Scense System Folders

 

Applications.

The ‘Applications’ folder is intended for organizing all application objects. Within this system folder administrators can create normal folders to further organize their applications.

Computers.

The ‘Computers’ folder can contain Configuration Scope objects for computer configuration.

An administrator can create these computer scopes and configure settings for it.

Users.

The ‘Users’ folder can contain Configuration Scope objects for user configuration.

An administrator can create these user scopes and configure settings for it.

Scripts.

The ‘Scripts’ folder is intended for organizing all script objects. Within this system folder administrators can create normal folders to further organize their scripts.

Scopes.

The ‘Scopes’ folder can contain Global Scopes. Within this system folder administrators can create normal folders to further organize their Scopes.

Printers.

The ‘Printers’ contains Printer objects. These Printer objects can be organized in folders and sub-folders as well.

Administrative Tools.

The ‘Administrative Tools’ system folder contains several sub folders intended for the Scense administrator. This folder will only show up in the ‘Expert’ operation mode which can only be set by Scense Administrators.

Active Administrators.

The content of the ‘Active Administrator’ folder displays an overview of all current Scense Explorer users. This folder uses services of the Scense Community Service.

If the Scense Community Service cannot be found, the content of the Active Administrator folder will be composed of database queries.

When using the Oracle database system, the Scense database user name has to be authorized to read the V$SESSION system view to be able to show administrative session information.

The following details are shown for each item:

  • Computer
    The workstation on which Scense Explorer has been started.
  • UserName
    The log on name of the user that is running Scense Explorer.
  • FullName
    The full name of the user
  • Program
    Name and version of the program
  • Connected
    The moment at which Scense Explorer connected to the database and the Scense Community Service.
  • Last Transaction
    Moment of the last user action.
  • Monitor
    Indicates whether the user has utilized the monitor function.
  • Current View
    Indicates in which folder the user executed the last action.

Licenses.

All Scense licenses can be viewed and administered in the ‘licenses’ folder.

The next details are shown for each item:

  • Holder
    Name of the license owner. His can be e.g. workstations in a certain domain, or the Scense system itself (Master License).
  • Type
    Definition of the license type:

    • Master License.
    • Console License.
    • Client License.
    • Service License.

If necessary, licenses can be removed from this folder after clicking the ‘View all licenses’ link.

Configuration Settings.

The Configuration Settings system folder holds several categories for Configuration Setting Templates. These templates are provided by Scense and cannot be edited.

In the ‘Custom’ category administrators can create their own custom settings.

Location Root.

The Location Root is the system folder in which the administrator can create a location tree.

A location tree is a hierarchical representation of the physical locations.

More information can be read in the Locations chapter.

Messages.

Messages the administrator organization wants to send to the users can be stored in the ‘messages’ folder.

Unlike conventional messaging or e-mail systems, these messages can easily be sent to a group of users, e.g. an applications users group.

Messages can be scheduled very precisely, and can be given a certain priority which influences the appearance of the messages on the users screen.

Per item the following details are shown:

  • Name
    Logical administrative name of the message.
  • Source
    Source of the message.
  • Priority
    Specification of the message’s priority.
  • Domain
    Domain in which the message should be available.
  • Group
    User group to which the message should be available.
  • Start
    Moment at which the message should become available.
  • Expiration
    Moment at which the message expires.
  • Text
    Actual text of the message.

Messages can be activated and deactivated by checking or unchecking the box in front of a message.

 

Sites.

The ‘Sites’ system folder contains all defined Site-objects.

Per item the following details are shown:

  • Description
    Descriptive name of the site object.
  • Code
    Unique site code.
  • ReferenceName
    Domain group to which the site is connected.

System Logging.

If the SiteParameter ‘VerboseSystemLog’ has value ‘1’, every change in the Scense database made by the administrator will be logged in the system log book.

If the SiteParameter ‘VerboseSecurityLog’ has value ‘1’, all security violations will be listed in the system log book as well.

Per item the following details are shown:

  • TimeStamp
    Time stamp of the moment the event occurred.
  • UserName
    User name of the individual that caused the event.
  • Computer
    Name of the workstation on which the event occurred.
  • Text
    Description of the event.
  • Source
    Reference to the object that concerned the event.

User Information.

The moment Scense_Executive writes-in logging in the database, user objects will automatically be added to the ’User Information’ system folder.

This means users do not necessarily have to be defined before they can use the Scense system.

A user object contains both an ‘executive’ and a ‘user’ logging.

Per item the following details are shown:

  • Name
    Logon name of the user.
  • UserName
    The user’s full name.
  • Domain
    Domain the user was logged onto.
  • AvgLogontime
    Average time the logon script takes for this user.
  • LogonTime
    Duration of the logon script at most recent logon.
  • ProfileLoadTime
    Time Windows needed to load the user profile.
  • Totaltime
    Logontime + ProfileLoadtime.
  • LastLogon
    Moment of user’s most recent logon.
  • AvgLogoffTime
    Average time the Logoff script needs to finish.
  • LastLogoffTime
    Moment of most recent logoff.
  • Workstation
    Name of the workstation the user most recently used.
  • Domain
    Name of the workstation’s domain.

The information in the preview windows will also show any applications, network drives and printers this user might have.

Computer Information.

The moment Scense_Executive writes-in logging in the database, user objects will automatically be added to the ’Computer Information’ system folder.

This means users do not necessarily have to be defined before they can use the Scense system.

A computer object contains an ‘executive’ logging.

Per item the following details are shown:

  • Name
    Logon name of the user.
  • UserName
    The user’s full name.
  • Domain
    Domain the user was logged onto.
  • AvgLogontime
    Average time the logon script takes for this user.
  • LogonTime
    Duration of the logon script at most recent logon.
  • ProfileLoadTime
    Time Windows needed to load the user profile.
  • Totaltime
    Logontime + ProfileLoadtime.
  • LastLogon
    Moment of user’s most recent logon.
  • AvgLogoffTime
    Average time the Logoff script needs to finish.
  • LastLogoffTime
    Moment of most recent logoff.
  • Workstation
    Name of the workstation the user most recently used.
  • Domain
    Name of the workstation’s domain.

Both User- and Computer objects offer direct access to the remote desktop.