Motherboard Monitoring Software

[OCS1]

Ive got a client w/ a custom built server running Small Biz 2003. The server is having a problem with random shutdowns. Ive checked for any issues w/ overheating and there are none. Ive already replaced the power supply just to be sure. The shutdowns still happen. My question is, what software can you guys recommend that will monitor and log the motherboards activities regardless of the make or model of motherboard?

 

[OCS1]

Ive come to the conclusion that it isnt a hardware problem. I was lucky enough to see it actually shutdown today and it just goes through the normal shutdown process, without any errors or warnings. There was nothing odd about the shutdown other than the fact that nobody issued the command. Nothing was listed in the event manager at the exact time of the shutdown.

The only things that are listed in the event manager that seem a bit strange are these 2 messages that are showing up back to back every minute, in 20 minute intervals:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 1/06/2005
Time: 7:18:53 PM
User: NT AUTHORITY\SYSTEM
Computer: JERNSERV
Description:
Windows cannot determine the user or computer name. (The
RPC server is unavailable. ). Group Policy processing
aborted.

Then immediately afterwards:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 1/06/2005
Time: 7:19:22 PM
User: JERNIGAN\Administrator
Computer: JERNSERV
Description:
Windows cannot query for the list of Group Policy objects. Check the event
log for possible messages previously logged by the policy engine that
describes the reason for this.

I seriously doubt this is causing the shutdowns, though. These errors have more to do with DNS and the server isnt a DNS server. There is only 1 workstation at that particular site and it gets its DNS info from it's ISP.

I can see no reason whatsoever why the shutdowns are occuring.

Any ideas?

 

[Rhodizzle]

There may be some sort of GPO applied to the server that sets it to shutdown if a certain set of variables are encountered, i would start by investigating all of the GPOs that are applied to the server.