SharePoint 2013 Administration

1 Preparing for SharePoint Installation1.1 Configure Service Accounts in ADConfiguring service accounts is done for security.

Remember the concept of "Least privilege", which is the idea of assigning only what is needed for the account to function

1.1.1 Theory: There are three main accounts to set up:

SQL Server account:

- Must de domain user

SharePoint Setup Account:

- Must be domain user- Must be local admin on all SharePoint Servers- Must have SQL login as securityadmin and dbcreator

Server Farm/Database Access Account:

- Must be domain user- Must have SQL login as securityadmin, dbcreator and db_owner (done automatically at Farm setup)- May NOT be local admin on any SharePoint Servers.

Accounts can also be created for every service, like the following:

- Application Pool Accounts- Application Pool Account for Excel Services Application- And so on… up to 16+ accounts for a simple farm are possible

Planning on multiple accounts? Plan for and set them up BEFORE installation and configuration!

1.1.2 Practical: Setting up the accountsIn AD Users and Computers, create a new account and copy it over.

SQL Server Account

SharePoint Setup User

Account

Server Farm/ Database

Access Account

All accounts have obvious names:

- Svc-sql12 – SQL Server 2012 Service Account- Svc-spfarm – SharePoint 2013 Farm Account- Svc-spsetup – SharePoint setup account- Scv-AppPool – Application Pool account

Set password to never expire inititally!

1.2 Practical: A Basic Install of SQL 2013Install SQL on a Server (2008 R2 or higher) if none exists.

The following things should be noted installing SQL:

- It WILL complain about the Firewall if enabled. This will be handled later if the Firewall is not going to be turned off.

- For Setup Role choose SQL Server Feature Installation- For Feature Selection, choose Database Engine Services and both Management Tools items- For Instance Configuration, choose Default Instance- For Service Accounts under Server Configuration, use the svc-sql12 account for both SQL Server Agent and

SQL Database Engine. - For Database Engine Configuration, do the following:

o choose Mixed Mode and enter domain password for SA password.o Select Add Current User (which is you!)

Now let it roll, apply latest Service Pack (2008 SP1 is most current) and updates to SQL Server.

1.3 Practical: Initial SQL configuration1. Open SQL Management Studio. And log on with your own account

1.3.1 Max Degree of ParallelismWe'll now set how SQL handles processes on the server by setting Max Degrees of Parallelism. For servers with more than 1 cpu, it must be changed from 0 to 1!

1. Select the server instance in SQL Management Studioand rightclick, choose properties2. In the dialogs, go to Advanced and set Max Degree of Parallelism to 1, then click Ok.

1.3.2 Setup SQL and server Permissions for svc-spsetup1. Add svc-spsetup to local admins on the server2. In SQL Management Studio, expand the serverSecuritylogins, then rightclick on Logins and choose New

Login.3. For username select svc-spsetup and under Servr Roles, select dbcreator and security admin. (leave public

checked as well).4. Click Ok.

1.3.3 Configure Windows Firewall to allow SQL Server Access1. Open Windows Firewall with Advanced Security2. Click Inbound Rule3. Click New Rule4. Choose Port, Protocol TCP, portnr. 1433, choose Allow the connection, allow Domain, Private and Public,

and name it Allow Inbound Port 1433 (SQL)

1.4 Preparing the SharePoint Servers1.4.1 Practical: Setup local admin for SharePoint Machines

- The svc-SPSetup account must be local admin on all SharePoint Machines

1.4.2 Practical: Install SharePoint PrerequisitesThis method only works for Server 2008 R2 and 2012, NOT for 2012 R2, we must install them in other ways.

1. Insert the SharePoint ISO2. Start the Prerequisite installer on the disk.3. Follow the prompts.4. Restart the Machine

2 Installing SharePoint Server 20132.1 Theoretical: Farm TopologiesSharePoint is basically composed of three server roles:

