---

Subject:	I highly recommend reading
Author:	[Not Specified]
Posted:	2014-05-15 11:32

I highly recommend reading the wiki article for that ZenPack: http://wiki.zenoss.org/ZenPack:Microsoft_Windows

Hydruid

---

Subject:	I'm getting the same error
Author:	[Not Specified]
Posted:	2014-05-15 14:01

Zeara,

Were you able to sort that error out I've been up and down the wiki page for the ZenPack with no luck so far. Running Ubuntu 14.04 and Zenoss 4.2.5, fresh install of both. I used the script you wrote, Hydruid, and it seemed to install fine. Good work on the script.

2014-05-15 14:44:58,746 WARNING zen.PythonClient: Error in zenoss.winrm.FileSystems: attempted Windows connection to non-Windows device
2014-05-15 14:44:58,747 WARNING zen.PythonClient: Error in zenoss.winrm.Interfaces: attempted Windows connection to non-Windows device
2014-05-15 14:44:58,748 WARNING zen.PythonClient: Error in zenoss.winrm.OperatingSystem: attempted Windows connection to non-Windows device
2014-05-15 14:44:58,750 WARNING zen.PythonClient: Error in zenoss.winrm.Services: attempted Windows connection to non-Windows device

Thanks.

---

Subject:	I think I figured it out
Author:	[Not Specified]
Posted:	2014-05-15 14:28

The wiki page mentioned above says:

zWinRMServerName
This property should only be used in conjunction with domain authentication when the DNS PTR record for a monitored server's managed IP address does not resolve to the name by which the server is known in Active Directory. For example, if myserver1 is known as myserver1.ad.example.com by Active Directory and is being managed by IP address 192.51.100.21, but 192.51.100.21 resolves to www.example.com, you will have to set zWinRMServerName to myserver1.ad.example.com for domain authentication to work.

In our network reverse DNS is set up and functioning correctly, so I left the zWinRMServerName parameter blank, thinking it wasn't needed. But, when I filled it in the errors mentioned in my previous post went away. Any idea if there is something I don't have configured correctly elsewhere in Zenoss that would cause this behavior

---

Subject:	Scratch that
Author:	[Not Specified]
Posted:	2014-05-15 15:38

Apparently at the same time I added the name I also removed the modeler plugins that were causing that error. So, when I added the modeler plugins back to the device group the errors returned. Back to square one.

---

Subject:	What version of windows are
Author:	[Not Specified]
Posted:	2014-05-16 08:24

What version of windows are your server(s) running Also wouldn't hurt to take a look at this article: http://support.microsoft.com/kb/976918

Also try these commands and report back what it says:
sudo su zenoss
kinit user@domain.tld
kinit user@DOMAIN.TLD

Also even if your DNS is setup properly, try changing the servername and kdc entries to the IP address.

Hydruid

---

Subject:	We're running Server 2012
Author:	[Not Specified]
Posted:	2014-05-16 10:15

We're running Server 2012 (not R2). The kinit command worked when I used ALL CAPS, and klist shows a good ticket. I updated the device configuration properties so that zWinKDC was an IP and zWinRMServerName was an IP as well. I also set the zWinRMUser to user@OUR.DOMAIN (it was lowercase before). I enabled debug logging for the modeler and modeled the device. Here's the output. http://pastebin.com/5Mu7nUiU Could IPv6 be causing us some trouble (line 85 in the pastebin). IPv6 is disabled at the OS level and the interface doesn't show IPv6 enabled.

---

Subject:	After quite a bit more
Author:	[Not Specified]
Posted:	2014-05-16 14:38

After quite a bit more digging around, it appears that zPythonClass needs to be set to ZenPacks.zenoss.Microsoft.Windows.Device. After setting that (and remodeling), it appears to be working correctly now. It's able to discover and enumerate everything on each device as expected. One other thing to note is that it works successfully without zWinRMServerName set.

Thanks for your help on this. I appreciate it!

---

Subject:	That is good to know!
Author:	[Not Specified]
Posted:	2014-05-16 15:07

