I know RC0 could not be installed in a SharePoint farm configuration. But RC1 seems to suggest that it can. Whenever I attempt it fails with: The web application or web site at http://localhost could not be found or the user who install FIM does not have sharepoint admin privilege. Please create web application and web site in http://localhost or grant the user who install FIM sharepoint admin privilege, and then click "Retry". <sic> Is there anything I could be missing in the SharePoint configuration? The only helpful information in the deployment guide is to ensure http://localhost is configured as an alternative mapping for the "default site" (a site created by following the Administrator tasks when first using the Central Administration page I presume). Obviously the account is a Sharepoint admin or it could not have done that. Paul

I'm still struggling with this! There must be a document somewhere that describes how to configure a new SharePoint farm for use with ILM/FIM? There must be a way of getting more information out of the error apart from the dumb message above, or the equally dumb "ended prematurely" message? The later "helpful hint" occurs when only installing the portals, so I can guess it is SharePoint at fault. Any answers?

The advice we, in MCS, are giving (which is based on discussion with the PG but is in no way final) is not to use a WSS farm. There's no real point and it introduces additional overhead and cost (in terms of management). I know this doesn't answer your question but the way I'm deploying with my customers is multiple standalone FIM Portal and FIM Service systems load balanced (in the lab I'm using WLBS; in production I'll be using Cisco HLB). I'm using the concept of an administrative server as a synchronisation service target and the box that polls exchange. I'm then load balancing the user-facing servers and making that URL publically known, i.e. users will be directed at the load balanced hostname and the administrative server will only be known to the few that need it.To answer your question, how have you configured WSS? Have you setup a farm and configured a web application? Have you defined the Farm Administrator and Site Collection administrator and are you running the installation as either or those accounts?

Hi Paul, Thanks very much. It never occurred to me that multiple standalone Portals would give the same effect; and why not, I see now. I did get the damn thing to install but the method seems mumbo-jumbo to me. The farm/site collection administrator is the installer so that was okay. What I did was try not to get too clever with the SharePoint install so as to mimic a "basic" install. But all that seemed to be was to use the NETWORK SERVICE account for the AppPool rather than a specific domain account and to name the top site "Team Site" using the "Team" template rather than the "blank" template. Na, I can't believe it was that either. The other thing that might have had an impact was that previously I'd configured the search database so that I could disable it as required by FIM. This time I didn't bother (why I ever did was a mystery). I also didn't bother telling the FIM install the NLB address (left it as "localhost"). Hum, more mumbo-jumbo me thinks. Maybe I was just more relaxed about it and willing the setup to suddenly show the dreaded "roll-back" like it always did: That probably did it! It was never going to do what I expected it to do. Hang on, when I think about it, I forgot to do the bit to ensure http://localhost is configured as an alternative mapping: The only thing the deployment guide tells you you must do when installing in a farm: Argggh! Paul

Colleague ran into this today trying to patch an install. In his case, modifying this registry value to http://server-fqdn.customer.com from http://localhost did the trick: HKLM\SOFTWARE\Microsoft\Forefront Identity Manager\2010\Portal\BaseSiteCollectionURLMy Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

THANK YOU! I ran into this "http://localhost could not be found" problem while attempting to apply build 3576 on the FIM Service/portal server in my lab. Updating the registry as described did the trick.