By Eric Harlan
Published: July 12, 2012
Updated: July 15, 2012
Welcome to SharePoint 2013! For months MVPs, Tap customers and Microsoft employees been chomping at the bit to finally hit the “publish” button on their blog and welcome a whole new era of a product most of us making our sole living from. It’s an exciting time and its happening right in front of our eyes.
Each version I’ve published versions of this blog post for SharePoint 2010 and I’d like to do the same for SharePoint 2013 here and now. This will be an on-going post just like the rest were; I’ll start off with core install and functionality and as time permits I’ll be adding additional posts such as this one on How to Migrate from SharePoint 2010 to SharePoint 2013 very soon. If you are familiar with properly installing SharePoint 2010, quite honestly not much has really changed. There is more functionality obviously but at the core most of the steps are the same. If you need a refresher check out my post on “How to install SharePoint 2010 and Manually configure Service Accounts”. Lets first talk about hardware and software prerequisites. Hardware for WFE’s and App servers is pretty much like 2010: Disk – 80 gigs on system or more Proc – 64 bit and 4 cores Ram – 4 for dev and 8 for production (AT A MINIUM please don’t put 8 gigs on your production WFE/App servers) Hardware for SQL: Disk – 80 gigs on system or more Proc – 64 bit and 4 cores for dev, 8 cores or more for prod (the size of your farm dictates how many procs) Ram – 8 gigs for dev and 16 for prod (again amount of ram is dictated by the complexity of your environment) Software requirements that get installed by the prereq tool: Microsoft .NET Framework 4.5 Windows Management Framework 3.0 CTP2 Application Server role Web Server (IIS) role SQL Server 2008 R2 Native Client Windows Identity Foundation (KB974405) Microsoft Sync Framework Runtime v1.0 SP1 (x64) Windows Server AppFabric Microsoft Identity Extensions Microsoft Information Protection and Control Client Microsoft WCF Data Services 5.0 CU Package 1 for Microsoft AppFabric 1.1. for WIndows Server (KB2671763 Service Accounts: The saying goes there is always someone out there that will say “I’ve been running SharePoint for 8 years on the same Service Account and I’ve never had any issue.” Don’t be that person, its dangerous its silly and takes 30 mins of setup and almost zero time in maintenance to setup the proper service accounts. It will save you potentially WEEKS worth of troubleshooting and countless nights on call. Just please setup the service accounts correctly and count your blessings. If you need more of a reason to do this, have a conversation with someone who tried troubleshooting a permissions issue in their farm with only a single service account. Service accounts have pretty much stayed the same at least in terms of the core ones. You can find a good list of those here SharePoint 2010 Service Account Reference Guide. As things progress I’ll update that post to represent 2013 specific. So let’s get to the getting.
The Key available on the MSFT download site is:
DECISION POINT: Decide to run the wizard at this step. There are a few important decisions to make before deciding. First thing to decide, do you want to run each Service application (or any) under its own service account. For more information about SharePoint 2010 Service accounts go here http://technet.microsoft.com/en-us/library/ee662513.aspx If you choose to run the wizard you may choose which service accounts run under any given previously setup service account. HOWEVER, if you deselect some applications (such as search) you will be able to re run the wizard to create them. The only caveat to this is that you will not be able to select an alternate service account for which to use for said Search Service Account (or any other that you wish to add after the fact). The same service account you used to create the initial Service Accounts will be selected and “grayed out” and you must use it if you run via the wizard. The alternative is to NOT run the wizard and configure the service applications manually. In the guide below we have run the wizard for some two service applications State Service and Health these are the only two where it is “kind of” ok to run under the admin account. We then configured Excel Services and User Profile etc. Best practice is typically to create all the service applications manually. Use what you need and isolate via service accounts and proper permissions. The only reason folks will use the wizard to create the State Service service application is because it is not available to create in the “Manage Service Applications” page. You must create this using PowerShell if you choose not to use the wizard. In my opinion, either is ok.
You’ll notice throughout the interface that SharePoint 2013 has got a lot more polite.
You’ll notice that in my example I choose to skip creation of the first Site Collection. This step is up to you, I usually choose to go through the hard part of getting my service applications setup and running correctly before I create the default site collection because it doesn’t tempt me to go play around it also lets me set my managed accounts correctly. On default when you install SharePoint 2013 (2010) on setup, SharePoint configures the first web application (assuming you use it) where your default site will live. If you don’t want to use the account created to run the application pool for that web app, you’ll need to go back and delete that web application and reconfigure. Just less wasted time.
Now back to the main Central Administration page we’ll click on Security > Configure Managed accounts
You’ll notice my default install account is already a managed account. I want to use another account to create my web app for my default site so I’ll click “Register Managed Account” Enter the account you want to use and if you want to use the password change feature.
Good to go.
Ok lets get down to business and start creating our Service Applications. Go to Application Management > Manage Service Applications.
Under “NEW” select Secure Store Service. (Notice there is no “State Service” again you need to create this via PowerShell or via the configuration wizard)
Enter your App Name. The database instance will be automatically filled in. And give your database name something easy to remember don’t leave the GUID in the name as you see in this photo.
If you have already configured your fail over server you can enter it here. Remember just designating a fail over server doesn’t mean your SharePoint 2013 environment/Service App will fail over, it needs to be configured on the server itself as well. Enter the name of your app pool and choose a managed account to run the app pool under.
We need to generate our key for later use. Click on your secure store service application (the link itself, not the proxy)
Click the “Generate New Key” icon
You will be asked to enter in your Pass Phrase that you used to setup your farm. Then you’re golden.
Next lets baseline configure Search. Go to Manage Service Applications > New > Search
Same as before choose your name and managed account you prefer to use.
Choose your Application Pool name or reuse a previous one. Then select the Managed Account you would like to use.
Next select the application pool you want the Search Query and Site settings web service to run under.
Notice you have something a little new in the Search Service Application architecture. More on that later.
You should be pretty familiar with this view. Not a whole lot has changed in terms of managing search however there are some new features. More on that later.
Ok what I don’t have shown in this screen shot is if you want to recreate your root web application that your default Site Collection will live under, you will need to go to “Application Management > Manage Web Applications > delete root web application. In this case I'm going to keep my default and create the site collection I want to live there now. The reason I do this now will be made apparent here in a second. Go to “Application Management” > “Create Site Collections”.
Add your info
Choose the type of experience you want (you can choose the 2010 FULL experience, not just a knock down version of it). I chose team site. Add the primary site collection administrator account. I don’t have a quota set, but if you are in a production environment, please setup a quote first. Your governance guide will thank me later. Hit “OK”
It will go off and do its thing and return a success message (hopefully)
Tada! Isn’t that pretty!? Ok let it be, lets get back to work.
Go back to “Application Management” > Manage Service Applications > New > Managed Metadata Service
Name your Managed metadata service, and give it a database name
Just as before fill in the above, although you want to pay special attention to the Content Type Hub field. Once you set this, you can not edit it so choose wisely. This is why I setup my new web application/site collection first. I chose my default site location. This will be the source of all my federated content types (just like in SharePoint 2010)
The feature set has stayed pretty much the same however the interface has been tweaked.
A new feature in SharePoint 2013 is the ability for translation of documents inside of the SharePoint interface. Go to “Application management > Manage Service Applications > New > Machine Translation Service
Just as before enter in the content you wish to use for configuration
Once configured you can choose which type of files the translation service will service
That is the core of SharePoint 2013 at least for now. Stay tuned for a walk through of the SharePoint 2013 User Profile Service and the Business Intelligence Center which houses Excel Services, Performance Point Services and Visio Services. Hold on to your hats, there is going to be a lot of information coming your way!
How to upgrade from SharePoint 2010 to SharePoint 2013
Submit Article 180515 Views -
View Comments (3)