Building SharePoint 2016 development environment – Part 8 – Installing SQL 2016 ready for SharePoint 2016.


A few years ago I wrote “Build your SharePoint 2013 development machine on Windows Server 2012” series, I mainly work in the cloud now, but as the blogs was so popular, I thought I would create a new series for the newer version of SharePoint.

You can access other parts of this post below.

Setting up directories for SQL.

We are going to set up following directories on the d: drive.

  • Bring up Explorer by click on Windows Key + E
  • Double click on the D drive.
  • Create the following directories.
    • D:\SQL
    • D:\SQL\Data
    • D:\SQL\Logs
    • D:\SQL\Temp\Data
    • D:\SQL\Temp\Logs
    • D:\SQL\Backup

Installing SQL Server 2016 Standard Edition 64 bit

From the part 5 of these blogs we have already inserted the ISO file into the virtual machine. By opening Explorer inside the virtual machine, you should see DVD Drive with the SQL disk inserted.

  • Double click on the DVD drive, or run Setup.exe
  • The SQL Server Installation Center will open up. On the left hand side, click Installation.
  • Click on New SQL Server stand-alone installation or add features to an existing installation
  • The product key should already be entered, click Next, accept the License Terms. Click Next.
  • Tick Use Microsoft Update to check for updates (Recommended). Click Next.
  • Setup install rules will identify any problems that might occur when installing SQL Server Setup support files. They should all passes. (Ignore warnings) Click Next.
  • On the Feature Selection Page. Select Database Engine Services, Full-Text and Semantic Extractions for Search. Click Next.
  • On the Installation Rules page click Next.
  • On the Instance Configuration page click Next.
  • On the Server Configuration page, change the SQL Server Agent Start Up Type to Automatic. Also change the SQL Server Database Engine to use your SP_SQL account, and enter the password. Pa55w0rd
  • Click Next
  • On the Database Engine Configuration page, select Mixed Mode and enter the password and confirm password as Pa55w0rd. And Click Add Current User.
  • On the Data Directories tab, change the location of the directories.
    • Data Root Directory – d:\SQL
    • User Database Directory – d:\SQL\Data
    • User Database Log Directory – d:\SQL\Logs
    • Backup Direcotory – d:\SQL\BackUp
  • On the TempDB tab
    • Data Directories – d:\SQL\Temp\Data
    • Log Directory – d:\Sql\Temp\Logs
  • On the FILESTREAM tab, tick Enable FileStream for Transact-SQL access and Enable FILESTREAM for file I/O access. Click Next.
  • On the Ready to Install page, click Install
  • After installation your SQL Server 2016 is installed. You may be asked to reboot.

Installing SQL Server Management Tools

It seems that SQL 2016 have now separated out the SQL Server and SQL Server Management Tools. So this is an additional step to carry out.

  1. Back on the SQL Server Installation Center (run setup.exe from DVD drive if not showing), click on Install SQL Server Management Tools
  2. This takes you off to a website address https://msdn.microsoft.com/en-us/library/mt238290.aspx to download the SQL Server Management Studio (SSMS) seperately.
  3. Click the download link, and run it. (Or Save and run it afterwards) Over 800MB in size.
  4. Click Install.
  5. Once installed, you will get a success message. Close this screen.

Configuring SQL Server 2016

  1. From the start screen type SQL Server Configuration Manager and select the application.
  2. Click to expand SQL Server Network Configuration (not the 32 bit), and choose Protocols for MSSSQLServer, and ensure TCP/IP and Named Pipes are enabled. To enable them right click them and select Enable. Click OK at the warning.
  3. Close the SQL Server Configuration Manager.

Apply the DisableLoopbackCheck Registry Fix

  1. Click the Windows PowerShell icon in the Taskbar.
  2. Run the following PowerShell commands, pressing [Enter] after each one:

Giving SP_Setup account access

Note: If you continue without doing the DisableLoopback Check registry you will get an error message saying “Login Failed. The login is from an untrusted domain and connot be used with Windows authentication”

  1. From the start screen type SQL Server 2016 Management Studio and open the application.
  2. Change the server name to SQL2016 (we set a host name in an earlier post)
    and logon as Windows authentication.
  3. Expand Security from the object explorer and right click Logins and select New Login…
  4. Next to the Login Name click Search
  5. Ensure the Location is set for Entire Directory, and then type SP_Setup and click Check Names.
  6. Click OK.
  7. On the left hand panel, select the Server Roles page, and tick dbcreator, securityadmin and sysadmin. Then click OK.

Now we can think about Installing SharePoint 2016.

Now is another good time to shut down both Domain Controller, and the SharePoint machine and take a checkpoint/snapshot before continuing.

Advertisements

Building SharePoint 2016 development environment – Part 7 – Adding AD accounts.


A few years ago I wrote “Build your SharePoint 2013 development machine on Windows Server 2012” series, I mainly work in the cloud now, but as the blogs was so popular, I thought I would create a new series for the newer version of SharePoint.

You can access other parts of this post below.

Creating the Accounts required

Please note that the following setup is just for a simple development environment. You should read the Microsoft SharePoint Server 2016 Prepare for Installation section.

First we need to create 9 different accounts.

SP_Farm – SharePoint Farm account

SP_Setup – SharePoint Setup Account

SP_Content – SharePoint Content account for the Content Databases

SP_Services – SharePoint account for the Shared Services within SharePoint

SP_SQL – The account to run SQL with.

SP_Search – The account used for SharePoint Search Crawler

SP_UserProfile – The account used for User Profile service

SP_SuperUser – SharePoint publishing infrastructure super user account

SP_SuperReader -SharePoint publishing infrastructure super reader account

  1. Log into the Domain Controller.
  2. In the Start Menu, type Active Directory Users and Computers. Select the application.
  3. Expand the tree in the left hand pane to see the Managed Service Accounts OU. Select the Managed Service Accounts OU.
  4. Right click on Managed Service Accounts and select New > User. Create a new user called SP_Farm. Set the Full Name and Log on name to SP_Farm. Click Next.
  5. In the password dialog screen, enter the following and click Next.
    1. Password and Confirm Password: Pa55w0rd
    2. Untick User must change password at next logon.
    3. Leave User cannot change password as unticked.
    4. Tick Password never expires
    5. Leave Account is disabled as unticked
    6. Click Next. Then Finish

Repeat the steps 1-4 for the remaining accounts (SP_Setup,
SP_Content, SP_Services, SP_SQL, SP_Search, SP_UserProfile, SP_SuperUser, SP_SuperReader, and SP_Unattended)

You could add any users here, but when creating their accounts, add them to User OU not the Managed Service Accounts

Setting up Host names (SQL2016, Intranet, Dev, HNSC, my)

  1. On your Domain controller, in the start menu, type DNS. Open the application to the DNS Manager
  2. Expand the forward lookup zones contained in the left panel.
  3. Right click on the zone cfcode2016.com and click on a New Host
    (A or AAAA)
  4. Type in the name of the record. In this case we are going to name our SQL Server SQL2016. Set the IP address as the IP address where we are installing SQL. This was configured in our previous post as 192.168.137.200. Click on Add Host.
  5. You will then get a verification dialog, and after click OK. You will see the record has been created in the right pane of the DNS manager.
  6. To Check that this is all working, open a command prompt, and type
    ipconfig -flushdns
    Then type
    ping SQL2016


    Note: If it’s unable to ping, you might have the firewall switched on for domains on your VM’s. You can turn this off. (Remember this is development machine only)

    Repeat the above steps 1-6 for Dev and Intranet, HNSC and my

Building SharePoint 2016 development environment – Part 6 – Creating SQL & SharePoint Machine.


