| Base
Requirements:
- Requires Microsoft Windows NT 4, 2000 (Workstation
or Server), XP or 2003.
- Requires Microsoft Access 97, 2000, 2002 or 2003.
InGOT requires a Microsoft Windows NT/2000/XP/2003
machine to run on. This may be a workstation or server but must
have local
or network access to the proxy server log files. In an Windows
Domain network, MS Proxy/ISA Server and inGOT would typically
run on the same server machine. In a Netware environment, inGOT
would run on a separate machine to BorderManager with network
access
to the log files.
InGOT uses a Microsoft Access database
to store user account information and log records. MS Access
must
be installed (preferably on the same machine as inGOT)
to view reports.
Requirements for NT/2000/2003 Domain and MS Proxy Server
environment:
- Microsoft NT 4, 2000 or 2003 Server
- Microsoft Proxy Server v2.0/ISA Server
- Microsoft Access ODBC driver.
- Access to the Primary Domain Controller.
In a Windows domain, inGOT requires Microsoft
Proxy Server v2.0 (with Proxy Server Service Pack 1 applied) or
Microsoft ISA Server.
The proxy server must be configured to log requests to an ODBC
database for inGOT to monitor requests. The inGOT
installation program will provide the databases needed for the
proxy server logging
and instructions to set up the proxy server to log into them.
The Microsoft ODBC driver for Access is required to permit the
proxy server to log to an Access database.
InGOT must have access to the User Accounts database on
your network's Primary Domain Controller and must be run with
Account
Administrator privileges in order to automatically add and remove
users from the domain network group that is used to grant proxy
access to the Internet.
Requirements for Novell Netware and BorderManager environment:
- Netware 4.1 operating system or later.
- Novell BorderManager 3 proxy server.
- Novell Netware Client for NT.
In a Novell Netware environment, inGOT requires
the Novell BorderManager 3 proxy server running in a Netware 4.1
(or later) environment using Novell Directory Services.
BorderManager must be configured to log requests to 'common' and
'extended' text log files for inGOT to monitor requests.
The Windows workstation or server running inGOT must have
the Novell Netware Client for NT/2000/XP loaded in order to authenticate
correctly to the Directory Services and provide the functionality
for inGOT to manipulate objects in the NDS tree.
InGOT must have administrative privileges on the NDS tree
in order to automatically add and remove users from the NDS groups
that are used to grant BorderManager access to the Internet.
Requirements for intranet access to user account information:
- Microsoft NT 4, 2000 or 2003 Server in a Windows
Domain environment.
- Microsoft Internet Information Server 4 or above.
- Microsoft Access ODBC driver.
To provide intranet pages for users to query their own account
information,
inGOT requires Microsoft IIS 4 or above running on the
Windows server in an Windows Domain environment. This can be (and
is typically)
the same machine on which both Proxy/ISA Server and inGOT
are running. The web folder in which the pages are installed must
be
configured to allow script execution to allow the Active Server
Pages to retrieve information from the database.
An ODBC entry pointing to the inGOT user account database
must be configured for the web pages to gain access to the database.
The Microsoft ODBC driver for Access is required on the web server.
The inGOT installation media has a copy of the Microsoft
ODBC installation program to install the required ODBC driver.
Other General Requirements:
- InGOT only charges users for requests through
Proxy Server.
- InGOT requires a secure terminal to execute
from.
InGOT only monitors requests as recorded by the
proxy server so all traffic that you want to charge for must go
through the proxy server. Other traffic that users have access to
will not be logged by proxy server and therefore not charged to
user accounts. User authentication (with no anonymous user access)
must be enabled so that the proxy server will log the user ids in
its log records. This allows inGOT to allocate costs to
the correct user accounts.
InGOT runs on a logged in workstation as a application
- it does not operate as an NT/2000 service. It is advisable to
maintain a secure terminal for inGOT to run on and to maintain
a protected directory for the Access databases containing the inGOT
user account information. The paths to the directories may be located
through shares. |
