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.

Comments

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 wou…

SharePoint 2013 - Setting Up External Content Type

There were earlier posts where we discussed External Content Types setup for SharePoint 2010:

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

External Content Types - Reload - Setting up for SQL Server database using SQL Server authentication - SharePoint 2010 Server

This one is about creating connection to the custom SQL Server database (External System) in SharePoint 2013.

1. Create Secure Store Service Target Application

1.1. Go to Central Administration -> Manage Service Applications -> Secure Store Service Application. Click "Generate New Key" if required:


1.2. Provide Pass Phrase:

1.3. Create "New" to create new Target Application:


1.4. Provide the name and other parameters and click "Next":

Note: It's good idea to specify "Group" for Target Application Type. In that case you would be able to manage access to the external data using Active Directory groups rather …

SharePoint 2010 Search Issue - FQDN Crawl

I have recently set up a standalone SharePoint 2010 environment.

The Web application was created with host header and the site collection is accessible from the client machines, but not internally. That was because of using FQDN to access the Web site.

The error when I tried to access site internally was similar to the one described here:

You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version

And the search returned the following error in the Event Log:

"The start address cannot be crawled.

Context: Application 'Search_Service_Application', Catalog 'Portal_Content'

Details: This item could not be crawled because the crawler could not connect to the repository."

One of the suggestions was to disable the loopback check, but that would compromise the Web server.

So what I have done was:

1. Added a binding to my IIS Web site for a different port. Let's say my Web server name is win-v7m…