Active Directory Domain Services Installation on Windows Server 2016 Technical Preview 4:

Alright, to all the system administrators out there, this post would be on how to promote your Windows server 2016 to become a domain controller by installing the “Active Directory domain services” role on it. The installation is no different from what we have been doing on the previous versions of Windows server and almost all the steps are the same.

With that being said, let’s get started with the installation steps now,

  1. Open server manager as shown in the screenshot below and click on “Manage”

1.PNG

2. Once you click on “Manage” you will see an option which says ” Add roles and features “ , choose that and click  next .You can also click on ” Add roles and features” which you see on the server manager pane above to add the necessary roles and features.

2.PNG

3. Choose “Role based or feature-based installation “option and click “Next “as shown in the screen below.

3

Note:

  • Role-based or feature-based installation: This installation type installs or removes the various roles and features included with Windows 8 Server operating system editions.
  • Remote Desktop Services scenario-based installation: This new installation type enables the installation and configuration of Remote Desktop Services.

4. On the next screen which says “Select destination server “, choose the appropriate server on which you need to install the ADDS role. In this scenario you can see the server being highlighted below on which I would be installing the ADDS role.

Note:

  • Select a server from the server pool: Use this option to select a server from the server pool on the local computer. Confirm the destination by verifying the destination server in the upper right hand corner of the wizard.
  • Select a virtual hard disk: Use this option to select a local or remote Windows 8 Server virtual hard disk file. Only virtual hard disks that contain a Windows 8 Server operating system are valid destinations. Blank virtual hard disks or hard disks that contain an operating system other than Windows 8 Server will fail.

4.PNG

5. Now since we have selected the destination server, it’s time to go ahead and install the ADDS role on it, for that please check the screenshot below. On the sever roles pane, please check the checkbox for “ Active Directory Domain Services” and click “Next” as shown in the screenshot below .

5

6. Once done you will get a window which asks you to add the necessary features for “Active Directory Domain services” role , please go ahead and click on “ Add features” button so that it will add all the necessary features for ADDS.

6

Note:  The checkbox which says “Include management tools (if applicable) “option has to be chosen only when you need to include management tools as a part of adding the features.

7. Once you’re done with adding the necessary features the next screen would ask you to add some other features if required, please go ahead and click “Next” as we have already added the necessary features in the previous screen.

7.PNG

8. The next screen would give you an explanation on what ADDS is all about, please review it if interested and click “Next”.

8.PNG

9. On the next screen, check the checkbox which says “Restart the destination server automatically if required “and click on “Install”.

9.PNG

10. You can notice the Installation getting started on the next screen.

10.PNG

11. You can also notice the Installation progressing eventually as shown in the screen below.

11.PNG

12. Finally you will get the screen which says the installation is succeeded as shown in the screenshot below.

12.PNG

Note : You can click on “Export Configuration settings” option to export the settings to a notepad .The same configuration settings can be used for feature installations also .

13. Once this is done, please click on close and then open server manager .You will see an option which says “Promote this server to a domain controller “on the top right corner of the screen. Please click on that.

15.PNG

14. Now on the next screen where it asks you specify the “root domain name” , please go ahead and entire your domain name .

17.PNG

Things to note while entering the domain name: Make sure you’re entering the domain name which you own, if it’s a lab environment and you’re connected to the internet you need to specify unique domain names which is not being used by others. You can’t enter a domain name which is owned by someone or by any company. So please make sure you abide to these things while entering the domain name.

The error which you see in the above screen is because I didn’t enter the root domain name correctly .The root domain name should be entered in this format (i.e. “domain name”.COM) and by any chance if you don’t do that correctly you will end up noticing that error message.

15. So please ensure that you’re entering the domain name correctly in the correct format and click on next, this will take you to the next screen which asks you to specify the domain controller options.

18

Now, on the above screen you will see an option which says “forest functional level” and “domain functional level”.  Now it’s very important that you choose these options very carefully or else you will end up in a scenario where you may not be able to add additional domain controllers to the server.

So let me try explaining what is a forest functional level and domain functional level, Functional levels determine the available Active Directory Domain Services (AD DS) domain or forest capabilities. They also determine which Windows Server operating systems you can run on domain controllers in the domain or forest. However, functional levels do not affect which operating systems you can run on workstations and member servers that are joined to the domain or forest.

When you deploy AD DS, set the domain and forest functional levels to the highest value that your environment can support. This way, you can use as many AD DS features as possible. For example, if you are sure that you will never add domain controllers that run Windows Server 2003 to the domain or forest, select the Windows Server 2008 functional level during the deployment process. However, if you might retain or add domain controllers that run Windows Server 2003, select the Windows Server 2003 functional level.

