Thoughts from the EPS Windows Server Performance Team
Useful Microsoft Blogs
Well, we are about finished. Only one post left after this one. Today marks the 15th post in our Launch Series and I know you’ll enjoy reading this one. With that said, let’s dive right in!
If you have installed Windows Server 2012, I'm sure you have noticed that Server Manager looks a lot different. The previous MMC-based Server Manager worked very well in many respects. The hierarchical organization was very logical and the familiar MMC snap-ins were easy to use. So why change it?
Server Manager has been rewritten from the ground up with a focus on providing true multi-server management support from a single console, as well as extended capabilities for Windows role and feature installation.
Like any UI changes, it might be a little disorienting at first, but once you learn the basics of navigating it, I think you will find it easy to use and very powerful.
When Server Manager first launches, it defaults to the Dashboard configuration view for the local server:
Understanding the layout is key to becoming productive with the new UI. Let's take a look.
The pane on the left side is the primary navigation pane. It always includes the Dashboard, the Local Server, and the All Servers group by default.
The installation of some roles and features adds groups specific to them to the navigation pane. Examples of roles that do this are File and Storage Services, Remote Desktop Services, Hyper-V, and DNS. The entry in the navigation pane for such a role (File and Storage Services in the screen shot above, for example) often has a ">" to the right of it. If you click that entry, it will expose a secondary navigation pane that includes the rest of the management hierarchy for that role.
From that point, you can select entries in the secondary pane to expose tasks related to each topic. This is where most of the management work will be done for a lot of roles and features.
You can add servers to the All Servers group by right-clicking it and selecting Add Servers. You can also create your own group by selecting Create Server Group from the Manage command menu on the command bar (the Command bar is discussed below). Server groups allow you to monitor and manage servers that have been delegated to an administrative person or team, that have related roles, or for which it otherwise makes sense to configure and manage them collectively.
That's the wide gray bar that contains "Server Manager > Dashboard" in our first screen shot. It simply indicates where your current focus is within Server Manager. It functions much like the address bar in Windows Explorer. You can overtype the path, or click on the ">" to select different locations within the path.
The portion of the wide gray bar that includes the flag icon and command options to the right of it. Again, these work like the menus in command bars of applications like Office apps. Click on each to see what commands are exposed.
The notification flag alerts you about actions that need attention. These can include such things as further configuration of a role required or the restart of the system to complete role installation. The notification flag shows the number of available tasks as a number underneath the flag as shown below.
Selecting the flag displays more details about the additional action(s) required.
You can click Task Details to even more details about the specific tasks (I'll spare you the additional screen shot).
The Manage menu includes actions that can be performed to configure Server Manager, or actions to be performed against the server or group selected in the navigation pane(s). The most common tasks are adding or removing roles or features, creating server groups, and adding servers to the selected group.
The Tools menu allows you to launch commonly used administrative tools and applications from within Server Manager. Role or feature installation can add additional tools to this menu based on whether the role or feature includes a tool as part of role installation so the list of available tools can grow with server configuration.
At the bottom of the Dashboard page, you will see a box for each server and group listed in the navigation pane.
These "thumbnails" allow you to monitor and be alerted about issues that might affect the operation of the server(s). Each thumbnail includes a quick status of one or more of these:
As you might guess, Red indicates a threshold has been exceeded and the number of those within each category that exceeded it is displayed. Green means all is well. If you click on each category, you will see more details about each alert, plus you can configure the alert thresholds to suit your needs. Again, I will spare you the gratuitous screen shots. You will get the most benefit from exploring on your own once you know the basics.
Configure this local server
On the Dashboard you will see Configure this local server as the first configuration task. As it implies, this is the first place you want to go to perform basic configuration tasks for any server, including changing the server name, joining a domain, configuring networking, setting time zone, etc.
Each of the items on that page are self-explanatory and are what you would typically see in WS 2008 R2 on the home page of the old Server Manager, in the properties of the Computer, or in the Initial Configuration Tasks.
I'll leave you with a parting tip!
There are perhaps a handful of ways to launch tools or tasks to be performed on a selected server or group. Each can have different options depending on the context (which server or group is selected, for example).
In general, I use Manage and Tools on the Command Bar when I want to perform a task on my local server, or a global task not specific to an individual server or group. For example, I don't want to be in the context of a Hyper-V server within Server Manager to launch Hyper-V Manager on my local machine.
But when you want to perform tasks on a specific server, the fastest way often is to right-click the server under All Servers or another group and choose the task from the list.
When managing a specific role, the Tasks drop-down in the upper right corner of each details pane provides a list of tasks that are relevant to the node selected in the navigation pane(s).
That’s it folks! We’ve come to the end of our Launch Series. We’ll have one more blog tomorrow to recap and talk about what lies ahead for upcoming posts. In the meantime, you can check out the AskCore Blog site for their launch series:
Ask the Core Team
-AskPerf blog Team
maybe you can answer this. I have a yellow bang in server manager for dhcp post install configuration. I run the wizard, enter credentials and click commit. I get an error that it failed to open a registry key. the winrm client cannot process the request.
the error occurs when trying to authorize the dhcp server and fails with error code 20070. the dhcp service could not contact the active directory.
there is no active directory, because there is no domain. it's a workgroup server. how do I fix it?
Excellent post, Blake. Thank you!
If anyone's interested in documentation about Server Manager, start right here: technet.microsoft.com/.../hh831456.aspx.
Also, Server Manager program manager Kriti Jindal has written a great blog about how to customize the Tools menu in Server Manager to display tools and scripts that you use the most: blogs.technet.com/.../customize-tools-menu-in-server-manager.aspx.
Thanks and enjoy Windows Server 2012,
Windows Manageability documentation team
Very useful info.
Is there any way to generate an email or SNMP trap based on a server group or "tile". Even a power shell trigger that could send an email if x custom group gets an error and send the error detail to the recipient?
Nice post !
Sorry for the late replies but maybe these will help someone with similar questions:
Scott, The list of servers in custom groups is located in %appdata%\Microsoft\Windows\ServerManager\ServerList.xml. There isn't a way to do what you asked within the Server Manager UI or related PowerShell cmdlets, but much of what you want to do can be done individually using Performance Counter Alerts in Data Collector Sets and Event Log Subscriptions. But I definitely see the benefit of being able to configure alerts based on your personal Server Manager configuration. (Other personalizations exist within Server Manager besides custom groups, such as performance thresholds, event thresholds, etc.). This is a good idea. I will bring it up with the appropriate teams. You might also want to go to Connect.microsoft.com to file it officially.
Gary, Authorizing the DHCP server requires AD. If it is not in a domain, then your error would make sense. There is no alternative to this in a workgroup to the best of my knowledge, so I would simply ignore that error.