Zenoss ZenTech Community

Subject:	RE: ZenOSS Core 6.2 unable to model Windows devices
Author:	Jay Stanley
Posted:	2019-06-07 08:15

You must have the device within the Server/Microsoft/Windows device class or in a device class that has the zPythonClass set to 'ZenPacks.zenoss.Microsoft.Windows.Device'

------------------------------
jstanley
------------------------------

Subject:	RE: ZenOSS Core 6.2 unable to model Windows devices
Author:	J K
Posted:	2019-06-10 03:50

Thanks for that Jay. I moved the lot of the servers and most of the devices modeled ok but I've got one that has a reverse DNS record which is something.domain.com instead of just hostname.domain.com so it errors out:

Server not found in Kerberos database: Attempted to get ticket for HTTP@something.domain.com. Ensure reverse DNS is correct.

I have already set the winRMkrb5DisableRDNS to true at the /Server/Microsoft/Windows level and the result is still the same even after remodel.

Also how do I get it to pull event logs?

------------------------------
J K
------------------------------

Subject:	RE: ZenOSS Core 6.2 unable to model Windows devices
Author:	Jay Stanley
Posted:	2019-06-10 11:53

Make sure there is a SPN (In Windows AD) set for the name you are trying to use

------------------------------
jstanley
------------------------------

Subject:	RE: ZenOSS Core 6.2 unable to model Windows devices
Author:	J K
Posted:	2019-06-11 12:00

The SPNs are set correctly when checked with setspn. I tried to delete and readd the device but it resulted in the same error.

Is there anything I need to reset?

------------------------------
J K
------------------------------

Subject:	RE: ZenOSS Core 6.2 unable to model Windows devices
Author:	Jay Stanley
Posted:	2019-06-11 14:26

Make sure your zWinRMServerName is set.

I use ${here/titleOrId} and then make sure the device title is set to the FQDN.

------------------------------
jstanley
------------------------------

Subject:	RE: ZenOSS Core 6.2 unable to model Windows devices
Author:	J K
Posted:	2019-06-12 10:46

That is in fact what I'm using and the device title is FQDN. Is there a command I can run similar to snmpwalk that will help me get a more verbose output of this step? I am suspecting some cached entry is persisting but I'm not sure how to connect and check the kerberos cache. I'm not sure which docker instance I need to attach to check this.

EDIT: It started working without any modification - it seems like the ticket expired. Would be useful to know how to clean it out for future reference.

The only item I've got left is the need to pull the eventlogs. How can I accomplish that?

------------------------------
J K
------------------------------

2019-06-07 11:10:46,832 INFO zen.ZenModeler: plugins: zenoss.winrm.CPUs, zenoss.winrm.FileSystems, zenoss.winrm.HardDisks, zenoss.winrm.Interfaces, zenoss.winrm.OperatingSystem, zenoss.winrm.Processes, zenoss.winrm.Routes, zenoss.winrm.Services, zenoss.winrm.Software

2019-06-07 11:10:46,832 ERROR zen.PythonClient: Error in zenoss.winrm.CPUs: attempted Windows connection to non-Windows device

2019-06-07 11:10:46,833 ERROR zen.PythonClient: Error in zenoss.winrm.FileSystems: attempted Windows connection to non-Windows device

2019-06-07 11:10:46,833 ERROR zen.PythonClient: Error in zenoss.winrm.HardDisks: attempted Windows connection to non-Windows device

2019-06-07 11:10:46,834 ERROR zen.PythonClient: Error in zenoss.winrm.Interfaces: attempted Windows connection to non-Windows device

2019-06-07 11:10:46,834 ERROR zen.PythonClient: Error in zenoss.winrm.OperatingSystem: attempted Windows connection to non-Windows device

2019-06-07 11:10:46,838 ERROR zen.PythonClient: Error in zenoss.winrm.Processes: attempted Windows connection to non-Windows device

2019-06-07 11:10:46,838 ERROR zen.PythonClient: Error in zenoss.winrm.Routes: attempted Windows connection to non-Windows device

2019-06-07 11:10:46,839 ERROR zen.PythonClient: Error in zenoss.winrm.Services: attempted Windows connection to non-Windows device

2019-06-07 11:10:46,839 ERROR zen.PythonClient: Error in zenoss.winrm.Software: attempted Windows connection to non-Windows device

The log shows only this:
Error on 10.175.24.17: attempted Windows connection to non-Windows device

Subject:	RE: ZenOSS Core 6.2 unable to model Windows devices
Author:	Jay Stanley
Posted:	2019-06-18 09:59

I think there is a kinit command that can be ran.. but I just restart zenpython container and it wipes out the cache.

------------------------------
jstanley
------------------------------

Subject:	ZenOSS Core 6.2 unable to model Windows devices
Author:	J K
Posted:	2019-06-07 07:12

ZenOSS Core 6.2 unable to model Windows devices