That is good to know!

Hydruid

---

Subject:	Thanks. What seemed to fix it
Author:	[Not Specified]
Posted:	2014-05-28 23:16

Thanks. What seemed to fix it for me was putty the domain name in Capitals.

---

Subject:	Modeling PDC # 3
Author:	[Not Specified]
Posted:	2015-05-21 12:48

I'm trying to model one of 3 domain controllers: This is the error.
2015-05-21 10:21:05,359 INFO zen.ZenModeler: Connecting to localhost:8789
2015-05-21 10:21:05,369 INFO zen.ZenModeler: Connected to ZenHub
2015-05-21 10:21:05,596 INFO zen.ZenModeler: Collecting for device ads-srv03.ad.wsd.edu
2015-05-21 10:21:05,809 INFO zen.ZenModeler: skipping WMI-based collection, PySamba zenpack not installed
2015-05-21 10:21:05,823 INFO zen.ZenModeler: Python collection device ads-srv03.ad.wsd.edu
2015-05-21 10:21:05,823 INFO zen.ZenModeler: plugins: zenoss.winrm.OperatingSystem, zenoss.winrm.FileSystems, zenoss.winrm.IIS, zenoss.winrm.CPUs, zenoss.winrm.Interfaces, zenoss.winrm.Processes, zenoss.winrm.Services, zenoss.winrm.Software
2015-05-21 10:21:05,829 WARNING zen.PythonClient: Error in zenoss.winrm.OperatingSystem: attempted Windows connection to non-Windows device
2015-05-21 10:21:05,834 WARNING zen.PythonClient: Error in zenoss.winrm.FileSystems: attempted Windows connection to non-Windows device
2015-05-21 10:21:05,839 WARNING zen.PythonClient: Error in zenoss.winrm.IIS: attempted Windows connection to non-Windows device
2015-05-21 10:21:05,844 WARNING zen.PythonClient: Error in zenoss.winrm.CPUs: attempted Windows connection to non-Windows device
2015-05-21 10:21:05,849 WARNING zen.PythonClient: Error in zenoss.winrm.Interfaces: attempted Windows connection to non-Windows device
2015-05-21 10:21:05,855 WARNING zen.PythonClient: Error in zenoss.winrm.Processes: attempted Windows connection to non-Windows device
2015-05-21 10:21:05,860 WARNING zen.PythonClient: Error in zenoss.winrm.Services: attempted Windows connection to non-Windows device
2015-05-21 10:21:05,865 WARNING zen.PythonClient: Error in zenoss.winrm.Software: attempted Windows connection to non-Windows device
2015-05-21 10:21:05,867 INFO zen.PythonClient: Python client finished collection for ads-srv03.ad.wsd.edu
2015-05-21 10:21:05,868 INFO zen.ZenModeler: No change in configuration detected
2015-05-21 10:21:05,869 INFO zen.ZenModeler: No command plugins found for ads-srv03.ad.wsd.edu
2015-05-21 10:21:05,870 INFO zen.ZenModeler: SNMP monitoring off for ads-srv03.ad.wsd.edu
2015-05-21 10:21:05,871 INFO zen.ZenModeler: No portscan plugins found for ads-srv03.ad.wsd.edu
2015-05-21 10:21:05,871 INFO zen.ZenModeler: Scan time: 0.28 seconds
2015-05-21 10:21:05,876 INFO zen.ZenModeler: Daemon ZenModeler shutting down

PySamba zenpack IS installed.

zWinKDC is set to the PDC IP Address
zWinRMPassword set to PDC password
zWinRMUser is set to PDC AdminUser administrator@AD.WSD.EDU
zWinRMServerName is set to ads-srv03.ad.wsd.edu

I thought I'd try to model PDC #3 before trying the other two. I can model all my other Windows servers without an issue but not the domain controller. What should I be looking for

---

Subject:	Mddantignac, this thread is a
Author:	Andrew Kirch
Posted:	2015-05-25 19:38

Mddantignac, this thread is a year old, please start a new thread.

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard