Moving user to new Postoffice and Domain

I have a small Groupwise setup, with about 65 users split across two postoffices and two domains. All agents/domains/postoffices reside on the same system.

I need to move a user from one domain/postoffice to the other. Is there a best practice or what should I be aware of when I do this? In the Admin console, I see a "Move" option, does that move both the user to both a new PO and a new domain?

I am on version 14.2.2 running on SLES 11

Thanks!
  • Hi,

    The process for moving a user is found here: https://www.novell.com/documentation/groupwise2014r2/gw2014_guide_admin/data/adm_user_mgt_move.html

    The user is moved to the receiving Post Office which is owned by the domain. You move a user to the Post Office and the system does the rest.

    Please let us know how it goes.

    Cheers,
  • In article <bkesting.803gu0@no-mx.forums.microfocus.com>, Bkesting wrote:
    > I need to move a user from one domain/postoffice to the other. Is there
    > a best practice or what should I be aware of when I do this


    in addition to the docs Laura posted, there is a Cool Solution that
    outlines the process and some recommended setting tuning to do ahead of
    time.
    https://www.novell.com/communities/coolsolutions/user-move-within-
    groupwise/
    While it was written for previous versions of GroupWise, the fundamentals
    are still the same. If you don't adjust the settings, your move will
    only run at about 10000 objects (messages, calender entries, etc.) Per
    hour. So if the user in question has lots of messages and such, then you
    really need to tune or it will take many hours. I have a client go ahead
    and move one of the bigger (ab)users of the system and while there was
    plenty of band width to do it in a couple hours, it ended up taking
    nearly 20 hours (~175K messages, a contacts list that makes support
    choke. Yes Pam, that guy).

    Make sure both POs are healthy and happy. Check your regularly run
    Content GWChecks to make sure there aren't any issues hanging on that
    could trip things up. http://www.konecnyad.ca/andyk/gwlogs.htm


    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    http://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!

  • Thank you for the information guys. Appreciate it.

    One final thing. I have a Mobility Server setup as well........will I have to do anything with the user inside Mobility after the move?
  • In article <bkesting.805g4n@no-mx.forums.microfocus.com>, Bkesting
    wrote:
    > One final thing. I have a Mobility Server setup as well........will I
    > have to do anything with the user inside Mobility after the move?


    Most of the time GMS handles it just fine. Occasionally if it messes up
    you need to remove and flush the user from GMS and add them back in.

    Oh, and make sure that Indexing is running fully on the destination PO,
    perhaps even increase it so that the newly moved user's mail gets
    indexed quickly. On that one big move, we didn't check that. It was
    only doing a few thousand a day, so later in the week I needed to kick
    it to full, and for that troublesome user it still took better part of a
    day to do.


    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    http://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!

  • Hi,

    I have seen some issues with GMS not handling user moves too well. I would recommend that you remove the user from GMS before doing the move. When the move is 100% completed add the user back.

    Cheers,
  • laurabuckley;2459740 wrote:
    Hi,

    I have seen some issues with GMS not handling user moves too well. I would recommend that you remove the user from GMS before doing the move. When the move is 100% completed add the user back.

    Cheers,


    I will do that. Thanks again
  • Follow up question:

    Along with moving user to a new post office I also need to move them to a new OU within eDirectory. Which move should I perform first, or does it matter?
  • Hi,

    I would recommend moving the users in eDirectory first and then ensuring that the LDAP information is updated in GroupWise - the period of time required would depend on your LDAP sync interval, unless you manually synchronise. Once that is all happy move the users to the new post office.

    Cheers,
  • laurabuckley;2462289 wrote:
    Hi,

    I would recommend moving the users in eDirectory first and then ensuring that the LDAP information is updated in GroupWise - the period of time required would depend on your LDAP sync interval, unless you manually synchronise. Once that is all happy move the users to the new post office.

    Cheers,


    Got it.

    Thanks
  • So I moved the user and no errors reported. Also created a nickname during the move and I can email the user from external email to both his new and old addresses successfully.

    When I try to email internally, using the old address (nickname), the message goes thru to his Mailbox but I also receive a "Item was undeliverable.....user not on post office [D101]" error.

    Is this normal? I know after tonight all GW address books will be updated, but is this message safe to ignore? This error only seems to come on my mailbox......have tried it on several other accounts and I don't see it.