Article
article
Reads:
4484
Score:
LUM Enabling SLED Workstation to use OES2 Server
Adding a SLED Workstation to the Tree
- On the SLED machine start YAST -> Software -> Software Management -> search for novell-lum rpm and Install.
- After the rpm is installed, go to Security, then Users tab in YAST, and click the "Linux User Management" option.
- During configuration of Linux User Management, select Remote server and enter the IP address of the master server in the OES2 tree under Directory server address. Under the Admin name with context, enter the LDAP Admin name and context. This is the fully distinguished name of a User object with administrative rights to LDAP (For example: cn=admin,o=novell) and enter the Admin password and click Next.
- Under the Linux/Unix config object, enter the eDirectory context where the Linux/UNIX Config object is created. Under the LUM workstation context, enter the eDirectory context (existing or created here) for the LUM (SLED) Workstation object created by the install for this server and click Next.
- Select the PAM enabled services for authenticating LUM users and click Finish. When complete, it will put a "Unix Workstation - <sledboxname>" object into the tree.
- When LUM enabling a user, assign them to a group, if that group lists this new object as an available unix workstation, then that LUM enabled user would have rights to login to that SLED workstation. If you remove that unix workstation object from the assigned group the user is in, then their rights to the SLED workstation have been removed.
Now the Admin user and the LUM enabled user should be able to login to the workstation
Note: If the SLED workstation has to be joined to more than one tree, it gives the error, "Error: Specified partition root and Partition root in the NDS configuration file doesn't match." The /etc/nam.conf file points to the first tree you add. If it needs to be pointed to a different tree other than the tree you initially ran the configuration against, you can workaround the problem by stopping namcd, deleting nam.conf, and rerunning namconfig.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
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, test, test before you do anything drastic with it.
Related Articles
User Comments
- Be the first to comment! To leave a comment you need to Login or Register
- 4484 reads
0