Novell Open Workgroup Suite Small Business Edition 2.0 Issues Readme

January 5, 2009

1.0 Documentation

The following sources provide information about Novell® Open Workgroup Suite Small Business Edition 2.0 (NOWS SBE 2.0):

2.0 Known Issues

To check the version of the server, run rpm -q simba. The version number is helpful information to include when posting bugs or service requests.

The server log is located in /var/log/simba/server.log. Be sure to include information from the log when posting bugs or any service requests.

2.1 Installation

2.1.1 Planning for Existing Data

IMPORTANT:Verify that there is no data on the disk prior to installing the NOWS SBE 2.0 server. If you install NOWS SBE 2.0 on hardware that has an existing data partition, all data on the drive is removed, and all partitions are overwritten. 

For suggestions on how to manage installation with existing data, see TID 3733516.

2.1.2 License Keys

When you are at the license key page during installation, either enter all three license keys at once or none of them.

If your license key fails, make sure that Rug is activated. To do so, use /etc/init.d/novell-zmd restart to log in to the console on the command line.

2.1.3 NOWS SBE 2.0 Passwords

Passwords with special characters are not supported in NOWS SBE 2.0.

2.1.4 YaST and NOWS SBE 2.0

If you install NOWS SBE 2.0 with YaST, the Web-based tools are no longer supported.

2.1.5 Installing Xen

IMPORTANT:Novell does not currently support NOWS SBE virtualization in Xen.

When installing as a Xen* guest, you have the option to choose either full virtualization or paravirtualization. Choose full virtualization. Not doing so causes your install to fail.

2.1.6 MD5 Checksum

Because corrupt burns and downloads might occur, it is important that you double-check the MD5 checksum to verify that it is valid.

2.1.7 Unconfigured Server Root Password

The root password on a server that is not yet configured is novell.

2.1.8 Installing without a DHCP Server

If you don’t have a DHCP server, set your IP address at the Network Configuration window during autoYaST. If you miss this step, follow this procedure:

  1. Log in to the server console as root. There is no password at this point.

  2. Right-click the console screen and select Open Terminal.

  3. Enter yast to launch the YaST configuration utility.

  4. Select Network Devices > Network Card.

  5. Click Change > Edit, then specify a static IP address and the subnet mask.

  6. Select Host Name and Name Server and specify the hostname, domain name, and name server (DNS) addresses.

  7. Select Routing and specify a default gateway.

  8. Click OK > Finish > Quit to exit YaST.

  9. Enter init 6 to reboot the server.

  10. Upon reboot, the console screen specifies the address to begin the Web configuration. On the Network Settings page of the Web configuration, specify all of this information again.

2.1.9 DNS and DHCP Configuration

The DNS and DHCP components do not provide a tool for making configuration changes. You can uninstall DNS or DHCP and then reinstall to change the configuration, or you can simply make the changes manually.


  • Edit the Zone files under /var/lib/named/master

  • To start or stop, use /etc/init.d/named start/stop

  • For additional information, use man named


  • Edit /etc/dhcpd.conf

  • To start or stop, use /etc/init.d/dhcpd start/stop

  • For additional information, use man dhcpd, man dhcpd.conf, or man dhcpd-options

2.1.10 iManager Configuration

If you click a link on the administration page and non-essential tasks appear in iManager, role-based services in iManager haven’t fully started. All components are functional, but only future logins appear in the simplified interface.

2.1.11 HylaFAX Modem Configuration

Your modem needs to be configured in YaST before you install HylaFAX*.

2.2 eDirectory

The following are issues specific to eDirectory™.

2.2.1 eDirectory Existing Tree Synchronization

If you install eDirectory into an existing tree, your NTP time needs to be synchronized with the existing tree.

2.2.2 eDirectory Remote Manager Login

The Novell Remote Manager login is the root user and password.

2.2.3 eDirectory Install Errors

If you install eDirectory and an error displays, the installer returns to the eDirectory install start page. To begin troubleshooting, go to the install log on the server, see what happened, and try again. The common issue is that ndsconfig failed.

2.2.4 eDirectory Passwords

If you install eDirectory into an existing tree that contains passwords with special characters, you need to change these passwords to ones that do not have special characters.

2.2.5 eDirectory Password Validation

If you install eDirectory into an existing tree with a bad password, you might not be notified of the error. You need to check the install log to validate your successful install

2.2.6 eDirectory Advanced Install

If you choose to install eDirectory Advanced with NCP™, create the NCP directory first.

2.2.7 Uninstalling eDirectory

Uninstalling eDirectory from an existing tree requires additional cleanup in the existing tree. See the Novell eDirectory documentation.

2.3 Migration

The NOWS SBE 2.0 server allows you to create NCP volumes on Linux* file systems (NSS volumes are not available). For more information about migrating data from a traditional NetWare® server to a NOWS SBE 2.0 Linux server, see TID 3219860.

