September 15, 2008
Novell® Nterprise™ Branch Office™ 2.0.5 ISO is available to customers who have Upgrade Procetion and is available on the Customer Care Portal to entitled customers after you log in. If you already have deployed Nterprise Branch Office (NBO), you can update your installation using the NetWare 6.5 Support Pack.
This document includes the following information about known issues related to NBO 2.0.software.
For best results, use the following Web browsers:
Windows Clients: Internet Explorer or Firefox
Macintosh Clients: Safari
If you have upgraded NBO to the NetWare 6.5 SP7 or SP8 server, the ISO generated by the image command may not be bootable when installed. You can boot the server using a DOS boot disk, then execute autoexec.bat file.
Instead, use the image command on the SP6 server, then upgrade the server to SP7 or SP8.
Make sure you remove any CDs in the appliance before beginning the imaging process (image command).
Occasionally, a bad CD burn results in miscellaneous installation failures. These issues are seen even when the ISO from the download site is validated and the MD5 values are correct. Sometimes the burn hardware / environment causes corruption in some cases. After burning the NBO 2.0.5 ISO to CD, check the MD5 values of the following files.
Make sure all CDs are removed from NBO appliance during network installations of NetWare® 6.5 Support Pack 5 or upgrade to NBO 2.0.5.
The following updates are included on the NBO ISO that were not included in NetWare 6.5 Support Pack 5:
server.exe – fix out of memory issues during installation
nwpa.nlm – fix to allow some newer hardware to install NBO
rsync.nlm – latest December 22, 2005 contains fixes for customer issues.
fatfs.nlm – Additional fixes for some SCSI configurations.
Script changes – Additional script changes to make IMAGE command worked from a locked NBO console and other Install from NBO CD script fixes.
Before installing the NetWare 6.5 Support Pack on a NBO server, delete any previous backups on c:\nwserver\backspx, where x can be 2 to 4. This prevents the server from running out of disk space on the c: drive during the Support Pack installation, which could cause an abend.
If you are upgrading a Branch Office 2.0 appliance using Support Pack 5, do not use the option or you will lose data.Instead, use the new Support Pack Upgrade feature. Refer to TID number 10088340 where a link is provided to instructions on how to install this feature for use in installing support packs.For more information about this new feature, see “Applying NetWare Support Pack Updates” in the Nterprise Branch Office Setup Guide.
Do not use the as an upgrade process. is intended as a method of backing up, and is not supported as a means to install the patch. If you have already used the feature to install the patch, follow these steps to properly install the patch on your systems:
Acquire the files config.txt, lsmldapx.nlm.lmo, and lcmldapx.nlm.lmo from the NetWare 6.5 Support Pack 5 in \products\nbo\nbo.zip.
At the NBO conole, unlock the NBO by entering unlock, and then entering y to accept the terms and conditions.
Save the files into your sys:\nmas directory.
To install, run the script: nmasint -addmethod -boma sys:\nmas\config.txt
On NBO console, type restart.
The process of copying sp5.zip to the appliance via the Nterprise Branch Office Web Administrator is slow (JVM issue). To more quickly install the Support Pack via the Web Administrator and you don't want to unlock the NBO console to run NWConfig for the upgrade, copy sp5.zip to the data:\softchip directory on the appliance first and unzip the sp5.zip file in that directory before running the option in the Web Administrator.
NBO removes all partitions during imaging/installation even vendor specific partitions on the drive because NBO requires four partitions.
Rsync does not support replicating older Mac files or applications that have resource forks. When Rsync attempts to replicate these files, you receive error -23. If you have an environment where backing up these files is a requirement, you need to use the SMS features of NBO or use a local backup of Rsync.
NOTE:The newer Mac OSX has moved away from using these resource forks, but still supports resource forks.
If you get a -10 error, refer to the volume:\system\rsync.log file for additional information. -10 errors are usually caused by invalid configuration of Rsync. Here are some common reasons for this error:
Replace volume with the actual volume name where you installed Rsync.
Mutual authentication or certificates aren't set up properly.
SSL on both corporate and NBO servers or NON-SSL on both corporate and NBO servers (they can't be different).
You might see one of the following symptoms after attempting mutual authentication:
Web Administrator hangs
The following error appears:
Replication Authentication error. If authentication failures persist, it may be because of stressed WAN conditions. Use Manual authentication instead.
Your NBO and corporate servers are probably on different networks, NBO requires an NDS replica on the corporate server for mutual authentication to function; otherwise, you should use manual authentication as the error message indicates.
By default, eDirectory data is backed up automatically once every 24 hours. If you make any directory changes and then perform an upgrade using the option before the backup process has been run again, you will lose those changes. This includes the creation or modification of user objects.
If you are going to perform a Support Pack upgrade, be sure that you either manually back up the directory before performing the upgrade, or that you perform the upgrade after the regularly scheduled directory backup, which by default is 6 p.m.
To back up the directory, run Rsync. Doing so places a current backup copy of eDirectory on the admin volume.For related information, refer to TID number 10088340.
Rsync is only supported in configurations where NBO communicates to a NetWare, Linux or Windows server.
Defaults in auditing don't report as much as the auditing in the previous version. Make the following changes to the NBO 2.0.5 auditing:
Unlock the NBO console.
At the system console, load audetext.nlm.
Login as supervisor.appuser (tab between fields, don't press Enter until you have entered the password).
Choose .
Exit the utility.
Restart and unlock the NBO.
Using iManager (with the Nsure audit plug-in), log in to NBO as supervisor.
Go to > , and browse to the server object.
Go to the tab and enable the needed events.
WARNING:Don't use the option; otherwise; the network is flooded with audit traffic.
In the NBO Web Administrator, enable Nsure Audit.
If eDirectory 8.8 is on the corporate server side, eDirectory 8.8 functions fine with NBO 2.0.5. NBO is not designed to function with eDirectory 8.8 installed at the NBO office.
Groupwise 6.5 is the post office that is part of the base image installed on the NBO.
The product has been designed to work with the Microsoft JVM. However the JVM is not available from Microsoft any more. You must have previously downloaded it. The Sun JVM 1.3x and 1.4x work with a few issues:
You might need to login twice,
You might not be able to tab between fields,
Screens may not draw out correctly.
Refresh your screen to resolve these or other problems with JVM.
The NBO Web Administrator does not function with any Sun JVM 1.5 or higher. This is a non-issue for the end users and affects only the administrator of the NBO.
In the Web Administrator, certain NICs do not work and the appliance doesn't completely cycle.
To resolve this, unlock the console and finish the inputting the settings on the other console. Toggle back to the NBO console and type “lock” to relock the console.
If you use the NBO 2.0.5 overlay to image a new appliance, Mac OS9 and OSx clients cannot login. To resolve this, you must image the appliance using the shipped NBO 2.0.0, and then update to 2.0.5 via the Web Administrator or NWConfig SP5 upgrade with the appliance unlocked.
Logging in to NBO SP5 presents the standard login screen. You must browse to the NetStorage page to see the NetIdentity login screen.
NBO only supports iPrint Windows clients.
NBO 2.0.5 on the NBO console will have a 4th digit incriminated (such as NBO 2.0.5.1) each time you unlock the console. This can be used to monitor how many times the console has been unlocked.
Virtual team owner accounts have to be configured to allow them to edit the link gadget. To resolve this issue, NBO supervisors must log in to the portal administrator and modify virtual team owner settings.
NBO 2.0.5 installs on VMWARE ESX and GSX. There are no known issues.
The rsync.nlm dated December 22, 2005 are newer than the updates included in NetWare 6.5 Support Pack 5. You can update your NetWare server with these newer versions via installation from the nbo_appliance\central_office\netware\install.exe on the NBO 2.0.5 CD.
SimplePassword NMAS™ Login Method is not installed by default on OES Linux servers. Without this method, users cannot authenticate to NBO via NCP™.You need to install the SimplePassword NMAS Login Method by executing the following command at the server’s terminal prompt:
console:nmastinst -addmethod <admin.context> <treename> /opt/novell/nmasmthd/SimplePassword/config.txt -w <password>
For more information on configuring Replication on NetWare, Linux, and Windows 2000/2003, refer to Novell Documentation.
Improved Hardware Support: NBO 2.0.5 has newer drivers and fixes to address newer hardware platforms that previously were unable to install NBO (Symptom: Pausing for drivers, hangs or reboots during imaging process, etc.).
Rsync.nlm Improvement of replication with fewer error -10 and -30 timeout. rsync.nlm also includes additional customer fixes.
NOTE:It is still possible to get error -10s in invalid setup configurations, incorrect hardware, and switch configuration issues.
Certificates when restoring: When restoring from floppy disk, you no longer need to reimport certificates.
Intruder lockout and home directories: Intruder lockout no longer renames user home directories.
iPrint pop up blocking resolved: The iPrint Client 4.15 or later resolves issues with pop up blocking when installing iPrint printers.
The following sources provide information about Novell Nterprise Branch Office 2.0:
Installation: Novell Nterprise Branch Office Setup Guide
Online product documentation: Nterprise Branch Office 2.0
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 (® , TM, 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 © 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.