- Web Server – fast, light-weight. Can be load-balanced. Directs requests to Application Server- Application Server – runs Application services like Search, etc. Queries the Databasees. Can have Service

Applications distributed on different Application Servers.- Database Server. Can be scaled by adding additional servers or a clustering method.

Possible options:

- 1-tier deployment – web, application and SQL on same server. For development/lab testing

- 2-tier deployment – web and application on one server, SQL on 2nd server.

- 3-tier deployment – separate servers for Web, application and SQL.

Single Server deployment:

- All on one server- Meant for development and testing, not for production.- Not scalabe = cannot add additional servers!- Limited Storage – 10 GB each DB- Can only use automatically installed SQL 2008 R2 SP1 Express- No Domain Services – so no domain accounts and no User Profile Services (= no mysites and social

capabilities)

Server Farm installation :

- Individual server for the roles (thoug can all three be on one server when installed as FARM with separate SQL installation on it).

- Needs a Domain Controller- Can work with an Office Web Apps server and Exchange Server.- Scalable when needed

2.2 Practical: SharePoint Installation.Start with the SharePoint Application server (SPAPP01), insert the disk and start it:

1. On the SharePoint 2013 splash screen, choose Install SharePoint Server2. Enter Product Key in wizard3. Accept Terms of Agreement4. Choose Server type: Complete5. Click Install Now.6. After installation, select Run the SharePoint Products Configuration Wizard and click Close7. In the wizard select Create a new server farm.8. enter the Name for the database server (SQL12) 9. Enter the name for the database: SP13SharePoint_Config

10. Enter the Database Access Account name and password (svc-spfarm) (this will automatically grant it the appropriate roles)

11. Enter a passphrase twice, needed for adding additional servers later.12. Specify the port 44444 and authentication provider NTLM (Kerberos needs a running and configured

Kerberos infrastructure already to work properly!)13. Let it install

On the Web Frontend, insert the disk

1. On the SharePoint 2013 splash screen, choose Install SharePoint Server2. Enter Product Key in wizard3. Accept Terms of Agreement4. Choose Server type: Complete5. Click Install Now.6. After installation, select Run the SharePoint Products Configuration Wizard and click Close7. In the wizard select Join an Existing Farm farm.8. Enter Database, account and passphrase details9. Let it install

2.3 Initial Configuration using the Central Admin Website.2.3.1 Theroretical: Initial configuration using the WizardUsing the Wizard, we might get defaults. Manual configuration using the site or PS might be better if you know what is needed. But some services can only be configured using PowerShell if customization is needed or the wizard is not used! (Specifically the Security Token Service Application).

2.3.1.1 Service ApplicationsSome Service Applications explained:

- Access Services Application – Allows hosting of access databases in SharePoint. Access Apps are new in 2013 and built using Access 2013 Client. Allows creation, editing, updating of linked Access 2013 DBs and viewing directly in the app. Also allows Access 210 and SharePoint 201 Web Databases to be viewed, edited, imported and republished to SharePoint 2013

- Excel Services Application – Shared service used to publish Excel 2013 workbooks to SharePoint Server. Workbooks can be managed and secured according to organizational needs and shared, and be rendered as workbooks in the server.

- PowerPoint Automation Services – new in 2013. Shared service providing unattended, server-side conversion of presentations into other formats like PDF or other file formats.

- Managed Metadata Service Application – allows using managed metadata and share content types accros site collections and web applications

- User Profile Service Application – stores information about users in central location. Social Computing features use this to enable productive interactions for more efficient collaboration.

2.3.2 Practical: Initial configuration using the Wizard1. The Central Admin site starts automatically after the Configuration Wizard. If it doesn't, open it in the Start

screen2. On the Welcome screen, choose Start the Wizard to start configuration3. Select Create new managed account under Service Account and enter the details for svc-apppool. (This

makes it a managed account, allowing SharePoint to manage its settings.)4. Select services we want.5. Click Next and take some coffee (or two)6. We're now at the Create Site Collection page. Click Skip, since it will be done in an individual lesson later on.

