NetWare to OES2 Linux Migration Guide

Back in June of 2007, I wrote a migration guide for NetWare to OES1. While there are similarities between the OES1 and OES2, there are also major differences. For the sake of a complete HowTo on migration, I have included those similarities here so the reader does not have to jump between multiple documents. What is not covered in this article are the enhancements you can apply, such as AutoYaST, to increase the efficiency of your own migration experience.

Note: At the time of writing of this article, ZENWorks Desktop Management 7 SP1 is not supported with OES2. There is a IR1 Hotfix to be released in latter January 2008 that will address issues related. I have included the installation of ZENWorks 7 because it is my personal experience that Application Objects are not affected and because earlier versions of ZENWorks do not support eDirectory 8.8.2 and vice versa.

Please make modifications to the data, where noted, to reflect your own organization's structure.

Other resources

Novell Open Enterprise Server 2 Migration Best Practices Guide


The services to be migrated include:

  • Data – User and other shared


  • ZENWorks – Applications and policies

  • Backup – RSYNC

  • After the migration is completed and tested, decommission of existing NetWare servers

The steps to perform the migration are listed here:

  1. Preparing your current environment.

1. Preparing your Environment

OES2 installs eDirectory 8.8.2 and can affect other applications in your environment. To see a list of which Novell applications are compatible with eDirectory 8.8 and which are not, look
Comment List
    I found the below rollback option, but it did not work (sure the command that i used was with my server options)
    the server replied "This option is not allowed in OES"

    Anybody any clues other than reinstalling the server and OES


    /opt/novell/eDirectory/bin/ndsconfig add -t 'treename' -n 'ou=context.o=novell' -a 'admin.novell' -p -d /var/opt/novell/eDirectory/data/dib -D /var/opt/novell/eDirectory -B -L 389 -l 636 -o 8028 -O 8030 --config-file
    Now just re-execute the same command but add -w
    while performing the upgrade, the process needed to be interrupted, after the dib migration.
    now the netware 6.5 was locked, but a dsrepair fixed it.
    However the oes2 server is also locked and i did not find a way to unlock it
    any idea
    Is there an updated document on this process, since EVMS has been dropped from SLES 11?

    Thank you!
  •   in reply to MigrationDeletedUser
    You can't. NetWare is it's own OS kernel and NW 6.5 SP7 is the latest version of that OS. OES 2 Linux is an addon for SLES 10 Linux. I think you're confused because after NetWare 6.5 SP4, Novell referred to this product as Open Enterprise Server, which is true. Although, OES Netware and OES Linux are both Open Enterprise Server, they are still completely different OSes with similar features and functionality. More than likely to ease the transition from NetWare to OES2 Linux.

    Anyone else care to add to this?
    I think this may be more common than we think. My friend thought that BorderManager ran on Linux because the OS "Version" command stated Open Enterprise Server.

    Just like SLES10SP1 allows installing OES2 as an add-on module to make OES2-Linux, is there a similar method to install OES2 on top of Netware6.5 to make OES2-Netware?

    Netware 6.5 SP7 does not seem to prompt user to install add-on module as does SLES10 during install procedure, and runs to completion.

    Any idea?

  •   in reply to MigrationDeletedUser
    There is no in place upgrade for this TTBOMK. But I have migrated a few Redhat servers using LDAP into eDir.
    So in a nutshell:
    - setup your new OES2 server
    - ldap export your current Linux users on sles 9 (based on no eDir), be sure to export userPassword.
    - import the users via ldap
    - export import the groups via ldap
    Tools : openldap
    Great information here. Many of these examples worked well in the labs I have been doing for customers. Keep in mind many customers will be moving from 32bit SLES9 on 64 bit hardware to 64 bit SLES10 sp2 on 64 bit hardware. Server to server migration with the target server tools would be your easiest path. In the case of single server inplace upgrades you will need to do some home work before you attempt at 32 bit OS to 64 bit OS swap. Remove all the OES applications from startup before you upgrade the OS. Then install the OES2 application stack.
    Clustering is another popular configuration, for customers that are running mixed NetWare and OES SLES9 nodes, I would plan on stopping this practice before moving to OES2sp1/SLES10sp2 this winter.

    This seems to deal with migrating from Netware to OES2. We are about to migrate from OES (sles 9) to OES2. Does anyone know the process for this, ie will the SCU on OES2 work equally well with OES to OES2 migrations ?

  •   in reply to MigrationDeletedUser
    I've done this very thing and its fine, as long as your replicas remain on One thing to note, if you have less than three replicas in a partition then when you install the OES2 server into it, it will try and become one. I had that problem, it took some effort to fix.
    I have a question about ZENWorks and eDir 8.8 compatibility. In your guide you wrote:

    If you have a version of ZENWorks prior to 7 SP1, I would suggest upgrading to this version prior to introducing eDirectory 8.8 into your tree. eDirectory 8.8 does not replicate attributes of prior versions of ZENWorks.

    We would like to add some OES2 servers with eDir 8.8 into our tree. We will keep our replica servers eDir We are planning an upgrade to ZENWorks 7 SP1 but that will not be ready for a long time. The OES2 (8.8.x) servers will be in the tree, but not replica servers.

    Do you think this will cause a problem with ZENWorks?