Systems and methods for remote tracking of reboot status

• US 7,017,085 B2
• Filed: 05/30/2002
• Issued: 03/21/2006
• Est. Priority Date: 05/30/2002
• Status: Active Grant

• Current Assignee: Capital One Services LLC (Capital One Financial Corporation)
• Original Assignee: Capital One Financial Corporation
• Inventors: Braun, Richard A.
• Primary Examiner(s): Beausoliel, Robert
• Assistant Examiner(s): MCCARTHY, CHRISTOPHER S
• Application Number:
  US10/159,767
• Publication Number:
  US 20030226059A1
• Time in Patent Office: 1,391 Days
• Field of Search: 714/24, 714/26, 714/57, 714/47, 714/36, 713/2, 434/118, 702/179, 702/188
• US Class Current: 714/47.3
• CPC Class Codes: G06F 11/0748 in a remote unit communicating with a single-box computer node experiencing an error/fault remote testing G06F11/2294
• CPC Class Codes: G06F 11/0775 Content or structure details of the error report, e.g. specific table structure, specific error fields
• CPC Class Codes: G06F 11/0787 Storage of error reports, e.g. persistent data storage, storage using memory protection
• CPC Class Codes: G06F 11/3024 where the computing system component is a central processing unit [CPU]
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: H04L 43/065 related to network devices
• CPC Class Codes: H04L 43/067 using time frame reporting
• CPC Class Codes: H04L 43/0817 by checking functioning

Abstract

Systems and methods consistent with the present invention provide for remote tracking of the reboot status for a plurality of user terminals. Each user terminal runs a start-up routine capable of creating a record of information about the terminal, including reboot status. The record of information is stored in log file on a file server, along with the records of information from other user terminals. A collection routine executed by a central server collects the log files from the file servers and stores the records in a database. Based on the records stored in the database, various status reports may be generated that reflect, among other things, a reboot status associated with the user terminals over a predetermined period of time.

Claims

1. A reboot tracking system, comprising:

a start-up routine installed on at least one terminal, wherein the start-up routine is configured to create a record reflecting a reboot status associated with the at least one terminal;

a file server for receiving and storing the record in a log file from the at least one terminal; and

a central server for collecting the log file from the file server and storing the record in a database and for generating a reboot status report based on the record stored in the database;

wherein the record contains a reboot flag reflecting whether the at least one terminal experienced a normal or abnormal shut down; and

wherein the startup routine is further configured to execute a shutdown routine that sets the reboot flag when the respective terminal shuts down.

2. A method for remotely tracking a reboot status of a first terminal and a second terminal, comprising:

using a start-up routine to create a first reboot record at the first terminal including a first reboot status reflecting whether the first terminal experienced a reboot;

creating, at a file server remotely located from the first terminal, a log file that includes the first reboot record from the first terminal and a second reboot record from the second terminal remotely located from the file server, wherein the second terminal includes a second reboot status reflecting whether the second terminal experienced a reboot;

providing the log file to a central server remotely located from the first and second terminal and the file server; and

generating a reboot status report that indicates the first reboot status for the first terminal and the second reboot status for the second terminal based on the provided log file;

wherein using a start-up routine to create a first reboot record includes;

determining whether the first terminal or the second terminal experienced an abnormal or normal shut down event; and

providing a flag in the first reboot record or the second reboot record indicating whether the respective first terminal or the second terminal experienced an abnormal or normal shut down based on the determining step.

3. A method for remotely tracking a reboot status of a first terminal and a second terminal, comprising:

using a start-up routine to create a first reboot record at the first terminal including a first reboot status reflecting whether the first terminal experienced a reboot;

creating, at a file server remotely located from the first terminal, a log file that includes the first reboot record from the first terminal and a second reboot record from the second terminal remotely located from the file server, wherein the second terminal includes a second reboot status reflecting whether the second terminal experienced a reboot;

providing the log file to a central server remotely located from the first and second terminal and the file server; and

generating a reboot status report that indicates the first reboot status for the first terminal and the second reboot status for the second terminal based on the provided log file;

wherein using a start-up routine to create a first reboot record includes;

determining whether the first terminal or the second terminal experienced an abnormal or normal shut down event; and

providing a flag in the first reboot record or the second reboot record indicating whether the respective first terminal or the second terminal experienced an abnormal or normal shut down based on the determining step;

wherein determining whether the first terminal or second terminal experienced an abnormal or normal shut down event further includes;

determining whether the first terminal or the second terminal experienced an abnormal shut down condition based on whether an operating system executing in the respective first terminal or the second terminal received a shutdown command during shut down.

4. A system for remotely tracking reboot status comprising:

a first terminal configured to use a start-up routine to generate a first record including a first reboot status of the first terminal;

a second terminal configured to generate a second record including a second reboot status of the second terminal;

a first file server configured to generate a first log file from the first record;

a second file server configured to generate a second log file from the second record; and

a central server for generating a reboot status report based on the first and second log files;

wherein the first terminal and the second terminal are configured to provide a flag in the respective first record and second record indicating whether the respective first terminal or second terminal experienced an abnormal or normal shut down; and

wherein the first terminal and the second terminal are configured to provide the flag based on a determination of whether the respective first terminal and second terminal determines that an operating system executing in the respective first terminal and second terminal received a shutdown command during shut down.

5. A method for improving the choice of a computer system part, the method comprising:

receiving a trend report, wherein the trend report shows data for a number of computer system parts, including at least one of CPU speed, RAM, operating system, or template build;

making a correlation between a particular computer system part and increased computer system reboots, or combination of computer system parts and increased computer system reboots; and

recommending a new computer system part based on the correlation between the computer system part and increased computer system reboots, or combination of computer system parts and the increased computer system reboots.

6. The method of claim 5, wherein the trend report is generated by

creating a first reboot record at a first computer including a first reboot status reflecting whether the first computer experienced a reboot;

creating, at a file server remotely located from the computer, a log file that includes the first reboot record from the first computer and a second reboot record from a second computer remotely located from the file server, wherein the second computer includes a second reboot status reflecting whether the second computer experienced a reboot;

providing the log file to a central server remotely located from the first computer and the second computer and the file server; and

generating a trend report based on the provided log file.

7. A method for improving user performance, the method comprising:

receiving a trend report, Wherein the trend report shows computer reboots for computers used by a users;

making a correlation between a particular user and higher then average number of computer reboots on a computer used by the particular user; and

recommending additional computer training for the user based on the higher then average number of computer reboots for the user.

8. The method of claim 7, wherein the trend report is generated by:

creating a first reboot record at a first computer including a first reboot status reflecting whether the first computer experienced a reboot;

creating, at a file server remotely located from the computer, a log file that includes the first reboot record from the first computer and a second reboot record from a second computer remotely located from the file server, wherein the second computer includes a second reboot status reflecting whether the second computer experienced a reboot;

providing the log file to a central server remotely located from the first computer and the second computer and the file server; and

generating a trend report based on the provided log file.