Abstract: A screen image for monitoring the usage state of a client computer is acquired, the acquired screen image is efficiently stored, and the stored screen image can be easily searched. A draw command is acquired by a driverware (22) when a screen image is generated in a client computer (2), and text data is extracted from the draw command. The extracted text data are associated with the draw command and stored in a database (13) of the server (3). The database (13) is searched using a keyword, and the screen image is reproduced from an associated draw command.

Abstract: A data processing device includes a notified party storage unit for storing a party notified of information on the data processing device; a notification unit for notifying each notified party of the information on the data processing device; a reception unit for receiving from an information processing apparatus a registration request for requiring notified party registration to the notified party storage unit; and a setting unit for setting at least one of the information processing devices as a specific information processing device, in which the notified party storage unit stores the notified party such that the number of the notified parties registered according to the registration request from information processing device that is not the specific information processing device does not exceed a predetermined number among the number of the notified parties that can be stored in the notified party storage unit.

Abstract: An embodiment of the invention is directed to providing robust file system information for non-native devices. In operation, a file system includes both a file storage area for providing access to the contents of files, and a metadata store. The metadata store stores metadata associated with each file or device. When a device is connected to the file system, metadata for that device, and its items, is generated and stored in the metadata store. The metadata persists within the metadata store when the device is disconnected from, or no longer available to, the file system.

Abstract: Load balancer management is described herein. In one implementation a load balancer system includes servers for hosting content on a network site, disparate load balancers that manage the servers to substantially balance data communications across the servers, and a load balancer management service which includes an application program interface (API) that provides for universal communication with the different interfaces of the disparate load balancers. Each of the disparate load balancers may be controlled via a different interface. The API is configured to receive an instruction set to manage the disparate load balancers, and to communicate the instruction set as translated instruction sets to each of the disparate load balancers via the respective different interfaces. The load balancer management service can be implemented as a Web-based service.