A few years ago I wrote “Build your SharePoint 2013 development machine on Windows Server 2012” series, I mainly work in the cloud now, but as the blogs was so popular, I thought I would create a new series for the newer version of SharePoint.

You can access other parts of this post below.

Creating your SQL & SharePoint Machine

  1. Follow my old blog on Creating your hyper V windows Server 2012 machine from a differencing disk. Give about 16GB (16,384Mb) of memory to the machine, and only add the Internal Network connection.
  2. When you start up your new Virtual Machine based on the base disk, you will be required to enter a valid Key Code for Windows Server 2012 R2 Standard Edition. Let the sysprep process complete, answer any installation questions required and then log in.
  3. You now have Virtual Machine that we are going to use for our SQL and SharePoint.
  4. Enhanced mode of Hyper V will work after you have logged in once, and then reboot. (Believe tools install themselves in the background).

Set Static IP address

  • In the start menu, type View Network Connections and under Settings you should see a link.
  • Right click your network internal adapter and click Properties.
  • In the properties windows, select Internet Protocol Version 4 (TCP/IPv4) and then click the Properties button.
  • Update the properties form to have the following information:
    • IP Address: 192.168.137.200
    • Subnet Mask: 255.255.255.0
    • Default gateway: 192.168.137.1
    • Preferred DNS Server: 192.168.137.100

Change the name of the Machine.

  1. From the Server Manager screen. Click on Local Server.
  2. Where it says Computer Name, click the link.
  3. This will open the System Properties dialog box.
  4. Click on the Change button.
  5. Enter the name of the server. I have called mine ‘CFSP2016’
  6. Click OK.
  7. Click OK and reboot when asked.

Add the SharePoint machine to the Domain.

  1. From the Server Manager screen. Click on Local Server.
  2. Where it says Workgroup, click the link.
  3. This will open the System Properties dialog box.
  4. Click on the Change button.
  5. Click on the Domain radio button. Type in the name of your domain you gave your machine in the previous blog post. (Part 4- Installing Active Directory)
  6. Enter the name of the server. I have called mine ‘CFSP2016’
  7. Click OK.
  8. Click OK and reboot when asked.

Important from now on: When you sign in, ensure you sign in as domain\administrator not computerName\Administrator, defaults to computerName\Administrator.
To ensure that when you type administrator into the SharePoint server to run as domain admin, it doesn’t automatically think that you mean built in administrator, we are going to rename the administrator built in account.

  1. From the Start menu, type User, and select Edit local users and groups
  2. In the left hand pane, select Users.
  3. On the right hand pane, right click Administrator and select Rename
  4. Change the name to something other than Administrator. I’ve renamed mine to Admin.
  5. If you log out, and try to log in as COMPUTERNAME\Administrator it will state the password is incorrect. Change this to COMPUTERNAME\Admin then try your password. You should be able to log in.

Adding a DVD drive for ISO in Virtual Machine.

Before I can install SQL or SharePoint I need a way to install my ISO files onto my Virtual Machine. These steps will show you how to add a DVD player to your virtual machine that will allow you to read ISO files.

  1. Open up Hyper-V Manager, right click your Virtual machine that you are using for SQL & SharePoint and click settings.
  2. Within the settings window, under Hardware select SCSI controller. Then select DVD Drive, and click Add.
  3. Then ready for the next step, select Image File: and find your SQL Server 2016 Standard Edition ISO file.

Building SharePoint 2016 development environment – Part 5 – Creating Certificate Authority.


A few years ago I wrote “Build your SharePoint 2013 development machine on Windows Server 2012” series, I mainly work in the cloud now, but as the blogs was so popular, I thought I would create a new series for the newer version of SharePoint.

You can access other parts of this post below.

Installing Certificate Authority

