We have two virtual servers hosted by a third party. Initially we installed SharePoint 2010 Beta on, which we very soon removed and installed SharePoint 2010 RTM. Currently SharePoint 2010 seems to work just fine, and we have no user problems whatsoever. Nevertheless, we've gotten a few reports from our virtual server provider that the FIMSynchronizationService fails to start on the frontend. I digged a little into it, and found that it concerned Forefront Identity Manager Synchronization Service. Or at least that is my assumption. In Services on the frontend, I found two services: Forefront Identity Manager Service Forefront Identity Manager Synchronization Service What was interesting, was that both had startup set as 'Disabled'. In addition, FIM Service is set to log on as 'Local System', while the FIM Synchronization Service was set to log on as '\'. Furthermore, there should apparently be some groups and users related to this FIMservice. I could not find these neither in AD nor on the local users and groups on the frontend. What are these groups? Moreover, I tried to start miisclient on the frontend, and the splash screen reveals that it concerns Forefront Identity Manager 2010 Releace Candidate 1. I get a simple error saying that it is unable to connect to synchronization service. We don't suspect we'll be needing the functionality from FIM, but it'd be still nice to get some background information why this is broken. We suspect that it is a harmless remnant of the SharePoint 2010 Beta installation. Can you confirm our suspicion, or supply with further information regarding how to fix this if needed?

I would suggest that you remove the installation of FIM 2010 RC1 (It appears to be broken) and install the RTM version. This should fix any issues with service accounts, service startup, and the like. -Jeremy

SharePoint 2010 ships with Forefront Identity Manager for User Profile Synchronization. User information from AD will be synchronized from AD (or other LDAP source) to your SP installation. If you did not configure UPS in SharePoint, those services will be disabled. They will appear broken since they have not been configured. The UI will say RC1 even in SP 2010 RTM. They use a full supported pre-release of FIM2010. /AndreasThis posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/copyright.htm

Ah.... Seems I missed the point entirely. We are discussing a FIM component that is bundled with Sharepoint. Is there any documentation on this, howit works, the intended purpose, etc..... -J

http://technet.microsoft.com/en-us/library/ff382639(office.14).aspx /AndreasThis posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/copyright.htm

Am having the same issue outlined here.. In my case, I configured the user profiles following the article http://technet.microsoft.com/en-us/library/ee721049.aspx and it was working just file. I was able to see the users importing from AD to SPS 2010. Looked good. And I saw those 2 Forefront services started as mentioned in the article. But today I needed to change some filtering on the User Profile, so went to the User Profile Mange Application Services" and when clicked on the "Configure Synchronization Connections", found out it's missing the connections. and then found out 2 Forefront services are disabled but they have the service acct associated with them. We had this problem with the BETA. We configured this SPS 2010 from scratch ( new OS windows 2008 R2) and installed SPS 2010 RTM. Hoped the problem has been fixed. The above article says don’t start those Forefront Services manually. So, wondering what's our option here to make user profile connection re appear and be able to edit those? Thanks in advance.

MONIR - I am facing the exact same issue. DId you manage to resolve this?