Create a Site Collection in SharePoint 2013

To create a Site Collection I am going to go to the Central Admin Home Page and
click on Create site collection under the Application Management heading.


From here I will fill in a Title and Description.  I also have the option of adding a managed path.


Next I will select the template I’d like to use and I can add site collection administrators.

Scrolling down brings me to the Quota Template drop down and the OK button.


After I click OK, SharePoint will create the Site Collection and present me with the following:


When I clicked on the link the box below appeard, and I clicked enable.  My screen shot is a little hazy.  This is asking if I want to enable the Microsoft Web Test Recorder 10.0 Helper add-on.


After clicking enable I am presented with my new Site Collection.



Quick Tour of my Office 365 Developer Site

Last week I happened upon this links, and took MS up on their offer to sign up for a development site.

After setting up my account, I received an email with my login information, and logged in.  I’m most interested in SharePoint, so the first thing I clicked on was sites.

I was presented with a pop up that asked if I’d like others to be able to see my newsfeed, I clicked yes and was presented with this screen:

After a bit of waiting I clicked on Check and was taken to my new My Site

Next I clicked on Sites and was presented with this screen.

When I clicked on the Public Website Tile I was taken here:

When I clicked on Team Site Tile I was taken here:

Stay tuned for more blogs about my Office 365 Developer site.

Create a Web Application in SharePoint 2013

From Central Admin click on Manage web applications under Application Management.

In the ribbon click New

I’m going to choose to rename the IIS web site, but this is really just up to the user.  In my case there is no need to allow anonymous access.  I’m also not using SSL.

Here comes something new.  I only have the option to select a Claims Authentication Type instead of either Claims or Classic.  It is possible to select classic, but only via powershell.  I’m going to have to research this and write a separate blog post about it as well.  Another couple topics to look for in the future will be setting up FBA and Trusted Identity providers.  For this post I’m going to stick to Window Auth and NTLM.

So with claims comes the option for a custom sign in page.  I’m going to stick to the default for this, and I am not using a host header, so no need for a different URL although I will remove the 80.

Next I’m going to name my application pool and select my content user to run it.  I’m also going to name my database with a prefix.

I have no failover database, and don’t have much by way of Service Apps at present.  I am going to select Enable Customer Experience Improvement Program in this case because this is the preview.

After this I click OK and SharePoint politely apologizes for making me wait 🙂

From here I have the option to create a Site Collection, which I will leave for another blog post.

Setting up SharePoint 2013 Logging

From the central admin home page click the Monitoring links on the left nav

Click Configure diagnostic logging

You are going to leave the top portion of the page alone.  You are really only going to use this to change logging levels of specific or all areas when troubleshooting issues.

Make sure that Enable Event log Flood Protection is checked.  Set the logging path in the Path text box.  I’m going to leave this as the default, but in a production environment it is a good idea for logs to be written to a separate disc .  I’m also going to leave the Number of days to store log files at 14.  You are going to want to limit this, but in production it is recommended that you backup the logs, so that they can be researched if needed.  I’m also going to click the restrict Trace Log disk space usage check box and set the max to 2 GB.  This setting really depends on the disc that you are writing your logs to.  After all these settings are sorted out I will click OK and this portion is complete.

I will be returned back to the Monitoring Page where I will click on Configure usage and health data collection

From here I will click the enable usage data collection check box, and leave the Events to Log settings set to default.

I’m going to leave my log file location set to default, but the same thing applies here as with trace logging, if you are in production this should really be a separate and if possible dedicated disc.

Next I’m going to check my logging schedules by clicking on the provided links.     These both just bring you to a list of jobs that are run as part of the Health Data Collection and Log Collection Schedule.  You can changes this if you want, but I will leave mine as default.

Next I get the option to name my database server.  I personally take advantage of this.  I like to add a prefix to my database names, so that they are all grouped together when I open SQL Server Management Studio.  In a past life I was a DBA which makes me appreciate this sort of thing.

Clicking on OK will create the database and concludes the logging set up for SharePoint 2013

SharePoint 2013 Training Resources

Just as they did with SharePoint 2010, Microsoft has created several training videos for SharePoint 2013.

Developer Training Videos:

IT Pro Training Videos:

This site has a pretty handy newsletter that has links to plenty of useful resources




Creating Managed Accounts in SharePoint 2013

Creating Managed Accounts in SharePoint 2013 Preview is done exactly the same way it was done in SharePoint 2010.

