Moving GroupWise in eDirectory

Wikis > Caledonia Private Wiki > Moving GroupWise > Moving GroupWise in eDirectory
In this section, we will discuss two different tasks:

Moving GroupWise systems to a new eDirectory tree
Moving GroupWise objects to a new location in an existing tree

This is a short chapter compared to some of the work we’ve gone through before, but it is important!

Moving GroupWise to a New eDirectory Tree

For some reason, this seems the “scariest” move in GroupWise, when in reality the “tree move” is probably the simplest. Perhaps this move seems so complicated because it involves so much work. For the most part, moving to a new tree involves all of the steps in moving to a different server, and maybe even those in moving to a different network operating system. However, the “new tree” move is really not the part of the process to be afraid of. It is typically the easiest.

Grafting Domains, Post Offices and Gateways

Once you have your objects located where you want them on your servers, it’s time to graft them into your new tree. The steps are really fairly simple.

NOTE: Make sure the schema is extended with the GroupWise Schema before you attempt to graft any GroupWise objects into it.

In ConsoleOne, go to the “eDirectory” view – i.e., not the “GroupWise” view at the bottom.
Highlight ANY eDirectory container in your new tree (although it saves some steps to highlight the container where you wish to place your domain/post office objects).
Under Tools|GroupWise Utilities|GW/eDirectory Association, choose Graft GroupWise Objects.
In most cases, you will receive a notice about DirXML. If you are using Identity Manager, follow the instructions on this screen. Then click OK.
Choose to graft GroupWise Domains, Post Offices and Gateways.
Choose the domain that you wish to Graft.
You will receive a message that the domain already belongs in your old tree, do you still wish to graft. Indicate yes.
If you are not attached to the former tree a login box will pop up. If you do not have access to this tree, just cancel. While you will receive an error, you will be able to continue the graft. If you are able to connect to the former tree, however, the objects will be updated and removed from that tree as well.
Verify the context where this domain should be placed. Click next.
If there are post offices in this domain, you will be presented with a “default” suggestion for the location in the tree for these objects. Verify this or change the location. Click next.
At the summary screen, double-check all of the information for accuracy and then click finish. The objects will be grafted into the new tree. You will be presented with a screen asking if you wish to graft more objects. If there are users associated with this domain, you should indicate yes and proceed to grafting your users.

Grafting Users, Resources, Distribution Lists and Libraries

If you have continued from the step above, continue with Step 5 below. Otherwise do the following:

In ConsoleOne, go to the “eDirectory” view – i.e., not the “GroupWise” view at the bottom.
Highlight ANY eDirectory container in your new tree (although it saves some steps to highlight the container where most of your users for this post office reside).
Under Tools|GroupWise Utilities|GW/eDirectory Association, choose Graft GroupWise Objects.
In most cases, you will receive a notice about DirXML. If you are using Identity Manager, follow the instructions on this screen. Then click OK.
Choose to graft users, resources, distribution lists and libraries.
Choose which post office(s) you wish to graft your objects for. You can select more than one post office by holding down the Control Key and clicking on each post office. If you are unfamiliar with grafting, it is best to start with one post office only.
Click Next.
For most sites, mapping “Additional User Fields” is unnecessary (we’ve never used it). Choose No and click Next.
A context for your resources comes next. Most sites put resources in the same container as the post office.
Distribution Lists are also often in the same tree as either the post office or users. Choose your container.
It is almost always recommended that you leave the libraries in the same container as your post office. Make your selection.
When all of the fields for resources, distribution lists and libraries are to your liking, click next.
Typically at the match users screen you want to choose your top-most container and allow the grafting to search for users. However, if your users are all in a sub-branch of the tree, or even in a particular OU, choose that instead to speed things up.
At the matched and unmatched users screen, choose whether you wish to ignore the unmatched users, add them to a text file, or to create them as external GroupWise entities. If you need to create eDirectory users for these email accounts, save them to a text file. If these users need no eDirectory login, choose to create them as external entities. If you choose to save to a text file, after you finish the graft, create the users that are listed in the text file and run the grafting process for your users again.
External entities will need a context – choose where to place these objects and click next.
Verify that your matched users look correct, and then click Next.
If all looks okay in the summary screen, click Finish.

Your objects should now be grafted to the new tree, and your “move” of your GroupWise system will be finished. By nature of the graft you now have the Domain, MTA, Post office and POA objects in your tree and the GroupWise databases are aware of what tree and context they are located in.

Moving GroupWise Objects to a Different Container in the Current Tree

There are some unique tricks to moving GroupWise objects such as Domains, Post Offices and External Entities to new locations in an eDirectory tree. Generally, simply trying to “move” them through ConsoleOne normally will result in problems in the GroupWise objects. Our steps here are:

Delete the GroupWise object with a tool that does not recognize GroupWise, and thus does not send a “delete” signal to the GroupWise Agents.
Graft the deleted object back into the tree using the steps outlined in the section above.

When we say that we use a tool that does not recognize GroupWise objects, that could be iManager or even ConsoleOne installed without GroupWise snapins. Back in the “old days” we used to use NetAdmin (really) to delete GroupWise objects that we wished to move. The important thing is that whatever tool you use cannot affect your GroupWise system in any way, and is only acting on eDirectory. iManager is a good choice, because you know it is safe. If you use ConsoleOne, the GroupWise objects that are deleted should have question marks next to them, indicating that the snapins are not installed.

Simply delete the object that you wish to move in the tree. Then go back through the grafting procedure outlined in the section above.

If you are nervous about the process (and it can be nerve-wracking), use a test object for your deletion until you are confident that you have the process down to a fine art. Then “move” away in eDirectory!