Say hello to what will very likely be the Server Manager replacement in Windows Server 2019: Windows Admin Center (WAC). Formerly Project Honolulu, WAC has officially gone GA with build 1804. Microsoft clearly has big plans for this tool which has the potential to replace everything and anything currently based on the well aged Microsoft Management Console (MMC). It will probably be the release that follows Server 2019 before we see any possible real deprecation of MMC.

Installation

Because WAC is a web service that manages individual servers, it must be installed on every node you intend to manage, for Server 2016/ 2012R2. Installation is a pain-free affair requiring only permission to modify a particular server’s trusted hosts settings, a designated web port for management and either a 60-day self-signed or other generated SSL cert.

If managing a cluster or larger environment, whichever node you intend to use as a gateway for management access must have visibility to all other nodes in the cluster or environment. Here I’m using S2D1 as my gateway and have manually added all relevant hosts and cluster objects. You can optionally use any Server 2016 or Win10 PC as a gateway to provide management access to all other servers in your environment. From what I can tell, the only thing that truly designates a node as a “gateway” is by adding other objects to it, per below.

The designated gateway itself can then authenticate assigned users or administrators based on local or Azure AD.

Upon installation, WAC will enable a few additional solutions depending on the features installed on your server. For my scenario WAC provided 4 distinct management panes: Server Manager, Computer Mgmt, Failover Cluster Manager and a brand new Hyper-Converged Cluster Manager.

Additional modules and configuration pages will be installable as extensions within WAC. All of the configuration pages in the sections that follow are essentially extensions so the extensibility of this tool is really only limited by the extensions available. Read: this tool has been designed for big things!

Computer Management

A notable change possibly coming here is that Computer Management will be for Win10 PCs only at some point. Right now you can use Server or Computer Management on servers, as neither tool is capable of completely replacing the other. “Computer” in this context will soon mean “PC”.

Server Manager

This is where the majority of new functionality exists currently. To a large extent, this is a combination of the legacy Server Manager tool with a few of the MMC-based tools and a nice coat of webby modern polish. Not all functionality is present here and for many things you will still need to access the MMC tool counterpart. A lot the items available are self explanatory but I’ll showcase a few of the interesting additions below.

Real-time system performance charts are visible on the Overview page with an option to enable disk metrics separately. The warning that follows suggests that these metrics consume a great deal of overhead so to only use when you must and then disable when you are finished. Notice that only my C drive is visible here, no Cluster Shared Volumes in use by S2D running on this same host. This appears to be a Server 2019 feature only.

Some areas are surprisingly good with new concise takes on existing models, such as the Firewall configuration. I can very simply see all incoming/ outgoing rules and easily create a new rule without having to use a series of wizard-driven questionnaires or multi-tab MMC dialogs. This is a fantastic example of what this tool should endeavor to change in future versions of Windows. If more granular manipulation is required, the settings dialog of any rule can be accessed to change things further.

A largely-functional network management stack is a welcomed addition here, no longer requiring ncpa.cpl to alter IP or DNS settings.

Another nice addition here is a fully functional and integrated Shell window. I can do whatever I need to within PowerShell right from WAC.

The registry editor makes an appearance here, no longer requiring regedit.exe to make any needed changes.

The Remote Desktop page provides an embedded frame for direct RDP connection to the server you are connected to. No need to launch a separate RDP client.

The Updates page in WAC appears to be a bit better than the Windows Update tool in the newer Settings UI. Windows Update says I only need a SQL SP2 update:

WAC shows me this same SQL update but a slew of others too, including Intel hardware driver updates. Awesome!

Hyper-V can be managed from WAC as well providing useful event and resource usage data including the ability to manipulate the VMs directly. One thing I don’t like about the current toolset is that when attempting to connect to a VM I am greeted with a popup to save a .rdp file, no direct/ protocol-less console. Hopefully this will get better.

Virtual Machine Inventory shows a summary view of all VMs on this particular host along with real-time resource utilization and clustered status. Important to note that VMs running as clustered on other nodes are not shown here.

The new VM dialog is simple and consolidated enabling quick deployment via minimal hoop jumping.

The full VM settings dialog is also available here for granular settings changes. This may actually be good enough to almost completely deprecate Hyper-V Manager for day-to-day use. Awesome!

Hyper-Converged Cluster Manager

To fully manage S2D clusters with Admin Center you need to be running a preview build of Server 2019, which I don’t have yet. Even though the error dialog below says an April patch is required for Server 2016, per this article, that’s not accurate. This gives a sense of the things the UI will let you do here however. It’s unclear if Admin Center will facilitate S2D setup or not, or if PowerShell will still be required for this in Server 2019.