To allow our SharePoint sites to use SSL, these certificates come from a trusted certificate authority. This is what we are going to create

  • On your domain controller, open up Server Manager
  • On the right, click Manage > Add Roles and Features
  • Click Next
  • On Select installation type ensure that Role-based or feature based installation is selected. Click Next
  • On Select destination server screen, keep default choice of your domain controller, and click Next.
  • Select Active Directory Certificate Services and click Add Features when dialog pops up. Click Next.
  • On Select features click Next.
  • On Active Directory Certificate Services screen, it informs you how you cannot change the name or domain settings of this computer. Click Next.
  • On Select role services, select the following
    • Certification Authority
    • Certificate Enrollment Policy Web Service
    • Certificate Enrollment Web Service

    Click Add Features when prompted.

  • On Web Server Role (IIS) click Next.
  • On the Select role services click Next
  • Tick the Restart the destination server automatically if required, say yes to the dialog prompt. Then click Install.
  • Once the installation completes, you need to configure the Certification Services, click the link Configure Active Directory Certificate Services on the destination server
  • On the Credentials screen, ensure you are using domain admin account. Click Next
  • On Role Services tick Certification Authority, then click Next
  • On Setup Type, leave the default of Enterprise CA, click Next
  • Since this is the first CA in the domain, on CA Type leave the default of Root CA. Click Next
  • On Private Key leave it as Create a new private key and click Next
  • On Cryptography for CA select SHA256. Click Next
  • On CA Name, for development environment, I recommend to rename it to something simple like MY-CA or you can leave as is (You’ll need to remember this much later). Click Next.
  • On Validity Period, you can change the number of years if you wish. I would imagine in 5 years SharePoint 2016 will be old hat, and be using SharePoint 2020. Click Next.
  • Accept the default locations of the CA Database. Click Next.
  • On the final screen, Confirmation, click Configure. You will be presented with a succeeded screen. Click Close. You will be prompted with a Do you want to configure additional role services? Dialog. Click Yes.
  • After clicking yes, you will be presented back with the Credentials screen. Click Next
  • On the Role Services screen, now select both Certificate Enrollment Web Service and Certificate Enrollment Policy Web Service. Click Next.
  • On the CA for CES screen, leave as is and click Next. This will allow your target CA to issue web certificates to SharePoint and other web servers. Click Next.
  • The Authentication Type for CES keep as the default Windows integrated authentication click Next.
  • On Service Account for CES switch the radio button to use Use the built-in application pool identity. Click Next
  • The Authentication Type for CEP leave as Windows integrated authentication. Click Next.
  • On the Server Certificate screen, select your existing self-signed certificate. Click Next
  • On the last screen, click Configure.
  • Finally, you are presented with success messages. Click Close.

Your Certificate Authority is now complete and read to give our certs to your SharePoint farm. This will be configured later after we have at least installed SharePoint.

Setting up a Global Policy for Certificate Enrollment.

Here we are going to change a global policy for all machines added to the domain. This is so Auto enrollment of certificate policies is allowed.

  1. Open up the Group Policy Management console, by typing gpmc.msc in a run window.
  2. Expand the Forest down to our domain.
  3. Right click the domain and select Create a GPO in this domain, and Link it here…
  4. In the New GPO dialog, give it the name of Cert Enrollment Policy, and click OK.
  5. In the left pane of Group Policy Management expand your domain and at the top you should see Cert Enrollment Policy, right click it and select edit.
  6. Navigate down to Computer Configuration > Policies > Windows Settings > Security Settings > Public Key Policies and double click Certificate Services Client – Auto Enrollment
  7. In the dialog, set the Configuration Model to Enabled. Click OK.

We have reached the end of this blog post. It again could be a good idea, to shut the machine down and create a new checkpoint.

Building SharePoint 2016 development environment – Part 4 – Installing Active Directory.


A few years ago I wrote “Build your SharePoint 2013 development machine on Windows Server 2012” series, I mainly work in the cloud now, but as the blogs was so popular, I thought I would create a new series for the newer version of SharePoint.

You can access other parts of this post below.

