SharePoint 2013 RTM!!!

I ran across this article yesterday, and was surprised to see this…

“Microsoft announced on Thursday that its next-generation Office  solutions and other “2013”-branded products have reached the release-to-manufacturing  (RTM) milestone.”

This portion of the article was very interesting to me as well,

Office 365 Service  Update Office 365, Microsoft’s service that delivers hosted  versions of Exchange, SharePoint and Lync, along with a premises-installed Office  Professional Plus, is also getting new capabilities. The Office 365  improvements happen a bit differently from the RTM releases because Microsoft  continually updates its Office 365 services through various “service  update” releases. The next service update with the new 2013-branded  capabilities will start becoming available to Office subscribers in November.

Developers building on Office 365 could see a bit of downtime  during the service update transition period, according to a  Microsoft blog post. Developer tools, including Napa, will get an upgrade  too at the time of the service update.”


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.