---

Subject:	Hi, I'm the community manager
Author:	Andrew Kirch
Posted:	2014-05-13 12:04

Hi, I'm the community manager at Zenoss. We have a KB article that might help but I haven't decided where to publish it yet. Would you please drop me an e-mail at community@zenoss.com and I will forward it to you.

Thanks!

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

---

Subject:	I had the same issue
Author:	[Not Specified]
Posted:	2014-05-16 22:05

I was connecting to two different windows servers with two different users. The issue was the auth ticket was being cached for the wrong user. I change the users to be the same for both servers and it resolved the issue once the ticket expired.

---

Subject:	Murigar, what did you end up
Author:	Jay Stanley
Posted:	2014-08-12 22:49

Murigar, what did you end up using

---

Subject:	Is this issue resolved ? As
Author:	[Not Specified]
Posted:	2014-12-17 00:57

Is this issue resolved As "migrating" to WINRM isn't playing in my favour:

2014-12-17 16:39:42,565 ERROR zen.PythonClient: Connection error on Win-01.Server.com: Connection reset by peer
2014-12-17 16:39:54,106 ERROR zen.PythonClient: Connection lost for Win-01.Server.com. Check if WinRM service listening on port 5985 is working correctly.
2014-12-17 16:39:54,201 ERROR zen.PythonClient: Query error on Win-01.Server.com: HTTP Unauthorized received on initial kerberos request. or check server WinRM settings
Please refer to txwinrm documentation at http://wiki.zenoss.org/ZenPack:Microsoft_Windows#winrm_setup
2014-12-17 16:39:54,478 ERROR zen.PythonClient: Query error on Win-01.Server.com: HTTP Unauthorized received on initial kerberos request. or check server WinRM settings
Please refer to txwinrm documentation at http://wiki.zenoss.org/ZenPack:Microsoft_Windows#winrm_setup
2014-12-17 16:39:54,485 ERROR zen.PythonClient: Query error on Win-01.Server.com: HTTP Unauthorized received on initial kerberos request. or check server WinRM settings
Please refer to txwinrm documentation at http://wiki.zenoss.org/ZenPack:Microsoft_Windows#winrm_setup
2014-12-17 16:39:54,491 ERROR zen.PythonClient: Query error on Win-01.Server.com: HTTP Unauthorized received on initial kerberos request. or check server WinRM settings
Please refer to txwinrm documentation at http://wiki.zenoss.org/ZenPack:Microsoft_Windows#winrm_setup
2014-12-17 16:40:14,659 ERROR zen.PythonClient: Query error on Win-01.Server.com: HTTP Unauthorized received on initial kerberos request. or check server WinRM settings
Please refer to txwinrm documentation at http://wiki.zenoss.org/ZenPack:Microsoft_Windows#winrm_setup
2014-12-17 16:40:14,670 ERROR zen.PythonClient: Query error on Win-01.Server.com: HTTP Unauthorized received on initial kerberos request. or check server WinRM settings
Please refer to txwinrm documentation at http://wiki.zenoss.org/ZenPack:Microsoft_Windows#winrm_setup
2014-12-17 16:40:14,682 ERROR zen.PythonClient: Query error on Win-01.Server.com: HTTP Unauthorized received on initial kerberos request. or check server WinRM settings
Please refer to txwinrm documentation at http://wiki.zenoss.org/ZenPack:Microsoft_Windows#winrm_setup
2014-12-17 16:40:14,685 WARNING zen.ZenModeler: Client Win-01.Server.com timeout

zWinRMPassword is set as per user "zenoss" created password within AD
zWinRMUser is set to "zenoss@Server.com"
zWinRMServerName is set to "Win-01.Server.com"
zWinKDC is set to "DC-01.Server.com"

User "Zenoss" has been made a member of the "WinRMRemoteWMIUsers_ "group within AD

Machine "Win-01.Server.com" 's WINRM settings:

