The Novell Samba components can be installed at the same time as Open Enterprise Server, or they can be added to an OES server after the initial installation.
NOTE:These instructions assume you are using the default graphical user interface for SLES 11 (GNOME) and installing from a network installation source. If you are using the ncurses (text) version of YaST, these instructions provide only an approximate guide through the interface. If you are installing from CDs, insert them when prompted.
To install Novell Samba as part of an initial OES server installation, follow the general instructions in OES 11 SP2: Installation Guide. Take note of the following Samba-specific guidelines as you go through the installation:
When installing an OES server for Novell Samba, the hostname you specify for the server must be shorter than 13 characters in length. The NetBIOS name for Samba is limited to 15 characters, including the “-W” that is appended to the hostname automatically, which leaves 13 characters for the hostname.
WARNING:If you enter a hostname that is longer than 13 characters, the Novell Samba setup truncates the NetBIOS name to 15 characters. As a result, iManager won’t be able to find the associated server and group objects. If you need to change the NetBIOS name, see Section B.2.3, Changing the NetBios Name.
Be sure to select the Novell Samba pattern when you are specifying what software you want to install on the server, along with any other OES Services patterns you need for your implementation.
When you reach the OES Configuration portion of the install, follow the instructions in Section 3.2.3, Configuring LUM and Novell Samba to configure LUM and Samba correctly for OES 11 SP2.
To install Novell Samba on an existing OES 11 SP2 server:
Log in to the server as the root user.
Start YaST by clicking> (located in Favorite Applications).
If you don’t already have the OES 11 SP2 software installed as an add-on product, select> and follow the on-screen prompts to specify the location of your OES 11 SP2 installation media.
Under OES Services, select.
SMS, LUM, and NRM are automatically selected as well. Select any other patterns you need for the server (such as iManager and NSS), then click.
When prompted, clickto install Novell Samba and related RPMs.
If prompted for the eDirectory Admin user password, enter it and click.
Continue with Section 3.2.3, Configuring LUM and Novell Samba.
The proper configuration of both LUM and Novell Samba is critical to the successful implementation of Samba on an OES server.
In the first LUM configuration screen, review the default settings and make any necessary changes.
The UNIX Configuration object is created in the default context shown. You can specify a different location for the Unix Configuration object, but the default should suffice in most implementations. There is one configuration object per eDirectory tree.
By default, the UNIX Workstation object is created in the same context as the OES 11 SP2 server’s NCP Server object. It is recommended that you leave this setting at the default.
(Optional) If you want to specify a proxy user for LUM, enter a username with context and a password.
(Optional) If you want users to have read and write access to each others’ home directories, deselect theoption.
This option is selected by default, which restricts read and write access to home directories for users other than the owner. The default selection changes the umask setting in /etc/login.defs from 022 to 077.
In the second LUM configuration screen, select the PAM-enabled Linux services you want to enable for LUM and Samba users.
The only service selected by default is sfcb. If you want eDirectory users to be able to run Linux commands such as login, ssh, and so on, you must enable the services by selecting them in this list.
To select a service, click the checkbox next to its name.
Clickto select all services in the list.
Clickto deselect all services in the list.
In the Samba configuration screen, specify theand proxy user settings.
By default, the Base Context is set to the context (eDirectory container) where the tree admin user is created. Typically, this is the Organization (O) container, and users are created in Organizational Unit (OU) containers beneath the O container.
If your Samba users are (or will be) located in the same container as admin or in a subcontainer of that container, you do not need to change this setting. Otherwise, specify a container in your tree that is at the same level or above the container where the Samba users will be created.
The proxy user is an eDirectory user that has rights to search the tree for Samba users.
The Novell Samba configuration suggests a default proxy user for Samba (cn=server_name-sambaProxy,o=org). If you want to use a different eDirectory user as the proxy user, specify the username in typeful format (for example, cn=proxy_user,ou=users,o=novell) and enter a password for the user.
If you specify a new user that does not already exist in eDirectory, the user is created and assigned the necessary rights and the password you specify here.
If you specify an existing eDirectory user, it is assumed that you have already assigned the user the necessary rights and no modification is made to the user.
If you specify an existing eDirectory user but specify a new password, you are prompted to change the password for that user.
Follow the on-screen prompts to continue with the OES configuration. When it is completed, clickto close YaST.
Now that LUM and Novell Samba are installed and configured, you must create eDirectory users and give them access to Samba shares on the OES server.
For instructions, refer to Section 7.1, Creating eDirectory Users for Samba.