Creating your Domain Controller Machine

  1. First remove the Base Virtual Machine you created in the previous posts from the Hyper V manager. Select the base virtual machine and on the right hand side, under the machine name, click Delete. Don’t worry this just deletes the machine, but keeps the virtual machine disk. By deleting this from Hyper V there is no chance of accidently starting it.
  2. Next follow my old blog on Creating your hyper V windows Server 2012 machine from a differencing disk. Give about 2GB of memory to the machine, use generation 2, and call your differencing disk AD2012R2, and the same with the machine name.
  3. When you start up your new Virtual Machine based on the base disk, you will be required to enter a valid Key Code for Windows Server 2012 R2 Standard Edition. Let the sysprep process complete, answer any installation questions required and then log in.
  4. You now have Virtual Machine that we are going to use for a Domain Controller.
  5. You should get Enhanced mode back after login in and rebooting once. I believe hyper V installing tools in the background the first time you login.

Adding the Internal Network connection

You can do the following steps with the Virtual Machine switched on or off.

  1. On the Hyper-V manager screen, right click your newly created Virtual Machine that we are using for Active Directory, and click Settings.
  2. On the Settings page add a new Network Adapter and click Add
  3. Select Internal as the Virtual Switch and then click OK.

Giving the Virtual Machine a Static External IP Address.

First thing you will need to do is Set the IP of the machine to Static address.

  1. Log on to the Virtual Machine, as administrator | Pa55w0rd.
  2. From Start Menu type CMD and open the command prompt.
  3. Type ipconfig /all
  4. Here you should see what the current dynamic IP address is for your virtual machine.
  5. Back in the start menu, type View Network Connections and under Settings you should see a link.
  6. Right click your network External adapter and click Properties.
  7. In the properties windows, select Internet Protocol Version 4 (TCP/IPv4) and then click the Properties button.
  8. Update the properties form to match your current machine configuration.
  9. Click OK. Click Close. After a moment your adapter will reset itself and you should have internet access again.

Giving the Virtual Machine a Static Internal IP Address

  • In the start menu, type View Network Connections and under Settings you should see a link.
  • Right click your network internal adapter and click Properties.
  • In the properties windows, select Internet Protocol Version 4 (TCP/IPv4) and then click the Properties button.
  • Update the properties form to have the following information:
    • IP Address: 192.168.137.100
    • Subnet Mask: 255.255.255.0
    • Default gateway: 192.168.137.1
    • Preferred DNS Server: 192.168.137.100

Configure the Host internal IP settings.

  • Back on your Host machine. Open the run command and type ncpa.cpl
  • Right click your Internal adapter, and click properties.
  • In the properties windows, select Internet Protocol Version 4 (TCP/IPv4) and then click the Properties button.
  • Update the properties form to have the following information:
    • IP Address: 192.168.137.1
    • Subnet Mask: 255.255.255.0
    • Default gateway: 192.168.137.1
    • Preferred DNS Server: 192.168.137.100

Change the name of the Machine.

  1. From the Server Manager screen. Click on Local Server.
  2. Where it says Computer Name, click the link.
  3. This will open the System Properties dialog box.
  4. Click on the Change button.
  5. Enter the name of the server. I have called mine ‘CFAD’
  6. Click OK.
  7. Click OK and reboot when asked.

