US20070106749A1 - Software distribution via stages - Google Patents

Software distribution via stages Download PDF

Info

Publication number
US20070106749A1
US20070106749A1 US11/614,819 US61481906A US2007106749A1 US 20070106749 A1 US20070106749 A1 US 20070106749A1 US 61481906 A US61481906 A US 61481906A US 2007106749 A1 US2007106749 A1 US 2007106749A1
Authority
US
United States
Prior art keywords
software
canceled
nodes
computers
via
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/614,819
Inventor
Daniel Melchione
Oyland Wong
Ricky Huang
Charles Vigue
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Secure Resolutions Inc
Original Assignee
Secure Resolutions Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US37521502P priority Critical
Priority to US10/421,645 priority patent/US7178144B2/en
Application filed by Secure Resolutions Inc filed Critical Secure Resolutions Inc
Priority to US11/614,819 priority patent/US20070106749A1/en
Publication of US20070106749A1 publication Critical patent/US20070106749A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/34Network-specific arrangements or communication protocols supporting networked applications involving the movement of software or configuration parameters

Abstract

Software can be automatically distributed in stages. An administrator can specify a stage indicating software to be distributed to nodes in a network. The nodes can be organized into groups. Administration functions can be performed via an application service provider scenario. For example, a browser-based user interface can be used to configure nodes and indicate an appropriate software stage for the nodes. Agent software at a node can query a data center to discover what software is appropriate. Software of the proper stage can be provided and installed. The software can be provided via an application service provider scenario, and automatic installation can be achieved even if the nodes are behind a firewall. A versionless arrangement can be implemented.

