Groupwise 2012 > 2014 onto a NEW Tree

I have a dying server with GW 2012

In the past to move to new Server in a new Tree I've used the Graft method

Can I simply copy the GW files (PO
  • bhrt60 wrote:

    > How would you do it ?


    GroupWise 2014 doesn't need eDirectory.

    Normally, you would run gwcheck before copying the domain and post
    office just to verify the health of your system.

    If your destination server is Linux (SLES) and the source server is not
    a Linux system, you need to use the dbcopy/gwcheck "storelowercase"
    function to ensure the files and database contain only lower case
    characters.

    Once that is done, simply install GroupWise 2014 R2 SP2. When you begin
    your configuration, you want to select "upgrade". You need to do this
    even thought this is a new install on this server so that you will be
    given to option to change existing settings stored in the GroupWise
    database.

    --
    Kevin Boyle - Knowledge Partner
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below this post.
    Thank you.
  • Thanks Kevin

    I sort of thought that but just wanted to make sure :)

    It's a OES11SP1 Server with ~30 users - didn't want to
    (1) mess with flakey server
    (2) go through transfering eDir and all that
  • bhrt60 wrote:

    > It's a OES11SP1 Server with ~30 users - didn't want to
    > (1) mess with flakey server
    > (2) go through transfering eDir and all that


    Will you be retiring that OES11SP1 server?

    Is that OES11SP1 server the only one in its tree?

    Will the old tree disappear too?

    Do you need to migrate users, files, and trustees to the new server?

    --
    Kevin Boyle - Knowledge Partner
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below this post.
    Thank you.
  • laurabuckley wrote:

    > Just be aware that after the move
  • Hi Kevin,

    If the users are to be associated with a new tree you need to change the association from one tree to another. If you don't do this the LDAP GUID will still point to the old tree and the user objects will be unmanageable i.e. you won't be able to change the details of the user such as first name, last name, telephone number, etc as that information is managed through iManager.

    Cheers,
  • laurabuckley wrote:

    > If the users are to be associated with a new tree you need to change
    > the association from one tree to another.


    That makes sense...

    IIRC, once you begin the GroupWise configuration on the new server you
    get to specify the (new) eDirectory tree, do you not?

    Once GroupWise is pointed to the new tree, there is no reason to run
    disassociation tool, is there?

    --
    Kevin Boyle - Knowledge Partner
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below this post.
    Thank you.
  • Hi Kevin,

    Nope... when you run the installer it's upgrading the databases not reconfiguring your LDAP setup. The disassociation tool is if you want to remove the associations and have just GroupWise users with no LDAP association.

    Cheers,