inGOT Notification #010008

HOWTO: Give inGOT Engine correct trustee permission to the NDS (Error 76).

Information in this article applies to:
- inGOT v4.x
- Netware NDS Domain with Border Manager logging.
- Microsoft Access or SQL Database Logging

Overview

This article has been updated and was formally called: “HOWTO: inGOT Engine user account configuration for Netware NDS” (12 August 2003)

With inGOT v4.0 the Engine component runs as a Windows Service. A Windows Service does not use the client login credentials to access network resources so the Netware Client utility cannot be used to provide the engine with permission to access NDS objects.

If trustee permission is not set correct the inGOT Engine will report “Error 76: Path Error” in the inGOT Engine system log (inGOTEngine_MMMYY.LOG).

NDS trustee permission is required for inGOT to read the Border Manager logs and update the NDS ‘Internet Access’ control group object(s).

Configuration

Option 1.

Three steps are required before the inGOT Engine can access resources on a NDS network:

1. Register the Window machine as a ZenWorks WORKSTATION

The Windows machine that runs the inGOT Engine must be registered as a ZenWorks WORKSTATION object in the NDS. Please see your Netware documentation for details on how to register a Windows workstation.

The workstation will appear as an object in the NDS

2. WORKSTATION Object Trustee rights.

The ZenWorks WORKSTATION object must be then be given trustee permission to several NDS objects. This includes:

• BorderManager log file folders (COMMON & EXTENDED folders)
• ‘Internet Access’ control NDS group object
• All User objects (if using the NDS User Field balance update facility)
• Access to the Internet

BorderManager log files are store in the COMMON and EXTENDED folder.

The workstation object must be given full trustee rights to the HTTP folder
(the folder that contains the COMMON and EXTENDED folders)

For inGOT to correctly scan the BorderManager log file folders the WORKSTATION object will need to be made SUPERVISOR trustee to these folders. We recommend that the WORKSTATION object be make SUPERVISOR to all objects to which it needs access.

3. Restart required

Unfortunately for changes to WORKSTATION object trustee right to take effect the WORKSTATION must be restarted.

Option 2.

If it is not possible to register the Windows machine as a ZenWorks WORKSTATION object the inGOT Engine can be run in ‘Client Mode’. Running the inGOT Engine in ‘Client Mode’ requires the Windows machine to stay permanently logged in.

Three steps are required to run the inGOT Engine in Client Mode:

1. Stop the inGOT Engine Windows Service.

The inGOT Engine service is, by default, set to automatically start when the machine restarts. It is therefore important to set the service to ‘Manual’ start. This is done via the Control Panel/Services window. Stopping the engine can be done via either the Control Panel/Services window or via the ‘Tools/Windows Service Control/Stop Engine’ menu in the inGOT Control user interface.

2. Manually start the inGOT Engine program

The inGOT Engine can be manually started by double-clicking on the ‘inGOTEngine.EXE’ application in the ‘C:\Program Files\inGOT4\’ folder. We would recommend creating a shortcut to this application.

3. Update the configuration of the inGOT Control User Interface.

The inGOT Control user interface is aware of the inGOT Engine running as a service. It is therefore necessary to change the configuration of the inGOT Control UI. This is achieved via the ‘inGOT Engine Settings’ in the inGOT Setup window. Uncheck the ‘Running as a Windows Service’ option and press ‘Okay’.

For further clarification please contact the Liverton support team at .

Copyright Liverton Ltd. ©2002