Grafting Merged Domain causes Multiple Primary Domains

After re-grafting newly merged Secondary Domain back into it's original eDirectory tree the Groupwise System shows 2 Primary Domains when connected to the Primary or the newly merged Secondary Domain.

This has been reported to Engineering.

If the original GroupWise Domain eDirectory object hasn't been deleted prior to re-grafting it may have an attribute "NGW: Type" that has a value of "2". This indicates that it's a Primary Domain. When a domain is merged into another GroupWise system it will be converted to a Secondary Domain however the eDirectory Object in the original eDirectory Tree isn't touched and therefore this attribute isn't modified at this time. If you need to keep management of this Domain in it's original eDirectory Tree then you will need to re-graft this Domain back into that tree. The ConsoleOne GroupWise Snap-Ins should change the value of NGW: Type to "1" (secondary) during the re-grafting. However, this is not happening and the GroupWise System is notified that this newly merged Secondary Domain is in fact a Primary. This then causes the GroupWise view in ConsoleOne, when connected to the real Primary or the new Secondary to show 2 Domains with a Red Bar indicating they are both a Primary Domain.

Workaround:
There are 2 workarounds for this issue.
1. Delete the existing/original Domain eDirectory Object only from the tree prior to re-grafting. (Please make sure you follow the Documented instructions for doing this! You will need to do this by removing the GroupWise Snap-Ins in ConsoleOne prior to performing the delete of the eDirectory Object!)
(TID:10084509 - How to Graft GroupWise Objects)

2. If unable or unwilling to use the first workaround then, prior to re-grafting, you will need to launch ConsoleOne without GW Snap-Ins, or use iManager, and Modify the NGW: Type attribute of the Groupwise Domain eDirectory Object. You will need to change it from "2" to "1".