Demo only for one server in the tree.
home page url:
UserKVYMonitor is an analyzer of user activity on a NetWare server. Only by using this program you can know who of your users has loaded the server.
UserKVYMonitor scans user connections on the NetWare server and collects the following information:
- The full list of users logged on the server.
- Connection numbers of these users.
- Their login time.
- How many bytes each user has read from the server after login and start of the program.
- How many bytes each user has written to the server after login and start of the program.
- How many requests each user has made on the server after login and start of the program.
- How many files each user created on volumes of the server.
- User's total time in the network after login.
Using this program you also can fulfill the following operations:
- Select servers for review.
- Disable/enable login on the server.
- Refresh information in the main window.
- Get the full list of all opened files on the server.
- Get the list of open files for each user.
- Search files by their types.
- Get information from NDS for a wanted user.
- Send a message to any user you want.
- Clear a user connection on the server.
- Set time for automatic poll of information from the server.
- Get information about server's work (the general information from the
Console Monitor utility).
- Save all information to a HTML file.
- Ping workstations and servers by IP or IPX.
- Remote management of workstations via Novell ZENworks Remote Management Agent.
- Review the current Console.log.
- Control NLM on the server.
- Execute a NCF file on the server.
- Run a network utility on your workstation.
- Purge all deleted files on the server volumes.
- Collect and save info (session statistics) about users, which logged out of the server.
The full information about the program and its new features is placed: http://www.kvy.com.ua.
Click to view.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.