Separating roles
If we look at all the FIM features we are about to install, we need to understand that in theory, we might be able to put them all in one box. But, that is not practical, and in some cases is not even supported by Microsoft.
The example setup I use in this book, for The Company, can be used as a starting point.
Databases
As you will see, you will need quite a few databases. Depending on load and other factors, you can choose to install the databases locally on each box hosting a FIM feature or choose to have them all in a central Microsoft SQL server. Or, you can even mix the two approaches.
If you find that your initial approach was not optimal, don't be alarmed. Moving the databases is fully supported. In this book I will use so-called SQL aliases when referencing the databases; one reason for this is that it will make moving the databases simpler.
The System Center Service Manager Data Warehouse, required by the FIM Reporting feature, is usually using a separate SQL server.
FIM features
As with the databases, the FIM features can also be co-located or separated. The only issue here is that FIM Certificate Management should not be co-located with other parts of FIM. The main reason for this is that the FIM CM setup and configuration tool will think it owns its local web server (IIS). If you have other FIM features using IIS on the same box, you will get a conflict.
Also, the System Center Service Manager used for Reporting requires separate servers. Read more about that at http://aka.ms/SCSM2010Deployment.
If I were to give you all the possible scenarios for the ways you could separate the FIM features, in order to get fault tolerance, performance, and so on, I would have to add some 50 pages just to cover that topic. I suggest you take a good look at the Microsoft TechNet site ( http://aka.ms/FIMPlanning), to find out how your company should separate or co-locate different parts.
In this book, The Company is using a design that can easily be expanded if the need arises. If you find that your company requires much better performance or maybe that you would only use part of the product or co-locate more services, this book will still be valid when it comes to the requirements and the setup procedures.