Set up an identity management server: SQL Server 2016 or 2017
Note
Sql Server 2017 setup procedure does not differ from Sql Server 2016 setup procedure.
Note
This walkthrough uses sample names and values from a company called Contoso. Replace these with your own. For example:
- Domain controller name - corpdc
- Domain name - contoso
- MIM Service Server name - corpservice
- MIM Sync Server name - corpsync
- SQL Server name - corpsql
- Password - Pass@word1
Important
MIM 2016 SP2 supports SQL AlwaysOn Availability Group (AoAG) listeners with RegisterAllProvidersIP option set to 0, meaning that SQL Server AoAG cross-subnet failover is not currently supported.
Important
SQL Transparent Data Encryption is supported by MIM Synchronization Service and MIM Service and Portal components with MIM SP2 or later builds.
Install SQL Server 2016 Standard/Enterprise Edition
Launch PowerShell as a domain administrator.
Change to the directory where the SQL Server setup program is located.
Type the following commands.
.\setup.exe /Q /IACCEPTSQLSERVERLICENSETERMS /ACTION=install /FEATURES=SQL /INSTANCENAME=MSSQLSERVER /SQLSVCACCOUNT="contoso\SqlServer" /SQLSVCPASSWORD="Pass@word1" /AGTSVCSTARTUPTYPE=Automatic /AGTSVCACCOUNT="NT AUTHORITY\Network Service" /SQLSYSADMINACCOUNTS="contoso\Administrator"
More info SQL deployment accounts and services can be found here
Note
SSMS is no longer included in SQL 2016. Download details can be found here
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for