Failover Cluster Manager

While Hyper-Converged Cluster Manager does not work for Server 2016, Failover Cluster Manager does, to some extent. If you have a S2D cluster some of this will not work, namely the details section on the Disks page. Anything touching S2D directly will likely fail and as a result may require a restart of the WAC service if the UI becomes unresponsive.

The dashboard page shows general status of the clustered components including options to start, stop, remove and simulate failures.

Many of the page tabs are fairly basic at the moment, so WAC doesn’t yet replace any MMC counterpart for full functionality.

Similar to the Virtual Machine page in the new Server Manager, the dialog here should be familiar although now we see which host server is running a particular VM in a clustered state. There is still this split brain problem in Hyper-V clusters where VMs are ‘optionally’ clustered or left local if you want. If you are running a cluster your VMs should be part of the cluster, storage resiliency is only possible if the VM lives on clustered storage. In the split brain model I now have 2 classifications of VMs, clustered or not and still require 2 distinct tools to manage each: Failover Cluster Manager for clustered VMs, Server Manager for non clustered VMs. I doubt this will change any time soon.

Other Items of Note

No love for IE. I got this somewhat hilarious error suggesting that I install Chrome or Edge to use Admin Center on the server itself, considering Server 2016 ships with IE only by default. Most will manage remotely but it would sure be nice to be able to do SOMETHING locally if I needed to without having to install another browser! Just another nail in the coffin. RIP IE.

The need to re-authenticate is definitely excessive, over and over and over again. Every piece part that you connect to, even sub-elements on particular pages sometimes prompted additional challenges for authentication. Even after entering explicitly defined admin credentials for “all connections” I was still prompted continuously to authenticate. In a large environment I would be tearing my hair out. This must be resolved!

Watch this space, managing Windows Server is about to change in a big way!

HTPC build for Plex three part series:

1. Hardware build and Storage Spaces
2. Plex server and clients
3. Performance

I’ve had a single disk Home Theater PC (HTPC) running Plex for a while now but with my ReadyNas nearing the end of its useful life, I decided to kill two birds with one stone: build an updated HTPC with drive redundancy to also take over the functions of my aging NAS. My HTPC stays on 24/7 anyway so this makes perfect sense. My design goals for this were to build a small, quiet, low power, data redundant and sufficiently performing box that I can stuff into my TV cabinet. The extent of the duties for this HTPC will be video streaming and file sharing/ backup, no gaming. This series details my build, Plex server, Plex clients, Windows Storage Spaces, as well as the performance of the storage subsystem.

Performance

In these performance tests I want to focus on the main activities my HTPC will be undertaking: file read/ write operations and streaming. I tested using both Parity and Mirror Spaces to demonstrate the capabilities of each.

WD Red Baseline (Control)

First to set a baseline for WD Red 3TB HDD, here is the observed write performance with a single 40GB file write operation (from C:\ to Z:\). The copy took around 4.5 minutes and the drive topped out around 145 IOPS. Subsequent read performance tests top out around the same level. Considering these disks have been reported to spin at 5400 RPMs, frankly that’s really not too bad.

Windows reported ~142MB/s transfer speed:

These drives produce absolutely ZERO audible noise. No clicking, no head seeking noise, no rotational noise…nothing. With the cover off of this box, all that is audible is the 3 spinning fans (case, CPU, PSU). Under the TV cabinet, my build is dead silent.

File copy between Mirror and Parity Space

Test constants:

C:\ = SSD
N:\ = Mirror space
M:\ = Parity space

This test demonstrates the performance capabilities of a Parity Space using the WD Red disks. Disk performance copying multiple files from a mirror space (N:\) to a parity space (M:\) was fairly poor, averaging 33 write IOPS on the parity space. Observed read performance on the source 2-way mirror space was low at 25 IOPS on average, but that’s all it was being asked to do. This is somewhat expected however, as one of the caveats with parity resiliency is reduced write performance.

Once again, the Windows file copy dialog tracks very closely to the observed maximum write performance in Perfmon.

Power consumption of the system under test varied between 50 to 75 watts. Very good!!

Write performance of Mirror and Parity Spaces:

Test constants:

C:\ = SSD
D:\ = Mirror space
M:\ = Parity space

Here you can clearly see the write performance disparity between a two-way mirror and parity space. Copying a 4.5GB file from SSD (with very high read performance) to my two-way mirror space yielded very reasonable write performance according to the Windows file copy dialog. The overhead of the mirror operation appears to be costing around 20 IOPS.

