Automated device blog creation

• US 20070136302A1
• Filed: 12/12/2005
• Published: 06/14/2007
• Est. Priority Date: 12/12/2005
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Zuber, Mark
• Application Number:
  US11/299,581
• Publication Number:
  US 20070136302A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04M 1/72445 for supporting Internet browser applications

Abstract

Automated device web log (“blog”) creation is described. Data associated with a computing device is automatically gathered and transmitted to a server. The gathered data may include, but is not limited to, configuration data, reliability data, health data, performance data, user-entered problem reports, and so on. The server formats the data as a blog for presentation to a user associated with the computing device for which the blog was created.

Claims

1. A computer-implemented method comprising:

receiving data associated with a remote computing device; and

automatically formatting the data for presentation to a user.

2. The method as recited in claim 1, wherein automatically formatting the data for presentation to a user comprises formatting the data as a chronological web log (blog).

3. The method as recited in claim 1, wherein the data associated with the remote computing device comprises at least one of computing device performance data, computing device health data, computing device reliability data, computing device configuration data, or software data.

4. The method as recited in claim 3, wherein the computing device performance data comprises at least one of a computer boot time, memory speed, disk speed, processor speed, network speed, or video card speed.

5. The method as recited in claim 3, wherein the computing device health data comprises at least one of antivirus status, firewall status, firewall policy update status, antivirus signature update status, antispyware status, data backup status, or disk fragmentation status.

6. The method as recited in claim 3, wherein the computing device reliability data comprises at least one of a number of computing device reboots, a reboot reason, a number of computing device crashes, a crash reason, disk health status data, a SMART disk failure notification, a potential invalid cluster layout notification, or a bad disk notification.

7. The method as recited in claim 3, wherein the computing device configuration data comprises at least one of a motherboard brand, a motherboard model, a central processing unit brand, a central processing unit model, a mouse brand, a mouse model, a keyboard brand, a keyboard model, a video card brand, or a video card model.

8. The method as recited in claim 3, wherein the software data comprises at least one of operating system data, an operating system version, an operating system patch status, a software patch installation status, product update version status, software install report, software uninstall report, or a start group program listing.

9. The method as recited in claim 1, wherein the data associated with the remote computing device comprises a user-entered problem report.

10. The method as recited in claim 1, further comprising:

receiving permissions data indicating a user that should be granted access to the data associated with the remote computing device;

receiving from the user a request to access the data associated with the remote computing device; and

providing the user with access to the data associated with the remote computing device.

11. The method as recited in claim 1, further comprising:

identifying a notification request associated with the remote computing device;

automatically generating a notification; and

transmitting the notification based on the notification request.

12. The method as recited in claim 11, wherein the notification request identifies a user to be notified when data associated with the remote computing device is updated.

13. The method as recited in claim 11, wherein transmitting the notification comprises sending at least one of an email, an instant message, a direct socket communication, an HTTP polling response, an XML web service polling response, an automated telephone call, a telephone text message, a beeper message, or a really simple syndication (RSS) message.

14. A web-based system comprising:

a device history data collection service configured to receive data associated with a remote computing device;

a user permission data store configured to maintain data that identifies one or more users to whom access to the data associated with the remote computing device is to be granted; and

a blog service configured to format the received data for presentation to any of the one or more users.

15. The web-based system as recited in claim 14, wherein the device history data collection service is further configured to:

receive user permissions data identifying a user who is to be granted access to the data associated with the remote computing device; and

update the user permission data store based on the received user permissions data.

16. The web-based system as recited in claim 14, wherein the device history data collection service is further configured to receive a notification request identifying a user who is to be notified when data associated with the remote computing device is updated.

17. The web-based system as recited in claim 14, wherein the blog service is further configured to automatically notify a user that data associated with the remote computing device has been updated.

18. One or more computer-readable media comprising computer-readable instructions which, when executed, cause a computer system to:

receive data associated with the performance, health, reliability, or configuration of a remote computing device; and

format the received data as a blog.

19. The one or more computer-readable media as recited in claim 18, further comprising computer-readable instructions which, when executed, cause the computer system to:

identify a user who is to be notified of updates to the blog;

generate a blog update notification; and

transmit the blog update notification to the user.

20. The one or more computer-readable media as recited in claim 18, further comprising computer-readable instructions which, when executed, cause the computer system to:

receive a request to access the blog from a user;

determine whether or not the user has permission to access the blog; and

in an event that the user has permission to access the blog, provide the user with access to the blog.