2.4 File Systems

2.5 Installing Novell Storage Services

This section describes how to manually install Novell Storage Services (NSS).

The simplified Novell Storage Services File System configuration described in the following procedure is not supported with NOWS SBE 2.0.

IMPORTANT:Before you begin, you need these two items:

  • Before installing NSS, use the NOWS SBE 2.0 administrative GUI to install eDirectory, then install iManager and Samba

  • You must have an uninitialized or logical disk available. It can contain no other mounted partitions. This configuration cannot be performed on the disk that contains either root (/) or swap.

  1. Log in as root to the server via SSH, or start the NSSMU console utility, then enter the following commands:

    1. Enter rug in novell-nss nss-kmp-default novell-nss-admin-session-openwbem-provider novell-nssfileversionutility-clients

    2. Enter chkconfig novell-nss on

    3. Enter /etc/init.d/novell-nss start or enter rcnovell-nss start

    4. Enter nssAdminInstall -a <admin name> -p <admin password> -o <nss admin object name>

    5. Finally, enter ndssch -t <tree_name> <admin_FDN> /opt/novell/sch/nssfs.sch

  2. Log in to iManager.

  3. In the Roles and Tasks column, select Storage > Devices.

  4. In the Devices window, select the uninitialized or logical disk to be used and click Initialize Disk.

  5. Read the warning message that appears. If you choose to proceed, click OK. This returns you to the iManager Administration page.

  6. In the Roles and Tasks column, select Storage > Pools. A new pool window appears.

  7. Name your pool, then click Next. Another New Pool window appears.

  8. Select your device and assign its space, then click Finish. This returns you to the iManager Administration page.

  9. In the Roles and Tasks column, select Storage > Pools. Confirm that your new pool is in the Pools column.

    Younow need to create a new volume in iManager.

  10. In the Roles and Tasks column, select Storage > Volumes to display the Volumes window.

  11. Click New to create a new volume.

    A New Volume window appears, prompting you to enter you new volume name.

  12. Name your volume, then click Next.

    Another New Volume window appears, prompting you to select a pool and volume quota.

  13. Fill in the appropriate information, then click Next.

    A final New Volume window appears, prompting you to fill in attribute information.

  14. Fill in the appropriate information, then click Finish.

You have successfully created a new disk, pool, and volume; NSS is now operational.

For additional information about installing NSS, see TID 3733516

2.6 VPN Access from SLED 10

If you are using a SLED 10 desktop and your VPN installation fails, you need to configure VPN access manually.

  1. Click the NetworkManager icon > VPN Connection > Configure VPN > Add > Forward > OpenVPN Client > Forward > Import Saved Configuration > CtrlL.

  2. In the Location box, enter ~/.keys.

  3. Click Open.

  4. Select your .pcf file.

  5. Click Open > Forward.

You should now have VPN access.

2.7 Site-to-Site VPN Access

NOWS SBE 2.0 does not provide a configuration tool for site-to-site VPN access, but you can set up this access manually.

For additional information about VPN setup, see TID 3165776.

2.8 Novell Clients

Use the versions of clients that ship with NOWS SBE 2.0 and are available in Desktop Downloads. These clients have been tested and verified to work properly with the server components on the system.

2.9 Helpdesk E-Mail Address

After Helpdesk installation is complete, you must create an e-mail account to notify Helpdesk users of the status of their incidents. The e-mail account can be set up in GroupWise® or an alternative e-mail server.

NOTE:The helpdesk username is helpdeskadmin.

2.10 Simba Commands

The NOWS SBE 2.0 interface is built by using Simba*, which is an application server similar to Tomcat or JBoss*. However, Simba is designed specifically for system installation and administrative tasks.

  • Simba files are located in the /var/lib/simba folder.

  • To stop Simba, use the following command: /etc/init.d/simba stop

  • To restart Simba, use the following command: /etc/init.d/simba start

  • The Simba server troubleshooting log is located at /var/log/simba/server.log

2.11 Creating an iFolder User

If you create a user after installing the Novell iFolder® component, iFolder might require up to 24 hours to recognize the user. To update the iFolder more quickly, go to the iFolder Administration page and click System > LDAP. Under the LDAP tab, click Update > LDAP > Synchronize Now. This forces iFolder to enable new users.

2.12 Changing an OES2 Linux Server’s IP Address

For complete information, see Changing an OES2 Linux Server’s IP Address

3.0 Open Source Code

Novell, hereby, offers to give any third party a complete machine-readable copy of the source code of Amanda, Clam, DLU, HylaFAX, Mailscanner*, OpenVPN*, and TightVNC, which are delivered as part of Novell Open Workgroup Suite Small Business Edition, under the terms of Sections 1 and 2 of version 2 of the GNU General Public License as published by the Free Software Foundation, on a medium customarily used for software interchange.

4.0 Documentation Conventions

In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (®, ™, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark