Role based server installation and configuration

• US 7,793,284 B2
• Filed: 03/25/2005
• Issued: 09/07/2010
• Est. Priority Date: 03/25/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Pletcher, Richard A., Laing, William A., Mason, Andrew T., Macintyre, John
• Primary Examiner(s): Zand; Kambiz
• Assistant Examiner(s): Tran; Tongoc
• Application Number:
  US11/089,840
• Publication Number:
  US 20060218548A1
• Time in Patent Office: 1,992 Days
• Field of Search: 713/191, 709/220, 709/229, 717/174, 717/140, 717/121
• US Class Current: 717/174
• 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. One or more device-readable storage media encoded with device-readable instructions that when executed by a processor cause the processor to perform steps comprising:

building core components from core components codes for a server including the processor;

installing and configuring only the built core components in the server wherein, after the built core components are installed and configured in the server, the server is operational to perform basic functions of a network computing device;

receiving a selection to further configure the operational server to perform functions related to a role for the server;

automatically identifying role-specific software components corresponding to the role;

building the role-specific software components from role components codes that are distinct from the core components codes;

installing only the built role-specific software components corresponding to the role in the operational server; and

configuring the installed role-specific software components in the operational server wherein, after the role-specific software components are installed and configured in the server, the operational server is further configured to perform functions related to the role.

2. The one or more device-readable media as recited in claim 1, the steps further comprising:

receiving selections of preferences associated with the role; and

configuring the role-specific software components corresponding to the role in accordance with the selected preferences.

3. The one or more device-readable media as recited in claim 1, the steps further comprising:

determining a manifest associated with the role, the manifest including information about the role-specific software components corresponding the role; and

automatically identifying the role-specific software components based, at least in part, on the information included in the manifest.

4. The one or more device-readable media as recited in claim 3, the steps further comprising building, installing, and configuring the role-specific software components based, at least in part, on the information included in the manifest.

5. The one or more device-readable media as recited in claim 1, the steps further comprising:

creating identifiers indicating the selected role and the installed role-specific software components associated with the selected role; and

including the identifiers in a program registry in the server.

6. The one or more device-readable media as recited in claim 1, the steps further comprising:

identifying applications in the operational server that will be affected by installing the role-specific software components associated with the selected role; and

providing a notification about the identified applications prior to installing the role-specific software components.

7. The one or more device-readable media as recited in claim 1, wherein the role includes at least one of file service, print service, directory service, domain name service (DNS), dynamic host configuration protocol (DHCP) service, update services, Sharepoint, application service, web server, terminal service, media server, remote authentication dial-in user service (RADIUS), application gateway, virtual private network (VPN) service, certificate service, active directory, federation service, universal description, discovery and integration (UDDI), Active Directory, Active Directory Application Mode (ADAM) or rights management service.

8. A system for configuring a server, comprising:

a server installer configured to install and configure only core components on the server, core components codes comprising the core components, wherein, after the core components are installed and configured on the server, the server is operational to perform basic functions of a network computing device;

a role management tool configured to identify a selection of a role for the operational server;

the role management tool further configured to build role-specific software components from role components codes that are distinct from the core components codes, the role-specific software components corresponding to the selected role and based, at least in part, on information in a manifest associated with the selected role, wherein the role components codes are distinct from the core components codes;

the role management tool further configured to install only the role-specific software components on the server; and

the role management tool further configured to configure the software components in accordance with the selected role.

9. The system as recited in claim 8, further comprising the role management tool further configured to identify the selected role and the associated role-specific software components using at least one of a registry or a role API call.

10. The system as recited in claim 8, further comprising the role management tool further configured to identify applications affected by installing the role-specific software components associated with the selected role and to provide a notification about the identified applications.

11. The system as recited in claim 8, further comprising the role management tool further configured to determine whether prerequisite components are installed on the server prior to installing the role-specific software components corresponding to the selected role.

12. A method comprising:

building core components from core components codes for a server including a processor;

installing and configuring only the built core components in the server wherein, after the built core components are installed and configured in the server, the server is operational to perform basic functions of a network computing device;

receiving a selection to further configure the operational server to perform functions related to a role for the server;

automatically identifying role-specific software components corresponding to the role;

building the role-specific software components from role components codes that are distinct from the core components codes;

installing only the built role-specific software components corresponding to the role in the operational server; and

configuring the installed role-specific software components in the operational server wherein, after the role-specific software components are installed and configured in the server, the operational server is further configured to perform functions related to the role.

13. The method of claim 12 further comprising:

determining a manifest associated with the role, the manifest including information about the role-specific software components corresponding the role; and

automatically identifying the role-specific software components based, at least in part, on the information included in the manifest.

14. The method of claim 13 further comprising building, installing, and configuring the role-specific software components based, at least in part, on the information included in the manifest.

15. The method of claim 12 further comprising:

creating identifiers indicating the selected role and the installed role-specific software components associated with the selected role; and

including the identifiers in a program registry in the server.

16. The method of claim 12 further comprising:

identifying applications in the operational server that will be affected by installing the role-specific software components associated with the selected role; and

providing a notification about the identified applications prior to installing the role-specific software components.

17. The method of claim 12, wherein the role includes at least one of file service, print service, directory service, domain name service (DNS), dynamic host configuration protocol (DHCP) service, update services, Sharepoint, application service, web server, terminal service, media server, remote authentication dial-in user service (RADIUS), application gateway, virtual private network (VPN) service, certificate service, active directory, federation service, universal description, discovery and integration (UDDI), Active Directory, Active Directory Application Mode (ADAM) or rights management service.