I was having this same issue when I implemented Zenoss. What I found through some digging on my end is that the user you have logging into the server must be part of the Local Machines Builtin Administrators group. Once I added the user to the group the error went away. We actually have 2 domains where I work. What I did was add the domain admins to the Builtin Administrators group on both of our Domain Controllers and that forced it down to the lower machines on the domain. I also double checked and if that didn't work I just added it manually. Ever since then I haven't had a single issue and now I'm getting a ton of information back from our servers. I monitor 15 Servers and over 60 Cisco Devices with Zenoss and it doesn't skip a beat.
------------------------ Mike Sartuche -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=11607#11607 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
