Originally Posted by ctaylor_wsc
|
|
The main reason for combining the servers is $$$. Our two current servers are both out of warranty and we only have the money to replace one.
|
How big an issue would it be to leave the old GIWA/Webaccess server up and running?, if the hardware is still in good order that is... Both processes don't need a high end server and are easy to recreate if the server does crash. You'd only need to focus on the domain/po move. Just a thought...
|
Quote:
|
|
As far as legacy settings, object location is the main thing. Also, if I do drop the secondary relay domain, I want to make sure that it is completely removed once I'm am done.
|
In that case grafting will do the job nicely, no need for a new domain/po.
|
Quote:
|
|
If I rename change the extension on the jar files in the snapins/groupwise directory under ConsoleOne, that will effectively "remove" the snapins, right? I'll have to do some reading up on grafting.
|
True... still I'd advise in downloading the latest ConsoleOne from the Novell site, install this on a clean pc. That way you're sure to only have the standard snapins running.
Some info on Grafting:
Novell Documentation
10016938: How to move a Novell GroupWise Post Office to a new NDS context.
For testing purposes you can set up an isolated test system to see how the grafting process works.. you can even use a copy of your existing GW system (domain and po), import the copy into your isolated eDir by grafting it in any container your wish. (example for regrafting into new tree - more steps then are needed for you running system!:
10007622: Moving a GroupWise system to new server in new NDS tree (basic))
When grafting the PO, also regraft users and check the associations using the Groupwise invalid association tool (container option).