--On April 25, 2007 2:26:26 PM -0500 Brandon Hall <suppressed> wrote: > I have 3 windows 2003 server machines that I'm trying to monitor and no > matter what I change in the UXMON-NET file, I can't get rid of a red > notice "WINLOGON (0 instances)". I've setup one of these machines with > the exact same procs line, but using a "!". That instance is the only > "WINLOGON" instance and it works perfectly. But I still have a rogue > WINLOGON from somewhere, making my status light red.... what does the History page on the big sister server say for the record where the alarm was first raised? -c ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bigsister-general mailing list suppressed https://lists.sourceforge.net/lists/listinfo/bigsister-general
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.