Cool Solutions

Important information for the April update for OES



May 16, 2013 1:09 pm





The April schedule maintenance update for OES2 SP3 and OES11 brings a significant update to eDirectory. Prior to this update eDirectory on these platforms was at various patch levels of 8.8 SP6. The current update makes eDirectory 8.8 SP7 Patch 3 available to these platforms in addition to OES11 SP1.

A list of fixes included in eDirectory 8.8 SP7 (in addition to fixes in the various past support pack and patch levels of eDirectory) can be found in TID 3426981

This is especially being done to make sure that customers on older version of OES get the current stable version of eDirectory. This assumes significance in the context of the impending end of general support of OES2. Novell thinks this is best for the continued support and maintenance of these platforms through the extended support period.

Of importance is that, to take full advantage of eDirectory 8.8 SP7, a schema extension is needed. However, this is not automatically done as part of the patch installation, as schema extension needs manual intervention and administrator credentials. So, it’s recommended that the schema is extended prior to applying the patch or soon after, depending on the best practices followed in your organization for patching and schema extension. This schema extension also enables interoperability with IDM 4.

Some helpful information to be aware of:

  • Even if the schema extension is not done, eDirectory 8.8 SP7 services come up and ndsd continues to work fine. However, we recommend it be done ASAP either before or after the update.
  • To avoid issues during patching, the previous patches of eDirectory 8.8 SP6 have been removed the patch channels and they will be available for download on the patch finder.
  • If you apply this patch on a version of OES and upgrade to a higher version (say OES2 SP3 to OES11, or OES11 to OES11 SP1) it might downgrade the version of newer OES platform, unless that platform is also patched as part of the upgrade process. There are automated checks which will halt upgrade process to prevent issues and allow you to proceed only after patching.
  • If you apply this patch on a version of OES which has ConsoleOne installed to administer Groupwise on the OES Server, you may encounter package conflicts. Refer to TID 7010864 to resolve this

We’ll keep adding more information and useful pointers in this regard.

Do post your comments / suggestions to /

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Announcements, Expert Views, Open Enterprise Server


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.


  1. By:Spauwels

    1) We are in the migration process where we still have NetWare servers, OES 2 and OES 11 ….
    What will be the impact of this update on the NetWare servers ?

    2) What would be the best strategy: Upgrade OES 11 first than OES 2 ?



    • By:hvaughan

      1) There is no impact to NetWare servers in any regard, provided schema is properly extended. We assign a high priority to backward compatibility when developing a new version of eDirectory. In regards to the schema update specifically, your NetWare servers may not be able to take advantage of the new features eDirectory 8.8 SP7 brings but they will continue to function as they do today.

      2) Since OES 11 and OES 2 SP3 both run the same version of eDirectory, 8.8 SP6, there is little difference between them in terms of the upgrade process. I would instead recommend basing your choice of who to upgrade first on replica placement, specifically [Root]. If this is to be the first eDirectory 8.8 SP7 server in your tree I would find a server holding a read-write or master of [Root] and perform the first upgrade there. This ensures schema gets properly extended to all servers though there are many other methods.

      We have just posted the schema files and instructions for those customers wishing to extend schema manually before starting your upgrades. They can be found here:

      Cheers to you as well,

      – hines