Cool Solutions

NOWS 2.5 admin / sbsadmin fail to perform administrative tasks


April 7, 2010 5:34 pm





Problem Statement:

Cannot Perform eDirectory administrative tasks as admin & sbsadmin in 64bit NOWS 2.5.

Intended Audience:

Test Engineers, Consultants, NTS and Customers who need to administrate eDirectory using iManager in NOWS 2.5

Problem Description

admin and sbsadmin of NOWS are not allowed to perform any administrative tasks listed under “eDirectory Maintenance” plug-in of iManager bundled in NOWS 2.5 64bit. The Error is shown in the screen shot below.

Click to view.

Fig 1: eDirectory Backup failure

As per the error message, RBS is not configured to perform this action. Even after configuring RBS for admin and sbsadmin to perform eDirectory Maintenance tasks, backup and other operations fails consistently. One more issue uncovered is admin and sbsadmin are not LUM enabled as shown in the screen shots below.

Click to view.

Fig 2: Linux Profile of admin

Click to view.

Fig 3: Linux Profile of sbsadmin


The issue here is admin and sbsadmin are not LUM enabled by default and hence though the RBS is configured, unable to perform any administrative tasks.

Following are the steps to address this issue.

  1. LUM enable admin and sbsadmin using the Linux User Management plug-in of iManager as shown in the below screen shots.

    • Login to iManager as admin.
    • Go to Linux User Management –> Enable users for Linux.

      Click to view.

      Fig 4:

    • From object selector, select admin and sbsadmin.

      Click to view.

      Fig 5:

    • Select the sbsadmins group as existing eDirectory group of which admin and sbsadmin are members.

      Click to view.

      Fig 6:

    • Select the UNIX workstation object to which admin / sbsadmin should have access and click next, to complete LUM enabling.

      Click to view.

      Fig 7:

    • Confirm admin and sbsadmin are LUM enabled by checking the Linux Profile by logging in to NRM as shown below.

      Click to view.

      Fig 8: After LUM enabling admin

      Click to view.

      Fig 9: After LUM enabling sbsadmin

  2. Configure Role Based Services for admin and sbsadmin using iManager as shown below.

    • Login to iManager and click the Configure button in the iManager tool bar.
    • Select Role Based Services –> RBS configuration.

      Click to view.

      Fig 10:

    • Select NEW –> Collection and Setup.

      Click to view.

      Fig 11:

    • Provide name for the role based service and the container in which to create RBS.

      Click to view.

      Fig 12:

    • Select the modules to be installed and scope for the RBS.

      Click to view.

      Fig 13:

    • Modules installed successfully.

      Click to view.

      Fig 14:

  3. After completing the RBS configuration try backup / restore or any other operation to confirm admin / sbsadmin has rights to perform that operation.

    • Perform Backup and Restore operations using iManager –> eDirectory Maintenance –> Backup as shown in the below screen shots.

      Click to view.

      Fig 15:

    • Verify the server and port details.
    • Start the backup process by clicking on the start button.

      Click to view.

      Fig 16:

    • Backup completed successfully.

      Click to view.

      Fig 17:

  4. Perform Restore operation.

    • Go to iManager –> eDirectory Maintenance –> Restore.
    • Verify the server details and provide if missing.

      Click to view.

      Fig 18:

    • Provide Backup file and log file details and start restore operation.

      Click to view.

      Fig 19:

      Click to view.

      Fig 20:

      Click to view.

      Fig 21:

    • Restore operation completed successfully.
0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.