WMI

Hey all,

Is there a way to see which account is getting used to run WMI requests?

Thanks

Brian

The following applications use WMI to collect some or all their data:

• ActiveDirectory
• Citrix
• Exchange
• Exchange2007
• IIS
• SQL2000
• SQL2005
• SQL2008
• Transaction: Service
• Transaction: WinProcess
• Transaction: WinScript
• Transaction: WinShare
• Transaction: WMIConnect
• Windows
• WindowsEventLog

WMI based collections require Local Administrator privileges on the target server. The Longitude Statistics Server Agent uses the permissions assigned to its service account to access WMI.

The following list displays the types of accounts that can be used to give the Statistics Server sufficient permissions to collect WMI data:

• Domain account that is a member of the Local Administrator group on the target server.
• Domain account that is a member of the Domain Administrator group, and will be a Local Administrator member on all domain servers by default.

Unfortunately you can not monitor Windows based applications with a Linux agent as the agent is unable to make WMI Calls to Windows Machines.

WMI (Windows Management Instrumentation) access must be permitted by Windows Firewall if the firewall is enabled using default settings. You can configure the firewall to allow WMI access by executing the following in a command prompt on the managed device:

netsh firewall set service RemoteAdmin

****Please note:
After installing Service Pack 2 on Windows XP, Windows Firewall is enabled by default. Please check the firewall configuration after applying SP2 to Windows XP devices that you plan to monitor with Longitude.
****

If the registration of a Longitude application fails and the error message indicates that the systeminfo command could not be executed due to a logon failure, check the DCOM settings on the computer you are trying to monitor, as follows:

1. Make sure the “Distributed Transaction Coordinator” service is started.
2. Run DCOMCNFG on the target.
3. Expand Component Services until you see My Computer.
4. Right-click My Computer and select Properties.

If you attempt to add the Windows application and receive an error referencing "Cannot parse system info" this means that Longitude encountered a problem while autodiscovering the properties of the server. To work around this problem:

1. Open the Longitude Web Interface.
2. Go to the Manage Longitude Properties function (Adminstration » Component Management » Manage Longitude Properties).
3. Under the Management Station folder, click on the Statistics Server component link.
4. In the resulting properties display, click on the Advanced button.

Some Longitude SQL collections (e.g. BufferManager, CacheManager, Databases, Locks, MemoryManager) rely on SQL Server performance objects. If the performance objects are missing, the collections will not return any data. To resolve the problem, reload the SQL Server performance objects on the managed device as follows:

1. Run the following from a command prompt to unload the existing counters:
   unlodctr.exe {MSSQLServer}