Open Central Admin and click Security


Under General Security click on Configure managed accounts.


Click Register Manager Account.


Enter the user account you’d like to add and click OK.



Repeat these steps to add the rest of your managed accounts.

If you have just configured your farm and need/want to add your farm account in place of your setup account, go back to the Central Admin home page and click Configure service accounts under Security.


Select Farm Account in the top drop down, select the account you want to make your farm account in the checking box on the bottom and click OK.


If you end up with a “Cannot Connect To Configuration Database” error you may have entered the incorrect password when you created the managed account, and will need to run this to fix it.

stsadm –o updatefarmcredentials –userlogin DOMAIN\username –password $password$

I got this stsadm tip from

Installing SharePoint 2013 Preview

Yesterday I was answering questions on the SharePoint 2010 forums, and much to my surprise, noticed a 2013 tab in the navigation.

Clicking on the tab brought me here:

Where I found loads of information AND a link to download the SharePoint 2013 Preview.  I went ahead and started downloading the preview right away and began reading and watching videos about SharePoint 15.

After downloading the preview I ran windows update to bring the 3 servers in my virtual farm up to date.  My environment is made up of a Domain Controller, a SQL Server and a SharePoint Server.  All of which are running Windows Server 2008 R2

Today I went through the steps to install the preview;

First I installed the Eval Version of SQL 2012 which I downloaded from:

Here are some install instructions:

Next I set up my service accounts.  I created a spsetup and spfarm account and gave them both dbcreator and security admin roles on my database.

As I always do I created a SQL Alias with which to connect to the SQL Server.  I also created the firewall rules needed.  The resources below cover this in detail.  Ignore the fact that the firewall rule post is about MOSS, this makes no difference given that the firewall rules are all you care about.

Make sure that your SQL Server’s firewall lets in traffic on ports 1433 and 1434.

After completing the steps above I was ready to begin.

I had the option to either burn the image I downloaded, or use Virtual CloneDrive or something similar to mount the image.

I used Virtual CloneDrive and browsed to the drive that the the image was mounted to and clicked on the installer.  Doing so resulted in the screen below appearing:

From here I clicked install software prerequisites.  The prereqs installer began to run, but after a little while I received the error message pictured below:

This began a fairly long troubleshooting session.  At first I just tried to rerun it, but I just received the same error.  Next I started searching the internet for the download, so I could just download it and move on.  This is when I learned that Windows Management Framework CTP2 was no longer available because the RC had been released, so that answered that.

I found the download link for the RC,

I proceeded to download this version, but instead of it installing, I was presented with this error box

After doing some digging and downloading the update over and over again it eventually worked.

I then ran the prereqs installed again and it moved on, but I ran into another error when it attempted to download SQL Server 2008 R2 SP1 Native Client.  Luckily, this time I just had  to click retry to solve that.

The prereqs installer continued on happily from this point and completed.

I restarted my machine and was then ready to install SharePoint 2013.

Side note: If you have ever install and configured SharePoint 2010 or 2007 you’ll notice that this all looks very similar.

The first thing I needed to do was enter the product key that Microsoft sent me when I downloaded the trial.

Next I had to accept the license terms, select the appropriate server type, and click install now.

Upon completion of the install I was presented with the screen below.  At this point I had the option to start the config wizard,  or run through the steps above for the other SharePoint servers in my farm.  I only have one SharePoint server, so I went ahead and let it open the config wizard for me.

Had I decided to run this later, the config wizard is accessible by opening the start menu, selecting all programs, selecting SharePoint 2013 Products, and clicking on the SharePoint 2013 Products Configuration Wizard.

When the Configuration Wizard opened I was presented  with this screen.

I clicked yes when this pop up appeared.

I selected the appropriate option below.

I entered the database server and set up account information.

I entered a passphrase, and noted it so I can add servers to my farm later.

I selected the appropriate options.

I made sure everything was entered properly and started the configuration.

Upon completion of the configuration I was presented with a screen that indicated that all went well and let me know that it would open Central Admin when I  closed the window.  My apologies for the lack of a screen shot.

When Central Admin first opened I was given an option to be part of the customer feedback program or something along those lines.  Once again I apologize for the lact of a screen shot.

Next I was presented with the option to allow another wizard to configure my farm further, or chose to do this myself.  I personally like to do this myself since that is how it should be done in a production environment.

Upon making a selection I was presented with Central Admin

Stay tuned for more blog posts about SharePoint 2013