Moving a GroupWise 5.5 Post Office

  • 2939365
  • 19-Jun-1998
  • 28-Oct-1999
  • 13

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.

Symptoms

AUDIENCE: GroupWise 5 Administrators moving a post office to a different File Server or UNC path.

NOTE: If your GroupWise Post Office contains a document library be aware that this document does not take into account document libraries.

MAJOR SECTIONS OF THIS DOCUMENT

(1.) Concepts section
(2.) Action items section
(3.) Further considerations
(4.) Potential problems
(5.) Moving a GroupWise 5.2 Post Office

Solutions

This document focuses on GroupWise 5.5, however the concepts largely apply to GroupWise 5.2 Post Offices and GroupWise 4.1 Post Offices. This document was first written for GroupWise 5.2, so if you want a document that takes into account some complexities that can enter in with GroupWise 5.2 go to the second half of this document.

(1.) CONCEPTS SECTION

[A Post Office is a Container]

A GroupWise Post Office can be treated as a container, in the sense that a post office can be moved around, as long as the whole post office directory structure is moved with the post office. The root directory of a post office is the directory that contains the WPHOST.DB file.

[Changing Connectivity to a Post Office]

Once a post office has been moved to a different location, such as a different server, the entities that connect to that post office directly must be identified and edited to reflect the new change. These are the entities that are affected by a Post Office moving:

1. GroupWise Clients
2. The GroupWise POA that services this post office
3. The GroupWise Domain MTA for the domain where the post office resides.
4. GroupWise WebAccess
5. GroupWise Internet Agent

(2.) ACTION ITEMS SECTION

-CLOSING THE POST OFFICE-

1. Get all users out of the post office that is to be moved. Generally this is as easy as bringing downt the POA. However if users have direct connections to a post office it's kind of hard to kick those users out. If users have the capacity to be connected directly to a post office vs. Client/Server access, you can monitor who is still in GroupWise by seeing who is connected to the WPHOST.DB file.

2. From the Domain MTA that services this post office, suspend connectivity to the post office. From a GroupWise 5.5 MTA at the NetWare Server Console you would do the following:

a. Press the F10 key
b. Select Configuration Status
c. Highlight the post office to be moved
d. Press enter on the post office and select the "Suspend" option

3. Bring down the POA or POAs that service the post office to be moved.

4. Rename the WPHOST.DB file in the post office directory to WPHOSTDB.bak. Do not proceed until you have successfully renamed this file.

5. Create an ASCII file in the post office called WPHOST.DB.

-MOVE THE POST OFFICE-

1. NCOPY or XCOPY can be used to move the file system. Make sure you include the appropriate switches to copy subdirectories as well as empty directories. I.E. xcopy /s/e

2. GWBACKUP could also be used. GWBACKUP is specially designed to backup a GroupWise post office. This utility can be found at the following location on the Internet:

TID # 2929217

(GW 5.x Backup Utilities)

Now that you've moved the post office proceed to the next section.

-THINGS TO DO IN NETWARE ADMINISTRATOR-

NOTE: Be sure to be connected to the domain that owns the post office that was just moved when you make the changes explained in this section. To be connected to a particular domain, go to the GroupWise view, highlight the domain you want to be connected to press the right mouse button and select "Connect".

1. GroupWise Post Office Object in NetWare Administrator

(a.) Edit the Post Office object and change the UNC path to the post office. The software distribution directory may need to be changed if the software distribution directory is not at the best location for the users of this newly moved post office. Make sure users have Read and File Scan rights to the Software distribution directory if necessary. If the GroupWise client is distributed to users via NAL or Zenworks then you don't need to worry about the Software Distribution Directory location, although every post office needs a Software Distribution Directory associated with.

2. GroupWise POA Object in NetWare Administrator

(a.) Edit the POA Object(s) associated with the moved post office, and change the Network Address to indicate the IP address of the server where the POA is running for this newly moved post office.

3. Check network links to see to it that the Domain that owns this post office has the correct connectivity to this post office. To do this:

a. Select Tools|GroupWise Utilities|Link Configuration
b. In the Link Configuration Utility select View|Post Office Links
c. Edit the link for the newly moved post office and make sure the link indicates the correct information

4. Now rebuild the WPHOST.DB file for this post office.

a. Highlight the post office
b. Select Tools|GroupWise Utilities|System Maintenance
c. Select Rebuild Database and then select the "Run" button

-OPEN THE POST OFFICE-

1. Load the GroupWise POA(s) servicing the post office

2. On the MTA that services the domain this post office is in, confirm that the MTA has connectivity to this post office. You may need to restart the MTA by selecting the F6 key on the MTA at the NetWare Server Console.

(3.) FURTHER CONSIDERATIONS

1. GroupWise Clients

(a.) If users use Client/Server with their GroupWise client, consideration of how the new users are going to discover the new address of their POA must be taken into account. There are two TIDs that discuss this issue. These TIDs can be found on the Internet at the following locations:

TID # 2937122
(Helping Users Find a Moved GW5.2 Post Office)

