Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Need to remove GW5.5 form a server

Status
Not open for further replies.

pipil2

Technical User
Aug 5, 2004
63
US
Hello all,
I have a server that will be removed from the tree, this server has GroupWise 5.5 enhance sp5 and is part of 5 offices the main PO is on a different server. my question is:
what I have to do or how to remove this PO and other GW objects from this server/NDS so the other GW servers will not see it again or complain when deleted.

thanks.
 
Depending on how complex the environment is and your skill level, a GroupWise consultant to help you plan this stuff out may be money well spent. If you are determined to forge ahead alone, here is a general outline. You may want to build a test environment on some old hardware that mimics your live system, that way you can do it over a few times and see how it should go. When I was just starting out as a GroupWise admin, I learned the hard way that you never want to try stuff like this for the first time on a production network.


First, be CERTAIN that the server does NOT hold the primary domain.

If you need to migrate users to another server, do so.

Once you have everything off that you want off, simply delete the POA and PO objects in NDS, along with any gateways, take the agents down, and you are done.

 
Well, I'm not a GroupWise expert I'm getting my way around, actually I will be doing this on a test-lab network with the real servers(images),now you mentioned migrate users from one PO to another one, do you know a good tid to do the user migration let's say to the main office server it's only 2 users.
for give my weak knowledge when you say Along any gateways, can you explain that some more?

thanks.

 
Maybe a simpler thing to ask is if you have one domain or many, with one or more Post Offices. Somewhere there is an MTA which moves messages between post offices. Somewhere there is an Internet Agent which moves mail in and out of the system. Depending on your environment you may have other gateways as well.

Here is a good TID on user moves.

 
Ok, there are one primary and 4 secondary domain the other 4 are located in the USA and europe each site have their own PO and MTAs, one of the sites will taken out of tree

thanks sstoppel.
 
OK, so a site in a secondary domain is going away.

Move the users and VERIFY they can log in and use their mailboxes on the new server
Down the POA and MTA from the remote site
delete the objects in the tree that point to those objects
delete the Post Office and Domain objects for the remote site.

Unless you need the space back, leave the file systems that correspond to the deleted objects. If something happens and you need them back, you can recreate the NDS objects and re-associate them with the file system. Then after a while, when you are sure you will never need them again you can delete the secondary domain and PO file areas as well.
 
Cool man I'll do that, i appreciate your help.
have a good day.
 
Well, what SSTOPPEL says on the removal of the retired domain and po is along the right guidlines, but the whole deal with moving users between post offices? Think about your link speeds on this and how big the mail boxes are. Even when my users were at mail box sizes of just 5 megs, I would not use the move features with in 5.5. Infact, Novell didn't get good code for moving users until 6.5SP3

The not so easier, but much more dependable way is to archive the users entire mailbox, then copy the arcive files to off line media or move them across the network to a storage location near the destination PO. You can then move the user if you wish, it's an empty mail box so there are less chances of issues, but you may also find users will still get stuck in a move state, which can be a real pain to recover from. The way I have done it is to just archive, delete the user inthe old PO, create a new user mail box in the destination PO, use the Archive FID editor to change the user FID to the new FID, then un archive the mail box.

You can get instructions on how to use the FID editor here.


May sound like more work, but in the end, you will complete the project with more hair on your noggen and less neck twitches the head aches the 5.5 user moves cause.

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Certified nut case [hippy]
Senior Network Engineer
 
hi Provogeek,
Sounds good, fortunatly I only have 2 users and I will follow your advise on archiving their emails sounds more practical than moving them across the wan.
thank you for your advise and have a good day.
 
Just migrate to exchange. I'm sure it's much easier than whatever you're trying to do. :p

(Sorry, somebody stuck MS in my head today and I've become delusional.)

Marvin Huffaker, MCNE
 
sure,...see ya guys thanks for everything
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top