to remove zenwin run the *svc.py files with the parameter remove then
remove the directory. We have a documentation person starting next
week so better documentation will begin coming soon for all parts of
the system.
-EAD
On Aug 29, 2006, at 9:18 AM, Marshall Shelton wrote:
Yes, I've verified those settings and they are correct.
I actually switched to an accout that was a domain admin as apposed
to the domain administrator account, the collection appears to work
but I now get heartbeat failure alerts in the event log. The
services are running on the windows box using the new credentials
but don't really report anything. Example, I tell Zenoss to monitor
a particular win service on the zenwin box, I then stop the service
and zenoss goes on reporting that it is up hours later. I am trying
to get the zenwin component running on another host using an
account that has local priv and domain admin rights but get the
errors saying that the user credentials cannot be used for local
connections and it appears that the whole thing is mucked up now :(
I guess I have 2 questions;
1) How would I completely remove any trace of zenwin from my Zenoss
system w/o completely deleting and rebuilding it.
2) Are there plans to have some better zenwin documentation or if
it exists, can you point me to it.
Thanks,
MS
Erik A. Dahl wrote:
Marshall,
How did you specify the username in zWinUser? domain\Administrator
or something like that? It should be defined on /Server/Windows
in the zProperties tab. If it works for the local box but not
remote I'm guessing that the value is currently blank... That said
it might be something else (like boxes are in different domain)?
You might also try creating a local account with admin privileges.
-EAD
On Aug 10, 2006, at 3:52 PM, Marshall Shelton wrote:
Ok, still having limited success with this.
Mainly I'm just getting Win Services information for the server
the Zenwin app is running on.
Trying to run the scripts from command line on that box gives me
permission errors on other windows servers even though I am
running them as the domain administrator and have opened WMI wide
open on all the other windows servers (does windows work any
other way :) ?).
Is there any further documentation on this other than the readme
file in the Zenwin dist?
Erik A. Dahl wrote:
You need to define the login information for your other boxes in
the zProperties page under /Devices. The properties are
zWinPassword and zWinUser. Remember that zProperties can be
defined at any level of the Device Tree event down to a
particular device. There is a complete list of zProperties at
the end of the AdminGuide.
-EAD
On Aug 8, 2006, at 3:56 PM, Marshall Shelton wrote:
Gotcha. pretty slick.
I'm getting windows service info on the box I installed zenwin on.
One last question, how do I then reconfigure existing defined
windows servers to use the zenwin app interface?
Eric Newton wrote:
That's right. You only need one windows device (real or
virtual) collecting for all the windows devices.
-Eric
Marshall Shelton wrote:
I'm setting up Zenwin on a test box and I'm a little confused
and am getting some errors.
I have Python and pywin all setup on my windows box and have
edited the cfg files changing them to my Zenoss server and
it's admin username and password. I run the forst 2 progams
(zenwin.py and zeneventlog.py) in the foreground and they bot
appear to exit w/o error, however when I run
zenwinmodelersvc.py it looks like collects information from
the local system but then moves on to try and collect
information from other windows servers I have defined in
Zenoss, which it does not have rights to and procedes to
error out.
I guess I may not be completely understanding the arch of the
zenwin programs, are they just supposed to be collecting data
for the system that they are on or all defined Zenoss windows
systems. If it's the latter then I assume you only need one
windows box running zenwin to collect information on all
other windows servers it has rights to?
Please advise, Thanks,
Marshall
_______________________________________________
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
Erik A. Dahl wrote:
Marshall,
How did you specify the username in zWinUser? domain\Administrator
or something like that? It should be defined on /Server/Windows
in the zProperties tab. If it works for the local box but not
remote I'm guessing that the value is currently blank... That said
it might be something else (like boxes are in different domain)?
You might also try creating a local account with admin privileges.
-EAD
On Aug 10, 2006, at 3:52 PM, Marshall Shelton wrote:
Ok, still having limited success with this.
Mainly I'm just getting Win Services information for the server
the Zenwin app is running on.
Trying to run the scripts from command line on that box gives me
permission errors on other windows servers even though I am
running them as the domain administrator and have opened WMI wide
open on all the other windows servers (does windows work any
other way :) ?).
Is there any further documentation on this other than the readme
file in the Zenwin dist?
Erik A. Dahl wrote:
You need to define the login information for your other boxes in
the zProperties page under /Devices. The properties are
zWinPassword and zWinUser. Remember that zProperties can be
defined at any level of the Device Tree event down to a
particular device. There is a complete list of zProperties at
the end of the AdminGuide.
-EAD
On Aug 8, 2006, at 3:56 PM, Marshall Shelton wrote:
Gotcha. pretty slick.
I'm getting windows service info on the box I installed zenwin on.
One last question, how do I then reconfigure existing defined
windows servers to use the zenwin app interface?
Eric Newton wrote:
That's right. You only need one windows device (real or
virtual) collecting for all the windows devices.
-Eric
Marshall Shelton wrote:
I'm setting up Zenwin on a test box and I'm a little confused
and am getting some errors.
I have Python and pywin all setup on my windows box and have
edited the cfg files changing them to my Zenoss server and
it's admin username and password. I run the forst 2 progams
(zenwin.py and zeneventlog.py) in the foreground and they bot
appear to exit w/o error, however when I run
zenwinmodelersvc.py it looks like collects information from
the local system but then moves on to try and collect
information from other windows servers I have defined in
Zenoss, which it does not have rights to and procedes to
error out.
I guess I may not be completely understanding the arch of the
zenwin programs, are they just supposed to be collecting data
for the system that they are on or all defined Zenoss windows
systems. If it's the latter then I assume you only need one
windows box running zenwin to collect information on all
other windows servers it has rights to?
Please advise, Thanks,
Marshall
_______________________________________________
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