The write activity of the physical disks participating in the mirror.

That same 4.5GB file written from SSD to my parity space (M:\) yielded significantly lower results (almost 3.5x lower):

Here is a more detailed view of the write performance against the parity space:

Read performance of Mirror and Parity Spaces:

Test constants:

C:\ = SSD
D:\ = Mirror space
M:\ = Parity space

Copying the same 4.5GB file from each space back to the SSD yielded better results overall. The read performance of the parity space during this operation is better but still below what the mirror space or even native drive are capable of:

Copying the file from the mirror space to the SSD was higher performing than the parity space and on par with native disk read performance, but the gap isn’t as wide here.

Plex Streaming Performance: Single File

Test constants:

-Physical disk 1 and 2 comprise a mirror Space
-Plex clients in use: Roku
-Media in use: single file, highly compatible, 1080p

Streaming being a highly sequential mostly read operation, there isn’t a great tax put upon the system resources. Multiple streams and transcoding complicate this a bit. The following chart shows the performance of a single video stream from my HTPC using a mirror Space to my Roku client. Interesting to note that the C:\ drive is busier than both disks in the mirror space, but all reads are sourced from a single disk.

Plex Streaming Performance: Single File, skipping around

Test constants:

-Physical disk 1, 2 and 3 comprise a mirror Space
-Plex clients in use: Chromecast
-Media in use: single file, highly compatible, 720p

Trying to force spaces to utilize all disks within a vDisk, I manually skipped around four times within a sample media file. Here you can see that with every color change within the performance chart is where I jumped to a different time within the media file. Almost every time I did this, Spaces offered up a different disk to be read from. The one exception is during the period between 7:40 and 7:43 where I performed a jump but the same disk was used. Otherwise, all three disks in  my mirror Space were used to read the file.

Plex Streaming Performance: Multiple Streams from One File

Test constants:

-Physical disk 1 and 2 comprise a mirror Space
-Plex clients in use: Roku, Chromecast, PS3 (DLNA)
-Media in use: single file, highly compatible, 1080p

To satisfy my curiosity, regardless of how infrequently this situation might actually occur, I wanted to see what the impacts were if I kicked off multiple streams of the the same file. I chose a mostly compatible file so we get the benefits of Direct Play here. Three simultaneous streams requiring transcoding would probably not work so well. There is a CPU spike when the third stream is launched and minor spikes on disk 2 for each stream event. You’ll note here that all reads are coming from disk 2. Looking at each TV screen individually and subjectively, the playback was completely normal.

Plex Streaming Performance: Multiple Streams from One File, 3 Disk Mirror

Test constants:

-Physical disk 1, 2 and 3 comprise a mirror Space
-Plex clients in use: Roku, Chromecast, PS3 (DLNA)
-Media in use: single file, highly compatible, 1080p

Just to see if there is any impact to performance, I ran this same test again but with three physical disks in my mirror Space. I would have expected my reads to be coming from at least two disks but as evident here, disk 1 is doing almost all of the work. Interesting to note that overall spikes are much lower now with read performance hovering around 1 IOPS. The takeaway here is that this third disk in my two-way mirror Space doesn’t add much from a performance perspective.

Plex Streaming Performance: Multiple Streams from Multiple Files

Test constants:

The following chart shows the effects when additional streams are added using three different media files, one requiring transcoding. You can see that system resource usage is relatively low with the first two streams, things change dramatically with the introduction of the third file. Transcoding means heavy CPU usage as evident here. Disk activity with 3 different files being accessed simultaneously jumps up quite a bit too. 

Zooming in here looking at the disk IO, you can see once again that almost all read requests are satisfied from a single disk. Hmm, where’s my striping performance??!

Here is the Plex transcoder in action:

Network Performance

Network performance of the Plex server with a single HD media stream is very reasonable. There are spikes north of 11Mbps but for most of the duration the  transmitting bandwidth stayed around 2Mbps.

Conclusions:

• The WD Red HDDs are a very quiet, very low power option that yield decent disk performance. Performance is more than acceptable for an HTPC that doubles as a NAS.
• Two-way mirror Spaces are the highest performing option in Storage Spaces but come with the highest disk cost as well (2x). Read performance is on par to that of a native disk with Spaces adding no discernable overhead, writes cost ~20 IOPS in overhead. If you have HDD capacity to spare, this is the resiliency option you want!
  • While writes clearly hit all disks in a mirror Space, observed read operations from streams are satisfied from a single disk in the Spaces pool. Jumping around within a media file does force reads from all disks in a Space.
  • 3 disks in a Storage Space really doesn’t buy you much other than additional capacity. With a 1-column two-way mirror you still only have two copies of data, on two physical disks. Read and write performance is not increased here.
