FIM 2010 R2 Topology
-
Thursday, February 14, 2013 6:42 AM
I am planing the below topology for FIM 2010 R2 for 3000 users.
Server 1 : App server
The server-side components are as follows:
• FIM Synchronization Service
• FIM Service
• FIM Portal
• FIM Password Registration Portal
• FIM Password Reset PortalServer 2: SQL Database Server
SQL Server 2008 database for the FIM Service.FIM Synchronization Service
SSCM
Reporting toolCan any one please suggets if it is not correct. Or any other way to install all components on the two server.
Thanks
Harry
- Edited by Harry-Harry Thursday, February 14, 2013 6:44 AM
All Replies
-
Thursday, February 14, 2013 7:37 AM
That's probably fine if you're only dealing with 3,000 users. Not too sure about SSCM though.
For larger installs, I'd definitely use a lot more than 2 servers.
- Ross Currie
FIMSpecialist.com | MCTS: FIM 2010
-
Thursday, February 14, 2013 7:47 AM
With SCSM 2010 there is a limitation that you can't install the Service Manager component on the same server as the Data Warehouse component. I'd imagine this problem was addressed in 2012, but I haven't tried it yet.
Piotr
-
Thursday, February 14, 2013 8:35 AM
I have come to know that SSCM 2010 and dataware house should be on two different windows server for reporting purpose. So i am planning to install the SQL database on server 1 also. As we are installing the FIM 2010 R2 only for lab exercise so i think below topology will be fine.
server 1:
Server 1 : App server
The server-side components are as follows:
• FIM Synchronization Service
• FIM Service
• FIM Portal
• FIM Password Registration Portal
• SQL Database for for the FIM Service.FIM Synchronization Service• Datawharehousing
Server 2: SQL Database Server
SSCM
Reporting tool and FIM Password Reset PortalCan you please let me know which is heavy SSCM or dataware house.So that we can plan which software can be installed on which server as we have only two server.
Thanks
Harry
-
Thursday, February 14, 2013 9:04 AM
This should work, but I'd stick with having all the web stuff on one box (as you planned in the first post), and there's no need to install SQL on that box.
If I only had two boxes, I think I'd stick everything FIM'ish on the first one (including FIM Reporting component as it has to be installed on a server with FIM Service), and keep the other box as SQL and host all the databases there. SCSM SM on the first one, and SCSM DW on the second SQL one.
If it's a lab environment you could put all the DBs on one SQL instance, but for production it's best to at least put the SCSM SM and DW databases on separate instances.Piotr
- Edited by Piotr PaczochaMicrosoft Employee Thursday, February 14, 2013 9:04 AM

