\n\nWe gradually reaching end of this 5 day course and day 4 was focused on User Profile Service and Search. Those are two big features, especially search. Though from indexing flow and search sub-components architecture it is normal full fledged search and my previous experience with Autonomy IDOL was somewhat handy for understanding this.\n\nService applications were introduced in Microsoft SharePoint Server 2010, replacing the Shared Service Provider architecture of Microsoft Office SharePointServer 2007. Service applications provide a flexible design for delivering services, such as Managed Metadata or PerformancePoint, to users who need them.Microsoft SharePoint Server 2013 includes more than 20 services, some of which are new to this version, whereas others are enhanced.In planning and configuring service applications, it is important that you understand the dependencies, resource usage, and business requirements for each.\n\nSharing, or federation, of service applications covered in more detail in course 20332B: Advanced Solutions of Microsoft SharePoint Server 2013.\n\nKey components and topologies for SharePoint Server 2013 service application architecture Provision and manage SharePoint 2013 service applications.\n\nThe service application architecture was introduced in Microsoft SharePoint Server 2010, replacing the Shared Service Provider (SSP) model of Microsoft Office SharePoint Server 2007. The architecture remains consistent in SharePoint 2013, with the addition of new service applications.The advantage of service applications over the SSP is that services are more granular and can be deployed only to web applications that require the functionality that individual services offer. This offers greater design flexibility for the management of resources and functionality.Describe the function of service application instances and service application dependencies.\n\nDescribe some of the key options for service application topology design.Explain how to map business requirements to service application design.\n\nSP Features work on 4 different levels: subsite, collection, farm, web app. Some basic feature can be enabled independently on any levels, other have dependencies.\n\n
\n\nyou should find “SharePoint Server Publishing Infrastructure” under\n\n”Site settings” > “Site Collection Administration” > “Site collection features”\n\nyou wont find it under site feature\n\nor you can access it through this link :\n
https://{sharepoint server}/_layouts/15/ManageFeatures.aspx?Scope=Site for Site scope features\nhttp://server/site/siteCollection/_layouts/ManageFeatures.aspx for Web scoped features\n\n\nArchitecture Picture\n\nhttp://sharepoint.stackexchange.com/questions/52248/why-does-my-feature-appear-in-the-site-collection\n\n\nSharePoint health analyzer – can report on missing service dependencies\nState Service Service Application – can be configured with PS only.\n\n[code language=”powershell”]\n#Uncomment the line below if you running this not in SP Management shell\n#Add-PSSnapin Microsoft.SharePoint.PowerShell\n$stateName = “State Service”\n$stateDBName = “State_Service”\n$stateDB = New-SPStateServiceDatabase -Name $stateDBName\n$state = New-SPStateServiceApplication -Name $stateName -Database $stateDB\nNew-SPStateServiceApplicationProxy -Name ”$stateName Proxy” -ServiceApplication $state –DefaultProxyGroup\n[/code]\n\n
SP User Profile Service (UPS)
Provides the ability to create and administer user profiles that can be accessed from multiple sites and farms.
The User Profile Service is a service application in Microsoft SharePoint Server 2013 that provides a central location for configuring and managing the keyelements of personalization settings. The User Profile Service holds the settings for the following features:
\n\nUser profiles. A user profile stores detailed information about the user in the form of properties. You can manage and display all of the properties that are related to each user.\n\nProfile synchronization. You can synchronize user profile information that the User Profile Service stores with external directory services such as Active Directory Domain Services. A user profile can incorporate data from more than one source. Youcan schedule synchronization depending on how often you expect the relevant information to change.\n\nAudiences. Audiences enable you to target content to users based on their jobs or tasks. You can define an audience by membership in a SharePoint group ordistribution list, by the organizational reporting structure, or by the public properties in user profiles.\n\nMy Site Host. My Site Host is a dedicated site for hosting My Site websites. You must provision a My Site Host before you can deploy the social features ofSharePoint 2013.\n\nMy Site website. Each user in your organization who has a synchronized user profile can have a personal site. Users can store documents, manage the contentof their My Site website, and share content with others. The My Site content storage is also referred to as SkyDrive@<companyname>.\n\nSocial tags and notes. Users can add social tags to documents, to other SharePoint items, and to other objects, such as external webpages and blog posts. Userscan also create notes on any SharePoint page. Administrators can delete all tags for employees when they leave the company or remove a tag that they do notwant.\n\nUser personalization permissions. You can use permissions settings within the User Profile Service application to control which users can edit profiles, usepersonal sites, and use tags and notes.\n\n
\n\nYou cannot access the Manage Profile Service page until an instance of a User Profile Service application exists and the associated services are started. You canuse the SharePoint Central Administration website in addition to Windows PowerShell to create and manage User Profile Service applications and other serviceapplications for non-hosted environments. You can also delegate management of a User Profile Service application to someone who does not have permissionsto manage other services or settings contained in Central Administration.\n\n
My Sites. Microsoft push for replacing it with Yammer, but this met certain resistance as Yammer is purely cloud thing whereas My Sites local/on-prem (loads of companies are still not ready to embrace cloud 🙂 ).
People Search.
Audiences.
Org Chart.
SQL Database Profiles.
Start 2 services: User Profile Service, User Profile Synchronization Service.
Create User Profile Service Application and 3 databases
Create separate site collection (optional) – as we need to have separate Web App, because we enabling auto creation of sites for users.
UPS sync with AD DS.
Special account – should have rights to replicate AD data (should be granted BOTH in ADUC and ADSI EDIT) on domain level (ADUC > Domain Properties > Security Tab > Grant Replicating Directory Changes)
miisclient.exe
SP Search Service
Changed significantly in SP 2013. Full text content search and attribute search.
Multiple content/index supported (mirror/stripe)
Configuring search:
Backup search service application: