Thanks Ryon! I just put it in verbatim for now:
http://dev.zenoss.org/trac/wiki/HowToSetupZenWin -Eric John Gardner wrote:
[EMAIL PROTECTED] wrote:I have WMI successfully running in my environment (multiple server setup). To get it working, make sure you create a domain user and if applicable a local user with the same user name and password; this user needs to be a member of the administrators group (for your domain and the local group.) For your member servers, add the domain administrators group to the local administrators group. Install the zenwin service on a server that is a member server and use a local account to run the service, I could not get zenwin services working using domain accounts. After the services are installed, go into the Services MMC and view the properties of one of the services. Go to the "Log On" tab and browse for the local user created above and add it, even though it is already there, and specify the password and click OK (you should see a box stating the user has been granted log on as service permissions.) You can also manually grant log on as service permissions by GPO or running "gpedit.msc". In the Zenoss web interface, set the zWinUser and zWinPassword under "/Devices/Server/Windows" zProperties to ".\User" (User = what ever your zenwin service user is). You do not need to specify the domain, just use the period and backslash. Then, for the one server running zenwin, navigate to that specific device and delete the zWinUser and zWinPassword; otherwise you will get some errors about credentials being used locally. A few other things to check: Check TCP/IP Settings - Right click "My Network Places" on the desktop and select properties - Right click your active Local Area Connection - Double-click TCP/IP - Click Advanced - Select the WINS tab - Select "Enable NetBIOS over TCP/IP" - Click OK - Click OK - Click OK Check Existing Windows Services REQUIRED Services: - "TCP/IP NetBIOS Helper", Startup Type set to Automatic - "Windows Management Instrumentation", Startup Type set to Automatic - "WMI Performance Adapter", Startup Type set to Manual - "COM+ Event System", Startup Type set to Manual - "COM+ System Application", Startup Type set to Manual NOT Required: - "Server" service, does not need to be installed or running - "Remote Registry", does not need to be running Check DCOM Click Start -> Run Type "dcomcnfg" Expand Component Services -> Computers Right-click "My Computer", select Properties Click the "Default Properties" Tab Make sure "Enable DCOM on this computer" is checked (If if is not, check it, click ok and reboot the computer) Try starting one of your services, typically I use the "Zenoss Eventlog Monitoring" and check the zenwin log files. You should at least see it attempting to connect to all the devices you've added to "/Devices/Server/Windows". If you see an error about "Bad WMI State", and you've been able to successfully test WMI using wbemtest, leave the service running for several hours and it should clear itself up (have not been able to figure this one out). I also have an issue regarding starting the services using RDP. For some reason if I connect to the console of the server and I start the services then log off, the services will stop working properly. They show they are running, but they do not collect any info. So, I connect without using the /console switch and start the services. - RyonRyon That's excellent 'how to' doc. I'll try and get Drew to add it to the Wiki or the FAQ. Great work! John
_______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
