Building a sharepoint 2016 home lab a how to reference on simulating

Building a SharePoint 2016 Home Lab A How-To Reference on Simulating a Realistic SharePoint Testing Environment Stacy Simpkins MCT, MCSE SharePoint 2013, MCSA Server 2012, MCITP E

Building a SharePoint

2016 Home Lab

A How-To Reference on Simulating a Realistic

SharePoint Testing Environment

Stacy Simpkins

MCT, MCSE SharePoint 2013,

MCSA Server 2012,

MCITP EA SharePoint 2010

Environment

Brandon, Florida, USA

ISBN-13 (pbk): 978-1-4842-2169-3 ISBN-13 (electronic): 978-1-4842-2170-9

DOI 10.1007/978-1-4842-2170-9

Library of Congress Control Number: 2016948362

Copyright © 2016 by Stacy Simpkins

This work is subject to copyright All rights are reserved by the Publisher, whether the whole or part of the material

is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed.

Trademarked names, logos, and images may appear in this book Rather than use a trademark symbol with every occurrence of a trademarked name, logo, or image we use the names, logos, and images only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark.

Cover image designed by freepik

The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified

as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights While the advice and information in this book are believed to be true and accurate at the date of publication, neither the authors nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may

be made The publisher makes no warranty, express or implied, with respect to the material contained herein Managing Director: Welmoed Spahr

Lead Editor: Gwenan Spearing

Technical Reviewer: Fabio Claudio Ferracchiati

Editorial Board: Steve Anglin, Pramila Balan, Laura Berendson, Aaron Black, Louise Corrigan, Jonathan Gennick, Robert Hutchinson, Celestin Suresh John, Nikhil Karkal, James Markham, Susan McDermott, Matthew Moodie, Natalie Pao, Gwenan Spearing

Coordinating Editor: Melissa Maldonado

Copy Editor: Kim Burton-Weisman

Compositor: SPi Global

Indexer: SPi Global

Artist: SPi Global

Distributed to the book trade worldwide by Springer Science+Business Media New York, 233 Spring Street,

6th Floor, New York, NY 10013 Phone 1-800-SPRINGER, fax (201) 348-4505, e-mail orders-ny@springer-sbm.com

or visit www.springeronline.com Apress Media, LLC is a California LLC and the sole member (owner) is Springer

Science + Business Media Finance Inc (SSBM Finance Inc) SSBM Finance Inc is a Delaware corporation.

For information on translations, please e-mail rights@apress.com , or visit www.apress.com

Apress and friends of ED books may be purchased in bulk for academic, corporate, or promotional use eBook versions and licenses are also available for most titles For more information, reference our Special Bulk Sales–eBook Licensing web page at www.apress.com/bulk-sales

Any source code or other supplementary materials referenced by the author in this text are available to readers at www.apress.com/9781484221693 For detailed information about how to locate your book’s source code, go to www.apress.com/source-code/ Readers can also access source code at SpringerLink in the Supplementary Material section for each chapter.

Printed on acid-free paper

Contents at a Glance

About the Author xi

About the Technical Reviewer xiii

Acknowledgments xv

Introduction xvii

■ Chapter 1: Home Lab Hardware and Software 1

■ Chapter 2: Hyper-V vs VMware and Virtual Switch Creation 11

■ Chapter 3: Creating Your Domain 21

■ Chapter 4: Active Directory 97

■ Chapter 5: Domain Name System (DNS) 117

■ Chapter 6: Joining the Machines to the Domain 133

■ Chapter 7: Group Policy 151

■ Chapter 8: Certifi cate Authority 175

■ Chapter 9: SQL Server 213

■ Chapter 10: Installing and Confi guring SharePoint 257

■ Chapter 11: SharePoint Service Applications, HNSCs, and an App Catalog 333

■ Chapter 12: Installing Dev Tools 455

■ Chapter 13: Troubleshooting 465

Index 485

Contents

About the Author xi

About the Technical Reviewer xiii

Acknowledgments xv

Introduction xvii

■ Chapter 1: Home Lab Hardware and Software 1

Drinking the Kool-Aid 1

Not a Single-Server SharePoint Farm 1

Operating Systems and Software 2

System Hardware Requirements 2

But What If I Only Have 8GB of RAM? 3

But What If I Don’t Have Windows 10 Pro? 3

Software Requirements 4

Planning Your Environment 5

Not a Comprehensive Text of All Microsoft-y Things 5

What Are You Going to Call Your Domain? 8

Software Download Links 9

Further Reading: a.k.a The “Do You Want to Know More?” Section 9

Summary 10

■ Chapter 2: Hyper-V vs VMware and Virtual Switch Creation 11

Hyper-V Manager 11

Which Adapter to Choose 17

Troubleshooting a Confi guration Error 17

