Download the latest from Windows, Windows Apps, Office, Xbox, Skype, Windows 10, Lumia phone, Edge Internet Explorer, Dev Tools more. Rational Guide to implementing Share. Point Server 2. 01. User Profile Synchronization. TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/75/59/metablogapi/0652.image_6778E17A.png' alt='Microsoft Project 2010 Sharepoint Synchronization' title='Microsoft Project 2010 Sharepoint Synchronization' />Print posted on Friday, April 2. PMIntroduction. Theres a ton of stuff out there on User Profile Sync in Share. Point Server 2. 01. Some of its good, some of its frankly terrible. Tech. Net has some of the best material, but unfortunately Tech. Nets format restrictions are counter intuitive. Therefore this article presents an end to end, rational guide to setting this up. UPDATE 0. Tech. Net has recently updated its Configure profile synchronization Share. Point Server 2. 01. I urge you to check this out. There are a couple of contentious setup requirements in here. I may discuss those in more depth later. For now, the following steps are required. Dont try and work around them, UPS will break. The following is the least privilege you can get away with. You should really read the Architecture Overview below to become acquainted with the moving parts involved, but if you are impatient, you can skip to the procedure itself. If you are having problems, firstly ensure you are following the steps below exactly. TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/91/98/metablogapi/3808.clip_image014_thumb_0A9C46DE.jpg' alt='Microsoft Project 2010 Sharepoint Synchronization' title='Microsoft Project 2010 Sharepoint Synchronization' />Microsoft Project 2010 has a shiny new interface, but thats not all. Under the hood, it contains powerful new scheduling, task management, and view improvements that. I have a follow up article which also details the most common problems with configuring profile synchronization, which may help. Stuck on Starting Common Issues with Share. Point Server 2. 01. User Profile Synchronization. The following logical component diagram provides an overview of the different elements that together deliver the profile synchronisation capability. UPDATE 1. Click above to view at full size. The key components are briefly described below. User Profile Service Application. Note A Share. Point Service Application is a logical conceptual object which is currently very badly articulated. I will be covering service applications in more detail in a future article. The relevant physical assets are described in this article. An IIS Application which sits in the Share. Point Web Services IIS Web Site. The IIS Web Site is on every machine in the farm. When we start the Service Machine Instance later, the IIS Application will be created. It will be named with a GUID and is hosted by an Application Pool which is also named with a GUID. It hosts a couple of WCF services profileproperty and profiledbcache. This is known as a Service Application Endpoint. The Service Application Endpoint has three associated back end databases and other configuration. Pages for managing the Service Application are hosted in Central Administration and are called using a GUID in the query string. The WCFs dont actually do any work themselves but provide an interface to calling clients and calls other elements of the system. There can be more than one instance of the User Profile Service Application, but there is a one to one mapping between a Service Application and the User Profile Synchronization Service Service Machine Instance or Share. Point Service. Note The concept of a Service Machine Instance or Share. Point Service i. Services on Server is very badly articulated in general and the name of course is deeply confusing. There is also a Service Connection aka Proxy. This lives within the Share. Point Foundation Web Application Service and allows Service Consumers Web Applications to call the Service Application. User Profile Service A Share. Point Service in Services on Server. This is not a Windows Service, but some. NET assemblies that do some work with profiles and other elements which are not to do with Synchronising of properties. There are no configuration options. This should run on the machine in the farm you wish to use to host the User Profiles Role. When its running that machine is known as the Service Machine Instance. User Profile Synchronization Service A Share. Point Service in Services on Server. This is a wrapper responsible for the provisioning of the Forefront Identity Manager FIM bits. You select a UPS SA to associate with, and need to specify the credentials under which the FIM Services will run. This should run on the machine in the farm you wish to use to host the User Profiles Role. When its running that machine is known as the Service Machine Instance. Forefront Identity Manager A bundled version of FIM that includes two Windows Services, and associated configuration and data. It is not supported to use the FIM client tool but this can be useful for viewing progress and identifying errors. The two FIM services are configured by the User Profile Synchronization Service Share. Point Service rolls off the tongue doesnt it. The FIM Client is located at C Program FilesMicrosoft Office Servers1. Synchronization ServiceUIShellmiisclient. Note For some social Share. Point features we require Search and Managed Metadata Service Applications setup more on that later. For the purposes of this article we have a very simple example scenario. We have two Web Applications intranet. The Intranet application will host our corporate published content and the My application will host My Sites. There is other configuration required and in some cases additional permissions required for complex domain environments. However for the scope of this article everything here is all you need. Preparing the Platform. Before we can administer User Profile Synchronization we must create and configure elements of the supporting infrastructure and Share. Point. We are notgoing to use the Farm Configuration Wizard FCW. The FCW is useful when standing up demo environments and for simple single server solutions, but it is entirely inappropriate for farm deployments and takes a number of shortcuts to provision a basic setup. We are going to do it properly in the same way any real farm deployment would be done. It is assumed that you have installed Share. Point Server 2. 01. Complete mode, and have run the Share. Sean O Connor Game Package Art there. Point Configuration Wizard SCW to create a new Farm using DOMAINspfarm for the Farm Account. DOMAINspfarm is not a domain or machine administrator at this point. Furthermore, once the SCW has completed, you have not run the Farm Configuration Wizard or made any other changes in Central Administration. It is also further assumed that you are not logging onto the server using the Farm Admin account or using it to access central adminUPDATE 0. Also, I assume that you have not used a Fully Qualified Domain Name or IP Address when specifying the SQL Server when running the Share. Point Configuration Wizard PSConfig. Using either is strongly discouraged, and will lead to failures with the provisioning of the User Profile Synchronization service instance. Stick to a Net. BIOS name, or a SQL Server Alias. The order of setting all this up is important, if you do things in the wrong order it will break and you basically need to start over again unless you enjoy tidying up broken apps and ensuring the File system, registry, config db etc is in a good shape. UPDATE 0. 11. 12. While it is not required to get things working, I strongly recommend that you deploy the June or August Cumulative Updates CU. Preferably the August CU, which offers a much easier installation. These contain numerous fixes related to User Profile Synchronization. Install these preferably before creating your Farm using PSConfig. The August CUs are available at KB 2. Share. Point Foundation 2. KB 2. 35. 23. 42 Share. Point Server 2. 01. Create and Configure Accounts and Permissions. The first step is to create some Active Directory accounts which will use as service account identities for Windows Services and Share.