As it was posted 5 months earlier:

>Please find the steps required for removing a DSFW from your server.
>From here the OES2SP3 server is being referred to as ADC (to be
>- Make sure to do a health check first, to make sure eDirectory is
>healty before executing the procedure below.
>For more information please see the link below:
>'Support | NDS / eDirectory Health Check Procedures - Cross Platform'
>- Remove the replicas of the Partition which is mapped to the DSFW
>domain from the ADC which has to be removed.
>- Remove the replicas of the schema and schema.configuration
>partitions if present from the ADC that has to be removed.
>- Remove the server from the tree, using ndsconfig rm
>- Delete all the references to the server, like certificates, ldap
>server / group objects.
>For more information please see the link below:
>'Support | How to remove eDirectory from a Linux server'
>- Delete the Domain controller object for this server in the
>ou=domaincontrollers container.
>- Export the dns zone used for the DSFW to a file (to have a backup)
>- Using iManager - dns management, Manually remove all records /
>references to either ip address or servername for the ADC that has
>been removed from the tree.
>Before removing the server the tree, all normal eDirectory
>precautions should be taken in consideration, for example which
>server is hosting the CA, making sure there are no partitions with
>single replicas. <<

Or is there a new procedure for OES2SP3 32-bit. (The remaining are
OES11SP1 servers).

W. Prindl