When you deploy a new forest, you are prompted to set the forest functional level and then set the domain functional level. You cannot set the domain functional level to a value that is lower than the forest functional level. For example, if you set the forest functional level to Windows Server 2008, you can set the domain functional level only to Windows Server 2008. In this case, the Windows 2000 native and Windows Server 2003 domain functional level values are not available. In addition, all domains that you subsequently add to that forest have the Windows Server 2008 domain functional level by default.

You can set the domain functional level to a value that is higher than the forest functional level. For example, if the forest functional level is Windows Server 2003, you can set the domain functional level to Windows Server 2003or higher.

16. So with that being said , I’m choosing the option as “ Windows server 2016 technical preview “ under forest function level and the same for domain functional level too and I’m clicking next. Also make sure you’re specifying the “Directory services restore mode “password also .This password has to be used for safe mode boot option in Windows servers which are acting as domain controllers. Using this password you can repair/recover and restore an Active Directory database.

19.PNG

17. On the next screen check the appropriate DNS options and click next.

20.PNG

18. Enter the “NetBIOS” name in the next screen and click next.

21.PNG

19. On the next screen, you will be asked to specify the AD database path where the “ NTDS.dit” file resides . Also you need to specify the log files path and the path for SYSVOL folder. Ideally the best practice is to keep this as it is .However, you can change the path as per your requirement.

22

20. Finally, you will get a screen where you can review the settings you made before clicking next.

23.PNG

21. You can click on the “View script “option, to view the script for the settings that you have configured. You can use that script for future configurations also if required. This is the screen you will get if you click on the “ View script “ option which displays the PowerShell command for the settings that we have configured .

24

22. Once you’ve verified that and clicked next, you will get a screen as shown below which will run the prerequisites check.

25.PNG

23. Once the prerequisite check is done, you will get a screen as shown below confirming that all the prerequisite checks have passed successfully.

26.PNG

24. Once you have verified that the prerequisites check is completed, go ahead and click on the install button, this will start installing ADDS.

27.PNG

25. Please be patient for few minutes as the installation will take some time .Once the installation is completed you server will be restarted.

28.PNG

26. Finally, you can verify the ADDS installation in your server by opening the Active directory console.

30.PNG

27. You can see the screen below where I’m logging into the server using the domain credentials.

29.PNG

So this concluded the ADDS installation steps in Windows Server 2016 Technical Preview 4 .Thanks for reading this post .Have a good one .

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Steps to deploy a farm solution in a SharePoint Farm:

Steps to deploy a farm solution (wsp file) in a SharePoint Farm:

Please follow the steps below to deploy a “farm solution” in a SharePoint Farm (both 2010 & 2013). A farm solution is something that can have an impact on the entire farm when deployed and being a SharePoint Administrator you can activate this on a specific web application or (on multiple web applications if you use the full-trust model ).

  1. Login to the SharePoint WFE server using the “SharePoint Farm account “.
  2. Open the “SharePoint Management Shell “window with elevated permissions and type the below command as show in the screenshot.

“ Add-SPSolution –LiteralPath D:\WSP\SPD_SendEmailWithAttachment.wsp”

1.png

Literal Path –>  Mention the folder path where you have saved the .wsp file.

SPD_SendEmailWithAttachment –> Here in this scenario the name of the wsp file that we are deploying is “SendEmailwithAttachment” and hence it has been named so.

WSP –> WSP stands for Windows SharePoint.

  1. Once you’re done typing the above command, hit “enter “and it will give you the details of the wsp file as shown below.

2.png

4. Once you’re done with that, run the below mentioned command to get the details of the .wsp file. Please make sure you’re copying the solution ID properly.

3.png

5. Now since you’re done with adding the farm solution, please go ahead and run the below mentioned command to install it. Please check the screenshot below for reference

“Install-SPSolution –Identity “solution ID” –GACDeployment”  (Solution ID would be the ID which you see in the screenshot below)

4.png

6. Finally, once you’re done installing the farm solution please navigate to “System settings” in Central Administration and click on “Manage farm solutions” as shown below.

5

7. Please check whether you’re able to see the wsp file that you currently deployed in the list of wsp files available there. In our scenario the wsp file name is “spd_sendemailwithattachment.wsp” and you can see that in the list of wsp files that has been deployed on the farm.

6.png

8. Since we have verified that the .wsp file has been deployed successfully, the next step would be to activate the feature on the web application. For this click on “Manage web applications” in Central Administration –>Select the web application on which you need to activate the feature –> click on Manage features on the top ribbon interface.

7.png

9. Finally check for the feature related to the solution that we deployed and click on activate (check screenshot below).