Setting up the Domain Controller.

  • Login to the CFAD virtual machine using administrator | Pa55w0rd
  • On the Server Manager > Dashboard, click (2) Add roles and features
    • On the Add Roles and Feature Wizard you will be present with Before you begin. Click Next
    • On Installation Type select Role-Based or Feature-based installation
    • On Select destination server accept the default of Select a Server from the server pool with CFAD selected. Click Next
    • On the Server Roles, select “Active Directory Domain Services
    • Accept the Additional features required, by clicking Add Features.
    • Keep press Next until you reach the Confirmation screen. Then click Install.
      Once it is installed click Close on the Wizard page.
  • Back on the Server Manager Dashboard you will see the item AD DS added to the Roles and Server Groups. Click on the title of AD DS. Note it will say at the top of the screen Configuration required for Active Directory Domain Services at CFAD. At the far right of this message click More…
  • The more link will bring up the All Servers Task Detail dialog. It will show an action of Promote this server to a domain. Click on that link.
  • On the Deployment Configuration screen select Add a New Forest.
    • I named my root domain cfcode2016.com. Click Next.
    • The next screen seems to processes for some time. I thought the screen was locked/froze but after a minute or so it was fine.
    • Give a password of Pa55w0rd to the Directory Services Restore Mode (DSRM) password. Click Next
    • Ignore the DNS Options warning. Click Next.
    • It then check the NetBIOS domain name. (This too takes a little time to show.) Click Next.
    • Next it will specify the Path locations of the AD DS database, log files, and SYSVOL. Accept the defaults and click Next.
    • The next page allows you to review your selection, and export to a Windows PowerShell script if you wish to automate additional installations. Click Next.
    • Before the actual install of AD, all prerequisites are checked. If all prerequisite checks are passed then click install. You can ignore warnings.
    • The machine will restart automatically after the promotion of the server to a DC has finished.
    • Once the server has rebooted and you have log on to it, if you click on Server Manager | Tools, you will notice that the following items have been installed:
      • Active Directory Administrative Center
      • Active Directory Domains and Trust
      • Active Directory Module for Windows PowerShell
      • Active Directory Sites and Services
      • Active Directory Users and Computers
      • ADSI Edit
      • DNS
      • Group Policy Management

  • Now is a good time to shut down the machine and perform a checkpoint in hyper V manager. That way if you don’t get something right in the next post, you can always revert back your machine back to the end of this post. (Wish I followed my own advice sometimes).

Building SharePoint 2016 development environment – Part 3 – Building a base disk to use for differencing disk.


A few years ago I wrote “Build your SharePoint 2013 development machine on Windows Server 2012” series, I mainly work in the cloud now, but as the blogs was so popular, I thought I would create a new series for the newer version of SharePoint.

You can access other parts of this post below.

Building a base disk to use for differencing disk.

Why am I using differencing disks? To build my dev environment, I need a minimum of 2 servers. An Active Directory, and a SQL & SharePoint server. You could possibly use 3 servers and separate the SQL and SharePoint out, or you might expand out SharePoint and not just use the stand alone configuration. You might add other servers in the future (You will need a beefy machine for this.) By building a base disk it will save you time in the future, Windows, the basic set up of features, updates, programs will already be on the machine, and you just need to add the extra programs you require for the given server.

What needs to go on here?

You need to put on this machine everything that you would probably want on all your virtual machines. Your list might be different to mine.

  • Windows Server 2012 R2 Standard Edition 64 bit.
  • Firefox
  • Chrome – with any extensions
  • Fiddler

Creating your Virtual Machine.

  1. Open up Hyper-V Manager
  2. Under Actions, click on New and select Virtual Machine. Click Next.
  3. Name you Virtual Machine, and your choice if you wish to store the virtual machine in a different location. (Preferably on a SSD drive)
  4. On the Specify Generation page, select Generation 2.
  5. Assign some memory, at this stage 6GB (6144mb) will be enough for installing everything. Click Next.
  6. Configure the Network to point to the External connection and click Next.
  7. Name your Virtual Hard Disk. Change the location if you wish, and I recommend creating a 400GB hard disk. (If you have room). We will split the disk inside the virtual machine into 100GB and 300GB for C and D drive. Click Next.
  8. Install Options, you can select Install an Operating system from a Boot CD/DVD-ROM and in my case I have selected the Windows Server 2012 R2 with Update (x64) Image file.

Install Windows 2012 R2 Server Standard Edition.

