Windows Server 2008 Server Manager Configuration Role

Differences between roles and functions

What can I do with Server Manager

Using Wizards

Managing Roles and Functions from the Command Line

One of the themes that runs through Windows Server 2008 is "simple". This does not mean that some features are removed unnecessarily. Instead, this is a strategy to simplify and clarify roles and tools so that you only install the content you need, and nothing is installed. Server Manager

is an important part of this concept in Windows Server® 2008.

It contains two aspects. The first is the most important concept about server roles and features, which are building blocks for Windows Server 2008. Followed by the "Server Manager" tool itself. Not only will this tool replace many of the tools used in Windows Server 2003, but it will also introduce multiple features in one place, making it easier for administrators like you to do more work faster and easier.

Role and Features

If you've read articles about Windows Server 2008, you're likely to encounter terms that you haven't heard of in the context of Windows®, such as “ Workload & rdquo; and “ role & rdquo; and so on. First I will explain what these terms mean for IT professionals.

At the beginning of the Windows Server 2008 development cycle, we spent a lot of time trying to understand how users use our server products. (By the way, this effort is still going on.) In general, we found that people deploying our servers generally do something specific. This may not sound difficult to understand, but for some of us, it's amazing to know that people don't make the server they buy fully functional. More importantly, they don't deploy servers to do a huge number of tasks. Instead, they want a server to perform only specific tasks. Of course, there are some exceptions, but in most cases, a server is provisioned to perform specific functions.

For these experiences, we group “specific things> into a broad category called workload. For example, there is a database workload and an application server workload. Because of the heavy workload and sometimes ambiguity, we created some subcategories in the workload, calling them roles. A role is a single, very targeted thing that a server has to do. Think about how you (and the users within your organization) refer to servers on the network. If you are like most users, you might think of them as file servers, domain controllers, print servers, web servers, and so on. Because people are used to seeing servers like this, Windows Server 2008 uses the same approach to handling roles.

Generally speaking, Windows Server 2008 includes three main categories of roles: identity and access management (as part of Active Directory®), infrastructure (including file servers, print servers, DNS, etc.) and Applications such as web server roles and terminal services.

Windows Server 2008 comes with approximately 17 server roles (such as Active Directory Certificate Services, Network Policy and Access Services, and Windows Server virtualization, etc.). Other additional roles (such as streaming service roles) are likely to be available for download.

Every character needs to be introduced in detail. Some of the roles were discussed in detail in this issue of TechNet Magazine, some have been discussed and some are coming soon. You should explore each role one by one, starting with the information in technet2.microsoft.com/windowsserver2008/en/servermanager/default.mspx.

When you start deploying Windows Server 2008, you need to choose which roles to install on each server. This role-based deployment is a very important concept, mainly on how to effectively use Windows Server 2008 and how to make resource deployment more flexible.

The role list does not include such things as <;BitLockerTM Drive Encryption> and "Network Load Balancing" (NLB). This is because these are functional, and although they are very exciting, they are not the real reason why users buy systems. Relatively speaking, the role is the task that needs to be performed after purchasing the system. For example, users do not purchase servers just to implement load balancing. However, they will buy servers in order to provide website services. In addition, although NLB may be an essential aspect of a purpose, such as a web server, it is not the purpose of the server.

We do not install all the features of the server and activate them, but the administrator selects the features that need to be installed. (The list of features included with Windows Server 2008 is shown in Figure 1.) Stability and security are improved because only the required roles and features are included. You no longer have to think about resources that are consumed by unsaved roles or features. It is also unnecessary to consider troubleshooting or security settings for features or roles that are not installed.

Figure1 Features Contained in Windows Server 2008

Microsoft .NET Framework 3.0 Features BitLocker Drive Encryption BITS Server Extensions Connection Manager Administration Kit Desktop Experience Group Policy Management Internet Print Client Internet Storage Name Server (iSNS) LPR Port Monitor Message Queuing Multipath I/O Peer Name Resolution Protocol Windows Audio/Video Experience Quality (qWave) Remote Assistance Remote Server Management Tool Removable Storage Manager RPC Over HTTP Proxy NFS Service SMTP Service Server SAN Storage Manager Simple TCP/IP Service SNMP Service UNIX-based Application Subsystem Telnet Client Telnet Server Common File Transfer Protocol (TFTP) Client Failover Cluster Network Load Balancing Windows Server Backup Windows System Resource Manager Windows Internet Naming Service (WINS) Server Wireless LAN Service Windows Internal Database Windows PowerShell Windows Process Activation Service

The Server Core installation option is the epitome of this concept. Server Core is beyond the scope of this article, but you can see logical extensions with unused roles and features, even without having to copy them to your hard disk or make them available. One major difference between a regular installation and a Server Core installation is that a regular installation includes the resources needed to install additional roles at all times, and it supports all roles. Server Core doesn't even have a GUI as its shell, and only supports a limited number of roles.

Server Manager

Windows Server 2008 The new "Server Manager" console makes it easier to manage and protect multiple server roles in the enterprise. "Server Manager" is essentially an extended Microsoft® Management Console (MMC) that allows you to actually view and manage all the information and tools that affect server productivity. It provides a single source for managing server identification and system information, displaying server status, determining server role configuration issues, and managing all roles installed on the server. (Note that it also replaces multiple features included in Windows Server 2003, such as "Management Server", "Configure Server", "Add or Remove Windows Components", etc.)
< In some cases, "Server Manager" can also reduce the need for administrators to run the Security Configuration Wizard (SCW) before deploying the server. Server Manager will configure your server to make any installed roles work (for example, automatically configure Windows Firewall). However, SCW is still a very valuable tool when roles are deleted after they are added, or if you want more control over precise security settings. For more information, see this issue of Jesper Johansson <Safety Watch" column""Sc" in Windows Server 2008 (microsoft.com/technet/technetmag/issues/2008/03).

When using Windows Server 2008, we have carefully studied how we want administrators to perform tasks. We've found ways to make work easier with tools and wizards, and also found that in some cases, you need to jump between tools. We have developed a common and important design goal for Windows Server 2008 (special purpose for “Server Manager), which makes server management more efficient by allowing administrators to perform multiple types of tasks in a single location. . So, with "Server Manager", you can:

View and change the server roles and features installed on the server.

Perform server-specific administrative tasks such as starting or stopping services, managing local user accounts, and more.

Execute administrative tasks specific to the roles installed on the server.

Check server status, identify critical events, and analyze configuration issues.

Install or remove roles, role services, and features using the GUI or the command line.