Rename NCP Server object in eDirectory in Linux

(Last modified: 21Nov2005)

This document (10099717) is provided subject to the disclaimer at the end of this document.

goal

fact

Novell Open Enterprise Server (OES)

Novell eDirectory

fix

The simplest way to rename an eDirectory server hosted on Linux is to use the ndsconfig utility with a 'set' parameter. An example follows:

ndsconfig set n4u.nds.server-name=myNewServerName

Replace 'myNewServerName' with the new server name. Once you have done this you will be prompted for your eDirectory authentication information (dot-notation). After successfully authenticating wait about ten seconds and refresh your view of eDirectory and you should see the new server name.

If you would like some of the objects in that same context to reflect the same server name restart the eDirectory service on that box:

/etc/init.d/ndsd restart

You should now see your SAS and Key Material Objects (KMO) with the server name correctly reflected in their names. This step is probably not required immediately after the server rename. Applications depending on those objects and their names should continue to work.

note

Setting many server-related variables can be done with this same command but with a different variable specified. Type `ndsconfig get` (without backticks) to see a list of variables.

Caution: Changing these variables may cause problems on your server or in your tree. Be sure of what you are doing before making any major changes in a production environment. These settings should all be considered major.

After renaming your server you probably will not want to run `ndsconfig upgrade` immediately because it will create duplicate SAS and KMO objects for the server. Restart ndsd before running that command to have the original objects renamed.

document

Document Title:	Rename NCP Server object in eDirectory in Linux
Document ID:	10099717
Solution ID:	NOVL104294
Creation Date:	17Nov2005
Modified Date:	21Nov2005
Novell Product Class:	Novell Directory Services

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.