Hopefully someone can help me out. I am using the W32 - TerminalService Sessions data template with SNMP and I am not receiving any values in my graph.
There are constant people logged into the machine so I nkow it should be returning the number of sessions > 0.
Thanks for your help in advance.
W32 - TerminalService Sessions (No Values)
Moderators: Developers, Moderators
what happens when you manually run the script?
If it works then and not with Cacti, then you have a security problem. Read the FAQ section in the guide in my signature relating to WMI.
If it works then and not with Cacti, then you have a security problem. Read the FAQ section in the guide in my signature relating to WMI.
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
Ok I have run the script manually and it works fine. Still not seeing any appearances in the graph though.
The Server running Cacti is a WIN2k3 Server. The Server I am trying to poll is a Win2k Server.
I followed the instructions in your FAQ but they seem to be referring to a WIN2k3 system for the dcom settings. All other settings I have managed to find, Just these dcom settings seem to be stopping me now. Do you have any advice on how to set this for Win2k servers?
Cheers
The Server running Cacti is a WIN2k3 Server. The Server I am trying to poll is a Win2k Server.
I followed the instructions in your FAQ but they seem to be referring to a WIN2k3 system for the dcom settings. All other settings I have managed to find, Just these dcom settings seem to be stopping me now. Do you have any advice on how to set this for Win2k servers?
Cheers
I don't have a Win2K server (nor do i have the time to set one up in VMware) to look at how the dcom/wmi security settings differ from the FAQ. I could possible remote to your computer some evening and take a look.
The quick (and unsafe) fix is to add the user running your cacti scheduled task to the admin group on the win2k box which the script does not work on (under cacti).
The quick (and unsafe) fix is to add the user running your cacti scheduled task to the admin group on the win2k box which the script does not work on (under cacti).
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
Who is online
Users browsing this forum: No registered users and 0 guests