Wireless networks get complex when the use case includes roaming, high densities, multiple SSID's, VLANs, or interference.

In this case, the client needed to provide a more reliable wireless network to church attendees, volunteers and employees.

Issue: Wireless users where getting dropped due to access point congestion (SonicPoint Access Points).

After an onsite wireless assessment, we spec'd the model and location of the new access points, and ordered hardware (Ruckus wireless Access Points and Controller in this case).

While waiting for hardware, we assisted the client in tested the existing Internet connection (50mbps) and configured the firewall with an additional isolated network.

After deploying the new solution, there are no dropped connections or lag, and the public/private networks are separated.

At App Gap, we do a lot of virtualization. That includes P2V (physical 2 virtual), V2V (virtual to virtual), tuning, replication, backup, etc...you get the picture.

It isn't unusual to P2V six servers onto 1 physical Hyper-V server.

But Containers!! Well, "Containers" are THE next evolution of virtualization. Containers will allow for EVEN MORE efficient use of hardware! Think dozens of Containers (virtual machines) on 1 physical server!

So what does that mean for my Windows Server environment? Well... guess what! Container support is built into Windows Server 2016!

Microsoft has a great 5 minute read on Containers, here:

https://msdn.microsoft.com/en-us/virtualization/windowscontainers/about/about_overview

Then, take another minute, and at least check out the picture on this page, and read the paragraph above it, to get a quick understanding:

https://azure.microsoft.com/en-us/blog/containers-docker-windows-and-trends/

And for you hard core types, 'Docker' is what started it all:

https://www.docker.com/whatisdocker

Wireless network for 500 simultaneous users, wireless roaming, with multiple SSIDs

It's here! It's here! Server 2016 and Containers!