Accelerators with IFD

I would like to know if these Accelerator work with IFD deployments? Most specifically, Event Management and eService.

I have looked at the eService Install doc and it suggests that you need to setup ASP.Net Membership but does not state where it is to be run. We have two CRM application servers load balanced. does it need installing on both? Also I notice in the install video
the CRMWeb user is a copy of the domain admin, is this nesseccary? if so why?

I have many more questions but I'll stop there for now and look forward to a responce.

They will work in IFD environment. You just need to change the authentication to SPLA rather than AD. Haven't tried it myself but aparantly that's all it takes.

No need to have CRMWeb as a copy of admin. For the demo, this is the quickest and definate way of ensuring the user being used has all the relevant permissions. In fact, in the real world, you would create Roles for the web user that only provided
access to the entities exposed and nothing else.

I would guess ASP.Net Membership only needs to be on the server that is hosting the eService website. That's where the "membership" resides. The ASP.Net Membership stores the usernames and passwords for the contacts that have access to
crm. If the Membership login is valid, enter crm as CRMWeb.

Still getting up to speed with it all myself so I look forward to more learned responses.

Do you need to use IFD if you want external contacts to be able to sign into and create cases with the e-service?

No, that's not absolutely necessary, but it depends on where you host the portal web site. The public-facing web portal that you create obviously needs to be 'internet facing' but web users have no direct connection with the CRM server, so your CRM installation
can be a straight 'on premise'. The devil is always in the details.

Again a quick question, Can eService be installed on a seperate server, other than CRM App and CRM DB Server...

The eService accelerator has some custom components that must be installed on the CRM server. The public-facing eservice portal web site can be installed on a different server, though. In fact, it probably should be..

You have to use the Discovery service to search for an identify the correct organization, then you ask it for an authentication token against that org. The token that you receive must then be used by the CrmService for any requests, instead of AD credentials.
Obviously, you can find full details in the CRM SDK.