Do You Want to Know More? 19

Summary 20

■ Chapter 3: Creating Your Domain 21

Creating the Machines 21

Inventory Planning 21

Dorking Your Hosts File 22

Creating the VMs 24

Confi gure the Domain Controller (and Additional Servers) 33

Confi guring the Domain Controller 42

Additional Member Servers and Other Steps 76

Summary 96

■ Chapter 4: Active Directory 97

Confi guring Active Directory 97

Creating User Accounts 101

PowerShell Example 107

Thwart Those Hackers 107

Do You Want to Know More? 116

Summary 116

■ Chapter 5: Domain Name System (DNS) 117

DNS Zones 117

We Are Using “Secure Only” 117

How Does the Information Replicate? 118

Resolution and Types of DNS Records 118

Host (A) and (AAAA) 118

Canonical Name (CNAME) Alias Record 119

Pointer (PTR) Record 119

Do You Want to Know More? 131

Summary 131

■ Chapter 6: Joining the Machines to the Domain 133

The Time You’ve Been Waiting For 133

Do You Want to Know More? 150

Summary 150

■ Chapter 7: Group Policy 151

What Is a GPO? 151

GPOs in Play 151

LSD Overuse 152

How It Works and the LSDOU Again 152

Local Security Policy a.k.a secpol.msc 152

Sites 152

Domains 153

Organizational Units 153

Are Your Eyes Crossed Yet? 153

Settings 153

Default Domain Policy 153

Default Domain Controllers Policy 154

Restricted Groups Policy 154

Local Admin Rename and New Local Admin User 167

Do You Want to Know More? 173

Summary 173

■ Chapter 8: Certifi cate Authority 175

License and Registration, Please? 175

Communicate Securely 176

Do You Want to Know More? 211

Summary 211

■ Chapter 9: SQL Server 213

Do You Want to Know More? 256

Summary 256

■ Chapter 10: Installing and Confi guring SharePoint 257

Prerequisites for Installing SharePoint 257

Purpose of SharePoint 257

Using a Client Alias 257

Overview of the Install and Confi guration Process 259

Installing the Prerequisites 260

Running Setup 271

Confi gure SQL for the Install 278

Recap of the Needed Service Accounts 287

SharePoint Install and Central Administration Scripts 293

Installing SharePoint Service Applications 299

Join the Servers to the Farm Running Central Admin on SSL 307

Do You Want to Know More? 332

Summary 332

■ Chapter 11: SharePoint Service Applications, HNSCs, and an App Catalog 333

Additional Service Applications, HNSCs, and an App Catalog 333

No “Sneaky Pete” Business, SharePoint! 346

Creating a Search Service Application and a User Profi le Service Application 351

User Profi le Service Creation 356

Managed Metadata 397

Quotas 403

Additional Confi guration 404

Host-named Site Collections (HNSCs) vs PBSCs 405

Minimal Download Strategy vs Publishing Infrastructure 416

Enterprise and Standard Features 416

Search Center 416

Web Applications, Site Collections, and Quotas 434

SharePoint Store 439

Publishing Infrastructure 448

Not in Conclusion, But a Good Start 452

Like a Fly Hitting a Windshield 452

Do You Want to Know More? 452

Summary 453

■ Chapter 12: Installing Dev Tools 455

SharePoint Designer Installation 455

Visual Studio Installation 458

Do You Want to Know More? 463

Summary 463

■ Chapter 13: Troubleshooting 465

Networking 465

Issues with Networking, Joining Machines, and Connections 465

Mstsc.exe 467

Incorrect Password or Account 469

DNS Records 469

Not Joined to the Domain 471

A Weirdly Named DC 471

Mapping Drives 472

Are the Drives Filling up on Your C? 473

Getting Scripts and Distributed Cache to Run 480

Scripts 480

Distributed Cache 481

Removing Search and/or User Profi le Service Application 481

Search Service 481

User Profi le Service Application 481

Security Patches and Running psconfi g 482

Patches vs CU 482

psconfi g Changes Central Admin URL 482

Getting Hyper-V Installed 483

Summary 483

Index 485

About the Author

Stacy Simpkins is a SharePoint enthusiast and consultant He’s worked in

the food, legal, manufacturing, health insurance, and professional services industries He also has over a decade of federal government experience as

an IT specialist He’s held various roles that involved architecting and developing small, medium, and large SharePoint environments Stacy has worked on SharePoint environments at a regional component of the Social Security Administration, at the Chicago office of the Blue Cross and Blue Shield Association, at the Jackson, Michigan, office of Dawn Foods, Inc., and at an international law firm’s operations center located in Brandon, Florida He’s also worked as a solutions architect for Magenium Solutions and as a senior consultant for Sogeti LLC Holding numerous Microsoft Certifications, he regularly blogs on SharePoint and other Microsoft products Stacy loves working with customers in assisting them in the understanding of the capabilities of SharePoint He enjoys speaking at user group meetings and other technology related events

About the Technical Reviewer

Fabio Claudio Ferracchiati is a senior consultant and a senior analyst/developer using Microsoft

technologies He works for Blu Arancio ( www.bluarancio.com ) He is a Microsoft Certified Solution

Developer for NET, a Microsoft Certified Application Developer for NET, a Microsoft Certified Professional, and a prolific author and technical reviewer Over the past 10 years, he’s written articles for Italian and international magazines, and coauthored more than 10 books on a variety of computer topics

Acknowledgments

The idea for this book materialized when I was on the Apress.com web site looking for free books to give away at the Tampa Bay SharePoint user group (tbspug) It was at this moment, when I came across the wide- open, easy-to-read, authorship contract, that I recalled a statement that one of my recent clients had said,

“Dang, Stacy! You really should write a book!” And, so I did I think other people had told me that in

different ways and at various times; but I hadn’t actually thought of writing a book until I was perusing the Apress.com web site When I saw how straightforward Apress is about the process, I knew I could do it I’ve always tried to share whatever I could; so, this just seemed like the natural next step

I believe everything that happens in our lives and the knowledge that we acquire are due to a series

of events, a series of successive nows, which continue indefinitely and are interrelated With that thought

in mind, I’d like to thank all the people who’ve contributed to my SharePoint and IT related learnings and success I’m pretty sure I won’t get all of you, and some of you might even wonder why you’re on this list, saying to yourself, or maybe out loud, “But, I don’t know anything or very much at all about SharePoint,” or,

“How could I’ve possibly affected you?” Well, you contributed to my learning or success in some direct or indirect way, either as my student, my boss, my team member, or as a mentor of some sort—you helped me

So, with that being said, thank you to Samar Singh Tomar, Adam Watson, Keller, Area 4 circa 2008, Jeanne J., Kelton Harris, Pablo Lomas, Allison Anderson, Lynn McCullough, Peter Nagaro, Chuck, Edward Manuel Jr., Karen Soltis, Akbar, Anees, Faraz Munshi, Tom Takach, Hari Pasupuleti, Tom Egan, Tom

Lamantia, Trax, Beth at Magenium, Tom Simpkins, Tim Sullivan, Brad Buoy, Andrew Philipson, Leo Doyle, Leo Lovely, John Heim, Tim “Master Sergeant B” Bridgham, Virgil Aurand, Paul “Mr Heat Meiser” Caouette, John Furmanek, Dan Nicholson, Seibert, Andrew Schroeder, Ari Ammon, Len Terranova, Art Garcia, Paul Beaton and the Softball team, Ciara, Dee at Dawn foods, Hedrick, Reed Beaver, Rajai Rahaman, Fabian Hernandez, Brian Swiger MCT, Brian Caudill, Eric Perry, Jim Heuser, Patrick Cox, Stephanie Cox, Gary L Cox, Brenda at HKlaw, Daniel Payne DBA, Eric Buckley DBA, Scott B DBA at spt.local, the infrastructure guys at Holland and Knight, the infrastructure guys at Dawn Foods, and the infrastructure guys at the Blue Cross and Blue shield association, Ramesh Balakrishnan DBA, Bahareh Saati, Chadd Sommerfield, Alejandro Barragan, Kim Moore, M.C Perkins, Howard Carl, Cuy Nuegebauer, Paul Artis, Jesse Brown, Eric Chang, Eric Andino, Rob Beverly, Shane Marler, Lourdes, Tom McHugh, Chris Jurkowski, Dan Bogstad, Ben Uhlmann, Lucy Simpkins, Carter and Jordan Simpkins, Paige Simpkins, Wade Simpkins, Raymond J Simpkins II, Kristy Ukauka, Laresa Simpkins, Gloria and Tim Uhlmann, and my mother and father—Judy and Raymond J Simpkins, and anyone else that I forgot to mention

I would also like to thank my editors at Apress, Gwenan Spearing, Laura Berendson, Fabio Claudio Ferracchiati, and Melissa Maldonado, and all the other members of the team, for all their help in getting this

to press, my first book ever And, I’d like to thank you, for actually reading this acknowledgement, if you’ve purchased a copy, and even if you haven’t

And last, but definitely not least, thank you to my wife, Krista, “the best wife ever” for putting up with all the late nights and complete weekends that were absorbed by the creation of this text I love you more than I’ll ever be able to say in words or actions!

Chapter 1 : Home Lab Hardware and Software

This chapter discusses the minimum requirements for building a home lab on your PC, laptop, or server, and goes over some planning for the home lab environment

Chapter 2 : Hyper-V vs VMware and Virtual Switch

