Building a Hyper-V Environment for SharePoint Prototype – Part 2

In the previous post in this series, I created the Hyper-V VM environment (running Windows Server 2012 R2) I’ll be using to build SharePoint Server 2016 on. The next step is to install either SQL Server 2014 or SQL Server 2016 for the database server requirements. Because I’m a geeky sort of guy and have to be on the bleeding edge, I’m going to use SQL Server 2016 with SP1, which is available from Microsoft for a 180 day evaluation period. Depending on when you are doing similar installations, the version that’s available may vary so remember to always check what the supported configurations are. We also need to install Active Directory so there are two parts to this post.

Installing SQL Server 2016 with SP1

The Microsoft link I just provided at this stage downloads a 3 Mb file, which of course is not the working SQL Server download. All that does is allow you to fire up a screen that allows you to select either a basic or custom installation, or to download the real media:

Click on the “Download Media” link and save the ISO file somewhere locally. The file is about 2.5 Gb in size so it will take some time to download, depending on the speed of your Internet connection. Next, start the VM you’re going to use if it isn’t still started, and mount the SQL Server ISO file to it by following the menu path “Media”, “DVD Drive”, “Insert Disk” (you may need to eject the Windows Server 2012 R2 ISO if it’s still loaded). Select the ISO file and click “Open”:

Next, open File Explorer on the VM, and double-click the DVD drive:

After a few seconds (depending on the speed of your VM), the “SQL Server Installation Center” opens. If you want, explore the various options it provides or just click “Installation” on the top left under “Planning”:

Click “New SQL Server stand-alone installation or add features to an existing installation”:

If you have a product key that can be applied, enter it here or choose either “Evaluation” or “Developer” from the free edition dropdown (NOTE: SQL Server Express is NOT supported so do not choose that option) and click “Next”:

Select the checkbox next to “I accept the license terms” and click “Next”:

If you want, select the checkbox to “Use Microsoft Update” then click “Next”:

You may get a warning for Windows Firewall. Ignore that and click “Next”:

On the “Feature Selection” screen, select “Database Engine Services” and click “Next”:

On the “Instance Configuration” screen, leave the selection on “Default instance” and click “Next”:

On the “Server Configuration” screen, just click “Next”:

On the “Database Engine Configuration” screen, I selected “Add Current User” but left the rest at their defaults and clicked “Next”:

On the next screen, review the options you have selected and click “Install” if you are happy to proceed with the installation:

When the installation completes, you’ll get a message saying you need to restart your computer after the setup process is completed:

Click on “Close” to complete the installation. Back on the “SQL Server Installation Center” page, there is one more thing you need to do. Click on “Install SQL Server Management Tools”:

When IE gets to the “Download SQL Server Management Studio” page, download the latest current release for Production use (at the time of writing this post, that is version 16.5.3):

Open the folder where you saved the download to and double-click the “SSMS-Setup-ENU.exe” file. On the Security Warning page, click “Run”:

Click the “Install” button:

Now go away and get coffee, because the installation will take a while! 🙂 When it finally completes, you will need to restart the VM so click the “Restart” button”:

Installing Active Directory

Strictly speaking, it isn’t necessary to install Active Directory Domain Services as you can use a connection to your company’s AD. However, given we are building a standalone VM environment here, it’s easier to have everything installed in one configuration. To install Windows Server 2012 R2 Active Directory Domain Services, start Server Manager (if it is not already started) and select “2. Add roles and features” from the middle of the screen or select “Add Roles and Features” from the “Manage” menu on the top right:

On the “Before you begin” screen, just click “Next”:

“Role-based or feature-based installation” should be selected by default. If it not, click the radio button to select it, then click “Next”:

There will only be one server in the server pool, so again click “Next”:

Select the “Active Directory Domain Services” checkbox and a pop-up will appear. Just click on “Add Features”:

Click “Next”:

Click on “Next” again:

