Cool Solutions

Migrating GroupWise to New Hardware


January 29, 2008 8:09 am






A Forum reader recently asked:

“I am doing a hardware upgrade on my single GW server running GW 7.01. Following the hardware upgrade, when the new server takes on the identity of the old one, do I run a new install or do I upgrade from the GroupWise setup
option? I plan to move the entire GroupWise directory structure over.”

And here is the response from Michael Bell …


GroupWise migration is easy.

1. Down the old POA.

2. Move structure over. Make sure you move your startup files and gwia.cfg, etc., too!

3. Reinstall the agents. For example, with the POA and MTA just go the agents subdir, run setup/install, and just click ok repeatedly. Don’t add the startup file info when it prompts. For GWIA, run with the /copyonly option.

4. Check startup files for any hard-coded IP or volumes. See note on #5.

5. Check GroupWise objects in ConsoleOne for unc/IP stuff. If the unc (server, volume, and path) and IP address are both the same, this will be incredibly painless – no work needed.

6. You’re done!

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.