In this chapter, you learn how to create a virtual switch for your home lab and begin creating the home lab You also skim the surface of the Hyper-V vs VMware battle

Chapter 3 : Creating Your Domain

You create an Active Directory domain controller in your home-lab This way, your SharePoint will not run on top of the domain controller You’ll create the virtual machines (VMs) that operate SharePoint, or whatever you decide to run You can use this book and the home lab for more than just SharePoint

Chapter 4 : Active Directory

In this chapter, you build out and partially configure Active Directory You’ll create a few users and

organizational units

Chapter 5 : Domain Name System (DNS)

DNS is a key component to any Windows-based domain You’ll learn about host (A) records, canonical name (CNAME) records, service location (SRV) records, and more!

Chapter 6 : Joining the Machines to the Domain

This is where the machines that you created in Chapter 3 are joined into the domain that you’re creating The concepts from Active Directory and DNS start to make more sense

Chapter 7 : Group Policy

You’ll create a restricted groups policy to control members of the local administrators group on your member servers You’ll also create a group policy that renames the local administrator account on your member servers

Chapter 8 : Certificate Authority

In a production environment, it is always a best practice to run everything over a security protocol such

as Transport Layer Security (TLS) or its predecessor, Secure Sockets Layer (SSL) In an attempt to provide create a more realistic environment, you’ll create a certificate authority and issue a certificate so that you can configure SharePoint to communicate over SSL

Chapter 9 : SQL Server

This chapter covers configuring SQL Server in a home-lab setting It provides references for using more than one service account, if you wanted to go the extra distance, as you would in a production environment When you’ve completed this chapter, you’ll have a working SQL server that interfaces nicely with SharePoint

Chapter 10 : Installing and Configuring SharePoint

This chapter provides you with the instruction for getting a SharePoint 2016 farm configured using the minimum role technology You’ll have central administration running on a vanity URL and over SSL

Chapter 11 : SharePoint Service Applications, HNSCs,

and an App Catalog

You’ll configure quite a few service applications, create some host-named site collections (HNSCs), such as it.tailspintoys.com and tbspug.tailspintoys.com , and create an app catalog

Chapter 12 : Installing Dev Tools

You’ll learn about installing Visual Studio for SharePoint and the method that works best You’ll also install SharePoint Developer and connect to one of your HNSCs

Chapter 13 : Troubleshooting

Hopefully, you won’t need to use this chapter; but, if you do, it provides guidance to help with certain sticking points that sometimes occur

ShareName

So, if you wanted to map a drive to the C:\ for a server named SP2016WFE, you would open Windows Explorer, type \\SP2016WFE\C$ , and press Enter

Pinning Items to Your Start Menu

After you get an application installed, you’ll want to have some quick access to it from your Start menu and

from the taskbar To do this after you install SharePoint, you navigate to the Start menu and type SharePoint ,

as shown in Figure  1

Figure 1 Pin it to your Start menu

Once, the search results show, you can pin the SharePoint-related items to your Start menu and or to your taskbar I recommend not pinning the Post Setup Configuration Wizard to your taskbar When you’ve finished pinning the various shortcuts to your Start menu, it will resemble Figure  2

Figure 2 Start menu example

Turning Off the UAC

The User Account Control in windows provides an added layer of security that virtualizes where programs can run when they need to run administratively And, every time an admin needs to run a program administratively, she’ll get prompted to allow This is great in a production environment; but it can be annoying in a home lab

Here are the steps to turn off the UAC prompts:

1 Open a Run bar, type secpol.msc , and then click OK

2 Once the Local Security Policy editor opens, navigate to Local Policies ➤ Security

Options, and then scroll down to the User Account Control policies toward the

bottom of the screen, as shown in Figure  3

3 Switch each UAC policy from Enabled to Disabled

here as an option, and that is why it is not an exercise!

Admin Mode

After you pin the management shell and the central administration icons to the taskbar as shown in Figure  4 , you should right-click each and select Properties (see Figure  5 )

Figure 3 secpol.msc

After the Properties window opens, click the Advanced… button, as indicated in Figure  6

Figure 4 Taskbar with new shortcuts

Figure 5 Click Properties

Once the Advanced Properties window opens, select “Run as administrator” and click OK, as shown in Figure  7

Figure 6 Universal naming convention paths

Figure 7 Run as administrator

Commonly Used Shortcuts

In this book, we use keyboard shortcuts, the Run bar, and commands quite a bit Table  1 lists some of the commands that you’ll use, along with brief descriptions

Table 1 Keyboard Shortcuts and Commands Used in this Book

Windows key + R Opens the Run bar

ipconfig Opens the ipconfig information

nslookup Opens a command-line interface to DNS

Ncpa.cpl Opens the Network connections

