Book Image

Windows Server 2016 Administration Cookbook

By : Jordan Krause
Book Image

Windows Server 2016 Administration Cookbook

By: Jordan Krause

Overview of this book

<p>Windows Server 2016 is an operating system designed to run on servers. It supports enterprise-level data storage, communications, management, and applications. This book contains specially selected, detailed help on core, essential administrative tasks of Windows Server 2016.</p> <p>This book starts by helping you to navigate the interface of Windows Server 2016, and quickly shifts gears to implementing roles that are necessarily in any Microsoft-centric datacenter.</p> <p>This book will also help you leverage the web services platform built into Windows Server 2016, available to anyone who runs this latest and greatest Server operating system. Further, you will also learn to compose optimal Group Policies and monitor system performance and IP address management.</p> <p>This book will be a handy quick-reference guide for any Windows Server administrator, providing easy to read, step-by-step instructions for many common administrative tasks that will be part of any Server Administrator’s job description as they administer their Windows Server 2016 powered servers.</p> <p>The material in the book has been selected from the content of Packt's Windows Server 2016 Cookbook by Jordan Krause to provide a specific focus on key Windows Server administration tasks.</p>
Table of Contents (12 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

Evaluating system performance with Windows Performance Monitor


While good old Task Manager and the new Resource Monitor are great utilities for monitoring system performance in real time, for any more extensive monitoring needs I tend to prefer Performance Monitor. Perfmon, as it is often nicknamed, is an excellent tool that can be used for collecting specific data over a predefined period of time.

We have all had cases where a report comes across our desk that a certain server is misbehaving or running slowly. By the time we get logged in, everything looks normal. Other than Event Viewer, we don't have a whole lot of options for investigating what was happening during the time of the problem. But it might happen again, and if we plan ahead with the Performance Monitor tool, we might be able to catch the server in the act, even if we don't see the data until after the event has finished.

Getting ready

We will be monitoring a Windows Server 2016 server in our environment for this recipe. Nothing...