There are also obvious implications for clustering because the CPL settings for clustered nodes must
match. For example, if an unmodified OES 2 SP1 node is clustered with an unmodified OES 2 SP2
node, their CPL settings will conflict and one of the nodes must be modified.
For more information about cross-protocol locking, see
NCP
Server" in the
OES 2 SP3: NCP Server for Linux Administration
1.3.6 Domain Services for Windows Installation
The DSfW installation has been rearchitected with a focus on usability and simplicity.
1.3.7 Java Console for DNS/DHCP
The Java Console for DNS/DHCP management is now available for Linux.
1.3.8 Performance Increases
AFP, NCP, and Samba all have improved performance in OES 2 SP2.
1.3.9 Pure-FTPd
Gateway parity with NetWare.
1.3.10 Upgrading Online
Support for upgrading through the SP Channel is included. For more information, see
Patch Channel to Upgrade
1.3.11 Windows 7 Client Support
OES 2 SP2 service clients are supported on Windows 7.
1.4 New in OES 2 SP1
Section 1.4.1, "YaST Install Changes," on page 19
Section 1.4.2, "Novell AFP," on page 20
Section 1.4.3, "Novell CIFS," on page 20
Section 1.4.4, "Novell Domain Services for Windows," on page 21
Section 1.4.5, "Migration Tool," on page 21
1.4.1 YaST Install Changes
The default behavior of the option to use eDirectory certificates for HTTPS services changed in
OES 2 SP1.
In OES 2, eDirectory certificates were only used by default if you were installing a new server.
(Online)" in the
OES 2 SP3: Installation
"Configuring Cross-Protocol File Locks for
Guide.
Guide.
"Using the
What's New or Changed
19