Regedit Opens the registry editor

Control netconnections Opens the network connections

Msinfo32 Opens the system information

Sysdm.cpl Opens the system properties

Dsa.msc Opens the Active Directory users and computers

Dnsmgmt.msc Opens the Domain Name System manager

Gpmc.msc Opens the Group Policy Manager

Control Panel Opens the Control Panel

Virtmgmt.msc Opens the Hyper-V Manager

Adsiedit.msc Opens the Active Directory Service Interface editor

Summary

The goal of this book is to provide you with a more in-depth understanding of the various components of any environment that you’ll be administering SharePoint, or any application or platform It will also leave you with a fully functional farm that capitalizes on the minimum role technology You can use your home lab for anything, though In other words, it doesn’t have to be strictly for SharePoint, as you’ll see as you go through the chapters in this book Enjoy!

© Stacy Simpkins 2016

S Simpkins, Building a SharePoint 2016 Home Lab, DOI 10.1007/978-1-4842-2170-9_1

Home Lab Hardware and Software

Drinking the Kool-Aid

You’ve just picked up a book that could change your life! To benefit from the instructions provided in this text, it doesn’t matter if you’re currently working in an IT role, or if you’re an IT consultant, a new college grad, a web manager\site collection admin, a project manager\business analyst, or even a high school student There is no time like the present to start “drinking” the Microsoft “Kool-Aid”!

All that matters is that you can read and follow instructions And, more importantly, that you have a desire to learn about creating Windows-based domains, SQL servers, and SharePoint 2016 farms

After reading this book and working through its exercises, you will have acquired a basic knowledge

of building domains and creating SharePoint farms This is will give you a great launching point for any number of IT jobs, and it will hopefully spark ideas for any certification paths that you are looking to pursue You will acquire a working knowledge of how a domain comes to life and then how a SharePoint farm is grown within that environment In fact, you could even list this experience on your résumé as a SharePoint admin of whatever you domain you decide to create Just make sure to list it out as “Home Lab” somewhere

on your curriculum vitae

Not a Single-Server SharePoint Farm

You’ll create a Windows-based domain in a home lab setting , running on Hyper-V You’re going to learn the

basic steps to create a functioning domain, followed by an SQL server, and finally a four-server SharePoint

2016 farm that's running on member servers of said domain You’ll be installing SQL on an actual SQL

server—as you would in the real world— with a few home lab modifications

You won’t be installing SQL on top of a domain controller as some guides would have you do, because that is not how it is done in the real world, and quite frankly, that’s crazy talk! Remember, just because you can doesn’t mean you should

With that being said, there is absolutely no requirement that your new domain be used for SharePoint

2016 either This text is going to provide the how-to on installing SharePoint 2016; but there’s nothing stopping you from using your new domain for SharePoint 2007, 2010, or 2013

Or maybe you have something entirely different in mind, like an Exchange Server install The home lab domain would also provide a life-like place to install IIS on a member server and practice developing web applications or sites You could even run up System Center Configuration Manager The sky’s the limit—you decide!

In this home lab domain, the idea is to end up with an environment that more closely simulates what you’ll encounter in a real SharePoint (or other platform) environment, or what I like to call “A live fire” situation: a farm with a back-end server and front-end servers

Electronic supplementary material The online version of this chapter (doi: 10.1007/978-1-4842-2170-9_1 ) contains supplementary material, which is available to authorized users.

Now you could go and build a single-server SharePoint farm monster, where you spin up a domain controller, build an SQL server on that domain controller, and then install SharePoint on top of that animal; but, and it’s a very big but… you’ll never roll out code in the real world on a SharePoint Server running on top of an SQL server that runs on top of a domain controller You just won’t, so why practice that way, right?

Active Directory, group policy, network configuration, Windows domains, certificate authorities, SharePoint administration, SharePoint development, Visual Studio, and so forth This book is a great overview that gives its owner what they need to start development in a real domain It covers most of the aforementioned topics at what I like to call the “what you need to know” level, and provides information at the end of each chapter with links to further reading, in the “Do You Want to Know More?” sections So, as you’ll see, and probably already know, it would be impossible to deep dive into all of these topics in one book, unless that book was 6,000 or so pages long (I’m only guessing here; it would probably be much more than 6K)

One more thing about this book, the “Further Reading” sections are not requirements to setting up your home lab This information is provided for anyone who wants to dive a little deeper It gives you what you need to know to get your domain running in a lab setting There are many things that would be done in a production setting, with regards to Active Directory and Group Policy, for example What you and I are building here is a minimalist lab setting that allows SharePoint to run, and not run, on a domain controller

You can always take things further by rolling out more service accounts, desired state configurations, or additional group policy objects, just to name a few, after all, you’ll have the start of a great domain and a SharePoint 2016 farm!

