When search results are returned from the People Search scope a number of groovy functions are available, including:
- Navigate to the person My Site
- Send an email to the person
- Interact via OCS presence
- Browse in organizational chart
- View content by person
The following screenshot illustrates these options:
In a farm deployment, you will install SharePoint on a server, but access the site via a DNS entry for example, http://ourintranet.*, but what happens when the organizational browser refuses to use the DNS name in its link?
A combination of items need to be correctly configured, they are:
User Profile Service Application
The UP service application drives the My Site configuration and the people search gets its results from the UP. Getting this 100% configured is crucial as a starting point. Under the UP, look for the “Setup My Sites” link and ensure all is well.
Search Content Source
In a default SharePoint environment a Local SharePoint Sites content source is provisioned. In this content source 2 addresses are there by default:
- http://%5Bservername%5D
- sps3://[servername]
Ensure that you update these addresses to:
- http://%5Bdnsname%5D
- sps3://[dnsname]
Initially, I had this set to the server name and most of the People search were correct except for the “Browse in organizational chart” link. I even tried adding a server name mapping, but the only thing that solved it was updating the actual sps3:// content source.
Tagged: Search, Social Networking
