Filtered Index

My company needed a way that users at the different branches could still function and perform their duties, even when the local branch server was down. The following should at least let you begin thinking about how this could be handled.

64bit OES2 SP1 server installed and configured with eDirectory. Registered to Novell Customer Center and updated with latest patches. Upgrade OES2 SP1 with 32bit novell-sss to OES2 SP2 using online rug upgrade. Upgrade fails with error “Dependency resolution failed:”. Here's a solution from hemajoshi.

When OES2 was released, NTS told us that it might be better to keep the SLP DAs on NetWare - which we did, but now we finally need to move those.

As I have understood there is still no Novell SLP on OES2, "only" Open SLP?
How do we make fault tolerant, as we cannot have such single point of failure?

Any experiences on this?

This article describes the import/export operations of Novell DHCP Service. The import/export functions are required to transfer Novell DHCP Service configuration's from system files to eDirectory and vice versa.

Set directory quotas on NSS with OES2 Linux.

ssutapalli explains how to use a new feature in iFolder to recover a Passphrase.