Finally click on “Install”:

NOTE: Do not close the installation dialog window, but instead click the link “Promote this server to a domain controller”:

On the “Deployment Configuration” screen, select the “Add a new forest” radio button, provide a root domain name and click “Next”:

On the “Domain Controller Options” screen, leave the options at their default and enter a DSRM password (twice):

Ignore the delegation warning and click “Next”:

Verify or change the NetBIOS domain name and click “Next”:

Change the folder names if you want. I just accepted the defaults:

Review the options you have chosen and click “Next”:

When the prerequisite checks are complete, click “Install”. There are a couple of warnings that you can ignore:

The system will reboot automatically:

When the machine restarts, you’ll notice you’re prompted to login to a domain account now:

Creating SharePoint Users in Active Directory

The SharePoint Server installation requires a couple of users to be created in Active Directory. If you bypass this step, when it comes to configuring SharePoint it will prompt you to either use existing managed accounts or create a new one, BUT it doesn’t do the actual creation and the configuration produces errors so it’s important to get this step done before configuring SharePoint Server 2016. To do this, start “Active Directory Users and Computers” from the list of Administrative Tools:

Drill into the domain created above (in my case, corp.archtisdev.com) and click “Users”, then click the “Create a new user in the current container” icon from the icons across the top of the screen:

In my case, I’m going to use spAdmin for the SharePoint Setup Administrator, and spFarmAcc for the SharePoint Farm Account. The steps are the same for each one at this level, so I’m just going to show one in the screenshots below. Enter values for full name, user logon name, and user logon name (pre-Windows 2000) and click “Next”:

On the next screen, enter and confirm a password. I also deselected the radio button for “User must change password at next logon” and selected “Password never expires”. Click “Next”:

Finally click “Finish”:

Repeat the same steps to create the spFarmAcc user.

We also need to need to add the spAdmin account to the administrators group. To do this, click on the “Builtin” domain under your domain name, then double click the “Adminsitrators” security group:

Click on the “Members” tab, then click “Add”:

Enter “spAdmin” in the object names field and click “Check Names”:

Click “OK” to close the window:

You can now exit “Active Directory Users and Computers”. Next we want to start SQL Server Management Studio so start that from the list of apps on your VM (for some reason, Microsoft has deemed it necessary to call it “Microsoft SQL Server Management Studio” rather than just “SQL Server Management Studio”, so you’ll need to look for that):

When prompted to connect to the server, just click “Connect”:

In the Object Explorer, drill into “Security” and then “Logins”. You’ll see spAdmin is not listed, so right-click on “Logins” and select “New Login…” from the menu:

On the “Login – New” page, enter your domain name followed by spAdmin (e.g. “ARCHTISDEV\spAdmin”) for the login name, then select the “Server Roles” page from the top left of the screen:

Select the dbcreator, securityadmin and sysadmin server roles in addition to public (which is selected by default) and click “OK”:

Now we should be able to move onto the SharePoint Server installation, which will be the subject of my next post.

Pete

After 22 years of working at Oracle in just about every role except Marketing and Support, in December 2016 I moved to a new role with a small company called archTIS, based out of Barton in the ACT, Australia. My new role is the technical architect for the company and I own the product technical solutions for the products produced by archTIS. archTIS has developed strategic architecture and solution services to enable the rapid implementation and accreditation of secure information management and sharing capabilities for both the enterprise and the smaller communities of interest. You can find out more about the company at our web site, www.archtis.com. I am also a member of the OakTable Network, and have presented at RMOUG Training Days, Hotsos Symposia, Oracle OpenWorld conferences, and other user group events. I have co-authored the Expert Oracle Enterprise Manager 12c and Practical Oracle Database Appliance books published by Apress, and am one of the authors of the Building Database Clouds in Oracle Database 12c book published by Addison Wesley.

Leave a Reply

Your email address will not be published. Required fields are marked *