winchute.exe and command line switches

[drdos]

When running winchute.exe to monitor UPS on host server over a Novell network, it polls all servers in tree, a lengthy process over two hours. Is there away to force it to look at only your host server.

 

[drdos]

I found this out on my own:
============================
Technical Description
PowerChute plus 4.3x is our first version that does not use bindery,
however 4.3, 4.31, 4.32 is not a practical application for some
enterprise customers because it is not possible to monitor one
server at a time or limit the amount of servers, as it will always
do a full search of the entire NDS tree. This search is impractical
for a enterprise customer with a large WAN, as it is very time
consuming and sometimes it is never completed.

Solution:
PowerChute plus4.33 will fix this problem.

How to implement Fix through Pwrchute.ini:

Find the NDS section of the Pwrchute.ini. The default value [Root]
for this parameter causes PowerChute plus
to search the entire NDS tree.

If no context is specified (SearchContext= ), PowerChute plus
searches your default context (the context you are logged into). For
example, if you have admin privileges to manage only the UPSs for
your branch office, and that branch office is defined as a separate
NDS context, you can let PowerChute plus search your default context
to dis-play only those UPSs you are responsible for managing.

If you explicitly specify an NDS context to search (such as
SearchContext=branch1.company), do not use brackets to enclose the
parameter value. Brackets are required only for the default context
[Root].

If an invalid context is specified, PowerChute plus displays a
dialog box indicating which context it attempted to search and also
logs the error in the pwrchute.err file.

Any changes made to the [NDS]section will not take effect until you
unload and reload the Pwrchute.nlm.
[NDS]
===============================

[sig][/sig]