Merging Two GroupWise System That Exist In Two Trees

  • 3276926
  • 07-Nov-2007
  • 26-Apr-2012

Environment

Novell GroupWise 5.2
Novell GroupWise 5.5 Enhancement Pack (EP)
Novell GroupWise 5.5
Novell GroupWise 6
Novell GroupWise 6.5
Novell GroupWise 7

Situation

Merging Two GroupWise System That Exist In Two Trees

Resolution

Note: For the following situation Domain A resides in Tree A, and Domain B resides in Tree B. Domain A will become the Primary and Domain B will become the Secondary.
1. In order to merge correctly, both systems must have an external Domain representing the other Domain
  • To create external system, highlight the GroupWise system object in the GroupWise View
  • Right click and chose Create
  • Chose External Domain
  • Fill in all of the fields appropriately, the name must match the other domain exactly. So, Domain A will have an external domain named Domain B, and Domain B will have an external Domain named Domain
2. Bring a copy of the WPDOMAIN.DB for Domain B to Domain A's site

3. Put WPDOMAIN.DB for Domain B into a temp directory on the same server as Domain A

4. In NWADMIN connect to Domain B
  • Tools | GroupWise System Operations | System Connections (In ConsoleOne select Tools | GroupWise System Operations | Select Domain)
  • Specify Other Domain, Browse to the temp directory containing Domain B's WPDOMAIN.DB
  • Click "OK"
  • Click "Connect"
  • Click "Close"
    Note: You should now see Domain B's system in the GroupWise view
5. Graft Domain B into Tree A
  • Tools | GroupWise Utilities | Graft GroupWise Objects (NDS view must be highlighted in order to graft)
  • Chose "Domains, post offices, and gateways" Click "Next"
  • Click "Next" past the Overview
  • Select the Domain B (it will be the Primary domain if there is more than one), Click "Next"
  • Click "Yes" when it ask you if you are sure you want to graft the Domain B in Tree A
  • Change the context of Domain B to a temp context in Tree A Click "Next"
  • Change the context of Domain B's post offices to a temp context in Tree A Click "Next"
  • Click "Finish" at the Summary
  • Chose "No" on Graft More objects and Click "Done"
6. In NWADMIN Connect to Domain A
  • Tools | GroupWise System Operations | System Connections (In ConsoleOne select Tools | GroupWise System Operations | Select Domain)
  • Specify Other Domain, Browse to the directory containing Domain A's WPDOMAIN.DB
  • Click "OK"
  • Click "Connect"
  • Click "Close"
    Note: You should now see Domain A's system in the GroupWise view
7. Change the UNC path for Domain B (this will be the external domain object defined in system A)
  • Highlight Domain B, right click chose details
  • Change the UNC path to reflect the temp directory where the WPDOMAIN.DB for Domain B is located
  • Click "OK"
8. Merge Domain B into System A
  • Highlight Domain B Tools | GroupWise Utilities | System Maintenance
  • Merge External Domain should be marked, Click "Run"
  • This starts the Merge Wizard, Click "Next"
  • Check the path and make sure it is pointing to the temp directory for the Domain B (If you are doing just steps 8 and 10 do not do this step.)
  • Click "Next"
  • Choose whether or not to merge external systems, then click"Next"
  • Close the MTA, Click "Next" (there should not be any agents running against Domain A or Domain B)
  • Click "Merge"
  • Click "Done"
  • Click "Close" to exit System Maintenance. Domain B should show as a secondary in the GroupWise View
9. Graft Domain B Back into Tree B ( this is done back in Tree B)
  • Rename the original WPDOMAIN.DB back in the Domain B's location
  • Take the WPDOMAIN.DB of Domain B out of the temp directory in location A and move it back to its original location
  • Start NWADMIN/CnosoleOne
  • Tools | GroupWise Utilities | Graft GroupWise Objects (NDS view must be highlighted in order to graft)
  • Chose "Domains, post offices, and gateways" Click "Next"
  • Click "Next" past the Overview
  • Select Domain B, Click "Next"
  • Click "Yes" when it ask you if you are sure you want to graft the Domain B in Tree B
  • Change the context of Domain B to Its original context in Tree B Click "Next"
  • Change the context of Domain B's post offices to their original context in Tree B Click "Next"
  • Change Domain B UNC path back to its original location
  • Click "Finish" at the Summary
  • Chose "No" on Graft More objects and Click "Done"

    Note: Sometimes there are problems grafting Domain B back into Tree B since there are NDS objects already there for the domain and post office in that tree. If this occurs, you should manually delete the domain and post office objects from Tree B using a non-snapped-in version of NetWare Administrator (such as NETADMIN or ConsoleOne). You can then proceed with Step #9.
10. Check Link Configuration for both domains
  • Highlight the domain, right click chose "Link Configuration"
  • Check the link between the two domains to make sure they are correct
11. To cleanup the objects created in Tree A use a non-snapped-in version of an Administration utility such as NETADMIN/ConsoleOne.
12. A top down rebuild of the merged domain(s) and post office(s) is recommended after the merge has completed
.

Additional Information

Note: If you can login into both trees from one workstation, only do steps 8 (excluding D from step 8) and 10. The full procedure is only intended to provide a solution for those who can't login to both trees.

Formerly known as TID# 10009631

Feedback service temporarily unavailable. For content questions or problems, please contact Support.