To check Service Applications: click Application Management and then Manage Service Applications under Service Applciation. We can now see our services.

3 Farm Configuration RevisitedWe'll take a closer look to SharePoint Farm Configuration beyond the standards seen in chapter two. We'll also visit some concepts not really covered in chapter two, like managed accounts and what they are and are used for, and look closer to Service Applications and application proxies.

3.1 Revisiting the Farm Configuration WizardWhen the Farm was created back in 2.2 we ran the SharePoint Configuration Wizard, which created two initial databases, the SharePoint_Config DB (which contains the SharePoint configuration) and SharePoint_AdminContent_<GUID> database (which has the Central Admin site content). Both can be seen after installation inside SQL Management Studio.

On the SharePoint Server inside Central Administration, we have Configuration Wizards in the main list. Opening it gives us one sole wizard, the Farm Configuration Wizard.

When we're in Ca and click on Application Management, we can choose Manage Web Applications, we'll see the SharePoint Central Administration v4 web application along with any other set up web applications.

When we now open IIS Manager and look at the Web App there, we see our Central Administration site and the SharePoint Web Services site(This one should not be touched, but always running!).

If we right-click with the mouse on our CA site and select Bindings, we see which ports the site is bound to and which hostnames it looks for (port 44444 in our example without any hostname).

When we look at Application Pools, we see the application pool for Central Administration.

This application pool and site are created by the SharePoint Configuration Wizard.

When we go back in CA to Application Management and choose Manage Service Applications, we see only two service applications exist. Both are created by the wizards and can otherwise only be created using PowerShell.

We'll see more after we run the Farm Configuration Wizards again later. For now, lets klook at…..

3.2 Managed AccountsWhen we go back to CA and select Configuration Wizards, and the use Launch the Farm Configuration Wizard, we get the following:

After we click Start the Wizards, the first thing we have to do is select a service account.

It asks for an account other than the Farm Account. When we can either choose another managed account, or make an existing AD account a managed account by entering the User Name and Password here.

We'll take another approach though.

We go back to CA and click Security, where we select Configure managed accounts under General Security.

We can now Register Managed Account, which will give us the Register Managed Accounts screen seen on the next page.

Here we can add AD accounts to be Managed, meaning SharePoint can take care of account maintenance like password changes. We'll us an Application pool service account in this example: PSAppPool, but when many accounts are used for the services, they MUST be set up as managed accounts, so SharePoint can manage password changes and register those changes in SharePoint properly.

When adding a Managed Account, We can set Automatica Password Change options to comply to Company Policies:

When we apply our changes we'll see it listed as managed account:

Having the account in the list allows us to specify the current password, which will be updated in AD AND in SharePoint!

When we check out Managed Accounts, we can

open an Account and at the bottom of the page we can see which Farm Components use this account.

Back to the Wizard….

When we now go back to the Farm Configuration Wizard, we can chose our new PSAppPool Managed Account and continue the Farm Configuration:

Looking at the Services, we'll look a little deeper into Service Applications first

3.3 Service ApplicationsWe've already reviewed some of them, but we need to know a little more about service applications and their connection to Web Application. Service Applications are background processes running independently of each other. Each Service Application ha an Application Connection, called a proxy, which creates a connection point for the application. This is the invisible connection between the Service Application and the Web Application. Each Web App usually has multiple Service Applications, which creates an Application Connection Group, known as Proxy Group, which is a logical grouping of application connections.

We'll only change the following in our Wizard for now:

- Disable Machine Translation Service- Disable PerformancePoint Service Application- Disable Visio Graphics Service

Now click next and let it run. If it completes successfully we'll be quite some time later!

When It's done, we''l get the Create Site Collection page for our initial site collection as seen on the next page.

We'll enter the details as shown in the images on the next page:

Now click Ok to create the site collection. We'll look more into Site Collections later, but for now we have the Farm Configuration Wizard completed!

