SharePoint 2015

SP 2015 Interoperability API documentation is available here

http://www.microsoft.com/en-us/download/details.aspx?id=28768

so, SP 2015 is on the way :)

SP 2013 Interview Questions

Hi folks,

I just across this article which gives an oversight about the interview questions which usually been asked on SP 2013

http://www.onlysharepoint2013.com/2012/09/sharepoint-2013-interview-questions-and.html

Quite Interesting, I will try to add more on this from my end.

Happy job hunting :)

Added some more here

SharePoint 2013 Q&A

1) What are the three user authentication methods that SharePoint 2013 supports?

1. Windows claims
2. Security Assertion Markup Language (SAML)-based claims
3. Forms-based authentication claims

2) Out of the available authentication methods, which one would is considered the recommend according to Microsoft?

Claims-based authentication methods are recommended.

3) What protocol does server-to-server authentication extend?

SharePoint 2013 extends OAuth.

4) SharePoint Store and App Catalog Access SharePoint resources on behalf of a user using?

OAuth 2.0.

5) What Business Data Connectivity (BDC) connections types are supported in SharePoint 2013?

1. WCF
2. SQL Server
3. NET assemblies
4. Open Data Protocol

6) What are some examples of technology that OData leverages?

1. HTTP
2. Atom Publishing Protocol (AtomPub)
3.  JavaScript Object Notation (JSON)

7) What types of authentication does Business Connectivity Services support?

1. Anonymous
2. Basic
3. Windows
4. Custom authentication to OData services when it is used with the Secure Store Service

8) What does a BDC model do?

Describes which tables to read, which items from those tables are of interest, and which operations to perform on them.

9) How is the BDC model in SharePoint 2013 more streamlined than in SharePoint 2010?

Visual Studio 2010 is able to connect to the OData endpoint through Business Connectivity Services and read the OData source. Visual Studio 2010 will then automatically generate the BDC model.

10) How is the BDC model used after being built?

Imported into the Business Data Catalog as a farm-scoped external content type, or be included in an app for SharePoint.

11) What Is An Event Listener in SharePoint 2013?

The event listener includes an event subscriber. The subscriber receives notifications from the event publisher (on the external system side) on changes to the data and then initiates predefined actions when changes occur.

12) How is an event listener useful?

Enables SharePoint users and custom code to receive notifications of events that occur in an external system.

13) With an event listener, what are the supported connections for an external system?

1. OData
2. SQL
3. WCF

14) What are apps for SharePoint?

Apps for SharePoint allow addition of functionality to a SharePoint site by using the self-contained app for SharePoint.

15) What is the primary benefit of using apps for SharePoint?

Each app for SharePoint is isolated from the rest of the system.

16) How are BDC models and apps for SharePoint related?

BDC models can be scoped to apps for SharePoint and connection information is defined and stored separately from the app-scoped BDC model in BDC connections.

17) What is eDiscovery in the context of SharePoint 2013?

Introduces a new site for managing discovery cases and holds. The site allows one to access discovery cases to conduct searches, place content on hold, and export content.

18) What are some examples of some things you can related to an eDiscovery case?

1. Sources
2. eDiscovery sets
3. Queries
4. Exports

 19) What is an in-place hold?

Content that is put on hold is preserved, but users can still change it.

20)  What the content can be included with SharePoint eDiscovery export?

1. Document
2. Lists
3. Pages
4. Exchange objects

21) In terms of enterprise-wide eDiscovery, what actions can be taken by an authorized user?

1.  Create a case, define a query, and then search SharePoint Server 2013, Exchange Server 2013, and file shares
2. Export all of the content that was identified.
3. Preserve items in place in SharePoint Server 2013 or Exchange Server 2013.
4. Track statistics related to the case.

22) What are the different types of mobile views offered in SharePoint 2013?

1. Contemporary view
2. Classic view
3. Full screen UI

23) What is the Microsoft Push Notification Service?

Supports applications on mobile devices that should receive notifications from a SharePoint site.

24) What field type would be used when working location specific SharePoint applications?

Geolocation field type

25) What is Site-based retention?

You can create and manage retention policies in that will apply to SharePoint sites and any Exchange Server 2013 team mailboxes that are associated with the sites.

26) What does a retention policy contain?

Generally what causes a project to be closed and when a project should expire.

