Moving a groupwise 7.x GWDOMAIN folder

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

MSIZAP - Windows Installer CleanUp Utility

After upgrading my network to ZFD 7.01 Hot Patch 5, I had a corrupted install of Zenworks for Desktop Agent on a machine that I couldnt upgrade or uninstall. I kept receiving the error -1722 "there is a problem with this windows installer package"

Eventually came across TID 10088429, which explains that this is simply inevitable on some machines when upgrading to ZFDAgent 7.0.1.4 (which is the latest version in Hot Patch 5). They reccommend using MSIZAP to blow away the msi info and let you install a new one without any problems.

I have to say that I am in love with MSIZAP aka Windows Installer CleanUp Utility, an invaluable little tool for dealing with naughty MSI's.

here is the KB Article on MSIZAP: http://support.microsoft.com/kb/290301

Rebuilding a Zenworks Server

If you have to blow away your zenworks for desktops server, make sure you delete the eDirectory objects before you install your new server, or it may not work properly.

Some of the eDirectory Objects include (using servername "zen" as an example):
ZEN-ZIS (Imaging Server object)
WOL Service_ZEN (wake on lan service)
Desktop Management Database_ZEN
Inventory Database_ZEN
Inventory Service_ZEN

*There are many other objects that should be deleted, but are not zenworks related so I will not be listing them here. there may be other zenworks objects as well, this is just for ZFD (Zen for desktops) as that is all I am running.


Background:
After a lengthy and unsuccessfuly repair process on my crashed zenworks server I decided to blow away the server and rebuild it since there wasn't any user data other than my workstation images (Bad VCU! Bad VCU! ...I wont go into this here...). After rebuilding the server, Zenworks Imaging would not work. I could take/restore an image manually, but automatic imaging attempts would return "no work to do" and never take the image. In the server logs I had the following error in the image server log (sys:system\zimglog.xml):

Status> Failure
ErrorMessage> Undefined error message
Timestamp> Fri Jun 22 14:03:36 2007

After pulling my hair out because of the "undefined error message" I decided to check the tree for any zen objects, delete them, and reinstall zenworks. After doing this, automatic imaging started working instantaneously. Specifically, the old ZEN-ZIS object was causing the problem.



Lesson of the Day: Delete server objects in eDirectory after blowing away a server, but before installing a new server of the same name.

Mission Statement

I've decided to make my own contibution the sea of internet blogs out there. The purpose of this is to blog Tech related information in my experience as a Network Administrator for two different companies. One public and one private sector... one Novell eDirectory network, and one Microsoft Active Directory network.

The main purpose of this blog will be to document caveats and not-so-well known fixes and processes that I have found to be extremely useful in my day-to-day tech life. I cannot count how many times I have found a forum post or a random blog with the answer to my unique problem, after hours and hours of searching. Hopefully this blog will randomly help someone out in the future (likely by a cached google search result as I so often use). I will not be restricting this blog to those specifics, however, I will allow the blog entries to wander a bit.