In this session, the star of the party, SharePoint Server 2013 gets installed. It is important to download the latest version from Microsoft.com, especially if RTM has been released, as it is often difficult to upgrade from a release candidate to RTM.
The steps shown in this article are unique to the environment, VMWare, and the errors and version installed at the time of this writing, therefore, take care to adjust or retry as needed based upon possible differences in the software and environments utilized. Furthermore, this article does show much with respect to security, the logged-in user, and provides explanations with respect to accounts but it is important to not transpose these recommendations to a production environment
Switch to VMWare and mount the SharePoint 2013 ISO.
Switch back to Remote Desktop with SPSetup logged in and run the installer.
Close the window and run prerequisiteinstaller.exe.
Install SharePoint Server 2013 Prerequisites
Log back in as SPSetup and re-run the prerequisite installer.
Install SharePoint Server 2013
Reboot the server and log back in as SPSetup.
Ensure the current user is SPSetup.
Enter the product key.
If it is a trial license then Microsoft will have sent an email containing the trial key.
Uncheck the box to run the SharePoint Products Configuration Wizard and close the dialog box.
Configure SharePoint 2013
Run the SharePoint 2013 Products and Configuration Wizard from the Start Menu.
Note that instead of referencing the current machine, the database server references the spsql alias created during the SQL installation.
The SQL server is not available.
In this test, the SQL server had not started after the reboot. If this occurs, locate Services and manually start the service.
The installation now advances if the SQL Server is available. Enter a passphrase.
Switch to SQL Server Management Studio and connect to the SQL Database Server.
Right mouse key on the database server.
In the server properties window, select Advanced and specify a value for Max Degree of Parallelism to equal or be greater than the number of CPUs for this virtual machine (this may range from 2-4 depending on the number of CPUs).
User does not have appropriate rights. Log back into the server as Administrator or an Enterprise Administrator (since we provide Enterprise Administrators with ServerAdmin rights on the SQL Server).
(Screenshot below while logged in in as ExpertAssist\Administrator in a different session – note that the screenshot is from VMWare, not Remote Desktop)
Set the Max Degree of Parallelism as a user that has serveradmin rights on the SQL Server.
Switch back to the SPSetup Session and restart the SharePoint 2013 Products and Configuration Wizard.
Switch to SQL Server Management Studio and delete the WSS_Config database, which is the core to any SharePoint server farm.
Return to the SPSetup session and complete the wizard.
Login to Central Administration
Login to Central Administration (this might not work).
The SPAppPool runs SharePoint so it should have access. Unfortunately, it appears that IIS is unable to authenticate the SPAppPool user when you are attempting to login on the server itself.
Try logging in as SPSetup after reopening the browsers.
Also try http://localhost:8080 – it is good to make sure default localhost access is available.
Note that using http://localhost:8080 will automatically send the current users credentials to IIS, thus the user is signed on without having to enter credentials. In this case, because SharePoint was installed as SPSetup and because the current logged in user is SPSetup, the browser automatically logs the user in as SPSetup.
It is important to login remotely from the host as well. Try logging in to http://sp2013:8080 instead.
Note that 8080 was the port specified for Central Administration when installing SharePoint.
Try from the host (in this case Chrome is used to make it clear we are logging in from the guest). We can’t use localhost in this case because that would not point to the SP2013 server. Instead, use http://sp2013:8080.
If the incorrect credentials are used, SharePoint 2013 has a tendency to remove passwords. To force a logout, use http://sp2013:8080/_layouts/15/SignOut.aspx by appending _layouts/15/SignOut.aspx to the URL the close and reopen the browser.
Update Farm Administrators
Before moving forward, users must be added to the farm’s administrator group. Click on Manage the farm administrators group.
During the creation of the new farm, the Application Pool (ExpertAssist\SPAppPool) and the Setup Account (ExpertAssist\SPSetup) are automatically added to the farm administrators group.
Add the appropriate users.
In this lab “Enterprise Admins”, which is a built-in AD security group will be added. In addition, the user ExpertAssist\Ulysses is added.
Add ExpertAssist\Ulysses, ExpertAssist\SPAdmin, and ExpertAssist\Enterprise Admins (SPSetup could be removed at this point).
Hint: click Alt+K to quickly complete a user’s name.
Ulysses Ludwig is a SharePoint architect with over 16 years in the IT and computer industry. Ulysses' primary focus is SharePoint but he dabbles in the latest web technologies and likes to develop software in his spare time.
While the previous articles in this series cover the installation and configuration of all major software components that support SharePoint 2013, including SharePoint 2013 itself, this article covers...
In this article, SharePoint 2013 is configured for remote and local access via the URL http://sharepoint/, security and the farm administrators group is defined, and the top level site collection is created.
Probably the most critical and overlooked portion of SharePoint installation is security. Without a well thought out security strategy and a plan of action, it is likely that SharePoint 2013 will not behave...
Comment for SharePoint 2013 Lab Build – Part 5 – SharePoint Server 2013 Install