Campus User Tracking LMS 2.6 User Name field is blank

Answered Question
Feb 19th, 2008
User Badges:

He Experts,

please explain me how to fill the User Name field in CUT. We using active directory to get the user names resolved.

Danke Gruss Steffen

Correct Answer by Joe Clarke about 9 years 5 months ago

The username field can be populated in one of three ways. Either your Windows hosts are running the UTLite process (see the User Tracking online help for more details on installing this), and they send periodic updates to CiscoWorks as to who is logged in on each end host. For your UNIX workstations, they need to be running rusersd, and UT will query each of the UNIX stations for the user logged in on the console. Finally, you can manually enter usernames, and they will persist.


In order for the first two methods to work, they must first be enabled under Campus Manager > Administration > User Tracking Admin > Acquisition. Then, as I said, you'll need to install UTLite on your Windows end hosts (really on the domain controller) and enable rusersd on your UNIX workstations, and UT should start showing you usernames after the next major acquisition.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Joe Clarke Tue, 02/19/2008 - 08:25
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

The username field can be populated in one of three ways. Either your Windows hosts are running the UTLite process (see the User Tracking online help for more details on installing this), and they send periodic updates to CiscoWorks as to who is logged in on each end host. For your UNIX workstations, they need to be running rusersd, and UT will query each of the UNIX stations for the user logged in on the console. Finally, you can manually enter usernames, and they will persist.


In order for the first two methods to work, they must first be enabled under Campus Manager > Administration > User Tracking Admin > Acquisition. Then, as I said, you'll need to install UTLite on your Windows end hosts (really on the domain controller) and enable rusersd on your UNIX workstations, and UT should start showing you usernames after the next major acquisition.

steffen.plorin Wed, 02/20/2008 - 22:35
User Badges:

He JClarke,


danke for your explanation. I got all what I need to discuss this implementation in our AD and PDC's

Gruss Steffen

srego4 Fri, 02/22/2008 - 08:22
User Badges:

I used to run utlite on all my wkstns when using LMS2.2. I notice that LMS 3.0 will not pick up the user info... guessing that LMS 3.0 has the file modified a bit ..right?


But from jclarke's post.. Is it possible to only have utlite (some version) of it running only on AD servers to get all the user info, or does it still need to be on the wkstns?

Joe Clarke Fri, 02/22/2008 - 08:42
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

UTLite is installed on the domain controllers, but always runs on the individual client machines. Yes, UTLite has changed quite a bit in LMS 3.0. The same UTLite33.exe executable from LMS 2.2 COULD be used, but we have fixed quite a few bugs in it, so you really should upgrade to the one that comes with the installed version of Campus Manager.


As for not seeing users with UTLite in LMS 3.0, there have been a few bugs about this. Upgrading to LMS 3.0.1 will get you over some of them, but others may still exist. One thing I have seen is that the end user database entries get tagged with the wrong DB ID. This will keep UTLite from matching MACs to usernames. The way to fix this is to purge all of the UT entries with:


NMSROOT/campus/bin/reinitdb.pl -ut

Actions

This Discussion