Method and system for on-demand installation of software implementations

• US 20030126592A1
• Filed: 10/04/2002
• Published: 07/03/2003
• Est. Priority Date: 09/21/1998
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Bharat A. Shah, David E. Kays Jr, Debi P. Mishra, Gregory A. Jensenworth, Mark H. Lucovsky, Markus Horstmann, Shannon J. Chan
• Inventors: Lucovsky, Mark H., Jensenworth, Gregory A., Shah, Bharat A., Chan, Shannon J., Mishra, Debi P., Kays, David E. Jr., Horstmann, Markus
• Granted Patent: US 6,754,896 B2
• Time in Patent Office: Days
• US Class Current: 717/176
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

A method and system for installing software implementations such as applications and COM classes as they are needed from an external source, such as a centralized network store. When a software implementation is needed, the system and method first look to the local system (e.g., registry) for that software implementation, and if found, returns the information such as a local path needed to use the software implementation. If the implementation is not found locally, the present invention dynamically looks to a centralized class store of a network, to locate the needed implementation. When located, the implementation is downloaded and locally installed in a manner that is essentially transparent to the user. Software implementations such as application products may be divided into features and components to improve on-demand installation thereof.

Claims

1. In a network of computer systems, a system for deploying software implementations to policy recipients, comprising, a centralized store of policy objects, at least one of the policy objects having an advertise script associated therewith, the advertise script including software implementation information of at least one software implementation for assigning to policy recipients, a first mechanism that applies policy objects to a policy recipient, wherein at least one of the policy objects applied to that recipient has the advertise script associated therewith, the first mechanism processing the script to advertise at least one software implementation to the policy recipient, a second mechanism that requests activation of a selected software implementation, and an installer for determining whether the selected software implementation is locally installed on the computer system, the installer automatically installing the selected software implementation if the selected software implementation is not locally installed on the computer system.

2. The system of claim 1 wherein the second mechanism comprises at least one component of an operating system and the selected software implementation comprises an application program.

3. The system of claim 1 wherein the second mechanism comprises a COM object.

4. The system of claim 1 wherein the selected software implementation comprises an object class.

5. The system of claim 1 wherein the selected software implementation corresponds to an executable program that is advertised as available to the policy recipient but is not locally installed on the computer system, the installer automatically installing the executable program when the second mechanism requests activation thereof.

6. The system of claim 5 wherein the installer automatically installs as least one component associated with the executable program when the second mechanism requests activation thereof.

7. The system of claim 5 wherein following the automatic installation of the executable program, path information of the executable program is returned to the second mechanism and the second mechanism executes the executable program based on the path information.

8. The system of claim 1 wherein the installer is capable of installing a plurality of different software implementations in response to the activation request, wherein only one software implementation is needed as the selected software implementation, and wherein the installer invokes a rule mechanism to determine which of the plurality of different software implementations to install as the selected software implementation.

9. The system of claim 8 wherein the rule mechanism determines the selected software implementation based on upgrade relationships among the plurality of different software implementations.

10. The system of claim 8 wherein the rule mechanism determines the selected software implementation based on a file extension priority among the plurality of different software implementations.

11. The system of claim 8 wherein the rule mechanism determines the selected software implementation based on an architecture.

12. The system of claim 8 wherein the rule mechanism determines the selected software implementation based on locale weights among the plurality of different software implementations.

13. The system of claim 8 wherein the rule mechanism determines the selected software implementation based on an in process, local and remote server precedence.

14. The system of claim 8 wherein the rule mechanism determines the selected software implementation by discarding other software implementations of the plurality in a discard order based on:

1) upgrade relationships among the at least two corresponding software implementations;

2) file extension priorities;

3) architectures;

4) locale weights; and

5) in process, local and remote server precedence.

15. In a computing environment, a method comprising:

advertising a software implementation as available for execution on a computer system, the advertising being independent of whether the software implementation is actually installed on the computer system;

receiving a request to activate the software implementation, the request including information that identifies the software implementation;

in response to the request, determining whether the selected software implementation is locally installed on the computer system; and

if the selected software implementation is not locally installed on the computer system, automatically installing the selected software implementation based on the information that identifies the software implementation.

16. The method of claim 15 wherein advertising the software implementation comprises executing an advertise script.

17. The method of claim 15 wherein advertising the software implementation comprises executing a logon script.

18. The method of claim 15 wherein automatically installing the selected software implementation comprises loading the selected software implementation from a network source.

19. The method of claim 15 further comprising, returning a path indicating an installed location of the requested software implementation.

20. The method of claim 19 wherein an application program requests installation of the software implementation, and wherein the path is returned to the application program.

21. The method of claim 15 further comprising, determining at least two separate software implementations that can satisfy the request if installed, and accessing additional information to determine which of the at least two separate software implementations to install as the selected software implementation.

22. The method of claim 21 wherein the additional information corresponds to upgrade relationships among the at least two separate software implementations.

23. The method of claim 21 wherein the additional information corresponds to a file extension priority among the at least two separate software implementations.

24. The method of claim 21 wherein the additional information corresponds to on an architecture.

25. The method of claim 21 wherein the additional information corresponds to locale weights among the at least two separate software implementations.

26. The method of claim 21 wherein the additional information corresponds to an in process, local and remote server precedence.

27. The method of claim 21 wherein the additional information corresponds to a discard order, including:

1) upgrade relationships among the at least two corresponding software implementations;

2) file extension priorities;

3) architectures;

4) locale weights; and

5) in process, local and remote server precedence.

28. A computer-readable medium having computer-executable instructions for performing the method of claim 15.

29. In a computing environment, a method comprising:

receiving policy data at a policy recipient corresponding to a computer system;

interpreting the policy data to advertise a software implementation as available for execution on a computer system prior to actual installation of that advertised software implementation;

determining in response to a request to activate the advertised software implementation that the software implementation is not locally installed on the computer system; and

automatically installing a software implementation corresponding to the advertised software implementation.

30. The method of claim 29 wherein the policy data is received via a group policy container associated with the policy recipient.

31. The method of claim 30 wherein interpreting the policy data comprises executing an advertise script associated with the group policy container.

32. The method of claim 30 wherein automatically installing the selected software implementation comprises accessing deployment information maintained in association with the group policy container.

33. The method of claim 30 wherein the deployment information provides a set of rules for determining which one of a plurality of software implementations associated with the advertised software implementation is to be installed in response to the request.

34. A computer-readable medium having computer-executable instructions for performing the method of claim 29.