Inside you Hyper V manager you should now see your Virtual Machine. In my case it’s called CFBase. By right clicking on the machine you can connect to it. A window will open. You can then click the Start Button.

  1. Configure the language. Click Next
  2. Then Click Install Now.
  3. Insert your product key. Click Next.
  4. Select Windows Server 2012 R2 Standard (Server with a GUI) and then click Next.
  5. Tick I accept the license terms. Click Next.
  6. Select the Custom: Install Windows only (advanced) option.
  7. In the Where do you want to install Windows. Click New Create a new space of 102400MB. This will create a 100GB space. Accept the message that says Windows might create additional partitions for system files. You should now see Drive 0 Partition 1: Recovery, Drive 0 Partition 2, Drive 0 Partition 3, Drive 0 Partition 4 and Drive 0 Unallocated Space. Select the last one and click New, then Apply. This will set up your drive space. Select Drive 0 Partition 4 (100GB) then click Next, and Windows 2012 R2 will start installing on the 100GB drive.
  8. Once it has finished installing itself, it will ask you for a password for the Administrator. I use Pa55w0rd. Click Finish.
  9. Now you can log in. To perform Ctrl + Alt + Del in a Hyper V Machine. Press Ctrl + Alt + End.

Configuring Windows 2012 R2

  1. Once you have logged back in again the Server Manager appears. On the left hand menu, click on Local Server. This will bring up all the properties for this machine.
  2. Disable the Windows Firewall, by clicking on the Windows Firewall Public: On link.
  3. Then click the Advanced Settings on the left of the screen.
  4. On the right panel of Windows Firewall with Advanced Security, click Properties.
  5. For each Tab Profile (Domain, Private, Public) switch the Firewall state to Off. Then Click OK.
  6. Back on the Server Manager screen click the On link for IE Enchanced Security Configuration. Then turn this off for Administrators and Users. Click OK.
  7. Go back to the Start menu. Type UAC, and select settings from the right hand side. Click on Change User Account Control Settings.
  8. On the User Account Control Settings, move the slider down to the bottom. This will prevent the screen keep prompting you when an administrative task needs to be made. Click OK.
  9. Back in the Server Manager properties window for the server. Enable Remote Desktop. Click the Disabled link. Then select Allow remote connections to this computer. Click OK.
  10. Back in the Server Manager properties window for the server, Click on Windows Update Not Configured link. This will open the Windows Update Dialog.
  11. Click Let me choose my settings. Then on Choose your Windows Update settings, I always have Download updates but let me choose whether to install them. And then I tick Recommended updates. Click OK.
  12. Your server will now check for updates. Install anything that is outstanding.
    Note: You might have to repeat the check for Windows Update process a couple of times.

Disable the Shutdown Event tracker

  1. Open the start menu and type gpedit.msc. Click on the program to open it.
  2. In Group Policy Editor, navigate to Computer Configuration\Administrative Templates\System, open the Display Shutdown Event Tracker policy, and set it to Disabled.

    Now when you shut down you shouldn’t see the Shutdown tracker appear.

Enabling the Desktop Experience

  1. Open up the Server Manager.
  2. On the right of the screen click Mange > Add Roles and Features
  3. Click Next.
  4. Ensure Role-based or Feature-based installation is selected. Click Next.
  5. On Select destination server click Next.
  6. On Select server roles click Next.
  7. On Select features. Expand User Interfaces and infrastructure (Installed) and tick Desktop Experience. Add the addition features that it requires. Click Next.
  8. Click Install.
  9. Restart the Server.

Getting the Sound to work within your Virtual Machine.

With Hyper V in Windows 10, there is an enhanced session.

By running in enhanced mode, hovering over the speaker Icon in the task bar, it will state that Audio Service isn’t running. Right click it, and select sounds. A dialog will then pop up and ask if you want the audio service to be enabled. Click Yes.

The speaker icon will no longer have a red cross over it. And you should be able to hear sound through your VM if you enter the machine by using enhanced mode, or via a remote desktop connection.