• Parity spaces will work fine for Plex and video streaming in general, as video streaming is sequential and read performance is acceptable. Parity spaces suffer massively in reduced write performance so copying files to or moving files around on your HTPC will be much slower. The trade off for poorer write performance in a parity space is more overall usable capacity (1.5x consumed in a parity space vs 2x in a mirror space).
• Plex makes excellent use of system resources and can handle just about anything you can throw at it. The Plex server doesn’t even break a sweat with highly compatible media types, even with multiple streams. Transcoding is CPU intensive and should work fine for a single stream, multiple streams may tax your system and degrade the viewing experience.

This post originated at Exit | the | Fast | Lane – weestro.blogspot.com

HTPC build for Plex three part series:

1. Hardware build and Storage Spaces
2. Plex server and clients (You are Here)
3. Performance

I’ve had a single disk Home Theater PC (HTPC) running Plex for a while now but with my ReadyNas nearing the end of its useful life, I decided to kill two birds with one stone: build an updated HTPC with drive redundancy to also take over the functions of my aging NAS. My HTPC stays on 24/7 anyway so this makes perfect sense. My design goals for this were to build a small, quiet, low power, data redundant and sufficiently performing box that I can stuff into my TV cabinet. The extent of the duties for this HTPC will be video streaming and file sharing/ backup, no gaming. This series details my build, Plex server, Plex clients, Windows Storage Spaces, as well as the performance of the storage subsystem.

Plex

So what is Plex and why do we need it? Plex is a very simple, very powerful media center server that can stream videos, music and photos to almost any device…most importantly TVs. Plex can be installed on many NAS devices as well as Windows/Mac/Linux based PCs. Without Plex, DLNA is available to watch supported content from network accessible locations and works fairly well most of the time, but this is simply a list of content. Plex can also talk DLNA but the media server greatly enhances the overall experience by providing art, posters, synopsis, which media has been watched/ which hasn’t, the ability to resume where you left off, remote streaming and transcoding. Plex also supports many file containers (AVI, MKV, MP4, etc), codecs and subtitles. I personally used the DLNA method for years before seeing the light on Plex and no way would I go back. I love Plex and you will too!!

First, create an account on http://plex.tv, you’ll need this later for remote access and it will make management much simpler. Setup is simple: install the Plex media server on the supported platform of your choosing, open the Plex console in a web browser and point Plex at the locations of your media by adding libraries. Media is best categorized by type which will make browsing, searching and updating content much easier. Plex makes this process very easy for you:

I use the following categories and will add one for photos soon:

Plex will then automatically connect to a variety of online sources, such as Freebase or The Movie Database, to download media information and art.  Once complete all of you media will be organized and accessible in the Plex console with full posters and even background music, if you want it.

Plex content can be browsed via normal folder structures if you like or you can use the Plex Dashboard where you will find “On Deck” and “Recently Added”. The latter should be self explanatory, On Deck is where you will find movies that you started and stopped or the next episode of a TV show in a series. This is Plex helping to keep your place in your media universe and it is incredibly useful. 

Plex provides three primary methods for playing content: Direct Play, Direct Stream and Transcoding. Bottom line is that Plex will play your media one way or another, you don’t have to worry about it, but this is how it does it.

• Direct Play is the best and exists in the ideal scenario. 100% file compatibility with very little resources consumed on the media server itself. The file is sent to the Plex client as-is, easy breezy.
• Direct Stream is used when a media file is mostly compatible but some element within is not and requires transcoding. The example Plex uses is a media file where compatible audio/video codecs are streamed direct and the non-compatible container is transcoded.
• Transcoding is used when either the audio or video format isn’t compatible and has to be converted into a compatible format. Audio transcoding is not very CPU intensive but video transcoding is.

Recommended Tweaks

Overall, you could change almost nothing post install and Plex will work fine right out of the box. Here are a few tweaks that I recommend to enhance your experience.

In the server settings, click Connect on the left, make sure to log into Plex (your online account) as this will allow you to connect to and stream media to any device anywhere you are. This is honestly one of the coolest features of Plex and you do not need a Plex Pass to do this! Once signed in on your server, you can now connect to your Plex environment from any smart phone, tablet or PC anywhere you have internet connectivity by using the IOS/ Android Plex app or by logging into Plex.tv. Traveling? As long as you have internet connectivity, you can browse and watch anything from your library. No USB thumb drives required!