TID # 2923844
(GroupWise Login Algorithim)

(b.) If users use a mapped drive to access the GroupWise post office, the login script for those users must be adjusted to account for the new location. It is recommended to use the same drive letter so that startup switches and environment variable do not need to be adjusted. Also, make sure your users have the correct file rights in the post office directories. For more information on file rights, use the Help files in NetWare Administrator. To get GroupWise help, go to the GroupWise view, highlight any object, and hit the F1 key. Then do a search for -- Rights|Post Office Directory|Grant Post Office Directory Rights -- .

(c.) If users are using the 16-bit GroupWise client, see if the SH_SH_.ENV file (shared code environment file) has any UNC references, and make the appropriate modifications.

2. GroupWise WebAccess

(a.) Edit the links to the post offices. Make sure that the links reflect the new UNC or TCP/IP links to the post office.

(b.) If the GroupWise WebAccess agent uses UNC connectivity to the moved post office, make sure that the /USER-USERID user has the correct file rights to the post office. The WebAccess agent will need Read Write Create Modify Erase File Scan rights to the post office.

3. GroupWise Internet Agent

NOTE: These steps only apply if your GroupWise Internet Agent (GWIA) is a POP3 and IMAP4 server. If the GWIA is only an SMTP server then the GWIA probably does not have links to your post offices.

(a.) Edit the links to the post offices. Make sure that the links reflect the new UNC or TCP/IP links to the post office.

(b.) If the GroupWise Internet Access agent uses UNC connectivity to the moved post office, make sure that the /USER-USERID user has the correct file rights to the post office. The GWIA will need Read Write Create Modify Erase File Scan rights to the post office.

4. NGWNameserver

If the POA for the post office that was moved is defined as NGWNameserver in the DNS, make sure to change IP address for the NGWNameserver host.

5. GroupWise Remote

If the POA's IP address has changed then you will want to notify remote users that use a TCP/IP connection to retrieve their remote e-mail.

6. The GroupWise Agents

If this file server does not contain the latest GroupWise agents do the following. Install the GroupWise agents from your fully patched software distribution directory\agents directory. Run the INSTALL.EXE program to do this.

(4.) POTENTIAL PROBLEMS

1. Agents With Conflicting TCP/IP ports

If you are moving a post office to a server that already has GroupWise agents loaded, make sure to see to it that the new agents don't conflict with the ports of the already existing agents.

MOVING A GROUPWISE 5.2 POST OFFICE

CONCEPTS:

- WHAT TO BRING DOWN BEFORE THE MOVE
- PHYSCIALLY MOVING THE POST OFFICE
- WHAT CHANGES TO MAKE
- WHAT TO BRING UP . . . WHEN
- POTENTIAL PROBLEMS

This Technical Information Document was written with GroupWise 5 terminology in mind, however the concepts generally apply to GroupWise 4 also.

CONCEPTS

[A Post Office is a Container]

A GroupWise Post Office can be treated as a container, in the sense that a post office can be move around, as long as the whole post office directory structure is moved with the post office. The root directory of a post office is the directory that contains the WPHOST.DB file.

[Changing Connectivity to a Post Office]

Once a post office has been moved to a different location, such as a different server, the entities that connect to that post office directly must be identified and edited to reflect the new change. These are the entities that are affected by a Post Office moving:

1. GroupWise Clients
2. The GroupWise POA that services this post office
3. The GroupWise Post Office based MTA that services this post office (If one exists)
4. The GroupWise Post Office based ADA that services this post office (If one exists)
5. The GroupWise Domain MTA for the domain where the post office resides.
6. The GroupWise Domain ADA for the domain where the post office resides.
7. GroupWise WebAccess
8. GroupWise Internet Agent

WHAT TO BRING DOWN BEFORE THE MOVE

1. Get all users out of the post office that is being moved.

2. Bring down the Domain MTA

3. Bring down the Domain ADA

4. Bring down the Post Office based ADA (if one exists)

5. Bring down the Post Office base MTA (if one exists)

6. Cut off GroupWise WebAccess connectivity to the post office

7. Cut off GroupWise Internet Agent connectivity to the post office

8. Bring down the POA for this post office

PHYSICALLY MOVING THE POST OFFICE

1. NCOPY or XCOPY can be used to move the file system. Make sure you include the appropriate switches to copy subdirectories as well as empty directories. I.E. xcopy /s/e

2. GWBACKUP could also be used. GWBACKUP is specially designed to backup a GroupWise post office. This utility can be found at the following location on the Internet:

(GW 5.x Backup Utilities)

WHAT CHANGES TO MAKE

1. GroupWise Post Office Object in NetWare Administrator

(a.) Edit the Post Office object and change the UNC path to the post office. The software distribution directory may need to be changed if the software distribution directory is not at the best location for the users of this newly moved post office. Make sure users have Read and File Scan rights to the Software distribution directory.

2. GroupWise POA Object in NetWare Administrator

(a.) Edit the POA Object, and change the Network Address to indicate the IP address of the server where the POA is running.

