• State Not Answered
  • Replies replies
    11
  • Subscribers subscribers
    15
  • Views views
    448
  • Users 0 members are here
  • Locked Locked
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Recommneded Upgrade from GW2014/SLES 11 to GW2018/SLES 12

bkesting
I currently have a Groupwise 2014 R2 system on a SLES 11 SP4 virtual machine. I have Mobility on a separate SLES 11 SP4 virtual machine. I'm planning to upgrade to GW 2018 and SLES 12. What's the preferred way to do this?

1) Upgrade inside existing VM?

2) Build brand new SLES 12 VM and then copy over postoffice and domain data and build GW2018 from scratch?
Parents Reply Children
  • 0 in reply to bkesting
    In article <bkesting.8fgy7b@no-mx.forums.microfocus.com>, Bkesting
    wrote:
    > What's the best way to upgrade Mobility?

    Thats easy, especially if you have a purchased cert. Build the new box
    with the newest versions. Set it all up so that it can do its sync of
    the users. Once that is all happy, move the cert over from your
    previous box and flip the DNS/NAT to the new box. Then the users
    devices will connect to the new box as if nothing has changed and away
    they go.

    If you don't have a purchased cert, this is a good time to play with
    LetsEncrypt to escape any of those issues that really want a public
    root CA tied cert. I've used this as part of migrations to SLES12 very
    successfully.


    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!

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0 in reply to Andy Konecny
    So in conclusion as I'm about to do a test GW 2018 install..............I can just install the GW 2018 software on my test SLES 12 box, don't "configure it" just yet, copy over postoffice/domains from old system, and then upgrade those using the GW2018 installation tool?
  • 0 in reply to bkesting
    bkesting wrote:

    >
    > So in conclusion as I'm about to do a test GW 2018
    > install..............I can just install the GW 2018 software on my
    > test SLES 12 box, don't "configure it" just yet, copy over
    > postoffice/domains from old system, and then upgrade those using the
    > GW2018 installation tool?

    More or less...

    You have the general idea but your domain and post office contain
    configuration information that refers to your existing (live?)
    GroupWise system. You want to make sure GroupWise 2018 doesn't try to
    use that information to interact with your GroupWise 2014 system.

    The best way to do that is to make sure your SLES 12 box can't talk to
    your SLES 11 box by either shutting down your SLES 11 box or by
    disconnecting your SLES 12 box from the network.

    --
    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.

    __________
    Kevin Boyle,     Knowledge Partner
    Calgary, Alberta, Canada

  • 0 in reply to Kevin Boyle
    KBOYLE;2479988 wrote:
    bkesting wrote:

    >
    > So in conclusion as I'm about to do a test GW 2018
    > install..............I can just install the GW 2018 software on my
    > test SLES 12 box, don't "configure it" just yet, copy over
    > postoffice/domains from old system, and then upgrade those using the
    > GW2018 installation tool?

    More or less...

    You have the general idea but your domain and post office contain
    configuration information that refers to your existing (live?)
    GroupWise system. You want to make sure GroupWise 2018 doesn't try to
    use that information to interact with your GroupWise 2014 system.

    The best way to do that is to make sure your SLES 12 box can't talk to
    your SLES 11 box by either shutting down your SLES 11 box or by
    disconnecting your SLES 12 box from the network.

    --
    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.


    Right.....I have my test box on an isolated network.

    Thanks!

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.