Zenoss ZenTech Community

I have 4.2.5 installed and I have configured winRM for my windows machines. I am running on centos 6 and I have the following options set:

zwinscheme = https
zWinRMUSer = user@domain.local
zWinRMPassword = ***
zWinKDC = dc (ip address)

This is what I see when I model the device:
2014-04-30 13:23:30,464 ERROR zen.PythonClient: Error on 192.168.1.240: kerberos authGSSClientStep failed (None).
2014-04-30 13:23:30,492 ERROR zen.PythonClient: Error on 192.168.1.240: kerberos authGSSClientStep failed (None).
2014-04-30 13:23:30,601 ERROR zen.PythonClient: Error on 192.168.1.240: kerberos authGSSClientStep failed (None).
2014-04-30 13:23:30,633 ERROR zen.PythonClient: Error on 192.168.1.240: kerberos authGSSClientStep failed (None).
2014-04-30 13:23:30,648 ERROR zen.PythonClient: Error on 192.168.1.240: kerberos authGSSClientStep failed (None).
2014-04-30 13:23:30,696 ERROR zen.PythonClient: Error on 192.168.1.240: kerberos authGSSClientStep failed (None).
2014-04-30 13:23:30,713 ERROR zen.PythonClient: Error on 192.168.1.240: kerberos authGSSClientStep failed (None).
2014-04-30 13:23:30,727 ERROR zen.PythonClient: Error on 192.168.1.240: kerberos authGSSClientStep failed (None).
2014-04-30 13:23:31,045 ERROR zen.PythonClient: Error on 192.168.1.240: kerberos authGSSClientStep failed (None).
2014-04-30 13:23:31,218 ERROR zen.PythonClient: Error on 192.168.1.240: kerberos authGSSClientStep failed (None).
2014-04-30 13:23:31,218 INFO zen.PythonClient: Python client finished collection for 192.168.1.240
2014-04-30 13:23:31,218 WARNING zen.ZenModeler: The plugin zenoss.winrm.OperatingSystem returned no results.
2014-04-30 13:23:31,218 WARNING zen.ZenModeler: The plugin zenoss.winrm.Processes returned no results.
2014-04-30 13:23:31,219 WARNING zen.ZenModeler: The plugin zenoss.winrm.Services returned no results.
2014-04-30 13:23:31,219 WARNING zen.ZenModeler: The plugin zenoss.winrm.FileSystems returned no results.
2014-04-30 13:23:31,219 WARNING zen.ZenModeler: The plugin zenoss.winrm.CPUs returned no results.
2014-04-30 13:23:31,219 WARNING zen.ZenModeler: The plugin zenoss.winrm.Software returned no results.
2014-04-30 13:23:31,219 WARNING zen.ZenModeler: The plugin zenoss.winrm.IIS returned no results.
2014-04-30 13:23:31,219 WARNING zen.ZenModeler: The plugin zenoss.winrm.Interfaces returned no results.

Subject:	If you didn't generate a
Author:	[Not Specified]
Posted:	2014-04-30 13:55

If you didn't generate a certificate you should be using HTTP instead of HTTPS

Hydruid

Subject:	Also the username has to
Author:	[Not Specified]
Posted:	2014-04-30 13:56

Also the username has to match how the realm is configured, mine for example is Administrator@HYDRUID.LOCAL

Hydruid

Subject:	I didn't generate a cert, so
Author:	[Not Specified]
Posted:	2014-04-30 14:21

I didn't generate a cert, so if I set it to http I get "Check WinRM AllowUnencrypted is set to true". If I go to the windows server and allow unencrypted, it works. My understanding of windowsRM is that it defaults to http. Is that not the case

Subject:	Yes it most definitely
Author:	[Not Specified]
Posted:	2014-04-30 14:41

Yes it most definitely defaults to HTTP but in your original post you said you had selected HTTPS in the zenoss config.

To get HTTPS working you have to generate a "Server Auth" Cert!

Hydruid

Subject:	But if I set it to http, then
Author:	[Not Specified]
Posted:	2014-04-30 14:43

But if I set it to http, then I get this error:

"Check WinRM AllowUnencrypted is set to true"

Subject:	That is correct, using HTTP
Author:	[Not Specified]
Posted:	2014-04-30 14:47

That is correct, using HTTP the trafic will be Unencrypted.

This is the command to allow it: winrm s winrm/config/service @{AllowUnencrypted="true"}

All of that is covered on the wiki article: http://wiki.zenoss.org/ZenPack:Microsoft_Windows

Hydruid

Subject:	Thanks for the confirmation
Author:	[Not Specified]
Posted:	2014-04-30 14:58

Thanks for the confirmation and clarification.

Subject:	WinRM is a very interesting
Author:	[Not Specified]
Posted:	2014-04-30 15:09

WinRM is a very interesting path for Microsoft to take, it can be a real pain in the rear ;)

Hydruid

Subject:	MikeC79: Was your issue
Author:	openavenzer
Posted:	2014-06-14 10:29

MikeC79: Was your issue resolved. I am still having the same issue !

Subject:	Hi All
Author:	openavenzer
Posted:	2014-06-14 11:40

My issue got resolved after adding DC name for zWinKDC, thanks

Subject:	None of this works for me even when I did the same
Author:	[Not Specified]
Posted:	2014-06-17 17:10

All my settings are basically the same....And the messed up part is that it worked 3 weeks for testing...

Subject:	4.2.5 - winRM - kerberos authGSSClientStep failed
Author:	[Not Specified]
Posted:	2014-04-30 13:41

4.2.5 - winRM - kerberos authGSSClientStep failed