Now let's look into the Managed Accounts again.

When we edit the PSAppPool account and scroll to the bottom, where we can see which services are bound to this account now:

Back into CA, when we open Manage Web Applications we now also see our new SharePoint – 80 application.

Our IIS Manager now also shows the new Web Application as well as new Application Pools fpor the SharePoint – 80 web and the 13 services we registered and set up.

Under Application Management we now go to View Site Collections listed under Site Collections.

This shows the site collection we just created.

Inside our SQL server qe'll now see some more additional Databases for the different services and the WSS_Content database/WSS_Logging

database for the web application.

4 The Logical Architecture of SharePointWe'll look at the Logical Architecture of SharePoint in this lesson, including Web Applications, Site Collections, Sties, Application Pools and lists.

Let's start with the Farm (not physical, but: Logical)

4.1 What is a Farm?- The Farm is where our Web Application Lives.- It can contain up to 20 Web Applications per

Farm.

4.2 What is a Web Application?- It is the highest level component in the architecture of SharePoint (the top-tier containing everything else)- It is an IIS site that will contain SharePoint Site Collections- Web Applications are not created inside IIS (manually that is, SharePoint creates them for us)- Web Applications have their own "Application Pools"- They can be restarted independently from IIS and thus isolates content, processes, features and users (e.g.,

hosting same content in different applications with different user groups).

Let's look inside IIS now:

We see the Web Applications SharePoint created for us:

- SharePoint – 80 (the one with the default site collection from the Wizard0- SharePoint Central Administration v4

We can also look at the Application Pools here:

We see here there are application pools created for both our Web Applications. This indicates both Web Applications have their own Application Pool. This shows how Web Applications can be isolated from another using Application Pools.

Looking at our diagram:

Each Web Application can have one or more Site Collections, with a maximum of 750.000 per Farm dependent on hardware availability.

4.3 What is a Site Collection then?- A site collection is a collection of sites. - SharePoint is a web based platform comprised of

many sites. - Site collections can organize sites into logical groups.

Looking back at the diagram, we see that out top-tier, the Web Application can have one of more Site Collections, each with one or more Sites.

Inside our SharePoint Environment we can have multiple site collections, as big or small as we want. But why would we need multiple site collections while we can create sub sites in each site collection?

- Site Collections can be created for logical units, Like Production, Sales and Marketing, each with its own administrator(s), permissions, user groups, services and features.

- Managing Site Collections is easier for Administrators than managing a whole hierarchy of Sites. This way Site Collection admins can be assigned for each site collection.

- Each Site Collection can have a maximum of 250.000 Sites.

4.4 So how about Application Pools?Application Pools can have one or more Web Applications assigned to it.

There can be 10 Application Pools per Web Server

What then is an Application Pool?

- They are Separate sets of IIS Worker processes that share the same configuration and application boundaries.

- Used to isolate web applications for better security, reliability, availability and performance

- Each can run without impacting one another

- Web applications can share application pools

Let look at an example of an internet facing site on a web application. You don't want it to impact your other applications. An Application pool can be used to isolate it.

4.5 Now then, where do Content Databases fit in?when we add content databases we add the containers for the sites and their content.

Each Web Application can have one or more content databases to hold its data.

There is a maximum of 500 content databases per Farm.

What is a content database?

- Hosts all your content

- One or more can be associated with a web application

The Web Application therefore is the top level of all that SharePoint is.

4.6 Ok, but what do the Site Collections provide?Starting at the top, we have a Web Application with one or more site collections. Each Site collection has a Top Level Site (without a TL site a site collection cannot exist).

Each TL Site can have multiple sites below them (sub-sites), or Lists and Libraries. Lists contain items like tasks etc., Libraries contain Documents. These can be organized using Folders.

5 Creating Web ApplicationsWe'll now look at creating Web Applications inside SharePoint. We'll create two separate Web Applications in this lesson, one for our local intranet site and another one for the mysites.

5.1 Adding a new web applicationWe'll be using Central Administration. Even though we might have the red bar on top, there will most likely always e something SharePoint does not like so no reason to panic! Most of the issues that exist now will be tackled in this course anyway.

Before we can set up web applications, we need to have a managed account to use. Let's register another one, spsetup. We know how to, so review the earlier lessons!

Let's now open Application Management and transgress to Manage Web Applications.

Here we see the two Web Applications we already created before. When we click the New Web Application, it will, as the tooltip shows, create a new IIS Web Site with backing databases for new sites.

Just like we learned in the lesson before!

We talked before about creating two Web Applications, one for our intranet and one for the mysites.

Next we choose Create a New IIS Web Site and name it (So effectively creating a new Web Application) Cassosoft – Intranet.

While at it, set the default port to 80 and set the Host Header to Intranet.Cassosoft.Local, which also changes the Path to something recognizable.

Of course we won't allow anonymous connections and when using SSL, set it to yes (we'll use NO here).

