information technology central services at the university of michigan WednesdayJanuary072009
University of Michiganitcs home
search itcs
find a person or group at U-M
Novell at University of Michigan
LNGS Home
Novell Home
ITCS Services
eDirectory
OES - Netware/Linux
nds routine maint
nw @ u of m
nw 5.0
nw 5.1
nw 6
nw 6.5
dns/dhcp
SuSE
How-To
ZENworks
Training
Licenses
Help


Remove a NetWare or Linux server from the MICHIGAN tree

Last Updated: February 14, 2008

It is important to remove a server from its tree in a way that informs eDirectory about its removal and allows that information to be communicated tree-wide. The procedure to do so is simple and you can easily do it yourself without the intervention of Novell Support.

The Procedure (server is still up and running):

  1. Be absolutely certain you have copied all data from the server, you have several good backups or it is no longer needed. Once the server has been removed from the tree there will be no way to retrieve the trustee/rights assignments to the files on the server.

  2. NetWare: Use NWCONFIG.NLM to remove NDS from the server.

    At the server console type NWCONFIG.
    Choose Directory options
    Choose Remove Directory Services from this server
    Respond to the prompts. When you are prompted for Directory Services Login/Authentication, supply your administrator name (admin.dept.umich) and password.

    Linux: use the command ndsconfig rm -a admin id, where admin id is your container administrator userid

  3. If the server you are removing has one of three (or fewer) replicas of your container (or if you are not sure), contact Novell.Support@umich.edu to place a third replica on another server.

  4. If you are on central campus, submit a NICR (Network Information Change Request) so that the databases can be updated. You can view your current NICR or get more information about the UMNet-Admin databases. If you are not on central campus, look at the UMNet-Admin page for information about whom to contact in your area.

The Procedure (server is not up and is no longer able to run):

If the server in question has crashed, been sent to Property Disposition, or has been down for a few weeks, then it must be removed from the tree manually (the hard way). Follow the instructions in Novell support TID #3338221. (To get that TID, go to the Novell support web site and enter 3338221 in the search box.

The TID specifies several DSREPAIR operations; run those on any replica-holding servers you have. Once you have finished all of the steps in the TID, contact ITCS Novell Support and they will run the DSREPAIR steps on their replica holders as well.

That's it. By following this procedure you will have done your part to ensure the Michigan tree remains healthy.

Your fellow Novell administrators thank you.

To offer constructive criticism, or provide other feedback about our site, click here.

ITCS
Information Technology Central Services at the University of Michigan

er.html" -->