components that will be required to support that feature set. Record which components will be required in Table A-4 in Appendix A. If multiple feature sets are selected, the components are additive, meaning that if identity management, user profile management, and certificate management functionalities are selected, the FIM Synchronization Service, FIM Synchronization Service database, FIM Service, FIM Service database, FIM Portal, FIM Certificate Management, and FIM Certificate Management database will all be required. However, multiple instances of the services will not necessarily be required because a single instance can be used to provide multiple capabilities. Table 2. FIM Feature Set to Infrastructure Component Mapping and Service on Domain Notification Portal Exchange Service database, on or Portal FIM CM FIM mailbox Change software 2007 and Synchronization FIM Client database (PCNS) Synchronization FIM Service, Password Client Service CM, CM Controllers Functionality FIM Service FIM database, FIM FIM FIM Exchange Password Service FIM FIM and 2010 Identity management X (classic functionality) Password X X X synchronization Password self-service X X O X User profile X X management Group management X X from portal management from X X X X Outlook Declarative provisioning X X Certificate management O O X X = Required O = Optional Step Summary In this step, the infrastructure components that will be required to support the desired feature sets were determined and recorded in Table A-4 in Appendix A.
components that will be required to support that feature set. Record which components will be required in Table A-4 in Appendix A. If multiple feature sets are selected, the components are additive, meaning that if identity management, user profile management, and certificate management functionalities are selected, the FIM Synchronization Service, FIM Synchronization Service database, FIM Service, FIM Service database, FIM Portal, FIM Certificate Management, and FIM Certificate Management database will all be required. However, multiple instances of the services will not necessarily be required because a single instance can be used to provide multiple capabilities. Table 2. FIM Feature Set to Infrastructure Component Mapping Functionality FIM Synchronization Service and FIM Synchronization Service database FIM Service, FIM Service database, and FIM Portal FIM Password Portal FIM Client software FIM Service mailbox on Exchange 2007 or Exchange 2010 Password Change Notification Service (PCNS) on Domain Controllers FIM CM, FIM CM database, and FIM CM Client Identity management (classic functionality) X Password synchronization X X X Password self-service X X O X User profile management X X Group management from portal X X management from Outlook X X X X Declarative provisioning X X Certificate management O O X X = Required O = Optional Step Summary In this step, the infrastructure components that will be required to support the desired feature sets were determined and recorded in Table A-4 in Appendix A.
ipd-forefront-identity-manager-version-1-1.docx