Use NTLM for Claims Authentication Type.

Now keep everything default until you reach the Application Pool section. Here we say to create a new one and name it meaningfully Cassosoft – Intranet, like the Web Application name.

The Security Account we'll use is PSSPSetup manages Account.

Next for the Database Server, Give it a meaningfull name for the database as well…: Cassosoft_Intranet_DB

Set Windows Authentication.

Now we get to the Service Application Connections. Default is everything, but we can also create a custom one and select what we want. We'll use default here.

This will create the new Web Application

When we're done we see the window at right.

When we click Ok, we'll automatically create a new site collection, but will do this later.

When we look in IIS we'll see our new Web Application as SharePoint Creaed it:

The bindings are set to port 80 for url intranet.cassosoft.local. any other calls to port 80 will go to SharePoint – 80 Web Application. This binding is what was specified in the Host Header. Likewise, we'll find an application pool for our new site.

Now we'll create a new Web Application for the My Sites. We'll basically do the same as the previous web application, with following details:

Name: Cassosoft – Mysitesport: 80Host Header: mysites.cassosoft.localNew Application Pool: Cassosoft – MysitesApplication pool Account: PSSPSetupDatabase Name: SP13Cassosoft_MySites_DB

Leave the default service applications.

After it is created, Central Admin shows the following in its Web Application overview:

Now before we continue on to Site Collections, we'll have to configure DNS. Create two DNS A-host records for mysites.cassosoft.local and intranet.cassosoft.local and point them to the IP of our servr sptst.

IIS will now also show the application pool and web application for the Mysites, which is bound to the host header mysites.cassosoft.local.

6 Creating Site CollectionsWe'll now create site collections for our web-apps. We'll now focus on creating sites and site collections under those Web Applciations.

Site Collection:

- A collection of sites (250.000 under each collection)- Sites can only belong to one site collection- All sites in one site collection must be stored in the same content database.- Site collections share the same:

o Ownero Administration Settings

- A Top-level Site is always created when a Site Collection is created.

6.1 Creating a site collectionCreating a site collection has three prerequisites before starting:

- Web Application must be there- Quota template in place if planning to use it- Managed path

6.1.1 So What are Managed Paths?Managed paths:

- Are managed locations where content will be created (where is the content created and will it be found in the database?). Without managed paths it is hard to find specific content in the database.

- Two types:o Explicit: allow for one single site collection to be created underneath it. o Wildcard: Designed to allow child URLs for unlimited Site Collections to be created underneath it.

This lesson wil use both explicit as well as wildcard paths.

Closer look at managed paths:

