UTLite is a utility that allows you to collect usernames from Active
Directory, primary domain controllers, and Novell servers. UTLite sends traps
to CiscoWorks Campus Manager whenever a user logs in or logs out. These
usernames will show up in the user tracking reports of Campus Manager, along
with other information of the end station such as the MAC address, hostname, IP
address, and so forth.
In order to enable network services to collect username information
from a Windows NT/2000 Primary Domain Controller (PDC) or Novell Directory
Services (NDS) server, you must:
Install the UTLite script on the appropriate servers
Configure the CiscoWorks server with correct preferences
This document details how to install the UTLite script on Windows NT
PDC servers. You must install the UTLite script on the Windows NT PDC and
update the domain controller logon script to get user logon information from NT
hosts. To install the UTLite script on Novell Servers, refer to the Online Help
of your CiscoWorks Server.
Note: This procedure is also available in of your CiscoWorks Server Online
Help. You can accessed it from your web browser using this URL:
CampusManager 3.3 and earlier versions
for CampusManager 4.0 and later versions
You must have Windows NT Administrator privileges on the primary domain
controller to install the UTLite logon script.
This document is not restricted to specific software and hardware
The UTLite script is supported on these platforms:
The UTLite script is not supported on these UNIX hosts:
In order to automatically retrieve user login names from a UNIX host,
rusersd must be enabled on the host. This is enabled
by default on Solaris and AIX hosts, but not on HP-UX hosts. You can enable
rusersd by updating the
/etc/inetd.conf or /etc/inet/inetd.conf file
on the host.
For more information on document conventions, see the
Technical Tips Conventions.
Follow these steps to install the UTLite script.
Copy the required files to the primary NT domain controller:
Log into the NT primary domain controller as Administrator.
Obtain the UTLite files from the CiscoWorks Server, where
C:\Program Files\ is the directory where you installed
Copy the UTLiteNT.bat and
UTLite.exe files into the NETLOGON folder. NETLOGON is located
in: %SYSTEMROOT%\system32\Repl\Import\Scripts, where
%SYSTEMROOT% is the root directory for the Windows NT operating system files.
To quickly locate this directory, enter set windir
or set systemroot from a command prompt window.
Note: In Campus Manager 3.3 and later versions, the UTLite files are
located at C:\Program Files\CSCOpx\campus\bin\. Also the
UTLite.exe file changes to UTLite33.exe. If
you have upgraded to CM 3.3 from previous version, the old logon scripts should
be replaced by new UTLiteNT.bat pointing to
Edit the UTLiteNT.bat file:
Open the UTLiteNT.bat file.
Locate this line and replace and with the domain name of the NT
domain controller and IP address of the computer running CiscoWorks Server:
start %WINDIR%\UTLite -domain <domain> -host <IP address> -port 16236
Note: If port 16236 is in use, enter a different number. This port
number must match the number entered in the User and Host Acquisition dialog
box, located on the CiscoWorks desktop under Setup>ANI Server
Admin>User and Host Acquisition in the Server Configuration drawer.
Edit the logon scripts:
Edit users' logon script files to run the
UTLiteNT.bat file when users log into the network by adding
Update the domain controller logon script for each NT domain that
Note: The first time users log into the network after you edit this
script, UTLite.exe is copied to the local WINDIR directory on
the Windows client system.
You specify the CiscoWorks server when you run your UTLite script. User
Tracking in Campus Manager gets the data from NT PDC.
When tracking Windows 95, Windows NT, and Windows 2000 users in
UserTracking, UTLite.exe is sometimes sending an empty
username. This is a known bug
(registered customers only)
found in Campus Manager 3.1 and is
resolved in Campus Manager 3.3.
UTLite script does not work for Windows 98 clients (CSCdw44519
(registered customers only)
) if you are using Campus Manager 3.1.
This bug is fixed in Campus Manager 3.3.