Item was not crawled because of a password change. Update password and retry crawling.

Recently i changed my service account password and updated the same in the following areas

1. Central Admin -> Managed Account
2. IIS -> Application Pool Identity
3. Services.msc -> If Search Service running service account.

but my search crawl history says "Item was not crawled because of a password change. Update password and retry crawling". Searched a lot and come to knew require to update the password separately in Default Content Access account.

To access the Default content access account use the following links.

Central Adminstration -> Manage Service Applications -> Search Service.

In the search service page. Look on the left top pane you have link called "Search Service Administration". Choose that and it opens a new page. In that we have a option called default content access account.

Thanks.

Difference between Explicit and Wildcard Inclusion in SharePoint

Recently i heard from one my friend who playing SharePoint developer role. He asked what is mean by explicit inclusion. What is the purpose of it and how it works. And they knew only wild card inclusion managed path and they thought that is the one which available in SharePoint.

With this experience i would like to share the information about explaining the managed path and its uses in SharePoint.

What's in a SharePoint Managed Path?

I often hear and sense confusion about SharePoint managed paths. Managed paths are essentially 'mount points' for site collections. 

There are two types of managed paths available in SharePoint.
- Explicit 
- Wildcard. 

What's the difference between an explicit managed path and a Wildcard managed path? 

By default, the root ‘/’ managed path is explicit, meaning only one site collection can be in it and it assumes the identity of the managed path. That's how you browse to http://servername:port and get a Web page. A Web application without a site collection in the root managed path will return a 404 error when browsing to the root. You could always create another explicit managed path for multiple portal support in a Web application, i.e. http://servername:port/HR. HR is a peer to '/'. Now, you can no longer have an HR sub-site in the root - you will get a security validation error because the URL space is already taken.

A Wildcard managed path is basically 180 degrees in the opposite direction. A Wildcard managed path can support hundreds or thousands of site collections, but they are appended to the managed path, like http://servername:port/sites/team, with sites being the Wildcard managed path. It will always return a 404 error when browsing directly to a Wildcard managed path. But, you can create many Wildcard MPs like teams or projects.  Wildcard managed paths are like a sorting mechanism for site collections.

I hope this helps your Web application structure and design.

Run all Health Analysis Jobs on Demand

Following an installation, nothing gives me more joy (pertaining to SharePoint anyway) than having a clean Health Report days after my installation (AKA: Review Problems and Solutions). Recently though, I was doing an installation and I decided to try to “force run” the health rules rather than wait for them to run.

Found this in PowerShell to run all the jobs on demand:

$jobs = Get-SPTimerJob | Where-Object {$_.Title -like "Health Analysis Job*"}
foreach ($job in $jobs)
{
  $job.RunNow()
}

SharePoint Server 2010 Service Pack 2 Updated

It is recommended to install June 2013 CU before SP2. June 2013 CU might not correctly identify the SP2 baseline. If SP2 has already been installed and June CU does not install you need to wait for August CU which will correctly identify the SP2 baseline.

Guess it wasn’t such a smart installer after all was it?

Let’s take a look at the version numbers based on installation order:

• SP2 only - 14.0.7015.1000
• June CU only - 14.0.7102.5004
• SP2 then June CU - 14.1.7015.1000
• June CU then SP2 - 14.1.7102.5004

Based on the original guidance from MS, you might be running the June 2013 CU baseline, but your build version will still show as SP2.

SharePoint 2013 New Feature Reference

This can be used as a quick reference for custom meetings or just yours to have on hand.

Requirements:

• Minimum OS: Server 2008 R2 SP1
• Minimum SQL: 2008 R2 SP1
• Supports SQL and Server 2012
• CPU: 4 Cores
• RAM: 12GB (3-tier farm deployment)

General Info:

• DB Attach only upgrade method
• BDC, MMS, UPA, Secure Store, Search support DB attach upgrade
• Site collection level upgrade supported. DB is upgraded but site collection stay 2010 until testing is complete. Not just visual upgrade
• Web analytics now integrated with search. No longer its own SA
• Office Web Apps now its own separate scalable server farm product that SP consumes
• New Service Apps:
  • App MGMT Service
    • Manage SP app licensing and permissions
  • Work MGMT Service
    • Aggregate and synchronize tasks between multiple environments, such as Project Server, Exchange and SharePoint.
  • Translation Service:
    • On the fly translation from 1 language to another
• Supports PowerShell 3.0 and .Net 4.x Framework
• Claims based authentication is the default (classic mode can still be implemented via PowerShell)
• FAST Search is now baked in.
• User Profile Service has a new 1 way AD import mode. Full 2 way FIM UPS stays the same and is still available