Do you want to get started on your journey to becoming a full-fledged “Microsoft Kool-Aid drinker”? Are you unsure what I mean by that? Then please read on But do so with fair warning that this stuff is addictive, and once you drink the proverbial Kool-Aid, there is no return

Operating Systems and Software

System Hardware Requirements

In order to build your domain, you’ll need a beefy laptop, PC, or server Now, please note: you do not need a server; but you do need a powerful machine By “powerful” I mean a computer that has at least 16 or more gigabytes (GB) of random access memory (RAM) and at least an Intel Core™ i5 or higher processor You’ll also want to make sure that you have at least 500GB, or preferably one terabyte (TB), of disk space on a non- solid-state drive (SSD), and if possible, a machine that has its operating system running on SSD, or similar speed non-SSD drives Most gaming machines will suffice for this, so if you're a gamer, you might need to remove that to free up some hard drive space

Table  1-1 lists the specs for the laptop that was used in the home lab shown throughout this book

But What If I Only Have 8GB of RAM?

This might work, but everything will be slower than if you had the minimum recommended 16GB If you have

a fast processor, you will more than likely be OK; but, again, a machine similar to the one in Table  1-1 will do you just fine, especially if you have the SSD drive And it is possible to build a home lab on a machine without

a SSD drive, so don’t let that steer you away You have nothing to lose and everything to gain by reading on

But What If I Don’t Have Windows 10 Pro?

Don’t worry if you don’t have Windows 10 Pro It’s not a requirement for building your home lab; although, with everything Microsoft, it helps to run the best operating system on the planet In other words, if you can upgrade to Windows 10 Pro, then that would be best I say “don’t worry” because it is possible to build the home lab domain on a machine with Windows 7 Pro or a professional version of Windows 8 And you could build it on the Windows Server 2012 R2 operating system, if you choose

The key takeaway here is that you need the professional version of Windows

You can determine your version of Windows by looking at the version information available from the WinVer executable Let's do a really quick exercise to determine your version of Windows (see Figure  1-1 )

CHECK YOUR WINDOWS VERSION

1 Right-click the Windows icon and click Run, or press the Windows key and the

letter R simultaneously on your keyboard (Windows key + R)

2 Once on the Run bar, type winver.exe and click OK or press Enter Then you can find

the version of Windows that you have installed by referencing Figure 1-1 and looking

at the text under the copyright symbol that begins with “The Windows 10 Pro ”

This lets you know that you have the professional version

Table 1-1 Specifications for Machine Used to Create Home Lab

BIOS\Firmware Virtualization supported and enabled

Graphics card NVIDIA GeForce GTX 970M

So, build the lab on Windows 7 Pro or higher, with Windows 10 Pro the recommendation

anytime soon Use a Pro version because Pro contains the Windows Hyper-V Manager feature Downloading it and installing on a non-Pro version of Windows is not an option

Software Requirements

SharePoint 2016 needs to run on top of Windows Server 2012 R2 and SQL Server 2014 or higher; so, you’ll need to download them from Microsoft Since this domain is purely for development purposes and not for production, you can use the 180-day free trial version of the software There are links in the resources section

at the end of this chapter Table  1-2 spells out the software required for your virtual machines (VMs)

Figure 1-1 Windows 10 Pro

Table 1-2 Software Requirements

Domain controller Server 2012 R2

Certificate authority Server 2012 R2

SharePoint servers (a.k.a member servers) Server 2012 R2

SharePoint 2016

SQL Server 2014 or higher

Planning Your Environment

You are going to build out a Windows domain Your domain will have a machine called a domain controller

Don’t worry if you’re not sure what that means, you’ll learn more about it in Chapters 3 – 5 You will also have member servers These are machines that will be joined into your domain The domain controller will let

them join the domain as members That’s why they are called member servers (because when created, they

are not members of the domain; but after creation, they are joined into the domain) When you first create the member servers, they are in a workgroup You will change their names and then add them to the domain

And remember, this book provides an overview of domains, Active Directory, and so forth; unfortunately, it is not

a dictionary on Microsoft technology

Not a Comprehensive Text of All Microsoft-y Things

Chapter 2 provides a basic how-to on creating a VM that act as an enterprise certificate authority; this chapter also covers the basics on how to issue an internally signed security certificate to run SharePoint on Secure Socket Layer (SSL) Chapter 2 does not get into all the reasons behind creating subordinate certificate authorities, or turning off the root authority server, or having it on an actual physical machine that’s locked

in a closet, 500 feet below ground in a missile silo, and so forth Instead, we’ll create it, make our cert, and then we’ll just turn it off

I’ll also cover installing SQL Server, an Active Directory–integrated Domain Name System (DNS), and,

