dep2002
asked on
Removing a Netware 6.5 sp7 server from the Tree Permanently
I am trying to remove a Netware 6.5 server from the tree Permanently. This server is a Secondary server and has a Read/write replica on it. All data has been moved off as well as any users. My plan to remove this server is as follows.
1. Perform Heath check against Edirectory Tree.
2. Go to NWCONFIG and choose Remove DS from this server.
3. Delete all the references in NDS using ConsoleOne or NWADMIN for Licences.
Here is where I am confused. Many Posts say to go into C1 and delete the replica and wait until all servers sych. (This would be done before my Step 2) Is that necessary? Wouldnt going into NWCONFIG accomplish the same thing?
1. Perform Heath check against Edirectory Tree.
2. Go to NWCONFIG and choose Remove DS from this server.
3. Delete all the references in NDS using ConsoleOne or NWADMIN for Licences.
Here is where I am confused. Many Posts say to go into C1 and delete the replica and wait until all servers sych. (This would be done before my Step 2) Is that necessary? Wouldnt going into NWCONFIG accomplish the same thing?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
the New server was left over from a copy / past action from a similar question where one server was replaced by another. IMHO removing DS with nwconfig will not damage edirectory.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The server has been taken out of service with very few problems. Thanks for all your help.
Hello all,
NWCONFIG -DSREMOVE should do it. Couple of things though.
1. If your servers are not in sync, you may have to do the -xk2 -xk3 for forcably kill the server. DON'T DO THIS without digging a bit further into how and why you need to do this.
2. Really, make sure that you do not have any replicas on the server. It goes better that way.
3. Most people miss this. If your server is CA root, you need to move that to another server FIRST.
4. Time!!!! If this server is a secondary, not a problem. Make sure in MONITOR that it is! If it is a primary or single, you need to change that. If you are running XNTPD, you need to figure that out too.
5. Remnents! I have yet to take a server out of eDirectory and see all of the objects associated with that server actually removed. You may have to go into c1, nwadmin, iManager and remove volume objects, volume pools, SLP objects, etc.
6. Finally, once the server is removed, MAKE SURE that eDirectory is healthy, and there are no stuck obituaries out there. Give it a hour or so, depending on how large your eDir is. Then go into all the servers and make sure a healthcheck comes back clean.
Tom
NWCONFIG -DSREMOVE should do it. Couple of things though.
1. If your servers are not in sync, you may have to do the -xk2 -xk3 for forcably kill the server. DON'T DO THIS without digging a bit further into how and why you need to do this.
2. Really, make sure that you do not have any replicas on the server. It goes better that way.
3. Most people miss this. If your server is CA root, you need to move that to another server FIRST.
4. Time!!!! If this server is a secondary, not a problem. Make sure in MONITOR that it is! If it is a primary or single, you need to change that. If you are running XNTPD, you need to figure that out too.
5. Remnents! I have yet to take a server out of eDirectory and see all of the objects associated with that server actually removed. You may have to go into c1, nwadmin, iManager and remove volume objects, volume pools, SLP objects, etc.
6. Finally, once the server is removed, MAKE SURE that eDirectory is healthy, and there are no stuck obituaries out there. Give it a hour or so, depending on how large your eDir is. Then go into all the servers and make sure a healthcheck comes back clean.
Tom
ASKER