server 2012 roles and features.docx

8/17/2019 Server 2012 Roles And Features.docx

1/22

A colleague asked me earlier today if I knew off the top of my head how many roles and features

there are inWindows Server 2012, and I had to admit that I did not know. As Albert Einstein once

said, why memorize what you can reference. However as a quick exercise I decided to not only

count them, but type them up into an article for Kalvin… and for all of you!

NOTE:I included all of the sub-roles and sub-features as well for all except for the Remote Server

Administration Tools, which would show a tool for all of the roles and features.

Roles:

1. Active Directory Certificate Services

2. Active Directory Domain Services

3. Active Directory Federation Services

4. Active Directory Lightweight Directory Services

5. Active Directory Rights Management Services

6. Application Server

7. DHCP Server

8. DNS Server

9. Fax Server

10. File and Storage Services

a. File and iSCSI Services

i. File Server

ii. BranchCache for Network Files

iii. Data Deduplication

iv. DFS Namespaces

http://aka.ms/downloadserver2012http://aka.ms/downloadserver2012http://aka.ms/downloadserver2012


2/22

v. DFS Replication

vi. File Server Resource Manager

vii. File Server VSS Agent Services

viii. iSCSI Target Server

ix. iSCSI Target Storage Provider

x. Server for NFS

b. Storage Services

11. Hyper-V

12. Network Policy and Access Services

13. Print and Document Services

14. Remote Access

15. Remote Desktop Services

16. Volume Activation Services

17. Web Server (IIS)

Features:

1. .NET Framework 3.5 Features

a. .NET Framework 3.5 (includes .NET 2.0 and 3.0)

b. HTTP Activation

c. Non-HTTP Activation

2. .NET Framework 4.5 Features


3/22

a. .NET Framework 4.5

b. ASP.NET 4.5

c. WCF Services

i. HTTP Activation

ii. Message Queuing (MSMQ) Activation)

iii. Named Pipe Activation

iv. TCP Activation

v. TCP Port Sharing

3. Background Intelligent Transfer Service (BITS)

a. IIS Server Extension

b. Compact Server

4. BitLocker Drive Encryption

5. BitLocker Network Unlock

6. BranchCache

7. Client for NFT

8. Data Center Bridging

9. Enhanced Storage

10. Failover Clustering

11. Group Policy Management

12. Ink and Handwriting Services

13. Internet Printing Client


4/22

14. IP Address Management (IPAM) Server

15. iSNS Server Service

16. LPR Port Monitor

17. Management OData IIS Extension

18. Media Foundation

19. Message Queuing

a. Message Queuing Services

b. Message Queuing DCOM Proxy

20. Multipath I/O

21. Network Load Balancing

22. Peer Name Resolution Protocol

23. Quality Windows Audio Video Experience

24. RAS Connection Manager Administration Kit (CMAK)

25. Remote Assistance

26. Remote Differential Compression

27. Remote Server Administration Tools

28. RPC over HTTP Proxy

29. Simple TCP/IP Services

30. SMTP Server

31. SNMP Server

a. SNMP WMI Provider


5/22

32. Subsystem for UNIX-based Applications (Deprecated)

33. Telnet Client

34. Telnet Server

35. TFTP Client

36. User Interfaces and Infrastructure

a. Graphical Management Tools and Infrastructure

b. Desktop Experience

c. Server Graphical Shell

37. Windows Biometric Framework

38. Windows Feedback Forwarder

39. Windows Identity Foundation 3.5

40. Windows Internal Database

41. Windows PowerShell

a. Windows PowerShell 3.0

b. Windows PowerShell 2.0

c. Windows PowerShell ISE

d. Windows PowerShell Web Access

42. Windows Process Activation Service

a. Process Model

b. .NET Environment 3.5

c. Configuration APIs


6/22

43. Windows Search Service

44. Windows Server Backup

45. Windows Server Migration Tools

46. Windows Standards-Based Storage Management

47. Windows System Resource Manager (Deprecated)

48. Windows TIFF IFilter

49. WinRM IIS Extension

50. WINS Server

51. Wireless LAN Service

52. WoW64 Support

53. XPS Viewer

Now: Adding roles and features inWindows Server 2012 is easier than it was previously… either use

theAdd Roles and Features Wizard (See my article and videohere). Or you can use Windows

