This post has been republished via RSS; it originally appeared at: Core Infrastructure and Security Blog articles.
First published on MSDN on May 25, 2018
This document is intended to be used as an operational build document for the Microsoft Identity Management 2016 Synchronization Server installation. You may perform search and replace on the variables listed below to create a detailed build guide customized for your environment.
|Description||Search and Replace Variable|
|The Domain’s common Name.||[Domain]|
|The Offline MIM Synchronization Server’s Common Name.||[Offline Sync Server]|
|The Offline Synchronization Server’s IP Address.||[Offline Sync Server IP]|
|Primary Synchronization Server’s Common Name.||[Primary Sync Server]|
|The Primary Synchronization Server’s IP Address.||[Primary Sync Server IP]|
|The SQL Server’s Common Name.||[SQL Server]|
|The SQL Server’s IP Address.||[SQL Server IP]|
|The Microsoft SQL Server instance name.||[SQL Server Instance]|
|The service account that the MIM Synchronization Service runs under.||[Synchronization Service Account]|
|The Installation account used to perform installation and upgrades of the MIM Synchronization Service Software.||[Install Account]|
|The name of the Synchronization Server Client’s Administrators Security Group.||[Admin Group Name]|
|The name of the Synchronization Server Client’s Operators Security Group.||[Operators Group Name]|
|The name of the Synchronization Server Client’s Joiners Security Group.||[Joiners Group Name]|
|The name of the Synchronization Server Client’s Browse Security Group.||[Browse Group Name]|
|The name of the Synchronization Server Client’s Password Management Security Group.||[PW Group Name]|
Please reference the following document for best practice guidance on MIM Synchronization Server configurations.
In this Synchronization Server build example, we install two Windows 2012 R2 virtual servers. These servers provide for the Primary Synchronization server and an Offline Spare Synchronization Server. Each server should have a minimum of 2 virtual CPUs and 32 Gb of RAM. The two servers in this example have the following disk allocations:
C:\ 100 gb Operating System and Software
E:\ 200 gb MIM 2016, associated management agents and rules extensions.
Please reference the following Microsoft document for best practice guidance on SQL server configuration settings and builds for MIM Synchronization Server.
In this Synchronization Server build example, we install a separated Microsoft SQL Server 2016 instance entitled SYNC.
|Hostname||IP Address (Public)||Description|
|[Offline Sync Server]||[Offline Sync Server IP]||Offline Spare Synchronization Server|
|[Primary Sync Server]||[Primary Sync Server IP]||Primary Synchronization Server|
|[SQL Server]||[SQL Server IP]||SQL Server|
The following new Active Directory domain accounts are needed to support the installation:
|Service Account Name||Usage||Notes|
|[Synchronization Service Account]||Service account for the Synchronization Service with SQL Server Database access.||Deny logon as batch job
Deny logon locally
Deny access to this computer from network
SQL Server Admin Rights to FIMSynchronizationService database.
|[Install Account]||This is the account used to perform the initial installation of the MIM Synchronization Service Software.||We will use this account for the installation in the MIM environment.
Need local admin on Sync server and
Full SQL Admin Rights to create and modify the FIMSynchronizationService database.
Launch Server Manager
Click Add Roles and Features , Next
Select Role-based or feature-based installation, Next
Select .Net Framework 3.5 Features
In the event you are notified that you may need to specify an alternate source path,
select Specify an Alternate source path .
Enter the drive letter for your Windows 2012 R2 Server Install disk and specify \sources\sxs\ as the path. (ex. E:\sources\sxs\)
Select Next, Install
Upon Successful completion
You can download the SQL Client installer (sqlncli.msi) from the Microsoft SQL Server 2012 SP2 Feature Pack located at the following link:
Launch the Microsoft SQL Server 2012 Native Client Installer
On the Welcome to the installation Wizard for SQL Server 2012 Native Client select Next
Review and Accept the License Terms to continue installation
On the Feature Selection window, select Next
On the Ready to Install the Program pane, select Install
Upon successful completion, select Finish
Some popular tools and utilities that you may consider installing include:
- Telnet Client
- Active Directory Users and Computers
- LDAP Client
- SQL Server Management Studio
- Oracle Server Client (If connecting to Oracle database)
The following document is intended to function as an operations guide for the installation of the MIM 2016 Synchronization Server. This document covers both the installation of the Offline Spare and Primary MIM 2016 Synchronization Servers.
The Offline Spare functions as a pre-installed synchronization engine whose MIM service is disabled until needed (re. in the event of failure of the primary synchronization server). The Offline Spare is installed first, followed by the installation of the Primary Synchronization Server.
Only one MIM Synchronization Server may be operational at a time. The Offline Spare and Primary Synchronization Server share a common SQL database (FIMSynchronizationService) that retains all configuration options, source code, and management agent configurations. The database name is defined via the Microsoft Identity Manager installer and should not be modified.
The installation media can be obtained from the Microsoft Customer Portal.
· This installation document covers the installation of a stand-by synchronization server which requires the SQL server database to be hosted on a separate SQL server.
· The SQL Server client will need to be pre-installed on this server prior to installation of the MIM Synchronization Server Software.
· The SQL Server will need to be enabled for remote access.
· The SQL Server and SQL Server Agent services for the instance (Ex. Sync) need to be running.
Active Directory Service Accounts :
· Installation Account with SQL Admin rights.
· Sync Service Account with SQL read/write rights.
· [Admin Group Name]
· [Operators Group Name]
· [Joiners Group Name]
· [Browse Group Name]
· [PW Group Name]
· TCP Port 1433 open between Sync Servers and SQL Server.
o [Primary Sync Server] [Primary Sync Server IP] – [SQL Server] [SQL Server IP]
o [Offline Sync Server] [Offline Sync Server IP] – [SQL Server] [SQL Server IP]
The stand-by synchronization server is installed prior to the primary synchronization server.
Offline Server Build Action:
Login to the Offline Synchronization server [Offline Sync Server] using the Installation Account [Install Account].
Primary Server Build Action:
Login to the Primary Synchronization server [Primary Sync Server] using the Installation Account [Install Account].
Mount the installation Media.
In Windows Explorer navigate to the root of the MIM 2016 installation media and double-click on FIMSplash to begin the installation.
If prompted how to view .htm files, select Internet Explorer .
This will open the MIM installation menu.
Note : This installation guide does not include screen captures of the installation process. If you prefer to view screen shots of the installation, please reference the following link provided below. Please be aware that you will need to return to this document for the remaining steps in completing the installation of the offline spare or Primary Synchronization Server. https://blogs.msdn.microsoft.com/connector_space/2015/08/26/installing-the-microsoft-identity-manager-2016-synchronization-service-clean-install/
Under Identity Manager Synchronization Service , Select Install Synchronization Service
If prompted to allow the program to make changes to this computer, you must select Yes to continue the installation.
Click Next to continue.
Read and accept the terms of the License Agreement.
To continue installation, select Next .
The default Installation Location is C:\program files\Microsoft Forefront Identity Manager\2010\
If you would like to modify the Installation Location, select the Change button, and enter the custom path setting.
Once complete, select Next to continue.
When installing your Synchronization Service with a warm stand-by, you must use a remote SQL Server configuration. The Stand-by and Live Synchronization servers reference the same SQL database.
SQL Server is located on :
Select A remote machine
Then enter the common name of the SQL server [SQL Server]
Note : Installation of the SQL Client is required as referenced in the Prerequisites section of this document.
The SQL Server instance is :
Select A named instance
Then enter the instance name [SQL Server Instance]
Select Next to continue.
Enter the Service account information under which the MIM Sync Service will run:
Service Account: [Synchronization Service Account]
Service Account Domain: [Domain]
Select Next when completed.
When implementing a stand-by synchronization server you should use Domain groups. This ensures your access groups remain consistent after implementing the stand-by server.
Prior to proceeding with the installation, the security groups should be created in Active Directory. You may use any naming convention you like for these groups, or you may choose to retain the default group names (Re. FIMSyncAdmins, FIMSyncOperators, FIMSynchJoiners, FIMSyncBrowse, and FIMSyncPasswordSet).
To configure for use with Domain groups, enter the following information:
Administrator: [Domain]\[Admin Group Name]
Operator: [Domain]\ [Operators Group Name]
Joiner: [Domain]\[Joiners Group Name]
Connector browse: [Domain]\[Browse Group Name]
WMI password Management: [Domain]\[PW Group Name]
Click Next to continue.
Check the box to Enable firewall rules for inbound RPC communications
Select Next , Install
Note : Warning messages are expected as part of the normal installation process. Please pay close attention to any Warning or Error messages received. Actions may differ for Offline Spare vs. Primary Synchronization Server. See details below for specific actions.
Warning 25051 :
Warning 25051. The Microsoft Identity Manager Synchronization Service service account is not secure in its current configuration. For more information about best practices for securing the service account, please see Microsoft Identity Manager Synchronization Service Help.
For Offline Spare and Primary Synchronization Server builds,
Select OK to continue.
To address this issue after installation, please refer to the following documentation:
Error 25009 :
Error 25009. The Microsoft Identity Manager Synchronization Service setup wizard cannot configure the specified database.
For Offline Spare and Primary Synchronization Server builds ,
Select Ok to continue.
The installation will rollback, select Finish .
Verify your installation account has SQL admin rights and the .net 3.5 Components are installed via server manager. Once resolved, you will need to start the installation process from the beginning.
Warning, A Microsoft Identity Manager Synchronization Service database already exists :
A Microsoft Identity Manager Synchronization Service database already exists. If you click Yes, you will restore the configuration with this database. If you click No, you must manually remove the previous database before installation can continue. Do you want to use the existing database?
Offline Spare Server build action only :
If you are building the Offline Spare for the first time, you should not receive this message. Verify you are connecting to the correct SQL server and instance. This could occur if you are reinstalling the synchronization server. In such a case, you will need to manually remove the database from the SQL server to proceed. As a matter of extreme caution, always backup the database before removing it.
Primary Synchronization Server build only :
You should receive the following Warning:
The Microsoft Identity Manager Synchronization Service setup Wizard will restore the configuration using the previous database. You must provide the encryption key set to use the previous database. Do you want to do this now?
Select the encryption key file (ex. E:\MIM\Keys\SyncKeys.bin)
Offline Spare Server build action only:
At this point you will be prompted to back up the database encryption key.
Select a location and enter a name for this key file, then click Save
Primary Synchronization Server build only:
If you installed an Offline Spare, you should not receive this message.
When notified of successful completion,
Click Finish to complete setup.
You must logoff and relogon your system for the security group membership to take effect. Please close the other applications and click Yes if you want to logoff now. You may click No if you want to logoff later.
You should now be able to open the MIM 2016 Sync Service. (Start, Run
To verify the version, click Help and About .
While the trademark is stamped Microsoft Forefront Identity Manager 2010 R2 , the MIM 2016 R1 starts at 4.4.xxxx.x whereas FIM 2010 R2 begins at 4.1.xxxx version.
From the Service management Console,
Right Click Forefront Identity Manager Synchronization Service
On the General Tab, next to Startup Type select Disabled .
If Service Status is “ Running ” select Stop
Select Apply , Ok
Once complete with the Offline Spare build, repeat the build instructions following all steps for the Primary Synchronization Server and skipping those steps noted for the Offline Spare build.
If you have completed the steps for both the Offline Spare and the Primary Synchronization Server, the synchronization server build process is complete.