General Information

This chapter contains general information about the NetWare^® 6 release.

For information about additional issues discovered after the release, see the Novell^® Support Knowlegebase and enter TID #10064501.

NetWare 6 Contents

The NetWare 6 package consists of the following:

Operating System CD

Client CD

Documentation CD

NOTE: We welcome your feedback about the completeness, accuracy, and accessibility of the NetWare 6 documentation. Please send your comments to webdoc@novell.com with NetWare 6 in the subject line.

MP-Enabled Components

The following core NetWare 6 components are MP-enabled:

Core operating system

ODI^TM (including LSL^TM, LAN, TSM^TM, MSM^TM, HSM^TM)

TCP/IP

NCP/IP

Winsock (including NILE and BSD)

CLIB BSD calls

Novell Storage Services^TM file system

Novell eDirectory^TM, including LDAP

Novell JVM for NetWare

Novell Modular Authentication Service (NMAS^TM)

Novell Cluster Services^TM

NetWare Enterprise Web Server

NetWare Web Search

NetWare FTP Server

Scripting products (NSN, Perl, and UCS)

All other NetWare 6 components included with this release function in an MP environment.

Compatibility with Other Novell Products

The following Novell products are compatible with NetWare 6:

Account Management 2.1 for Windows 2000

DirXML^TM 1.01

GroupWise^® 5.5 Enhancement Pack 3 and GroupWise 6

iChain 1.5 and 2.0

Novell BorderManager^TM 3.6 Support Pack 1a

Novell Internet Messaging System^TM (NIMS^TM) 2.6 and 3.0

Novell OnDemand Services^TM 1.0

Novell Portal Services 1.0

Novell Single Sign-on 2.1
If you install Novell Single Sign-on to a NetWare 6 server that is not an SD Key Server and you select No when prompted to make the server an SD Key Server, you may see messages indicating that Novell Single Sign-on did not successfully install. The messages and entries in the log file (sys:system\sssi.log) falsely indicate that the SD Key Client and Secret Store Service were not installed successfully.

Despite these messages, SSS.NLM is correctly installed, the schema is extended, and Novell Single Sign-On should function properly in the tree.

Novell ZENworks^TM for Desktops 3.0 Support Pack 1 and Novell ZENworks for Desktops 3.2

Novell ZENworks for Servers 2 with the latest Support Pack
There are some compatibility issues using NetWare 6 with ZENworks for Servers 2. For an explanation of the issues and their resolution, see the ZENworks for Servers 2 online documentation.

NetWare 5.1 Products Not Included in NetWare 6

NIAS components that enable NetWare to function as a WAN or RAS (dial-up) gateway

If you are upgrading from a previous version of NetWare, your INITSYS files might need to be edited to remove WAN components that are autoloaded.

Novell Servlet Gateway
This functionality is now provided by the Tomcat servlet engine.

IBM* WebSphere* application server
This has been replaced by the Tomcat servlet engine. If you are using a previous version of WebSphere on NetWare, you can use the WebSphere-to-Tomcat migration utility included with NetWare 6. For instructions on using the utility, see Migrating from WebSphere to Tomcat in Getting Results with Novell Web Services.

Collabra News Server and Novell Media Server
During an upgrade from a NetWare 5.1 server, these products are removed without warning.

Client DOS Utilities

Many DOS utilities have been removed from NetWare 6. The following utilities are still included for your convenience, but they are not supported:

CAPTURE

FILER

LOGOUT

MAP

NCOPY

NDIR

NetWare Administrator

NLIST

NPRINTER

RIGHTS

International Issues

Euro Character. There are several places throughout Netware 6 where the euro character is displayed as its hex value "[20AC]". This happens because the server code page does not support some of the newer extended characters, including the euro. Although the hex value of the euro is displayed in a few locations, the integrity of the object containing the euro character should remain intact.

Web Page Encoding Issue. To properly display international text in your Web browser, the proper Code Page must be selected for that language. From the main browser menu, click View > Encoding. Then select the proper Code Page for the language you want to display. If the correct Code Page is not selected, you might see question marks or corrupted text.