Adding a second server and Post Office

Windows 2012r2, Gw2018.0.1

Can anyone direct me to documentation to add a 2nd GW2018 server to a domain?  Attempts so far -installing the server, then adding a PO ... The install finds the Domain, but only copies poa file,  wphostdb file, and the start cmd.  The installer completes successfully, but no addtional PO files are installed. 

Corrupt Domain DB ? 

 

 

  • Hi.

     

    You're not giving us much detail to work with. No details about where you install what exactly, no error messages. Also you don't add "servers" to groupwise. You add domains and post offices.

    I can only guess with the bit of info, but it seems you are adding a second post office on a different server than the one you already have? From your description, what else did you expect to happen? That's all that is needed (again, guesswork based on no detail), the rest will be created/copied when you start the po.

     

    MAy I also ask why you're running such outdated software? I wouldn't recommend to anyone today to still run GW18.0..

  • Thank you for the recommendation, we'll do that.    And Mobility too. 

    We are in a test system - on the 2nd Windows server, we choose to install a Post Office only?  There is no need for the Server software? 


  •  wrote:

    We are in a test system - on the 2nd Windows server, we choose to install a Post Office only?  There is no need for the Server software? 


    You need to read the GroupWise documentation.

    The post office is just a bunch of files. You need the same GroupWise software on the 2nd Windows server just like you have on your main GroupWise server to access them and manage them. 

    • You need to install the GroupWise software.
    • You need to create a new secondary domain.
    • You need to create a new post office.
    • The 2nd Windows server will have its own MTA and POA.
    • Your configuration will connect it to your main GroupWise server.

     

  • OK, thank you  - - in the past I had skipped the secondary domain reading, other than a quick look-see.  Time to bring it into focus.   We will update the software on the [primary] first, then add a second Win server and Groupwise domain. 

    But after a review of the documentation. 

     


  •  wrote:

    • You need to create a new secondary domain.

     


    Ahem, no? While a second domain may make sense, there is absolutely no need for it whatsoever.

  • OK ... I have it working.  The Domain Admin account (Windows) was having issues with the 2nd server NTFS file/folder rights.  Manually starting the poa from the folder displayed a number of [error] messages with a common theme relating to rw rights.  

    - Install GW server on 2nd Windows server

    - Install PO on 2nd server (with appropriate file system rights)

    Plan to add users, send emails between POs in the test system, and look ahead to the Production system Version updates.... and the associated Mobility upgrade.  Thank you all for the replies - it kept me in the game. 

  • While a second domain may make sense, there is absolutely no need for it whatsoever.

    there is one reason for having a second domain,  to have a live backup of the wpdomain.db in case something messes up the primary

     


  •  wrote:

    While a second domain may make sense, there is absolutely no need for it whatsoever.

    there is one reason for having a second domain,  to have a live backup of the wpdomain.db in case something messes up the primary

     


    I know, that's why I said it may make sense, but it's not a must.

  • Well, we decided a 2nd domain will be in 2020.  For now we added a 2nd Windows server with GW server installed, then added individual post offices.  Pretty direct stuff . . . but the agents did not load automatically and we ran "startAgent"  in the PO folder.  Then changed the PO service to use local admin to start. Finally, closed the running service and changed the login to a local service account.  Oh, and lastly we stopped and started GWIA and MTA on the primary Windows server. 

    Updates and upgrades to be next. 

     

    Thanks all for a great discussion - a learning process here. 

  • I know, that's why I said it may make sense, but it's not a must.

    Yes, I saw that.  just wanted to make sure the reminder of the only real reason for having a second one in such a situation.   It has saved my butt before where a client insisted that their file level backups worked just perfectly despite not having done anything about handling such normally locked files.  <sigh>