| The following numbered list is an exhaustive task list for moving a user. If you are moving several users, most steps in the list can be done simultaneously for all users. Tip Do not proceed from one item to the next unless you have achieved success with the current task!
Here are some terms to keep in mind as you review the task list: Destination domain: The domain that owns the post office the user is being moved to. Destination PO: The post office that the user is being moved to. Source PO: The post office that the user is currently a member of. USERA: The user being moved.
Tip The following is a tip from Richard Griffith, who has several years of experience with GroupWise. "We have over 400 post offices in the company. "Each small office has a post office due to bandwidth issues. I have noticed the default thread setting on the POA is too small, even though the post office may only have 12 users. The POA's default Max Thread Usage for Priming and Moves at 20% causes a problem. Twenty percent of 6 is 1.2. If the POA is doing anything with a TCP handler thread, the move will error. If I increase the threads to 12, user moves seem to happen more reliably. If I don't increase the thread, the log will display the following over and over: 18:19:09 24E (trACKMOVE) (Move.) Queue Live Deferred Retry Message (no thread available): rgriffith (a1c). "The move may not take place for days and the user move status never clears, even though the move finishes sometime later." So the recommendation here is based on Richard's observations. Increase the Max Thread Usage for Priming and Moves to 50% for post offices that have a small number (under 10) of TCP Handler Threads configured.
Following are the minimum recommended steps for moving a user: 1. | In ConsoleOne, connect to the destination domain.
To do this, select Tools, GroupWise System Operations, Select Domain. Browse to the UNC path for the destination domain and select the WPDOMAIN.DB file.
Tip Throughout the remainder of this list of steps, always stay connected to the destination domain. | 2. | Check and clean USERA's message store with Mailbox/Library Maintenance routines.
Note Avoid using the stand-alone GWCheck (GWCHECK.EXE). It is slower compared to the POA routines spawned from Mailbox/Library Maintenance. Highlight USERA and select Tools, GroupWise Utilities, Mailbox/Library Maintenance. Then select the Structural Rebuild option, make sure that only the User check box is checked under the Databases tab, and then click Run.
Issue an Analyze/Fix Databases command on the contents of USERA's user database (don't bother with the message database). You can issue this Mailbox/Library Maintenance job immediately after issuing the structural rebuild.
Confirm that both of these maintenance routines happened, and that there are no major problems with USERA's message store. Make sureif you are not set up as the GroupWise domain's administrator in ConsoleOnethat you CC yourself via the CC option on the Results tab.
| 3. | Make sure that USERA's object will synchronize to the source and destination POs.
Temporarily change USERA's phone number.
Log in as a test user on the destination PO and confirm that USERA's phone number changed, and that the user shows up as a member of the source PO.
Log in as a test user on the source PO. Confirm that USERA's phone number changed, and that the user shows up as a member of the source PO.
Change USERA's phone number back.
Tip When you're moving a large number of users in a short period, it won't be practicable to take this step. Try to synchronize all the users, though. When moving multiple users, simply highlight the users to be moved by Shift-clicking or Ctrl-clicking, and then select Tools, GroupWise Utilities, Synchronize. Tip If you are going to move USERA to another eDirectory OU, go to step 4. If not, skip to step 5. | 4. | Disassociate USERA's eDirectory object from the user's GroupWise object.
Highlight USERA. Select Tools, GroupWise Utilities, GW/eDirectory Association, Disassociate GroupWise Attributes. Move USERA to her new eDirectory OU.
| 5. | View the details on USERA and make note of the FID.
Highlight USERA and edit the properties. Select the GroupWise Account property page to take note of the file ID.
| 6. | Move USERA.
Highlight USERA in the GroupWise view. Right-click the USERA object and select Move. Select the world icon in the GroupWise Move dialog box and browse to and select the destination post office. Follow the remaining prompts to allow the user to move.
| 7. | If you disassociated USERA's eDirectory object from USERA's GroupWise object, reassociate them.
Highlight USERA in the eDirectory view, not the GroupWise view. Edit USERA, and go to the GroupWise Account property page. Click the world icon to the right of the Post Office field. Select the post office that USERA is now a member of. When you click OK as though you want to finish the operation on USERA, a message should come up that asks whether you want to associate USERA's eDirectory object with its GroupWise object. Click the Yes button, if everything is correct.
| 8. | Assess the success of your move. Do so using the User Move Status utility explained in the next section. Be sure to use the Clear Status feature when you have determined that the user did move successfully.
|
When you have confirmed that USERA has moved successfully, be sure to reassociate the user's GroupWise object with her eDirectory object. Do this by highlighting USERA in the GroupWise view and selecting Tools, GroupWise Utilities, GW/eDirectory Association, Associate Objects. Then associate USERA's GroupWise object with her eDirectory object. |
