|Publication number||US8055617 B2|
|Application number||US 12/142,723|
|Publication date||Nov 8, 2011|
|Filing date||Jun 19, 2008|
|Priority date||Mar 24, 2003|
|Also published as||CA2518439A1, CA2518439C, CN1791871A, CN1791871B, EP1606721A2, EP1606721A4, US7398272, US20050086534, US20080320006, WO2004086199A2, WO2004086199A3|
|Publication number||12142723, 142723, US 8055617 B2, US 8055617B2, US-B2-8055617, US8055617 B2, US8055617B2|
|Inventors||David Salim Hindawi, David Leigh Donoho, Lisa Ellen Lippincott, Dennis Sidney Goodrow, James Milton Brown, Peter James Lincroft, Peter Benjamin Loer, Orion Yosef Hindawi|
|Original Assignee||International Business Machines Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (73), Referenced by (9), Classifications (17), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application is a continuation of U.S. patent application Ser. No. 10/804,799, U.S. Pat. No. 7,398,272 filed Mar. 19, 2004, which application claims benefit of U.S. provisional patent application Ser. No. 60/457,480, filed Mar. 24, 2003, the entirety of which is incorporated herein by this reference thereto.
1. Technical Field
The invention relates to the network management technology. More particularly, the invention relates to an enterprise console for management of large-scale the networks of computational devices.
2. Description of the Prior Art
Information technology (IT) administrators in enterprises everywhere face a daunting task of managing the software and hardware on tens, hundreds, or thousands of machines in their domains. With so many incompatibilities, patches, and policy advisories announced daily, the task is much more than just acquisition and installation. Even simply keeping aware of all potentially problematic situations on hardware and software products used in an enterprise requires more than a full-time job. Dealing with those situations in response to user complaints adds still further taxing demands. Thus, it is required that IT managers must anticipate the situations which may soon arise in a specific enterprise and make plans to deal with those before they cause major problems. This creates an urgent need of a technique which enables the IT managers to understand the configuration of the hardware and software in a given intranet, to keep track of the policy advisories, updates, incompatibilities and patches relevant to the specific enterprise, and to match those policy advisories, updates, and patches with the specific equipment in the enterprise.
Donoho et al disclose in U.S. Pat. No. 6,256,664 a technique which enables a collection of computers and associated communications infrastructure to offer a new communications process. This process allows information providers to broadcast information to a population of information consumers. The information may be targeted to those consumers who have a precisely formulated need for the information. This targeting may be based on information which is inaccessible to other communications protocols because, for example, under other protocols the targeting requires each potential recipient to reveal sensitive information, or under other protocols the targeting requires each potential recipient to reveal information obtainable after extensive calculations using data available only upon intimate knowledge of the consumer computer, its contents, and local environment.
This process enables efficient solutions to a variety of problems in modern life, including the automated technical support of modern computers. In the technical support application, the disclosed invention allows a provider to reach precisely those specific computers in a large consumer population which exhibit a specific combination of hardware, software, system settings, data, and local environment, and to offer the users of those computers appropriate remedies to correct problems known to affect computers in such situations.
Whereas in the consumer setting it is acceptable for the computer user to be in control of the process, learning which problems exist and applying the fixes, in the enterprise setting it is often the case that end user administration of computers is frowned upon. Instead, computers are often managed centrally, and a system administrator is in charge of keeping configurations workable and avoiding enterprise-wide problems.
What is desired is a technique that provides centralized advice management in a large-scale the network of computers.
What is further desired is that such technique provides a management interface that can display relevant advisories of all computers in the network and deploy suggested actions to all relevant computers.
What is still further desired is that such management interface allows a system administrator to manage subscription of advice provider sites, monitor status of deployed actions and monitor status of computers in the network.
What is still further desired is that such technique can automatically apply the required management tasks to fix problems on susceptible machines before they occur.
Commonly assigned PCT application no. PCT/US02/36644, which application is incorporated herein in its entirety by this reference thereto, discloses a system and method for centralized advice management of large-scale the networks, wherein a number of distributed clients run on registered computers, gathering advisories and report relevance to a central server. A system administrator may view the relevant messages through a management interface and deploy suggested actions to distributed clients where the actions are executed to apply the solutions of the advisories.
In a preferred embodiment, a centralized advice management system includes a plurality of distributed clients, a central server, a central database, and a management interface. The distributed clients gather advisories from a plurality of advice provider sites and report relevance of advisories to the central server. A system administrator may view the details of relevant advisories and deploy the suggested actions to distributed clients of relevant computers, where the actions are executed to apply solutions provided by the advisories.
In another equally preferred embodiment, a centralized advice management system includes a plurality of distributed clients, a mirror server, a central server, a central database, and a management interface.
In another equally preferred embodiment, a centralized advice management system having a distributed client is provided, in which the distributed client comprises various components performing functions such as gathering advisories, authenticating advisories, evaluating relevance of advisories, registering a computer to a central server, reporting relevance to the central server, listening messages from the central server, gathering deployed actions from the central server, and executing deployed actions.
In another equally preferred embodiment, a method for providing centralized advice management for large-scale computer the networks is disclosed that comprises the steps of:
The method may further comprise a step to manage subscription of advice provider sites to the distributed clients. It may further comprise a step to monitor the status of deployed actions. Alternatively, it may further comprise a step to monitor the status of registered computers.
It would be advantageous to provide an enterprise console by which such system is used to identify vulnerable computers on the network, and that then allows authorized personnel to correct problems across any subset of the network with a few simple mouse-clicks.
The presently preferred embodiment of the invention comprises a console for an enterprise suite. The enterprise suite addresses the increasingly complex problem of keeping critical systems updated, compatible, and free of security holes. It uses Fixlet® technology to identify vulnerable computers on the network and then allows authorized personnel to correct problems across any subset of the network with a few simple mouse-clicks. The enterprise suite helps keep the networked computers updated and properly patched, all from a central console which, along with supporting architectural enhancements, is the subject matter of this document. The invention allows rolling out a security patch in minutes instead of months, thus allowing an administrator to stay ahead of potential hacker attacks. The invention also makes it possible to track the progress of each computer as updates are applied, thus making it simple to gauge the level of compliance across the entire enterprise.
The Enterprise Suite solves the increasingly complex problem of keeping critical systems updated, compatible and free of security holes. It uses patented Fixlet® technology to identify vulnerable computers on the network and then allows authorized personnel to correct problems across any subset of the network with a few simple mouse-clicks (see U.S. Pat. Nos. 6,604,130, Donoho, et al., issued Aug. 5, 2003 for Relevance clause for computed relevance messaging; 6,356,936, Donoho, et al., issued Mar. 12, 2002 for Relevance clause for computed relevance messaging; 6,263,362, Donoho, et al., issued Jul. 17, 2001 for Inspector for computed relevance messaging; and 6,256,664, Donoho, et al., issued Jul. 3, 2001 for Method and apparatus for computed relevance messaging, each of which is incorporated herein in its entirety by this reference thereto). It is easy to keep the networked computers updated and properly patched, all from a central Console. Rolling out a security patch can be accomplished in minutes instead of months, allowing a user to stay ahead of potential hacker attacks, viruses and worms. One is able to track the progress of each computer as updates and patches are applied, making it simple to gauge the level of compliance across the entire enterprise. In addition, the invention keeps a running history of all remedial actions, providing a detailed audit trail for every Fixlet action and every patched computer on the network.
A Typical Installation
A typical installation of 10,000 or fewer Clients is shown in
Overview of the System
The system has the following main components:
The Main Console window (see
The Fixlet Messages tab is selected, and the user is viewing a message opened from the list panel: In general, the Console operator views the list of Fixlet messages, opens each one and sees what the issues are. Each Fixlet message describes a problem that has been discovered on some Client. The Fixlet document in the bottom panel presents one with a short, clear explanation of the problem. If one wishes, one can inspect the actual code used in the Relevance Expressions and the proposed actions.
Once one decides to deploy the action to the relevant computers, just click on the action (represented by a button or a hyperlink in the Fixlet Window) and follow the prompts. After deploying the action, the affected Clients are fixed and no longer report the problem, so the Fixlet disappears.
One can set preferences that govern how responsive and secure one want s Fixlet the network to be. To change the default values, select Preferences from the File menu.
The Enterprise Suite is a powerful and feature-packed program that may seem overwhelming to a new user. Fortunately, once one masters the typical workflow, the operation becomes straightforward and intuitive. Let's run through a sample session:
This is the workflow that one uses for typical computer maintenance and remediation. As one explores the interface, one discovers that the invention can also help one inventory computers, manage users and maintain a detailed history of every patch and upgrade. In each case, one starts with the top panel, uses the left panel to filter the list and then finds further information in the bottom panel. With this simple overview, one is ready to maintain the network in prime operating condition with a minimum of fuss.
Viewing Fixlet Messages
To display a Fixlet message,
The body of the Fixlet message shows up in the lower display region (click the Description tab if not already selected). All of the Fixlet messages (as well as computers, actions and operators), when selected, get windows of their own, which can be managed by selecting items from the Window menu.
The Fixlet display region has three tabs:
When Fixlet messages become relevant somewhere on the network, the invention adds them to the list of Fixlet messages to be displayed under the Fixlet Messages tab in the Console main window. The Fixlet filter/list contains entries that include the following information:
As with all the filter/lists in the Console, one can filter this list using the panel of folders on the left. Each folder contains data groupings that one can use to narrow down the list of Fixlet messages on the right. Then, in the listing area itself, one can sort the Fixlet messages by clicking a column heading. For example, one might filter the list by opening the Source Severity folder and selecting Critical to filter out non-critical Fixlet messages. Then one could sort the Fixlet messages by Affected Computer Count (which shows the number of affected computers) to find which Fixlet messages are relevant to the greatest number of computers. If one does not see one of the columns listed above, right-click in the Fixlet header and select it from the pop-up menu.
Commenting on a Fixlet Message
Some Fixlet Sites contain, as part of the Site design, a link or button that says Comments. This link is designed to provide feedback to the Fixlet author.
One can hide a Fixlet message with the following procedure:
The hidden Fixlet message is no longer displayed in the Fixlet list. In addition, some Fixlet sites contain, as part of the site design, a link that says Hide Fixlet Message. Here's what to do:
Generally speaking, it is not necessary to hide Fixlet messages, as one can simply ignore them. The main reason for hiding a Fixlet message is if one feels that the message is not relevant to the network and could never be useful and one wants to avoid viewing the message every time one launches the Console.
One can see a list of the hidden Fixlet messages by selecting View>Hidden Fixlets. From this panel, one can also restore or “unhide” a Fixlet message by selecting it and clicking the Restore Fixlet button.
To inspect various aspects of a computer quickly, the Relevance Language was developed. This human-readable language allows Fixlet authors to target actions to just those computers that need the fix and no others. Thus one can feel confident that only broken machines are being fixed and that the rest are never bothered.
The Relevance Language can query an exhaustive set of computer properties, and it is designed for speed. Most Console operators rely on third parties to write Fixlet messages, and so their exposure to the Relevance Language is not critical to operating the Console. However, the Console can be customized with short lines of code from the Relevance Language (called Relevance Expressions) which allow an unprecedented amount of control over the Client computers on the network.
A typical Relevance Expression might be vendor name of processor
This expression returns the name of the manufacturer of the CPU (which may be Intel, for instance), which can then be used to determine relevance. One can use Relevance Expressions to create retrieved properties which one can use to organize and filter the Clients on the network. For example, Table 1 below shows some possible properties that might be useful to know about Client computers.
Client Computer Properties
family name of main processor
True if the processor is
Total space of drive “c:” <
True if the drive is
smaller than 2 GB.
absolute value (now - apparent
True if the clock is off
registration server time) > 1 hour
by more than one
file version of application
Version number of
“iexplore.exe” of the registry
application of key
the name of the app
that handles mailto
of the registry
requests from a
exists running application whose
True if Word is
(name of it as lowercase is
running on the BES
date of Bios
BIOS date, if it exists.
number of processors
The total number of
processors in the
BES Client computer.
Use the Retrieved Properties dialog to see how these custom properties work. Click the Add New button, supply the property name, and type in the Relevance Expression in the text box. There are literally thousands of useful Retrieved Properties—far too many to list here.
Viewing Relevance Expressions
When a Fixlet message becomes relevant to some computer on the network, one may want to know exactly what triggered it. One may also want to scrutinize the specifics of the suggested action. One can, because these items are written in the Relevance Language, which is a human-readable language for probing and acting on computers.
To view these Relevance Expressions:
This opens a new panel with two main areas to display the “brains” behind the Fixlet message:
At the heart of the system is the ability to deploy actions to fix one or many computers. Here's how:
The action are sent to all the computers targeted in the Take Action dialog. Once the action has executed and the targeted computers are fixed, those computers should no longer report this Fixlet message as relevant.
When one agrees to take a proposed action he is given several options concerning its deployment—for example, one might schedule the action to take place unattended, after midnight, or to take place explicitly with computer user involvement during the day. After actions have been scheduled, the Server attempts to signal individual computers that actions are waiting for them. Ideally, the Client gathers the action information from the action site and carries it out immediately. More typically however, some computers are powered off and others are mobile and undocked at the time of the deployment. As soon as these computers are powered on or docked to the network, the remedial actions are applied to them as well. The Console lets one monitor the entire rollout, from start to finish.
Should one ever find it necessary to stop execution of an action that's already been deployed but hasn't finished running yet, follow these steps:
If one wants to modify an action that's been deployed but hasn't finished running, one must first stop the action as described and then start a new action with the desired characteristics. There is no way to modify the targeting or scheduling of an action once the deployment is initiated.
Restarting an Action
If one has stopped an action before it finished, one can start it up again with this command:
This places the action back on the server, which then begins to target the action to the relevant machines.
Many Fixlet messages have a default action that can be applied automatically. This is a simple process:
Often, a suite of related Fixlet messages becomes relevant all at once. If they each have default actions, one may be able to apply all of them with a single click:
One can create custom actions to fix problems across the network that are not currently addressed by the standard content sources. Although the process is simple to describe, there are an infinite number of actions and targeting techniques that can be used. To create a custom action:
The actions are applied using whatever constraints and schedules specified.
Monitoring Computer Status
Although the invention is primarily a preventive maintenance tool, it can also be used to analyze the computers in the network. Using the Relevance Language, one can query any Client and get a real-time response. This can be invaluable for analyzing trends and potential problem areas on the network. To view the computers on the network:
The folder names and column headers represent important, continuously updated properties of the networked computers, called retrieved properties. To view the Relevance Expressions that define the column headers:
That is, CPU is a concatenation of relevance expressions and strings that produces an output such as: 2800 MHz Pentium 4.
If one changes any of the factory-installed properties, one can restore them by re-entering the original relevance expression. See Restoring Retrieved Properties. One can quickly select which properties to display by right-clicking on the column headers. A pop-up menu is displayed that allows one to check or uncheck the properties one wants to display. Notice that when one delete a property from the headers, it also disappears from the filter panel to the left of the list.
Creating Retrieved Properties
One can collect information from Clients by defining various retrieved properties. An impressive range of computer attributes can be monitored as retrieved properties. There are several reasons why one might want to create some custom retrieved properties of own:
To create a custom retrieved property, follow these steps:
entries and even data in specific files on the client computers. After one define the new column heading, the Clients automatically compute the value of the corresponding relevance expression and return it to the Database.
Note: Some of these properties are primarily aimed at Windows computers. Some properties do not work on certain versions of Windows and return a blank string. A blank string is also returned if more than one result is retrieved for a property.
Restoring Retrieved Properties
It is easy to customize the retrieved properties that are used as column headers in all the Console computer listings. Should one want to restore the predefined properties, do the following:
If one needs to add back a field that one inadvertently deleted:
One can change the locked status of any Client in the network. This lets one exclude specific computers or groups of computers from the effects of Fixlet actions. This could be useful, for instance, if one wants to insulate certain development computers from any changes or updates. It also provides a powerful technique for testing new Fixlet actions on a limited set of unlocked computers, while keeping the rest of the network locked down. Client computers can be locked forever (until explicitly unlocked) or for a defined period of time.
Changes are made to the locked status of a Client by sending an action. As a consequence, the Console operator must supply proper authentication to lock or unlock any computer. Even though a Client is locked, there is still a subset of actions that can be accepted by the client. These include clock changes and unlock actions as well as actions from the Support site. To lock or unlock a computer, follow these steps:
In a typical deployment, there may be thousands of computers sharing a centralized Fixlet database. If they are all administered by a single Console, there may be an overwhelming amount of information to view and the response rate may suffer.
A better way to organize the network of this size is to break it down into departments. Each department head can be assigned management rights to his own departmental computers. For even larger the networks, these departments can be broken down again. Because different managers can be assigned to overlapping groups of computers, any kind of configuration is possible. Managers only receive information from their assigned computers, dramatically improving responsiveness.
Here's how to grant or revoke management rights:
Management rights are distributed as Fixlet actions, so one sees a brief Action Progress dialog as the new rights are deployed.
To remove a computer from Administration, follow this procedure:
This computer is no longer under Administration, and is no longer be queried for vulnerabilities.
Managing Fixlet Sites
Upon installation, is automatically set up to subscribe to the Support Site. Depending on the terms of license, one may have subscriptions to other sites as well. This means that content from those Sites automatically flows into enterprise and are evaluated for relevance on all computers running the Client.
To subscribe to a site, follow these two steps:
The masthead is propagated to all Clients, which immediately begins to evaluate the Fixlet messages from the new site.
Viewing Site Properties
After initiating a subscription, one may want to inspect its properties and signing authorities. This can be useful when tracking down the origin of a particular Fixlet message or action. Here's how:
The Site Properties dialog box appears, detailing information about the site publisher and the precise URLs from which the content has been gathered. Among other things, this dialog box shows e-mail addresses for user feedback and the recommended gather frequency.
Canceling a Subscription
One can afford to be adventurous in trying out Fixlet Site subscriptions for organization, since Fixlet messages themselves place no perceptible burden on computers and since no actions on those computers are ever taken without approval. Nevertheless, if one finds that a subscription is not useful, one can cancel it by removing the Site from the list of subscriptions, as follows:
Relays are optional the network components that can significantly improve the performance of installation. Downloads and patches, which are often large files, represent by far the greatest fraction of bandwidth. Relays are designed to take over the bulk of the download burden from the Server. Rather than downloading patches directly from a Server, Clients can instead be instructed to download from designated Relays, significantly reducing both server load and client/server the network traffic. Relays help in the upstream direction as well, compiling and compressing data received from the Clients before passing it on the Server. Any Windows 2000 or XP-based client can serve as a Relay.
A Relay simultaneously mitigates two bottlenecks:
Assigning Relays is simple, and Clients can be made to automatically discover and link to them. Automatic discovery is recommended because it insures optimal performance even while computers and relays are being disconnected and reconnected across the network.
A Relay takes over most of the download duties of the Server. If several Clients simultaneously request files from a Relay, a significant amount of the computer's resources may be used to serve those files. Other than that, the duties of the Relay are not too demanding. The requirements for a Relay computer vary widely depending on three main factors:
The Relay system requirements are similar to those for a workgroup file server. A computer with 1 GHZ CPU, 256 MB RAM, and 5 GB of free space on the hard drive should be able to act as a Relay for several hundred to several thousand computers—provided that the Console operator distributes the file downloads over an appropriate length of time. Here are some further requirements and recommendations:
Although Clients can automatically seek out and connect to the available relay, one may want to control the process manually. If so, for each Client in the network, one may specify both a primary and secondary relay (see
Relays are failsafe. If the primary Relay fails, the secondary kicks in. If the secondary also fails (or no secondary has been designated) then the Clients automatically revert to downloading files directly from the Server. Although optional, it is recommended that whenever a Relay is created, a secondary Relay should be created as well. Here's a useful strategy for using the primary and secondary relays:
To set up a Relay, one needs to designate a Windows 2000, 2 k3 or XP client computer to take over some server duties. Once a Relay has been set up, computers on the network can automatically find them and connect to them (or, if one need, one can manually assign Clients to point at specified relays).
This significantly reduces the client/server communication necessary for patch application and management. Clients start to download from these designated relays, minimizing the load on thin connections to the Server. The Clients also upload their status information to the Relay, which compiles it and compresses it before passing it on up to the server.
Relays help enormously to spread out and optimize the network traffic, ensuring maximum responsiveness with minimum bandwidth. Relays are especially attractive with remote offices connected by relatively slow VPNs. The Server sends a single download to the remote Relay, which can then distribute it to the Clients over a faster local subnet.
To configure a client computer as a Relay, follow these steps:
After the relay has been created, Clients can be made to automatically discover them and connect up to them, always seeking the Relay that is the fewest hops away. If need to manually configure Clients, one must notify each computer that it should use a specific relay to point to, as described in Using Relays.
Once one has set up a Relay one needs to direct Clients on the network to gather from that relay, instead of from the Server. This is actually a good job for a computer, and can automatically assign relays for one. This is a good idea for two reasons:
Here's how one can ensure that Client computers are automatically signing up to the nearest relays:
One can select all the computers (or any given subset) of the local net to gather from the relay. The procedure is different for setting a single computer or multiple computers. Here's how to set multiple computers:
Here's how to set a single computer to point to a relay:
The Web Reports can monitor, print or archive the status of the local database. It also has the ability to read the databases of other Servers and aggregate the data. That offers one a top-level view of a large or far-flung enterprise with multiple database servers. Aggregation servers allow one to view information from multiple the networks with hundreds of thousands of computers.
Web Reports can be viewed at any time from the desktop by selecting Start>Programs>Enterprise>Web Reports or from the Console under Tools>View Web Reports.
Any Web Report server can be set up to aggregate data from the other Servers.
Web Reports Overview
One can view the data in the database from several different points of view and save or print the output. One may also export the output to Excel for further manipulation.
These features are provided by the Web Reports program, which can be run at any time from the desktop by selecting Start>Programs>Enterprise>Web Reports or from the Console by selecting Tools>View Web Reports.
When one runs the Web Reports program, it presents one with an overview of relevant Fixlet messages and remediation efforts. One finds charts summarizing the number of administered computers in the network and vulnerability status. In addition, one finds overall statistics and a list of the most common issues detected. One can click on these popular Fixlet messages to see them in greater detail.
At the top of the screen are five tabs offering different services:
There are three buttons at the bottom of most reports:
Using the Web Reports program, one can create reports that can be printed out or exported to Microsoft Excel for further manipulation. Creating a report is as simple as clicking a few buttons to customize the output, but do not let the simplicity fool one—there are thousands of different reports that can be generated by this Web-based program.
To create a Web report, follow these steps:
There are several types of report, divided into five main categories. Click one of the buttons on the left edge of the screen to specify the type and subtype of the report one desire. For most of the selections, one may also be able to filter the data to shorten the reports. If a particular report type does not allow these filters, the filter controls are grayed out.
The available report types (grouped into five categories) are:
There are three buttons at the bottom of most reports:
One can view the data in the database from several different points of view and save or print the output for inventory or audit purposes. One may also export the reports to Excel for further manipulation.
Web Reports can be viewed at any time by selecting Start>Programs>Enterprise>Web Reports from the desktop.
Or one can start it from the Console:
The Server installer includes an installer for MSDE 2000 SP3a. Due to restrictions built into MSDE 2000 by Microsoft, when too many database connections are open, MSDE slows itself down. The Server components use several database connections and each Console operator also uses a database connection. When multiple Consoles are running at the same time, one may see some performance degradation due to the MSDE restrictions. This can corrected by using SQL Server 2000 instead of MSDE 2000.
Editing the Computer Settings has a number of advanced configuration settings that allow one to fine-tune deployment for optimal performance. One can customize the behavior of any Server, Relay or Client in the network. It is recommended that one gain some experience with the default settings before one edits these values. These settings are at the heart of the system, granting one great power, but requiring careful planning.
To edit the settings for a particular computer or set of computers, follow these steps:
The File Menu offers the following commands:
The Edit Menu offers the following commands:
are not accepted by them. This toggling menu item shows or hides those messages that are relevant entirely on locked computers.
The About dialog displays the version of the Enterprise System Console. It also includes an e-mail address for tech support and a list of the developers. This dialog is available by selecting:
One can view the status of an action as it is deployed across the network. Just click the Actions tab and double-click on the desired action from the list. In the lower part of the screen, the Action opens up in its own document window, displaying details of the deployment.
The Reported Computers tab of the Action document displays a filter/list of the computers targeted by the action, along with the current status of each. This set of computers was targeted when the action was initially specified. The deployed actions progress through a series of well defined stages on a given computer. This dialog lets one track all the stages of each action across all targeted computers.
This dialog is available by clicking the Actions tab and double-clicking on an action from the list. Then click the Reported Computers tab in the Action document window.
The Constraints tab of the Action document is a read-only display. It shows the scheduled actions and specifies whether user action is needed. These settings were created when the action was initially specified. (To change these values, see Take Action—Constraints).
This might be desired when the action requires user feedback or intervention.
An Action document (see
At the top of the Action document one finds the name, a time stamp, the operator's name, how many computers were affected and how many were fixed. There are seven tabs in an Action document. They are:
An Action document is opened whenever one open an item in an action list. To display an action list, click the Actions tab.
The Execution tab of the Action document is a read-only display. It shows the execution settings that were created when this action was initially specified. (To set or change these values, see Take Action—Execution).
If the Fixlet Message becomes relevant again after the action has successfully executed, automatically reapply the action. If this box was checked when the action was deployed, the action are reapplied should it ever become relevant again.
Limit to XX reapplications. If the above box is checked, it indicates that the action is reapplied no more than the given number of times after a successful execution.
This dialog is available by clicking the Actions tab and double-clicking on an action from the list. Then click the Execution tab in the Action document window.
Action Site Signing Keys
This dialog prompts the Console operator to supply private keys and certificates that are needed to authorize actions before they can be deployed.
The Console operator must obtain these items from the Site Administrator, who must first create them using the Authorize Tool.
The three documents one must get from the Site Administrator are:
Once these three documents have been created, the Site Administrator can then hand them out to authorized personnel. Without these certificates, actions can't be propagated. To sign an action, the authorized Console operator must browse to the appropriate certificates (usually stored on a removable disk) and provide a password.
This dialog also allows Console operators to change their passwords. Click the Change Password button at the bottom of the screen.
The Message tab of the Action document is a read-only display. It shows the settings of the message box that were created when the action was initially specified. (To set these values see.
Display message before running action: This box indicates whether a message are presented. When this box is checked, the box below displays the message.
Message Buttons Two optional buttons to display to the user:
This dialog is available by clicking the Actions tab and double-clicking on an action from the list. Then click the Message tab in the Action document window.
Action Progress Report
This dialog box shows the progress of an action as it is applied across the Fixlet the network. First, it shows the progress of any downloads (patches, updates, etc.). If there are files to download, it displays the name of the downloaded file, the total number of bytes, the current amount downloaded, the transfer rate and the estimated time to completion.
There are three buttons at the bottom of the progress dialog:
The Relevance tab of the Action document is a read-only display. It shows what criteria are being used to judge when a computer is considered to be fixed. Typically, the original Fixlet is designed to trigger only when it becomes relevant to the given computer. Fixing the problem also deactivates the trigger, so the Fixlet is no longer relevant (it becomes FALSE). In other words, a computer is considered to be fixed when the Fixlet no longer applies. That is the automatic solution and is the default setting (top button).
There may be reasons to specify different criteria, provides three options:
Consider a computer to be “Fixed” when:
If a change was made to the default relevance expression, the customized version are listed in the following text box.
This dialog is available by clicking the Actions tab and double-clicking on an action from the list. Then click the Relevance tab in the Action document window.
Action: Action Script
The Action Script tab of the Action document is a read-only display. It shows the action script that was initially selected for deployment. (To set or change these values, see Take Action—Action Script).
This dialog is available by clicking the Actions tab and double-clicking on an action from the list. Then click the Action Script tab in the Action document window.
The Target tab of the Action document presents a read-only display. It shows which computers were originally targeted when the action was initiated. (To set these values, see Take Action—Target).
There are two radio buttons at the top of this dialog:
This dialog is available by clicking the Actions tab and double-clicking on an action from the list. Then click the Target tab in the Action document window.
The Actions tab allows one to follow the progress of all the Fixlet actions that have been deployed across the network to date. Click the Actions tab to bring up a filter panel and a list of Fixlet actions.
To learn more about an action, double-click on it from the list or right-click and choose Open from the pop-up menu. That brings up an Action document in the work area below. This dialog is available by clicking the Actions tab, selecting View>Actions or pressing the F11 key.
Add Custom Setting
This dialog box lets one edit or add a custom setting to the selected computer. Type a name for the variable in the first input box, and type the value of the variable in the second box. This dialog is available from the Edit Computer Settings dialog. Right-click on a computer from any listing and then select Edit Computer Settings from the pop-up menu.
Assign User Management Rights
The Assign User Management Rights dialog lets one add or delete computers from an operator's purview. This dialog displays the current set of computers that can be managed by the selected Console operator and lets one add or delete computers from that set. There are two buttons in this dialog:
This dialog is available by selecting the Console Operators tab, right-clicking on any operator in the list and choosing Assign User Management Rights from the pop-up menu (or choose Assign User Management Rights from the Edit menu).
Show the help files for the Console. These on-line files provide a tutorial, a description of the program and a full-text search capacity.
This dialog is available by selecting:
The Action History tab provides a listing of all the actions that have been deployed on the specified computer. Note that unlike the general action list for all computers available from the main Actions Tab, this list contains only actions targeted to the selected computer. The Action History list has the following headers:
To view more information about a particular action, double-click on it. That will bring up an Action document in the bottom panel. This dialog is available by clicking the Computers tab and double-clicking on a computer from the list. Then click the Action History tab in the Computer document window.
A Computer document is displayed in the bottom window of the Console when one open an item from any computer list. One can do this by double-clicking on the item or right-clicking and selecting Open from the pop-up menu. One sees a window as shown on
There are six tabs in a Computer document. They are:
A Fixlet document is opened whenever one open (double-click) an item in any Fixlet list. To display a Fixlet list, click the Fixlet Messages tab.
Computer: Fixlet Message History
The Fixlet Message History tab of the Computer Status dialog displays a list of all the Fixlet messages that have become relevant over time on any given computer. The list can be sorted by the column headers in both ascending or descending order. One can add or delete column headers by right-clicking on them and selecting new headers from the pop-up list. The column headers include:
This dialog is available by clicking the Computers tab and double-clicking on the desired computer in the right-hand list. Then click the Fixlet Message History tab in the Computer document window.
Computer: Management Rights
The Management Rights tab of the Computer Status dialog lists the users who are currently granted management rights to apply actions to specified computers. To edit the current set of managers, click on the Edit Management Rights button above this list. The list has three headers:
This dialog is available by clicking the Computers tab and double-clicking on a computer from the list. Then click the Management Rights tab in the Computer document window.
Computer: Retrieved Properties
The Properties tab of the Computer document lists various properties of the given computer. These properties are derived from Relevance Expressions, and one can customize them by right-clicking in the column header of any computer list in the Console. These properties help one define subsets or sorting fields for the various client computers under administration.
The default properties include, but are not limited to:
If one accidentally remove or redefine these predefined properties, one can restore them by reentering their definitions. Find out more in the sections on computer properties and Relevance Expressions.
This dialog is available by clicking the Computers tab and double-clicking on a computer from the right-hand list. Then click the Retrieved Properties tab in the Computer document window.
Computer: Relevant Fixlet Messages
The Relevant Fixlet Messages tab of the Computer document lists all the Fixlet messages that are relevant to the selected computer. This filter list is updated in real-time, refreshing its display as Fixlet messages are reevaluated.
This dialog is available by clicking the Computers tab and double-clicking on a computer from the list. Then click the Relevant Fixlet Messages tab in the Computer document window.
Computer: Computer Settings
The Computer Settings tab of a Computer document lists all the settings for the selected computer. This is a read-only display that includes locking, relays and custom settings:
This dialog is available by clicking the Computers tab and double-clicking on an computer from the list. Then click the Computer Settings tab in the Computer document window.
The Computer tab displays all the Client computers on the network, along with their properties, that one can select for deeper inquiry. When one click on the Computers tab, one sees a filter/list.
These are some of the original predefined properties, but they can be customized by defining
Retrieved Properties from the Tools menu. Using the relevance language, it is possible to retrieve a list of values (not just a single value) in a retrieved property, but these can't always be displayed properly. If this happens, a dialog box pops up to warn one, and that header field are hidden.
The right-click menu has these options:
To learn more about a computer, double-click on it from the list or right-click and choose Open from the pop-up menu. That brings up a Computer document in the work area below.
This dialog is available by clicking on the Computers tab, selecting View>Computers or pressing the F10 key.
Connect to Database
The Connect to Database dialog pops up when one select Connect from the File Menu. It lets one select which Database one wish to manage.
This dialog is available by selecting: •File>Connect . . .
Edit Computer Settings
The Edit Settings dialog allows the Console operator to alter the settings for a selected computer. (To apply settings to multiple computers, ctrl-click or shift-click to select more than one computer).
Locked. Click this button to lock the computer.
Lock Expires MM/DD/YYY HH:MM. Set the date and time for the expiration of the lock.
Run relay server on this computer. Check this box to make the selected computer a Relay. This allows a single Windows 2000 computer to take over some of the download burden from a Server. A Relay gathers a download once from the Server and then redistributes it to a designated group of Clients. This can dramatically reduce client/server bandwidth.
Assign Relays Manually. Relays can be automatically assigned. Uncheck this box to select automatic discovery (the recommended setting). If one wants to manually specify a particular relay for this Client, check this box and select the desired relays from the pull-down menus below.
Custom Settings This list box contains custom named variables that can be assigned to each computer. This is a valuable technique for organizing the network of computers, and can help to identify individual computers as well as groups. This data in the value column is editable simply by clicking in the fields and entering data.
There are three buttons to the right of the list:
Finally, there is a More Options button at the bottom of the dialog, that expands on these functions.
This dialog is available by selecting the Computers tab, right-clicking on a computer and selecting Edit Computer Settings from the pop-up menu.
Edit Multiple Computer Settings
The Edit Multiple Computer Settings dialog allows Console operators to change certain computer attributes across a specified set of computers, including locking, making the client a Relay, pointing to Relays and creating custom settings.
There are four tabbed dialogs on this screen to target and customize the settings for a selected group of Clients:
When multiple computers are selected, this dialog is available by right-clicking and selecting.
Edit Computer Settings from the pop-up menu (or select Edit Computer Settings from the Edit menu).
Edit Multiple Computer Settings—Constraints
The Constraints tab of the Edit Multiple Computer Settings dialog lets one schedule when settings are applied to the targeted Clients. Settings are issued as simple actions, which can be constrained in several ways:
When multiple computers are selected, this dialog is available by right-clicking and selecting Edit Computer Settings from the pop-up menu. Then select the Constraints tab.
Edit Multiple Computer Settings—Message
The Message tab of the Edit Multiple Computer Settings dialog. Settings are propagated to the Clients as simple actions. As with other actions, one may want to notify the user before the setting is activated on a Client. The Message tab allows one to require that an active user be present when the setting is activated, to alert the user with a specific message, and to offer certain interactive features on the message display, including the ability to see more information about the proposed setting and to cancel the proposed setting.
When this box is checked, two boxes are opened for text entry:
When multiple computers are selected, this dialog is available by right-clicking and selecting Edit Computer Settings from the pop-up menu. Then select the Message tab.
Edit Multiple Computer Settings—Settings
The Edit Multiple Computer Settings—Settings dialog allows the administrator to apply certain settings to multiple targeted computers, including locking, relays and custom variables. It includes the following controls:
Locking Status. Check this box to either lock or unlock the targeted computers. One might wish to lock a computer because it is currently being used in program development, it is in the middle of a lengthy process or because it is running specialized software. As long as a computer is locked, no actions are executed on it.
Lock Expires MM/DD/YYY HH:MM. Set the day and time for the expiration of the lock.
Relay Service Status. Check this box to enable or disable the service that connects this computer to a Relay.
Primary Relay Server. Select a primary Relay. Check the box and enter the IP address of the Windows 2000 computer that are used as the primary Relay. Any attached Clients then gather Fixlet downloads from this relay rather than directly from the Server.
Secondary Relay Server. Select a secondary Relay. Check the box and enter the IP address of the Windows 2000 computer that are used as the secondary Relay. Any attached Clients then gather Fixlet downloads from this relay if the primary relay is unavailable.
Custom Setting. This feature allows the Master Operator to create named variables that can be associated with the targeted computers.
When multiple computers are selected, this dialog is available by right-clicking and selecting.
Edit Computer Settings from the pop-up menu.
Edit Multiple Computer Settings—Target
The Edit Multiple Computer Settings—Target tab lets one target a group of Client computers for the application of certain settings, including locking, relays and custom variables.
There are three basic ways to target Client computers:
When multiple computers are selected, this dialog is available by right-clicking and selecting.
Edit Computer Settings from the pop-up menu. Then select the Target tab.
Enter Private Key
The Enter Private Key dialog requests a password. Type in the publisher password that one were given by Site Administrator. This dialog is displayed whenever an action is deployed, in order to assure that only authorized personnel are allowed to update computers on. the network.
Fixlet: Action History
The Action History tab of the Fixlet document displays a list of all the actions deployed by this particular Fixlet. In order to see something in this dialog, one typically must have an Action still pending from this Fixlet.
This dialog is available by opening a Fixlet message from any list and clicking the Action History tab.
The Fixlet Description provides an English-language description of the problem and typically provides one or more actions that can be taken to remedy it. Click on the link or button to deploy the action across the network. When the action completes, the Fixlet usually disappears, since the problem no longer pertains.
The Fixlet Properties panel (slide the panel open from the right edge or select View>Show Fixlet Message Properties) exposes the Relevance Expressions and Action buttons, so the Console operator can scrutinize them before deployment. In the panel, one sees a group of numbered Relevance Expressions that are evaluated on each Client computer to decide if the Fixlet message is relevant to that computer. Below that one can see the list of actions that are executed on the relevant computers.
This dialog is available by opening a Fixlet message from any list and clicking the Description tab.
A Fixlet document is displayed in the bottom window of the Console when one open a message from any Fixlet list. One can do this by double-clicking on the Fixlet message or right-clicking and selecting Open from the pop-up menu (see
There are three tabs in a Fixlet document. They are:
A Fixlet document is opened whenever one open an item in a Fixlet list. To display a Fixlet list, click the Fixlet Messages tab.
Fixlet Properties Panel
The Fixlet Properties panel exposes the Relevance Expressions and Action buttons, so the Console operator can scrutinize them before deployment. In the panel, one sees a group of numbered Relevance Expressions that are evaluated on each Client computer to decide if the Fixlet message is relevant to that computer. Below that one can see the list of actions that can be executed on the relevant computers. This panel is always available when a Fixlet message is being displayed, but it may be slid all the way to the right. To expand the panel, grab the vertical divider at the right of the screen and drag it to the left.
This dialog is available by selecting: •View>Show Fixlet Message Properties
Fixlet: Relevant Computers
The Relevant Computers tab of the Fixlet document displays all the networked computers that are affected by the currently selected Fixlet message. This is a filter/list view with a filter panel on the left, allowing one to narrow down the displayed list of computers. To do so, just open a retrieved property from the left panel and select a value to filter the list. Like other filter/lists in the Console, one may sort it by clicking on the column headers. If one would like to add own custom headers, select Tools>Define Retrieved Properties . . . .
This list is much like selecting the Computers tab from the main Console, but it only lists those computers that have this specific issue. Drilling down like this helps to focus efforts on one Fixlet at a time. This dialog is available by opening a Fixlet message from any list and clicking the Relevant.
Fixlet Messages Tab
The Fixlet Messages tab displays all the Fixlet messages that are relevant on the network, along with their properties, that one can select for deeper inquiry. When one click on the Fixlet Messages tab, one sees a filter/list as shown on
The right-click menu has these options:
To learn more about a Fixlet message, double-click on it from the list or right-click and choose Open from the pop-up menu. That brings up a Fixlet document in the work area below.
This dialog is available by clicking on the Fixlet Messages tab, selecting View>Fixlet Messages or pressing the F9 key.
The Hidden Fixlets dialog is a listing of all the Fixlet messages that have been “hidden” from the Console. Hiding allows Console operators to indicate that they are no longer interested in listing the specified Fixlet message, even though it is relevant. Hidden Fixlet messages are still evaluated, even though they aren't displayed. The management of hidden Fixlet messages is local, and each Console keeps its own record of which Fixlet messages are hidden or not.
One can hide Fixlet messages by right-clicking on them from the Fixlet list and choosing “Hide Fixlet Message” from the pop-up menu.
One can also unhide—or restore—Fixlet messages from this interface. Click on the Fixlet message in the list, then click the Restore Fixlet button.
The list header includes the following fields:
This dialog is available by selecting: •View>Hidden Fixlets . . . .
Main Console Window
The Main Console window (see
Fixlet Messages: Displays a list of Fixlet messages that are relevant on the various Client computers on the network.
The Manage Sites dialog brings up a list of the current set of Fixlet site subscriptions.
Fixlet Site Subscription List:
Add Site . . . To add a site, click this button. It brings up a Windows Open dialog, and lets one subscribe to a Fixlet site by selecting its masthead. These mastheads are usually saved in a masthead folder.
Properties . . . Click this button to view the properties of this site.
This dialog is available by selecting: •Tools>Manage Sites . . . .
Operator: Administered Computers
The Administered Computers tab of the Console Operator document displays a filter/list of all the computers administered by the selected operator. Like any other computer list, one can filter and sort it by retrieved properties. That means one can use own custom-created properties to parcel out administrative rights. One might use a retrieved property, for instance, to match up specific applications to experts in organization. Or one could connect departmental IT managers to their own domains, automatically. This list is similar to other computer lists in the Console, but it is specific to the selected operator, letting one focus on one person at a time. This dialog is available by double-clicking on an operator from any Console Operator list and selecting the Administered Computers tab.
Console Operator Document
A Console Operator document is displayed in the bottom window of the Console when one open an item from any Console Operator list. One can do this by double-clicking on the item or right-clicking and selecting Open from the pop-up menu (see
There are three tabs in a Console Operator document. They are:
A Console Operator document is opened whenever one open an item in a Console Operator list. To display a Console Operator list, click the Console Operators tab.
Operator: Issued Actions
The Issued Actions tab of the Console Operator document displays a filter/list of all the actions that have been deployed by the selected operator. Like any other action list, one can filter and sort it by various properties. This list is similar to other action lists in the Console, but it is specific to the selected operator, letting one focus on one person at a time.
This dialog is available by double-clicking on an operator from any Console Operator list and selecting the Issued Actions tab.
Operator: Management Rights Assignment
The Management Rights Assignment tab of the Console Operator document displays a retrieved property tree. If there were any management rights assigned on the basis of a retrieved property (for instance, based on a computer setting named “department”) one sees them here. In this example, as people changed from one department to another, they are automatically handed over to a new Console operator. This is a read-only display. To alter these settings, right-click on an operator from any Console Operator list and select Assign User Management Rights from the pop-up menu.
This dialog is available by double-clicking on an operator from any Console Operator list and selecting the Management Rights Assignment tab.
Console Operators Tab
The Console Operators tab displays all the Console operators authorized for the network, which one can select for individual viewing. When one clicks on the Console Operators tab, one sees a filter/list, as shown in
The right-click menu has these options:
To learn more about a Console operator, double-click on a name from the list or right-click and choose Open from the pop-up menu. That brings up a Console Operator document in the work area below.
This dialog is available by clicking on the Console Operators tab, selecting View>Console Operators or pressing the F12 key.
The Preferences dialog lets one adjust certain system-wide parameters:
Refresh list every XX seconds: Controls how often the Fixlet display is updated. The default setting causes the Database to be queried every 15 seconds. More frequent updates cause more the network traffic, but less frequent updates increase the response time. As the Database increases in size, a longer refresh rate may be desirable. In practice, 15 seconds provides a good balance between latency and bandwidth concerns.
Send heartbeat every XX minutes: Controls how often the Client computers check in with the Server to update their status. Each time a Client sends a heartbeat, it includes any retrieved property values which have changed. 15 minutes is the default value.
Mark as offline after XX minutes: Controls how long to wait after the last heartbeat before a computer is declared to be offline. The default is 50 minutes.
This dialog is available by selecting: •File>Preferences
The Retrieved Properties dialog contains a list of computer properties retrieved from each Client. This list forms the basis of all client listings in the Console. These properties are used as column headers whenever the client computers are listed. In addition, these properties are used to target or filter computers for Fixlet messages or actions.
There are several properties listed as defaults in the top panel, but one can add to these and delete the optional ones by using the buttons on the right:
If one change any of the pre-installed properties, one can restore them by re-entering the appropriate relevance expressions. See Restoring Column Headings.
Some of the properties (such as the ID and the relay status) are essential to the proper functioning of the Console, and may not be renamed or deleted.
This dialog is available two ways:
The Site Properties dialog displays information about the selected Fixlet site, including details about the Site publisher and the precise URLs from which the content has been gathered. The dialog box shows e-mail addresses for user feedback and the recommended gather frequency. For instance, a typical Fixlet site may have a daily subscription and be signed by both a signing authority and a software or hardware vendor.
This dialog is available by selecting: •Tools>Manage Sites . . . >Select a site>Properties button.
The Take Action dialog. When one click on an action button, this dialog pops up, letting one specify exactly how the selected actions are to be deployed to the computers on the network. It contains four tabs:
When one decide to take an action, click OK. One needs to enter a password before the Console issues the action. When one do, a progress dialog pops up to keep one posted on the deployment. This dialog is available by opening a Fixlet message from any list and then clicking on an action button.
Take Action: Constraints
The Constraints tab of the Take Action dialog lets one schedule actions, specify whether the user is needed and filter certain computers.
This dialog is available by selecting a Fixlet message from any list, then clicking an action button. From the Take Action dialog, select the Constraints tab.
Take Action: Execution
The Execution tab of the Take Action dialog. When an action becomes relevant, this dialog lets one adjust how often it are applied, how to deal with failure and whether or not to reboot the Client after the action is applied.
If the Fixlet message becomes relevant again after this action has successfully executed, automatically reapply this action. Check this box to keep reapplying this action whenever it becomes relevant.
On failure, retry XX times: Check this box to retry the action in case of a failure. If an action fails, it may be that the user dismissed it or that the computer crashed or was otherwise unable to execute the action. Select a number of retry attempts (the default is 3) and then select a condition for trying again from the choices below:
Force restart after XX seconds. This option allows a waiting period before restarting the computer. A countdown dialog appears on the Client to warn the user of the impending restart.
Force shutdown after XX seconds. This option allows a waiting period before shutting down the computer. A countdown dialog appears on the Client to warn the user of the impending shutdown.
Distribute execution of the action over MM minutes to reduce the network load: By checking this box, one can force the program to space out the execution of actions. This can be useful to reduce the load on the network in the case of bandwidth-intensive actions. It is especially useful for allowing Relays to effectively service hundreds of attached Clients.
This dialog is available by selecting a Fixlet message from any list, then clicking an action button. From the Take Action dialog, select the Execution tab.
Take Action: Message
The Message tab of the Take Action dialog. Ordinarily, the system applies actions in the background, without bothering any end user who may be present. There are, however, occasions in which the Console operator might prefer that the action be taken only with end-user involvement. The Message tab in the Take Action dialog box allows the operator to require that an active user be present when the action is run, to alert the user with a specific message, and to offer certain interactive features on the message display, including the ability to see more information about the proposed action and to cancel the proposed action.
Display message before running action: Check this box if one want to deliver a message. When this box is checked, two boxes are opened for text entry:
This dialog is available by selecting a Fixlet message from any list, then clicking an action button. From the Take Action dialog, select the Message tab.
Take Action: Relevance
The Relevance tab of the Take Action dialog lets one determine what criteria are used to judge when a computer is considered to be fixed. Typically, the original Fixlet is designed to trigger only when it becomes relevant to the given computer. Fixing the problem also deactivates the trigger, so the Fixlet is no longer relevant (it becomes FALSE). In other words, a computer is considered to be fixed when the Fixlet no longer applies. That is the automatic solution and is the default setting (top button).
There may be reasons to specify different criteria provides three options:
Consider a computer to be “Fixed” when:
This dialog is available by selecting a Fixlet message from any list, then clicking an action button. From the Take Action dialog, select the Relevance tab.
Take Action: Action Script
The Action Script tab of the Take Action dialog lets one improvise own action scripts. We highly recommend that one use the action scripts that come with each Fixlet. But should one want to customize the scripts for any reason, one can do it here. There are two buttons in this dialog:
The Target tab of the Take Action dialog. When an action is relevant, the Console operator can select, or target, a subset of users to receive the action. There are two radio buttons at the top of this dialog:
Note that one can filter this computer list by selecting items from the tree view in the left panel. Once one click OK, the selection of computers in this list are frozen—the retrieved values is not reevaluated before the action is deployed. Thus, if a computer is affected by this problem in the future, it is not covered by this option. It triggers the same Fixlet, but requires one to target it again.
These options grant one great power in the deployment of Fixlet actions. Think carefully about choices here. The first button is the safest, since it describes a static set of computers that one wishes to target. The second choice is more powerful, because it continues to evaluate and automatically deploy relevant actions, but it could also have long-term consequences that one should consider.
This dialog is available by selecting a Fixlet message from any list, then clicking an action button. From the Take Action dialog, select the Target tab.
View Action Info
The View Action Info dialog displays information on a specific action for a given computer.
This dialog is available from any action document in the bottom panel. Select the Reported Computers tab, right-click on a computer and select Show Action Info from the pop-up menu (or select Show Action Info from the Edit menu). One can also open this dialog from the Action History tab of any Computer document.
View Web Reports
The View Web Reports dialog. This dialog provides access to Web reports which are collected from various Servers and aggregated into a set of HTML reports. These include summaries of the history and status of Fixlet messages and Actions across extended the networks of computers. These reports can be used to track software deployments and compliance across a global the network of independent LANs.
To view a Web report, select a Server URL and click the Launch Web Reports button.
This dialog is available by selecting:
Although the invention is described herein with reference to the preferred embodiment, one skilled in the art will readily appreciate that other applications may be substituted for those set forth herein without departing from the spirit and scope of the present invention. Accordingly, the invention should only be limited by the Claims included below.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5586304||Sep 8, 1994||Dec 17, 1996||Compaq Computer Corporation||Automatic computer upgrading|
|US6123737||May 21, 1997||Sep 26, 2000||Symantec Corporation||Push deployment of software packages using notification transports|
|US6151643||Jun 7, 1996||Nov 21, 2000||Networks Associates, Inc.||Automatic updating of diverse software products on multiple client computer systems by downloading scanning application to client computer and generating software list on client computer|
|US6161218||Jan 16, 1996||Dec 12, 2000||Sun Microsystems Inc.||Software patch architecture|
|US6233449 *||Aug 24, 1998||May 15, 2001||Telefonaktiebolaget L M Ericsson (Publ)||Operation and maintenance control point and method of managing a self-engineering telecommunications network|
|US6233612 *||Aug 31, 1998||May 15, 2001||International Business Machines Corporation||Dynamic network protocol management information base options|
|US6237144||Sep 21, 1998||May 22, 2001||Microsoft Corporation||Use of relational databases for software installation|
|US6240394 *||Dec 12, 1996||May 29, 2001||Catalina Marketing International, Inc.||Method and apparatus for automatically generating advisory information for pharmacy patients|
|US6240451||Nov 12, 1997||May 29, 2001||Punch Networks Corporation||Method and apparatus for automatically disseminating information over a network|
|US6256668||Oct 9, 1998||Jul 3, 2001||Microsoft Corporation||Method for identifying and obtaining computer software from a network computer using a tag|
|US6289510||Sep 2, 1998||Sep 11, 2001||Fujitsu Limited||Online program-updating system and computer-readable recording medium storing a program-updating program|
|US6321258||Dec 11, 1997||Nov 20, 2001||Hewlett-Packard Company||Administration of networked peripherals using particular file system|
|US6324691||Nov 12, 1998||Nov 27, 2001||Hewlett-Packard Company||Manufacture of software distribution media packages from components resident on a remote server source|
|US6324693||Aug 17, 1999||Nov 27, 2001||Siebel Systems, Inc.||Method of synchronizing independently distributed software and database schema|
|US6327617||Apr 25, 2000||Dec 4, 2001||Microsoft Corporation||Method and system for identifying and obtaining computer software from a remote computer|
|US6330715||May 19, 1998||Dec 11, 2001||Nortel Networks Limited||Method and apparatus for managing software in a network system|
|US6345386||Sep 21, 1998||Feb 5, 2002||Microsoft Corporation||Method and system for advertising applications|
|US6347396||Mar 11, 1999||Feb 12, 2002||Telefonaktiebolaget Lm Ericsson (Publ)||Disturbance free update of data|
|US6347398||Nov 8, 1999||Feb 12, 2002||Microsoft Corporation||Automatic software downloading from a computer network|
|US6353902 *||Jun 8, 1999||Mar 5, 2002||Nortel Networks Limited||Network fault prediction and proactive maintenance system|
|US6353926||Jul 15, 1998||Mar 5, 2002||Microsoft Corporation||Software update notification|
|US6353928||Jan 4, 1999||Mar 5, 2002||Microsoft Corporation||First run installer|
|US6360366||Oct 15, 1999||Mar 19, 2002||Managesoft Corporation||Systems and methods for automatic application version upgrading and maintenance|
|US6363524 *||Sep 10, 1999||Mar 26, 2002||Hewlett-Packard Company||System and method for assessing the need for installing software patches in a computer system|
|US6378128||Oct 8, 1998||Apr 23, 2002||Microsoft Corporation||System and method for dynamically modifying an install-set|
|US6381742||Jun 19, 1998||Apr 30, 2002||Microsoft Corporation||Software package management|
|US6389589||Sep 21, 1998||May 14, 2002||Microsoft Corporation||Class store schema|
|US6405250 *||Jan 25, 1999||Jun 11, 2002||Lucent Technologies Inc.||Network management system based on passive monitoring and proactive management for formulation behavior state transition models|
|US6418554||Sep 21, 1998||Jul 9, 2002||Microsoft Corporation||Software implementation installer mechanism|
|US6449642||Sep 15, 1998||Sep 10, 2002||Microsoft Corporation||Method and system for integrating a client computer into a computer network|
|US6460175||Jul 18, 1997||Oct 1, 2002||International Business Machines Corporation||Program product for modular, parallel, remote software installation with repeatable, externally-invocable steps|
|US6477703 *||Jun 29, 1999||Nov 5, 2002||Hewlett-Packard Company||Software patch selection tool|
|US6493594||Jun 4, 1999||Dec 10, 2002||Lucent Technologies Inc.||System and method for improved software configuration and control management in multi-module systems|
|US6496977||Oct 21, 1999||Dec 17, 2002||International Business Machines Corporation||Method and system for implementing network filesystem-based aid for computer operating system upgrades|
|US6523166||Sep 21, 1998||Feb 18, 2003||Microsoft Corporation||Method and system for on-demand installation of software implementations|
|US6532491||Nov 5, 1997||Mar 11, 2003||Novell, Inc.||Processes and apparatuses for managing network devices|
|US6557054||Apr 20, 2000||Apr 29, 2003||Richard R. Reisman||Method and system for distributing updates by presenting directory of software available for user installation that is not already installed on user station|
|US6564369||Aug 20, 1998||May 13, 2003||Pearson Technical Software, Inc.||Conflict checking using configuration images|
|US6574537 *||Feb 5, 2001||Jun 3, 2003||The Boeing Company||Diagnostic system and method|
|US6594692||Apr 29, 1996||Jul 15, 2003||Richard R. Reisman||Methods for transacting electronic commerce|
|US6594759||Dec 29, 1998||Jul 15, 2003||Esignx Corporation||Authorization firmware for conducting transactions with an electronic transaction system and methods therefor|
|US6611862||Apr 20, 2000||Aug 26, 2003||Richard R. Reisman||User station software that controls transport and presentation of content from a remote source|
|US6622146 *||Jun 29, 1999||Sep 16, 2003||Fujitsu Limited||System managing method and apparatus for decreasing a load applied to a common processing unit|
|US6654714||May 22, 1998||Nov 25, 2003||Micron Technology, Inc.||Method and system for selecting compatible processors to add to a multiprocessor computer|
|US6658464||Apr 20, 2000||Dec 2, 2003||Richard R. Reisman||User station software that controls transport, storage, and presentation of content from a remote source|
|US6658489||Mar 29, 2000||Dec 2, 2003||International Business Machines Corporation||Method for replacing a device driver during system operation|
|US6725242||Jan 2, 2001||Apr 20, 2004||Fujitsu Services Limited||Multiple-computer data processing system and method with time-versioned data storage|
|US6725452||Jun 1, 2000||Apr 20, 2004||Aduoa, Inc.||Method for resolving dependency conflicts among multiple operative entities within a computing environment|
|US6735766||Mar 3, 1999||May 11, 2004||Microsoft Corporation||Method and computer-readable medium for installing an upgrade to an application program|
|US6745766||Mar 28, 2001||Jun 8, 2004||Mallinckrodt Holdings B.V.||Heat and moisture exchanger|
|US6751661 *||Jun 22, 2000||Jun 15, 2004||Applied Systems Intelligence, Inc.||Method and system for providing intelligent network management|
|US6763517 *||Feb 12, 2001||Jul 13, 2004||Sun Microsystems, Inc.||Automated analysis of kernel and user core files including searching, ranking, and recommending patch files|
|US6769009||Apr 20, 2000||Jul 27, 2004||Richard R. Reisman||Method and system for selecting a personalized set of information channels|
|US6789255||Sep 26, 2000||Sep 7, 2004||Microsoft Corporation||Determining update availability via set intersection over a sub-optimal pathway|
|US6802061||Dec 21, 2001||Oct 5, 2004||Microsoft Corporation||Automatic software downloading from a computer network|
|US6804663||Sep 21, 1998||Oct 12, 2004||Microsoft Corporation||Methods for optimizing the installation of a software product onto a target computer system|
|US6836794||Sep 21, 1998||Dec 28, 2004||Microsoft Corporation||Method and system for assigning and publishing applications|
|US6904457||Jan 5, 2001||Jun 7, 2005||International Business Machines Corporation||Automatic firmware update of processor nodes|
|US6920631||Nov 26, 2001||Jul 19, 2005||Microsoft Corporation||Software installation and validation using custom actions|
|US6922831||Aug 2, 2000||Jul 26, 2005||Gateway Inc.||Method and system for providing software utilizing a restore medium and a network|
|US6941453||Jan 27, 2004||Sep 6, 2005||Bitfone Corporation||System and method for determining if a device needs to be updated and locating and invoking an update agent to update the firmware or software in the device|
|US6971094||Feb 22, 2000||Nov 29, 2005||Hewlett-Packard Development Company, L.P.||Deployed agent used in the installation and maintenance of software|
|US6996815||Nov 29, 2000||Feb 7, 2006||Microsoft Corporation||Method and software tools for intelligent service pack installation|
|US6996819||Sep 10, 1999||Feb 7, 2006||Unisys Corporation||Method for efficiently downloading SCSI and SERVO firmware to SCSI target controllers|
|US7398272 *||Mar 19, 2004||Jul 8, 2008||Bigfix, Inc.||Enterprise console|
|US20010032091 *||Dec 18, 2000||Oct 18, 2001||Schultz Michael A.||Method and apparatus for providing intranet/web based programs|
|US20020112200||Feb 12, 2001||Aug 15, 2002||Hines George W.||Automated analysis of kernel and user core files including searching, ranking, and recommending patch files|
|US20030033396 *||Aug 6, 2001||Feb 13, 2003||Mccall John E.||Method and system for providing management information|
|JP2001318814A||Title not available|
|JP2002247033A *||Title not available|
|JP2002523841A||Title not available|
|JP2003076434A *||Title not available|
|WO2003040944A1||Nov 12, 2002||May 15, 2003||Bigfix Inc||Formalizing, diffusing, and enforcing policy advisories and monitoring policy compliance in the management of networks|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8495157||Sep 14, 2010||Jul 23, 2013||International Business Machines Corporation||Method and apparatus for distributed policy-based management and computed relevance messaging with remote attributes|
|US8879713 *||Aug 15, 2012||Nov 4, 2014||Nuance Communications, Inc.||Optimized method to select and retrieve a contact center transaction from a set of transactions stored in a queuing mechanism|
|US8966110||Sep 9, 2010||Feb 24, 2015||International Business Machines Corporation||Dynamic bandwidth throttling|
|US9015531 *||Oct 31, 2012||Apr 21, 2015||International Business Machines Corporation||Preventing distribution of a failure|
|US9152602||Apr 16, 2012||Oct 6, 2015||International Business Machines Corporation||Mechanisms for evaluating relevance of information to a managed device and performing management operations using a pseudo-agent|
|US20100332640 *||Sep 14, 2010||Dec 30, 2010||Dennis Sidney Goodrow||Method and apparatus for unified view|
|US20110066841 *||Sep 14, 2010||Mar 17, 2011||Dennis Sidney Goodrow||Platform for policy-driven communication and management infrastructure|
|US20120314847 *||Dec 13, 2012||International Business Machines Corporation||Optimized method to select and retrieve a contact center transaction from a set of transactions stored in a queuing mechanism|
|US20130159793 *||Oct 31, 2012||Jun 20, 2013||International Business Machines Corporation||Preventing Distribution of a Failure|
|U.S. Classification||707/613, 707/781, 709/203, 707/636, 707/728|
|International Classification||G06F17/30, H04L9/00, G06F, G06F9/445, G06F15/16|
|Cooperative Classification||Y10S707/99935, H04L63/1433, Y10S707/959, G06F8/65, Y10S707/951|
|European Classification||G06F8/65, H04L63/14C|
|Apr 13, 2011||AS||Assignment|
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BIGFIX, INC.;REEL/FRAME:026115/0369
Effective date: 20110223
|Jun 19, 2015||REMI||Maintenance fee reminder mailed|
|Nov 8, 2015||LAPS||Lapse for failure to pay maintenance fees|
|Dec 29, 2015||FP||Expired due to failure to pay maintenance fee|
Effective date: 20151108