Home / Windows 7 / Getting Started

---

Application-Oriented Servers

Application-oriented servers are servers that provide specific application services to end users. Because of this, they are part of the virtual service offerings infrastructure. The servers in this category include:

• Application servers Servers that host applications that provide specific functionality to end users. These servers provide application services based on either commercial software, such as Exchange Server, SQL Server, Commerce Server, and so on, or on custom corporate applications. This also includes applications based on the .NET Framework. A good example of an application based on .NET Framework is PowerShell, since it requires .NET Framework to support its many cmdlets.
• Dedicated Web servers Servers that run Web application services in a single-purpose server model. This role is based on the Web edition of Windows Server 2008 (WS08). They are similar to the Application Server role, but only focus on Internet Information Services (IIS) or Web service applications.
• Terminal servers Servers that centrally host applications and provide access to them through a thin client model. The entire execution environment resides on the server itself.
• Collaboration servers Servers that host applications that are specifically designed to support collaboration efforts between end users. Examples of their services include, among others, Windows SharePoint Services (WSS) and Streaming Media Services.

NOTE: Streaming Media Services are also known as Windows Media Services and are not part of WS08 by default. You must download them at www.microsoft.com/windows/windowsmedia/forpros/server/server.aspx. In addition, WSS is now part of Server Manager's ability to integrate other roles and features from the Microsoft download center or the Windows Update Web site.

These roles are the last server roles you need to set up before you can begin to move end users into the parallel network and provide them with a full complement of services. Once again, the structure for the coverage of each of these server roles includes:

• Functional requirements: Discussions on how the service must be designed for the enterprise network and the rationale for the service.
• Features: Features supporting the role or service within WS08 (includes new features).
• Implementation instructions: How to proceed with the preparation of the server role within the parallel virtual service offerings (VSO) network environment.

The roles mentioned here are normally assigned to member servers. As with the file and print server roles, it will also be important to cover specific considerations for all server types, such as the network load balancing and failover cluster services. Both offer powerful redundancy features that minimize risk within your organization. The table at the end of this tutorial outlines the resource requirements to build each server role covered here. It serves as a guide for server role construction.

Finally, once the basis for network services has been covered, it will be time to continue the design of the Virtual Service Offerings organizational unit (OU) structure within the directory. As with the People and PC OU structures, this design includes both Group Policy Object (GPO) and delegation principles, but it will also involve the unique design of a services administration plan. WS08 offers the capability to assign specific administrative rights based on the task the administrator is responsible for. You no longer need to grant domain administration rights to one and all just to let them perform their work. This services administration plan will be a key element of your security infrastructure for the enterprise network.

The Virtual Service Offerings OU structure is built up as each service is added to the network. It is at this point that more OU contents will be identified. Once each additional service has been covered, the administrative, delegation, and Group Policy requirements for each will be covered in detail.