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?
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?