27) What are some improvements in Excel Services in SharePoint 2013?

1. Field list and field well support
2. Calculated measures and members
3. Enhanced timeline controls
4. Application BI Servers
5. Business Intelligence Center update

 28) What is the In-Memory BI Engine (IMBI)?

The In Memory multidimensional data analysis engine (IMBI), also known as the Vertipaq engine, allows for almost instant analysis.

29) What does the Power View Add-in for Excel do?

Power View (“Crescent”) enables users to visualize and interact with modeled data by using highly interactive visualizations, animations and smart querying.

30) Can PerformancePoint be displayed on iPads?

Yes.

31) What is the Analysis Services Effective User?

Eliminates the need for Kerberos delegation when per-user authentication is used for Analysis Services data sources. By supporting Analysis Services Effective User feature, authorization checks will be based on the user specified by the EffectiveUserName property instead of using the currently authenticated user.

32) What are Community Sites in SharePoint 2013?

Community Sites offer a forum experience to categorize and cultivate discussions with a broad group of people across organizations in a company.

33) What is the primary change with MySite document libraries in 2013?

Users can specify permissions for a specific document without having to understand the inheritance model.

34) What are Image renditions?

Image renditions let you display different sized versions of an image on different pages.

35) How are multilingual sites implemented?

Variations, integrated translation service, cross-site publishing

36)  What is Cross-site publishing?

Cross-site publishing lets you store and maintain content in one or more authoring site collections, and display this content in one or more publishing site collections.

37) What is Managed navigation?

Managed navigation lets you define and maintain the navigation on a site by using term sets.

38) What are Category pages?

Category pages are page layouts that are used for displaying structured content such as catalog data.

39)  What is the Content Search Web Part?

Displays content that was crawled and added to the search index.

40) What are Refiners and faceted navigation?

Refiners are based on managed properties from the search index. With faceted navigation you can configure different refiners for different terms in a term set.

41) What is the Analytics Processing Component?

Runs different analytics jobs to analyze content in the search index and user actions that were performed on a site to identify items that users perceive as more relevant than others.

42) What does the Workflow Manager do?

High Density and Multi-Tenancy, Elastic Scale, Activity / Workflow Artifact Management, Tracking and Monitoring, Instance Management, Fully Declarative Authoring, REST and Service Bus Messaging, Managed Service Reliability.

43) What is a ranking model in SharePoint 2013 search?

A ranking model determines recall (which items are displayed in the search results) and rank (the order in which search results are displayed).

44) What actions can a query rule specify?

1. Add one or more result blocks
2. Change ranked results
3. Add Promoted Results (formerly called Best Bets) that appear above ranked results

45) What are Result sources?

Result source allow you to restrict queries to a subset of content by using a query transform.

 46) What is a Continuous crawl?

Eliminates the need to schedule incremental crawls and automatically starts crawls as necessary to keep the search index fresh.

47) How can you remove items from the search index?

Using the crawl logs.

48) How can you specify which entities to look for in the content in relation to SharePoint search?

Create and deploy your own dictionaries

49) What does document parsing functionality do?

Document parsers extract useful metadata and remove redundant information.

50) Is Visual Upgrade available in SharePoint 2013?

No.

51) What are the New Changes in Search?In SharePoint 2013 the best of two Search Engines "SharePoint Search" and “FAST Search Server for SharePoint” was combined
to make one Search Engine that would provide greater redundancy and for better scalability. For more Info on Search architecture see Search 2013 Architecture

Q2. What is Continuous Crawl?
Ans: A new Crawl Option "Continuous crawls" has been Introduced in search's Crawl Schedule Category to help keep the search index and search results as fresh as possible. Continuous crawls run every 15 minutes by default.

Q3. What are Display Templates?
Ans: To eliminate the fact that the designers and power users needed to modify the XSLT each time they needed a particular look and feel in SharePoint, a new concept of Design Templates has been introduced. Each Display Template consist of two files an HTML file (.html) and JavaScript File (.js). For more Info on Display templates see Display Templates

Q4. What is the new Analytics Processing Component in SharePoint 2013?
Ans: The Analytics Processing Component in SharePoint Server 2013 analyzes both the Content and the way users interact with it.The results from the analysis are added to the items in the search index to be used by Search Webparts,Recommendation Reports,Most Popular Items reports and other WebParts.