Formatting the second drive.

If you take a look in explorer, you will only see a C:\ drive which should have 149GB. However we created a 400GB disk, and spilt it into 150GB and 250GB. We need to format the second disk.

  1. In Server Manager, in the top right corner, select Tools > Computer Management.
  2. In the Computer Management window, in the left hand pane, under storage, select Disk Management
  3. First thing I will do, is change the CD-ROM drive from D: to E: just so I can have a C and D drive as hard disk.
    1. Right click CD-ROM 0 at the bottom of the screen. Select Change Drive Letter and Path.
    2. On the dialog, click the Change button.
    3. Assign the new drive letter as E. Click OK.
    4. Click Yes to the warning message.
  4. Now we will format the 250GB drive.
    1. At the bottom, on Disk 0 row, at the end you should see 250.00 GB RAW. Right click this and select Format
    2. Put a name is the Volume label if you wish. I’m going to delete mine, and then leave everything as it is. Click OK.
    3. Assuming you have clicked on the correct area, click OK to the Format dialog warning.
    4. After the formatting has completed, right click on the area again, and this time, select Change Drive Letter and Paths.
    5. On the dialog, click Add.
    6. Ensure that D is assigned. Then click OK.
    7. Your explorer window will now show a C, D and E drive.

Extra Stuff to install.

Now you can install any additional software that you want to be available on every virtual machine you build. Below is a list of items I’m installing, you might have more.

Setting up the menu

If you currently look at your menu you will notice that everything is everywhere. You can click and drag tiles and position them in more logical sections. By moving them between other sections you can create new sections.

By clicking on the bottom right of the menu screen there is a minus icon. By clicking this, you will zoom out. Then by right clicking a section you can then name it.

I organised my menu to look like below screen shot. You might prefer a different layout, or have other programs to add.

Sysprep the machine.

As I have already written a blog on Sysprepping a machine while keeping the Menu the same after sysprep follow the following blog. Windows 8 and Windows Server 2012 Start Screen is Reset when Sysprep

Once you have completed the above post of Sysprep while keeping the Start menu. Do not turn on your Virtual Machine again. If you do it will start the Sysprep process. At this point, go to where the base hard drive is for the Virtual Machine, and set it to Read Only.

Building SharePoint 2016 development environment – Part 2 – Setting up and configuring Host Computer using Hyper V.


A few years ago I wrote “Build your SharePoint 2013 development machine on Windows Server 2012” series, I mainly work in the cloud now, but as the blogs was so popular, I thought I would create a new series for the newer version of SharePoint.

You can access other parts of this post below.

Setting up and Configuring Host Computer using Hyper V.

From comparing from my SharePoint 2013 blog post, I’ve noticed I haven’t actually upgraded my PC in 4 years. I still have an i7 3770K, 32GB ram. I have larger SSD hard drives than before. My host PC is running Windows 10, and I have activated the feature to include Hyper V (Same for Windows 10).

Configuring the Network adapters

I will be creating just two Virtual Machines. The Domain Controller machine and the SQL & SharePoint machine. I want the Virtual Machines to have internet access, but to be on their own network IP range. The following instructions will show you my set up.

  • Open Hyper V Manager, and on the right hand side of the screen, click Virtual Switch Manager.
  • Create an external adapter (if it’s not already there) and point the network to your external network connection of your host machine.
  • Then create an Internal adapter. Point that to the Internal network.
  • Click OK. To save your Virtual Switches information.
  • On your host machine, open up your Network Connections. In run command, type npca.cpl
  • When the Network connections open, you should see your two newly created Network switches.
  • Right Click on the External adapter and click Properties.
  • Select the Sharing tab, and then tick to ‘Allow other network users to connect through this computer’s Internet connection.’ Then select your Internal adapter and click OK on the properties.
  • The External Adapter should now say Shared

We will be doing further configuration within the Virtual Machines network in a later post, but for now we are done.