Server move

Hello,

last release running on windows 20xx, only primary domain on oes 11.
Two jobs in the pipeline:
a) IP change of windows server running secondary domain and po
b) Move this server to new hardware

Found TID 7013085:
- no applicable advice to pure ip change
Just change in agent settings on both sides (primary and local) in
admin console?

with regards
Gotthard Anger

--
Gotthard Anger
Anwenderbetreuung Netzwerkadministration
Landeskirchenamt der EKM
gotthardanger@no-mx.forums.novell.com
https://forums.novell.com/member.php/35038-gotthardanger

Mails an diese Adresse werden nur nach vorheriger Ansage gelesen!
Mails for this address will only be read if you trigger me before.

Tags:

  • Gotthard.

    Am 21.11.2017 um 08:01 schrieb Gotthard Anger:
    > Hello,
    >
    > last release running on windows 20xx, only primary domain on oes 11.
    > Two jobs in the pipeline:
    > a) IP change of windows server running secondary domain and po


    Change the IP(s) in Groupwise first POAs first, MTAs second, and wait
    until the chnage has replicated (noticeable when the agents become
    unreachable). Once done, change the IP on the OS "for real". Groupwise
    should become reachable again.

    If not, there's always the rebuild as last resort to get the proper IP
    into the remote databases.

    > b) Move this server to new hardware


    Hardware? Really? Haven't seen Windows Servers running on Hardware (vs
    VMs) in a long time. There are literally hundreds of possibilities, only
    very few involve works in groupwise itself. This sounds as if you want
    to transfer the whole OS?

    CU,
    --
    Massimo Rosen
    Micro Focus Knowledge Partner
    No emails please!
    http://www.cfc-it.de
  • Hello,

    JFTR ATM:
    1. start admin console on primary domain
    1.1. confirm remote poa and domain offline
    1.2. goto poa agent settings and change ip address to new address
    1.3. goto mta settings and change ip address to new address
    2. on remote server
    2.1 goto domain folder
    2.2 edit <domain-name>.mta
    activate /ip-parameter and insert new address
    2.3 restart MTA service
    2.4 goto po folder
    2.5 edit <po-name>.poa
    activate /ip-parameter and insert new address
    activate /mtpoutipaddr-parameter and insert address of mta agent
    2.6 restart POA service
    2.7 restart admin service
    3. open admin console on remote server
    3.1 change ip address of poa
    3.2 change ip address of mta
    4. open admin console on primary domain
    4.1 change ip address of poa
    4.2 change ip address of mta

    this workflow works for me

    Gotthard





    Am 21.11.2017 um 08:01 schrieb Gotthard Anger:
    > Hello,
    >
    > last release running on windows 20xx, only primary domain on oes 11.
    > Two jobs in the pipeline:
    > a) IP change of windows server running secondary domain and po
    > b) Move this server to new hardware
    >
    > Found TID 7013085:
    > - no applicable advice to pure ip change
    >     Just change in agent settings on both sides (primary and local) in
    > admin console?
    >
    > with regards
    > Gotthard Anger
    >
    >  --
    > Gotthard Anger
    > Anwenderbetreuung Netzwerkadministration
    > Landeskirchenamt der EKM
    > gotthardanger@no-mx.forums.novell.com
    > https://forums.novell.com/member.php/35038-gotthardanger
    >
    > Mails an diese Adresse werden nur nach vorheriger Ansage gelesen!
    > Mails for this address will only be read if you trigger me before.



    --
    Gotthard Anger
    Anwenderbetreuung Netzwerkadministration
    Landeskirchenamt der EKM
    gotthardanger@no-mx.forums.novell.com
    https://forums.novell.com/member.php/35038-gotthardanger

    Mails an diese Adresse werden nur nach vorheriger Ansage gelesen!
    Mails for this address will only be read if you trigger me before.
  • Am 21.11.2017 um 10:30 schrieb Gotthard Anger:
    > Hello,
    >
    > JFTR ATM:
    > 1. start admin console on primary domain
    > 1.1. confirm remote poa and domain offline


    Nonono! They must be *online*, not offline. No change to the system can
    ever reach the databases when the agents aren't running.

    > 1.2. goto poa agent settings and change ip address to new address
    > 1.3. goto mta settings and change ip address to new address
    > 2. on remote server
    > 2.1 goto domain folder
    > 2.2 edit <domain-name>.mta
    >     activate /ip-parameter and insert new address


    Not necessary whatsoever.

    > 2.3 restart MTA service
    > 2.4 goto po folder
    > 2.5 edit <po-name>.poa
    >     activate /ip-parameter and insert new address
    >     activate /mtpoutipaddr-parameter and insert address of mta agent


    See above.

    > 2.6 restart POA service
    > 2.7 restart admin service
    > 3. open admin console on remote server
    > 3.1     change ip address of poa
    > 3.2     change ip address of mta
    > 4. open admin console on primary domain
    > 4.1     change ip address of poa
    > 4.2     change ip address of mta
    >
    > this workflow works for me


    It's unnecessarily complicates, and you end up with a static config via
    POA/MTA files you can not chnage again from the admin console.

    CU,
    --
    Massimo Rosen
    Micro Focus Knowledge Partner
    No emails please!
    http://www.cfc-it.de