Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Using the SQL Management Console

...

 In → In the SQL Management Console, select New Query and enter the script below; replace the placeholders accordingly.

...

Adding Users and a Group to the Windows Domain

...

 Make → Make sure that your Windows domain contains users who have the following permissions:

...

Info

Note: If the AD user you are going to use to connect to the Microsoft SQL Server already has an SQL login entry, or is in a group with login access, you can skip this step and continue with Configuring the UMS User, Schema, and Database Permissions.

Using the SQL Management Console

...

Using the SQL Management Console

...

 In → In the SQL Management Console, select New Query and enter the script below; please note the following.

...

  1. In SQL Server Management Studio, open the database that was created in Creating the UMS Database.

  2. Under Security > Users, right-click New User.

  3. Under General, search for your login name (<ad_user>) and give the user a name.

  4. In the Membership area, give the user the db_owner role.

  5. Go to Security > Schemas and right-click on New Schema.

  6. Search for the <ums_user> as the Schema owner and provide a Schema name.

  7. Under Security > Users in your UMS database, double-click on the <ums_user>.

  8. Under General, set the default schema to <schema_name>.

  9. Under Security > Logins > Users, double-click on the <ad_user>.

  10. In the User Mapping area, check the mapping of the UMS database, the user, and the default schema.

...

  1. Log into the UMS Server with the credentials configured for connecting to the UMS database on the Microsoft SQL Server.

  2. Open services.msc and right-click the IGEL Remote Manager Server service.

  3. Select Properties and navigate to the Log On tab.

  4. Select This Account and use the Browse button to find the one that owns the SQL database.

  5. Depending on whether you are using a single server or a cluster for your Microsoft SQL database, continue with Connecting the UMS to the Database (Single Server Instance) or Connecting the UMS to the Database (Cluster)

Connecting the UMS to the Database (Single Instance)
Anchor
ADNativeAuthConnectSingle
ADNativeAuthConnectSingle

Note

Before configuring the connection, perform the following:

  1. Right-click the UMS Administrator (for example, in the start menu) and select Run as different user from the context menu.

  2. Authenticate with the SQL AD Service Account.

  3. Log into the UMS server as the SQL AD Service Account.

  4. Run the UMS Administrator.

  1. In the UMS Administrator, set up a new SQL Server AD Native type data source.

  2. Edit the data as follows:

    • Host: The Fully Qualified Host Name (FQDN) of the Microsoft SQL server. If you deploy MS SQL Server Always On Availability Groups, enter the domain name of the Always On Availability Group listener.

    • Port: The port on which the Microsoft SQL Server listens for requests. (Default: 1433)

    • Schema: The database schema

    • Database / SID: The database name 

    • JDBC Parameter (double-click): 

      • sendStringParametersAsUnicodefalse

      • trustServerCertificatetrue

  3. Select your database configuration and click Activate.

Connecting the UMS to the Database (Cluster)
Anchor
ADNativeAuthConnectCluster
ADNativeAuthConnectCluster

Note

Before configuring the connection, perform the following:

  1. Right-click the UMS Administrator (for example, in the start menu) and select Run as different user from the context menu.

  2. Authenticate with the SQL AD Service Account.

  3. Log into the UMS server as the SQL AD Service Account.

  4. Run the UMS Administrator.

  1. In the UMS Administrator, set up a new SQL Server Cluster AD Native type data source.

  2. Edit the data as follows:

    • Host: The Fully Qualified Host Name (FQDN) of the Microsoft SQL server

    • Port: The port on which the Microsoft SQL Server listens for requests. (Default: 1433)

    • Schema: The database schema

    • Database / SID: The database name

    • Instance:  The instance for your Microsoft SQL Server Cluster 

    • JDBC Parameter (double-click): 

      • sendStringParametersAsUnicodefalse

      • trustServerCertificatetrue

  3. Select your database configuration and click Activate.

...