OES2 SP2 Novell Open Enterprise Server 2 Oes Readme Copy
User Manual: Novell Open Enterprise Server 2
Open the PDF directly: View PDF 
.
Page Count: 44
| Download | |
| Open PDF In Browser | View PDF |
Readme - Beta 3 Novell ® Open Enterprise Server 2 SP2 June 12, 2009 www.novell.com OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 AUTHORIZED DOCUMENTATION 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. See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals. Copyright © 2009 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 (http://www.novell.com/company/legal/patents/) and one or more additional patents or pending patent applications in the U.S. and in other countries. Novell, Inc. 404 Wyman Street, Suite 500 Waltham, MA 02451 U.S.A. www.novell.com Online Documentation: To access the latest online documentation for this and other Novell products, see the Novell Documentation Web page (http://www.novell.com/documentation). novdocx (en) 13 May 2009 Legal Notices For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners. novdocx (en) 13 May 2009 Novell Trademarks novdocx (en) 13 May 2009 4 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 Contents About This Readme 9 1 Frequently Asked Questions 11 2 What’s New 13 2.1 2.2 2.3 New in Beta 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New in Beta 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.2 CIFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.3 DNS/DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.4 Domain Services for Windows (DSfW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.5 iFolder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.6 iPrint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.7 Linux User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.8 Migration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.9 Novell Cluster Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.10 Novell Storage Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.11 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New in Beta 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.1 AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.2 CIFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.3 DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.4 iFolder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.5 iPrint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.6 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Getting Started with OES 2 SP2 3.1 3.2 3.3 Installing OES 2 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.1 Minimum 256 Colors Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2 Before Installing a Migration Target Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.3 Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.4 64-Bit eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.5 64-Bit NCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the DNS/DHCP Java Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1 Installing the Java Console on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2 Installing the Java Console on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Service Issues 4.1 4.2 Installation/Upgrade Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1 Apply the Latest Patches Before Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.2 Do Not Upgrade to eDirectory 8.8 Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.3 If Apache Fails to Start After You Upgrade QuickFinder . . . . . . . . . . . . . . . . . . . . . . 4.1.4 Incompatible TLS Configurations Give No Warning . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.5 Installing from the IPP Page Fails After Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.6 Storage-Related Plug-Ins Must Be Uninstalled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.7 Upgrading a 64-Bit Installation Breaks Some Novell Products . . . . . . . . . . . . . . . . . Apple Filing Protocol (AFP) Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 13 13 13 14 14 14 14 15 15 15 15 16 16 16 17 17 17 17 18 19 19 19 19 19 19 19 20 20 20 20 21 21 21 22 22 22 22 23 23 24 Contents 5 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.2.1 Server Registration Doesn’t Happen through Bonjour. . . . . . . . . . . . . . . . . . . . . . . . CIFS Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.1 Cross-Platform Junctions Not Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2 Junction Target Changes Require Restarting the Windows Client . . . . . . . . . . . . . . 4.3.3 Duplicate CIFS Share Names for NSS Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.4 Configuring LDAP with Secure Channel Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.5 Performance Degradation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributed File Services (DFS) Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.1 Failure Creating a Management Context with Two Replicas . . . . . . . . . . . . . . . . . . . 4.4.2 Hard Links Are Not Supported in a DFS Move/Split Volume Operation . . . . . . . . . . 4.4.3 Specifying Non-Default VLDB Database Paths on Replica Sites . . . . . . . . . . . . . . . DNS/DHCP Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.1 Java Console Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.2 DNS-Specific Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.3 DHCP-Specific Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . eDirectory Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.1 eDirectory Not Starting Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iFolder Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iPrint Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8.1 Installing the Printer Agent on Macintosh Workstations Requires Mozilla Firefox . . . 4.8.2 64-Bit Mozilla Firefox Can’t Install Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8.3 Client Installation on SLED 11 Appears to Fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8.4 System PPD Upload Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8.5 Creating the Driver Profile Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8.6 Vista 64-Bit Driver Not Being Associated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8.7 Printers Are Re-Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8.8 Driver Upload Not Working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NSS Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.1 Monitoring Compression Might Cause the System to Reboot . . . . . . . . . . . . . . . . . . 4.9.2 Startup Conflict with McAfee LinuxShield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.3 Unable to Change the Lookup Namespace on a Clustered Volume . . . . . . . . . . . . . 4.9.4 Unable to Rename the Volume Mount Point with Shared Volumes. . . . . . . . . . . . . . Samba Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10.1 Using Samba to Open a File with BATCH_OPLOCK Fails . . . . . . . . . . . . . . . . . . . . Security Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.11.1 All LUM Users Can Administer QuickFinder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storage Management System (SMS) Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Xen Virtualization Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.13.1 Server Fails to Boot After Installing OES 2 SP 2 Linux on a Xen-Based VM . . . . . . 5 Migration Tool Issues 5.1 5.2 5.3 5.4 5.5 5.6 5.7 6 ID Transfer Migration Requires a Pre-Migration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Migration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Migration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File System Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1 File System Migration Fails for NetWare Servers Identified by IP Address . . . . . . . . 5.4.2 Directory Consolidation Is Case-Sensitive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iPrint Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.1 iprntman Doesn't Handle ACL Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.2 ZENworks Print Policies Break During Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows Migrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . For More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OES2 SP2: Readme - Beta 2 24 24 24 25 25 25 25 25 25 26 26 26 26 26 27 27 27 27 27 27 27 28 28 28 28 28 28 28 28 29 29 29 29 29 29 29 30 30 30 31 31 32 32 32 32 32 32 32 33 33 33 novdocx (en) 13 May 2009 4.3 6.1 6.2 6.3 6.4 6.5 6.6 Installation and Configuration Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.1 Installing DSfW by Using AutoYaST Makes Invalid LDAP Calls . . . . . . . . . . . . . . . . Provisioning Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing a DSfW Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMC Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.1 Copying a User Object from the MMC Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.2 Users Must Change Their Own Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compatibility with Other Novell Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DSfW Interoperability Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.1 ZENworks Endpoint Security Management 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.2 GroupWise 8.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6.3 Novell SecureLogin 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Caveats 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.10 AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.1 User Credential Synchronization with eDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.2 Anti-Virus Solutions and AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.3 OpenOffice 3.0 Is Required for File Locking on Macintosh Workstations . . . . . . . . . CIFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.1 CIFS Server Can’t Co-exist with Samba Daemons and DSfW . . . . . . . . . . . . . . . . . 7.2.2 Changing the Server IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.3 Number of Shares Hosted on the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.4 Proxy User Creation Depends on the Existing Password Policy . . . . . . . . . . . . . . . . 7.2.5 Trustee Assignments for Files/Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.6 Proxy User Credential Synchronization with eDirectory . . . . . . . . . . . . . . . . . . . . . . 7.2.7 Using a Preexisting Cluster Pool for CIFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DNS/DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.1 DNS Credential Change in OES 2 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DSfW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4.1 Time Must Be Synchronized or Name-Mapped Installation Fails . . . . . . . . . . . . . . . Installation and Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.1 Java and Other Conflicts Displayed During an Upgrade from OES 2 Linux . . . . . . . 7.5.2 The Tree Admin Is Not Automatically Granted Rights for Server Administration. . . . 7.5.3 VNC Install Fails to Set the IP Address in /etc/hosts . . . . . . . . . . . . . . . . . . . . . . . . . Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6.1 Storage Error in iManager When Accessing a Virtual Server . . . . . . . . . . . . . . . . . . 7.6.2 Truncated DOS-Compatible Short Filenames Are Not Supported. . . . . . . . . . . . . . . LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.7.1 Subtree Search Times Out (Bad XML Error) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.8.1 Limitation for Restoring an NCP POSIX Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSANDS Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.9.1 Single Object/Partial Restore from a Full or Subtree Backup . . . . . . . . . . . . . . . . . . 7.9.2 TSANDS Does Not Connect to eDirectory Running on a Non-Default NCP Port . . . Xen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.10.1 Backing Up a Xen Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . novdocx (en) 13 May 2009 6 Domain Services for Windows Issues 35 35 35 35 36 36 36 36 36 37 37 37 37 39 39 39 39 39 40 40 40 40 40 41 41 41 41 41 41 41 42 42 42 42 42 42 43 43 43 43 43 43 44 44 44 44 Contents 7 novdocx (en) 13 May 2009 8 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 About This Readme The information in this Readme applies to Novell® Open Enterprise Server (OES) 2 SP2 Beta 3 and contains the following sections: “Frequently Asked Questions” on page 11 “What’s New” on page 13 “Getting Started with OES 2 SP2” on page 19 “Service Issues” on page 21 “Migration Tool Issues” on page 31 “Domain Services for Windows Issues” on page 35 “Caveats” on page 39 About This Readme 9 novdocx (en) 13 May 2009 10 OES2 SP2: Readme - Beta 2 Where’s NetWare? Novell® Open Enterprise Server 2 SP2 does not include NetWare®. Anyone who wants to test NetWare in an OES 2 SP2 environment should download NetWare 6.5 SP8 from the Novell download site. Frequently Asked Questions 11 novdocx (en) 13 May 2009 1 Frequently Asked Questions 1 novdocx (en) 13 May 2009 12 OES2 SP2: Readme - Beta 2 This section summarizes the new features introduced in each of the Novell® Open Enterprise Server (OES) 2 SP2 Beta releases. 2 Section 2.1, “New in Beta 3,” on page 13 Section 2.2, “New in Beta 2,” on page 13 Section 2.3, “New in Beta 1,” on page 16 2.1 New in Beta 3 The following services have new features introduced in Beta 3. 2.2 New in Beta 2 The following services have new features introduced in Beta 2: Section 2.2.1, “AFP,” on page 13 Section 2.2.2, “CIFS,” on page 13 Section 2.2.3, “DNS/DHCP,” on page 14 Section 2.2.4, “Domain Services for Windows (DSfW),” on page 14 Section 2.2.5, “iFolder,” on page 14 Section 2.2.6, “iPrint,” on page 14 Section 2.2.7, “Linux User Management,” on page 15 Section 2.2.8, “Migration Tool,” on page 15 Section 2.2.9, “Novell Cluster Services,” on page 15 Section 2.2.10, “Novell Storage Services,” on page 15 Section 2.2.11, “General,” on page 16 2.2.1 AFP AFP service discovery by network Mac* clients using the Bonjour* protocol Cross-protocol file locking support for Novell AFP users who access Novell Storage Services (NSS) volumes Lower CPU utilization Bonjour support for Mac OS 10.5 2.2.2 CIFS Cross-protocol file locking support Distributed File Services (DFS) support 10% performance improvement What’s New 13 novdocx (en) 13 May 2009 What’s New 2 The Java* Console Management Utility is now supported on Linux*. 2.2.4 Domain Services for Windows (DSfW) “Install Changes” on page 14 “Beta 2 Testing Scope” on page 14 Install Changes Beta 2 features a new DSfW install. Installation and configuration are now handled in a two-step process: A YaST install that prepares the server and the tree for Domain users. This part of the process features restructured installation screens. A Provisioning GUI, which is a separate utility that configures the DSfW server and supporting services, and completes the installation process. Beta 2 Testing Scope For this release, Novell recommends testing Domain Controllers (FRD) and Child Domain Controllers. Additional Domain Controllers (ADC) are not ready to be tested in Beta 2. When installing DSfW in an existing eDirectoryTM tree setup, map only OU units to domains. Other mappings are not supported in Beta 2. 2.2.5 iFolder Novell iFolder® server integration with Active Directory* that automates admin and proxy user creation 2.2.6 iPrint Auto driver/profile update Bi-directional driver profiles1 This is available only with HP* and Xerox* drivers and is intended for evaluation purposes only. Your feedback is welcome. Client support for Windows* 7 Client for SUSE® Linux Enterprise Desktop (SLED) 11 Banner support for iPrint Direct Scripted support for ZENworks® 7 and ZENworks Configuration Management 10 iPrint policies after migrating the server to OES 2 SP1.1 The Linux and Macintosh* iPrint clients now support the following: Auto-removal of printers on clients if they are removed from the server.1 14 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 2.2.3 DNS/DHCP novdocx (en) 13 May 2009 Printer redirection.1 Automatic driver updates.1 1 Indicates features that have received only basic testing and are expected to be hardened in a future Beta release. 2.2.7 Linux User Management Allow namcd to cache updates only 2.2.8 Migration Tool File System Migrations Migration of non-English directories and trustees Uninterrupted migration for cluster volumes 2.2.9 Novell Cluster Services MPK Removal 2.2.10 Novell Storage Services “NSS Management Enhancements” on page 15 “NSS Utility Enhancements” on page 15 “RAID 0+1 and RAID 5+1 Support” on page 16 NSS Management Enhancements NSSMU has improved response in multi-disk environments NSSMU and iManager can take an extremely long time to list devices and do various other things when the server has multiple devices. This is because of how information is read from EVMS. To address this, the management code has been modified to support multiple devices. The NSS management pieces can now use a single request to get the needed information about multiple devices, thus avoiding multiple evms_open_engine() calls. NSS Utility Enhancements The enhancements included with Beta 2 are: The attrib and rights commands now have an option to work with link files. NSSComp now includes an NSS compression screen for OES 2 Linux There is now an nss command on OES 2 Linux The NSS utility can now monitor compression statistics for a volume) The mirror status command is now available on OES 2 Linux. What’s New 15 information, etc. and these are also listed in the ? help. A new quota utility is included for setting user and directory quotas. RAID 0+1 and RAID 5+1 Support Support for RAID 0+1 and RAID 5+1 has been added in Beta 2. 2.2.11 General No performance decrease in AFP, CIFS, NCPTM, or NSS Cross-protocol locking (CIFS, AFP, NCP) 2.3 New in Beta 1 The following new services were introduced in Beta 1: Section 2.3.1, “AFP,” on page 16 Section 2.3.2, “CIFS,” on page 17 Section 2.3.3, “DNS,” on page 17 Section 2.3.4, “iFolder,” on page 17 Section 2.3.5, “iPrint,” on page 17 Section 2.3.6, “Migration,” on page 18 2.3.1 AFP Dynamic Volume Event Detection: The AFP server now dynamically detects volume add/ mount events, volume delete/umount events, and volume updates on the OES 2 server. A reload is not required when there is a change in the list of volumes mounted on the server. New Configuration Option: EXPORT_ALL_VOLUMES is now a valid option in the afptcpd.conf file. If the option is set to yes (the default), the AFP Server uses all of the available volumes on the machine. If the option is set to no, only the volumes listed in the afpvols.conf file are exported by the AFP Server. afpvols.conf Changes: This file now acts as a resource for alias names and for the list of volumes to be used. Cluster Enabled Volumes Display: When a Mac client connects to the physical IP assigned to the AFP server, the local volumes and the cluster-enabled shared volumes are exported to the client. However, if the client connects to the cluster (virtual) IP, only the cluster-enabled shared volumes associated with the cluster IP are exported. Alternate Guest Account Name: This capability removes the restriction to have one preconfigured guest account. With OES2 SP2, any valid eDirectoryTM user account name with appropriate privileges can be specified as a guest account name. 16 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 Additional options are now available in NSSCON for quitting, displaying the next line of novdocx (en) 13 May 2009 Cross-Protocol Lock Configuration Management Change: Cross-protocol lock configuration is now managed centrally in the ncpserv.conf configuration file. 2.3.2 CIFS CIFS now supports cross protocol locking of the Share mode and byte range locks with AFP and NCP. To enable cross-protocol locking, enter the following at a terminal prompt: # ncpcon set "CROSS_PROTOCOL_LOCKS=1" To disable cross-protocol locking, enter the following at a terminal prompt: # ncpcon set "CROSS_PROTOCOL_LOCKS=0" To see if cross-protocol locking is enabled or disabled, enter the following at a terminal prompt: # ncpcon set Listing more than 255 shares from the Windows client is now supported. 2.3.3 DNS Deletion of Empty Resource Records(RRs): dns-maint -d is an option in the DNS maintenance utility that lets you delete the empty Resource Records of zones in eDirectory tree. You can delete the empty RRs of a list of zones by specifying a command line parameter or by using a zone list in the locator object. New parameter:file, 1->CASA)> is now included in the DNS install and maintenance utility for selecting CASA or a file as the credential store. 2.3.4 iFolder iFolderTM client support is included for OpenSUSE® 11.1 and SUSE Linux Enterprise Desktop (SLED) 11 The Novell iFolder 3.7 enterprise server supports iFolder clients for both OpenSUSE 11.1 and SLED 11. A 64-bit version of the iFolder client is available for Vista 64. This includes: A new 64-bit install A new 64-bit Flaim database New iFolder binaries in 64-bit Reverting an iFolder now uses the same dialog box that is used by the iFolder main window. It has Delete from server enabled. iFolder client startup performance has been enhanced. The iFolder client now starts much more quickly. 2.3.5 iPrint Print Gateway enhancements What’s New 17 File System Cluster volumes are migrated through file system command line utilities. To migrate the cluster volumes, specify the cluster resource IP in the mls, migfiles, maptrustees, and migtrustees commands. The volumes are available even if the resource fails over. Overall Migration Auto-refresh for log messages is enabled while migration or synchronization is in progress. You can also click the Refresh button for viewing the offline log messages. In the Migration Tool GUI > Services to Migrate, the Status field is updated with the status and last executed date and time of the migration or the sync activity. Hot keys are available for accessing the Migration GUI. 18 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 2.3.6 Migration The information in this section helps you get started with Novell® Open Enterprise Server (OES) 2 SP2. 3 Section 3.1, “Installing OES 2 SP2,” on page 19 Section 3.2, “Installing the DNS/DHCP Java Console,” on page 20 Section 3.3, “Documentation,” on page 20 3.1 Installing OES 2 SP2 NOTE: For installation issues, see the section for the platform you are installing. Section 3.1.1, “Minimum 256 Colors Required,” on page 19 Section 3.1.2, “Before Installing a Migration Target Server,” on page 19 Section 3.1.3, “Installation Instructions,” on page 19 Section 3.1.4, “64-Bit eDirectory,” on page 19 Section 3.1.5, “64-Bit NCP Server,” on page 19 3.1.1 Minimum 256 Colors Required A minimum color depth of 8 bits (256 colors) is required by your video card and driver setting to run the installations properly. On NetWare®, the video card must also be VESA-compliant. 3.1.2 Before Installing a Migration Target Server Before you install or prepare any migration target servers, be sure to read the information and directions in Section 5.1, “ID Transfer Migration Requires a Pre-Migration Server,” on page 31. 3.1.3 Installation Instructions Hardware and installation requirements remain unchanged from OES 2. See the OES 2 online documentation (http://www.novell.com/documentation/oes2/install-update-upgrade.html#instl-oes). 3.1.4 64-Bit eDirectory Selecting Novell eDirectory when using OES 2 SP2 64-bit media automatically installs 64-bit eDirectoryTM. OES 2 SP2 32-bit media installs 32-bit eDirectory. 3.1.5 64-Bit NCP Server Selecting NCP Server when using OES 2 SP2 64-bit media, automatically installs 64-bit NCPTM server. OES 2 SP2 32-bit media installs 32-bit NCP server. Getting Started with OES 2 SP2 19 novdocx (en) 13 May 2009 Getting Started with OES 2 SP2 3 Section 3.2.1, “Installing the Java Console on Windows,” on page 20 Section 3.2.2, “Installing the Java Console on Linux,” on page 20 3.2.1 Installing the Java Console on Windows 1 Download the Java Console for your Windows platform (32-bit or 64-bit) from the OES 2 Welcome Page (https://server_IP_address/welcome/manage.html). The filename for 32-bit windows is DNSDHCP_SA.zip; for 64-bit windows it is DNSDHCP_SAx64.zip. 2 Extract or unzip the file. 3 Run setup.exe from the extracted files and follow the prompts to complete the setup. 3.2.2 Installing the Java Console on Linux 1 Download the Java Console for the Linux platform (32-bit or 64-bit) from the OES 2 Welcome Page (https://server_IP_address/welcome/manage.html). The tar filename for 32-bit Linux is dnsdhcp-jc-i586.tar.gz and for 64-bit Linux it is dhsdhcp-jc-x86_64.tar.gz. 2 Untar the file for your platform by using tar -xzvf filename. The RPM for your platform is untarred. The 32-bit RPM is novell-dnsdhcp-jc-1.0.01.i586.rpm; the 64-bit RPM is novell-dnsdhcp-jc-1.0.0-1.x86_64.rpm. 3 Install Java Console by using rpm -ivh rpm name. 3.3 Documentation This Readme lists the issues specific to the OES 2 SP2 release. For all other OES 2 documentation, see the OES 2 SP1 documentation on the Web (http:// www.novell.com/documentation/oes2). 20 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 3.2 Installing the DNS/DHCP Java Console This section contains most of the issues for Novell® Open Enterprise Server (OES) 2 Linux. The remaining issues are documented in Chapter 5, “Migration Tool Issues,” on page 31 and Chapter 6, “Domain Services for Windows Issues,” on page 35. 4 Caveats are documented in Chapter 7, “Caveats,” on page 39. Section 4.1, “Installation/Upgrade Issues,” on page 21 Section 4.2, “Apple Filing Protocol (AFP) Issues,” on page 24 Section 4.3, “CIFS Issues,” on page 24 Section 4.4, “Distributed File Services (DFS) Issues,” on page 25 Section 4.5, “DNS/DHCP Issues,” on page 26 Section 4.6, “eDirectory Issues,” on page 27 Section 4.7, “iFolder Issues,” on page 27 Section 4.8, “iPrint Issues,” on page 27 Section 4.9, “NSS Issues,” on page 28 Section 4.10, “Samba Issues,” on page 29 Section 4.11, “Security Issues,” on page 29 Section 4.12, “Storage Management System (SMS) Issues,” on page 30 Section 4.13, “Xen Virtualization Issues,” on page 30 4.1 Installation/Upgrade Issues Section 4.1.1, “Apply the Latest Patches Before Upgrading,” on page 21 Section 4.1.2, “Do Not Upgrade to eDirectory 8.8 Separately,” on page 22 Section 4.1.3, “If Apache Fails to Start After You Upgrade QuickFinder,” on page 22 Section 4.1.4, “Incompatible TLS Configurations Give No Warning,” on page 22 Section 4.1.5, “Installing from the IPP Page Fails After Upgrading,” on page 22 Section 4.1.6, “Storage-Related Plug-Ins Must Be Uninstalled,” on page 23 Section 4.1.7, “Upgrading a 64-Bit Installation Breaks Some Novell Products,” on page 23 Also see Section 7.5, “Installation and Upgrade,” on page 42. 4.1.1 Apply the Latest Patches Before Upgrading Before you can upgrade an OES 1 Linux or OES 2 Linux server to OES 2 SP2 Linux, ensure that you have patched the server to the latest patch level and that the server and OES services are running as desired. You should also ensure that you meet the other upgrade requirements. For more information, see “Updating an OES 2 SP1 Linux Server” in the OES2 SP1: Linux Installation Guide. Service Issues 21 novdocx (en) 13 May 2009 Service Issues 4 If you are running OES 1 SP2, do not upgrade to eDirectoryTM 8.8 independently of upgrading to OES 2 SP2. For example, do not upgrade from eDirectory 8.7.3 to eDirectory 8.8.2 through the oes-edir88 patch channel prior to upgrading to OES 2 SP2. Doing so causes configuration problems that the OES 2 SP2 install is not designed to handle. 4.1.3 If Apache Fails to Start After You Upgrade QuickFinder If you installed QuickFinder Server as part of the original OES 1 release, the RPM isn’t upgraded properly and Apache* fails to start. The workaround is to manually update the quickfinder-server RPM after the upgrade by entering the following commands at a terminal prompt after upgrading to OES 2 SP2: rug install quickfinder-server rcapache2 restart 4.1.4 Incompatible TLS Configurations Give No Warning When you install a new eDirectory tree, the eDirectory Configuration - New or Existing Tree screen has the Require TLS for Simple Binds with Password option selected by default. If you keep this configuration setting, the eDirectory LDAP server requires that all communications come through the secure LDAP port that you specified on the eDirectory Configuration - Local Server Configuration screen. By default, this is port 636. Unfortunately, the OES install doesn’t display a warning if you subsequently configure OES services to use non-TLS (non-secure) LDAP communications (port 389). The installation proceeds normally but the service configuration fails. For example, if you accept the TLS default, then configure Novell DHCP to use non-secure communications (by deselecting the Use secure channel for configuration option), the OES install doesn't warn that you have created an incompatible configuration. After eDirectory and the iManager plug-ins install successfully, the Novell DHCP configuration fails. You must then use iManager to change either the LDAP server configuration or the Novell DHCP configuration to support your preferred communication protocol. Simply enabling non-TLS LDAP communications doesn’t disable TLS. It merely adds support for non-secure communications with the LDAP server. Novell has no current plans to change this. 4.1.5 Installing from the IPP Page Fails After Upgrading After upgrading a server from OES 1 SP2 to OES 2 SP2, attempting to install printers from the IPP page results in errors, such as error 1345 and error 1285. 22 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 4.1.2 Do Not Upgrade to eDirectory 8.8 Separately novdocx (en) 13 May 2009 To resolve the issues based on the errors shown, see the following TIDs: 3484700 (http://www.novell.com/support/ search.do?cmd=displayKC&sliceId=SAL_Public&externalId=3484700) 3790999 (http://www.novell.com/support/ search.do?cmd=displayKC&sliceId=SAL_Public&externalId=3790999) 4.1.6 Storage-Related Plug-Ins Must Be Uninstalled After upgrading to OES 2 SP2 Linux, you must uninstall all of the old storage-related plug-ins for iManager, then install the new ones for iManager 2.7.2. The storage-related plug-ins are available on the installation media. In OES 2 for Linux and NetWare®, the Novell Distributed File Services and Native File Access Protocols (AFP and CIFS) for NetWare were delivered in the NSS Management plug-in (nssmgmt.npm).In OES 2 SP2, these roles are delivered separately in their own NPM files. Distributed File Services is now delivered as dfsmgmt.npm. The Native File Access Protocols for NetWare service has been replaced by Novell AFP (afpmgmt.npm) and Novell CIFS (cifsmgmt.npm). In OES 2 SP2, the Novell AFP and Novell CIFS plug-ins support AFP and CIFS services for NSS volumes on both Linux and NetWare. These new plug-ins also require the NSS Management (nssmgmt.npm) and Storage Management (storagemgmt.npm) plug-ins. Other storage-related plug-ins include Archive Versioning (arkmgmt.npm) and Cluster Services (ncsmgmt.npm). All storage-related plug-ins share code in common with the Storage Management plug-in. You must uninstall the existing storage-related plug-ins, then install the new plug-ins at the same time to make sure that the common code works for all plug-ins. 4.1.7 Upgrading a 64-Bit Installation Breaks Some Novell Products All versions of the following Novell products run only with 32-bit eDirectory and cannot run on 64Bit OES Linux after upgrading to OES 2 SP2: Novell Identity Manager Novell Access Manager Novell SecureLogin When you upgrade an installation of 64-bit OES 2 to OES 2 SP2, the 32-bit installation of eDirectory that was installed with 64-bit OES 2, is upgrade to 64-bit eDirectory 8.8. Until Novell releases a 64-bit version of the products listed above, you cannot run them on a 64-bit OES 2 SP2 server. NOTE: If you are running 32-bit OES 2 on 64-bit server hardware, you can upgrade the server to 32-bit OES 2 SP2 without affecting the listed products. Service Issues 23 4.2 Apple Filing Protocol (AFP) Issues Section 4.2.1, “Server Registration Doesn’t Happen through Bonjour,” on page 24 Also see Section 7.1, “AFP,” on page 39. 4.2.1 Server Registration Doesn’t Happen through Bonjour NOTE: This issue should be resolved when SLES 10 SP3 is introduced as the base platform for OES 2 SP2. To work around this issue, do the following: 1 Install the Avahi daemon. 2 Modify the /etc/dbus-1/system.d/avahi-dbus.conf file by replacing the line, allow send_interface="org.freedesktop.Avahi"/ with allow send_destination="org.freedesktop.Avahi"/ 3 Stop and then restart the dbus daemon by using the following commands: rcdbus stop rcdbus start 4 Start the avahi daemon by using the following command: /etc/init.d/avahi-daemon start 4.3 CIFS Issues The following is the list of known Novell CIFS issues: Section 4.3.1, “Cross-Platform Junctions Not Supported,” on page 24 Section 4.3.2, “Junction Target Changes Require Restarting the Windows Client,” on page 25 Section 4.3.3, “Duplicate CIFS Share Names for NSS Volumes,” on page 25 Section 4.3.4, “Configuring LDAP with Secure Channel Disabled,” on page 25 Section 4.3.5, “Performance Degradation,” on page 25 Also see Section 7.2, “CIFS,” on page 40. 4.3.1 Cross-Platform Junctions Not Supported Novell CIFS only supports junctions that target volumes and subdirectories on OES Linux servers. Novell has no current plans to change this. 24 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 Upgrading from 32-bit OES 2 to 64-bit OES 2 SP2 is not supported. novdocx (en) 13 May 2009 4.3.2 Junction Target Changes Require Restarting the Windows Client The Windows client caches junction locations when it starts. If you modify the junction target location, the client continues to point to the old junction target path until you restart the client. 4.3.3 Duplicate CIFS Share Names for NSS Volumes When NSS volumes are added to an OES Linux server, they are automatically added as CIFS shares. If you rename these shares and restart CIFS, the original share names appear in addition to the new share names you specified. Novell has no current plans to change this. 4.3.4 Configuring LDAP with Secure Channel Disabled If you are installing a new tree or configuring Novell CIFS for the first time in YaST, do not change the default settings for the secure LDAP port number, the server IP address, or the Secure Channel. If you do, CIFS is not configured. Novell has no current plans to change this. 4.3.5 Performance Degradation A performance degradation has been observed when cross-protocol locking is enabled and Oplock is disabled. Novell has no current plans to change this. 4.4 Distributed File Services (DFS) Issues Section 4.4.1, “Failure Creating a Management Context with Two Replicas,” on page 25 Section 4.4.2, “Hard Links Are Not Supported in a DFS Move/Split Volume Operation,” on page 26 Section 4.4.3, “Specifying Non-Default VLDB Database Paths on Replica Sites,” on page 26 4.4.1 Failure Creating a Management Context with Two Replicas Random failures might occur if you attempt to specify two VLDB replica sites when you create the DFS management context. The second replica site is not created, causing the DFS creation process to fail. To avoid or resolve this problem, specify only a single VLDB replica site when you create the DFS management. After the management context has been successfully created, go to Distributed File Services > Manage Replicas, then click the New link to add the second replica site for the management context. Novell has no current plans to change this. Service Issues 25 DFS does not support move or split operations on volumes containing hard links. The hard links on the volume do not move correctly for either operation. Novell plans to address this issue in a future OES release. 4.4.3 Specifying Non-Default VLDB Database Paths on Replica Sites If you specify two replica sites when you create a DFS management context, it is not possible to specify non-default VLDB paths that are different for each of the replica sites. By default, each replica site uses the default VLDB path appropriate for its platform. If you specify a non-default VLDB path when two sites are selected, that path applies to both selected replica sites. For example, you typically specify a non-default VLDB path when you cluster the VLDB service for a replica site so that the VLDB is located on a clustered resource. If you cluster each replica site, the sites might need different non-default paths on their respective servers. To specify different non-default paths for two replica sites, create the DFS management context with a single replica site, and specify its non-default VLDB path. After the management context is successfully created, use the Distributed File Services > Manage Replica Sites task in iManager to add the second replica and specify the non-default VLDB path to use for its VLDB. Novell has no current plans to change this. 4.5 DNS/DHCP Issues Section 4.5.1, “Java Console Limitations,” on page 26 Section 4.5.2, “DNS-Specific Issues,” on page 26 Section 4.5.3, “DHCP-Specific Issues,” on page 27 NOTE: There are also some caveats documented in Section 7.3, “DNS/DHCP,” on page 41. 4.5.1 Java Console Limitations The DNS/DHCP Java Console cannot be used to configure DNS/DHCP in a DSfW environment. A Locate Summary Error is displayed. Non-English environments are not supported with the Java Console. The Import feature is not supported with the new Java Console. Novell has no current plans to change this. 4.5.2 DNS-Specific Issues There are no known DNS-specific issues. 26 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 4.4.2 Hard Links Are Not Supported in a DFS Move/Split Volume Operation novdocx (en) 13 May 2009 4.5.3 DHCP-Specific Issues There are no known DHCP-specific issues. 4.6 eDirectory Issues Section 4.6.1, “eDirectory Not Starting Automatically,” on page 27 4.6.1 eDirectory Not Starting Automatically After a system crash or power failure, eDirectory services (ndsd) might not automatically start in some situations. To start eDirectory again, delete the /var/opt/novell/eDirectory/data/ndsd.pid file, then enter /etc/init.d/ndsd start at a terminal prompt. Novell has no current plans to change this. 4.7 iFolder Issues See the iFolder 3.7 Readme (http://www.novell.com/documentation/beta/ifolder3/ifolder37_readme/ data/ifolder37_readme.html). 4.8 iPrint Issues Section 4.8.1, “Installing the Printer Agent on Macintosh Workstations Requires Mozilla Firefox,” on page 27 Section 4.8.2, “64-Bit Mozilla Firefox Can’t Install Printer,” on page 27 Section 4.8.3, “Client Installation on SLED 11 Appears to Fail,” on page 28 Section 4.8.4, “System PPD Upload Fails,” on page 28 Section 4.8.5, “Creating the Driver Profile Fails,” on page 28 Section 4.8.6, “Vista 64-Bit Driver Not Being Associated,” on page 28 Section 4.8.7, “Printers Are Re-Installed,” on page 28 Section 4.8.8, “Driver Upload Not Working,” on page 28 4.8.1 Installing the Printer Agent on Macintosh Workstations Requires Mozilla Firefox Only Mozilla* Firefox* is supported for installing the printer agent on Macintosh workstations. Novell has no current plans to change this. 4.8.2 64-Bit Mozilla Firefox Can’t Install Printer You cannot install a printer with the 64-bit Mozilla Firefox browser (Minefield) in the Beta 1 release. Novell has no current plans to change this. Service Issues 27 You can successfully install the iPrint client on SUSE® Linux Enterprise Desktop (SLED) 11 using the software manager, but YaST hangs and continues to report progress until you kill the process. Novell plans to fix this in the shipping product. 4.8.4 System PPD Upload Fails If you use Firefox 3.0 on SLED 11, the system PPD upload fails with the 64-bit iPrint client included in OES 2 SP2 Beta2. 4.8.5 Creating the Driver Profile Fails Creating the driver profile fails on Windows Vista and Windows 7 with the 5.20 iPrint client. 4.8.6 Vista 64-Bit Driver Not Being Associated The Vista 64-bit driver is not being associated with the printer when creating the printer from Manage Print Manager. 4.8.7 Printers Are Re-Installed Printers are reinstalled if the auto driver update flag is enabled when restarting the spooler. 4.8.8 Driver Upload Not Working The iPrint plug-in does not work in OES 2 SP2 Beta 2 if you are using Internet Explorer* 8 on Windows 7. The driver upload should be done from Vista. 4.9 NSS Issues Section 4.9.1, “Monitoring Compression Might Cause the System to Reboot,” on page 28 Section 4.9.2, “Startup Conflict with McAfee LinuxShield,” on page 29 Section 4.9.3, “Unable to Change the Lookup Namespace on a Clustered Volume,” on page 29 Section 4.9.4, “Unable to Rename the Volume Mount Point with Shared Volumes.,” on page 29 4.9.1 Monitoring Compression Might Cause the System to Reboot Novell has observed that when Maximum Concurrent Compressions is set to 8, monitoring the compression statistics from the nssmu compression screen while data is being compressed can cause a system reboot. This seems to be a random issue at this point. Novell plans to address this in the shipping product. 28 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 4.8.3 Client Installation on SLED 11 Appears to Fail novdocx (en) 13 May 2009 4.9.2 Startup Conflict with McAfee LinuxShield A startup conflict between NSS and McAfee* LinuxShield* might result in a soft hang. The situation is timing and hardware sensitive, so it might be seen randomly on successive reboots or on different machines. For a workaround solution, refer to the McAfee Knowledgebase for its LinuxShield product. 4.9.3 Unable to Change the Lookup Namespace on a Clustered Volume The lookup namespace on a clustered volume cannot be modified. Namespace modification requires a volume umount and mount. NSS does not curently remember the changed namespace value and resets it back to the default namespace, which is LONG. Novell plans to fix this in the released product. 4.9.4 Unable to Rename the Volume Mount Point with Shared Volumes. Renaming the mount point is currently not working on shared volumes. Novell plans to fix this in the released product. 4.10 Samba Issues Section 4.10.1, “Using Samba to Open a File with BATCH_OPLOCK Fails,” on page 29 4.10.1 Using Samba to Open a File with BATCH_OPLOCK Fails BATCH_OPLOCK (opportunistic file locking in batch mode) requests are not handled correctly on an OES 2 Linux server. Programs that request a BATCH_OPLOCK on a Samba share receive no oplock. Requests for Exclusive and Level 2 oplocks are handled correctly. Novell has no current plans to change this. 4.11 Security Issues Section 4.11.1, “All LUM Users Can Administer QuickFinder,” on page 29 4.11.1 All LUM Users Can Administer QuickFinder Any LUM-enabled user can access and use the QuickFinderTM admin console. Novell has no current plans to change this. Service Issues 29 There are no known SMS issues in Beta 2. Also see Section 7.8, “SMS,” on page 43. 4.13 Xen Virtualization Issues Section 4.13.1, “Server Fails to Boot After Installing OES 2 SP 2 Linux on a Xen-Based VM,” on page 30 Also see Section 7.10, “Xen,” on page 44. 4.13.1 Server Fails to Boot After Installing OES 2 SP 2 Linux on a Xen-Based VM During an OES 2 SP2 Linux install on a Xen*-based virtual machine, if you configure the root partition (/) as the first partition on the system disk and the swap partition second, table information is overwritten for the first partition and the server cannot be booted. To avoid this problem, be sure to following the instructions in “Setting Up Disk Partitions (http:// www.novell.com/documentation/oes2/inst_oes_lx/data/btlcu50.html#bnx3yh4)” in the OES 2 SP1: Linux Installation Guide (http://www.novell.com/documentation/oes2/inst_oes_lx/data/front.html) Novell has no current plans to change this. 30 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 4.12 Storage Management System (SMS) Issues This section documents Novell® Open Enterprise Server (OES) 2 Migration Tool issues in the Beta 3 release.. 5 Section 5.1, “ID Transfer Migration Requires a Pre-Migration Server,” on page 31 Section 5.2, “Installing the Migration Tool,” on page 32 Section 5.3, “Starting the Migration Tool,” on page 32 Section 5.4, “File System Issues,” on page 32 Section 5.5, “iPrint Issues,” on page 32 Section 5.6, “Windows Migrations,” on page 33 Section 5.7, “For More Information,” on page 33 5.1 ID Transfer Migration Requires a PreMigration Server The OES 2 Migration Tool is designed to meet all of your OES migration needs. However, when you install the target server for a Transfer ID migration, and you reach the Software Selection and System Tasks dialog box, you must select the Novell Pre-migration Server option. Migration Tool Issues 31 novdocx (en) 13 May 2009 Migration Tool Issues 5 Before performing a Transfer ID migration, we recommend that you manually back up eDirectory and the NICI keys. 5.2 Installing the Migration Tool The Migration Tool is automatically installed with OES 2 SP2, in the /opt/novell/migration folder. 5.3 Starting the Migration Tool You can access the Migration Tool in two ways: To start the migration GUI on the server desktop, click Computer > More Applications > System > Novell Migration Tool. To start the migration CLI, enter the following command at a terminal prompt: miggui 5.4 File System Issues Section 5.4.1, “File System Migration Fails for NetWare Servers Identified by IP Address,” on page 32 Section 5.4.2, “Directory Consolidation Is Case-Sensitive,” on page 32 5.4.1 File System Migration Fails for NetWare Servers Identified by IP Address If the source server is NetWare®, file system migration might fail randomly. Specify the DNS hostname of the source server instead of the IP address, then try again. 5.4.2 Directory Consolidation Is Case-Sensitive The Migration Tool uses the case-sensitive naming convention. When consolidating directories with the same name but a different case on the source volume compared to the target volume, the Migration Tool fails to merge the directories and creates new directories instead. 5.5 iPrint Issues Section 5.5.1, “iprntman Doesn't Handle ACL Migration,” on page 32 Section 5.5.2, “ZENworks Print Policies Break During Migration,” on page 33 5.5.1 iprntman Doesn't Handle ACL Migration After migrating a server in the same tree, the ACL may not be migrated properly. This can be resolved by opening a terminal prompt and entering the following command : 32 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 This prepares eDirectoryTM for the Transfer ID migration that you will perform later. novdocx (en) 13 May 2009 /opt/novell/bin/iprintman psm --xml-import /opt/novell/iprint/bin/ psmimport.xml -s target-server-IPAddress -u admin -f --accept-cert Novell plans to address this issue in the shipping product. 5.5.2 ZENworks Print Policies Break During Migration If iPrint printers are distributed through ZENworks® Print policies (either ZENworks 7 or ZENworks Configuration Management 10), the policies might be broken after printers are migrated to a new target server. Development of a solution is underway and is planned for inclusion in the OES 2 SP1 patch channel. If your policies are broken after a migration, the patch has not yet been released, and the workaround is to repopulate the policies with new printers. 5.6 Windows Migrations You can migrate Windows shares through YaST by using the Open Enterprise Server > Migrate Windows Shares tool. See “Using the Migrate Windows Shares Utility” in the OES 2 SP2: Migration Tool Administration Guide. The following are known issues with the tool: User information is not generated for DFS shares on Windows source servers. Novell has no current plans to change this. Ownership for files and folders changes after the migration. Novell has no current plans to change this. When migrating files from an NTFS share, some of the localized/foreign language files aren’t copied, and the tool reports that the file has vanished. Novell has no current plans to change this. Selecting Statically Apply Trustee Rights has no effect. The migration always uses the default setting. Novell has no current plans to change this. Compressed files are migrated as uncompressed. Novell has no current plans to change this. 5.7 For More Information For information on using the Migration Tool GUI, refer to the help file associated with the Migration Tool GUI or see “Using the Migration Tool GUI” in the OES 2 SP2: Migration Tool Administration Guide. Migration Tool Issues 33 novdocx (en) 13 May 2009 34 OES2 SP2: Readme - Beta 2 6 This section lists various known issues that have been encountered during the installation and configuration of Domain Services for Windows (DSfW). For installation instructions, see “Installing and Configuring Domain Services for Windows” in the OES 2 SP2: Domain Services for Windows Administration Guide. IMPORTANT: DSfW requires the latest version of Samba. To get the latest version of Samba on your SUSE® Linux Enterprise Server (SLES) 10 SP2 server, you must register the server with the Novell® Customer Center and then download and install all of the available patches prior to configuring DSfW. For more information on registering your server and retrieving patches, see “Specifying Novell Customer Center Configuration Settings” in the OES2 SP1: Linux Installation Guide. Section 6.1, “Installation and Configuration Issues,” on page 35 Section 6.2, “Provisioning Issues,” on page 35 Section 6.3, “Removing a DSfW Server,” on page 36 Section 6.4, “MMC Issues,” on page 36 Section 6.5, “Compatibility with Other Novell Products,” on page 36 Section 6.6, “DSfW Interoperability Issues,” on page 37 6.1 Installation and Configuration Issues Section 6.1.1, “Installing DSfW by Using AutoYaST Makes Invalid LDAP Calls,” on page 35 6.1.1 Installing DSfW by Using AutoYaST Makes Invalid LDAP Calls When you try to configure a DSfW server using the YaST generated autoyast.xml file, it might respond with the invalid LDAP syntax errors. To avoid these errors, specify the correct server context format in the XML file. Novell has no current plans to change this. 6.2 Provisioning Issues After provisioning DSfW, the winbindd deamon might go into not responding mode. Ensure that winbindd is running by using the /etc/init.d/winbind status command. During installation of an additional Domain Controller, the SLAPI plug-in configuration task fails to execute. To resolve this, refresh LDAP by using the following command: ldapconfig -R -a admin FDN -w password Domain Services for Windows Issues 35 novdocx (en) 13 May 2009 Domain Services for Windows Issues 6 Controller. The provisioning plug-in fails to validate the credentials of the current domain during domain configuration. 6.3 Removing a DSfW Server When you use the ndsdcrm utility to remove a failed installation, it fails to remove the provisioning.xml file. To resolve this issue, manually remove the file from the /etc/opt/ novell/xad/ folder. 6.4 MMC Issues You might encounter the following issues while using MMC to manage the DSfW server: Section 6.4.1, “Copying a User Object from the MMC Fails,” on page 36 Section 6.4.2, “Users Must Change Their Own Passwords,” on page 36 6.4.1 Copying a User Object from the MMC Fails When you copy a user object from MMC, it fails with an unspecified error. Novell has no current plans to change this. 6.4.2 Users Must Change Their Own Passwords After a user is created, the administrator cannot force password changes through MMC because the check box is disabled. Users must change their own passwords. Novell has no current plans to change this. 6.5 Compatibility with Other Novell Products Novell doesn't support installing other Novell products within a DSfW partition. Some products might be supported in name-mapped implementations of DSfW. Consult the product documentation (http://www.novell.com/documentation) and the Novell Support site (http:// www.novell.com/support) for confirmation before attempting such installations. You should assume that an installation is not supported unless these sources indicate otherwise. NOTE: This section refers to other Novell products, such as GroupWise®. It doesn’t apply to services included with OES 2, such as Novell iPrint. Limitations for installing OES 2 services on the same server are outlined in “Unsupported Service Combinations” in the OES 2 SP2: Domain Services for Windows Administration Guide. 36 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 The DNS Configuration task fails to excute while provisioning an Additional Domain novdocx (en) 13 May 2009 6.6 DSfW Interoperability Issues IMPORTANT: The following list is provided here for your convenience. Do not consider the list as complete. Be sure to consult the documentation for your other Novell products for information on interoperability issues with DSfW. Section 6.6.1, “ZENworks Endpoint Security Management 3.5,” on page 37 Section 6.6.2, “GroupWise 8.0,” on page 37 Section 6.6.3, “Novell SecureLogin 6.1,” on page 37 6.6.1 ZENworks Endpoint Security Management 3.5 On an OES 2 SP1 machine with DSFW installed, the ESM utility fails on all DSfW server ports. Novell has no current plans to change this. 6.6.2 GroupWise 8.0 In a DSfW three-server tree, when you launch ConsoleOne® to assign GroupWise passwords to the users, the post office indicates that all the users are added to it. However, the property pages of the DSfW users indicate that the users residing within the DSfW partition are not assigned to the post office, but other users are correctly added. Novell has no current plans to change this. 6.6.3 Novell SecureLogin 6.1 On installing SecureLogin on an existing DSfW partition, it functions as expected. If DSfW is deployed on a tree that has SecureLogin already installed, the existing LDAP mapping is replaced with the automapped LDAP names (for example, NDS Name Prot:SSO Auth is mapped to LDAP name ProtSSOAuth, which is intended to be protocom-SSO-Auth-Data). To resolve this issue, the administrator must manually change the LDAP schema mapping for SecureLogin to work. Novell has no current plans to change this. Domain Services for Windows Issues 37 novdocx (en) 13 May 2009 38 OES2 SP2: Readme - Beta 2 You should be aware of the following items as you work with Novell® Open Enterprise Server (OES) 2 SP2 services. Novell has no current plans to change any of these caveats. Section 7.1, “AFP,” on page 39 Section 7.2, “CIFS,” on page 40 Section 7.3, “DNS/DHCP,” on page 41 Section 7.4, “DSfW,” on page 41 Section 7.5, “Installation and Upgrade,” on page 42 Section 7.6, “Management,” on page 42 Section 7.7, “LDAP,” on page 43 Section 7.8, “SMS,” on page 43 Section 7.9, “TSANDS Limitations,” on page 43 Section 7.10, “Xen,” on page 44 7.1 AFP Section 7.1.1, “User Credential Synchronization with eDirectory,” on page 39 Section 7.1.2, “Anti-Virus Solutions and AFP,” on page 39 Section 7.1.3, “OpenOffice 3.0 Is Required for File Locking on Macintosh Workstations,” on page 39 7.1.1 User Credential Synchronization with eDirectory If you need to change the AFP proxy user’s password, you must use YaST and reconfigure AFP. 7.1.2 Anti-Virus Solutions and AFP The Apple* Filing Protocol (AFP) support for NSS files on OES 2 SP2 Linux is implemented via a technology that bypasses the real-time scanning employed by most OES 2 anti-virus solutions. NSS files shared through an AFP connection might be protected by on-demand scanning on the OES 2 server or by real-time and on-demand scanning on the Apple client. 7.1.3 OpenOffice 3.0 Is Required for File Locking on Macintosh Workstations If your network users access files on OES Linux servers through AFP, CIFS, or NCPTM connections by using OpenOffice on Macintosh workstations, they should use OpenOffice 3.0 to avoid overwriting each other’s changes. Macintosh versions of OpenOffice earlier than 3.0 don’t create temporary lock files, meaning that each requested copy of the same file is a normal read-write copy. If multiple users open and edit the same file during the same time period, they overwrite each other’s changes. Caveats 39 novdocx (en) 13 May 2009 7 Caveats 7 7.2 CIFS Section 7.2.1, “CIFS Server Can’t Co-exist with Samba Daemons and DSfW,” on page 40 Section 7.2.2, “Changing the Server IP Address,” on page 40 Section 7.2.3, “Number of Shares Hosted on the Server,” on page 40 Section 7.2.4, “Proxy User Creation Depends on the Existing Password Policy,” on page 40 Section 7.2.5, “Trustee Assignments for Files/Folders,” on page 41 Section 7.2.6, “Proxy User Credential Synchronization with eDirectory,” on page 41 Section 7.2.7, “Using a Preexisting Cluster Pool for CIFS,” on page 41 7.2.1 CIFS Server Can’t Co-exist with Samba Daemons and DSfW The CIFS server does not come up if the Samba server or DSfW is running. For Samba, the workaround is to login as root and stop all the running Samba daemons, then restart the CIFS server. Use the following commands to stop the running Samba daemons: /etc/init.d/smb stop /etc/init.d/nmb stop 7.2.2 Changing the Server IP Address Reconfiguring CIFS might not take effect if the server IP address is changed and is not being populated in YaST. The workaround is to reconfigure the LDAP server IP address for the changes to be populated in YaST and eventually in the CIFS configuration. 7.2.3 Number of Shares Hosted on the Server There is a limitation on the number of shares a CIFS server can host. For most configurations this limit is between 300 to 500 shares. 7.2.4 Proxy User Creation Depends on the Existing Password Policy Proxy user creation fails if the default generated password does not adhere to the Password policy assigned to the container. The workaround is to create a password that conforms to the password restrictions in the existing Password policy. For more information, see “CIFS is not coming up after installation” in the OES 2 SP1: Novell CIFS for Linux Administration Guide. 40 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 OpenOffice 3.0 prevents this problem by providing only the first requester with a read-write copy of the file and placing a temporary lock file on the server. As long as the first requester has the file open, all other requesters get read-only copies of the file and cannot modify it. novdocx (en) 13 May 2009 7.2.5 Trustee Assignments for Files/Folders A file or folder loses its explicit trustee assignments if Rename/Move operations are performed on it. An administrator must re-assign trustee rights to the renamed or moved folder or file. 7.2.6 Proxy User Credential Synchronization with eDirectory If the proxy user password is changed, the Admin user must reconfigure CIFS through YaST and change the password. Use the procedure in “CIFS is not coming up after installation” in the OES 2 SP1: Novell CIFS for Linux Administration Guide. 7.2.7 Using a Preexisting Cluster Pool for CIFS Enabling CIFS on a preexisting cluster pool requires the following manual steps to be done by the administrator: IMPORTANT: Ensure that Python* is installed on SUSE® Linux Enterprise Server. 1 Enable CIFS for POOL_SERVER through iManager. 2 Offline the POOL_SERVER. 3 Run the following command: python cifsPool.py Resource_DN CIFS_Server_Name ldaps://ldapserver:636 Admin_DN Admin_password For example, python cifsPool.py cn=POOL_SERVER,cn=clus1,o=novell CIFS_POOL ldaps://192.168.1.1:636 cn=admin,o=novell xxxxxx NOTE: The length of the CIFS server name should not exceed 15 characters. 7.3 DNS/DHCP Section 7.3.1, “DNS Credential Change in OES 2 SP2,” on page 41 7.3.1 DNS Credential Change in OES 2 SP2 In OES 2 SP1, credentials could be stored in both CASA and in a file. In OES 2 SP2, credentials can be stored in either CASA or in a file but not in both. 7.4 DSfW Section 7.4.1, “Time Must Be Synchronized or Name-Mapped Installation Fails,” on page 41 7.4.1 Time Must Be Synchronized or Name-Mapped Installation Fails DSfW cannot install if there are time synchronization problems among the servers in the [root] replica ring. To ensure that DSfW does not encounter this problem during installation, you must have all the servers in the [root] replica synchronized correctly before installing DSfW. Caveats 41 Section 7.5.1, “Java and Other Conflicts Displayed During an Upgrade from OES 2 Linux,” on page 42 Section 7.5.2, “The Tree Admin Is Not Automatically Granted Rights for Server Administration,” on page 42 Section 7.5.3, “VNC Install Fails to Set the IP Address in /etc/hosts,” on page 42 7.5.1 Java and Other Conflicts Displayed During an Upgrade from OES 2 Linux If you get package conflict errors during an upgrade to OES 2 SP2, you can either choose to ignore the conflicts (if that option is available), or you can delete the packages. Patches that have been deleted are still in the patch channel if you need to add them later. Testing has revealed no service differences or problems with taking either course of action. 7.5.2 The Tree Admin Is Not Automatically Granted Rights for Server Administration The only administrator who is granted rights to the services on a server is the administrator who installs the server. For example, if a container admin installs a DSfW server, the tree admin cannot manage the DSfW services on that server after the install. The administrator credentials that you entered during the install are automatically configured to allow the admin who did the install to manage services on the server. After the install, you can add another administrator. For more information regarding this issue, see “eDirectory Rights Required to Install OES Linux” in the OES2 SP1: Linux Installation Guide. 7.5.3 VNC Install Fails to Set the IP Address in /etc/hosts If you install through a VNC connection, the /etc/hosts file is configured with a loopback address assigned to the hostname. This can cause problems with services. Using a text editor, modify /etc/hosts so that the hostname is associated with its actual IP address. 7.6 Management Section 7.6.1, “Storage Error in iManager When Accessing a Virtual Server,” on page 42 Section 7.6.2, “Truncated DOS-Compatible Short Filenames Are Not Supported,” on page 43 7.6.1 Storage Error in iManager When Accessing a Virtual Server iManager returns a Storage Error when you access the Authentication tab for a virtual server object. This is working as designed. 42 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 7.5 Installation and Upgrade novdocx (en) 13 May 2009 7.6.2 Truncated DOS-Compatible Short Filenames Are Not Supported Use the actual filenames instead of names such as filena~1.txt during file operations from the command prompt. 7.7 LDAP Section 7.7.1, “Subtree Search Times Out (Bad XML Error),” on page 43 7.7.1 Subtree Search Times Out (Bad XML Error) If you are using Novell eDirectory 8.7.3x, timeouts are possible when you search from iManager for eDirectory objects, such as NCP Server objects, Volume objects, and Cluster objects. This is because the Object Class attribute is not indexed by default. The LDAP subtree search can take over 30 seconds, which causes the query to time out. For example, a Cluster objects search from the Cluster Options page returns the error: Bad XML found during parsing when accessing cluster options We recommend that you create a value index on the objects’ Object Class attribute. (Object Class is considered an attribute for indexing purposes.) This helps to reduce the time needed for the subtree search from over 30 seconds to 10 to 50 milliseconds. For instructions, see “Creating an Index” in the Novell eDirectory 8.8 Administration Guide. Building indexes speeds up the subtree search, even if some partitions being searched do not contain these types of objects. For example, searching for a Cluster object in a context that contains only users is not expected to return results; however, the Object Class search is still performed, and benefits from having an index present. The subtree search performance issue is resolved in the eDirectory 8.8.x release with the addition of the AncestorID feature. 7.8 SMS Section 7.8.1, “Limitation for Restoring an NCP POSIX Volume,” on page 43 7.8.1 Limitation for Restoring an NCP POSIX Volume On restoring an NCP POSIX* volume, the NSS user must be LUM-enabled to preserve the user’s ID. 7.9 TSANDS Limitations Section 7.9.1, “Single Object/Partial Restore from a Full or Subtree Backup,” on page 44 Section 7.9.2, “TSANDS Does Not Connect to eDirectory Running on a Non-Default NCP Port,” on page 44 Caveats 43 Restoring a single object from a full or subtree backup is not supported. 7.9.2 TSANDS Does Not Connect to eDirectory Running on a Non-Default NCP Port If eDirectory is running on a non-default NCP port (that is, other than 524), TSANDS does not connect to it. NOTE: TSANDS must be loaded manually by using following command: /opt/novell/sms/ bin/smsconfig -l tsands For further information on TSANDS, refer to the tsands man page. 7.10 Xen Section 7.10.1, “Backing Up a Xen Virtual Machine,” on page 44 7.10.1 Backing Up a Xen Virtual Machine When you back up a Xen virtual machine running virtualized NetWare, we recommend using a remote backup source rather than a local tape device because of limitations in detecting a local tape device. 44 OES2 SP2: Readme - Beta 2 novdocx (en) 13 May 2009 7.9.1 Single Object/Partial Restore from a Full or Subtree Backup
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.6 Linearized : Yes Page Mode : UseOutlines XMP Toolkit : Adobe XMP Core 4.0-c320 44.293068, Sun Jul 08 2007 18:10:11 Producer : Acrobat Distiller 5.0.5 (Windows) Create Date : 2009:06:12 09:17:40Z Modify Date : 2009:06:12 09:20:42-06:00 Metadata Date : 2009:06:12 09:20:42-06:00 Creator Tool : FrameMaker 8.0 Format : application/pdf Creator : Novell Documentation Title : OES2 SP2: Readme - Beta 2 Document ID : uuid:10d3eafa-4a08-4bc8-a808-dc3e54d19305 Instance ID : uuid:f4b3f442-2a67-45ab-ade5-83b17ae179f0 Page Count : 44 Author : Novell DocumentationEXIF Metadata provided by EXIF.tools