Q5: What analysis are done by Analytics Processing Component in SharePoint 2013?
Ans: The Analytics Processing Component runs two main types of analyses: Search analytics and Usage analytics. Search analytics analyzes content in the search index, and usage analytics analyzes the user actions.

Q6. What is the purpose of new Content Search Web Part(CSWP)?
Ans: In SharePoint 2013 Microsoft has introduced a new webpart called “Content Search Web Part (CSWP)”.This Web Part queries
against search Index to display results. The webpart displays search results in a way that you can easily format it and customize it.

Q7. What is Shredded Storage?
Ans: It’s a new Feature Introduced in SharePoint 2013 where Documents and Changes to the Documents are stored as “Shredded BLOBS” in the new DocStreams Data Table. Unlike SharePoint 2010, it helps to lower down the amount of storage required for saving files by saving only the Changes and not the entire Versions of the Files in database.

Q8: Why would you Disable Shredded Storage?
Ans: Shredded storage is a per document feature.So if two Copies of the exactly same document is stored in two different libraries, these two documents will still have their own set of shreds which will take up twice the space of each individual document.

Q9. Whats new in SPSite Powershell Cmdlet?
Ans: SPSite has few new parameters in SharePoint 2013 to make Site Collection Operations easier.
New-SPSite cmdlet allows to Create a Host-name Site Collections adding a using the HostHeaderWebApplication parameter that identifies the Web Application where the site collection is being Created.
Copy-SPSite (new) Use the Copy-SPSite cmdlet to make a copy of a site collection from one Source content database to a specified destination content database.The copy of the site collection has a new URL and a new SiteID.This will be very useful when renaming a SiteCollection.


Q10: Whats are the new Delegate Controls in SharePoint 2013?
Ans: In SharePoint 2013, three New Delegate Controls have been Introduced for the purpose of displaying the new Top Suite bar (with links SkyDrive, NewsFeed,Sync,follow). These Controls are -

• SuiteBarBrandingDelegate delegate Control
• SuiteLinksDelegate delegate Control
• PromotedActions Delegate Control

Q11: What are the Changes in CSOM and REST based APIs?
Ans:  Microsoft has improved both Client Side Object Model (CSOM) and Representational State Transfer (REST) based APIs by adding a much needed support for the Search, User Profiles, Taxonomies, and Publishing Object Model.Client.svc service is extended with REST capabilities and accepts HTTP GET, PUT, POST requests.


Q12: What’s the new App model?
Ans: SharePoint 2013 Introduces a Cloud App Model that enables you to Create apps.Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. An app may include SharePoint components such as lists, workflows, and site pages, but it can also surface a remote web application and remote data in SharePoint.

Q13: What is the new SPSecurityEventReceiver?
Ans:  SharePoint 2013 Introduces a Cloud App Model that enables you to Create apps.Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. An app may include SharePoint components such as lists, workflows, and site pages, but it can also surface a remote web application and remote data in SharePoint.

SharePoint Online Tags & Notes feature retired

The Tags & Notes feature of SharePoint Online has been retired.

The details about the retire is available here

Looks like Microsoft wants to promote Yammer as a enterprise social platform and make users to move towards it.

SharePoint OnPrem to Azure Migration

Hi,

Recently I happen to work on a proposal for which we need to provide  multiple options to migrate a SharePoint 2007/2010 farm to Azure and also to SP Online to some extent. There are couple options got discussed and each one has it own pros and cons. Choosing the option and methodology is purely based on the business scenario what you are handling right now. I tried to detail the various options here,

Option 1 : SP OnPrem Upgrade - then to Azure

First Upgrade the On-premise previous version SharePoint farm to latest one (SP 2013) and then migrate the upgraded SP 2013 Vms to Azure as VM's.

Things to keep in mind

• SP 2007/2003 does not have a direct upgrade to SP 2013, it needs to be followed sequentially (2007 to 2010 and then 2010 to 2013). you need to plan an infrastructure setup and cost accordingly also the licenses
• This option will work out very well if your on-premise infra is virtualized and applications are running in VMs
• Copying Vm from On-premise to Azure for various products has various approaches  like VMware to Azure, Hyper-V to Azure..etc
• All customizations, orphaned/unwanted sites, content cleanup, 3rd party components compatability, site restructuring, taxonomy redfine..etc will be checked and fixed before we are moving the application to cloud.
• Data migration from Azure Vm to SP Online will be bit faster as compared to doing it directly from On-premise. Because the data transfer rate between the Microsoft  data centers will be fast as when compared to the On-Prem and SP Online
• Site to Site VPN tunnel can be established between On-Premise and Azure to fasten the vm copy process

