Migrate User from Moss 2007 to SharePoint 2013

After successfully migration of content Database from Moss 2007 to SharePoint 2013 via SharePoint 2010 as intermediate.

As part of this regular approach database detach –attach method and migrated the existing Moss 2007 site .Migration was successful and we were able to access the site  with the system account. Later we tried with couple of site admin accounts, to our surprise we were getting “ACCESS DENIED” with any other user id.

SharePoint assumes all users to be claim users and renders them so. Therefore, a normal windows user – “Domain\UserName” appears as “i:0#.w|Domain\UserName”.

To convert all window authentication user to claim based authentication:-

Open SharePoint 2013 Management Shell with Administrator account and run the below commands

$WebAppName = "http://"

$wa = get-SPWebApplication $WebAppName

$wa.UseClaimsAuthentication = $true

$wa.Update()

$wa.MigrateUsers($true)

$wa.ProvisionGlobally()

After successful provision, check the user - which will show claim based user and all user will be able to login the site also.

Happy Coding..

Google Vs Enterprise SharePoint 2013 Search

Why Enterprise Search Implementation is more sufficient at Enterprise level not google search

This article is more on thoughts.

As working on SharePoint 2013 Contextual search project. Meaning of Contextual is different in different prospective.

SharePoint Technology point of View, Contextual Meaning is Set Limit and Boundaries.

More Details: - If I search with in List, So List is my Context - system should search with in list only or if I am search with in Sub-Site, So Sub Site is my Context - system should search with in Sub site.

So this type of process is easy and where we can easily set limit and boundaries.

I have very informative article on that, which explained very nicely.

http://manojmittalblogs.blogspot.in/2015/06/configure-contextual-search.html

Now Story starts:-

Business says: - Contextual meaning User Context (Not User Segment): means: - What is user skill, Department, expertise, area of interest etc.

User Skill, Department, Expertise, area of Interest and lots more, these properties exists in use profile and we can access and use as input parameter for my search.

After Interval of the Story:-

We came to know, one more contextual meaning I.e. what are happening activity around the user i.e. what s (he) doing day-day basis.

Elaborate:-

What document, I am sharing with others and what people are sharing with me.

What type of conversation, I having with people and people having with me etc?

Then I thought, I should explore more on Exchange API, LYNC API, and OneDrive API etc. from where I will take the latest happening activity keyword and which will become the input for my search output.

It may consist confidential info also. I should carefully take care those also. Lots of other activity need to do for the same don’t know whether organization will allow me to take those information or not.

Now twist comes.

We are not “Google”. We are searching at Enterprise or Organizationa level.  Google is not having profile page and not having relevant keyword related user, so It take the relevancy key words from other social media and shows the result but at enterprise level we have enough data related to user. We should utilize those only.

Conclusion:-

Now the Use case exists:-

We have enough user data at the organization level which is exists in our system itself and which is exposed also in authorized environment. We should do the Proper ranking as per the weightage of the keyword and business requirement.

Please share your thought for the same.

Call Back Error in SharePoint People Picker Control.

Most of the blog says its permission issue: - at least for us it was not.

http://blogs.msdn.com/b/sofocle/archive/2011/05/17/sharepoint-2010-people-picker-issue-quot-there-was-an-error-in-the-callback-quot.aspx

As per above article – I check all the permission and User Policy – Everything was properly set, UPSA was also working fine

Issue: - When I was checking for user in address book or people picker

When I was adding the user in SharePoint group – It was throwing the Unexpected error:-

Architecture Structure of Server:-

Why I am explaining the architecture server – It’s very important  because most of people doesn’t know how to check the logs in all server.If we have proper farm setup with multiple server – We should check the Logs in all server.

Here is Power shell command which give  consolidated result from all sharepoint server.

Merge-SPLogFile –Path “E:\SPLogs\MergedLogs.log” –Correlation 3ae2a6c0-da14-43a1-afda-5bb6bbff3d43

Resolution:-

Steps Followed:-

• Restart SharePoint Timer Services
• Remove the Attached DB from Web Application using Central Admin
• Created DB with same Name.
• After Configuring the DB – Unable to browse site. – It was showing “Page Not Found”.Scared what happen suddenly.
• Finally - Clear the SharePoint Configuration Cache. Location “Drive:\ProgramData\Microsoft\SharePoint\Config\GUID”
• Deleted all log files
• Modify the Cache.ini with any numeric value put like 1 and save.

It seems like some services stuck in between or some configuration cache issue. After following the above steps.

SharePoint Site was browsing fine and people picker was also working fine without any fail.

Happy Coding.