ConsoleOne

To manage a Novell / NDS infrastructure, you need management tools such as ConsoleOne or iManager, configured with the appropriate snap-ins and defaults.

As with Client-32, maintaining such a collection of snap-ins can be a tiresome and never-ending process. ITD Microsystems maintains a version of ConsoleOne for their own use and makes it available to others as a service to other groups on campus.

Note that you do need Client-32 installed to use ConsoleOne on a Windows Workstation!

Running from the Server

For occasional ConsoleOne use, you may find it sufficient to create a shortcut to

\\itd_apps_server\apps\ITD\ConsoleOne\1.2\bin\ConsoleOne.exe

This usually can also be accessed as L:\ITD\ConsoleOne\1.2\bin\ConsoleOne.exe

For all but the most casual of use, the performance of running ConsoleOne in this manner may prove insufficient.

Manual Copy from the Server for performance

If you copy all of the files rooted at \\itd_apps_server\apps\itd\ConsoleOne\1.2 to your local hard drive, you will see a significant performance improvement. Further improvements can be had by executing run.bat in place of ConsoleOne.exe . The run.bat file tells java to use more memory, which improves performance.

Versions

At the time this document was last updated, the version of Console One installed on itd_apps_server was:

ConsoleOne: 1.3.6f
Cluster Services snapin: 1.7
NDS Snapin: 1.2d
Zenworks Snapin: 7.0.0

 

About Microsys | Accessibility in our Services | Feedback | Microsys RSS Feeds | January 4, 2007