January 5, 2009
The following sources provide information about Novell® Open Workgroup Suite Small Business Edition 2.0 (NOWS SBE 2.0):
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.
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.
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.
Passwords with special characters are not supported in NOWS SBE 2.0.
If you install NOWS SBE 2.0 with YaST, the Web-based tools are no longer supported.
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.
Because corrupt burns and downloads might occur, it is important that you double-check the MD5 checksum to verify that it is valid.
The root password on a server that is not yet configured is novell.
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:
Log in to the server console as root. There is no password at this point.
Right-click the console screen and select .
Enter yast to launch the YaST configuration utility.
Select > .
Click > , then specify a static IP address and the subnet mask.
Select and specify the hostname, domain name, and name server (DNS) addresses.
Select and specify a default gateway.
Click > > to exit YaST.
Enter init 6 to reboot the server.
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.
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.
DNS:
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
DHCP
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
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.
Your modem needs to be configured in YaST before you install HylaFAX*.
The following are issues specific to eDirectory™.
If you install eDirectory into an existing tree, your NTP time needs to be synchronized with the existing tree.
The Novell Remote Manager login is the root user and password.
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.
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.
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
If you choose to install eDirectory Advanced with NCP™, create the NCP directory first.
Uninstalling eDirectory from an existing tree requires additional cleanup in the existing tree. See the Novell eDirectory documentation.
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.
A simplified Novell Storage Services™ (NSS) File System configuration is not supported with NOWS SBE 2.0. If you want to install NSS manually, see Section 2.5, Installing Novell Storage Services.
For additional information about Samba, see the OES Planning and Implementation Guide “Overview of File 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.
Log in as root to the server via SSH, or start the NSSMU console utility, then enter the following commands:
Enter rug in novell-nss nss-kmp-default novell-nss-admin-session-openwbem-provider novell-nssfileversionutility-clients
Enter chkconfig novell-nss on
Enter /etc/init.d/novell-nss start or enter rcnovell-nss start
Enter nssAdminInstall -a <admin name> -p <admin password> -o <nss admin object name>
Finally, enter ndssch -t <tree_name> <admin_FDN> /opt/novell/sch/nssfs.sch
Log in to iManager.
In the column, select .
In the window, select the uninitialized or logical disk to be used and click .
Read the warning message that appears. If you choose to proceed, click . This returns you to the iManager Administration page.
In the column, select . A new pool window appears.
Name your pool, then click . Another window appears.
Select your device and assign its space, then click . This returns you to the iManager Administration page.
In the column, select . Confirm that your new pool is in the column.
Younow need to create a new volume in iManager.
In the column, select to display the window.
Click to create a new volume.
A window appears, prompting you to enter you new volume name.
Name your volume, then click .
Another window appears, prompting you to select a pool and volume quota.
Fill in the appropriate information, then click .
A final window appears, prompting you to fill in attribute information.
Fill in the appropriate information, then click .
You have successfully created a new disk, pool, and volume; NSS is now operational.
For additional information about installing NSS, see TID 3733516
If you are using a SLED 10 desktop and your VPN installation fails, you need to configure VPN access manually.
Click the NetworkManager icon > .
In the Location box, enter ~/.keys.
Click .
Select your .pcf file.
Click > .
You should now have 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.
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.
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.
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
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 > . Under the tab, click > > . This forces iFolder to enable new users.
For complete information, see Changing an OES2 Linux Server’s IP Address
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.
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
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2007-2008 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed on the Novell Legal Patents Web page and one or more additional patents or pending patent applications in the U.S. and in other countries.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.