To auto-populate the domain_krb.properties file, the connector attempts to find domain controllers that are at the same site so there is minimal latency between the connector and Active Directory.

About this task

To find the site, the connector determines the subnet on which it resides, based on its IP address and netmask, then uses the Active Directory configuration to identify the site for that subnet. If the subnet is not in Active Directory, or if you want to override the automatic subnet selection, you can specify a subnet in the runtime-config.properties file.

Procedure

  1. (Linux virtual appliance) Edit the /usr/local/horizon/conf/runtime-config.properties file.
    1. Log in to the virtual machine as the root user.

      For an on premises deployment with no external connectors, log in to the service virtual machine. If you are using an external connector for the directory, log in to the connector virtual machine instead.

      For a SaaS deployment, log in to the connector virtual machine.

    2. Edit the /usr/local/horizon/conf/runtime-config.properties file to add the following attribute.

      siteaware.subnet.override=subnet

      where subnet is a subnet for the site whose domain controllers you want to use. For example:

      siteaware.subnet.override=10.100.0.0/20

  2. (Windows server) Edit the installDir\IDMConnector\usr\local\horizon\conf\runtime-config.properties file to add the following attribute.

    siteaware.subnet.override=subnet

    where subnet is a subnet for the site whose domain controllers you want to use. For example:

    siteaware.subnet.override=10.100.0.0/20

  3. Save and close the file.
  4. Restart the service.

    For a Linux virtual appliance, use this command:

    service horizon-workspace restart