Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

winchute.exe and command line switches

winchute.exe and command line switches

winchute.exe and command line switches

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.

RE: winchute.exe and command line switches

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.

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

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.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close