How do I create or reinstall an ADAM instance on a Primary or Secondary 8.5 and later server? (NETIQKB72804)

  • 7772804
  • 10-Feb-2011
  • 20-Mar-2013

Environment

Directory and Resource Administrator 8.5.x

Directory and Resource Administrator 8.6.x


Situation

How do I manually create or reinstall an ADAM instance on a Primary or Secondary 8.5 and later server?

How do I manually create an ADAM instance on a Primary or Secondary server?

How do I reinstall an ADAM instance?

How do I manually create a primary ADAM instance?

How do I manually create a secondary ADAM instance?

ADAM Instance fails to create during initial installation of, or upgrade to, Directory and Resource Administrator 8.5 & 8.6

ADAM Installed on the Directory and Resource Administrator server, but failed to create the instance.

Resolution

Open Add/Remove Programs and locate the ADAM instance name specified during the installation or upgrade of DRA 8.5 / 8.6 and remove the instance. If you are reinstalling ADAM on ALL DRA Servers, remove all secondary instances of ADAM BEFORE the primary instance (located on the Primary DRA Server). If the ADAM instance being removed is not the only ADAM instance in the server, recycle the ADAM service (typically called DRASecureStorage) on all other servers hosting ADAM instances to clear the entry from the configuration partition to avoid replication errors.

Prior to starting the steps below, STOP the NetIQ DRA Administration Service on the DRA Server. If this instance will be on the Primary DRA Server follow this process, if this instance is being created on a Secondary DRA Server, skip this process and proceed to the next portion of the article beginning with Creating a Replica instance on a Secondary DRA Server.

  1. Stop the DRA Service
  2. Open the registry on the Primary DRA Server and navigate to:
    • HKLM\Software\WOW64Node <Only Used for 64bit OS>\Mission Critical Software\OnePoint\Administration\Modules\Server Configuration\ADAM Configuration\
      • Set ADAMInstallationFlag to 1
      • Set AdminAccount to the Domain Local Security Group that contains the ADAM Administrators
      • Set AQSchemaExtensionsFlag to 0
      • Set AQSchemaExtensionVASupportFlag to 0
      • Set InstanceCreationFlag to 1
      • Set InstanceName to the EXACT name to be used during manual instance creation. (Note: This should be a different name than the previous name if a reinstall of ADAM is being done)
      • Set LDAPPort to the EXACT port you will enter during manual instance creation.
      • Set RootContainersFlag to 0
      • Set SHConfigRootContainersFlag to 0
      • Set SHConfigSchemaExtensionsFlag to 0
      • Set SSLPort to the EXACT port you will you will use during manual instance creation.
      • Set VASchemaExtensionsFlag to 0
    • Next Update the following regsitry Key:
      • HKLM\Software\WOW64Node <Only Used for 64bit OS>\Mission Critical Software\OnePoint\Administration\Data\Modules\Server Configuration\PrimaryAdamConfiguration
      • Set PrimaryInstanceStatusFlag to 1
  3. Browse to the DRA installation folder (<install drive>\Program Files (x68) <Note the X86 is used for 64bit OS>\NetIQ\DRA) and create a new empty folder named exactly what you wish the new ADAM instance is to be named (i.e. DraSecureStorage1)

  4.  Navigate to Start-Programs-ADAM and Select Create an ADAM Instance (Windows 2003) OR Start-Programs-Administrative Tools-Active Directory Lightweight Directory Services Setup Wizzard (Windows 2008)

  5. Select a Unique Instance <next>

      • Enter the EXACT instance name you specified in the registry and in the folder you created. <next>
      • Enter the EXACT LDAP and SSL ports you specified in the registry. <next>
      • Select 'Yes, create an application directory partition".
      • Enter the partition name of DC=DRA,DC=COM . <next>
      • Change the Data Location to the path of the empty folder you created in the DRA directory.
      • Recovery files can be placed at any location you choose, or left at the default. <next>
      • Select Network Service Account. <next>
      • Select "This Account" and enter the Domain Local Security Group that contains the ADAM Administrators. <next>
      • Select "Do not import LDIF files for this instance of ADAM". <next>
      • Review the summary and check for any mistakes.  <next>
  6. Start the ADAM Service

Creating a Replica instance on a Secondary DRA Server.

If the ADAM Instance that you are creating will be a Replica ADAM instance residing on a Secondary DRA Server, follow the steps below

  1. Prior to beginning this process, uninstall all ADAM instances on the Secondary via Add/Remove Programs.

  2. Open registry on the DRA Secondary Server

  3. Update the following Regsitry Keys under HKLM\Software\WOW64Node <Only Used for 64bit OS>\Mission Critical Software\OnePoint\Administration\Modules\Server Configuration\ADAM Configuration\ :

      • Set the Instance Creation Flag to 0

  4. Log on to the Primary DRA Server and expand the Configuration Management node and select Administration Servers

  5. Select the Primary DRA server and right click on it.

  6. Choose Synchronize - Full Refresh

Once the synchronization is complete, ADAM should be recreated on your primary and secodary servers.

Cause

Directory & Resource Administrator 8.5x
Directory & Resource Administrator 8.6x

Additional Information

Formerly known as NETIQKB72804

If you are using Virtual Attributes and / or Custom Queries within DRA, these will be DELETED once the Primary ADAM instance is removed.

Once the DRA Service is stopped Assitant Admins will not be able to use DRA while connected to the specfic DRA server being modifed.

Once the ADAM creation / reinstallation process has been completed, the status can be verifed from the DRA server as follows:

Connect to the Delgation and Confiuration console of the each DRA server as a DRA Admin

  1. Highlight the Configuration Tree
  2. From the right hand side window, choose Update Administration Server Options
  3. From the Update Administration Server Options windows, click the ADAM Confiuration
  4. Verfiy that all settings are True / OK

Also if ADAM has been recreated on the Primary DRA, you will need to verify the Reporting Services Configuration as well.

 


Feedback service temporarily unavailable. For content questions or problems, please contact Support.