Import this key to resolve the event that causes the RAIDMonitor MOM alert. This key is not found on all 2U servers so I have added it here for Support. Below are the solutions as per Johan's research done on the issue. Ken Eder ====================================================== I've seen several MOM alerts that have something to do with the Megaraid SCSI software in our 2U servers. This does not apply to HP or DELL servers. The following application log error causes a MOM alert: Souce: MegaServ.Log EventID : 6304 Unable to Open from Registry. Use Default Schedule Settings. This reg key sets the schedule for raid controller battery health checks. It checks the voltage and charge on the battery. [HKEY_LOCAL_MACHINE\SOFTWARE\RAIDMonitor\ChkConSchedule] "DateOfYear"="07/14/2006" "DayOfWeek"=dword:00000000 "HourOfDay"=dword:00000000 "WeekOfMonth"=dword:00000001 "ChkConEnableFlag"=dword:00000000 "SMARTCheck"=dword:00000001 "SMARTChkInterval"=dword:00000014 In other cases these 2 services are installed but not running : RAID_SERVER and/or REG_SERVER I believe these two services have something to do with centralized raid management software from megaraid. We don't use this, so these services are not correctly configured and cannot start. Non of these errors are critical, but they are picked up by MOM and get turned into tickets...wasting a lot of time I have seen 4 different permutations, and this is how I fixed it: 1. Reg key is there. Services are not installed. --> Everyone is happy 2. Reg key is there. RAID_SERVER service is set to automatic but cannot start. --> Disable the service 3. Reg key is missing. Services are not installed --> Export reg key from another server and import it 4. Reg key is MISSING. RAID_SERVER and REG_SERVER is set to automatic but cannot start --> Copy reg key from another server and disable the services It looks like there is some inconsistancy in the way the megaraid drivers are installed. I do not know if this is due to changes in the kick or drivers installed during or after QC The most recent ticket dealing with this problem is : https://core.rackspace.com/py/ticket/view.pt?ref_no=061024-00426 Server 34441-100835 is only 2 weeks old, so I assume this is a pretty recent kick. Is the RAID_SERVER service installed in the kick, or during the QC process ? Any comments on this would be useful, but let's try to get to the bottom of this and get it right in the future. Fewer event log errors = fewer MOM alerts = fewer tickets = shorter queues ! Johan van Zyl Microsoft Trainer/Intensive Support