Microsoft released the IT Preview of SharePoint 2016 on August 2015 24th. I will, as usual, post, a step by step installation guide for installing SharePoint 2016 in order to build a trial or development environment. The aim of this guide is to be as detailed as possible with all the screen shots in order:
--> So be sure to have a computer with at least 16 Go of RAM with 200 Go of free disk space.
--> For this tutorial, I will use Windows Server 2012 R2, because the version of SharePoint 2016 is already a preview. I don't take the risk of mixing 2 preview products (there is a known issue when using Windows Server 2016 Technical Preview 3 regarding the IIS role when running the SharePoint 2016 preview prerequisites Installation (thanks to Corey Roth).
--> For this tutorial, I will use SQL Server 2014 , because as said before, the version of SharePoint 2016 is already a preview. I don't take the risk of mixing 2 preview products. (even if SQL Server 2016 seems to be much faster than SQL 2014)
Choose the ISO option
It is better to use an English version for an evaluation purpose so as to be sure to have the system messages in English. There is much more informations in the search engine for English messages.
To the question do you want System Center components included, choose "No".
Then, you can finally download the .ISO file of Windows Server 2012 R2
When VMWare is installed, open it and Click the "Create New Virtual Machine" button.
Then, add the reference to the .iso file of the Windows Server 2012 R2 OS you have downloaded. VMWare recognises the OS version automatically.
Then specify the Virtual Machine name and location.
Microsoft recommend 80 Go for the main hard disk. I let the automatic sizing set by VMWare regarding Windows Serve 2012 R2, because, if needed I know I can expand my disk. I chose to store the disk within a single file because it is better in matter of performances.
Then, VMWare is summarizing your first settings but you have to add some more regarding the hardware configuration.
First, start setting the memory as recommended by Microsoft, so at least 8 Go. (Of course it depends also on the amount you have in your Host Machine. Your host machine is your real computer).
Choose the same number of processors than in your host machine :
A good way to know the number or Cores is to open the task manager, and in the "Performances" tab, check the number of graphes... I have only one block so I have a mono Core in my host machine.
Deactivate all the devices you won't use, sound card, printer and so on. You don't need them for a trial or development environment...
Then, you can start installation. If you have a message 'You have an incorrect version of driver "vmci.sys"', open the machine .vmx file located in the virtual machine folder, locate the vmci0.present parameter and set it to FALSE.
The installation is starting loading the files...
Then, you are asked for chosing the langage settings...
Then you have to choose the type of Windows Server 2012 R2 OS you want... Choose a standard with GUI, and accept the License terms
After that you could choose the drive where install the OS but in our case as there is only one disk, we have no choice...
After having performed all that settings the installation is really starting...
It lasts roughly 10 to 20 minutes depending of the capacity of your host machine... Finally you are asked for setting the password for the Administrator account. Note : to do a ctrl Alt Del for a VMWare machine you have first to click on it then type ctr Alt and inser. You can also use the VMWare "Player" menu where this action is available.
When your Admin password is set, the system asks you to sign in.
and you finally can reach the machine with Windows Server 2012 R2 installed.
As your virtual machine will host SQL Server and SharePoint, you don't need to join a network, so click "No" to the right screen. So, it is done, you have a virtual machine with Windows server 2012 R2 on it, we just have to install SQL Server 2014 and SharePoint now, but before, let's perform some settings to improve the user experience of this trial or development environment and also preparing the installation of the other softwares (SQL Server 2014 and SharePoint 2016).
You can start the installation using the "Player" menu.
Then you have to give to the install program the authorization to run, on the next screens, just click "ok".
When the installation is finished you are asked for rebooting the vistual machine, just do it.
When the machine has restarted just minimize it and maximize it and you will notice that the virtual machine screen is now adjusting automatically to the host machine screen. Morevover, If you use the full-screen feature, you will have an experience as if the Windows Server 2012 R2 has been installed on your host computer!
Change the description and the server name (don't use a too long name since it is limited by the BIOS policy)
When it's done you are warned you will have to restart the server.
You will asked to "Restart now" when you will have clicked on the "Apply" button of the first modal window. Just do it
When your server are restarted you will notice that its name has changed...
Set everything to off.
When refreshing the dashboard you will notice that IE enhanced security has been set to Off.
Because we use a single virtual machine for trial or development matters, we can disable the firewall. Disabling the Firewalls will improve performances, and, furthermore, we won't have a warning regarding Firewall when installing SQL Server 2014. Thus, navigate to the Server Manager page and locate the "Windows Firewall" link button.
Click on it and on the opening pop-up, disable the Firewalls.
You will warn that it is not the recommended configuration, but, just don't care, our environment is for trial or development matters.
When closing the Firewalls configuration pop-up, you will notice that Firewalls has been deactivated properly.
Pass the warning screen... and the two next ones
Then, select the Feature menu and check the Framework 3.5 option.
Start the activation of this feature...
You will obtain this screen when it is complete.
SQL Server 2014 requires this Service Pack. Navigate to the Microsoft Download Center page for downloading this Service Pack 1
Download the package...
when it's downloaded run the installation. If it is not running, don't mind, it means that the feature on the server is already complete.
We can proceed to the installation of SQL Server 2014
Navigate to the Technet page to downlod the SQL Server 2014 SP1 180 days evaluation. You will be warned that you have to sign in.
Take care to choose the ISO file
and the 64bit type version of SQL Server 2014 + SP1
For a matter of testing, it is always better to choose the English products...
Then you finally can proceed to the download...
then, browse for the SQL Server 2014 installation .iso file
When the .iso image is mounted click the Windows Server 2012 R2 start button.
Then, locate the "This PC" button and click on it.
You can see that the .iso image of the SQL Server 2014 + SP1 has been properly mounted.
We are now ready to install SQL Server 2014 + SP1
So, double-click on the SQL Server 2014 .iso image. The SQL Server 2014 installation wizard is launched. Then click on the installation menu item
And the first item of the new screen : New SQL Server stand-alone installation...
Pass the license screen since we use an evaluation version
and the license terms...
Then enable the automatic checking for updates...
Check that the first rules are passed
Let the first option checked for the next screen
Regarding the features, for SharePoint, you only need two : Database Engine Service and Management Tools - Basic
Pass the Feature Rules
Let the default option for the next screen. Don't use a named instance because it will be more complicated to install SharePoint with a named instance.
Let the automatic service account settings
Enable Mixed mode that allows you to use the "sa" account to connect. Set a complex password, like P@ssw0rd, if not you won't be able to pass this screeen. It is very useful sometimes to have this account in case of connection problem to SQL Server. Use the administrator account of the machine to be the administrator account of SQL.
SQL intallation wizard, then, summarizes your choices...
Then, launch the installation...
You should obtain this screen when installation is complete :
We are now going to check if SQL Server has been installed properly. Click the Window Start button and when arriving in the Start Screen don't click anything, just type "SQL Server" on your keyboard. You will notice that the search input zone took your request automatically. At the bottom of the search results, you will see the SQL Server 2014 Managment Studio link. Click on it.
SQL Server 2014 Management Studio is openning...
All the connection parameters are automatically detected... So you just have to click to connect...
You, then, can check that the SQL 2014 Database Engine is working properly, and that you are able to see the Masters databases:
We are now finally able to install SharePoint 2016
First, here is the link to download the SharePoint 2016 preview... Start downloading the package on your host machine (your real computer)...
Don't close the download page because there is the product key of the SharePoint 2016 evaluation on it, or take care to back-up the product key before closing the page.
When it's done, mount the .iso image just as we did for the SQL 2014 Server .iso image previously:
Using the start menu, access to the "This PC" folder and locate the mounted .iso image for the installation of SharePoint 2016, and double click it.
Choose the HTA option for opening the SharePoint 2016 installation menu
Before launching the SharePoint tools be sure that your virtual machine can access the Internet because the tool will download a large amount of softwares. The SharePoint 2016 installation menu is opening... Click on install softwares prerequisites
First the SharePoint 2016 product preparation tool is summarizing the actions to be done...
Accept the licence terms...
The prerequisites are downloaded and installed by the SharePoint 2016 product preparation tool...
Finally, as we had properly configured the server, the prerequisites installation is successful. But you have to restart the server.
After restarting the server, configuration is definitively successfull.
Click on finish to close the SharePoint 2016 Products Preparation Tool. We are now really going to install SharePoint 2016.
Go back to the main SharePoint 2016 installation menu. This time click on "Install SharePoint Server".
Accept the license terms
Copy and paste the product key that was in the SharePoint 2016 preview download page.
Then, let the next config as it is since we have only one drive within our server...
The SharePoint 2016 binaries are the installed on the server...
At this point you can notice, that, on the server, the 14 and the 16 hive has been created. The 16 is for SharePoint 2016. The 14 seems to allow SharePoint 2010 to run on a SharePoint 2016 Farm. I will check this point.
As I don't see 15 folder, I imagine that you can completely run SharePoint 2013 within the SharePoint 2016 "16" folder... to be verified also...
And the SharePoint dll are in the new GAC (c:\windows\microsoft.net\assembly
If we had activated the Domain Controler Role within our server we could have an Active Directory and could follow the installation with the SharePoint wizard. But as we are using only one account (Administrator) that is a local account, if we try to create a SharePoint Farm referencing this account, we will have the following exception:
Local account should only be used in stand alone mode
The workaround is to use a shell instruction. so use the start menu and when arriving on the start screen type "SharePoint", in order to display all the SharePoint programs, and locate the SharePoint 2016 Management Shell. Click on it to open a command prompt...
Now it is the little touchy part for non technical people you have to type a command to create your SharePoint Farm :
psconfig.exe -cmd configdb -create -server sp2016-local -database SharePoint_Config -user Administrator -password YOUR password -passphrase P@ssw0rd -admincontentdatabase SharePoint_AdminContent -localserverrole SingleServerFarm
If you have followed this tutorial carefully and named the computer as I did, the only diference between your command line and mine is the Administrator account pasword. If your server name is different you will have also to update the server name.
Here are the screens you should obtain after executing the command :
After that, you will notice that the databases have been created:
Internet Information Services has been configured successfully also:
and same thing for the server services dedicated to SharePoint :
That is to mean: you have a SharePoint Farm running on your Server. Last thing to do: enable the SharePoint Central Administration to administrate the Farm and create new sites, new content, etc...
Using the Start Screen of the server, type "SharePoint" to locate the SharePoint Products Wizard and launch it. The wizard detects the Farm we have just created.
Click next, and provide a number easy to remember for the port of the Central Admin Site (I always use 55555). Let the NTLM option checked.
Then, the wizard summarizes your choices...
Launch the wizard to provision the SharePoint Farm Central Administration Site...
You are warned that the configuration was successful
And when you close the window, the Central Administration Site is called... and you have first to answer to the participation at the Improvement Program
Then, you are asked for using a wizard to configure the services. Don't use it and cancel the wizard.
When closing the wizard the SharePoint 2016 Central Administration Site is finally displaying...
Don't mind for the health analyzer issues. It is normal because we didn't follow the best practices since we wanted to quickly mount a trial SharePoint environment.
You have anyway installed SharePoint 2016 on premises successfully. Well done!
Using the "New" button of the Ribbon diplay the pop-up for creating a new web application.
On the pop-up, let all the automatic settings except the content database name
When the Web Application is created this pop-up is displaying:
When you close it you can notice that the Web Application has been created succesfully.
Just populate the site name and choose your Admin account as the Site Collection primary administrator.
You are then warned that the Site Collection has been successfully created...
And when you click the new Site Collection link you are redirected to its landing page.
You can now be sure that your SharePoint 2016 installation is working properly.
- non technical person (trainer, non technical IT pro, etc.) to be able to mount a trial environment.
- All the installation will be on a single virtual machine
- this tutorial will use the trial versions of the products (OS, SQL Server) so as trainers or developers to be able to build a SharePoint 2016 environment for free.
- I will use the most simple features so as the installation to be as fast and simple as possible (sort of installation for dummies). For example, I will use the Administrator local account for installing all the softwares and to be the only service account (that is a very bad practice for a real environment)
1 - Deciding for the best configuration
If you check the post of Bill Baer, the SharePoint Senior Product Marketing Manager, that gives the recommendations, in our case, for a trial or development environment:System Requirements
Scenario | Deployment type and scale | Processor | RAM | Hard disk |
Database server running a single SQL instance | Development or evaluation installation with the minimum recommended services | 64-bit, 4 cores | 12-16 GB | 80 GB for system drive 100 GB for second drive |
--> So be sure to have a computer with at least 16 Go of RAM with 200 Go of free disk space.
Operating System Requirements
SharePoint Server 2016 is supported on Windows Server 2012 R2 and Windows Server Technical Preview. Evaluation copies of both operating systems can be downloaded from the TechNet Evaluation Center:
- Windows Server 2012 R2
http://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2012-r2 - Windows Server Technical Preview
http://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-technical-preview
SharePoint Database Server Requirements
SharePoint Server 2016 requires SQL Server 2014 for its databases. You can download SQL Server from the TechNet Evaluation Center at http://www.microsoft.com/en-us/evalcenter/evaluate-sql-server-2014. In addition SharePoint Server 2016 will support SQL Server 2016. For additional information on SQL Server 2016 see also http://www.microsoft.com/en-us/server-cloud/products/sql-server-2016/.
--> For this tutorial, I will use SQL Server 2014 , because as said before, the version of SharePoint 2016 is already a preview. I don't take the risk of mixing 2 preview products. (even if SQL Server 2016 seems to be much faster than SQL 2014)
2 - Creating the Virtual Machine
2.1 - Download Windows Server 2012 R2 Evaluation
Start downloading a 180 days evaluation version of Windows Server 2012 R2. You will have to sign in to obtain. Choose the ISO option
It is better to use an English version for an evaluation purpose so as to be sure to have the system messages in English. There is much more informations in the search engine for English messages.
To the question do you want System Center components included, choose "No".
Then, you can finally download the .ISO file of Windows Server 2012 R2
2.2 - Creating the Virtual Machine
Download the VMWare player trial versionWhen VMWare is installed, open it and Click the "Create New Virtual Machine" button.
Then, add the reference to the .iso file of the Windows Server 2012 R2 OS you have downloaded. VMWare recognises the OS version automatically.
Then specify the Virtual Machine name and location.
Microsoft recommend 80 Go for the main hard disk. I let the automatic sizing set by VMWare regarding Windows Serve 2012 R2, because, if needed I know I can expand my disk. I chose to store the disk within a single file because it is better in matter of performances.
Then, VMWare is summarizing your first settings but you have to add some more regarding the hardware configuration.
First, start setting the memory as recommended by Microsoft, so at least 8 Go. (Of course it depends also on the amount you have in your Host Machine. Your host machine is your real computer).
Choose the same number of processors than in your host machine :
A good way to know the number or Cores is to open the task manager, and in the "Performances" tab, check the number of graphes... I have only one block so I have a mono Core in my host machine.
Deactivate all the devices you won't use, sound card, printer and so on. You don't need them for a trial or development environment...
Then, you can start installation. If you have a message 'You have an incorrect version of driver "vmci.sys"', open the machine .vmx file located in the virtual machine folder, locate the vmci0.present parameter and set it to FALSE.
The installation is starting loading the files...
Then, you are asked for chosing the langage settings...
Then you have to choose the type of Windows Server 2012 R2 OS you want... Choose a standard with GUI, and accept the License terms
After that you could choose the drive where install the OS but in our case as there is only one disk, we have no choice...
After having performed all that settings the installation is really starting...
It lasts roughly 10 to 20 minutes depending of the capacity of your host machine... Finally you are asked for setting the password for the Administrator account. Note : to do a ctrl Alt Del for a VMWare machine you have first to click on it then type ctr Alt and inser. You can also use the VMWare "Player" menu where this action is available.
When your Admin password is set, the system asks you to sign in.
and you finally can reach the machine with Windows Server 2012 R2 installed.
As your virtual machine will host SQL Server and SharePoint, you don't need to join a network, so click "No" to the right screen. So, it is done, you have a virtual machine with Windows server 2012 R2 on it, we just have to install SQL Server 2014 and SharePoint now, but before, let's perform some settings to improve the user experience of this trial or development environment and also preparing the installation of the other softwares (SQL Server 2014 and SharePoint 2016).
3 - Configuring the Windows Server 2012 R2 OS
3.1 - Installing VMWare tools
VMWare tools gives to the Virtual Machine great features like resizing the virtual machine screen properly to adjust it to the screen fo your host machine and enabling the copy-paste feature from the virtual machine to the host one and vice & versa, so install the tools. You can start the installation using the "Player" menu.
Then you have to give to the install program the authorization to run, on the next screens, just click "ok".
When the installation is finished you are asked for rebooting the vistual machine, just do it.
When the machine has restarted just minimize it and maximize it and you will notice that the virtual machine screen is now adjusting automatically to the host machine screen. Morevover, If you use the full-screen feature, you will have an experience as if the Windows Server 2012 R2 has been installed on your host computer!
3.2 - renaming the server
As you can notice, the server name is not friendly, so click on it to rename the serverChange the description and the server name (don't use a too long name since it is limited by the BIOS policy)
When it's done you are warned you will have to restart the server.
You will asked to "Restart now" when you will have clicked on the "Apply" button of the first modal window. Just do it
When your server are restarted you will notice that its name has changed...
3.3 - Disabling the Internet Explorer Enhanced Security
For a best experience using Internet Explorer disable enhanced security. Locate the link button. Set everything to off.
When refreshing the dashboard you will notice that IE enhanced security has been set to Off.
3.4 - Disabling the Firewalls
Because we use a single virtual machine for trial or development matters, we can disable the firewall. Disabling the Firewalls will improve performances, and, furthermore, we won't have a warning regarding Firewall when installing SQL Server 2014. Thus, navigate to the Server Manager page and locate the "Windows Firewall" link button.
Click on it and on the opening pop-up, disable the Firewalls.
You will warn that it is not the recommended configuration, but, just don't care, our environment is for trial or development matters.
When closing the Firewalls configuration pop-up, you will notice that Firewalls has been deactivated properly.
3.5 - Adding the Microsoft .NET Framework 3.5 feature
We need .Net Framework 3.5 feature activated on the Server because SQL Server 2014 requires it. Let's activate this feature. Go to the Server Manager Dashboard, and click on "Add Roles or Features"Pass the warning screen... and the two next ones
Then, select the Feature menu and check the Framework 3.5 option.
Start the activation of this feature...
You will obtain this screen when it is complete.
3.6 - Installing Microsoft the Service Pack 1 of the .NET Framework 3.5
SQL Server 2014 requires this Service Pack. Navigate to the Microsoft Download Center page for downloading this Service Pack 1
Download the package...
when it's downloaded run the installation. If it is not running, don't mind, it means that the feature on the server is already complete.
We can proceed to the installation of SQL Server 2014
4 - Installation of SQL Server 2014 on Windows Server 2012 R2
4.1 - Downloading the SQL Server 2014 SP1 180 days evaluation
Navigate to the Technet page to downlod the SQL Server 2014 SP1 180 days evaluation. You will be warned that you have to sign in.
Take care to choose the ISO file
and the 64bit type version of SQL Server 2014 + SP1
For a matter of testing, it is always better to choose the English products...
Then you finally can proceed to the download...
4.2 - Mounting the .iso image of the SQL Server 2014 SP1 on the Windows Server 2012 R2 virtual machine
When your .iso file is downloaded, mount it as the d:\ drive of your virtual machine. Start navigating to the CD settings via the "Player" menu; then, browse for the SQL Server 2014 installation .iso file
When the .iso image is mounted click the Windows Server 2012 R2 start button.
Then, locate the "This PC" button and click on it.
You can see that the .iso image of the SQL Server 2014 + SP1 has been properly mounted.
We are now ready to install SQL Server 2014 + SP1
4.3 - Installing SQL Server 2014 SP1 on Windows Server 2012 R2
So, double-click on the SQL Server 2014 .iso image. The SQL Server 2014 installation wizard is launched. Then click on the installation menu item
And the first item of the new screen : New SQL Server stand-alone installation...
Pass the license screen since we use an evaluation version
and the license terms...
Then enable the automatic checking for updates...
Check that the first rules are passed
Let the first option checked for the next screen
Regarding the features, for SharePoint, you only need two : Database Engine Service and Management Tools - Basic
Pass the Feature Rules
Let the default option for the next screen. Don't use a named instance because it will be more complicated to install SharePoint with a named instance.
Let the automatic service account settings
Enable Mixed mode that allows you to use the "sa" account to connect. Set a complex password, like P@ssw0rd, if not you won't be able to pass this screeen. It is very useful sometimes to have this account in case of connection problem to SQL Server. Use the administrator account of the machine to be the administrator account of SQL.
SQL intallation wizard, then, summarizes your choices...
Then, launch the installation...
You should obtain this screen when installation is complete :
4.4 - Checking the Installation of SQL Server 2014 SP1 on Windows Server 2012 R2
We are now going to check if SQL Server has been installed properly. Click the Window Start button and when arriving in the Start Screen don't click anything, just type "SQL Server" on your keyboard. You will notice that the search input zone took your request automatically. At the bottom of the search results, you will see the SQL Server 2014 Managment Studio link. Click on it.
SQL Server 2014 Management Studio is openning...
All the connection parameters are automatically detected... So you just have to click to connect...
You, then, can check that the SQL 2014 Database Engine is working properly, and that you are able to see the Masters databases:
We are now finally able to install SharePoint 2016
5 - Installing SharePoint 2016 on Windows Server 2012 R2
5.1 - Downloading and mounting the .iso image of SharePoint 2016
First, here is the link to download the SharePoint 2016 preview... Start downloading the package on your host machine (your real computer)...
Don't close the download page because there is the product key of the SharePoint 2016 evaluation on it, or take care to back-up the product key before closing the page.
When it's done, mount the .iso image just as we did for the SQL 2014 Server .iso image previously:
Using the start menu, access to the "This PC" folder and locate the mounted .iso image for the installation of SharePoint 2016, and double click it.
Choose the HTA option for opening the SharePoint 2016 installation menu
5.2 - Running the SharePoint 2016 Products Preparation Tool (prerequisites installation)
Before launching the SharePoint tools be sure that your virtual machine can access the Internet because the tool will download a large amount of softwares. The SharePoint 2016 installation menu is opening... Click on install softwares prerequisites
First the SharePoint 2016 product preparation tool is summarizing the actions to be done...
Accept the licence terms...
The prerequisites are downloaded and installed by the SharePoint 2016 product preparation tool...
Finally, as we had properly configured the server, the prerequisites installation is successful. But you have to restart the server.
After restarting the server, configuration is definitively successfull.
Click on finish to close the SharePoint 2016 Products Preparation Tool. We are now really going to install SharePoint 2016.
5.3 - Installing the SharePoint 2016 binaries
Go back to the main SharePoint 2016 installation menu. This time click on "Install SharePoint Server".
Accept the license terms
Copy and paste the product key that was in the SharePoint 2016 preview download page.
Then, let the next config as it is since we have only one drive within our server...
The SharePoint 2016 binaries are the installed on the server...
At this point you can notice, that, on the server, the 14 and the 16 hive has been created. The 16 is for SharePoint 2016. The 14 seems to allow SharePoint 2010 to run on a SharePoint 2016 Farm. I will check this point.
As I don't see 15 folder, I imagine that you can completely run SharePoint 2013 within the SharePoint 2016 "16" folder... to be verified also...
And the SharePoint dll are in the new GAC (c:\windows\microsoft.net\assembly
5.4 - Creating the SharePoint 2016 Farm
If we had activated the Domain Controler Role within our server we could have an Active Directory and could follow the installation with the SharePoint wizard. But as we are using only one account (Administrator) that is a local account, if we try to create a SharePoint Farm referencing this account, we will have the following exception:
Local account should only be used in stand alone mode
The workaround is to use a shell instruction. so use the start menu and when arriving on the start screen type "SharePoint", in order to display all the SharePoint programs, and locate the SharePoint 2016 Management Shell. Click on it to open a command prompt...
Now it is the little touchy part for non technical people you have to type a command to create your SharePoint Farm :
psconfig.exe -cmd configdb -create -server sp2016-local -database SharePoint_Config -user Administrator -password YOUR password -passphrase P@ssw0rd -admincontentdatabase SharePoint_AdminContent -localserverrole SingleServerFarm
If you have followed this tutorial carefully and named the computer as I did, the only diference between your command line and mine is the Administrator account pasword. If your server name is different you will have also to update the server name.
Here are the screens you should obtain after executing the command :
After that, you will notice that the databases have been created:
Internet Information Services has been configured successfully also:
and same thing for the server services dedicated to SharePoint :
That is to mean: you have a SharePoint Farm running on your Server. Last thing to do: enable the SharePoint Central Administration to administrate the Farm and create new sites, new content, etc...
5.5 - Provisioning the Central Administration Site for the SharePoint 2016 Farm
Using the Start Screen of the server, type "SharePoint" to locate the SharePoint Products Wizard and launch it. The wizard detects the Farm we have just created.
Click next, and provide a number easy to remember for the port of the Central Admin Site (I always use 55555). Let the NTLM option checked.
Then, the wizard summarizes your choices...
Launch the wizard to provision the SharePoint Farm Central Administration Site...
You are warned that the configuration was successful
And when you close the window, the Central Administration Site is called... and you have first to answer to the participation at the Improvement Program
Then, you are asked for using a wizard to configure the services. Don't use it and cancel the wizard.
When closing the wizard the SharePoint 2016 Central Administration Site is finally displaying...
Don't mind for the health analyzer issues. It is normal because we didn't follow the best practices since we wanted to quickly mount a trial SharePoint environment.
You have anyway installed SharePoint 2016 on premises successfully. Well done!
6 - Testing the SharePoint 2016 installation on Windows Server 2012 R2
6.1 - Creating a new Web Application
On the SharePoint 2016 Central Administration locate the "Manage Web Applications" link button and click on it.Using the "New" button of the Ribbon diplay the pop-up for creating a new web application.
On the pop-up, let all the automatic settings except the content database name
When the Web Application is created this pop-up is displaying:
When you close it you can notice that the Web Application has been created succesfully.
6.2 - Creating a new Site Collection
Close the Pop-Up, go back to the Central Administration Home page and this time click on the "create site collections" link. Just populate the site name and choose your Admin account as the Site Collection primary administrator.
You are then warned that the Site Collection has been successfully created...
And when you click the new Site Collection link you are redirected to its landing page.
You can now be sure that your SharePoint 2016 installation is working properly.