PowerShell (which is the preferred way to do it) by using the cmdletInstall-WindowsFeature

. Eventhough there is a distinction between Roles and Features, the cmdlet to install them is the same for

both.

PART - 1

http://aka.ms/downloadserver2012http://garvis.ca/2012/10/11/server-manager-manage-multiple-servers-just-got-easier/http://aka.ms/downloadserver2012http://garvis.ca/2012/10/11/server-manager-manage-multiple-servers-just-got-easier/


7/22

Introduction

By now you have probably heard that with its Metro interface and redesigned Server Manager, indows Server !"1!

is vastly different fro# its predecessors$ %n fact, #any ad#inistrators initially find the#selves having trouble

perfor#ing even so#e of the #ost basic tas&s because the interface is so different fro# what they are used to$ That

being the case, % decided to write an article series that wal&s you through the process of perfor#ing co##on tas&s in

a indows Server !"1! environ#ent$

Rebooting the Server

The one thing that % personally had the toughest ti#e figuring out when % first got started with indows Server !"1!

was rebooting the server$ After all, the Start #enu is gone, and so is the shut down option that has always e'isted on

the Start #enu$

To power down (or reboot) your server, #ove your #ouse to the upper, right corner of the screen$ hen you do,

indows will display a series of icons along the right side of the screen$ *lic& the Settings icon and you will be ta&en

to the Settings page, which you can see in +igure A$ As you can see in the figure, the botto# row of icons includes a

Power button$ ou can use this icon to shut down or to reboot the server$

Figure A: se the Power icon to shut down or reboot the server$

Accessing the Control Panel

Another tas& that so#e ad#inistrators have struggled with is that of accessing the *ontrol Panel$ There are actually

several different ways to get to the *ontrol Panel, but % will show you the two #ost co##on #ethods$

The first #ethod is to use the sa#e set of icons that % showed you in the previous step$ Move your #ouse to the

upper, right corner of the screen and then clic& on Settings$ hen the Settings page appears, clic& the *ontrol Panel

lin&, which you can see in +igure A$


8/22

Another way to access the *ontrol Panel is to go into .es&top #ode and then #ove your #ouse pointer to the lower

left corner of the screen$ hen you do, the Start tile will appear$ Right clic& on this tile and a #enu will appear$ This

#enu contains an option to access the *ontrol Panel, as shown in +igure B$

Figure B: ou can access the *ontrol Panel by right clic&ing on the Start tile and selecting the *ontrol Panel option

fro# the resulting #enu$

Accessing the Administrative Tools

%n indows Server !""/ and !""/ R!, you could access the ad#inistrative tools by clic&ing the Start button, and

then going to All Progra#s and clic&ing the Ad#inistrative Tools option$ 0eedless to say, since the Start #enu no

longer e'ists, you have to access the ad#inistrative tools in a new way$

There are a couple of different ways to access the ad#inistrative tools in indows Server !"1!$ ne way involves

using the Server Manager$ As you can see in +igure *, the Server Manager2s Tools #enu contains all of the

ad#inistrative tools that you are probably fa#iliar with fro# indows Server !""/$

Figure C: The ad#inistrative tools are accessible fro# the Server Manager2s Tools #enu$

f course it2s &ind of a pain to have to go into the Server Manager every ti#e that you need to access an

ad#inistrative tool$ %t would be a lot easier if the tools were accessible fro# the Start screen$ The good news is that it

is easy to #a&e that happen$

To do so, #a&e sure that you are loo&ing at the indows Start screen$ This techni3ue won2t wor& if you are in

.es&top #ode$ 0ow, #ove your #ouse to the upper right corner of the screen and then clic& on the Settings icon$

hen the Settings page appears, clic& on the Tiles lin&$ As you can see in +igure ., there is a slide bar that you canuse to control whether or not the Ad#inistrative Tools are shown on the Start screen$ ou can see the Ad#inistrative

Tools icon in the lower left corner of the screen capture$


9/22

Figure D: ou can use the slide bar to enable the Start screen to display the ad#inistrative tools$

Accessing Your Applications

Perhaps one of the #ost frustrating aspects of the new interface is that applications are no longer bound to a

centrali4ed Start #enu$ This #ight not be such a big deal if all of your applications happen to have tiles on the Start