SQL:

• SQL has always on HA/DR and improved I/O with SP 2013
• 7 DB have been deprecated in SP 2013
  • 4 Project related DBs
  • Search Property
  • 2 Web Analytics DBs
• 5 New databases
  • Project Service
  • Search Service Application Links Store Database Library
  • Search Service Application Analytics Reporting Store Database
  • App Management Service Database
  • Translation Service Database

Converting SharePoint website from Classic to Claims based Authentication

$App = get-spwebapplication “URL”

$app.useclaimsauthentication = “True”

$app.Update()

Example:-

$App = get-spwebapplication “http://sp1:5000”

$app.useclaimsauthentication = “True”

$app.Update()

UserName showing up as DomainName\UserName instead of Full Name in SharePoint

UserName showing up as DomainName\UserName instead of Full/Display Name in SharePoint.

Solution 1 : 

• Set-SPUser -Identity ‘scs\shiva4224’ -DisplayName ‘Shivashankaran S C’ –Web http://algorithm
• Get-SPUser –Web http://algorithm | Set-SPUser –SyncFromAD

FOR ALL USERS : Get-SPUser –Web http://algorithm | Set-SPUser –SyncFromAD

Solution 2 :

 1. Opened Central Administration on SharePoint 2010, logged in as the Administrator.

2. Clicked into "Application Management," then "Manage Service Applications."

3. Scrolled down to "User Profile Service Application," and clicked to open that.

4. Clicked "Manage User Profiles" under the main People heading.

5. Searched for the account I was looking for - "shiva" - and made the changes like first name, last name, and full name were showing.

6. Saved - and now I'm hoping for the best. With SharePoint 2010 it took up to 15 minutes without IIS Restart to become available; we'll see with SharePoint 2013.

Powershell Commands for Installing Solutions and Features in SharePoint.

Earlier i discussed about how to add the solution (WSP) to the SharePoint. In the continuation now i am going to explain how to install (Deploy) the solution to the concern web application.

After that how to enable or disable the feature through powershell.

To know about adding solution in SharePoint Click Here.

Installing the Solution

After adding a solution definetly we need to deploy the solution to web application. To do that we have command called Install-SPSolution. Syntax and Example are provided below for your understanding.

SYNTAX

    Install-SPSolution [-Identity] <SPSolutionPipeBind> [-AllWebApplications <S

    witchParameter>] [-AssignmentCollection <SPAssignmentCollection>] [-CASPoli

    cies <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParam

    eter>] [-GACDeployment <SwitchParameter>] [-Language <UInt32>] [-Local <Swi

    tchParameter>] [-Time <String>] [-WebApplication <SPWebApplicationPipeBind>

    ] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

    Install-SPSolution [[-Identity] <SPSolutionPipeBind>] -Synchronize <SwitchP

    arameter> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Swit

    chParameter>]] [-Language <UInt32>] [-WhatIf [<SwitchParameter>]] [<CommonP

    arameters>]

Example:

Install-SPSolution –Identity recruitment.wsp –WebApplication http://myrecruitmentsite -GACDeployment

Note: You can also use the following parameters

                     –CASPolicies: If you are not deploying to the GAC

                     –AllWebApplications: if you want to deploy the solution to all web applications

                     –Force: to force the deployment of the solution

                     -GACDeployment: It will place the DLL files to the Assembly folder in Windows directory.

Updating the Solution in SharePoint

Without redeploying the solution you need to overwrite the solution with some changes in the code level means, we can use Update-SPSolution. The example are provided below.

Update-SPSolution –Identity recruitment.wsp –LiteralPath E:\solutions\recruitment.wsp –GACDeployment

Uninstalling the Solution from SharePoint

This command will just retract your solution from the specified web application. After executing the below command the mentioned web application can't use the feature which are bind with the solution.

Uninstall-SPSolution –Identity recruitment.wsp –WebApplication http://myrecruitmentsite

Removing the Solution from SharePoint

This command will completely remove your solution from the SharePoint server. Before executing this command the solution should be retracted from all the web application where it deployed.

Remove-SPSolution –Identity recruitment.wsp

Enable or Disable the Feature in SharePoint

The below command will help you to enable or disable the feature to the site level.

Enable-SPFeature –Identity RefertheBuddy –url http://myrecruitmentsite

Disable-SPFeature –Identity RefertheBuddy –url http://myrecruitmentsite

Thanks Guys for Watching this Blog. :-)