[ngw] 'moving' from GW8/NetWare to GW12/Linux

Danita Zanre dzanre.ngwlist at gmail.com
Mon Feb 3 20:09:40 UTC 2014

Here's what I'd do:

1.  Create a new secondary domain on Linux.  
2.  Promote it to primary
3.  Upgrade it.
4.  Create PO
5.  Move users

As Todd points out, the resources can be moved - they just need to be assigned to a user on the new PO - so get a user over who does NOT own resources first (perhaps an administrative type of user) and then assign the resources to that account as you move them.  

You do not lose single-instance storage.  GW after about 6.5 is smart enough to manage this during a move,  

FIDs will not be changed (unless there was a conflict, so don't create "new" users on the new PO until you've moved everyone just t be sure no conflicts are created).  

Danita Zanrè
Become a GroupWise Power Admin!  


Sent with Mail Pilot  

On Feb 3, 2014 12:43:14 PM, Michael Statman <Mike at emesconsulting.net> wrote:  
I have a customer who's been stuck on GW8/NetWare because of an NLM fax
gateway that is still in production. We want to get moved to GroupWise
12, but since we still need to use the gateway it precludes a standard
migration. (There's a replacement in the pipeline, but requires some
hardware changes and telco updates and it's just not happening anytime

The existing system has a primary domain with a single post office, as
well as the fax gateway in this domain, on the NetWare server. (There
also exists a secondary domain on Linux with GWIA and WebAccess).

What if... we create a new GW8 domain on Linux and a new post office,
move each mailbox to the new post office, then promote the new domain to
be primary, then upgrade it to GW12? About 120 users, mailboxes are
'relatively' small due to quotas and auto-archiving. We know we'd lose
single instance storage of attachments with this approach.

Documentation claims that "When you move a user’s account from one
GroupWise 6.x or later post office to another, all items are moved
correctly and all associations (proxy rights, shared folder access, and
so forth) are resolved so that the move is transparent to the user."
That sounds encouraging.

But it further states: "A user who owns a resource cannot be moved.
If the user owns a resource, reassign ownership of the resource to
another user who is on the same post office as the resource." -- so
then presumably resources cannot be moved at all and will need to be
recreated in the new post office ?

What about FIDs and access to existing archives, is that preserved with
a mailbox move to another post office?

Thanks for your comments and suggestions...

ngw mailing list
ngw at ngwlist.com

More information about the ngw mailing list