of course, SharePoint 2016 The SharePoint install is performed in what is known in the industry as a “least privileged” installation All of these platforms (SharePoint, SQL, Active Directory, etc.) run services that require service accounts

In a real-world domain, you need to rename the domain administrator account and local administrator

accounts to thwart hackers Then you create a dummy administrator account named administrator that is

actually not an admin of any kind We’ll go over this procedure in a later chapter; but for now, think of a code name for the admin account Maybe something like Zeus, Apollo, Mortimer, Ricky Bobby, or whatever you want; just not svc_admin, Administrator, and so forth

You’ll need to create the service account for SQL shown in Table  1-3 We’re not going to get into creating all the various service accounts for SQL; but instead just one account for a DBA account

a domain admin account, as you would if you were building that single-server monster that I spoke of earlier The reason that we’re not creating numerous accounts for SQL is that this is a home lab In the “Do You Want to Know More” section, there is a link to a great blog that describes the various SQL service accounts—it is a great read!

Table 1-3 SQL Server Universal Service Account

svc_SQLDBA SQL database administration and service

■ Note You can call the service accounts anything you want; but it’s best practice to precede the account

with some sort of naming convention that indicates that it is a service (svc) account If you opt to create the SharePoint home lab, you’ll need to create the SharePoint service accounts shown in Table 1-4

recommendations you can use are shown in Table 1-5 But please feel free to create your own

Table 1-4 SharePoint Service Accounts

svc_Install Installation account

svc_Farm Farm\System account

svc_svcacct SharePoint service application account

svc_content SharePoint web application content access account

svc_search SharePoint search crawler account used to access content

svc_sync SharePoint account used to synchronize user profiles with Active Directory svc_superuser SharePoint publishing infrastructure super user account

svc_superreader SharePoint publishing infrastructure super reader account

svc_unattened SharePoint unattended access account for secure store, performance point, and

Visio graphics services

Table 1-5 Virtual Machine (VM) Names

DC1AD1.yourDomainName.com Domain controller

CA.yourDomainName.com Certificate authority

SP2016APP.yourDomainName.com SharePoint application server

SP2016CACHE.yourDomainName.com SharePoint distributed cache server

SP2016SEARCH.yourDomainName.com SharePoint search server

SP2016SQL.yourDomainName.com SharePoint SQL Server

SP2016WFE.yourDomainName.com SharePoint web front-end server

Now that you’ve chosen your service account names and server names, it’s time to determine one more aspect for your servers: Their Internet Protocol (IP) addresses This is needed because the IPs will be statically assigned

Table  1-6 offers some suggestions; like the machine names, these are not set in stone

PLAN FOR MACHINE NAMES

1 In the following exercise, provide the complete FQDN for your servers and their

desired IP addresses (see Table 1-7 )

Table 1-6 VM Names and IPs

SQL Server Web front-end server

Now that you have determined the users and computers for your domain, you need to decide on the name of your domain Before we do that though, let’s talk a little bit about the concept of a fully qualified domain name

A fully qualified domain name includes all domain levels in the name of the machine, as well as its NetBIOS name (see Table  1-9 )

Based on how a FQDN is enumerated, the machine in Table  1-9 has a FQDN of SP2016APP.tailspintoys.com

What Are You Going to Call Your Domain?

Microsoft exams often use some of the following domains: Tailspintoys.com, Adatum.com, AdventureWorks com, BlueYonderAirlines.com, CohoVineyard.com, CohoWinery.com, FourthCoffee.com, Fabrikam.com, HumongousInsurance.com, NorthwindTraders.com, Proseware.com, Treyresearch.com, WingtipToys.com, Contoso.com, Reskit.com, and WideWorldImporters.com

You should use one of these or make up a fictional domain for your home lab I’ve used Tailspintoys com in the examples for this home lab

PLAN FOR SERVICE ACCOUNT NAMES

1 In the following exercise provide the desired account names for your service

accounts and remember to make the domain admin, something like “Zeus” or

“Ralph”, but whatever you do, don’t leave it unchanged (see Table 1-8 )

Table 1-9 FQDN Breakdown

SP2016APP tailspintoys com

Table 1-8 Plan Your Account Naming Conventions

Domain Administrator SQL Database Administrator Installation Account

Farm\System Account Service Application Account Web application content Account Search Crawler Account

Super User Account - Publishing Super Reader Account - Publishing User Profile Sync Account

Unattended Access Account

Software Download Links

Table  1-10 describes the software requirements

anyone who is looking to get trial copies of Exchange Server, System Center, or other products; it is not needed for building SharePoint 2016 You can download the software to your local machine now or later The software is needed before you start Chapter 3

Further Reading: a.k.a The “Do You Want to Know More?” Section

Table  1-11 provides additional information

Table 1-10 Software Requirements and Optional Software

