I've got over 40 different VPNs running to various client networks, each fully tunneled and routed, as if they were just local LAN segments.  In those 40+ nets, I've got anywhere from 1 to 30 servers that I monitor, and have literally hundreds of WMI disk free space checks to alert when they drop below various thresholds.

On several systems (half dozen or so), I cannot retrieve the Logical Disk Counters via WUG.  Other counters show up, just not logical.  I've also verified that the logical counters are AVAILABLE from another server that is a member of that Active Directory Domain, just NOT thru WUG.  Typically, I specify in the WMI active monitor the system by IP address, but I've also created a local hosts file to place a flat netbios name, as well as having a fully meshed DNS selective forwarding--I can resolve the names with a variety of methods.  Very wierd.  I think it has something perhaps to do with a Kerberos based connection vs. Lanman style authentication.  WUG certainly isn't doing Kerberos.  Oddly, if I preset a STORED USERNAME and PASSWORD, and use PERFORMANCE LOGS and ALERTS and create a new Performance log, I CAN retrieve the logical disk counters with LOGs, but not live Perfmon.

The machines in question, if memory serves me, all are Exchange 2003 servers.  Additional notes, SQL is also typically on them, usually in the form of MSDE for Backup Exec.  I was thinking that maybe Exchange or SQL modified/replaced the Logical Disk\% Free Disk Space counter with one of their own, but I don't see them in the list.  Since logical disk is available to a domain member, the counter IS there, and available. 

Starting to wonder about the 'Exchange' monitors built into WUG 11a PRO...  There's a default Exchange value of 50mb free space monitoring, which also fails. I'm about to call Ipswitch support on this--it's been a problem for over a year, and tonight I spent another 4 hours attempting to isolate, no luck yet.

Bob

Wmi is some typical Microsoftish stuff : add layers and layers and layers of complexity hoping that it will appear to make a (somewhat complicated) thing simpler. GET RID OF IT AS MUCH AS YOU CAN !!! (There are places where you can't because Snmp does not expose the info you want; but they are few).

That said;

1/ Have you tried, FROM THE PERFMON ON THE WUG SERVER, to reach this counter ? (Not clear to me if you did or not).

2/ WUG DOES use Kerberos for authentication (just put a wrong password in your credentials, try to access a box, and look at the event log on the remote box; you'll see Kerberos auth failures). But, if Kerberos was failing, you prolly would not get *ANY* counter at all. Just in case it's useful, I enclose a doc I wrote some time ago talking about all of this; maybe it's useful to you.

Reading, writing and arithmetic - If you need to choose, please take option 1.

I had similar problems on Windows Server 2003 with missing Exchange WMI Performance counters. The command

wmiadap /f

helped, see http://msdn2.microsoft.com/en-us/library/aa394528(VS.85).aspx . This didn't even need a reboot.

On Windows 2000 Server I used

diskperf -Y

to enable LogicalDisk WMI Performance counters, see http://support.microsoft.com/kb/253251/en-us . After restarting the servers the counters were up.

Regards, LLS71

---
Leonardo Schieder
A. PORR AG - http://www.porr.at
System Management

http://www.xing.com/go/invita/7686498

Bob

If a system that passes credentials is NOT within the Active Directory Domain, and likewise, not within the Kerberos Realm, it cannot successfully authenticate via Kerberos.  It has to be using NTLM/NTLM2 or even LM authentication, if I'm not mistaken.  Kerberos realms within Microsoft Active Directories are forest dependent, and won't cross domain boundaries.

As for running perfmon locally, on the WUG server, yes and no.  Using the performance logs and alerts MMC snapin, I can successfully create a performance LOG over time because this portion of perfmon.msc allows you to specify credentials.  I haven't been able to use the LIVE charting portion of Perfmon on cross domain machines, since you don't get the opportunity to set up credentials, it just passes the current logged on username/password, unless you use a RUNAS.  The runas would almost work, except that the credentials that you specify for the remote system have to have validity within the origin's domain/security.

With WUG, it appears to use WMI to collect the perflib data right from the registry of a monitored box.   Taking two boxes, one that I can poll properly, and then one that I cannot, I've compared anything that I can think of between them, but they always show as the same--so there's something I'm missing still.  Things I've checked:  hklm\software\microsoft\windowsnt\currentversion\PERFLIB\009 , checked the keys, data values and permissions, even went as far as granting EVERYONE full control.  Also, under HKLM\System\CurrentControlSet\Services\ checked again, security, keys, data values, etc.  Also, full audit security for fails and successes to account logon events, system process audits, and privilege use.  The results all look the same.  What doesn't look the same though, is the list of categories listed by perflib.  I know the library behind the category has got to be intact because without disabling/changing the library, perfdisk.dll, CAN get the proper info from a valid domain member, just not from my WUG box.

I'm still running 11.A, and I see three new updates-I think I'll give 11.03 a shot, maybe it's an already known bug?

I've been hesitant to do the upgrade, they always scare me.  I'm running two different WUG servers, both connecting to separate MSSQL instances on Sql 2005, so not quite a default install, and I know that the schema must be manually updated per database.  Any gotchas on this upgrade?

Thanx for the thoughts and suggestions, keep em coming!

I'll check that wmiadap right away, fingers crossed...

Thx,

Bob

WMIADAP /F made the logical disk counters available on at least one of the servers in question!!! Man, thanks a million!  I'm going to run throught the other boxes to see if it fixes them up as well.

Thanks!

Bob