Description

    PRIORITY CLAIM
  • This application is a divisional of U.S. Non-provisional application Ser. No. 10/421,645, filed Apr. 22, 2003, which claims the benefit of U.S. Provisional Patent Application No. 60/375,215, filed Apr. 23, 2002, both of which are hereby incorporated herein by reference.
  • CROSS-REFERENCE TO OTHER APPLICATIONS
  • The U.S. provisional patent applications No. 60/375,216, Huang et al., entitled “Software Administration in an Application Service Provider Scenario via Configuration Directives”; No. 60/375,176, Vigue et al., entitled, “Fault-tolerant Distributed Computing Applications”; No. 60/375,174, Melchione et al., entitled, “Providing Access To Software Over a Network via Keys”; No. 60/375,154, Melchione et al., entitled, “Distributed Server Software Distribution,”; and No. 60/375,210, Melchione et al., entitled, “Executing Software In A Network Environment”; all filed Apr. 23, 2002, are hereby incorporated herein by reference.
  • TECHNICAL FIELD
  • The invention relates to software distribution and, more particularly, to software distribution in stages across a network of nodes such as computers.
  • COPYRIGHT AUTHORIZATION
  • A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
  • BACKGROUND
  • Organizations have become increasingly dependent on computers to maintain high levels of productivity. Administering a large number of computers in an organization can be a burdensome task. The burden is further compounded when the computers are scattered throughout various locations and departments of the organization.
  • One particularly challenging aspect of computer administration relates to software upgrades. It may be desirable to adopt new or upgraded software to take advantage of new or enhanced functionality. However, when software is installed, unanticipated problems may arise. Such problems can range from minor annoyances to a complete disruption of functionality.
  • As a result, those responsible for the administration of an organization's computers may be reluctant to install new software until after they have had an opportunity to test the effect of installing the software. During testing, solutions for overcoming disruptions can be found, or it may be discovered that the software needs further work by the software developer.
  • Software installation to a set of computers in an organization is thus a burdensome task that can disrupt an organization if not properly implemented. Improvements in the field of software installation are needed.
  • SUMMARY
  • The above issues can be problematic to administrators, whether they manage a small network or an enterprise having thousands of computers spread over multiple locations.
  • Software can be automatically distributed to nodes in a network. However, automatic installation can cause its own problems. For example, if installation of the software is causing disruption, automatic installation simply automatically disrupts the organization.
  • In various embodiments described herein, software can be released in a plurality of stages. For example, one or more nodes of a network can be designated as to be distributed software of a particular stage. When software is to be distributed to a node, a software release associated with the specified stage is selected for distribution. To assist in administration, nodes can be placed in groups, and the groups can be associated with a particular stage to associate nodes in the group with the stage.
  • In some embodiments, software administration can be accomplished via an application service provider scenario. For example, nodes can be placed in groups via an application service provider scenario, and the groups can be associated with a stage via an application service provider scenario.
  • In an application service provider scenario, communication between nodes and an application service provider data center can be accomplished via an HTTP-based protocol. A node can include an agent that periodically queries the application service provider data center to discover which software is to be installed on the node. In this way, software distribution can be accomplished even if the nodes are behind a firewall. For example, if a query comes from a node, a response can be sent based on the node's identity and a stage associated with it.
  • When software of a particular stage becomes available, a database can be updated appropriately, and automated distribution of the software takes place according to whether a node is designated as to be distributed software of the stage. A versionless arrangement can be implemented whereby software versions are transparent to the administrator.
  • A distribution threshold can be designated in some arrangements to specify a threshold within a stage. The distribution threshold can be helpful in avoiding high peaks in network traffic.
  • An appropriate stage can be incorporated into a set of configuration directives and associated with a group of nodes to facilitate software administration. If desired, an application service provider scenario can be used to specify the configuration directives and associate them with a group of nodes.
  • Responsibilities for various portions of the system can be divided so that an application service provider controls various aspects to relieve software administrators of various duties.
  • Additional features and advantages will be made apparent from the following detailed description of illustrated embodiments, which proceeds with reference to the accompanying drawings.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is an illustration of an exemplary application service provider scenario.
  • FIG. 2 is an illustration of an exemplary arrangement by which software administration can be accomplished via an application service provider scenario.
  • FIG. 3 depicts an exemplary user interface by which software administration can be accomplished in an application service provider scenario.
  • FIG. 4 illustrates an exemplary business relationship accompanying an application service provider scenario, such as that shown in FIG. 1 or 2.
  • FIG. 5 shows an exemplary system by which software is distributed via stages.
  • FIG. 6 illustrates software releases categorized according to stage.
  • FIG. 7 depicts an exemplary arrangement using distribution indices.
  • FIG. 8 is a flow chart showing an exemplary method of incorporating software functionality into a system by which the software can be administered via an application service provider scenario.
  • FIG. 9 is a flow chart depicting an exemplary method for accomplishing software administration via an application service provider scenario.
  • FIG. 10 is a flow chart depicting an exemplary method for accomplishing a software administration function over a network.
  • FIG. 11 depicts an exemplary scenario in which a vendor hosts application services for more than one organization.
  • FIG. 12 is an exemplary arrangement involving anti-virus software.
  • FIG. 13 is a screen shot showing an exemplary user interface for manipulating groups.
  • FIG. 14 is a screen shot showing an exemplary user interface for manipulating policies.
  • FIG. 15 is a screen shot showing an exemplary user interface for manipulating configuration directives related to an agent.
  • FIG. 16 is a screen shot showing an exemplary user interface for manipulating configuration directives related to virus infection resolution.
  • FIG. 17 is a screen shot showing an exemplary user interface for manipulating configuration directives related to scheduled tasks.
  • FIGS. 18A-18J show an exemplary database schema for use with an implementation of the technologies described herein.
  • FIGS. 19A-19B show another exemplary database schema for use with an implementation of the technologies described herein.
  • DETAILED DESCRIPTION Application Service Provider Overview
  • The embodiments described herein can be implemented in an application service provider scenario. In particular embodiments, software administration can be accomplished via an application service provider scenario.
  • An exemplary application service provider scenario 100 is shown in FIG. 1. In the scenario 100, a customer 112 sends requests 122 for application services to an application service provider vendor 132 via a network 142. In response, the vendor 132 provides application services 152 via the network 142. The application services 152 can take many forms for accomplishing computing tasks related to a software application or other software.
  • To accomplish the arrangement shown, a variety of approaches can be implemented. For example, the application services can include delivery of graphical user interface elements (e.g., hyperlinks, graphical checkboxes, graphical pushbuttons, and graphical form fields) which can be manipulated by a pointing device such as a mouse. Other application services can take other forms, such as sending directives or other communications to devices of the vendor 132.
  • To accomplish delivery of the application services 152, a customer 112 can use client software such as a web browser to access a data center associated with the vendor 132 via a web protocol such as an HTTP-based protocol (e.g., HTTP or HTTPS). Requests for services can be accomplished by activating user interface elements (e.g., those acquired by an application service or otherwise) or automatically (e.g., periodically or as otherwise scheduled) by software. In such an arrangement, a variety of networks (e.g., the Internet) can be used to deliver the application services (e.g., web pages conforming to HTML or some extension thereof) 152 in response to the requests. One or more clients can be executed on one or more devices having access to the network 142. In some cases, the requests 122 and services 152 can take different forms, including communication to software other than a web browser.
  • The technologies described herein can be used to administer software (e.g., one or more applications) across a set of administered devices via an application services provider scenario. Administration of software can include software installation, software configuration, software management, or some combination thereof. FIG. 2 shows an exemplary arrangement 200 whereby an application service provider provides services for administering software (e.g., administered software 212) across a set of administered devices 222. The administered devices 222 are sometimes called “nodes.”
  • In the arrangement 200, the application service provider provides services for administrating instances of the software 212 via a data center 232. The data center 232 can be an array of hardware at one location or distributed over a variety of locations remote to the customer. Such hardware can include routers, web servers, database servers, mass storage, and other technologies appropriate for providing application services via the network 242. Alternatively, the data center 232 can be located at a customer's site or sites. In some arrangements, the data center 232 can be operated by the customer itself (e.g., by an information technology department of an organization).
  • The customer can make use of one or more client machines 252 to access the data center 232 via an application service provider scenario. For example, the client machine 252 can execute a web browser, such as MICROSOFT INTERNET EXPLORER, which is marketed by MICROSOFT Corporation of Redmond, Wash. In some cases, the client machine 252 may also be an administered device 222.
  • The administered devices 222 can include any of a wide variety of hardware devices, including desktop computers, server computers, notebook computers, handheld devices, programmable peripherals, and mobile telecommunication devices (e.g., mobile telephones). For example, a computer 224 may be a desktop computer running an instance of the administered software 212.
  • The computer 224 may also include an agent 228 for communicating with the data center 232 to assist in administration of the administered software 212. In an application service provider scenario, the agent 228 can communicate via any number of protocols, including HTTP-based protocols.
  • The administered devices 222 can run a variety of operating systems, such as the MICROSOFT WINDOWS family of operating systems marketed by MICROSOFT Corporation; the Mac OS family of operating systems marketed by APPLE Computer Incorporated of Cupertino, Calif.; and others. Various versions of the operating systems can be scattered throughout the devices 222.
  • The administered software 212 can include one or more applications or other software having any of a variety of business, personal, or entertainment functionality. For example, one or more anti-virus, banking, tax return preparation, farming, travel, database, searching, multimedia, security (e.g., firewall) and educational applications can be administered. Although the example shows that an application can be managed over many nodes, the application can appear on one or more nodes.
  • In the example, the administered software 212 includes functionality that resides locally to the computer 224. For example, various software components, files, and other items can be acquired by any of a number of methods and reside in a computer-readable medium (e.g., memory, disk, or other computer-readable medium) local to the computer 224. The administered software 212 can include instructions executable by a computer and other supporting information. Various versions of the administered software 212 can appear on the different devices 222, and some of the devices 222 may be configured to not include the software 212.
  • FIG. 3 shows an exemplary user interface 300 presented at the client machine 252 by which an administrator can administer software for the devices 222 via an application service provider scenario. In the example, one or more directives can be bundled into a set of directives called a “policy.” In the example, an administrator is presented with an interface by which a policy can be applied to a group of devices (e.g., a selected subset of the devices 222). In this way, the administrator can control various administration functions (e.g., installation, configuration, and management of the administered software 212) for the devices 222. In the example, the illustrated user interface 300 is presented in a web browser via an Internet connection to a data center (e.g., as shown in FIG. 2) via an HTTP-based protocol.
  • Activation of a graphical user interface element (e.g., element 312) can cause a request for application services to be sent. For example, application of a policy to a group of devices may result in automated installation, configuration, or management of indicated software for the devices in the group.
  • In the examples, the data center 232 can be operated by an entity other than the application service provider vendor. For example, the customer may deal directly with the vendor to handle setup and billing for the application services. However, the data center 232 can be managed by another party, such as an entity with technical expertise in application service provider technology.
  • The scenario 100 (FIG. 1) can be accompanied by a business relationship between the customer 112 and the vendor 132. An exemplary relationship 400 between the various entities is shown in FIG. 4. In the example, a customer 412 provides compensation to an application services provider vendor 422. Compensation can take many forms (e.g., a monthly subscription, compensation based on utilized bandwidth, compensation based on number of uses, or some other arrangement (e.g., via contract)). The provider of application services 432 manages the technical details related to providing application services to the customer 412 and is said to “host” the application services. In return, the provider 432 is compensated by the vendor 422.
  • The relationship 400 can grow out of a variety of situations. For example, it may be that the vendor 422 has a relationship with or is itself a software development entity with a collection of application software desired by the customer 412. The provider 432 can have a relationship with an entity (or itself be an entity) with technical expertise for incorporating the application software into an infrastructure by which the application software can be administered via an application services provider scenario such as that shown in FIG. 2.
  • Although not shown, other parties may participate in the relationship 400. For example, network connectivity may be provided by another party such as an Internet service provider. In some cases, the vendor 422 and the provider 432 may be the same entity. It is also possible that the customer 412 and the provider 432 be the same entity (e.g., the provider 432 may be the information technology department of a corporate customer 412).
  • EXAMPLE 1 Exemplary System Overview
  • FIG. 5 depicts an overview of an exemplary system 500 by which software can be distributed via stages. In the arrangement, a data center 512 keeps a record of releases 524 in a database 526. The releases can be associated with a particular stage (e.g., stages 1-n). Based on the stage associated with a software release, the software is distributed via a network 542 (e.g., the Internet), to various sites (e.g., the sites 550A, 550B, and 550N), which may be associated with a particular customer or customers.
  • Accordingly, different releases may appear at different sets of nodes within the system 500. In the example, a set of nodes 560A is distributed release n, some nodes 560B at site 550B are distributed release 2, while other nodes 560C at the same site are distributed release 1. At site 550C, some nodes 560D are distributed release 1, while others 560E are distributed release n. It may take time for a release to percolate through the system after it is released, so a set of machines may have a mixture of releases.
  • The releases can be of different versions. For example, release 1 could be a mature release of version 1.3 of a program, release 2 could be an early release of version 1.3 of the program, and release n could be an initial (e.g., beta) release of version 2.0 of the program. Instead of, or in addition to, a version number, a timestamp can be used. The system can appear to be versionless in that an administrator need not be concerned with the version of the software.
  • Distribution of the releases can be accomplished in any number of ways. For example, in a scenario supporting software administration, an administrator can specify which nodes are to receive which releases. Automated processing can then handle the details of distributing the software to the appropriate nodes. To relieve network congestion, the releases 524 may reside at a location other than the data center 512, and the data center 512 can provide a reference (e.g., an URL) to the releases 524 to accomplish release distribution.
  • In the example, the releases can be categorized according to stage. As software progresses in its life cycle, it typically moves from an initial stage to a later stage. After a release is made available to the system, a determination of which release is appropriate for a node can be made by consulting information that has been previously specified by an administrator to indicate which nodes are to receive software of which stage. For example, a database (e.g., the database 526) can associate a node or group of nodes with a stage, and the releases can also be associated with a stage.
  • Accordingly, distribution can be handled automatically when a release is made available to the system. In this way, administration of the software can be greatly improved, and system administrators can avoid the burden of software distribution. Because a stage can be specified by an administrator, initial (e.g., beta) versions of software can be specified for a small set of nodes (e.g., in a lab or quality assurance team). The performance and behavior of the beta software can be evaluated before a later version moves to other nodes in the network.
  • The illustrated system can use the Internet for the network 542. Also, administration can be performed via an application service provider (or “ASP”) scenario (e.g., via the Internet or some other network).
  • EXAMPLE 2 Exemplary Software Stages
  • FIG. 6 shows an exemplary set of software stages. In the example, software progresses through the n stages 610A, 610B, and 610N. A first release of the software is typically not fully functional or not fully properly functional and is associated with an initial stage (e.g. stage 610A). As modifications are made to the software, it becomes closer to a finished stage and is associated with a later stage (e.g., stage 610B). Eventually, the software reaches a level of maturity appropriate for an even later stage (e.g., stage 610N).
  • As software proceeds through the stages, any number of modifications can be made, including fixes for erroneous logic (e.g., bugs) and addition of new or enhanced functionality. It may be that more than one release is associated with a particular stage. As the software progresses through the stages, it may be assigned different version numbers (e.g., 1.0α, 1.0β2, 1.0rc 1, 1.0, 1.01, 1.2, etc.). At some point, a decision may be made whereby the entire cycle is started again, and the software returns to an early stage. Sometimes such a situation is called releasing a new version or new major version. The version numbers may be adjusted accordingly (e.g., 2.0α, 2.0β2, 2.0rc1, 2.0, 2.01, 2.2, etc.). A variety of other version schemes can be used (e.g., a major and a minor version number, a time stamp, or both).
  • During software development, a software team may continue to work on the software, but a later release can be categorized in an earlier stage. For example, new, untested functionality may be incorporated that causes the software to be categorized as a beta release, even though an earlier release of the same software had progressed beyond the beta stage.
  • If appropriate, a numerical system can be used to classify the releases into an appropriate stage. For example, software having up to 70% functionality can be classified in a first stage, and software having 95% functionality can be graduated to a second stage, and so on.
  • The software stages can be associated with appropriate identifiers. For example, a database table can contain a row for a software stage.
  • EXAMPLE 3 Distribution Threshold
  • If desired, a distribution threshold can be used within a stage. A distribution threshold can be helpful for avoiding network congestion related to distributing software of a particular stage. For example, when a software release of a particular stage becomes available, there may be a large number of nodes slated to receive the release. Accordingly, network congestion can develop as the software is distributed to the appropriate nodes.
  • A distribution threshold can be used to stagger the distribution over time. For example, nodes in a particular organization, network, subnet, or other division can be assigned a distribution threshold (e.g., between 0 and 999). When a release first becomes available, a progressing index parameter can be used to stagger distribution according to the distribution threshold. The distribution threshold can be controlled by the customer, a vendor, or the operator of a data center. In some cases, a customer may provide additional compensation to be awarded a particular distribution threshold (e.g., a particularly early or a particularly late threshold).
  • The index parameter can start at a low number and progress to a higher number over time. As the parameter reaches the distribution threshold for a set of nodes, the software is then distributed (or selected for distribution) to the appropriate nodes. The parameter can be controlled by the customer, a vendor, or the operator of a data center. In some cases, it may be appropriate to reduce or reset the parameter.
  • In this way, the distribution threshold can be used to avoid spikes in network traffic.
  • FIG. 7 depicts an exemplary arrangement involving distribution thresholds. In the example, there are three stages, and an organization has been assigned a distribution threshold of 500 712. Accordingly, when a distribution-controlling parameter reaches a value of 500 or higher, software of stage 1, if any, is distributed to nodes within the organization designated as to receive software of stage 1.
  • In the example, a node has been assigned a distribution threshold of 2 716. Accordingly, when the controlling parameter reaches a value of 2 or higher, software of stage 2, if any, is distributed to the node.
  • The distribution threshold can be uniform throughout each stage for a set of nodes, or the distribution threshold can take a different position within each stage if desired. Similarly, the parameter controlling distribution can also be used across plural stages, or a separate parameter can be used for each stage. If finer granularity is desired, a sub-threshold may be used.
  • Alternatively, a distribution threshold can be assigned per release. When the index parameter reaches the distribution threshold for the release, it is then selected for distribution to the appropriate nodes.
  • EXAMPLE 4 Selecting Appropriate Software
  • When selecting which software is appropriate for a node, any number of schemes can be used. For example, based on the stage and threshold associated with a node, a release may be chosen. It may be desirable to distribute software of the specified stage or later. For example, in the case of a node assigned stage 1, it may be desirable to select stage 1 software if available, but stage 2 software can be selected if available. In such a scenario, software of a later version may be specified as separate software to prevent confusion between versions (e.g., confusion between a mature release of version 1.0 and an initial release of version 2.0). In a versionless system, a the version number need not be disclosed to the users or software administrators. Alternatively, a date can be used (e.g., the most recent software out of the appropriate stages is sent or the most recent software is sent).
  • An indication of selected software can be interpreted as a directive to uninstall software not specified. For example, upon an initial release of version 2.0 for a node specified as associated with stage 1, an indication that version 2.0 is appropriate can be interpreted as a directive to uninstall the version 1.0 software).
  • EXAMPLE 5 Incorporating Software Functionality into an ASP Scenario
  • In some cases, it may be desirable to take an arbitrary piece of software and incorporate it into a system by which the software can be administered via an application service provider scenario. FIG. 8 is a flow chart showing a method 800 for accomplishing such an arrangement. The method 800 can be performed by the developer of the software or an entity specializing in application service provider scenarios which works in tandem with the software developer.
  • At 822, the software is packaged for distribution over a network. For example, software components and an installation program can be assembled into a package (e.g., according to the .CAB file specification of Microsoft Corporation).
  • At 832, the software package is incorporated into a database maintained by the application service provider (e.g., the database 526). The software package itself may reside at a separate location, and a reference to the package can be incorporated into the database.
  • At 842, the organization wishing to avail itself of software administration via the application service provider scenario is provided with appropriate network references (e.g., URL's) by which the organization can access the application services for administering the software throughout its locations.
  • As described below, the network references can be sufficient for accomplishing administration via an application provider service scenario. For example, an administrator can configure a network so that software can be distributed as described herein via the network references. In this way, distribution of software via conventional media (e.g., diskettes or CD's) can be avoided.
  • EXAMPLE 6 Application Service Provider Scenarios
  • Providing software administration services via an application service provider scenario can be challenging because typical network connections include security measures that inhibit various functionality. For example, while it may be possible to install software to a remote machine, doing so over the Internet is typically not possible because organizations employ a firewall by which certain directives originating outside the firewall are not allowed to arrive at machines inside the firewall.
  • One way to accomplish administration via an application service provider scenario is to use a protocol which has been designated as relatively safe and is typically allowed to pass through the firewall (e.g., an HTTP-based protocol). Some functions related to administration can be accomplished in other ways, such as via distribution of programs embedded in or referred to within relatively safe protocols (e.g., a control conforming to the ActiveX specification of Microsoft Corporation embedded in a web page). Other arrangements are possible. For example, in a scenario in which the application service provider (e.g., an IT department) maintains a data center within the firewall, other protocols may be used. However, an HTTP-based protocol can also be used in such a scenario.
  • FIG. 9 shows an exemplary method 900 for accomplishing software administration via an application service provider scenario. At 912, a remote deployment utility (e.g., with push functionality) is provided via a network reference (e.g., an URL). For example, the network reference can refer to a location (e.g., a web server) maintained by an application service provider, and an administrator can acquire the remote deployment utility via the location. The remote deployment utility can then be installed behind the firewall so that an administrator can direct installation of appropriate software at nodes within the network (e.g., behind the firewall). Further details relating to the remote deployment installation utility can be found in U.S. Provisional Application No. 60/375,210, Melchione et al., entitled, “Executing Software In A Network Environment,” filed Apr. 23, 2002, which is hereby incorporated herein by reference.
  • At 922, agent software is installed at nodes to be administered via the remote deployment utility. For example, an administrator can select a list of nodes at which the agent software is to be installed, and the remote deployment utility sends the software to the nodes and arranges for it to be installed at the nodes over a network connection (e.g., without having to physically visit the nodes).
  • At 932, an administrative user interface is provided via a network reference. For example, the network reference can refer to a location (e.g., a web server) maintained by an application service provider. The administrative user interface can provide a variety of functions by which an administrator can administer software at administered nodes, including distributing software in stages as described herein.
  • At 942, administration information is collected from an administrator via the network. For example, various web pages can be presented by which an administrator selects various options and configuration directives. The options and configuration directives can include placing nodes into named groups and associating the named groups with a software stage. The user interface and administration information can be communicated via an HTTP-based protocol. Accordingly, the information can pass through a firewall.
  • At 952, the agent software at the administered nodes periodically queries the application service provider (e.g., a data center) to determine what configuration directives need to be carried out at the node. The queries and returned information can be communicated via an HTTP-based protocol. Accordingly, the information can pass through a firewall.
  • In the case of software distribution, the application service provider can provide a list of software (e.g., listing a software package containing software of a stage as designated by the administrator) that should reside at the node at 962 in response to a query by an agent.
  • At 972, the agent can pull down the appropriate software (e.g., a software package) and install it at the node 982.
  • In the case of an application service provider scenario using the Internet, software administration can thus be accomplished from any device having access to the Internet. Thus, a network behind a firewall can be administered via the Internet, even by an administrator employing a device (e.g., a web browsing computer) outside the firewall.
  • FIG. 10 depicts an exemplary method 1000 for accomplishing a software administration function over a network. In the example, software of an appropriate stage is provided to a node behind a firewall. However, other arrangements are possible, such as providing software within the firewall.
  • At 1002, an HTTP-based protocol request is sent to an application service provider (e.g., a web server at a data center). For example, an agent can send a GET or POST request by which certain parameters can be placed in the request. For instance, a node identifier can be passed to the server. The request can be periodically generated (e.g., according to 952 of FIG. 9). The frequency of the request can be controlled by an administrator via manipulation of web pages.
  • At 1012, in response to the request, the server provides a list of software that should be installed at the requesting node. The list can be generated with reference to the stage information for the node. For example, if the node belongs to a group designated to receive software of stage 2, a list of such software can be provided. A distribution threshold can also be taken into account.
  • At 1022, the list of software provided is compared with the software installed on the node (e.g., by the agent).
  • At 1032, it is determined whether there are any differences between the list and the software installed on the node. If there are no differences, processing for software distribution can end. Other processing may be appropriate for carrying out additional configuration directives (e.g., adjusting the periodic request interval).
  • If it is determined that there are differences, the software is acquired at 1042 and installed at 1052. The software may be acquired in a variety of ways, such as via an HTTP-based protocol. For example, the software may reside at a server maintained by the application service provider, at a mirror site, or at a location within the network (e.g., behind the firewall) if desired.
  • The list can be interpreted so that software not appearing in the list is uninstalled from the node (e.g., by the agent). Old software distribution units may be retained so they can be provided to other nodes (e.g., in a peer-to-peer arrangement).
  • Although administration can be accomplished via an application service provider scenario as illustrated, functionality of the software being administered need not be so provided. For example, a hybrid situation may exist where administration and distribution of the software is performed via an application service provider scenario, but components of the software being administered reside locally at the nodes.
  • EXAMPLE 7 Software Distribution Over Many Enterprises
  • In some situations, it may be desirable for one vendor to host application services for more than one organization. For example, a vendor can host a plurality of customers to avoid having a data center for each customer, to avoid having to hire separate staff for each customer, or to otherwise reduce the cost of providing the services. The technologies described herein can be implemented in such a scenario.
  • FIG. 11 depicts an exemplary scenario 1100 in which a vendor hosts application services for more than one customer. The vendor can act as an application service provider or delegate the hosting responsibilities to another entity if desired. Also, it is possible for one application service provider to provide services for a plurality of vendors. It is also possible for the pictured scenario 1100 to be applied to a single organization (e.g., departments or geographical locations can be considered sub-organizations within such an organization).
  • In the example, a data center 1102 can include a variety of hardware and software (e.g., web servers) for processing requests from a variety of nodes via the network 1122. The network 1122 may be the Internet or some other network. In the case of the Internet, there may be one or more firewalls between the data center 1102 and the nodes administered.
  • The data center 1102 can include a database 1132 that has an organization table 1134 and one or more configuration tables 1136. In this way, the database 1132 can track which nodes belong to which organization (e.g., via a nodes table) and the configuration appropriate for the nodes. Various other tables can also be included (e.g., a groups table). In some cases, an organization may be sensitive to having its information commingled with other organizations, so a separate table, a separate database, a separate server, or a separate data center 1102 can be maintained for such organizations, if desired.
  • As shown, three organizations 1142A, 1142B, and 1142C are availing themselves of the services provided by the application service provider via the data center 1102 over the network 1122. Within the organization, nodes can be associated into groups or subnets (e.g., the group 1152). Administration can be accomplished by an administrator accessing the data center 1102 (e.g., via an HTTP-based protocol) from within the respective organization, group, or subnet.
  • It is also possible that the organizations be administered by yet another entity via another computer 1162. For example, a consulting firm can perform software administration functions for the three organizations by accessing web pages over the Internet. The initial installation of agents to the nodes may be challenging in a situation where no administrator is behind the organization's firewall, but such installation can be accomplished by emailing an appropriate hyperlink to a user at the node. When activated, the hyperlink can install the appropriate agent software.
  • Distribution of software via stages as described herein can be administered via any of the illustrated scenarios. For example, an administrator inside or outside of an organization can access the data center 1102 to manipulate configuration settings designating nodes be distributed software of an appropriate stage. Security measures can be put into place to prevent unauthorized manipulation of configuration settings.
  • EXAMPLE 8 Groups
  • Various nodes can be placed into named groups to facilitate administration of a large number of nodes. For example, a set of nodes can be placed into a group named “lab” to designate that the nodes are machines in a lab where software functionality is tested. A group can have one or more nodes and be associated with a group name.
  • The named group can then be associated with various configuration directives, including association with a software stage. In the example of the “lab” group, the nodes might be associated with an initial (e.g., beta) stage so that the computers in the lab are the first to receive a new version of software.
  • EXAMPLE 9 Policies
  • A set of configuration directives can be grouped into a named set called a policy. The policy can include a stage of software to be distributed to nodes associated with the policy. The policy can be associated with nodes via the group mechanism described above.
  • EXAMPLE 10 Beta, Early, and Live Stages
  • If desired, a three-stage software system can be used. For example, the earliest stage can be called “beta,” a middle stage called “early,” and the late stage called “live.” Typically, beta software is that for which considerable additional feedback is sought by the developer. The middle stage is a more mature release, and the live version is considered to be one of the final releases of the software. However, other arrangements can be used.
  • EXAMPLE 11 Anti-Virus Software Administration
  • In any of the examples described herein, the software being administered can be anti-virus software. An exemplary anti-virus software arrangement 1200 is shown in FIG. 12.
  • In the arrangement 1200, a computer 1202 (e.g., a node) is running the anti-virus software 1222. The anti-virus software 1222 may include a scanning engine 1224 and the virus data 1226. The scanning engine 1224 is operable to scan a variety of items (e.g., the item 1232) and makes use of the virus data 1226, which can contain virus signatures (e.g., data indicating a distinctive characteristic showing an item contains a virus). The virus data 1226 can be provided in the form of a file.
  • A variety of items can be checked for viruses (e.g., files on a file system, email attachments, files in web pages, scripts, etc.). Checking can be done upon access of an item or by periodic scans or on demand by a user or administrator (or both).
  • In the example, agent software 1252 communicates with a data center 1262 (e.g., operated by an application service provider) via a network 1272 (e.g., the Internet). Communication can be accomplished via an HTTP-based protocol. For example, the agent 1252 can send queries for updates to the virus data 1226 or other portions of the anti-virus software 1222 (e.g., the engine 1224).
  • EXAMPLE 12 Exemplary Implementation
  • FIGS. 13-17 are screen shots illustrating an exemplary implementation related to the above technologies. The screen shots show a user interface as presented by a web browser such as the Microsoft Internet Explorer software, which is marketed by Microsoft Corporation. Other software can be used, and either Internet (e.g., http://www.sitename.com/xyz.asp) or intranet (e.g., http://subnet.companyname/xyz.asp) references can be used to acquire the user interfaces. The illustrated user interface can be provided by any number of software packages, including a server-side scripting environment (e.g., Microsoft active server pages technology) associated with a web server.
  • To acquire access to the application services, an organization can enter into a contractual arrangement with an application service provider vendor (e.g., by subscribing to the services and agreeing to pay a monthly fee). The application service provider can provide an appropriate network link and a user name and password by which an administrator can log into the system and begin administering the software.
  • As described above, an administrator can acquire an installation utility and remotely deploy and install agent software to the nodes to be administered. The administrator can then go about the process of configuring how the nodes are to be administered.
  • During the process, it may be desirable to place one or more nodes into a group. FIG. 13 shows a screen shot 1300 depicting an exemplary user interface for manipulating groups. A database of configuration information can be adjusted according to the administrator's selections.
  • It may also be desirable to place one or more configuration directives into a named set. Such a named set can then be assigned to a group as show in FIG. 14, which shows an exemplary user interface 1400 for manipulating policies. One directive of the policy (i.e., “Release State”) relates to the stage of the software to be distributed for the group. The stage can be specified as “Beta,” “Early,” or “Live.”
  • The configuration directives can take many forms. For example, FIG. 15 shows an exemplary user interface for manipulating configuration directives related to an agent. Changes by an administrator are stored in a configuration database, and agents assigned the related policy are updated accordingly (e.g., when they contact the application service provider data center). The user interface for the administered software can be hidden via the options (e.g., “Show Agent UI”). Also, as shown, an option “Show Exit option” can be used to control whether an icon appears in an icon menu by which a user can exit the software running at a node.
  • Other configuration directives are possible. FIG. 16 shows a configuration directive related to whether on-access scanning is enabled.
  • In addition, tasks can be scheduled for policies. For example, FIG. 17 is a screen shot showing an exemplary user interface 1700 by which an administrator can schedule tasks. Additional user interfaces can be presented by which tasks can be added and task recurrence can be specified. Additional recurrence parameters can be specified by another user interface (e.g., whether to occur every day or recur every n days, whether to recur indefinitely or n times, and whether to use default advanced settings, such as a jitter value, late limit, and maximum duration parameters). Alternatively, a task can be scheduled for a group.
  • Various other user interfaces can be presented. For example, a list of computers can be presented (e.g., indicating a computer name, domain, operating system, and group).
  • Software administration will proceed according to the configuration specified via the user interfaces. For example, if a group of computers has been assigned the “Beta” stage, upon availability of a software release associated with the “Beta” stage, queries from agents for appropriate software will be answered by providing a list including software of the “Beta” stage.
  • For example, agent software at a node can send an HTTP-based request to a data center, providing a node identifier unique to the node. In response, the data center can provide a list of software based on the configuration information specified by the administrator.
  • The agent software can then acquire the software it needs to conform with the configuration information specified by the administrator. In this way, automatic software distribution via stages can be accomplished.
  • When a new release becomes available (e.g., a software development team releases software), it can be added to an appropriate database with a reference indicating a location from which the release can be obtained. Subsequent queries from agents receive replies taking the new release into account. The software will thus percolate down to the agents as they request it. If a node is off-line (e.g., a mobile user having a computer not connected to a network), there may be some lag time, but upon connecting to the network, the agent can query the data center and an appropriate software list can be provided.
  • In the example, the list of software can be a list of files conforming to the .CAB file specification of Microsoft Corporation. If software administered by the system is installed but not listed in the list, the software is uninstalled. The .CAB file may remain on the node so that another node can access it (e.g., in a peer-to-peer arrangement).
  • At some point, the software life cycle may begin again or move to an earlier stage in some other way. In such a case, beta versions of the software will be distributed to those nodes associated with a group that is associated with a policy specifying beta software.
  • There may be more than one version of the software (e.g., a beta of 1.0 and a beta of 2.0); however, a versionless system can be used from the administrators point of view (e.g., there is a beta release of the software, but no version need be associated with it).
  • In this way, software administration can be accomplished via an application service provider scenario. Although administration can include a wide variety of functions, the illustrated example enables monitoring (e.g., for producing reports of virus infection), configuration, and installation of software. In addition, the polled pull scenarios described can allow the system to operate even though there may be a firewall in place. Thus, application administration can be performed in such a way that software is automatically updated through a firewall. Such an arrangement can provide a valuable service in many situations, such as for a large enterprise's information technology department. Such an enterprise may have 10, 100, 1000, 10,000, 100,000, or more nodes.
  • Because more than one such enterprise can be served in an application service provider scenario, 10,000, 100,000, 1,000,000, 10,000,000, or more nodes can be administered by the described technologies.
  • EXAMPLE 13 Database Schema
  • FIGS. 18A-J show an exemplary database schema for implementing software administration via an application service provider scenario.
  • FIGS. 19A-B show another exemplary database schema for implementing software administration via an application service provider scenario.
  • The schema are examples only. A wide variety of other arrangements are possible, and another approach (e.g., XML) can be used.
  • Alternatives
  • Having described and illustrated the principles of our invention with reference to illustrated embodiments, it will be recognized that the illustrated embodiments can be modified in arrangement and detail without departing from such principles. It should be understood that the programs, processes, or methods described herein need not be related or limited to any particular type of computer apparatus. Various types of general purpose or specialized computer apparatus may be used with, or perform operations in accordance with, the teachings described herein. Elements of the illustrated embodiment shown in software may be implemented in hardware and vice versa.
  • Technologies from the preceding examples can be combined in various permutations as desired. Although some examples describe an application service provider scenario, the technologies can be directed to other arrangements. Similarly, although some examples describe anti-virus software, the technologies can be directed to other arrangements.
  • In view of the many possible embodiments to which the principles of our invention may be applied, it should be recognized that the detailed embodiments are illustrative only and should not be taken as limiting the scope of our invention. Rather, we claim as our invention all such embodiments as may come within the scope and spirit of the following claims and equivalents thereto.

Claims (48)

1. (canceled)
2. (canceled)
3. (canceled)
4. (canceled)
5. (canceled)
6. (canceled)
7. (canceled)
8. (canceled)
9. (canceled)
10. (canceled)
11. (canceled)
12. (canceled)
13. (canceled)
14. (canceled)
15. (canceled)
16. (canceled)
17. (canceled)
18. (canceled)
19. (canceled)
20. (canceled)
21. (canceled)
22. A method of providing application services to a plurality of enterprises, the method comprising:
via an application service provider scenario, collecting indications associating computers within the enterprises with stages of software;
periodically receiving requests from the computers within the enterprises for indications of what software is to be installed on the computers; and
responsive to the requests, sending lists of software to be installed at the computers according to the stages associated with the computers.
23. The method of claim 22 wherein the application service provider scenario is accomplished via an HTTP-based protocol.
24. The method of claim 22 wherein the requests are sent via an HTTP-based protocol.
25. The method of claim 24 wherein the requests are sent by an agent automatically without action by a user.
26. The method of claim 22 further comprising:
comparing at least one of the lists of software to be installed with software installed on at least one of the computers;
installing software indicated as to be installed, but not installed.
27. The method of claim 26 wherein the installing comprises:
retrieving the software from an application service provider.
28. (canceled)
29. A system for providing application services for installing a plurality of software releases at a plurality of nodes, the system comprising:
a data store operable to associate the software releases with a software stage and to associate the nodes with a software stage; and
one or more servers operable to receive indications of software stages associated with the nodes and modify the data store;
wherein the servers are further operable to receive queries from the nodes to provide a list of software to be installed at the nodes and reply thereto according to stage information in the data store.
30. The system of claim 29 wherein the servers are operable to receive associations for the software stages via an HTTP-based protocol.
31. The system of claim 29 wherein the servers are operable to receive the queries from the nodes via an HTTP-based protocol.
32. (canceled)
33. (canceled)
34. (canceled)
35. (canceled)
36. (canceled)
37. (canceled)
38. The method of claim 22 wherein collecting indications associating computers within the enterprises further comprises:
providing an administrative user interface by which administrators select various options and configuration directives; and
responsive to selections made via the administrative user interface, placing computers into named groups and associating the named groups with a software stage.
39. The method of claim 22 further comprising;
from computers sent lists of software, receiving requests for software on the lists; and sending the requested software.
40. The method of claim 22 wherein the frequency of the periodically received requests is controlled by an administrator via manipulation of a web page.
41. The method of claim 22 wherein the stages of software comprise a beta stage and plural sent lists of software comprise beta stage software to be installed.
42. Sew) The system of claim 29 wherein the servers are further operable to receive requests from the nodes for software listed in the list of software and to return the requested software.
43. The system of claim 29 wherein the data store associates a set of configuration directives as a policy and the policy is associated with a group of nodes.
44. The system of claim 43 wherein associations of the data store are defined via a database schema.
45. The system of claim 29 wherein the servers are further operable to provide an administrative user interface by which administrators select indications of software stages.
46. A computer readable medium having computer-executable instructions, the instructions comprising:
instructions for collecting indications associating computers within enterprises with stages of software;
instructions for receiving requests from the computers within the enterprises for indications of what software is to be installed on the computers; and
instructions for sending responsive to the requests, lists of software to be installed at the computers according to the stages associated with the computers.
47. The computer readable medium of claim 46 wherein the computer executable-instructions further comprise instructions for receiving the requests via an HTTP-based protocol.
48. The computer readable medium of claim 46 wherein the computer-executable instructions further comprise:
instructions for providing an administrative user interface by which administrators select various options and configuration directives; and
instructions for responsive to selections made via the administrative user interface, placing computers into named groups and associating the named groups with policies.
US11/614,819 2002-04-23 2006-12-21 Software distribution via stages Abandoned US20070106749A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US37521502P true 2002-04-23 2002-04-23
US10/421,645 US7178144B2 (en) 2002-04-23 2003-04-22 Software distribution via stages
US11/614,819 US20070106749A1 (en) 2002-04-23 2006-12-21 Software distribution via stages

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US11/614,819 US20070106749A1 (en) 2002-04-23 2006-12-21 Software distribution via stages

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/421,645 Division US7178144B2 (en) 2002-04-23 2003-04-22 Software distribution via stages

Publications (1)

Publication Number Publication Date
US20070106749A1 true US20070106749A1 (en) 2007-05-10

Family

ID=30772839

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/421,645 Expired - Fee Related US7178144B2 (en) 2002-04-23 2003-04-22 Software distribution via stages
US11/614,819 Abandoned US20070106749A1 (en) 2002-04-23 2006-12-21 Software distribution via stages

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/421,645 Expired - Fee Related US7178144B2 (en) 2002-04-23 2003-04-22 Software distribution via stages

Country Status (1)

Country Link
US (2) US7178144B2 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080076401A1 (en) * 2006-09-07 2008-03-27 Qualcomm Incorporated System and methods for remotely upgrading software applications
US9104813B2 (en) 2012-12-15 2015-08-11 International Business Machines Corporation Software installation method, apparatus and program product

Families Citing this family (68)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040073903A1 (en) * 2002-04-23 2004-04-15 Secure Resolutions,Inc. Providing access to software over a network via keys
US7401133B2 (en) 2002-04-23 2008-07-15 Secure Resolutions, Inc. Software administration in an application service provider scenario via configuration directives
US20030200300A1 (en) * 2002-04-23 2003-10-23 Secure Resolutions, Inc. Singularly hosted, enterprise managed, plural branded application services
US20040006586A1 (en) * 2002-04-23 2004-01-08 Secure Resolutions, Inc. Distributed server software distribution
US20030233483A1 (en) * 2002-04-23 2003-12-18 Secure Resolutions, Inc. Executing software in a network environment
US7178144B2 (en) * 2002-04-23 2007-02-13 Secure Resolutions, Inc. Software distribution via stages
US20040153703A1 (en) * 2002-04-23 2004-08-05 Secure Resolutions, Inc. Fault tolerant distributed computing applications
US7356577B2 (en) * 2003-06-12 2008-04-08 Samsung Electronics Co., Ltd. System and method for providing an online software upgrade in load sharing servers
US9118710B2 (en) 2003-07-01 2015-08-25 Securityprofiling, Llc System, method, and computer program product for reporting an occurrence in different manners
US9118708B2 (en) 2003-07-01 2015-08-25 Securityprofiling, Llc Multi-path remediation
US9118709B2 (en) 2003-07-01 2015-08-25 Securityprofiling, Llc Anti-vulnerability system, method, and computer program product
US9118711B2 (en) 2003-07-01 2015-08-25 Securityprofiling, Llc Anti-vulnerability system, method, and computer program product
US9350752B2 (en) 2003-07-01 2016-05-24 Securityprofiling, Llc Anti-vulnerability system, method, and computer program product
US9100431B2 (en) 2003-07-01 2015-08-04 Securityprofiling, Llc Computer program product and apparatus for multi-path remediation
US8984644B2 (en) 2003-07-01 2015-03-17 Securityprofiling, Llc Anti-vulnerability system, method, and computer program product
US20070113272A2 (en) 2003-07-01 2007-05-17 Securityprofiling, Inc. Real-time vulnerability monitoring
US20070113265A2 (en) * 2003-07-01 2007-05-17 Securityprofiling, Inc. Automated staged patch and policy management
DE10356368A1 (en) * 2003-11-28 2005-06-23 Abb Patent Gmbh System for automatic generation and installation of functionalities into data files, esp. system components in distributed automation system, includes system planning tool
US7743008B2 (en) * 2003-12-30 2010-06-22 International Business Machines Corporation Adaptive management method with workflow control
US7142848B2 (en) * 2004-02-26 2006-11-28 Research In Motion Limited Method and system for automatically configuring access control
WO2005089209A2 (en) * 2004-03-12 2005-09-29 Microsoft Corporation Application programming interface for administering the distribution of software updates in an update distribution system
US20060015840A1 (en) * 2004-03-31 2006-01-19 Wendall Marvel Parameter-based software development, distribution, and disaster recovery
JP4843208B2 (en) * 2004-09-30 2011-12-21 株式会社東芝 Digital content editing apparatus, a digital content editing method, a digital content editing program and the digital content editing program recording medium recording
US7890952B2 (en) * 2004-10-07 2011-02-15 International Business Machines Corporation Autonomic peer-to-peer computer software installation
US8555286B2 (en) * 2004-10-27 2013-10-08 International Business Machines Corporation Method, system, and apparatus for establishing a software configurable computing environment
US7555551B1 (en) 2005-04-13 2009-06-30 Symantec Corporation Automatic controllable deployment of software updates
US7334005B2 (en) 2005-04-13 2008-02-19 Symantec Corporation Controllable deployment of software updates
JP4455403B2 (en) * 2005-05-17 2010-04-21 キヤノン株式会社 Management method and management apparatus
US7770168B1 (en) * 2005-05-25 2010-08-03 Landesk Software Limited Systems and methods for distributing software using nodes within a network group
US9270532B2 (en) * 2005-10-06 2016-02-23 Rateze Remote Mgmt. L.L.C. Resource command messages and methods
US20080015968A1 (en) * 2005-10-14 2008-01-17 Leviathan Entertainment, Llc Fee-Based Priority Queuing for Insurance Claim Processing
US8533309B1 (en) * 2005-10-24 2013-09-10 Crimson Corporation Systems and methods for distributed node detection and management
US8271970B2 (en) * 2005-10-27 2012-09-18 Siemens Aktiengesellschaft Method for software distribution
US8122446B2 (en) 2005-11-03 2012-02-21 International Business Machines Corporation Method and apparatus for provisioning software on a network of computers
US8078952B2 (en) * 2005-11-28 2011-12-13 Microsoft Corporation Site redirection
JP4564464B2 (en) * 2006-01-05 2010-10-20 株式会社東芝 Digital content reproducing apparatus, method and program
JP4577225B2 (en) * 2006-01-31 2010-11-10 セイコーエプソン株式会社 The information processing apparatus, control method and control program for an information processing apparatus
US7694294B2 (en) * 2006-03-15 2010-04-06 Microsoft Corporation Task template update based on task usage pattern
US7899892B2 (en) * 2006-03-28 2011-03-01 Microsoft Corporation Management of extensibility servers and applications
US7873153B2 (en) * 2006-03-29 2011-01-18 Microsoft Corporation Priority task list
US20070282983A1 (en) * 2006-06-05 2007-12-06 Manoj Gujarathi System and Method for Information Handling System Management With a Directory Service Tool Box
US8312449B2 (en) * 2006-10-31 2012-11-13 International Business Machines Corporation Viral installation of operating systems in a network
US8813063B2 (en) * 2006-12-06 2014-08-19 International Business Machines Corporation Verification of successful installation of computer software
JP4905150B2 (en) * 2007-01-22 2012-03-28 富士通株式会社 The software operation performance management system, method and program
US8316364B2 (en) * 2007-02-28 2012-11-20 Red Hat, Inc. Peer-to-peer software update distribution network
US20080276234A1 (en) * 2007-04-02 2008-11-06 Sugarcrm Inc. Data center edition system and method
EP2145254A4 (en) * 2007-04-09 2010-04-28 Sugarcrm Inc Data center edition system and method
WO2008127340A1 (en) * 2007-04-16 2008-10-23 Leviathan Entertainment Intellectual property application drafting, preparation, and submission tools
US8458693B2 (en) * 2007-08-02 2013-06-04 Sap Ag Transitioning from static to dynamic cluster management
US8756318B1 (en) * 2007-10-09 2014-06-17 Microsoft Corporation Software deployment using client location
WO2009134927A2 (en) * 2008-04-29 2009-11-05 Sugarcrm, Inc. Business software application system and method
US8418164B2 (en) * 2008-05-29 2013-04-09 Red Hat, Inc. Image install of a network appliance
US9038056B1 (en) * 2009-03-31 2015-05-19 Avaya Inc. Method and apparatus for performing automatable software upgrades using a lightweight serviceless install agent
JP5093266B2 (en) * 2010-03-02 2012-12-12 コニカミノルタビジネステクノロジーズ株式会社 Image forming apparatus, preview display method and a display program in the apparatus
US8990361B2 (en) * 2010-04-23 2015-03-24 Psion Inc. Method and system for proximity-based, peer-initiated device configuration
US8875120B2 (en) * 2011-08-01 2014-10-28 Salesforce.Com, Inc. Methods and apparatus for providing software bug-fix notifications for networked computing systems
US20140157238A1 (en) * 2012-11-30 2014-06-05 Microsoft Corporation Systems and methods of assessing software quality for hardware devices
US20150128121A1 (en) * 2013-11-06 2015-05-07 Improvement Interactive, LLC Dynamic application version selection
US20150156057A1 (en) * 2013-12-02 2015-06-04 John C. Leung Executable-Based Platform Selection
US20150229518A1 (en) * 2014-02-13 2015-08-13 Monolith Technology Services, Inc. Systems and methods for providing rapid product development for service assurance
US9575741B2 (en) * 2014-03-20 2017-02-21 Google Technology Holdings LLC Methods and devices for wireless device-to-device software upgrades
US9965262B2 (en) * 2015-05-21 2018-05-08 International Business Machines Corporation Application bundle pulling
US10152516B2 (en) 2015-05-21 2018-12-11 International Business Machines Corporation Managing staleness latency among application bundles
US9888057B2 (en) 2015-05-21 2018-02-06 International Business Machines Corporation Application bundle management across mixed file system types
US20160344799A1 (en) * 2015-05-21 2016-11-24 International Business Machines Corporation Managing redundancy among application bundles
US20160344843A1 (en) * 2015-05-21 2016-11-24 International Business Machines Corporation Managing redundancy among application bundles
JP2017033147A (en) * 2015-07-30 2017-02-09 キヤノン株式会社 Distribution system, distribution method, and program
US10133566B2 (en) * 2017-03-30 2018-11-20 Adtran, Inc. Software upgrading system and method in a distributed multi-node network environment

Citations (77)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5008814A (en) * 1988-08-15 1991-04-16 Network Equipment Technologies, Inc. Method and apparatus for updating system software for a plurality of data processing units in a communication network
US5495610A (en) * 1989-11-30 1996-02-27 Seer Technologies, Inc. Software distribution system to build and distribute a software release
US5778231A (en) * 1995-12-20 1998-07-07 Sun Microsystems, Inc. Compiler system and method for resolving symbolic references to externally located program files
US5781535A (en) * 1996-06-14 1998-07-14 Mci Communications Corp. Implementation protocol for SHN-based algorithm restoration platform
US5809145A (en) * 1996-06-28 1998-09-15 Paradata Systems Inc. System for distributing digital information
US6029147A (en) * 1996-03-15 2000-02-22 Microsoft Corporation Method and system for providing an interface for supporting multiple formats for on-line banking services
US6029256A (en) * 1997-12-31 2000-02-22 Network Associates, Inc. Method and system for allowing computer programs easy access to features of a virus scanning engine
US6029196A (en) * 1997-06-18 2000-02-22 Netscape Communications Corporation Automatic client configuration system
US6055363A (en) * 1997-07-22 2000-04-25 International Business Machines Corporation Managing multiple versions of multiple subsystems in a distributed computing environment
US6083281A (en) * 1997-11-14 2000-07-04 Nortel Networks Corporation Process and apparatus for tracing software entities in a distributed system
US6151643A (en) * 1996-06-07 2000-11-21 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
US6199204B1 (en) * 1998-01-28 2001-03-06 International Business Machines Corporation Distribution of software updates via a computer network
US6256683B1 (en) * 1998-12-23 2001-07-03 Bops, Inc. Methods and apparatus for providing direct memory access control
US20010007100A1 (en) * 1999-10-29 2001-07-05 Revashetti Siddaraya B. Active marketing based on client computer configurations
US6266811B1 (en) * 1997-12-31 2001-07-24 Network Associates Method and system for custom computer software installation using rule-based installation engine and simplified script computer program
US6269456B1 (en) * 1997-12-31 2001-07-31 Network Associates, Inc. Method and system for providing automated updating and upgrading of antivirus applications using a computer network
US6314465B1 (en) * 1999-03-11 2001-11-06 Lucent Technologies Inc. Method and apparatus for load sharing on a wide area network
US6336139B1 (en) * 1998-06-03 2002-01-01 International Business Machines Corporation System, method and computer program product for event correlation in a distributed computing environment
US6385641B1 (en) * 1998-06-05 2002-05-07 The Regents Of The University Of California Adaptive prefetching for computer network and web browsing with a graphic user interface
US20020091819A1 (en) * 2001-01-05 2002-07-11 Daniel Melchione System and method for configuring computer applications and devices using inheritance
US20020095522A1 (en) * 2001-01-16 2002-07-18 Hayko James Steven System and method for automatic provision of an application
US6425093B1 (en) * 1998-01-05 2002-07-23 Sophisticated Circuits, Inc. Methods and apparatuses for controlling the execution of software on a digital processing system
US6442694B1 (en) * 1998-02-27 2002-08-27 Massachusetts Institute Of Technology Fault isolation for communication networks for isolating the source of faults comprising attacks, failures, and other network propagating errors
US20020124072A1 (en) * 2001-02-16 2002-09-05 Alexander Tormasov Virtual computing environment
US6453430B1 (en) * 1999-05-06 2002-09-17 Cisco Technology, Inc. Apparatus and methods for controlling restart conditions of a faulted process
US20020133723A1 (en) * 2001-03-16 2002-09-19 John King Frederick Tait Method and system to provide and manage secure access to internal computer systems from an external client
US6460023B1 (en) * 1999-06-16 2002-10-01 Pulse Entertainment, Inc. Software authorization system and method
US6484315B1 (en) * 1999-02-01 2002-11-19 Cisco Technology, Inc. Method and system for dynamically distributing updates in a network
US20020199118A1 (en) * 2001-02-02 2002-12-26 Medinservice.Com, Inc. Internet training course system and methods
US20030023408A1 (en) * 2001-03-06 2003-01-30 Robin Wight System for collecting and storing information
US6516416B2 (en) * 1997-06-11 2003-02-04 Prism Resources Subscription access system for use with an untrusted network
US6516337B1 (en) * 1999-10-14 2003-02-04 Arcessa, Inc. Sending to a central indexing site meta data or signatures from objects on a computer network
US20030027552A1 (en) * 2001-08-03 2003-02-06 Victor Kouznetsov System and method for providing telephonic content security service in a wireless network environment
US20030028653A1 (en) * 2001-08-06 2003-02-06 New John C. Method and system for providing access to computer resources
US20030028785A1 (en) * 2001-08-01 2003-02-06 Pak Michael Chin-Hwan System and method for executing computer virus definitions containing general purpose programming language extensions
US20030033536A1 (en) * 2001-08-01 2003-02-13 Pak Michael C. Virus scanning on thin client devices using programmable assembly language
US20030065793A1 (en) * 2001-09-28 2003-04-03 Victor Kouznetsov Anti-virus policy enforcement system and method
US20030079145A1 (en) * 2001-08-01 2003-04-24 Networks Associates Technology, Inc. Platform abstraction layer for a wireless malware scanning engine
US20030084377A1 (en) * 2001-10-31 2003-05-01 Parks Jeff A. Process activity and error monitoring system and method
US6601233B1 (en) * 1999-07-30 2003-07-29 Accenture Llp Business components framework
US20030163702A1 (en) * 2001-04-06 2003-08-28 Vigue Charles L. System and method for secure and verified sharing of resources in a peer-to-peer network environment
US20030163471A1 (en) * 2002-02-22 2003-08-28 Tulip Shah Method, system and storage medium for providing supplier branding services over a communications network
US6625581B1 (en) * 1994-04-22 2003-09-23 Ipf, Inc. Method of and system for enabling the access of consumer product related information and the purchase of consumer products at points of consumer presence on the world wide web (www) at which consumer product information request (cpir) enabling servlet tags are embedded within html-encoded documents
US20030200300A1 (en) * 2002-04-23 2003-10-23 Secure Resolutions, Inc. Singularly hosted, enterprise managed, plural branded application services
US20030233551A1 (en) * 2001-04-06 2003-12-18 Victor Kouznetsov System and method to verify trusted status of peer in a peer-to-peer network environment
US20030233483A1 (en) * 2002-04-23 2003-12-18 Secure Resolutions, Inc. Executing software in a network environment
US6671818B1 (en) * 1999-11-22 2003-12-30 Accenture Llp Problem isolation through translating and filtering events into a standard object format in a network based supply chain
US20040006586A1 (en) * 2002-04-23 2004-01-08 Secure Resolutions, Inc. Distributed server software distribution
US20040019889A1 (en) * 2002-04-23 2004-01-29 Secure Resolutions, Inc. Software distribution via stages
US6691176B1 (en) * 1999-11-04 2004-02-10 Microsoft Corporation Method for managing client services across browser pages
US6701441B1 (en) * 1998-12-08 2004-03-02 Networks Associates Technology, Inc. System and method for interactive web services
US6704933B1 (en) * 1999-02-03 2004-03-09 Masushita Electric Industrial Co., Ltd. Program configuration management apparatus
US6718364B2 (en) * 1999-08-10 2004-04-06 Sun Microsystems, Inc. Method and apparatus for expedited file downloads in an applet environment
US6721941B1 (en) * 1996-08-27 2004-04-13 Compuware Corporation Collection of timing and coverage data through a debugging interface
US20040073903A1 (en) * 2002-04-23 2004-04-15 Secure Resolutions,Inc. Providing access to software over a network via keys
US6728960B1 (en) * 1998-11-18 2004-04-27 Siebel Systems, Inc. Techniques for managing multiple threads in a browser environment
US6742141B1 (en) * 1999-05-10 2004-05-25 Handsfree Networks, Inc. System for automated problem detection, diagnosis, and resolution in a software driven system
US6760903B1 (en) * 1996-08-27 2004-07-06 Compuware Corporation Coordinated application monitoring in a distributed computing environment
US20040153703A1 (en) * 2002-04-23 2004-08-05 Secure Resolutions, Inc. Fault tolerant distributed computing applications
US6782527B1 (en) * 2000-01-28 2004-08-24 Networks Associates, Inc. System and method for efficient distribution of application services to a plurality of computing appliances organized as subnets
US6799197B1 (en) * 2000-08-29 2004-09-28 Networks Associates Technology, Inc. Secure method and system for using a public network or email to administer to software on a plurality of client computers
US6826594B1 (en) * 2000-07-15 2004-11-30 Commission Junction Method and system for remote content management of a designated portion of a web page
US6826698B1 (en) * 2000-09-15 2004-11-30 Networks Associates Technology, Inc. System, method and computer program product for rule based network security policies
US20040268120A1 (en) * 2003-06-26 2004-12-30 Nokia, Inc. System and method for public key infrastructure based software licensing
US20050004838A1 (en) * 1996-10-25 2005-01-06 Ipf, Inc. Internet-based brand management and marketing commuication instrumentation network for deploying, installing and remotely programming brand-building server-side driven multi-mode virtual kiosks on the World Wide Web (WWW), and methods of brand marketing communication between brand marketers and consumers using the same
US6910066B1 (en) * 2001-03-05 2005-06-21 Principal Financial Services, Inc. System, method, and apparatus for applet caching
US6931546B1 (en) * 2000-01-28 2005-08-16 Network Associates, Inc. System and method for providing application services with controlled access into privileged processes
US6944632B2 (en) * 1997-08-08 2005-09-13 Prn Corporation Method and apparatus for gathering statistical information about in-store content distribution
US6947986B1 (en) * 2001-05-08 2005-09-20 Networks Associates Technology, Inc. System and method for providing web-based remote security application client administration in a distributed computing environment
US6950991B2 (en) * 1995-11-13 2005-09-27 Citrix Systems, Inc. Interacting with software applications displayed in a web page
US6983326B1 (en) * 2001-04-06 2006-01-03 Networks Associates Technology, Inc. System and method for distributed function discovery in a peer-to-peer network environment
US6982729B1 (en) * 2000-04-19 2006-01-03 Hewlett-Packard Development Company, Lp. Constant size image display independent of screen resolution
US6990655B2 (en) * 2001-09-27 2006-01-24 International Business Machines Corporation Apparatus and method of providing a pluggable user interface
US7028295B2 (en) * 2001-10-31 2006-04-11 Seiko Epson Corporation Dynamic java class loading for application execution
US7089259B1 (en) * 2001-08-03 2006-08-08 Mcafee, Inc. System and method for providing a framework for network appliance management in a distributed computing environment
US7130921B2 (en) * 2002-03-15 2006-10-31 International Business Machines Corporation Centrally enhanced peer-to-peer resource sharing method and apparatus
US7146531B2 (en) * 2000-12-28 2006-12-05 Landesk Software Limited Repairing applications

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6049671A (en) 1996-04-18 2000-04-11 Microsoft Corporation Method for identifying and obtaining computer software from a network computer
AU2002232464A1 (en) 2001-02-09 2002-08-28 Microsoft Corporation Distribution of binary executables and content from peer locations/machines

Patent Citations (80)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5008814A (en) * 1988-08-15 1991-04-16 Network Equipment Technologies, Inc. Method and apparatus for updating system software for a plurality of data processing units in a communication network
US5495610A (en) * 1989-11-30 1996-02-27 Seer Technologies, Inc. Software distribution system to build and distribute a software release
US6625581B1 (en) * 1994-04-22 2003-09-23 Ipf, Inc. Method of and system for enabling the access of consumer product related information and the purchase of consumer products at points of consumer presence on the world wide web (www) at which consumer product information request (cpir) enabling servlet tags are embedded within html-encoded documents
US6950991B2 (en) * 1995-11-13 2005-09-27 Citrix Systems, Inc. Interacting with software applications displayed in a web page
US5778231A (en) * 1995-12-20 1998-07-07 Sun Microsystems, Inc. Compiler system and method for resolving symbolic references to externally located program files
US6029147A (en) * 1996-03-15 2000-02-22 Microsoft Corporation Method and system for providing an interface for supporting multiple formats for on-line banking services
US6151643A (en) * 1996-06-07 2000-11-21 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
US5781535A (en) * 1996-06-14 1998-07-14 Mci Communications Corp. Implementation protocol for SHN-based algorithm restoration platform
US5809145A (en) * 1996-06-28 1998-09-15 Paradata Systems Inc. System for distributing digital information
US6721941B1 (en) * 1996-08-27 2004-04-13 Compuware Corporation Collection of timing and coverage data through a debugging interface
US6760903B1 (en) * 1996-08-27 2004-07-06 Compuware Corporation Coordinated application monitoring in a distributed computing environment
US20050004838A1 (en) * 1996-10-25 2005-01-06 Ipf, Inc. Internet-based brand management and marketing commuication instrumentation network for deploying, installing and remotely programming brand-building server-side driven multi-mode virtual kiosks on the World Wide Web (WWW), and methods of brand marketing communication between brand marketers and consumers using the same
US6516416B2 (en) * 1997-06-11 2003-02-04 Prism Resources Subscription access system for use with an untrusted network
US6029196A (en) * 1997-06-18 2000-02-22 Netscape Communications Corporation Automatic client configuration system
US6055363A (en) * 1997-07-22 2000-04-25 International Business Machines Corporation Managing multiple versions of multiple subsystems in a distributed computing environment
US6944632B2 (en) * 1997-08-08 2005-09-13 Prn Corporation Method and apparatus for gathering statistical information about in-store content distribution
US6083281A (en) * 1997-11-14 2000-07-04 Nortel Networks Corporation Process and apparatus for tracing software entities in a distributed system
US6266811B1 (en) * 1997-12-31 2001-07-24 Network Associates Method and system for custom computer software installation using rule-based installation engine and simplified script computer program
US6029256A (en) * 1997-12-31 2000-02-22 Network Associates, Inc. Method and system for allowing computer programs easy access to features of a virus scanning engine
US6269456B1 (en) * 1997-12-31 2001-07-31 Network Associates, Inc. Method and system for providing automated updating and upgrading of antivirus applications using a computer network
US6425093B1 (en) * 1998-01-05 2002-07-23 Sophisticated Circuits, Inc. Methods and apparatuses for controlling the execution of software on a digital processing system
US6199204B1 (en) * 1998-01-28 2001-03-06 International Business Machines Corporation Distribution of software updates via a computer network
US6442694B1 (en) * 1998-02-27 2002-08-27 Massachusetts Institute Of Technology Fault isolation for communication networks for isolating the source of faults comprising attacks, failures, and other network propagating errors
US6336139B1 (en) * 1998-06-03 2002-01-01 International Business Machines Corporation System, method and computer program product for event correlation in a distributed computing environment
US6385641B1 (en) * 1998-06-05 2002-05-07 The Regents Of The University Of California Adaptive prefetching for computer network and web browsing with a graphic user interface
US6728960B1 (en) * 1998-11-18 2004-04-27 Siebel Systems, Inc. Techniques for managing multiple threads in a browser environment
US6701441B1 (en) * 1998-12-08 2004-03-02 Networks Associates Technology, Inc. System and method for interactive web services
US6256683B1 (en) * 1998-12-23 2001-07-03 Bops, Inc. Methods and apparatus for providing direct memory access control
US6484315B1 (en) * 1999-02-01 2002-11-19 Cisco Technology, Inc. Method and system for dynamically distributing updates in a network
US6704933B1 (en) * 1999-02-03 2004-03-09 Masushita Electric Industrial Co., Ltd. Program configuration management apparatus
US6314465B1 (en) * 1999-03-11 2001-11-06 Lucent Technologies Inc. Method and apparatus for load sharing on a wide area network
US6453430B1 (en) * 1999-05-06 2002-09-17 Cisco Technology, Inc. Apparatus and methods for controlling restart conditions of a faulted process
US6742141B1 (en) * 1999-05-10 2004-05-25 Handsfree Networks, Inc. System for automated problem detection, diagnosis, and resolution in a software driven system
US6460023B1 (en) * 1999-06-16 2002-10-01 Pulse Entertainment, Inc. Software authorization system and method
US6601233B1 (en) * 1999-07-30 2003-07-29 Accenture Llp Business components framework
US6718364B2 (en) * 1999-08-10 2004-04-06 Sun Microsystems, Inc. Method and apparatus for expedited file downloads in an applet environment
US6516337B1 (en) * 1999-10-14 2003-02-04 Arcessa, Inc. Sending to a central indexing site meta data or signatures from objects on a computer network
US20010007100A1 (en) * 1999-10-29 2001-07-05 Revashetti Siddaraya B. Active marketing based on client computer configurations
US6691176B1 (en) * 1999-11-04 2004-02-10 Microsoft Corporation Method for managing client services across browser pages
US6671818B1 (en) * 1999-11-22 2003-12-30 Accenture Llp Problem isolation through translating and filtering events into a standard object format in a network based supply chain
US6782527B1 (en) * 2000-01-28 2004-08-24 Networks Associates, Inc. System and method for efficient distribution of application services to a plurality of computing appliances organized as subnets
US20050188370A1 (en) * 2000-01-28 2005-08-25 Networks Associates, Inc. System and method for providing application services with controlled access into privileged processes
US6931546B1 (en) * 2000-01-28 2005-08-16 Network Associates, Inc. System and method for providing application services with controlled access into privileged processes
US6982729B1 (en) * 2000-04-19 2006-01-03 Hewlett-Packard Development Company, Lp. Constant size image display independent of screen resolution
US6826594B1 (en) * 2000-07-15 2004-11-30 Commission Junction Method and system for remote content management of a designated portion of a web page
US6799197B1 (en) * 2000-08-29 2004-09-28 Networks Associates Technology, Inc. Secure method and system for using a public network or email to administer to software on a plurality of client computers
US6826698B1 (en) * 2000-09-15 2004-11-30 Networks Associates Technology, Inc. System, method and computer program product for rule based network security policies
US7146531B2 (en) * 2000-12-28 2006-12-05 Landesk Software Limited Repairing applications
US20020091819A1 (en) * 2001-01-05 2002-07-11 Daniel Melchione System and method for configuring computer applications and devices using inheritance
US20020095522A1 (en) * 2001-01-16 2002-07-18 Hayko James Steven System and method for automatic provision of an application
US20020199118A1 (en) * 2001-02-02 2002-12-26 Medinservice.Com, Inc. Internet training course system and methods
US20020124072A1 (en) * 2001-02-16 2002-09-05 Alexander Tormasov Virtual computing environment
US6910066B1 (en) * 2001-03-05 2005-06-21 Principal Financial Services, Inc. System, method, and apparatus for applet caching
US20030023408A1 (en) * 2001-03-06 2003-01-30 Robin Wight System for collecting and storing information
US20020133723A1 (en) * 2001-03-16 2002-09-19 John King Frederick Tait Method and system to provide and manage secure access to internal computer systems from an external client
US20030163702A1 (en) * 2001-04-06 2003-08-28 Vigue Charles L. System and method for secure and verified sharing of resources in a peer-to-peer network environment
US6983326B1 (en) * 2001-04-06 2006-01-03 Networks Associates Technology, Inc. System and method for distributed function discovery in a peer-to-peer network environment
US20030233551A1 (en) * 2001-04-06 2003-12-18 Victor Kouznetsov System and method to verify trusted status of peer in a peer-to-peer network environment
US6947986B1 (en) * 2001-05-08 2005-09-20 Networks Associates Technology, Inc. System and method for providing web-based remote security application client administration in a distributed computing environment
US20030033536A1 (en) * 2001-08-01 2003-02-13 Pak Michael C. Virus scanning on thin client devices using programmable assembly language
US20030028785A1 (en) * 2001-08-01 2003-02-06 Pak Michael Chin-Hwan System and method for executing computer virus definitions containing general purpose programming language extensions
US20030079145A1 (en) * 2001-08-01 2003-04-24 Networks Associates Technology, Inc. Platform abstraction layer for a wireless malware scanning engine
US7089259B1 (en) * 2001-08-03 2006-08-08 Mcafee, Inc. System and method for providing a framework for network appliance management in a distributed computing environment
US20030027552A1 (en) * 2001-08-03 2003-02-06 Victor Kouznetsov System and method for providing telephonic content security service in a wireless network environment
US20030028653A1 (en) * 2001-08-06 2003-02-06 New John C. Method and system for providing access to computer resources
US6990655B2 (en) * 2001-09-27 2006-01-24 International Business Machines Corporation Apparatus and method of providing a pluggable user interface
US6892241B2 (en) * 2001-09-28 2005-05-10 Networks Associates Technology, Inc. Anti-virus policy enforcement system and method
US20030065793A1 (en) * 2001-09-28 2003-04-03 Victor Kouznetsov Anti-virus policy enforcement system and method
US7028295B2 (en) * 2001-10-31 2006-04-11 Seiko Epson Corporation Dynamic java class loading for application execution
US20030084377A1 (en) * 2001-10-31 2003-05-01 Parks Jeff A. Process activity and error monitoring system and method
US20030163471A1 (en) * 2002-02-22 2003-08-28 Tulip Shah Method, system and storage medium for providing supplier branding services over a communications network
US7130921B2 (en) * 2002-03-15 2006-10-31 International Business Machines Corporation Centrally enhanced peer-to-peer resource sharing method and apparatus
US20030200300A1 (en) * 2002-04-23 2003-10-23 Secure Resolutions, Inc. Singularly hosted, enterprise managed, plural branded application services
US7178144B2 (en) * 2002-04-23 2007-02-13 Secure Resolutions, Inc. Software distribution via stages
US20040153703A1 (en) * 2002-04-23 2004-08-05 Secure Resolutions, Inc. Fault tolerant distributed computing applications
US20040073903A1 (en) * 2002-04-23 2004-04-15 Secure Resolutions,Inc. Providing access to software over a network via keys
US20040019889A1 (en) * 2002-04-23 2004-01-29 Secure Resolutions, Inc. Software distribution via stages
US20030233483A1 (en) * 2002-04-23 2003-12-18 Secure Resolutions, Inc. Executing software in a network environment
US20040006586A1 (en) * 2002-04-23 2004-01-08 Secure Resolutions, Inc. Distributed server software distribution
US20040268120A1 (en) * 2003-06-26 2004-12-30 Nokia, Inc. System and method for public key infrastructure based software licensing

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080076401A1 (en) * 2006-09-07 2008-03-27 Qualcomm Incorporated System and methods for remotely upgrading software applications
US8170540B2 (en) * 2006-09-07 2012-05-01 Qualcomm Incorporated System and methods for remotely upgrading software applications
US8594653B2 (en) 2006-09-07 2013-11-26 Qualcomm Incorporated System and methods for remotely upgrading software applications
US9104813B2 (en) 2012-12-15 2015-08-11 International Business Machines Corporation Software installation method, apparatus and program product

Also Published As

Publication number Publication date
US7178144B2 (en) 2007-02-13
US20040019889A1 (en) 2004-01-29

Similar Documents

Publication Publication Date Title
US8875218B2 (en) Deploying policies and allowing off-line policy evaluations
US8396890B2 (en) Using information usage data to detect behavioral patterns and anomalies
US8375136B2 (en) Defining and implementing policies on managed object-enabled mobile devices
US7069541B2 (en) System and method for a web-based application development and deployment tracking tool
US8315198B2 (en) Mobile provisioning tool system
US6360255B1 (en) Automatically integrating an external network with a network management system
US7716240B2 (en) Techniques and system to deploy policies intelligently
US7124289B1 (en) Automated provisioning framework for internet site servers
US6931546B1 (en) System and method for providing application services with controlled access into privileged processes
CN1882911B (en) A method in a network of the delivery of files
US8239915B1 (en) Endpoint management using trust rating data
US6795830B1 (en) Techniques for providing off-host storage for a database application
US7536686B2 (en) Techniques for automatically installing and configuring database applications
US8234639B2 (en) Autonomic auto-configuration using prior installation configuration relationships
US7925729B2 (en) Network management
US7748000B2 (en) Filtering a list of available install items for an install program based on a consumer's install policy
US8903365B2 (en) Mobile device management
CA2495339C (en) Tag-based schema for distributing update metadata in an update distribution system
US7216163B2 (en) Method and apparatus for provisioning tasks using a provisioning bridge server
US8595794B1 (en) Auditing communications
CA2480821C (en) Connector gateway
US7730408B2 (en) User interface to display and manage an entity and associated resources
US6957256B1 (en) Linking external applications to a network management system
US9239857B2 (en) System and method for building business service model
US5550981A (en) Dynamic binding of network identities to locally-meaningful identities in computer networks

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION