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.
- Ryon
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wesley.Sparks
Sent: Tuesday, February 06, 2007 6:40 AM
To: General discussion of using zenoss system
Subject: RE: [zenoss-users] Major WMI issues
I have tried the local administrator of the box and a domain user
account and a domain admin account. I thought the same thing but I
logged in as the user the that the services run as and it still worked
from command line but not the service. I have done the wbemtest using
all three of those accounts and can connect successfully and run the
service query. I am assuming the service needs to use the account that
is also in zproperties for the device? I am also assuming when using a
domain account you use domain\username in zproperties? I was hoping
someone that has successfully gotten WMI to work to post their total
config so we can see if we got some config wrong somewhere.
Thanks
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric Newton
Sent: Tuesday, February 06, 2007 8:34 AM
To: General discussion of using zenoss system
Subject: Re: [zenoss-users] Major WMI issues
Hi Wesley,
What user are the services running under? I know that when it works
from the command line, but not as a service, it's often a permission
problem.
-Eric
Wesley.Sparks wrote:
> It is proper in my files, looks like it got garbled up when I sent it.
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of John Gardner
> Sent: Monday, February 05, 2007 1:00 PM
> To: General discussion of using zenoss system
> Subject: Re: [zenoss-users] Major WMI issues
>
>
>
>>
>>
>> winurl http:///
>>
> myserver/:8080/zport/dmd/Devices/Server/Windows
>
>> zopeusername admin
>>
>> zopepassword zenoss
>>
>> zem http:///myserver/:8080/zport/dmd/ZenEventManager
>>
>>
>>
>
> Wesley
>
> Is the above a cut and paste from your actual file or a retype? I
only
> ask because there are too many slashes after http: and :8080 should be
> immediately after your server name, without the slash.
>
> John
>
>
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
----------------------------------------------------------------------
The information contained in this e-mail and any attachments is to be
considered legally privileged and confidential. If you have received this
communication in error, please notify the sender and permanently delete the
e-mail and any attachments immediately; you should not retain, copy or use this
e-mail or any attachment for any purpose, nor disclose all or any part of the
contents to any other person.
We have taken every reasonable precaution to ensure the integrity of this
communication and that it does not contain any malicious payload (i.e.
attachments, embedded code, links, etc.). The recipient is responsible for
re-verification. The Credit Union accepts no liability for any damage caused
by this communication.
----------------------------------------------------------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