Option 2: SP OnPrem to Azure and then upgrade

Move an existing On-premise vm to azure as it as (using microsoft acelerator tool for azure) first and then upgrade the Azure old version farm to SP 2013

Things to keep in mind

• As-Is Vm movement from On-premise to cloud and then an upgrade, so user will get the feel of SP 2013 use only at the end of the migration phase
• Immediate movement of an on-premise vm to azure will have an drastic change in your infrastructure cost
• Cloud enablement and cloud dependent solutions, 3rd party components surprises will come only after you start doing the SP upgrade in azure
• 2 environment need to be available in azure, i.e. SP 2010 farm and SP 2013 farm along with your typical ALM (Dev, Test & Staging) environments. 
• Maintaining the same kind of environment on-premise should be costlier than in Azure

Option 3 : SP Onprem to Azure using 3rd party tool
Move an existing On-premise SP any version application to Azure SP 2013 using any 3rd party data migration tool like metalogix, docave..etc

Things to keep in mind

You will have complete freedom to redfine the IA and taxonomy in the new platform and make use of the new features while defining the architecture itself

It is only data migration between On-prem to azure not an environment movement

Manually need to move all the custom components, 3rd party solutions to new environment and rebuild to make it compatible in SP 2013

3rd party migration tool is needed to do this migration, ofcourse the tool cost you have to keep in mind

Network latency and migration tool capability to transfer the data b/w on-prem and azure need to be considered and should do migration plan based on how much(GB) can be transferred in how much time (hr)

Happy Migration !

Site Policies in SP 2013

This is new feature got introduced in SP 2013 and more useful when we have selfservice site getting created without any governance.

Site Policies will also a play vital role when we are implementing SP governance in OnPremise farm

Through Site Policies you can control the life cycle of a SharePoint site. Suppose your requirement is that you want a site should automatically delete after 6 months of date of creation. Or you want it should start a workflow automatically and then it should delete the site.  In this type of schenarious site policies will be helpful.

In SharePoint 2010, you could create only policies attached to content types or at the site collection level. But in SharePoint 2013, an new link on the name of Site Policies is available under Site Collection Administration in Site settings page.

Site policy has various option like:
- Do not close or delete the site automatically
- Delete the site automatically.
- Close the site automatically and delete the site automatically
- Run a workflow to close the site, and delete the site automatically

No-code solutions using SharePoint 2013 Composites

I just came across this page in TechNet and its really a useful one when we wanted to have a no-code solution for some of our business requirements in SP 2013 and 2010

Try it out by your self
http://technet.microsoft.com/en-us/office/dn756398

 

ULS Viewer for SharePoint 2013

Hope everyone is aware of ULS viewer and its usage in SP 2010 environments  (Check with developers and Support team), it will be nightmare if we don't have this tool to identify an exact issues.

 

Microsoft released ULS Viewer for SharePoint 2013. It is a very good tool for developers to get very good debugging information. This version has some very good fixes.

Here is the download link for ULS Viewer.

http://www.microsoft.com/en-us/download/details.aspx?id=44020

 

 

Source : TechNet

 

High Available SP 2013 farm in Azure

Step by step : deploy a high available SharePoint 2013 farm in Azure VM's

Nice article which details each step to quick establish SharePoint farm in Azure

 

a complete highly-available SharePoint Server 2013 farm can be provisioned in the cloud … with as few as 8 clicks!

http://blogs.technet.com/b/keithmayer/archive/2014/07/14/deploy-an-ha-sharepoint-server-farm-in-the-cloud-in-only-8-clicks.aspx

 

Source : Technet

Content Query Webpart Vs Content Search Webpart

There are two Web Parts on a SharePoint publishing site that are very similar: the Content Query Web Part (CQWP) and the Content Search Web Part (CSWP). Just by looking at their names, it’s not clear to distinguish the difference between the two.

 

 

