When I migrated our Groupwise server to a new machine, I decided to change around some of the volumes.
In this example, I moved GWDOMAIN from BORDER\SYS:\ to BORDER\Groupwise:\
First I shut down all groupwise agents/NLMs on the server. Then I made the config changes and brought groupwise up like normal.
Here are all of the configurations I had to change to make the move work:
gwia.cfg
from
/Home-\\border\sys\gwdomain\wpgate\GWIA
to
/Home-\\border\groupwise\gwdomain\wpgate\GWIA
domain.mta
from
/home-\\BORDER\sys\gwdomain
to
/home-\\BORDER\groupwise\gwdomain
webac70a.waa
from
/ph=\\Border\sys\GWDOMAIN\WPGATE\WEBAC70A
to
/ph=\\Border\groupwise\GWDOMAIN\WPGATE\WEBAC70A
gmtacfg.ini
from
BackLink=\\BORDER\sys\gwdomain\GWAVA\config
to
BackLink=\\BORDER\groupwise\gwdomain\GWAVA\config
ConsoleOne
GWIA-
"Server Directories" Tab had to be modified
Domain Object Properties- UNC Path:
from
\\BORDER\sys\gwdomain
to
\\BORDER\groupwise\gwdomain
GWAVA 3.x:
edit thie file: gwdomain/gwava/config/gmtacfg.ini
The following lines had to be modified:
Home=\\BORDER\groupwise\gwdomain
MTASieveBase=\\BORDER\groupwise\gwdomain\GWAVA
ProgramBase=\\BORDER\sys\SYSTEM
ArchiveDirectoryPath=\\BORDER\groupwise\gwdomain\GWAVA\archive
POQueuePath=\\BORDER\groupwise\gwdomain\GWAVA\config\poq
Sunday, September 2, 2007
Subscribe to:
Post Comments (Atom)
1 comment:
Nick, helping a friend with her Kelnhofer history..email me at
tammy54321@hotmail.com
Would love to see if your linked.
Tam
Post a Comment