3. GroupWise Clients

(a.) If users use Client/Server with their GroupWise client, consideration of how the new users are going to discover the new address of their POA must be taken into account. There are two TIDs that discuss this issue. These TIDs can be found on the Internet at the following locations:

TID # 2937122
(Helping Users Find a Moved GW5.2 Post Office)

TID # 2923844
(GroupWise Login Algorithim)

(b.) If users use a mapped drive to access the GroupWise post office, the login script for those users must be adjusted to account for the new location. It is recommended to use the same drive letter so that startup switches and environment variable do not need to be adjusted. Also, make sure your users have the correct file rights in the post office directories. For more information on file rights, use the Help files in NetWare Administrator. To get GroupWise help, go to the GroupWise view, highlight any object, and hit the F1 key. Then do a search for -- Rights|Post Office Directory|Grant Post Office Directory Rights -- .

(c.) If users are using the 16-bit GroupWise client, see if the SH_SH_.ENV file (shared code environment file) has any UNC references, and make the appropriate modifications.

4. GroupWise Post Office based MTA (If one exists)

NOTE: This is often called IP to the POST or a Post Office based MTA

(a.) Edit the Network Address for the Post Office based MTA to indicate the new IP address.

(b.) Make sure that the startup file for the Post Office based MTA indicates the correct path to the Post Office directory.

5. GroupWise Post Office based ADA (If one exists)

NOTE: This is often called a Post Office based ADA.

(a.) Edit the Network Address for the Post Office based ADA to indicate the new IP address. This is only required if SNMP is being used.

(b.) Make sure that the startup file for the Post Office based ADA indicates the correct path to the Post Office directory.

6. GroupWise Domain MTA

The Domain MTA that services the Post Office needs to know about the new UNC path or IP address to the post office. To ensure that this has been done, perform the following:

(a.) Edit the link from the domain to the post office. To do this, go to Tools|GroupWise Utilities|Link Configuration. Edit the link to indicate either the new UNC address or the IP address to a post office based MTA

(b.) If the GroupWise Domain MTA uses UNC connectivity to the moved post office, make sure that the /USER-USERID user has the correct file rights to the post office. The MTA will need Read Write Create Modify Erase File Scan rights to the post office. Do the same for the userid that the ADA uses if it's different from the userid the MTA uses.

7. GroupWise WebAccess

(a.) Edit the links to the post offices. Make sure that the links reflect the new UNC or TCP/IP links to the post office.

(b.) If the GroupWise WebAccess agent uses UNC connectivity to the moved post office, make sure that the /USER-USERID user has the correct file rights to the post office. The WebAccess agent will need Read Write Create Modify Erase File Scan rights to the post office.

8. GroupWise Internet Agent

NOTE: These steps only apply if your GroupWise Internet Agent (GWIA) is a POP3 and IMAP4 server. If the GWIA is only an SMTP server then the GWIA probably does not have links to your post offices.

(a.) Edit the links to the post offices. Make sure that the links reflect the new UNC or TCP/IP links to the post office.

(b.) If the GroupWise Internet Access agent uses UNC connectivity to the moved post office, make sure that the /USER-USERID user has the correct file rights to the post office. The GWIA will need Read Write Create Modify Erase File Scan rights to the post office.

9. NGWNameserver

If the POA for the post office that was moved is defined as NGWNameserver in the DNS, make sure to change IP address for the NGWNameserver host.

10. GroupWise Remote

If the POA's IP address has changed then you will want to notify remote users that use a TCP/IP connection to retrieve their remote e-mail.

11. The GroupWise Agents

If this file server does not contain the latest GroupWise agents do the following. Install the GroupWise agents from your fully patched software distribution directory\agents directory. Run the INSTALL.EXE program to do this.

WHAT TO BRING UP . . . . WHEN

1. Bring up the Domain MTA that services the domain for the moved post office.

2. Bring up the Domain ADA that services the domain for the moved post office.

3. Bring up the Post Office based ADA (if one exists)

4. Bring up the Post Office based MTA (if one exists)

5. Wait for about 5 minutes to process all the synchronization as well as other administration changes.

6. Bring up the POA.

7. Bring up the GWIA and WebAcess and make sure links to the post office are good.

POTENTIAL PROBLEMS

1. Information not getting to the WPHOST.DB file

If there is a post office based MTA and/or ADA, it's possible that some information will not spill down to the WPHOST.DB file. Without this information the POA and the post office based MTA may not function correctly. The only resolution to this is to rebuild the WPHOST.DB file. To do so from NetWare Administrator highlight the post office and select Tools|GroupWise Utilities|System Maintenance|Rebuild Database and then select the "Run" button.

There may be other problems with the WPHOST.DB file being out of synch, so just rebuild the WPHOST.DB file if the POA is giving you strange errors and not loading.

2. Agents With Conflicting TCP/IP ports

If you are moving a post office to a server that already has GroupWise agents loaded, make sure to see to it that the new agents don't conflict with the ports of the already existing agents.