Compare the strengths and limitations of the Web Parts

It’s important that you understand the strengths and limitations of the two Web Parts because if you choose the wrong one, your site could run into performance problems. You can use both Web Parts to show content that is based on a query. In a simplified world, here’s how you can decide between the two:

• Use the CQWP when you have a limited amount of content, your query is simple, and you don’t expect your content to grow much in the future.
• Use the CSWP in all other scenarios when you want to show content that is based on a query.

The table below gives a comparison of the two Web Parts:

Web Part behavior	Content Query Web Part	Content Search Web Part
Query configuration	Easy	You’ll need to know about certain search features such as managed properties.
Query across large amounts of content	Limited	Yes
Handle complex queries	Limited	Yes
Scale to handle future content growth	Limited	Yes
Display content from other site collections	No	Yes (see section below)
Design of query results can be customized	Yes, by using XSLT.	Yes, by using HTML.
Maintenance cost in a complex site architecture	High	Small (see section below)
Narrow down the query results that are displayed in the Web Part	No	Yes, in combination with the Refinement Web Part.

How the Web Parts display content

You can use both Web Parts to display information that is stored in a subsite. The user experience for content authors and home site visitors is identical, regardless of which Web Part you use. The difference between the two Web Parts is the technology that the Web Parts use. The CQWP queries a database, whereas the CSWP queries the search index.

Here’s an example of how these Web Parts behave. Example A shows a company that’s using a CQWP to show content from its sales subsite, and example B shows a company that’s using a CSWP to show content from its sales subsite.

Image callout	Example A: Content Query Web Part	Example B: Content Search Web Part
1	You author content in a list.	You author content in a list.
2	The list items are immediately stored in a database.	At a set time interval, the list items are automatically crawled and added to the search index.
3	A visitor views the home site. The CQWP automatically issued a query to the database.	A visitor views the home site. The CSWP automatically issues a query to the search index.
4	The database returns a query result and displays it in the CQWP.	The search index returns a query result and displays it in the CSWP.

Factors that you should to consider

Because the Web Parts use different technologies, the use cases for when you should choose one Web Part over the other differ. A use case is often more complex than the simple example shown in the previous section. Before you decide which Web Part to use, it’s important that you consider the following:

• How much content do I have?
• How complex will by query be?
• Where’s my content going to be stored?
• How much will my content grow over time?
• How much will my maintenance costs grow over time?

We recommend that you address all of these areas as a whole rather than separately.

 Note    If you’re considering moving from a SharePoint on-premises site to a SharePoint Online site, and you are using CQWPs on your SharePoint on-premises site, you could run into a couple of performance issues. In SharePoint Online you won’t be able to scale your tenant to improve performance. Also, the caching functionality behaves differently in SharePoint Online than in SharePoint on-premises.

What can affect the performance of the Content Query Web Part

In the previous example, if the News list contains less than 5000 items, the performance of the CQWP is likely to be very good. However, if the News list exceeds 5000 items, and the query in the CQWP is complex, the Web Part can run into performance problems. It’s difficult to define exactly what a complex query is, but a Source that goes across all sites in your site collection is more complex than aSource that queries a specific list. Also, if you query uses Additional Filters, the query complexity increases. The query complexity increases depending on the site column types and conditions that you use. Here are some examples:

• A query that filters on a site column of type Multiple lines of text is more complex than a query that filters on a site column of type Yes/No.
• A filter that uses a contains condition is more complex than a query that uses an is equal to condition.
• Multiple Or conditions increases the complexity of the query.

The performance of the CQWP is also affected by where your content is stored. If your content is stored across several sites, the total amount of list items the Web Part has to process will affect its performance. For example, on your company’s home site, you want to display the latest news items from lists that are maintained in multiple subsites. Each list contains 1000 items. That means that the CQWP will have to query across 3000 items.

In this example, if the query is simple, the performance of the CQWP is likely to be good as long as the total amount of items is less than 5000. However, if the query is complex, the CQWP could run into performance problems even when the total amount of items is a few thousand.

Another important factor that can affect the performance of the CQWP is if your content grows. A solution that works well today might not apply to your future content. If you expect a large increase in the number of sites or amount of content, you should not use the CQWP.

Use the Content Search Web Part to keep maintenance cost down

