---

Subject:	I've forwarded this thread to
Author:	Andrew Kirch
Posted:	2015-12-30 12:08

I've forwarded this thread to one of our solutions engineers who works on the Windows ZenPack.

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:	Error
Author:	Dave Bouchillon
Posted:	2016-01-04 10:02

Are you still experiencing an issue with this

If so, can you reinstall the ZenPack and restart Zenoss We have not seen this issue.

Thanks

Dave

---

Subject:	Yes, still seeing the issue.
Author:	[Not Specified]
Posted:	2016-01-06 12:55

Yes, still seeing the issue. I've reloaded the ZenPack and restarted Zenoss and still seeing it.

---

Subject:	Do you have zWinKDC set to a
Author:	[Not Specified]
Posted:	2016-01-07 14:41

Do you have zWinKDC set to a domain controller FQDN

---

Subject:	odd
Author:	Dave Bouchillon
Posted:	2016-01-07 14:55

The only way you would see this is if your txwinrm library is out of date. I wouldn't think this is possible as it is part of the ZenPack. Did you install the txwinrm package separately

---

Subject:	Mdiorio,
Author:	[Not Specified]
Posted:	2016-01-08 09:55

Mdiorio,

I do have the zWinKDC set to a FQDN of a domain controller. zWinRDC, zWinRMPassowrd, and zWinRMUser are all set the way they were working in previous versions.

Dbouchillon,

I don't see any reason why I would have installed the txwinrm package separately. I've only followed the install instructions online. How would I go about checking the version

---

Subject:	txwinrm
Author:	Dave Bouchillon
Posted:	2016-01-08 10:49

This wouldn't be a z property problem. This is a python error that is occurring because of an out of date txwinrm library. The txwinrm library is part of the ZenPack egg.

You can verify it is using the correct version through zendmd. You should see something like the following:

>>> import txwinrm

>>> txwinrm.__path__

['/opt/zenoss/ZenPacks/ZenPacks.zenoss.Microsoft.Windows-2.5.5-py2.7.egg/ZenPacks/zenoss/Microsoft/Windows/lib/txwinrm']

Can you post the results of checking the path

What version of Zenoss are you running

---

Subject:	['/opt/zenoss/lib/python2.7
Author:	[Not Specified]
Posted:	2016-01-08 14:27

['/opt/zenoss/lib/python2.7/site-packages/txwinrm-1.1.10-py2.7.egg/txwinrm'] is what I get. Running Zenoss Core 4.2.5

---

Subject:	remove txwinrm
Author:	Dave Bouchillon
Posted:	2016-01-08 14:41

Ok, there's the problem. Somehow that old egg was installed into your instance. You'll need to remove that egg and to be sure, resinstall the Windows ZenPack.

1) rm -rf /opt/zenoss/lib/python2.7/site-packages/txwinrm-1.1.10-py2.7.egg

2) remove txwinrm line from /opt/zenoss/lib/python2.7/site-packages/easy_install.pth

3) reinstallZenPacks.zenoss.Microsoft.Windows-2.5.5-py2.7.egg

4) restart Zenoss

---

Subject:	I didn't have a file named "
Author:	[Not Specified]
Posted:	2016-01-08 14:47

I didn't have a file named "/opt/zenoss/lib/python2.7/site-packages/easy_install.pth". That being said the first command followed by reinstalling the ZenPack seems to have resolved the issue. Now the path I'm seeing is "['/opt/zenoss/ZenPacks/ZenPacks.zenoss.Microsoft.Windows-2.5.5.egg/ZenPacks/zenoss/Microsoft/Windows/lib/txwinrm']"

It seems to be working fine now, thanks for your help! (This was all on my test server before I push the update to our production monitor.)

---

Subject:	fantastic!
Author:	Dave Bouchillon
Posted:	2016-01-08 14:49

Fantastic! Glad to help.