C:\>winrm get winrm/config
Config
MaxEnvelopeSizekb = 500
MaxTimeoutms = 60000
MaxBatchItems = 32000
MaxProviderRequests = 4294967295
Client
NetworkDelayms = 5000
URLPrefix = wsman
AllowUnencrypted = false
Auth
Basic = true
Digest = true
Kerberos = true
Negotiate = true
Certificate = true
CredSSP = false
DefaultPorts
HTTP = 5985
HTTPS = 5986
TrustedHosts
Service
RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)(A;;GR;;;IU)S:P(AU;FA;GA;;;WD)(AU;SA;G
XGW;;;WD)
MaxConcurrentOperations = 4294967295
MaxConcurrentOperationsPerUser = 1500
EnumerationTimeoutms = 240000
MaxConnections = 300
MaxPacketRetrievalTimeSeconds = 120
AllowUnencrypted = true
Auth
Basic = true
Kerberos = true
Negotiate = true
Certificate = false
CredSSP = false
CbtHardeningLevel = Relaxed
DefaultPorts
HTTP = 5985
HTTPS = 5986
IPv4Filter = *
IPv6Filter = *
EnableCompatibilityHttpListener = false
EnableCompatibilityHttpsListener = false
CertificateThumbprint
AllowRemoteAccess = true
Winrs
AllowRemoteShellAccess = true
IdleTimeout = 7200000
MaxConcurrentUsers = 10
MaxShellRunTime = 2147483647
MaxProcessesPerShell = 25
MaxMemoryPerShellMB = 1024
MaxShellsPerUser = 30

What am I missing

---

Subject:	The KB article was published
Author:	Andrew Kirch
Posted:	2014-12-22 08:46

The KB article was published last week. I apologize for whatever reason this thread never made it in front of me again.
https://support.zenoss.com/ics/support/KBAnswer.aspquestionID=222
https://support.zenoss.com/ics/support/KBAnswer.aspquestionID=9
https://support.zenoss.com/ics/support/KBAnswer.aspquestionID=202

Additionally release 2.2 of the Windows ZP dropped last week. I suggest updating to it (at least in testing, and following the above linked references)

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

---

Subject:	Hi Andrew, I tried to follow
Author:	Joan
Posted:	2015-01-14 05:56

Hi Andrew, I tried to follow these links but they're returning a 404 (it seems as if there was an update on the support system)

---

Subject:	Almost all of this should be
Author:	Andrew Kirch
Posted:	2015-01-19 08:22

Almost all of this should be relevant to core, please note the windows articles.
https://support.zenoss.com/hc/en-us/categories/200152355-Resource-Manager

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

---

Subject:	Hate to revive an old thread,
Author:	R S
Posted:	2016-11-14 14:57

Hate to revive an old thread, however what is the fix for this"HTTP Unauthorized received on kerberos initialization"

---

Subject:	Please follow below guide.
Author:	[Not Specified]
Posted:	2016-11-17 00:56

Please follow below guide.

https://support.zenoss.com/hc/en-us/articles/202432249-How-To-Monitor-Windows-2012-2012-R2-2008R2-And-2003-Standard-Edition-Servers-With-The-Microsoft-Windows-Zenpack-Using-WinRM-

Thanks,

Kr!

---

Subject:	I've followed the guide, and
Author:	R S
Posted:	2016-11-23 15:19

I've followed the guide, and Windows 2008R2 boxes are working (sort of, see below). Windows 7 is the problem with this particular error regardless of what I do.

Windows 2008R2 - I can add and model/monitor devices fine with WinRM. Rebooting a server, it generates an alert when it boots back up "Unauthorized received on initial kerberos request". However, I can monitor and re model no problem. It only occurs on a reboot, I can clear the error and it will not come back unless I restart.

Windows 7 - Can't monitor it with WinRM, constantly getting errors "Unauthorized received on initial kerberos request" when attempting a model

---

Subject:	Just to update the situation
Author:	R S
Posted:	2016-11-25 11:39

Just to update the situation

Windows 2008R2 - I can add and model/monitor devices fine with WinRM. Rebooting a server, it generates an alert when it boots back up "Unauthorized received on initial kerberos request". However, I can monitor and re model no problem. It only occurs on a reboot, I can clear the error and it will not come back unless I restart

Seems to happen all the time when I reboot a monitored Windows 2008r2 hyper-v guest, and only sometimes when reboooting a monitoreda physical 2008R2 box

---

Subject:	1) When you reboot a device
Author:	[Not Specified]
Posted:	2016-11-28 17:44

1) When you reboot a device data sources will fail. So you will be getting those events. But events should close automatically once device is up and collection started once again.

Thanks,

Kr!