We beginnen met de URL met de locatie van de web application (http://intranet.cassosoft.local) . Vervolgens volgt de locatie van de site collection (/main/). Next will be a site location (/home/) in our example here). This makes it easy for the server to find things.

In our demonstration here we'll take the following diagram as base point:

We start with our Web Application http://intranet.cassosoft.local, which we have in place already.

Next will be our first Site Collection: The basic intranet site collection for the whole company. It is an Explicit site collection called Main.

Next will be a wildcard Site Collection for the departments, allowing additional site collections to be created underneath it.

Each department gets its own site collection in this example, which are used as boundaries for owner and administration settings and user groups.

6.2 Practically: Creating the Site CollectionsWe start at CA, then to Application Management and Manage Web Applications. When in the Web Applications screen, we see that Managed Paths is disabled, since we didn't select an application to manage paths for.

Now select Cassosoft – Intranet, after which Managed Paths becomes available.

Web Application:http://intranet.cassosoft.local/

Explicit: Main Wildcard: Departments

Finance

Operators

Click on Managed Paths and a new dialog appears:

We see two managed paths, Root, which is not going to show in the url, but places the Site Collection in the Application root (http://intranet.cassosoft.local/) and sites, which comes to http://intranet.casssosoft.local/sites/. The first is explicit, meaning there can be only ONE in the root.

We'll add additional paths now, one for Main being Explicit and one for Departments, being wildcard.

Back in our Web Applications windows, go back to Central Administration Application Management, and then choose Create Site Collections

Start with selecting the correct Web Application (http://intranet.cassosoft.local/.

Title: Cassosoft Main IntranetWeb Site Address: setlect .main to add this site collection as explicit under the Main managed path we just created.

Under Template Selection, select the appropriate language and version (2013, English and as template select Team Site.

Primary Site Collection Administrator: Cassosoft\administrator

Secondary "" "": cassosoft\rcamies

Site Collection Administrators have MORE rights/permission/responsibilities than Site Owners!

Quota Template: No Quota. (If we wanted quota's, it would have been best to configure these first!)

Since the /main managed path is explicit, it will NOT be available if any new Site Collections are created.

Click Ok now to create the first site collection.

Once complete we'll see a message the Top Level Site Collection is created succesfulle.

Next site collections:

Create Site Collection:

Title: Cassosoft Finance

URL: /departments/finance

Team site and administrators are same.

URL becomes: http://intranet.cassosoft.local/departments/finance

Create Site Collection:

Title: Cassosoft Finance

URL: /departments/finance

Team site and administrators are same.

URL becomes: http://intranet.cassosoft.local/departments/finance

We now have two site collections created under the /departments/ wildcard managed path, and one under the /main/ explicit managed path.

Back in CA, under Application Management, choose View all Site Colections under Site Collections. The following will appear:

Clicking any of the URLs will give us details on the right for that URL/Site Collection.

WE made 3 site collections, yet we're not done yet….

6.3 Creating the Site Collection for the MySite host.We already created the MySite Web Application, so now we'll create the MySite Host Site Collection.

In CA, go to Application Management. Go to Manage Web Applications and choose Cassosoft – Mysite. We see the url being http://mysites.cassosoft.local. The mysites are actually individual Site Collections for the individual Users, meaning we need a wildcard includion managed path for them.

With the Mysites Web Application selected, choose Managed Paths and add an Wildcard Includion Managed Path titled personal.

Next, in Web Application Management, with Cassosoft – mysite still selected, turn on Self Service Site Creation by clicking it in the ribbon. This allows users to create the Mysite Sitecollections when they go to an url with a valid username.

A dialog will appear, where following has to be filled in:

Allow Users to create: On. This allows users to create a mysite by going to http://mysites.cassosoft.local/_layouts/15/scsignup.aspx

Under Start a Site, we can allow users to create teamsites as subsite of the personal mysite site collection.

For now, Chooose: Be hidden from users.

This greys out the other two setteings. If Users are allowed to create sites under their personal mysite, require a secondary contact for your own convenience!

Click Ok.

Now, we get an error!

Errrr… we have not yet created the Mysite root Site Collection, so we'll create it first, then will go back to enable mysite selfservice creation.

Back in Application management, select Create Site Collection with following details:

Web Application: Title: Mysite Host

URL: select the root "/" (we need the root mysite site collection for it to work!

For Template, select My Site Host Under Enterprise (OTHER OPTIONS WILL NOT WORK FOR MYSITE!!!!)

Add the site admins (cassosoft\administrator and cassosoft\rcamies)

After creating the root sitecollection for the Mysite Host, go to Application Management, Manage Web Applications, select the MySite host and Click: Self Service Site Creation and enable it as we discussed before.

The managed path /personal/ will be used in the setup for the User Profile Services as well later on.

7 The Managed Metadata Service Application7.1 Introdution to Managed MetadataWhat is Managed Metadata?:

Microsoft's definition: "Managed Metadata is a hierarchical collection of centrally managed terms that you can define, and then use as attributes for items in SharePoint Server 2013"

Which can be simpler explained by breaking it down a little more.

Basically metadata is information about data. Managed metadata provides you with a centralized location to store that data and make it available for utilization on any site within the farm.

Terms: a word or a phrase that can be associated with an item

Term Set: A collection of related terms

For example, in a column in SharePoint lists you can specify that it must contain one or more terms from a specific term set. (Columns will be explained later).

The Managed Metadata Services publishes a Term store as database where these terms and term sets are stores, which allows SharePoint to access and use them using a Service Connection.

Managed Terms:

- Usually pre-defined- Can only be created by users with the appropriate permissions- Typically organized into a hierarchy

Enterprise Keywords:

- Words or phrases that were added to SharePoint items- Part of a single, non-hierarchical set names "the keyword set"

Basic differences between Enterprise Keywords and Managed Terms sets is that the managed terms are created and controlled, by specific people, while Enterprise Keywords allow end-users to add keywords to the database.

Enterprise Keywords can be turned off, but this prevents users from creating their own search terms.

7.2 Practically: managing TermsTo manage the Managed Metadata Service Application, go to Application Management in the CA, choose Manage Service Applications.

When the Service Applications screen is shown, we see both the Managed Metadata Service Application (top one) and the Managed Metadata Service Connection Proxy (bottom one). Select the top one by clicking RIGHT besides the link, which enables the ribbon for the application.

If we look at the ribbon, we have the following options:

- New – create a new service application- Connect – connects to service application in other farm- Delete – removes the instance of the service- Manage – gives the management window (In this case, the "Term Stor Management Windows" for the

Managed metadata service)- Administrators – Allows specification of users allowed to manage this service application- Properties – gives service properties, which is the create new

MMS window, showing the current MMS service with its configuration.

- Publish- Permissions

Let's first check out Administrators. This opens a new dialog to add MMS administrators. MMS administrators manage the application, not by definition the terms set! This can be delegated in the service properties and management options! (This will be the Terms Store administrator)

Add your own account for full control and the other SharePoint admins.

The Properties window also shows a Content Type Hub URL box. Content types are a deep and involved topic, in which content types are simply items that we create and assign metadata to be used to. This allows us to create a centralized location (hub) that allows all our sites and site collections to access those content types.

Now click on Manage. This brings us to the Terms Store Management Tool.:

As the Managed Metadata Service administrator, we can't do anything here EXCEPT changing the items on the Home branch called Managed Metadata Servcie. We should now add Term Store Administrators.

You could also have multiple MMSes, for different site collections, each with their own administrators. We can choose the MMS we use here under the Available Service Applications.

Add here: Site Collection Admin, Site Owner, Power User with advanced SharePoint knowledge, because they should administer it (and add the domain admins/your private account, so you can manage it if needed)!

REMEMBER TO SAVE THE SCREEN USING THE SAVE BUTTON AT BOTTOM RIGHT!

(Normally you would now log in under another account. For course purposes wetemporarily included psspsetup as Term Store Administrator).

As user on the site we can go to the Site Settings and open the Term Store Management link to manage the Term Store.

The Term Store Admin can now work on the Term Store.

In the Term Store Management Tool, we can now manage items below the Managed metadata service home.

We have two predefined groups, each with term sets, with a term. Clicking a group, item or term set gives a small dropdown arrow allowing us to administer the group, termset or term. (terms can have child terms!)

Click on the Managed Metadata Service and select New Group. Call it Benefits

In the group window we can define name, description Group Managers and Contriobutors.

Right-click the ew group Benefits and select New Term Set.

Call it Insurance.

This time we can add group name, description, owner, contact e-mail, stake holders and submission policy. We'll leave it ast closed, so only group managers and contributors can add to it. (so not from within a 'tagging application' like office apps!).

Next we create a new term called Life Insurance and one for Health Insurance. We now have created a new group, set and terms to use!

We also have additional tabs for the sets and items. Check them out!

When we click the System Group, we can see it contains the Keywords set, which is the earlier mentioned Enterprise Keywords set.

Hashtags can also be added like keywords. Orphan terms are terms used where the terms or term sets were deleted, so they should be reassigned to sets.

When in the Home branche of the service, we have an import option in the attributes at right. We can create a sample file here, open it and save it as csv. Next we can choose or create a new Term Set and import it there.

7.3 Practical: Creating a Managed Metadata Service ApplicationBack to Central Administration. Go to Manage Service Applications and select New and then Managed Metadata Service.

Here we can create an additional Managed Metadata Service Application. Create one, check its properties, its terms store, etc, and then DELETE it!

8 Search Service ApplicationWe'll talk about The Search Service Application in this lesson.

8.1 IntroductionIn SharePoint 2007/2010 we had two search products, SharePoint Search and FAST Search/Enterprise Search. SharePoint 2013 only has one Search product, a combined, unified search tool.

Out of the Box Search:

- Enterprise Search- People Search- Site Search- Media Search- New: Topic Pages- New: Content by Search

Both new ones allow for creation of search driven sites.

Another nice feature is the My Tasks in the My Sites, which allows users to search for their tasks and pull them together in a central location.

8.2 Creating the Search Service AppliciationsInside CA, go to Manage Service Applications. Here we'll see the Search Administration Web Service for Search Service Application, the Search Service Application and the Search Service Application Proxy (which is the Connector).

These were created using the Farm Configuration Wizard. We'll first delete it and then recreate it.

Click at right of the Search Service Application Link, select Delete and delete it with its data. This can take some time, and will delete all three Search Service Applications at once.

Next, go to NewSearch Service Application now enter a name, service, select an application pool for the services. We won't create a new Application Pool here, but in real life we want to, with its own account. Click Ok to create.

When it's done, we have both the Search Administration Web Service for Search Service Application, and the Search Service Application and the proxy available to us.

Now click on the Search Service to open the Search Administration pages.

If it does NOT display all checkmarks after creating the service under Search Application Technology, please wait 15 minutes and reboot the server.

When we now go to our intranet site and upload some files, the search will not find it, since we didn't set up a search crawler, allowing it to index everything. We need to configure the crawler.

8.3 8.3 Setting up the Search CrawlerGo back to the Search Service Application Page (under Manage Search Service Applications, remember?).

We see a recent crawl rate of 0 items per second…. Searchable Items 0…

So, go to the Crawling section and click the Content Sources link.

This shows where the crawler is going to look for data. By default it is set up to crawl the Local SharePoint Sites. Click it!

Here we can set up which start addresses to crawl and set up crawl settings. The Continuous crawl is new in SharePoint 2013, but is resource intensive! Best if placed on separate server when using this!. Next set up a Full and Incremental Crawl Schedule and a priority.

Click OK and back in the Content sources screen, click Add Content Source and see what we can crawl.

Enterprise Search People Search Site Search

Media Search Topic pages Content by Search

Back in the Content Sources screen, click Start all Crawls to start the search crawl (which takes some time).

Once complete, its is NOT going to work!

Lesson 09 – 16:30