Skip to main content

SharePoint 2013 Preview - Installation

Today I have got the SharePoint Server 2013 Preview and straight away prepared a virtual machine and installed it.

Here's the process:

0. Check the system requirements

My set up is Windows 2008 Server R2 4Gb RAM, standalone, Web Server role enabled, SQL Server 2008 R2 SP1

1. Install prerequisites

Run prerequisiteinstaller.exe


Click "Next" and wait till the process finished

 


After you click "Finish" the system will restart and the installation will continue.



2. Install the following hotfixes:

KB 2554876
KB 2708075
KB 2472264

3. Configure service accounts:

I used two custom service accounts: DOMAIN\sqlservice and DOMAIN\spservice. First is used to run/access SQL Server and second to run\access SharePoint

4. Run setup:

Run setup.exe


Type the Product Key and click "Continue":


Read the License Terms, accept the terms and click "Continue":


Choose where you want to install the files and click "Install Now":


Wait till the process finished to run the configuration wizard:



5. Configuration:

When SharePoint Products Configuration Wizard starts click "Next":


Click "Yes" to continue the wizard in the notification dialog:


Choose "Create a new server farm" option and click "Next":


Specify the database server and name for the configuration database and username and password of the account that will be used to connect to the configuration database. In many cases it would be the farm account:


Specify passphrase and click "Next":


Specify Central Administration Web Application port number. I normally use 10000. Also specify the authentication provider. I have chosen NTLM in this case, but in many scenarios Kerberos is required or preferred. Click "Next":


Click "Next" to confirm the settings or "Back" to change settings:



After confirmation the process will start: 


Wait till it's finished and click "Finish":


Here we go, the new looking SharePoint 2013 Preview Central Administration site! I would choose the wizard first to run through the process quickly and see what are the options and what's installed by default to compare with SharePoint 2010:


We add the new service account that is different to the configuration database account and leave the default selection of service applications that will be installed.

There are some new service applications that from the first sight didn't exist in SharePoint 2010:

App Management Service
Machine Translation Service
Work Management Service Application

Will look closer into those shortly.

Click Next:


Wait till the wizard finished:



6. First site collection:

After the wizard creates service applications it shows create site collection screen.
There are some new site collection templates in SharePoint 2013 including:


Developer Site
Community Site
Project Site
Discovery Center
Product Catalog

I have chosen "Community Site" for the new site collection, provided the administrator etc. and clicked "OK":



Site was created:


Awesome UI design! Very clear and lightweight.

Initial installation and configuration is completed:


As you have seen, the process of SharePoint Server 2013 Preview installation in case of standalone scenario is not different to SharePoint Server 2010. There is a big difference in UI though and there is presumably many new features and service applications that are new and/or improved.

Stay tuned for more posts as I move through the SharePoint 2013 Preview.
Labels:

Comments

Post a Comment

Popular posts from this blog

Setting up External Content Type for SQL Server database using SQL Server authentication - SharePoint 2010 Foundation

This post is a follow up on the issues that I have got setting up External Content Type (ECT) on SharePoint 2010 Foundation that was going to connect to remote SQL Server database for information. I cannot use my SharePoint user accounts to access SQL Server. According to the information I have discovered ECT and Business Connectivity Services are available in the SharePoint 2010 Foundation, but there are some issues if you want to use authentication methods in your external connections that are different from Windows Identity or Current User Identity. This is because there is no Secure Store Service in SharePoint 2010 Foundation which serves as an impersonation hub and is only available in SharePoint 2010 Server edition. The issues are coming from the fact that you can actually create ECT in SharePoint Designer 2010 providing just Secure Store ID and system would ask you for credentials and here you go, but when you try to use your ECT in External Lists or as a lookup columns you w
37 comments
Read more

InfoPath 2013 Preview - URL not valid error when publishing

In InfoPath 2010 there is a problem when you try to publish a Form to a SharePoint site that doesn't have root site collection. You will get an error message "The following url is not valid". It's described here:   http://support.microsoft.com/kb/981854 The solution is to create root site collection for the Web application. Same problem is with InfoPath 2013: In my situation I didn't create the root site collection initially, but used "/sites" managed path instead for all site collections. To solve the problem with InfoPath I had to create it. Used a new site template "Project Site". Will get a chance to research that too. :)  
Post a Comment
Read more

Document Sets - SharePoint 2010 - Part 1

Hi again, in this post I am going to demonstrate how set up and start using Document Sets in SharePoint 2010. In Beta version there was a little problem when working with Document Sets. You could see the discussion around it here: Document Set content type issue . Now it is fixed and I will show you how to set up Document Sets properly to also use Keywords. 1. Activate two site collection features - Document Sets and Document ID Service: 2. Select a document library settings where you want to implement Document Sets. In my case it is Shared Documents. When you have selected the settings go to Advanced settings and then allow content types management: 3. Add an existing content type called Document Set: 4. Now I want to create a new Document Set. I have a sales opportunity and I have two documents related to this sales opportunity. So first I select New Document -> Document Set command, then provide name and description and there it is: 5. To check if our Document ID
15 comments
Read more