Create each of these accounts as normal Users and choose the expiry options (never expire, user can’t change password).We need to grant the Replicating Directory Changes permission on the domain to the DOMAIN\spups account.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.“Stuck on Starting”: Common Issues with Share Point Server 2010 User Profile Synchronization An IIS Application which sits in the Share Point Web Services IIS Web Site. 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). The Service Application Endpoint has three associated back end databases and other configuration.Install these preferably before creating your Farm using PSConfig.The August CUs are available at: The first step is to create some Active Directory accounts which will use as service account identities for Windows Services and Share Point Application Pools.
Furthermore, once the SCW has completed, you have not run the Farm Configuration Wizard or made any other changes in Central Administration.In which case you also need to configure the Service Application (after creation, details in a later step).To provision the UPS service – we must make the DOMAIN\spfarm account a local administrator of the box hosting the UPS service. Don’t try and work around this – you won’t succeed!We are *not* going 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.