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

Create a new organizational unit

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

The existing organizational units (for example OU=Systems, OU=OASySDNA) can hold objects of any class (oasysdnaCSystem). However, if a new Organizational Unit is needed to organize objects for a newly created class, then the following procedure can be executed.

To create a new organizational unit

  1. Using an installer account, start the ADSIEdit Microsoft management control snap-in (typically located at C:\Windows\System32\adsiedit.msc).

  2. If ADSIEdit is not configured to display OASySDNA Core, then:

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

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

    3. Select Select or type a Distinguished Name or Naming Context in the Connection Point section and enter OU=OASySDNA.

    4. Set the Name to OASySDNA Core.

    5. Select OK.

  3. Select OASySDNA Core in the ADSI Edit left hand panel, then expand it to show OU=OASySDNA.

  4. To create a new OU (Organizational Unit):

    1. Right-click OU=OASYSDNA and select New > Object. Choose to create an OrganizationalUnit, then select Next.

    2. Assign the common name as the Value (for example GlobalProjectSettings) then select Next.

    3. Optional: Select More Attributes if you want to set the description attribute or another attribute.

    4. Select Finish to complete the creation of the OU.

  5. If you want the OU to be modifiable by users that are not installers, then the OU's access control rights must be configured. Still using the installer account, start a command shell (run as an Administrator), then use the dsacls program to set the general access (GA) permission. For example, the following command allows control access to users with DNA Permission - Security_Administration membership so that they can add/delete/modify objects in OU=GlobalProjectSettings, OU=OASySDNA: c:\windows\adam\dsacls.exe \\localhost: 55002\OU=GlobalProjectSettings, OU=OASySDNA /I:T /G "CN=DNA Permission- Security_Administration, OU=Permissions, OU=OASySDNA":GA.