You can use both Web Parts to display content based on information from your site navigation. For example, when a visitor goes to a page, the Web Part on that page automatically issues a query that contains information from your site navigation. The search results are displayed in the Web Part. If you don’t have much content and the query is simple, you can use several CQWPs to display your content. However, because you have to maintain each CQWP individually, your maintenance costs can quickly escalate.

By using the CSWP with managed navigation and a category page, your maintenance costs will stay the same as your content grows. For example, if you add a new navigation category to your content, you can use the same category page to display the content that belongs to the new navigation category. So even though your content is growing, you’ll only need to maintain the same amount of pages.

In the example below, you can see how four CQWPs can be replaced by one CSWP on a category page.

Use the Content Search Web Part to display content from other site collections

You can use the CSWP to display content from other site collections. For example, if you want to author content in one site collection and display this content in another site collection, you have to use the CSWP. The CQWP can only display content from one site collection.

When in doubt, choose the Content Search Web Part

 

If you’re unsure about which Web Part to use, then the CSWP is probably the best choice in most cases. This Web Part is more flexible than the CQWP and will give you better performance results if you’re planning on expanding your content over time.

If you decide to use the CQWP, we recommend that you do testing to find out if the Web Part meets your current and future performance and maintenance requirements.

 

Source : Microsoft Office

 

CAML Designer 2013

CAML designer 2013 is available to download.

Requirement:
-.Net framework 4.5.
- Windows 8 or Windows Server 2012.

Download CAML designer for SharePoint 2013 from the below URL

http://biwug-web.sharepoint.com/CamlDesigner2013/CamlDesigner2013.application

https://onedrive.live.com/download?resid=C935657DE4CD44BF%2123633&authkey=%21AMHAEvfmcUvaNXA&ithint=file%2c.zip

 

Also you can check some screen shot in Karine Bosch's blog.

http://karinebosch.wordpress.com/my-articles/caml-designer-for-SharePoint-2013/

SP 2013 Search Configuration

Create and configure a Search Service Application  in SharePoint Server 2013

If you used the Farm Configuration Wizard after you installed SharePoint Server 2013 , a Search Service Application might have been created at that time. To verify whether a Search Service Application exists, you can click Manage service applications in the Application Management section on the Central Administration home page. For the remainder of this article, it is assumed that a Search Service Application does not exist yet, and that therefore you must create one.

When you deploy and configure a Search Service Application, you perform the following main tasks: 

1.Create Accounts
  Certain domain user accounts are required specifically for a Search Service Application.

2. Create a Search Service Application

  A Search Service Application provides enterprise search features and functionality. 

3. Configure the Search Service Application

 Basic configuration of a Search Service Application includes configuring a default content access account, an email contact, and content sources. 

4. Configure the Search Service Application Topology
 You can deploy search components on different servers in the farm. You can also specify which instance of SQL Server is used to host the search-related databases.

Step 1: Create Accounts that are required for a SharePoint Search Service Application

The following table lists the accounts that are required when a Search Service Application is created.

 

The accounts that you use for the Search service, the Search Admin Web Service application pool, and the Search Query and Site Settings Web Service application pool must be registered as managed accounts in SharePoint Server 2013 Preview so that they are available when you create the Search Service Application. Use the following procedure to register each of these accounts as a managed account.

To Register a Managed Account

1. On the Central Administration home page, in the Quick Launch, click Security.

2. On the Security page, in the General Security section, click Configure managed accounts.

3. On the Managed Accounts page, click Register Managed Account.

4. On the Register Managed Account page, in the Account Registration section, type the user name and         password that you want to use as credentials for the service account.

5. If you want SharePoint Server 2013 Preview to manage password changes for this account, select the           Enable automatic password change check box and configure the parameters for automatic password       change.

6. Click OK.

Step 2: Create a SharePoint Search Service Application

Each Search Service Application has a separate content index. You can create multiple Search Service Applications if you want to have different content indexes for different sets of content. For example, if you want to segregate sensitive content (such as employee benefits information) into a separate content index, you can create a separate Search Service Application to correspond to that set of content.

Use the following procedure to create a Search Service Application.

To create a Search Service Application

1. Verify that the user account that is performing this procedure is a member of the Farm Administrators           group for the farm for which you want to create the service application.

2. On the Central Administration home page, in the Application Management section, click Manage             service applications.

