---

Subject:	Just to add error: its
Author:	[Not Specified]
Posted:	2016-06-30 10:47

Just to add error: its showing "ERROR zen.PythonClient: Timeout on xx.xx.xx.xx: Verify WinRM and firewall setup "

andkrb5workstation has been installed.

---

Subject:	Is port 5985 open between
Author:	[Not Specified]
Posted:	2016-06-30 12:49

Is port 5985 open between your server and Zenoss

---

Subject:	yes, there is no firewall
Author:	[Not Specified]
Posted:	2016-06-30 13:10

yes, there is no firewall block in between and port 5985 is allowed

---

Subject:	Hi Jane,
Author:	[Not Specified]
Posted:	2016-07-01 03:21

Hi Jane,

The Link which you provided is not working, Could you please provide the other

---

Subject:	There is a good document here
Author:	Jane Curry
Posted:	2016-07-10 05:40

There is a good document here with some detailed instructions - https://support.zenoss.com/hc/en- us/article_attachments/200942039/202_monitor_win_svr_w_winrm_windows_zenpack_10 172014b_RevD.pdf

NB NB NB - just checked this link and it appears correct but doesn't work. The link below is to the zenoss support page - follow the link to the pdf doc - that works this morning (July 10th, 2016).

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-

For the scenario where authentication to Windows devices is through an AD domain controller, yoiu need to modify one parameter from the above document so that you do NOT use basic authentication. Parameters I have used on a test target Windows system are:

winrm quickconfig

winrm s winrm/config/service '@{AllowUnencrypted="true"}'
winrm s winrm/config/service '@{MaxConcurrentOperationsPerUser="4294967295"}'
winrm s winrm/config/winrs '@{MaxShellsPerUser="2147483647"}'
winrm s winrm/config/winrs '@{IdleTimeout="7200000"}'
winrm s winrm/config/service/auth '@{Basic="false"}'

You do NOT need to do any certificate copying with these parameters.

The ZenPacks.zenoss.Microsoft.Windows ZenPack should have created /Server/Microsoft/Windows.

Modify zProperties for this device class so, assuming on your test Windows you have a user mytest in domain mydomain with password mypassword:

zWinRMUser mytest@mydomain
zWinRMPassword mypassword
zWinKDC IP address of the domain controller
zWinScheme http

You should NOT set zWinRMServerName unless your DNS cannot resolve the name of the target (both forward and reverse). See the document referenced above.

Prerequisites on the Zenoss server are the PythonCollector ZenPack and krb5workstation.

Cheers,

Jane

Email: jane.curry@skills-1st.co.uk    Web: https://www.skills-1st.co.uk