Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Mastering Windows Server 2016

You're reading from   Mastering Windows Server 2016 A comprehensive and practical guide to Windows Server 2016

Arrow left icon
Product type Paperback
Published in Oct 2016
Publisher Packt
ISBN-13 9781785888908
Length 416 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Jordan Krause Jordan Krause
Author Profile Icon Jordan Krause
Jordan Krause
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Mastering Windows Server 2016
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
1. Getting Started with Windows Server 2016 FREE CHAPTER 2. Installing and Managing Windows Server 2016 3. Core Infrastructure Services 4. Certificates in Windows Server 2016 5. Networking with Windows Server 2016 6. Enabling Your Mobile Workforce 7. Hardening and Security 8. Tiny Servers 9. Redundancy in Windows Server 2016 10. Learning PowerShell 5.0 11. Application Containers and Docker 12. Virtualizing Your Datacenter with Hyper-V Index

Creating a new virtual switch


Here is an example I use often. I am running this new Hyper-V Server, which is connected physically to my corporate network and so I can spin up new VMs, connect them to my external virtual switch, and have them communicate directly to the corp network. This allows me to domain join them, and interact with them like I would any server on my network. But maybe I have the need to create some VMs that I want to be able to talk with each other, but I do not want them to be able to communicate with my production network. A good example of this scenario in the real world is when building a test lab. In fact, I am taking this exact approach for all of the servers that we have used throughout this book. My physical Hyper-V Server is on my production network, yet my entire Contoso network and all of the VMs running within it are on their own separate network, which is completely segregated from my real network. I did this by creating a new private virtual switch. Remember...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images