3. On the Manage Service Applications page, on the ribbon, click New, and then click Search Service           Application.

4. On the Create New Search Service Application page, do the following:

a) Accept the default value for Service Application name, or type a new name for the Search Service            Application.

b) In the Search Service Account list, select the managed account that you registered in the previous               procedure to run the Search service.

c) In the Application Pool for Search Admin Web Service section, do the following:

i. Select the Create new application pool option, and then specify a name for the application pool in the        Application pool name text box.

ii. In the Select a security account for this application pool section, select the Configurable option, and    then from the list select the account that you registered to run the application pool for the Search Admin        Web Service.

d) In the Application Pool for Search Query and Site Settings Web Service section, do the following:

i. Choose the Create new application pool option, and then specify a name for the application pool in the      Application pool name text box.

ii. In the Select a security account for this application pool section, select the Configurable option, and    then from the list select the account that you registered to run the application pool for the Search Query          and Site Settings Web Service.

5. Click OK.

Step 3: Configure the SharePoint Search Service Application

You configure a Search Service Application on the Search Administration page for that service application. Use the following procedure to go to the Search Administration page for a particular Search Service Application.

To go to the Search Administration page

1. Verify that the user account that is performing this procedure is an administrator for the Search Service         Application that you want to configure.

2. On the home page of the Central Administration website, in the Application Management section, click     Manage service applications.

3. On the Manage Service Applications page, click the Search Service Application that you want to                 configure.

On the Search Administration page, configure the settings as described in the following sections:

 

• Specify the default content access account
• Specify the contact email address
• Create content sources

 

 

 

Specify the default content access account

When you create a Search Service Application, the account that you specify for the Search service is automatically configured as the default content access account. The crawler uses this account to crawl content that does not have an associated crawl rule that specifies a different account. For the default content access account, we recommend that you specify a domain user account that has read access to as much of the content that you want to crawl as possible. You can change the default content access account at any time.

If you have to crawl certain content by using a different account, you can create a crawl rule and specify a different account for crawling. Use the following procedure to specify the default content access account.

To specify the default content access account

1. On the Search Administration page, in the System Status section, click the link in the Default content        access account row.

2. In the Default Content Access Account dialog box, in the Account box, type the account that you             created for content access in the form domain\user name.

3. Type the password for this account in the Password and Confirm Password boxes.

4. Click OK.

To specify the default content access account

1. On the Search Administration page, in the System Status section, click the link in the Default content       access account row.

2. In the Default Content Access Account dialog box, in the Account box, type the account that you             created for content access in the form domain\user name.

3. Type the password for this account in the Password and Confirm Password boxes.

4. Click OK.

Specify the contact email address

The Search service writes the contact email address to the logs of crawled servers. The default contact email address, someone@example.com, is a placeholder. We recommend that you change this to an account that an external administrator can contact when a crawl might be contributing to a problem such as a decrease in performance on a server that the search system is crawling.

Use the following procedure to specify the contact email address.

To specify the contact email address

1. On the Search Administration page, in the System Status section, click the link for the Contact e-mail        address.

2. In the Search E-mail Setting dialog box, in the E-mail Address box, type the email address that you         want to appear in the logs of servers that are crawled by the search system.

3. Click OK.

Create content sources in a SharePoint Search Service Application

Crawling requires at least one content source. A content source is a set of options that you use to specify the type of content to crawl, the starting URLs to crawl, and when and how deep to crawl. When a Search Service Application is created, a content source named "Local SharePoint sites" is automatically created and configured for crawling all SharePoint sites in the local server farm. You can create content sources to specify other content to crawl and how the system will crawl that content. However, you do not have to create other content sources if you do not want to crawl content other than the SharePoint sites in the local farm.

If you choose the Standalone installation option when you install SharePoint Server 2013 Preview, a full crawl of all SharePoint sites in the farm is automatically performed after installation and an incremental crawl is scheduled to occur every 20 minutes after that. If you choose the Server Farm installation option when you install SharePoint Server 2013 Preview, no crawls are automatically scheduled or performed.

Step 4: Configure the SharePoint Search Service Application Topology

When you create a Search Service Application, the SharePoint Server Search service is started on the application server that is hosting the Central Administration website, and search components are deployed to that server. If you have more than one application server in your farm, you can deploy additional search components on other application servers, depending on your requirements. You can deploy multiple instances of certain components.

