Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

TABLE OF CONTENTS

Extend AD LDS schema

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedApr 24, 2025
  • 2 minute read

AVEVA Enterprise SCADA AD LDS schema can be extended. However, once a class or attribute has been added, it cannot be deleted or modified. Therefore, you must plan your extensions before executing this procedure.

To extend AD LDS schema

  1. Create a copy of %DNAInstallRoot%\Common\config\ADLDS\ADLDSSchema_Example.xml, and assign it a project-specific file name within the %DNADataRoot%\Common\config\ADLDS directory.

  2. Edit the new file. If you use Visual Studio or an XML editor, then you will see any XML errors and be able to get assistance in creating the new elements.

  3. Read the comments in the file in order to understand the elements and attributes that must be specified. After the comment block, you will find some example class and attribute definitions. You can copy these example elements or create your own. If you copy the examples, ensure that Deactivated is set to 0 to enable the creation of the new class or attribute.

  4. For each NewAttribute and NewElement, assign the OIDExtension attribute according to the directions in the header comment block.

  5. For each NewAttribute and NewElement run GUIDgen.exe (it is provided as a Visual Studio tool). Copy the new GUID into the element’s SchemaIDGUID attribute.

  6. Log in as a user that belongs to the DNA Installers group (for example the dnaInstaller user).

  7. On the desktop, double-click the Windows PowerShell for DNA shortcut.

    Windows PowerShell for DNA opens.

  8. Execute the following commands:

    set-silo Common

    DNAExtendADLDSSchema

    To see the list of options, run the above command with the –h option. The typical execution is: DNAExtendADLDSSchema –f <nameOfSchemaXMLfile>.

  9. To verify that the changes have correctly taken place, use the ADSIEdit Microsoft management control snap-in (C:\Windows\System32\adsiedit.msc).

    1. Right-click on the ADSI Edit text in the left hand panel and select Connect to.

    2. Select the Computer section’s Select or type a domain or server and enter the server name and port configured for AD LDS (for example localhost:55002).

    3. Select Select a well known Naming Context: in the Connection Point section and select Schema.

    4. Set the Name: to OASySDNA Schema, then select OK.

    5. The left hand panel should now contain OASySDNA Schema. Expand it to show the CN=Schema,… folder. Select the folder in order to display the schema elements in the right hand panel.

    6. Scroll down the right hand panel to view the classes and attributes that exist in AD LDS and find the ones added for the project. Double-click on an object in order to verify its properties (for example verify that an attribute’s oMSyntax shows the correct data type; verify that a class’s mayContain shows the list of attributes that you added to the class).

  10. If you created a new AD LDS class, then continue to the Creating a Configuration Assembly for a New AD LDS Class section. If you added attributes to an existing class, then skip to step Creating a NMC Extension to Support AD LDS Extensions.