Role based server installation and configuration

• US 9,197,500 B2
• Filed: 01/23/2013
• Issued: 11/24/2015
• Est. Priority Date: 03/25/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Mason, Andrew T., Laing, William A., Macintyre, John, Pletcher, Richard A.
• Primary Examiner(s): Zand, Kambiz
• Assistant Examiner(s): Tran, Tongoc
• Application Number:
  US13/748,398
• Publication Number:
  US 20130138784A1
• Time in Patent Office: 1,035 Days
• Field of Search: 726/17, 713/189, 713/191, 709/220, 709/222, 709/229, 717/174, 717/140, 717/121
• US Class Current: 1/1
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/447 Target code generation
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/62 Uninstallation
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play

Abstract

The described systems and methods are directed at configuring a server based on a selected role. An installation application is configured to install core components in a server where these core components enable the server to perform the basic functions of a network computing device. A role management application is configured to enable a system administrator to select a role for the server and to automatically determine software components associated with the selected role. The role management application is then configured to build the software components and install the components on the server. The role management application is further configured to configure the components for the selected role. The automated installation process performed by the role management application enables a server to be efficiently configured for a particular role without installing other unnecessary components unrelated to the role.

Claims

1. A method performed on a device, the method comprising:

configuring core components of the device, where the device including the configured core components is further configured for performing a role identified by a role manifest, where the role manifest is associated with the device and is processed by a role-management tool executed on the device to identify, build, and configure role-specific components corresponding to the role, and where the core components perform at least some functions specific to the role.

2. The method of claim 1 where the device including the configured core components is configured for performing basic functions of a networked device.

3. The method of claim 2 where the basic functions are selected from a set of functions including file handling, network access, account administration, and firewall functionality.

4. The method of claim 1 where the role is one of a plurality of roles, and where the device is capable of being configured to perform one or more of the plurality of roles.

5. The method of claim 1 where the role-specific components, once identified, built and configured on the device, are sufficient along with the configured core components to enable the device to perform the role corresponding to the role manifest.

16. The method of claim 1, further comprising:

installing on the device, in response to the configuring of core components of the device, the role-specific components identified by the role manifest corresponding to a selected role for the device.

6. At least one storage device storing computer-executable instructions that, when executed by a device, cause the device to perform actions comprising configuring core components of the device, where the device including the configured core components is further configured for performing a role identified by a role manifest, where the role manifest is associated with the device and is processed by a role-management tool executed on the device to identify, build, and configure role-specific components corresponding to the role, and where the core components perform at least some functions specific to the role.

7. The at least one storage device of claim 6 where the device including the configured core components is configured for performing basic functions of a networked device.

8. The at least one storage device of claim 7 where the basic functions are selected from a set of functions including file handling, network access, account administration, and firewall functionality.

9. The at least one storage device of claim 6 where the role is one of a plurality of roles, and where the device is capable of being configured to perform one or more of the plurality of roles.

10. The at least one storage device of claim 6 where the role-specific components, once identified, built and configured on the device, are sufficient along with the configured core components to enable the device to perform the role corresponding to the role manifest.

17. The at least one storage device of claim 6, further causing the device to perform actions comprising installing on the device, in response to the configuring of core components of the device, the role-specific components identified by the role manifest corresponding to a selected role for the device.

11. A device and at least one software module together configured for performing actions comprising configuring core components of the device where the device including the configured core components is further configured for performing a role identified by a role manifest, where the role manifest is associated with the device and is processed by a role-management tool executed on the device to identify, build, and configure role-specific components corresponding to the role, and where the core components perform at least some functions specific to the role.

12. The device and at least one software module of claim 11 where the device including the configured core components is configured for performing basic functions of a networked device.

13. The device and at least one software module of claim 12 where the basic functions are selected from a set of functions including file handling, network access, account administration, and firewall functionality.

14. The device and at least one software module of claim 11 where the role is one of a plurality of roles, and where the device is capable of being configured to perform one or more of the plurality of roles.

15. The device and at least one software module of claim 11 where the role-specific components, once identified, built and configured on the device, are sufficient along with the configured core components to enable the device to perform the role corresponding to the role manifest.

18. The device and at least one software module of claim 11, further configured for performing actions comprising installing on the device, in response to the configuring of core components of the device, the role-specific components identified by the role manifest corresponding to a selected role for the device.