Windows Server 2012 R2 https://www.microsoft.com/en-us/evalcenter/

evaluate-windows-server-2012-r2 SQL 2014 https://www.microsoft.com/en-us/evalcenter/

evaluate-sql-server-2014 SharePoint 2016 RTM https://www.microsoft.com/en-us/download/

details.aspx?id=51493 Microsoft software in the Evaluate Now section https://www.microsoft.com/en-us/evalcenter

Table 1-11 Not Required Reading, but Here If You Want to Dive Deeper

Create a new domain tree https://technet.microsoft.com/en-us/

library/cc782483(v=ws.10).aspx Creating a domain (old school but still applicable) https://technet.microsoft.com/en-us/

library/cc960577.aspx Managed service accounts https://technet.microsoft.com/en-us/

library/dd548356(v=ws.10).aspx Create a service account (old school but still applicable) https://technet.microsoft.com/en-us/

library/cc739458(v=ws.10).aspx SharePoint Service Accounts http://social.technet.microsoft.com/wiki/

service-accounts.aspx

Summary

This chapter described how this book is a good launching point for building a working domain, but it is not the end-all resource of all things Microsoft I noted that this domain is not production ready; but it is definitely ready for a SharePoint farm! I touched on a couple of ideas related to the domain controller and member servers, learned about the software and hardware requirements for the host system (laptop, PC, or server), and also covered some basic planning steps that are needed for building out the domain We created

an inventory plan and a user account plan Finally, we decided on when to download the software needed for the domain and we came up with a domain name

In Chapter 2 , I’ll talk briefly about the differences between Hyper-V and VMware, and then begin discussing how to configure the virtual network switch that will become our medium between the home lab and the rest of the network, including the Internet In Chapter 3 , we’ll start building the VMs that comprise the home lab domain

© Stacy Simpkins 2016

S Simpkins, Building a SharePoint 2016 Home Lab, DOI 10.1007/978-1-4842-2170-9_2

Hyper-V vs VMware and Virtual

Switch Creation

In Chapter 1 , you created a plan for your virtual home lab environment You determined your domain name and mapped out names for the service accounts and the virtual machines (VMs) Now it’s time to start building the environment

I’m not going to spend time comparing Hyper-V to VMware from a platform perspective; but I will say this: Hyper-V has matured and it is enterprise ready and it is a worthy foe of VMware

Drinking the Microsoft Kool-Aid, time and time again, I’m showing you how to create your lab using Hyper-V Now you can create the domain in VMware if you want And if you have access to VMware, then by all means please feel free to utilize it This book does not provide instruction on provisioning the VM with VMware, though

The bulk of these instructions work with VMware, short of the actual creation of the VM Everything after VM creation applies to VMware the same as it does to Hyper-V, in regards to Windows servers,

SharePoint, and SQL Server

VMware comparison” and you will find a plethora of information

Your Hyper-V network can run across a wireless or wired connection Your host computer is the laptop,

PC, or server that you are running Hyper-V Manager on You’ll need to install Hyper-V Manager on your host computer, and then you’ll need to open it and create a virtual switch

Hyper-V Manager

Hyper-V Manager is Microsoft’s answer to VMware vSphere center You can access Hyper-V Manager after

it is installed by navigating to Windows ➤ Start menu ➤ Programs ➤ Windows Administrative Tools ➤ Hyper-V Manager Or, you could open a Run bar by pressing the Windows key and the letter R, and then

input virtmgmt.msc and click OK Let’s take a few minutes and install Hyper-V Manager in your Windows

Professional operating system in the next exercise

INSTALL HYPER-V MANAGER

1 Right-click your Windows Start icon

2 Click Control Panel

3 Click Programs

4 Click “Turn Windows features on or off”

5 Check the box for Hyper-V (at first it is not checked, as shown in Figure 2-1 ; make sure that it looks like Figure 2-2 ) Click OK

Figure 2-1 Hyper-V Manager not enabled

Figure 2-2 Hyper-V Manager enabled

enabled for virtualization You will more than likely receive an error when you attempt to configure the virtual switch, as well Please see Chapter 13 to learn how to get through this obstacle

If your computer wants to restart, go ahead and restart it

Now that Hyper-V Manager is installed, let’s configure the virtual switch

VIRTUAL SWITCH CREATION

1 Open Hyper-V Manager

2 Click Virtual Switch Manager (see Figure 2-3 )

Figure 2-3 Virtual Switch Manager

3 Make sure External is selected under “What type of virtual switch do you want to create?” Then, click Create Virtual Switch (see Figure 2-4 )

Figure 2-4 External switches let you contact the Internet

4 Give your switch a name, make sure that you have the correct network adapter

selected, and then click Apply (see Figure 2-5 )

Figure 2-5 Creating a virtual switch on a USB adapter