Monthly Archives: October 2016

Why Virtualize?

Tech Administration

<![CDATA[There are a lot of reasons to consider virtualizing your servers.  Here is a short list.

  1. A virtualized server is easier to backup.
    • You can export, snapshort, image, or use a vendor provided backup option.
  2. A virtualized server is easier to move to new hardware when needed.
    • Easier hardware upgrades!
    • Backup and restore to the new machine with increased capability.
    • Add virtual drives, NICs, on the fly and they just appear on the server.
  3. You can separate server roles so that if you are upgrading a single role, only one server is affected.
    • I can’t oversell separating roles!  If you have an AD, DNS, DHCP, File Server, Print server…you need to separate some things!  While AD, DNS, DHCP may go together, print and file servers do not, they belong on their own servers.
  4. You maximize your computing resources.
    • You can afford a better machine if it is running 5 VMs on it, and when it needs power, it is there.  Sharing 8 cores and 32Gb of RAM is cheap and runs 4 VMs easy.
  5. It is more energy efficient (Go Green!)
    • One PSU running those 4 VMs is 1/4 the power, enough said.
  6. You can extend the life of old applications.  If you have a piece of software that only works on an old OS, you can move that machine to a VM and have it rock on the new hardware.  I hate keeping 2003 around, but the software only works on that OS, so we stripped everything else off of the server, virtualized, and can keep it running until the new software comes out.
  7. Fast deployment.
    • When I was asked if we could make a 2012R2 system for the new video surveillance system in a meeting I had the new server up before the meeting was over.  (I have a 2012R2, 208R2, 2016 Sysprep and can make a server in 6 minutes)
    • Did that impress my administrative team and the vendor?  You bet.  Be a IT superhero!  🙂
    • I have a separate VM with no active machines on it for these fast requests and immediate needs.  I move them later to the “right” place.
  8. It is FREE!  While there are obviously versions that do cost.  VMWare ESXi is free and HyperV comes with your copy of Windows Server.

Our current VMWare servers are 20 core i7s with128Gb of DDR4 RAM.  We use a 2Tb M2 SSD as well as additional 2Tb 850 Pros as needed.  The server can maintain 10+ servers without seeming to be running more than 1.  The cost per server are around 4000.  We reuse the server cases but include new gold rated PSUs with a new build.]]>

Windows Server 2016 RDS Client Server

IT Support, Staff Tech Reviews

<![CDATA[Windows Server 2016 : Remote Desktop Services
This guide will walk you through how to setup Remote Desktop Session Host on Server 2016.  Our application of this role is to provide a central connection server for thin client users.  There are two parts of this guide, the licensing server and connection server.  This guide covers the connection server, and assumes you have already setup a licensing server named “TRAIL5”.

Connection Server
After creating a new Windows Server 2016 server, open the server dashboard and add “Remote Desktop Services”. (figure 1-1)

figure 1-1
figure 1-1

Continue through the wizard by clicking next, without adding features.  The next screen will display role services for remote desktop services.  Add “Remote Desktop Gateway” and “Remote Desktop Session Host” and then finish the wizard. (figure 1-2)
figure 1-2
figure 1-2

After Installation completes, restart the server as required.  Once restart has completed, create a group policy to define the licensing information.  This can be achieved on the local machine by running “gpedit.msc” or by creating a group policy object applied to the container in which this server resides.  Local policy can be applied at the following path: Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing.  This is where you set the licensing server and type. (figure 1-3)
figure 1-3
figure 1-3

A policy that is applied through group policy rather than locally would be below. (figure 1-4)
figure 1-4
figure 1-4

Once this policy is applied, you may restart the server.  After a restart, it will be fully licensed and ready to use.

This guide was to setup the client access server portion of a remote desktop environment.  To setup the licensing server to process CAL’s, please see this post.]]>