To maximize ease of use when you add content, make sure the following settings are enabled. This will ensure that Plex will automatically scan your library when files are added vs having to run a manual or timed scan. Plex will see that you’ve added a file and will automatically add it to the library for playback and download related art.

Under the Web settings, click Player on the left, you can control the streaming quality based on where you will be streaming to. 1080p for local streaming and a lower setting for remote streaming, for example. I have found that setting the local quality to 4Mbps/ 720p greatly increases local streaming responsiveness and makes it easier to skip around in a given media file.

Further customization at this point is highly preferential and you’ll figure it out by clicking through the available options. Plex has made this all VERY easy. In Windows, Plex runs as a process launched by an interactive user so does require that a user account is logged into the desktop. There is no Windows service offering yet but there are ways to work around this. I have an account set to login automatically after a reboot then the screen locks after 1 minute for security. In lieu of a Windows service starting with the OS, this works fine.

Plex Clients

With the HTPC built and Plex installed, let’s talk about client connectivity. There are a number of ways to go here which is another benefit of Plex: extreme flexibility. The methods below are my top 3 in order by preference.

Smart TV app

If you own an internet connected Samsung Smart TV then you already have access to the best free Plex client available. Nothing is required externally, just install the Plex app from the Samsung app store on your TV, launch and it should find your Plex server on the network. Your TV remote will navigate the Plex menus and this will provide the richest experience you can get while navigating Plex on your TV screen. Sadly, if you own a Panasonic TV you will have to use an external client. There is no and will be no native Plex app in the foreseeable future.

Google Chromecast

Chromecast is a very simple and very cheap option that I personally use on my Panasonic plasma. $35 gets you an HDMI-connected dongle that simply casts or displays content on your TV via wifi. This is an important distinction to make when considering the Chromecast. There are no on-screen menus to navigate and there is no integration with your all-in-one remote. Your PC, tablet, or phone is your remote and where you select the content you want to display on your TV. This does require that you purchase the Plex app for IOS/ Android ($5) or if you choose to pay for PlexPass, you’ll get the app for free. Chromecast for Plex works great, the downside is the other services currently supported are a bit limited compared to Roku and the like (if you care). Chromecast is powered via a USB port on your TV or from a wall adapter.

Chromecast setup is very simple and pretty neat in what they do. Initially the Chromecast turns itself into a wifi Access Point (AP) by broadcasting a SSID that you connect to for configuration using the Chromecast app on your device. Once the local wifi network SSID and password are selected, Chromecast will disable its own AP and connect to yours.

Once Chromecast is configured, launch the Plex app on the device of your choosing and navigate to the content you want to watch. Connect Plex to the Chromecast by pushing the “Cast” button in the top right corner and select the Chromecast, this will also automatically change the input on your TV to the correct HDMI slot. Press play on the chosen content. This method is definitely different than the more traditional on-screen navigation approach but having used it for going on a year now, I really like the experience this solution provides. Your more technically challenged family members may not like or fully understand this method without some training.

Roku Streamstick

Roku is a favorite of many home theater aficionados and provides several client options with varying price points. The Roku Streamstick is the Roku answer to the minimalist HDMI dongle but with the majority of the value that Roku provides. I use this client on my older Samsung plasma that doesn’t have built-in wifi support. Roku Streamstick is powered via a USB port on your TV or from a wall adapter. Setup is simple and handled via the specialized Roku remote included. Connect Roku to your home wifi and you are good to go.

Roku uses the more traditional on-screen navigation approach and has an impressive catalog of connectable services you can use. One of the neat things Roku provides is an impressive search function that gives you multiple options as to where you can find/ buy/ play the content you’re looking for. Roku works using a concept of “channels” which are really apps that you add to your client. Plex, Netflix, Amazon, etc. Plex is one of those channels and costs $5 just like the IOS/ Android version. PlexPass members get this app for free as well. Unlike the Smart TV or Chromecast methods, Plex on Roku is a very minimalist affair that provides a very basic visual experience.

While Roku does ultimately provide the essentials for Plex, it is my least preferred method and comes with the following caveats:

• Separate non-IR Roku remote required to control on-screen navigation. No integration into traditional IR all-in-one remotes possible.
• Very slow boot up compared to Chromecast and takes a very long time to get to a point you can actually use it.
• $50 vs $35 for the Chromecast
• Least rich experience of the 3 options with a very basic user interface.

Please also see part one of this series which details the hardware build and part three which discusses performance.

References:

https://plex.tv/

Converting ISO, Video_TS and other disk image formats