Deploying the share point user profile service

  • 1,193 views
Uploaded on

Compact presentation on pitfalls and best practices for deploying the user profile service in SharePoint Server 2010.

Compact presentation on pitfalls and best practices for deploying the user profile service in SharePoint Server 2010.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,193
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
6
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. 1 Deploying the SharePoint User Profile Service internal
  • 2. Deploying the SharePoint User Profile ServicePitfalls & best practicesAndries den HaanAugust 2012
  • 3. SharePoint is the center of the universe SharePoint is the center of the universe3 Deploying the SharePoint User Profile Service internal
  • 4. The User Profile Service provides a full set ofsocial features for SharePoint Server 2010• Social tagging and commenting• extensible activity feed SITES• maintains current user information COMPOSITES COMMUNITIES• multiple sources• sets user context: • organization Browser INSIGHTS CONTENT • status • recent activity SEARCH • common relationships • expertise, ask me about.4 Deploying the SharePoint User Profile Service internal
  • 5. But deploying the User Profile Service can be abit cumbersome to say the least • The User Profile Service (UPA) is a complex part of SharePoint with many subcomponents and (internal) references and dependencies • the amount of deployment pitfalls may drive you crazy • customers want it really bad, because it’s the “Social” component • so there’s no way to run or hide!5 Deploying the SharePoint User Profile Service internal
  • 6. Let’s take a deep dive and explore the UPA step Let’s take a deep dive andby step UPA step by step explore the6 Deploying the SharePoint User Profile Service internal
  • 7. Agenda Architecture & components Some interesting anomalies Common deployment pitfalls Putting it all into practice A final word of advice Some practical references7 Deploying the SharePoint User Profile Service internal
  • 8. The architecture for the UPA is a bit differentfrom other SharePoint Server 2010 components SharePoint Content Related Service Applications Application Pool DOMAINSPContentAppPool Search http://portal (Web application) Managed Metadata User Profile Service Application Proxy SharePoint Web Services Default User Profile Synchronisation Service Application Pool DOMAINSPWebServicesAppPool SharePoint Service Instance User Profile Service Windows Services User Profile DOMAINSPFarmAccount SharePoint Service Instance ServiceApplication Forefront Identity Manager .Net Assemblies Forefront Identity Manager Synchronisation Directory Service Social DB Profile DB Sync DB8 Deploying the SharePoint User Profile Service internal
  • 9. Some interesting anomalies might indicate thatthe UPA suffered from release pressureNaming just a few to get you all warmed up:• Some parts of the UP have direct Profile database access• FIM is only required for writing back to AD (issue for import-only scenarios solved in “15)• SharePoint Server 2010 RTM was bundled with a FIM version lower then Release Candidate 1 (fixed in CU June 2011)• database schema bugs during service application creation• alternate service account permissions during provisioning• re-provisioning of the UPA after deploying updates• after a server restart, the UPS service instance is stopped.9 Deploying the SharePoint User Profile Service internal
  • 10. Some common deployment pitfalls:It’s SharePoint! What could go wrong?With incorrect settings, provisioning will still start(up to 15 times), but will always fail:• the service account (Farm account) needs Local Administrator permissions, but only during provisioning• the Active Directory synchronization account requires “Replicate directory Changes” permissions in the domain in order to successfully import user profile data• database bugs when using PowerShell: the default schema for the Farm Account in the Synchronization database is set incorrectly• import performance is slow (fixed in CU June 2011)• co-existence with .Net Framework 4.0 (manual fixes).10 Deploying the SharePoint User Profile Service internal
  • 11. Putting it all into practice to successfullyperform the User Profile Service deployment We’ll take a step-by-step approach: • setting the correct permissions upfront • using Windows PowerShell magic to create the Service Application and sync connections • monitoring UPA provisioning using the ULS viewer and checking that FIM services are properly configured and started • reviewing active directory import activities through the FIM client.11 Deploying the SharePoint User Profile Service internal
  • 12. Een beheersingsplan voorziet in de juiste A final word of advice:spelregels en richtlijnen Never use the Farm Configuration Wizard!12 Deploying the SharePoint User Profile Service internal
  • 13. Some practical references that will help you onthe road to success and infinite glory Configure profile synchronization (SharePoint Server 2010) http://technet.microsoft.com/en-us/library/ee721049.aspx ULS Viewer http://www.microsoft.com/en-us/download/details.aspx?id=21101 Spencer Harbar’s rational Guide http://www.harbar.net/articles/sp2010ups.aspx “Stuck on Starting” http://www.harbar.net/articles/sp2010ups2.aspx13 Deploying the SharePoint User Profile Service internal
  • 14. Connect | Share | DiscoverWould you like to know more?andries.denhaan@kpn.com