Go to documentation repository
Documentation for Intellect 4.11.0-4.11.3. Documentation for other versions of Intellect is available too.
Previous page Next page
INTELLECT™ installed as a Service, is started before user authorization in Windows OS and before Windows applications are launched (including the Explorer application which is used for starting up such applications as Windows OS and various other applications installed on the Server).
Note.
64-bit modules are not available when installing Intellect as a Service. 32-bit modules will be started after Intellect is installed as a Service. See also Configuring of using 64-bits modules.
While installing the Intellect software as a service the IntellectUsers user group will be created and the user who performed the installation will be added to this group. To add other users to the IntellectUser group use the Windows OS means. Users in the IntellectUsers group have the rights to configure the Intellect as a Service and access its interfaces. When it is necessary to arrange the access to the Intellect as a Sevice interfaces for a large number of users, it may be convenient to use the Active Directory (AD) - see Configuring INTELLECT™ as a Service to work with Active Directory (AD).
Note.
To start Intellect as another user admin rights must be assigned to this user or rights are to be advanced as described in the OS settings for correct operation of Remote Admin Workstation or Server section.
Note.
When the user from the IntellectUsers group enters a system, the Intellect software restarts under this user. If the Intellect software launch under the user name is not needed, i.e. the Intellect software is to be launched under the SYSTEM user name, restart is to be disabled using the Tweaki.exe utility – see The Settings panel of the Windows section part.
Note.
If INTELLECT™ is installed as a Service and database connection is performed via Windows account information, then for operation under the user different from the user who installed INTELLECT™ this user is to have SQL server permissions.