Related Manuals for Novell OPEN ENTERPRISE SERVER 2.0 SP2 - UPGRADING TO OES-PLANNING AND IMPLEMENTATION GUIDE 12-2009
Summary of Contents for Novell OPEN ENTERPRISE SERVER 2.0 SP2 - UPGRADING TO OES-PLANNING AND IMPLEMENTATION GUIDE 12-2009
- Page 1 AUTHORIZED DOCUMENTATION Upgrading to OES—Planning and Implementation Guide Novell ® Open Enterprise Server 2.0 SP2 December, 2009 www.novell.com OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 2: Legal Notices
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. - Page 3 Novell Trademarks 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.
- Page 4 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 5: Table Of Contents
What Do Novell Customers Recommend?........ - Page 6 Upgrading Novell FTP to OES ........
- Page 7 Platform Differences in Novell DHCP ........
- Page 8 Reviewing the Current Cluster ......... 94 10.2.2 Upgrading Novell Cluster Services to OES 2 SP2 ......94 10.2.3 Additional Information .
- Page 9 E.1.1 Overview ............117 E.1.2 FAQs .
- Page 10 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 11: About This Guide
About This Guide ® Open Enterprise Server (OES) 2 SP2 is the next generation of the Novell services that have long been valued by a wide variety of businesses and other organizations, ranging from small businesses to multi-national enterprises. ®... - Page 12 For the most recent version of this guide, see the OES 2 Documentation Web site (http:// www.novell.com/documentation/oes2/upgrade_to_oes_lx/data/front.html). Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark.
-
Page 13: Frequently Asked Questions
Open Source Solutions: Open source initiatives such as Apache* and Tomcat* have been supported on NetWare only as Novell or others have ported them to the platform, but they are automatically available on OES. Xen virtualization technology: This no-cost virtualization solution runs on OES 2 SP2 and lets you create NetWare virtual machines for those services that you want to keep on NetWare for the time being. -
Page 14: Can I Move My Netware Disks To An Oes 2 Server
(NSS) file system, but also traditional Linux file systems, such as Ext3, XFS, and Reiser FS. OES Services enhancements: As Novell OES services continue to evolve, the new features and technologies are almost always only available on OES 2 SP2. -
Page 15: What's New In Oes 2
The list is quite impressive. 1.5 What Do Novell Customers Recommend? Periodically, Novell polls customers to get a reality check. The table below summarizes customer advice from a survey of OES 2 SP2 customers. From a Recent Novell Customer Survey... -
Page 16: What Are The Differences Between Netware And Oes 2
Make sure you have a test environment that mimics your production installation. It works the same as NetWare. The Novell management Interfaces look the same. iPrint, iManager, etc.—all of the benefits of NetWare are available on OES 2 SP2. Don't freak out about service and management differences Learn the iMonitor and iManager Web tools for service and server management. -
Page 17: System And Administrative User And Group Differences
OES 2 servers. For example, many OES 2 services, such as Novell AFP and Novell CIFS require proxy users to retrieve service-related information, such as user passwords and service attributes, and in some cases to write service information in eDirectory. - Page 18 NetWare 6.5 SP8 OES 2 Platform Differences / Migration Issues CIFS (Windows File Yes - NFAP Yes - Novell Both NFAP and Novell CIFS are Novell Services) CIFS proprietary and tightly integrated with eDirectory and Novell Storage Services (NSS). Novell Samba Samba is an open source product ®...
- Page 19 Guide. Health Monitoring The Health Monitoring Server, which was Services included in OES 1, has been removed in OES 2. This is now available in various Novell Remote Manager dialog boxes on both platforms. For more information, see “Health Monitoring Services”...
- Page 20 Guide, and “Overview” in the NW 6.5 SP8: iPrint Administration Guide. (Internetwork Novell has no plans to port IPX to OES. Packet Exchange from Novell iSCSI The iSCSI target for Linux does not support eDirectory access controls like the NetWare target does.
- Page 21 These and other differences are summarized in “NetStorage” in the OES 2 SP2: Planning and Implementation Guide. NetWare Traditional Novell has no plans to port the NetWare File System Traditional File System to Linux. NetWare Traditional Volumes Yes - NFAP...
- Page 22 “Functions Unique to the NetWare Platform” in the NW 6.5 SP8: OpenSSH Administration Guide. PAM (Pluggable PAM is a Linux service that Novell Authentication leverages to provide eDirectory Modules) authentication. eDirectory authentication is native on NetWare. Pervasive.SQL* Pervasive.SQL is available for Linux from the Web (http://www.pervasive.com/...
- Page 23 Directory Agent scope information in eDirectory. This provides for sharing of scope information among DAs. Novell SLP is not available on Linux. OpenSLP on Linux is not customized to provide DA synchronization. Therefore, DA synchronization is only available for eDirectory on NetWare.
-
Page 24: Services Not Included In Oes 2 Sp2
We recognize that time and resources are a problem for customers, and we recommend following the example of one of our customers: Four months prior to rollout, Novell provided OES and SLES training for their administrators at their site and on their hardware and software. -
Page 25: Conduct A Training Assessment
Troubleshooting 1.7.2 Conduct a Training Assessment Novell recommends that you conduct a training needs assessment. You should determine whether current skill sets are absent, adequate, or proficient, so that you can recommend a training package. Three levels of Linux expertise are recommended:... -
Page 26: What Training Is Available
If you can't find what you need on Novell's documentation site, add a comment, tell us what we missed, and we'll see that you get the answer you need. Open Enterprise 2 documentation is available at the following URL: http://www.novell.com/documentation/oes2/index.html (http://www.novell.com/documentation/... -
Page 27: Does Novell Have Community Support To Help Me With My Migration
There are a two good places to connect with other administrators, ask questions, and find answers to your specific migration questions. Novell Forums (http://forums.novell.com/) Cool Solutions Upgrade to OES Community Page (http://www.novell.com/communities/ coolsolutions/upgradetooes) There is a list of the top TIDs (http://www.novell.com/communities/node/8781/top-oes-upgrade-... - Page 28 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 29: Getting Started
To ensure you are equipped with the latest pre-upgrade information and are aware of known issues, we recommend that you validate your OES upgrade readiness using the Novell Support Advisor 1.1 (or later) tool. For more information and to obtain this free tool, access the... - Page 30 Partition and replication diagrams. NDS versions, such as NDS v6, v7, and/or v8. Versions of NDS/eDirectory that are installed on non-NetWare operating systems. Other Novell applications that are directly dependent on eDirectory, such as Novell ® Account Management, DirXML , and Identity Manager.
-
Page 31: Identifying Needed Improvements
14 Collect or document the hardware information for your NetWare servers, including processor specs, RAM configuration and storage adapters. 15 Document any NetWare clusters in your network, both Novell Clustering Services clusters and Business Continuity Clustering clusters. Specify the function of each cluster node, including service failover configurations. -
Page 32: Server Hardware Considerations
Server Hardware List (http://www.novell.com/ partnerguide/section/677.html#c_531). If you don’t already have an agreement with a hardware vendor, all Novell Partners deserve consideration. Be sure to communicate with your chosen hardware vendors regarding server sizing guidelines to ensure that you select the right server and hardware configuration. -
Page 33: Consolidation Considerations
For example, Novell recently consolidated fourteen older file and print servers to two new servers. Which combinations of eDirectory, file, print, GroupWise, WebAccess, etc., might reasonably work together on the same host server? 2.2.3 Virtualization Considerations... -
Page 34: File System Considerations
If so, you should probably preserve all the rights, metadata, and trustee information associated with the data on those volumes, so it makes sense to stay with Novell Storage Services. Are your volumes already in a SAN environment with NSS? If so, switching to a SAN environment that uses NSS on Linux is quite easy. -
Page 35: Time Synchronization
Novell recommends implementing multiple LDAP servers because of the critical nature of the LDAP service. LDAP servers should be fronted with an L4 switch for load sharing and redundancy. If an L4 switch is not available, then DNS round-robin could be used as an alternative. -
Page 36: Lan/Wan Connection Considerations
Because of the multitude of applications being used by our customers, it is impossible for Novell to make recommendations in every instance, so you might need to contact the vendor directly. But first check the Novell Partner Products site (http://www.novell.com/partnerguide/section/677.html) the latest certifications. -
Page 37: Upgrading Edirectory To Oes
Upgrading eDirectory to OES This section discusses upgrading eDirectory to OES 2 and includes the following sections: Section 3.1, “About eDirectory in OES 2 SP2,” on page 37 Section 3.2, “Planning Your eDirectory Upgrade,” on page 40 Section 3.3, “Upgrading eDirectory,” on page 44 Section 3.4, “Post-Upgrade Checks,”... -
Page 38: Edirectory Version Considerations
(http://www.novell.com/documentation/edir88/). eDirectory 8.7.3 Novell supports eDirectory 8.7.3.9 or later on NetWare to facilitate the transition from NetWare to OES 2 SP2. Although they have somewhat different feature sets, these two versions of eDirectory are tested and certified to inter-operate within the same tree. -
Page 39: About Edirectory Management Tools In Oes 2
Several tools, many of them Web-based, can be used to manage aspects of eDirectory. The primary tools are listed here. iManager 2.7: A browser-based tool that lets you set up and manage your Novell eDirectory tree; manage eDirectory objects, schema, partitions, and replicas; and create and manage users, groups, and other objects. -
Page 40: Planning Your Edirectory Upgrade
(flat tree designed for a specific situation such as an identity vault or LDAP authentication) make better sense in your environment? Many Novell customers are opting for a flat tree so LDAP can walk the tree more efficiently to find a user object. -
Page 41: Checking Edirectory Health
User accessibility needs: Which applications and services are needed by which users? Do users need to read data or modify it? which rights need to flow from the root? How many users need remote access? Where will remote users access data from? Application needs: Which offices use the same applications? How many users are there per application? Are applications installed locally or centrally? Administrative strategies: Do you intend to manage eDirectory centrally or from many... - Page 42 NetWare can cause synchronization problems. All NDS versions should be at the latest version on their respective operating system platforms. If your version of NDS or eDirectory is outdated, download the latest software patch from Novell Directory Services Patches and Files (http://support.novell.com/patches.html). Time Synchronization: NDS communication uses time stamps to uniquely identify objects and the object's modification time for synchronization purposes.
-
Page 43: For More Information
Depending on your preference, you can perform an eDirectory server health check in several ways: Use the health check utilities in eDirectory 8.8: Novell eDirectory 8.8 runs a health check by default with every upgrade before the actual package upgrade. -
Page 44: Upgrading Edirectory
Moving to OES 2 SP2 provides an opportunity to update the tree by starting from scratch. You might consider consolidating more services while adding new OES servers. Some Novell customers have incorporated specialty trees, such as an identity vault on SLES 10 rather than on OES 2 SP2. -
Page 45: Moving, Creating, Or Importing Edirectory Users
Adding a branch to an existing tree Some Novell customers transfer objects to a new OES 2 SP2 branch and then gradually retire the older NetWare branch. By adding a branch, it's easier to drag and drop users and login scripts, certificates, and PKI so they don't need to be re-created. -
Page 46: Post-Upgrade Checks
Users can work in a pure Windows desktop environment and still take advantage of some OES back-end services and technology, without the need for a Novell Client™ or even a matching local user account on the Windows workstation. - Page 47 Windows Explorer* (CIFS) or authentication through the provided by Samba to NSS Internet Explorer (WebDAV Web eDirectory server, using common or traditional Linux file Folders). No Novell Client can be on the Windows authentication systems. machine. protocols, including Kerberos*, For eDirectory users, NTLM, and SSL/TLS.
- Page 48 DSfW User Management Overview Figure 3-2 Management Tools Users Novell iManager DSfW Administrators DSfW eDirectory server Microsoft Management Console AD server The following table explains the information illustrated in Figure 3-2. Management Tools Users iManager manages DSfW users exactly DSfW users must have the Default Domain Password policy like other eDirectory users.
-
Page 49: Additional Edirectory Resources
OES 2 SP2: Domain Services for Windows Administration Guide. For implementation information, see the OES 2 SP2: Domain Services for Windows Administration Guide. 3.6 Additional eDirectory Resources Click the following links to access additional eDirectory resources. eDirectory 8.8 Documentation (http://www.novell.com/documentation/edir88/) Upgrading eDirectory to OES... - Page 50 Health Check - Online Tutorial (http://support.novell.com/additional/tutorials/ tid10060600/) eDirectory Training Courses (http://www.novell.com/training/courseware/catalog.jsp?pl=112) OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 51: Upgrading Nss And Data Storage To Oes
It is designed to manage access control in enterprise file sharing environments. One of its key features is the Novell Access Control Model, which securely scales to hundreds of thousands of users accessing the same storage. NSS and its predecessor (NWFS) are the only file systems that can restrict the visibility of the directory tree based on the user accessing the file system. -
Page 52: Platform Differences In Nss
NSS devices and storage can be managed in the Web-based Novell iManager utility. NSS also supports third-party tools on both platforms for advanced data protection and management, virus scanning, and traditional archive and backup solutions. In a mixed-platform cluster with Novell Cluster Services... -
Page 53: Moving Data From Nss On Netware To Nss On Oes 2 Sp2
The OES 2 SP2 Migration Tool supports transferring data from a source NSS volume on NetWare to a target NSS volume on OES 2 SP2. This method preserves both the Novell Trustee Rights for eDirectory users and the NSS directory and file attributes supported by only the NSS file system. -
Page 54: Limitations
Linux to allow access to its file data. However, the open source version lacks the identity management tie-ins, and therefore, has little utility. NWFS is not supported on OES 2 SP2 and should, therefore, be moved—probably to the Novell Storage Services (NSS) file system. -
Page 55: Post-Upgrade Procedures
On Linux file systems, this is not possible, so an alternative must be found. Novell recommends the following permissions as a starting point. You might need to change the permissions to better fit your needs. -
Page 56: Upgrading Distributed File Services (Dfs) To Oes
4.6 Upgrading Distributed File Services (DFS) to The new DFS junction support on OES 2 brings the NetWare Novell Distributed File System feature set to Linux with the following additions: VLDB services are cluster-enabled. Junctions can point to subdirectories, not just the root of a volume. -
Page 57: Upgrading File Services To Oes
Native File Access Protocols (NFAP) service have now been ported to OES as Novell AFP. The Novell AFP service lets users on Macintosh workstations access and store files on OES 2 SP2 servers with NSS volumes without installing any additional software, such as the Novell Client... -
Page 58: Platform Differences In Afp File Services
“Enabling and Disabling “Administering the AFP AFP” in the NW 6.5 SP8: AFP, Server” in the OES 2 SP2: Novell CIFS, and NFS (NFAP) AFP For Linux Administration Administration Guide Guide. Filenames and Paths sys:\etc\ctxs.cfg /etc/opt/novell/afptcpd/ afpdircxt.conf... -
Page 59: Planning To Transfer Afp Services
Source Server Target Server NetWare 5.1 or later OES 2 SP2 The Novell AFP service pattern is installed but not configured. Data can be moved independently of the service. Users can always see what they have rights to see. Upgrading File Services to OES... -
Page 60: Upgrading Afp
Linux Administration Guide. Universal Password Although Simple Passwords were an option with AFP on Netware, Novell AFP requires Universal Password, as listed in Section 5.1.2, “Platform Differences in AFP File Services,” on page The process of upgrading AFP services to OES ensures that a Universal Password policy is assigned to all of the eDirectory contexts listed for AFP users on the NetWare server. -
Page 61: Upgrading Cifs File Services To Oes
Native File Access Protocols (NFAP) service have now been ported to OES as Novell CIFS. The Novell CIFS service lets users on Windows workstations access and store files on OES 2 SP2 servers with NSS volumes without installing any additional software, such as the Novell Client (see Figure 5-2). -
Page 62: Platform Differences In Cifs File Services
How Novell CIFS Works Figure 5-2 Access Methods Authentication File Storage Services CIFS Any CIFS/SMB Client (such as Windows Explorer) eDirectory users have CIFS server automatic access processes to Novell CIFS file services. WebDAV Web Folders OES Linux (Windows Explorer or... -
Page 63: Planning To Upgrade Cifs Services
CIFS services on NetWare and OES 2 SP2 Table 5-3 Service NetWare OES 2 SP2 64-Bit Support Distributed File Services for NSS Future Volumes OpLocks Cross Protocol Locking Future NSS Support CIFS-enabled shared NSS pool/ volume in a NetWare-to-NetWare or OES-to-OES cluster CIFS-enabled shared NSS pool/ volume in a mixed NetWare-to- OES cluster... - Page 64 (Consolidate and Transfer ID), but the server configuration information is transferred only with a Transfer ID migration. Upgrading Novell Samba Not Supported The OES 2 SP2 Migration Tool does not support Novell Samba as a source service for transferal to Novell CIFS. Universal Password A Universal Password policy is required for Novell CIFS.
-
Page 65: Upgrading Cifs
Section 5.3.5, “Post-Upgrade Checks,” on page 66 5.3.1 About FTP File Services Novell FTP (File Transfer Protocol) is integrated with Novell eDirectory so that users can securely transfer files to and from OES 2 SP2 or OES NetWare volumes. 5.3.2 Platform Differences in FTP File Services... -
Page 66: Planning
Transfer ID migrations must occur within in the same tree. For more information, see Section A.1.2, “Transferring an Entire NetWare Server,” on page 106. To transfer Novell FTP from NetWare to OES 2 SP2, follow the instructions in “Migrating FTP from NetWare to OES 2 Linux” in the OES 2 SP2: Migration Tool Administration Guide. -
Page 67: About Ifolder On Oes 2 Sp2
5.4.1 About iFolder on OES 2 SP2 NetWare runs only iFolder 2.x while OES 2 SP2 runs iFolder 3.8, and as the version numbers imply, iFolder on OES 2 SP2 is much more robust and flexible. How Novell iFolder 3.8 Works Figure 5-3 Authentication/File Encryption Access Methods iFolder 3.7 Services... -
Page 68: Platform Differences In Ifolder File Services
Sharing iFolders: Users can share their iFolders with other iFolder users, granting them full, read/write, or read only access. File-type Synchronization: If desired, you can limit which file types are synchronized. For a complete list of differences, see “Comparing Novell iFolder 2.x with 3.7 and Later Versions” in the Novell iFolder 3.8 Administration Guide. -
Page 69: Upgrading Ifolder
Transfer ID migrations must occur within in the same tree. For more information, see Section A.1.2, “Transferring an Entire NetWare Server,” on page 106. To upgrade Novell iFolder on NetWare to OES 2 SP2, follow the instructions in “Migrating iFolder 2.x” in the OES 2 SP2: Migration Tool Administration Guide. -
Page 70: Upgrading Netware Core Protocol (Ncp) File Services
With NCP Server, you can define NCP volumes (NCP shares on Linux Ext3 and Reiser file systems). The advantage of using an NCP server is that you can control access using the Novell trustee model. Windows and Linux workstations running Novell Client software can access data and... - Page 71 Access Methods Authentication NCP Services Access is through an NCP All file service access is Files are stored on NetWare or client—specifically, the Novell controlled by eDirectory NCP volumes that the Client. authentication. administrator has created. The same core set of NetWare file attributes are available on both OES and NetWare.
-
Page 72: Planning To Upgrade Ncp File Services
If the data is properly moved to ensure that trustee assignments are left intact, users can access their data using a Novell Client on a Linux or Windows workstation just as they did when the data resided on a NetWare server. -
Page 73: Upgrading Netstorage
NetStorage provides secure Web access to files and folders on your OES and NetWare servers. It is a bridge between a company's protected Novell storage network and the Internet. Using a Web browser, your eDirectory users can securely copy, move, rename, delete, read, write, recover, and set trustee assignments for their files from any Internet-attached workstation, anywhere in the world, with nothing to download or install on the workstation. -
Page 74: Platform Differences In Netstorage File Services
Access Methods Authentication NetStorage Server Target Servers Users have read and write File service access is The NetStorage NetStorage on OES can access to files from controlled by LDAP- server receives and connect eDirectory users based authentication processes to their files and folders Windows Explorer: Is through the eDirectory connection requests... -
Page 75: Netstorage Is Not Transferred
Despite these differences, NetStorage on OES 2 SP2 is every bit as valuable as NetStorage on NetWare and is well worth the small amount of time required to install and configure it. 5.6.3 NetStorage Is Not Transferred Because of the differences explained above, it doesn’t make sense to transfer an exact NetStorage configuration from NetWare to OES 2 SP2. - Page 76 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 77: Upgrading Print Services To Oes
The currently supported Novell print service, iPrint, is a greatly enhanced version of NDPS that is: Completely IP-based and platform independent on both the client and server side Not dependent on the Novell Client Web-based for both printer provisioning and deployment Fully cluster-aware 6.2 Platform Differences in iPrint... -
Page 78: Upgrading Iprint To Oes
If the printer/manager configurations are using IP address assignments rather than DNS, Novell recommends deploying the iPrint agent to all of the workstations and changing the existing iPrint managers to a DNS configuration. This will allow you to convert to iPrint in OES without having to revisit the workstations. -
Page 79: Additional Information
Set up iPrint on OES 2 SP2. Deploy iPrint agents to workstations. Novell's Server Consolidation and Migration Tool or the OES 2 SP2 Migration Tool are available to copy a NetWare-based iPrint/NDPS environment to an OES iPrint infrastructure. This allows for a phased parallel installation approach to an OES upgrade with minimal user and administrative impacts. - Page 80 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 81: Upgrading Quickfinder To Oes
Upgrading QuickFinder to OES is a manual process, but it is also very straightforward, as is the planning process: 1. Identify the QuickFinder service you plan to upgrade from NetWare to OES 2 SP2. 2. Install QuickFinder on the OES 2 SP2 server, using the Novell QuickFinder service pattern. Upgrading QuickFinder to OES... -
Page 82: Upgrading Quickfinder To Oes
7.4 Upgrading QuickFinder to OES Complete the instructions in “Migrating QuickFinder Server from NetWare to OES 2 Linux” in the OES 2: Novell QuickFinder Server 5.0 Administration Guide. 7.5 Post-Upgrade Considerations Complete the instructions in “Post-Migration Considerations” in the OES 2: Novell QuickFinder Server 5.0 Administration... -
Page 83: Upgrading Novell Archive And Versioning Services To Oes
Upgrading Backup Services to Section 8.1, “Upgrading Novell Archive and Versioning Services to OES,” on page 83 Section 8.2, “About Upgrading Storage Management Services (SMS),” on page 84 8.1 Upgrading Novell Archive and Versioning Services to OES Section 8.1.1, “About Archive and Versioning Services in OES 2,” on page 83 Section 8.1.2, “Platform Differences in Archive and Versioning Services,”... -
Page 84: About Upgrading Storage Management Services (Sms)
Section A.1.2, “Transferring an Entire NetWare Server,” on page 106. To upgrade Novell Archive and Versioning Services from NetWare to OES 2 SP2, follow the instructions in “Migrating Novell Archive and Version Services to OES 2 SP2 Linux” in the... -
Page 85: Upgrading Network Services To Oes
The administration of DNS does not change between NetWare and OES 2; either iManager or the Java* console can be used as the administrative tool. If you are using the Novell NetWare DNS and DHCP services and hosting it via a cluster, this configuration can also be carried forward into an OES 2 environment. -
Page 86: Upgrading Dhcp Services To Oes
DHCP infrastructure from NetWare to OES, as well as centrally administer it the same way you do on NetWare. Section 9.2.1, “About Novell DHCP in OES 2,” on page 86 Section 9.2.2, “Platform Differences in Novell DHCP,” on page 87 Section 9.2.3, “Planning to Upgrade Novell DHCP,”... -
Page 87: Time Synchronization
The source and target servers have their times synchronized. Limitations 9.2.4 Upgrading DHCP To transfer Novell DHCP services from NetWare to OES 2 SP2, follow the instructions in “Migrating DHCP from NetWare to OES 2 SP2 Linux” in the OES 2 SP2: Migration Tool Administration Guide. -
Page 88: Planning To Upgrade Time Synchronization Services
What NTP Provides All servers with Internet access can get time from NTP servers on the Internet. NTP synchronizes clocks to the Universal Time Coordinated (UTC) standard, which is the international time standard. The hierarchy that indicates where each server is getting its time is referred to as a stratum, with the first time provider designated as stratum 1. -
Page 89: Service Location Protocol (Slp)
“Caveats” on page 90 SLP on NetWare NetWare uses a Novell customized version of SLP called Novell SLP that provides an additional agent type, the Directory Agent or DA, which can synchronize information between DAs. Upgrading Network Services to OES... -
Page 90: Setting Up Slp On Oes 2 Sp2
OpenSLP, NetWare servers can also be configured to use OpenSLP. The Novell version of SLP takes certain liberties with the SLP standard in order to provide a more robust service advertising environment, but it does so at the expense of some scalability. For a... - Page 91 For additional OpenSLP setup instructions, see “Setting Up OpenSLP on OES 2 Networks” in the OES 2 SP2: Planning and Implementation Guide. Additional Information Novell eDirectory 8.8 Administration Guide, “Configuring OpenSLP for eDirectory” Upgrading Network Services to OES...
- Page 92 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 93: Upgrading Novell Cluster Services To Oes 10.1 Overview
Adding OES nodes to an existing NetWare cluster Changing existing NetWare cluster nodes to OES cluster nodes (Rolling Cluster Conversion) Using a mixed NetWare/OES cluster Using the Novell Cluster Services tool to manage live cluster transfers from the Novell NetWare OS ® to Novell SUSE Linux via a rolling conversion is one of the easier methods and is documented here. -
Page 94: Planning To Upgrade Novell Cluster Services
Typically, the primary purpose of a cluster is to provide file and print services. Make sure you check the volume resources because it is easy to overload these services. As a general guideline, Novell recommends that NSS volume resources be kept at a total capacity of 80% or less. If you need to reduce the number of standalone servers in production, the logical approach is to move data and transfer services into the high availability resources of a cluster. -
Page 95: Additional Information
Novell Consulting before upgrading a cluster. Novell Cluster Services software must be running on the OES server (SLES 10 and OES 2 must be installed on every server you want to add to a cluster). You can install Novell Cluster Services and create a new cluster, or add a server to an existing cluster either during the SLES 10/OES installation or afterwards, using YaST. -
Page 96: Caveats
Novell Cluster Services software must be running on the OES server (SLES 10 and OES must be installed on every OES 2 SP2 server added to a cluster). You can install Novell Cluster Services and create a new cluster, or add a server to an existing cluster either during the SLES 10/OES installation or afterwards, using YaST. -
Page 97: Upgrading Other Novell Products To Oes
GroupWise documentation (http:// www.novell.com/documentation/gw8/gw8_admin_qs/data/gw8_admin_qs.html#aix5v8a), this guide focuses on migrating to OES 2 SP2. For specific planning instructions, see the following information: GroupWise 7: “Planning Your Basic GroupWise System” (http://www.novell.com/ documentation/gw7/gw7_install/data/a4bblzn.html) in the GroupWise 7 Installation Guide (http://www.novell.com/documentation/gw7/gw7_install/data/a20gkue.html). GroupWise 8: “Planning a Basic GroupWise System”... -
Page 98: Preparing To Migrate
NetWare, you must upgrade to GroupWise 7 or GroupWise 8 with the latest support pack before migration to OES 2 SP2. Migrating vs. installing GWIA and WebAccess: Novell Support recommends deleting the NetWare-based GWIA and WebAccess objects and then installing new GWIA and WebAccess services on OES, even though there are instructions for migrating the GWIA and WebAccess services from NetWare to OES in the documentation. -
Page 99: Migration Instructions
“Verifying that the GroupWise Migration Succeeded” on page 100 “Transferring the NetWare Server’s Identity” on page 100 Migrating GroupWise If your NetWare server is currently running GroupWise, you must run the GroupWise Server Migration Utility before performing the Transfer ID migration. Upgrading Other Novell Products to OES... -
Page 100: Additional Information
For instruction on running the GroupWise Server Migration Utility, see the GroupWise Server Migration Utility 1.1 Installation and Migration Guide (http://www.novell.com/documentation/ gwutilities/index.html). Verifying that the GroupWise Migration Succeeded You should verify that GroupWise has migrated correctly and is running successfully for several weeks in the OES environment before completing the Identity Swap. -
Page 101: Zenworks
OES 2 SP2 platform. For an example of migrating ZENworks 7 from NetWare to OES 2 SP2 by using the OES 2 SP2 Migration Tool, see Section E.3, “Server Identity Migration,” on page 126. Upgrading Other Novell Products to OES 101... - Page 102 102 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 103: About Third-Party Applications
Two of the most important categories of third-party applications are anti-virus software and backup software. Anti-Virus Software For a current list of antivirus software vendors that support Novell Open Enterprise Server, see Novell Open Enterprise Server Partner Support: Backup and Antivirus Support (http:// www.novell.com/products/openenterpriseserver/partners_communities.html). This list is updated quarterly. - Page 104 104 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 105: Oes 2 Sp2 Migration Tool
Tools for Upgrading to OES 2 SP2 OES 2 SP2 contains the following utilities, each of which fulfills a specific migration or service- consolidation purpose as explained in the following sections: Section A.1, “OES 2 SP2 Migration Tool,” on page 105 Section A.2, “Server Consolidation and Migration Tool (SCMT),”... -
Page 106: Transferring An Entire Netware Server
Migration Tool Administration Guide: “Migrating AFP from NetWare to OES 2 SP2 Linux ” “Migrating Novell Archive and Version Services to OES 2 SP2 Linux” “Migrating CIFS from NetWare to OES 2 SP2 Linux” 106 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide... -
Page 107: Server Consolidation And Migration Tool (Scmt)
Support for migrating from newer NetWare platforms has not been removed from SCMT (as reflected in the Novell Server Consolidation and Migration Toolkit Administration Guide). However, Novell recommends using the OES 2 SP2 Migration Tool rather than SCMT when possible. A.3 NetWare Migration Wizard ®... - Page 108 108 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 109: Novell Imanager 2.7
Available Novell Plug-in Modules: iManager 2.7 lists all the available iManager plug-ins contained in the packages directory/download site by default. You can download and install plug-ins from within iManager by querying the Novell download Web site. The previous versions of iManager listed only the updates to the installed plug-in modules. -
Page 110: Supported Web Browsers
Guide. B.2 Novell Remote Manager (NRM) Novell Remote Manager for OES is a browser-based utility that can be used to manage one or more OES servers from a remote location to monitor server health, change the server configuration, or perform diagnostic and debugging tasks. -
Page 111: About Novell Remote Manager And Oes 2 Sp2
B.2.2 About Novell Remote Manager and OES 2 SP2 There is no need to migrate Novell Remote Manager (NRM) from NetWare to OES 2 SP2. Instead, this service can be installed when any Open Enterprise Server pattern is installed. Then, if you have created server groups for monitoring NetWare 6.5 servers, they can be accessed and monitored from... - Page 112 112 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 113: C Workstation Considerations
Section 3.5, “About Domain Services for Windows,” on page Novell Client As OES 2 is implemented, existing clients can be used (Windows XP, 2000, NT, Vista). However, an upgrade to the latest clients and workstation OS is required to take full advantage of the new features of eDirectory and OES 2, such as NMAS and Password Self Service. - Page 114 114 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 115: D Server Consolidation
Server Consolidation The OES 2 SP2 Migration Tool includes a Consolidate migration type that is specifically designed to support server consolidation. For more information, see Section A.1.1, “Consolidating Selected Data or Services,” on page 105. Server Consolidation... - Page 116 116 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 117: Replica And Ca Server Migration
Examples ® This section contains a few real-world examples of upgrades to OES 2 SP2 that Novell customers have done. If you have an example you want to share, please submit a User Comment for this page with your e-mail address, and we’ll contact you. -
Page 118: Preparing And Transferring Your Replica Server
DNS /etc/hosts server are correct. Apply the latest SLES 10 SP3 and OES 2 SP2 patches from the Novell Customer Center to the target server. For more information, see “Updating (Patching) an OES 2 SP2 Server” in the OES 2 SP2: Installation Guide. -
Page 119: Cluster Migration
If it is not working, rebuild the VLDB using the instructions in “Repairing VLDB” in the OES 2 SP2: Novell Distributed File Services Administration Guide. 4 For information about time synchronization services on a Novell network, see “Time Services” in the OES 2 SP2: Planning and Implementation Guide. -
Page 120: General Notes And Tips
E.2.2 General Notes and Tips In the YaST install, clustering is disabled by default. To set up clustering, you must enable it for configuration. See “Novell Cluster Services Parameters and Values” in the OES 2 SP2: Installation Guide. Clustering on OES 2 SP2 is case-sensitive. Always make sure that you have specified the correct case for each name, etc. -
Page 121: Transferring Dhcp In The Cluster
“Adding New OES 2 Linux Nodes to Your NetWare Cluster” in the OES 2 SP2: Novell Cluster Services 1.8.7 for Linux Administration Guide. 3 Set up an OES DHCP cluster resource using the instructions in the first three section only of “Installation and... -
Page 122: Transferring Dns In A Cluster
Continuing with the same example, you use the following command to copy and rename the file: cp /var/opt/novell/dhcp/leases/DHCP_SERVER.leases /media/nss/DHCP_VOLUME/ var/lib/dhcp/db/dhcpd.leases 11 Offline the DHCP cluster resource that has been running on NetWare. 12 Online the OES DHCP cluster resource. -
Page 123: Iprint Migration In A Cluster
The script also assigns access and ownership rights for the preceding directory to the DNS user. 4 Run the DNS Server by using the following command: /opt/novell/named/bin/novell-named -u DNS_User -V DEST_DNS2_VOL This step ensures that DNS server is running on the cluster node. - Page 124 You must create the iPrint NSS pool and volume as instructed in Step 2 on page 120 prior to adding OES nodes to the cluster or running the migration. Transferring iPrint in a Cluster 1 Download the script (http://www.novell.com/documentation/oes2/scripts/ iprint_load.sh iprint_load.sh) and the script (http://www.novell.com/documentation/ iprint_unload.sh oes2/scripts/iprint_unload.sh)
- Page 125 /opt/novell/iprint/bin ./iprint_nss_relocate -a admin.fqdn -p password -n NSS/path -l cluster For example, enter ./iprint_nss_relocate -a cn=admin,o=novell -p novell -n /media/nss/ NSSVOLNAME -l cluster 8 Migrate the iPrint resource to another OES 2 SP2 node in the cluster, then repeat...
-
Page 126: Transferring Afp In A Cluster
IMPORTANT: When you authenticate to the source and target servers, use the IP address of the source Novell Cluster Services iPrint resource (secondary IP) and the IP address of the target Novell Cluster Services iPrint resource (secondary IP). file is located in the directory. -
Page 127: Preparing And Transferring Your Replica Server
DNS /etc/hosts server are correct. Apply the latest SLES 10 SP3 and OES 2 SP2 patches from the Novell Customer Center to the target server. For more information, see “Updating (Patching) an OES 2 SP2 Server” in the OES 2 SP2: Installation Guide. -
Page 128: Post-Migration Steps
OES 2 SP2: Migration Tool Administration Guide. ZENworks 7 “Novell ZENworks 7 Desktop Management” on page 128 “Novell ZENworks 7 Server Management” on page 128 IMPORTANT: You need the ZENworks for Desktops 7 SP1 IR3a HP4 patch for imaging on 64bit Linux . - Page 129 6. If you were using variables, access the Subscriber and re-create the variables, making sure they point to the new location on the OES 2 SP2 server. 7. Open the ports in the firewall on the OES 2 SP2 server. “Ports used by ZEN” (http://www.novell.com/support/php/ search.do?cmd=displayKC&docType=kc&externalId=3880659&sliceId=1&docTypeID=DT_ TID_1_1&dialogID=22570644&stateId=1%200%2022568512)
- Page 130 130 OES 2 SP2: Upgrading to OES—Planning and Implementation Guide...
-
Page 131: F Documentation Updates
Added more links to resources. Help Me with My Migration?” on page 27 August 4, 2009 Chapter or Section Changed Summary of Changes “Why Not Stay on NetWare?” on page 13 Added a link to a new Novell white paper. Documentation Updates... - Page 132 Chapter or Section Changed Summary of Changes “Caveats” on page 90 Removed the caveat about not configuring a client to access both Novell SLP and OpenSLP. The item was apparently erroneous. June 15, 2009 Chapter or Section Changed Summary of Changes Section 6.3.2, “Limitations,”...