Configuring Data Archiver to use Active Directory Service Interface

About this task

By default, the Data Archiver tries to enumerate all the available domain controllers during startup. If a Primary or Backup Domain Controller cannot be located when the Historian Data Archiver service starts, access to Historian is denied to all users. Also, when you have domain controller machines spread across a wide area network (WAN), you may find that logins are successful but slow.

With the Active Directory Support feature, you can configure the Data Archiver to use a different set of Windows calls called Active Directory Services Interface (ADSI) when using Historian security. Configuring the Data Archiver to use Active Directory Services Interface (ADSI) allows you to:

  • Log in to the Historian even if the Data Archiver is unable to enumerate any domain controllers during the Data Archiver startup.
  • Access a Backup Domain Controller if a Primary Domain Controller is not available temporarily or permanently.

You should configure the Data Archiver to use Active Directory Services Interface (ADSI) only when the Data Archiver fails to enumerate domain controllers.

You can determine whether or not the Data Archiver is able to locate a domain controller by viewing the data archiver.shw log file. In the data archiver.shw log file If "Group Server #01:" is empty, then the Data Archiver is unable to locate a domain controller.
Security Settings
=================
 Group Mode : GLOBAL
 Use Client Windows User for Logon : TRUE
 Security Domain : <your domain>
 Group Server #01 :

The following procedures provide guidelines for configuring the Data Archiver to use Active Directory Services Interface (ADSI) calls.