screen, but what happens if certain tiles are 5#issing67

So#e ad#inistrators have found that after upgrading fro# a previous version of indows Server that their Start

screen contains only a s#all subset of the ite#s that previously resided on their server2s Start screen$ The good news

is that these #issing ite#s are not lost$ ou 8ust have to &now where to loo& for the#$

To access all of the tiles that the Start screen is hiding, right clic& on an e#pty area of the Start screen$ hen you do,

a blue bar will appear at the botto# of the screen, as shown in +igure 9$ *lic& on the All Apps icon that appears on

this bar$ hen you do, you will be ta&en to an Apps screen that2s si#ilar to the one shown in +igure +$ As you can see

in the figure, the apps are categori4ed in a #anner si#ilar to how they #ight have been on the Start #enu$


10/22

Figure : Right clic& on an e#pty area of the Start screen to reveal the blue bar and the All Apps icon$

Figure F: The Apps screen contains all of the #issing tiles$

The Run Prompt and the Command !ine

%n previous versions of indows Server, % used the Run pro#pt and the *o##and :ine e'tensively$ +or e'a#ple, if

you needed to access a utility such as the .is& Manage#ent *onsole, the easiest way to get to it was to clic& on the

Run pro#pt and enter the .%S;M


11/22

Si#ilarly, % also spent a lot of ti#e in a *o##and Pro#pt environ#ent$ Sure, PowerShell is the way of the future, but

there are so#e co##ands that 8ust don2t wor& in a PowerShell environ#ent$ Most of the co##and line utilities will

only wor& fro# a true co##and line environ#ent$ +or e'a#ple, the 9S9T%: tool that co#es with 9'change Server

!"1" is designed to be used fro# a *o##and Pro#pt and it doesn2t wor& in PowerShell$

+ortunately, the Run pro#pt and the *o##and Pro#pt are both easily accessible$ To reach these ite#s, navigate

into .es&top #ode$ pon doing so, #ove your #ouse pointer to the lower, left corner of the screen$ hen the Starttile appears, right clic& on it and you will see a #enu listing options for Run, *o##and Pro#pt and *o##and Pro#pt

