Windows

In our latest version we changed how our Service Rule works.
We monitor all automatic services and if any of the automatic services are down, we will create ONE event which will list the services that are currently down.
If you want an event created for each service being down, you can turn off the existing task, Win_Services, and turn on the task Win_Service which creates an event for each service being down.
To turn on/off tasks, go to the AdvancedUI -> Monitoring -> Manage Tasks
Select the task and click Disable Tasks or Enable Tasks.

I’ve written in the past about the battle for the hearts and minds of IT organization in terms of the adoption of virtualization technology. Here is an interesting read from Computerworld “Big vendors look to challenge VMware with open source”

VMware ESX 4 vs MS Windows Hyper-V? Well, the battle rages on between the two hypervisor titans. While VMWare has the lion’s share of the market now, Hyper-V is certainly starting to get some traction. The increased pressure for server consolidation as well as Microsoft’s aggressive pricing and bundling of technology has resulted in many conversations where we are asked to provide advice as to which hypervisor is the best choice. In the past the decision was simple as VMware was the de facto standard.

Anyone know how to monitor disk free space on a Windows mount point?

Yes you can Monitor 64 bit Windows and Unix with 6.1.2. You cannot however install the management console on a 64 bit Server. If you would like the ability to have your management console and agents installed on 64 bit servers you will need to upgrade to version 6.2.

1. If you want to monitor Windows on an Active Passive Cluster you should Monitor the Windows Application on the nodes and on the Virtual Server.
2. Set up Disk Filters by going to Manage Monitoring and clicking on the gear for windows.
3. Then click modify on the Disk Collection. You should now see an Add Filter Button.
4. You want to only monitor the shared drives on the virtual server and on the nodes monitor the physical drives.

In order to change the Disk Task Interval you will have to do the following

1. Stop all of your services from services.msc
2. Navigate to Longitude\Applications\Windows\Collections.
3. Open up the file Windows_Disk.xml in Wordpad or Notepad.
4. You will need to edit the file to the schedule you want.. You can choose from EveryFifteen, EveryTwenty, EveryHalfHour, and EveryHour. Change the Italics to the schedule you would like modifying the interval to the number of seconds... (e.g. 3600 seconds per hour)
5. ConsolidatorCollections Count="1"
   

When you click on the Windows gear and then click test for the Services the only Services that will be listed are services that are set to automatic and not running. Longitude is monitoring all services set to automatic but to conserve space in the database it will not display all running services. To monitor a service that is manual and cannot be changed to automatic you will need to use a Transaction and monitor Winservice.

We recommend trying to monitor the Windows 2008 server with the Windows Firewall turned off.

If you have to leave the Windows Firewall on, please make sure you allow the following Inbound Rules:

File and Printer Sharing (Echo Request - ICMPv4-In)
Windows Management Instrumentation (DCOM-In)
Windows Management Instrumentation (WMI-In)

After registering a Windows application, Disk and/or Disk I/O collections may not be available. The Windows application has 2 different methods for collecting Disk data, and 3 different methods for collecting Disk I/O data. When a Windows application is registered, Longitude will make a best guess as to which version of collector to use, but may need to use an alternate collector if the initial collector fails. After several consecutive collection failures, the Disk or Disk I/O collection method will failover to an alternate method.