8

 

Thanks for reading this post . Happy SharePointing!!!

 

 

 

 

 

 

 

 

Setting up Windows Server 2016 Technical Preview 4 in Hyper-V:

Setting up Windows Server 2016 Technical Preview 4 in Hyper-V:

This article will give you a step-by-step explanation on how to set up Windows server 2016 Technical Preview 4 on Windows 10 Hyper-V:

  1. Open the Hyper-V manager console as shown in the screenshot below.

Note: If you’re not able to find Hyper-V on windows search, then that’s probably because you haven’t turned that on under “Turn Windows feature on or off” in Control Panel. So please make sure that is turned on

1

2. Click on “New” and choose “New Virtual machine “option as shown in the screenshot below.

2.png

3. Click “ Next”

3.png

4. In the next screen you need to specify the “Name” of the virtual machine and also the “location” to save it. Check screenshot below.

4.png

5. In the next screen you need to specify which “generation” you’re planning to go with. Now choosing the correct generation depends on certain criteria’s and please check this link for reference. Here, in this scenario I’m planning to go with “Generation 1” as this serves my purpose.

5.png

6. Specify the “RAM” configuration in the next screen, I’m planning to assign 4000 MB for this Virtual machine .However, if you check the “Dynamic memory” check box, then the Hyper-V will automatically re size the RAM configuration based on the application it hosts/runs.

6.png

NoteStarting in Windows 10/Windows Server Technical Preview, Hyper-V allows you to resize virtual machine memory without shutting down the virtual machine. To know how to do this, please check the screenshot below.

You can notice the “ Startup RAM”  being enabled for you , which means you’re allowed to change the “Startup RAM “ settings even when the Virtual machine is running .This was not the case in the previous version of Windows server and client Operating systems . This functionality got newly added in Windows 10/Windows server technical preview.

7. In the next screen, you need to specify the “Network” settings for creating the connection. This is something which has to be done prior hand itself before creating the “Virtual machine “ .You don’t need to worry if you didn’t configure this before creating the virtual machine as this can be done even after creating the “Virtual Machine” .

7.png

8. Now, if you need to identify which “Virtual switch” to use for your Hyper-V manager, then please check the options below. You need to choose the appropriate one based on your need.

8.png

a. External Switch will link a physical NIC of the Hyper-V host with a virtual one and then give your VMs access outside of the host, meaning your physical network and internet (if your physical network is connected to internet).

b. Internal switch should be used for building an independent virtual network when you need to connect VMs to each other and to a hypervisor as well.

c. Private switch will create a virtual network where all connected VMs will see each other, but not the Hyper-V host. This will completely isolate the VMs in that sandbox.

9.png

9. In the next screen you need to specify the “storage” size. I’m specifying “40GB” as the storage size here.

10.png

 

10. Please specify the “installation media” on the next screen. I’m choosing the “Image file” option as shown in the screenshot below as I’ve already saved the image file for Windows Server 2016 Technical Preview (i.e. ISO file) on my hard drive. Browse to the location where you have saved the Image file and add it.

11.png

11. The next screen will give you a summary of all the specifications you made.

12.png

12. Finally once that’s done please click on the “Finish” button and that will start the Virtual machine configuration. You can also see the new Virtual machine you’ve created on the “Virtual machine” console as shown in the screenshot below. You can see “Win2K16” below ….

13.png

13. Now, it’s time to go ahead and install the “Windows Server 2016 Technical Preview 4 “Operating system as we are done with the Virtual machine configuration. For that, please click on “Connect” as shown below and this will turn on the “Virtual machine “.

14.png

14. Post this step , just follow the traditional Windows OS installation steps which we have been doing for years till now. Hence, to get started, please click on “Install Now “as shown in the screen below.

16

 

15. The setup is starting now as shown in the screenshot below.

17.png

 

16. Now on the next screen , please choose the appropriate option that suits your need .The first one is server core installation which doesn’t give you a GUI and the next one is the normal ( Desktop experience ) installation which gives you the GUI option .

Server Core option:

18.png

GUI (desktop experience) based installation:

19.png

17. Choose Custom installation method.

20.png

18. Choose the drive to perform the installation on the next screen as shown below.

21.png

19. Click next and this will start the installation, the entire process would take about 20 minutes max, so please be patient until it’s complete.

22.png

20. Once the installation is done, it will prompt for the administrator password, please go ahead and specify that.

23.png

21. On the next screen, press “Ctrl+Alt+Delete” to unlock and key in the Administrator password.

24.png

22. You should be all set by now with the installation and now you can see Windows Server Technical 2016 preview 4 spinning on your new Virtual machine.

25.png