(Ad#in)$

Conclusion

Although the indows Server !"1! interface can be confusing at first, the vast #a8ority of the ite#s that were

available in the indows Server !""/ R! interface still e'ist$ ou 8ust have to &now where to loo& for the#$ %n Part !,

% will show you how to perfor# so#e #ore basic #anage#ent tas&s in indows Server !"1!$


12/22

Part - !

Introduction

% spent #ost of the first part of this series showing you how indows Server !"1!2s new user interface wor&s$ %n this

article, % want to shift gears a little bit and wal& you through so#e co##on tas&s that you #ight typically need toperfor# when setting up a new server$

Renaming the Server

Although indows Server !"1! auto#atically assigns each server a rando# na#e, ad#inistrators often li&e to

change the na#e to so#ething #ore #eaningful$ This is especially true in virtual server environ#ents where it can

beco#e 3uite confusing if the server2s co#puter na#e (the na#e used by indows to identify the server) doesn2t

#atch the virtual #achine na#e (the na#e displayed within the =yper-> Manager)$

To rena#e a server, #ove the #ouse pointer to the lower left portion of the screen to reveal the Start tile$ Right clic&

on this tile and select the Syste# co##and fro# the shortcut #enu$ pon doing so, indows Server !"1! will

display the Syste# dialog bo', which is nearly identical to the version used in indows Server !""/ and !""/ R!$ou can see what this loo&s li&e in +igure A$

Figure A: ou can use the Syste# dialog bo' sheet to change the co#puter na#e$

0ow clic& on the *hange Settings lin& and indows will display the Syste# Properties sheet$ Ma&e sure that the

*o#puter 0a#e tab is selected and then clic& the *hange button$ 9nter the new co#puter na#e and clic& ;$ ou

will have to reboot the server in order for the change to ta&e effect$

Assigning an IP Address to the Server


13/22

The process of assigning an %P address to a indows Server !"1! server is very si#ilar to the #ethod used in

indows Server !""/ and !""/ R!$ Begin the process by #oving the #ouse to the lower left corner of the screen to

reveal the Start tile$ Right clic& on the Start tile and then choose the *ontrol Panel option fro# the resulting #enu$

hen the *ontrol Panel opens, clic& on the 0etwor& and %nternet lin&, shown in +igure B$ 0e't, clic& on 0etwor& and

Sharing *enter, followed by *hange Adapter Settings$

Figure B: *lic& on the 0etwor& and %nternet lin&$

At this point, indows should display a series of networ& adapters$ Right clic& on the adapter to which you want to

assign an %P address and choose the Properties co##and fro# the shortcut #enu$ Scroll through the list of

networ&ing co#ponents and select the %nternet Protocol >ersion ? (T*P@%Pv?) co#ponent and clic& Properties$ ou

will now be ta&en to a screen that allows you to enter an %P address for the adapter$ After doing so, clic& ;$

ne thing that you need to &now about %P address assign#ents in indows Server !"1! is that you #ust be careful

to only assign %P addresses to adapters that are not being used for other purposes$ +or e'a#ple, if an adapter is

being used by =yper-> then the only co#ponent that should be enabled for that adapter is the =yper-> 9'tensible

>irtual Switch$ ou cannot assign an %P address directly to the adapter without causing proble#s$ %nstead, =yper->

creates a virtual networ& adapter on the physical server$ This virtual networ& adapter corresponds to the physical

networ& adapter, and that is where you should #a&e the %P address assign#ent$

The sa#e basic concept applies to indows !"1! servers that are using a 0%* tea#$ hen you create a 0%* tea#,you are binding #ultiple networ& adapters together into a logical networ& adapter$ The 0etwor& Adapters screen

displays the physical networ& adapters alongside the 0%* tea#, as shown in +igure *$ The only co#ponent that

should be enabled on tea#ed physical adapters is the Microsoft 0etwor& Adaptor Multiple'or protocol$ %P address

assign#ents #ust be #ade only to the tea#ed 0%*, not to individual 0%*s within the tea#$


14/22

Figure C: The 0etwor& *onnections screen shows physical networ& adapters and 0%* tea#s$

"oining a Server to a Domain

The process of 8oining a indows Server !"1! server to an Active .irectory do#ain is very si#ilar to the #ethod that

% previously de#onstrated for rena#ing a server$ ;eep in #ind however, that before you can 8oin a server to a

do#ain, the server #ust be able to co##unicate with the do#ain$ Specifically this #eans that the server2s %P

address configuration #ust reference the do#ain2s .0S server$ therwise, indows will be unable to contact ado#ain controller during the do#ain 8oin$

To 8oin the server to a do#ain, #ove your #ouse pointer to the lower, left corner of the screen and then right clic& on

the Start tile$ Select the Syste# co##and fro# the Start tile2s #enu$ hen the Syste# dialog bo' appears, clic& the

*hange Settings lin&, which you can see in +igure A$ The server should now display the Syste# Properties sheet$

Ma&e sure that the *o#puter 0a#e tab is selected and then clic& the *hange button$ hen indows .isplays the

*o#puter 0a#e @ .o#ain *hanges dialog bo' shown in +igure ., enter your do#ain na#e and clic& ;$ indows

will locate the do#ain and then pro#pt you for a set of ad#inistrative credentials$ hen the do#ain 8oin co#pletes

you will be pro#pted to restart the server$

Figure D: 9nter your do#ain na#e and clic& ;$


15/22

Disabling Internet #plorer nhanced Securit$ Con%iguration

%n indows Server !"1!, Microsoft uses a #echanis# called %nternet 9'plorer 9nhanced Security *onfiguration to

loc& down %nternet 9'plorer, thereby #a&ing it #ore or less unusable$ The good news is that you can disable %nternet

9'plorer 9nhanced Security *onfiguration$

Before % show you how to acco#plish this, % need to point out that %nternet 9'plorer 9nhanced Security *onfigurationis put in place for your protection$ The %nternet is not a ris&less place, and it is possible to infest a co#puter with

#alware 8ust by accidentally visiting a #alicious eb site$ Most security professionals agree that you should never

use a eb browser directly fro# a server console$

hile % certainly agree with the senti#ent of these ideas, % find that % often need access to the %nternet when % a#

setting up a new server$ ften ti#es % will need to download patches, drivers, etc$ and %nternet 9'plorer 9nhanced

Security *onfiguration gets in the way$ hat % usually do (and this is by no #eans a reco##endation) is to disable

%nternet 9'plorer 9nhanced Security *onfiguration, download anything that % need, and then re-enable %nternet

9'plorer 9nhanced Security *onfiguration$

To disable %nternet 9'plorer 9nhanced Security *onfiguration, open the Server Manager and then clic& on the :ocal

Server tab$ hen you do, the console will display the local server properties$ *lic& on the n&nown lin& ne't to %9

9nhanced Security *onfiguration, as shown in +igure 9$

Figure : *lic& on the n&nown lin& ne't to %9 9nhanced Security *onfiguration$

ou will now see a dialog bo' that allows you to enable or disable this co#ponent$ %nternet 9'plorer 9nhanced

Security *onfiguration can be enabled or disabled separately for users and for ad#inistrators$

Conclusion

%n this article, % have wal&ed you through a few basic configuration tas&s in indows Server !"1!$ %n Part % will

continue the discussion by showing you how to perfor# so#e #ore co##on configuration tas&s$


16/22

Part -

%ntroduction

My goal throughout this series has been to wal& you through the process of perfor#ing co##on#anage#ent tas&s in indows Server !"1!$ indows Server !"1!2s version of the ServerManager is radically different fro# what was included in previous versions of indows Server$That being the case % wanted to try to help people by de#onstrating so#e of the #ore co##on#anage#ent tas&s$

*onfiguring the indows +irewall

So#e ad#inistrators li&e to control the indows +irewall through group policy settings, but others configure the

firewall #anually (especially in s#aller shops)$ %f you need to access the indows +irewall you can do so by opening

the Server Manager and then choosing the indows +irewall with Advanced Security co##and fro# the Tools #enu,

as shown in +igure A$

Figure A: ou can open the configuration interface for the indows +irewall by choosing the indows +irewall with

Advanced Security co##and fro# the Server Manager2s Tools #enu$

Adding Roles and +eatures

The process of adding new roles and features to indows Server !"1! is at least so#ewhat intuitive$ The easiest

way to acco#plish this is to open the Server Manager and choose the Add Roles and +eatures co##and fro# the


17/22

Manage #enu, as shown in +igure B$ This causes indows to launch the Add Roles and +eatures wi4ard$ %n #any

ways this wi4ard is si#ilar to what you #ight be used to in so#e of the previous versions of indows Server, but

there are a few differences$

Figure B: ou can launch the Add Roles and +eatures i4ard by choosing the Add Roles and +eatures co##and

fro# Server Manager2s Manage window$

hen the wi4ard begins, clic& 0e't to bypass the elco#e screen$ The ne't screen that you will see as&s you if youwant to perfor# a Re#ote .es&top Services installation or if you would prefer to perfor# a role based or a feature

based installation$ nless you are configuring the server to run the Re#ote .es&top Services, you should choose the

Role Based or +eature Based %nstallation option$ *lic& 0e't to continue$

The ne't screen that you will see is very different fro# anything that e'isted in previous versions of indows Server$

This screen as&s you where you would li&e to install the role or feature$ Although this is a see#ingly si#ple 3uestion,

the wi4ard gives you a few different options, as shown in +igure *$

Figure C: ou #ust tell indows where you want to install the role or feature$


18/22

%n previous versions of indows Server it was assu#ed that if you were installing a role or a feature then you were

perfor#ing the installation on the local server$ indows Server !"1! still allows you to perfor# local installations of

roles and features$ As a #atter of fact, this is the default behavior$ %f you were to si#ply clic& 0e't on the screen

above then the wi4ard would assu#e that the roles or features that you choose later on will be installed on the local

server$ Although this is the default behavior, it is not your only option$

%f you loo& closely at the screen capture shown above, you will notice that the option that is selected allows you toselect a server fro# a server pool$ %n indows Server !"1!, a server pool is si#ply a collection of servers that can be

#anaged through Server Manager$ As it stands right now, no additional servers have been added to the server pool

for the lab server that was used to create the figure above$ %f additional servers had been added to the server pool

however, those servers would appear directly beneath the server that is selected$ % will show you how to add a server

to the server pool a little bit later on$

The other option that appears on the screen capture is the option to select a virtual hard dis&$ Previous versions of

indows Server re3uired you to install roles and features on a running copy of indows$ This isn2t the case in

indows Server !"1!$ %t is actually possible to install a role or a feature on to a virtual hard dis& that contains a

indows Server installation that is not currently running$

hen you clic& 0e't, you will see a screen displaying all of the various server roles that you can install$ The list of

server roles really isn2t all that different fro# those found in indows Server !""/$ hen you #a&e your selectionyou can clic& 0e't and you will be ta&en to the +eatures screen$ =ere you can choose the features that you want to

install$

hen you clic& 0e't once again, you will see a confir#ation screen that provides infor#ation about the roles were

features that are about to be installed$ %t is a good idea to ta&e 8ust a #o#ent to read this screen and verify that the

roles or features that are about to be installed are the ones that you intended$ Assu#ing that all is well, you can clic&

the %nstall button to perfor# the installation$

Adding Servers to the Server Pool

%n the previous section, % #entioned that it was possible to add additional servers to the server pool so that those

servers could be #anaged through Server Manager$ The advantage to populating the server pool is that doing soallows you to #anage #ultiple indows servers through a single pane of glass$

%f you want to add additional servers to the server pool, open Server Manager and choose the Add Servers co##and

fro# the Manage #enu as shown in +igure .$ hen you do, you will see the dialog bo' shown in +igure 9$

Figure D: To add servers to the server pool choose the Add Servers co##and fro# the Manage #enu$


19/22

Figure : ou can use this dialog bo' to add servers to the server pool$

As you can see in the figure, indows provides three different #ethods for adding servers to the server pool$ %n #ost

cases, you will probably want to use the Active .irectory tab$ This tab allows you to specify the na#es of co#puters

that are registered in the Active .irectory database$ ou will notice in the figure above that indows gives you the

option of specifying the co#puter2s location, and you can even filter the search results by operating syste#$

Another option is to specify co#puters by their fully 3ualified do#ain na#es or by %P address$ This can be

acco#plished through the .0S tab$ The .0S tab is useful for adding co#puters that e'ist on your networ&, but that

are not #e#bers of an Active .irectory do#ain$ +or e'a#ple, edge servers are al#ost never do#ain #e#bers$

+inally, the %#port tab is used for i#porting large nu#bers of co#puters$ This #ethod allows you to add all of the

co#puters to a file, and then i#port that file rather than having to i#port each co#puter individually$ nce added, the

servers in the pool will be accessible through the Server Manager, as shown in +igure +$

Figure F: Server Manager can be used to #anage #ultiple co#puters$

*onclusion

%n this article, % have e'plored so#e #ore of the basics of wor&ing with indows Server !"1!$ %n Part ? % plan to

conclude this series by showing you so#e #ore techni3ues for wor&ing with roles and features$

Part & '


20/22

Introduction

Throughout this article series, #y goal has been to e'plain how to perfor# the #ost basic and co##on configuration

tas&s using indows Server !"1!$ %n this article, % plan to wrap up the series by wal&ing you through a few #ore

techni3ues$

(or)ing *ith Roles and Features

%n the previous article % wal&ed you through the process of installing roles and features onto indows Server !"1!$ %

want to wrap up this series by showing you what to do after the roles and features have been installed$

%f you loo& at +igure A, you will see the Server Manager dashboard$ There are several ite#s on this screen that are

worth paying attention to$

Figure A: This is the Server Manager dashboard$

The first thing that you will probably notice is the big, orange section near the center of the screen$ This section is

designed to help you to 3uic&ly get the server configured$ As you can see in the figure, this section contains lin&s that

you can clic& to add roles and features, add other servers to #anage, or to create server groups$ As you have seen

throughout this series, all of these tas&s can be perfor#ed #anually, but if you forget how to do so then you can

si#ply clic& on one of these lin&s to get the ball rolling$

The ne't thing that % want to point out is the colu#n on the left$ This colu#n lists a nu#ber of different Server

Manager views$ At the #o#ent the .ashboard view is selected, but you can switch to a different view by clic&ing on

the view$

So#e of the views that are listed are standard for indows Server !"1!$ The .ashboard, :ocal Server, All Servers,

and +ile and Storage Services views are created by default$ There are also views that #ay e'ist as a result of the

way that you have configured your server$ +or e'a#ple, in the figure above the A. .S, .0S, and =yper-> views

e'ist as a direct result of installing the corresponding roles and features$ The botto# two ite#s on the list are :ab

Servers and Production Servers$ These are actually co#puter groups that % #anually created at an earlier ti#e$


21/22

% want to delve into views a little bit #ore, and tal& about how the views relate to the roles and features that are

installed$ Before % do that though, ta&e a loo& at the lower portion of the screen capture shown in +igure A$ This

section contains a series of bo'es for the roles and server groups that e'ist on the server$

As you can see in the figure, each bo' corresponds to a specific role or server group$ The bo'es are color coded$

Bo'es display green to indicate that there are no issues related to the particular role or server group$ *onversely, the

red bo'es indicate that there are issues that need to be addressed$

These bo'es are designed to help #a&e it easy for you to resolve the issues that have been detected$ %f you loo&

bac& at the figure, you will notice that each of the red bo'es contains a nu#ber 8ust to the right of the bo' na#e$ This

nu#ber reflects the nu#ber of issues that need to be resolved$

%f you loo& beneath each bo'2s header, you will see a series of categories listed (Manageability, 9vents, Services,

Perfor#ance, BPA Results)$ A red flag to the left of a category indicates that there are issues related to that category

that need to be resolved$ +or e'a#ple, in the screen capture the :ab Servers server group has two #anageability

and one service related issue that need to be addressed$

Before % show you how to e'a#ine these issues, % need to 3uic&ly clarify one thing$ The Server Manager has a way of

#a&ing these issues see# critical because of the way that the issues are displayed in red$ %n #ost cases however,

you will li&ely find that the issues that have been detected are anything but critical$

To atte#pt to resolve an issue, si#ply clic& on the issue category$ This causes indows to display a detail view$ +or

e'a#ple, when % clic& Manageability under =yper->, indows displays the screen shown in +igure B$

Figure B: This screen was displayed when % clic&ed the Manageability container in the =yper-> bo'$

As you can see in the figure above, the dialog bo' identifies the source of the proble#$ %n this case the server needs

to be restarted$

There is however, one #ore i#portant piece of infor#ation displayed in this dialog bo' that #ight not be readily

apparent fro# the screen capture$ %f you loo& closely at the alert that is being displayed, you will notice that the server


22/22

na#e and the server2s %P address are both listed as a part of the alert$ The reason why % bring this up is because in

the screen capture above the alert that is displayed actually pertains to a re#ote server that is not even powered on

at the #o#ent$ Therefore, when you see alert #essage is displayed in the Server Manager dashboard, you cannot

auto#atically assu#e that the alerts are for the local server$ ften ti#es, the alerts pertain to re#ote #achines

instead$

bviously, correcting this alert would have been as easy as turning on the server that is #entioned and then allowingit to reboot$ hat if the proble# had been #ore serious though7 %f the proble# had been #ore serious than the alert

should have at least given a hint as to the cause of the proble#$ The dialog bo' also contains a

button that could be used to open the interface that is needed to correct the proble# (in this case the =yper-> view)$

0ow that % have shown you how the alert bo'es wor&, % want to go bac& and tal& a little bit #ore about the views that %

#entioned earlier$ As previously #entioned, #any of the views are specifically related to roles or features that have

been installed on the server$ hen you clic& on a role or feature related view, Server Manager displays a nu#ber of

pieces of infor#ation related to that view$ ou can see an e'a#ple of this in +igure *$

Figure C: Selecting the =yper-> view causes Server Manager to display infor#ation related to =yper->$

As you can see in the figure above, selecting the =yper-> view causes indows to display the =yper-> servers, and

events and services related to =yper->$ %f you were to scroll down, you would find the Best Practices Analy4er, the

Perfor#ance Monitor, and infor#ation about the =yper-> role$ All of these tools can be accessed in other places

throughout the operating syste#, but Server Manager puts the# all together in one place for you$

Conclusion

Throughout this article series, % have discussed so#e of the #ost co##on #anage#ent and configuration tas&s thatyou will have to perfor# when you are first getting a indows !"1! server up and running$ As you can see, the

general configuration process for indows Server !"1! really isn2t all that different fro# earlier versions of indows

Server$ %t is si#ply the new user interface that ta&es so#e getting used to$

server 2012 roles and features.docx

Documents