Create a Search Center site in SharePoint 2013 Preview

A Search Center site, or Search Center, provides an interface for users to submit search queries and view search results. A Search Center site is the top-level site of a site collection that a farm administrator creates by using the Enterprise Search Center template or the Basic Search Center template.

Depending on the kind of installation that you performed and the site collection template that you selected at that time, the farm might already have a Search Center site. To check this, browse to the top-level site for the site collection that you created during installation. In either case, you can create a Search Center site and grant users access to it by using the procedures in this article. After you create the Search Center site, the site collection administrator or site owner might want to add features and functionality so that the site provides a richer interface than the search box that appears by default on each SharePoint site.

To create a SharePoint Search Center Site

1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group.

2. On the home page of the Central Administration website, in the Application Management section, click Create site collections.

3. On the Create Site Collection page, do the following:  

a) In the Web Application section, select a web application to contain the new site collection. To use a web application           other than the one that is displayed, click the web application that is displayed, and then click Change Web Application.

b) In the Title and Description section, in the Title box, type the name for the new Search Center site. Optionally, type a         description in the Description box.

c) In the Web Site Address section, for the part of the URL immediately after the web application address, select /sites/, or     select a managed path that was previously defined, and then type the final part of the URL.

Note the address of the new Search Center for future reference.

d) In the Template Selection section, do the following:

i. In the Select the experience version drop-down list, select 2013 to create a Search Center site that provides the SharePoint 2013 Preview user experience, or select 2010 to create a Search Center site that provides the SharePoint 2010 Products user experience.

ii. In the Select a template subsection, click the Enterprise tab, and then do one of the following:

·         If you are using SharePoint Foundation 2013 Preview, select the Basic Search Center template.

·         Otherwise, if you are using SharePoint Server 2013 Preview, select the Enterprise Search Center template.

e) In the Primary Site Collection Administrator section, in the User name box, type the user name of the primary site             collection administrator for this site collection in the form domain\user name.

f) (Optional) In the Secondary Site Collection Administrator section, type the user name of a secondary site collection           administrator in the form domain\user name.

g) In the Quota Template section, select No Quota.

A Search Center site is not intended to be a data repository. Therefore, you do not have to select a quota template.

h) Click OK.

4. On the Top-Level Site Successfully Created page, click the link to the Search Center site that you created.

After you create the Search Center site, you must grant site access to users so that they can perform search queries and view search results. Use the following procedure to grant site access to users. 

To grant access to the SharePoint Search Center

1. Verify that the user account that is performing this procedure is a member of the Owners group on the Search Center site.

2. In a web browser, go to the Search Center site.

3. Open the Site menu by clicking the gear icon in the upper-right portion of the page, and then click Site Permissions.

4. In the Shared with dialog box, click Invite people.

5. In the Share  dialog box, in the Enter users separated with semicolons text box, type the names        of the Windows user groups and Windows users to whom you want to grant permissions for submitting queries and            viewing search results in the Search Center.

For example, to grant access to the Search Center to all Windows users, type NT Authority\authenticated users.

6. Click Show options.

7. Clear the Send an email invitation check box.

8. In the Select a group or permission level drop-down list, select  Visitors [Read].

9. Click Share.

Be sure that the Search Service Application has been created and the service is up and running.

 

The first new thing that I saw is the “Where should users searches go?” When you click on it, it will ask you to fill the “Preferred Search Center”

 

At the right side, you can see that the service has never been ran, so you can click on the left side “Content Sources”

So we are going to test the search on my Portal SpPirate, I made a search on Document, but the search returned nothing.

Under Content Sources we can define which site should be crawled for search. I have only one site, but if you have many sites, you can edit them here.

Under the version 2010, you had incremental and full crawl. Now there is a new crawl i.e. “Continuous Crawl”.

Note: This is a special type of crawl that eliminates the need to create incremental crawl schedules and will seamlessly work with the content source to provide maximum freshness.

When you start the crawl you will see that the Status will change.

Now, when we made a new search under the Portal SpPirate, the Search WebPart will return now values.

We even can now apply filters with a progress bar. Even, when you wait on a searched element, you will be prompted by a new great tool where you can:

 

• Open the searched element
• View the library
• Send the searched element