For NetWare servers, the Server Migration Utility has an Auto-Detect feature that attempts to locate post offices and domains on the NetWare server. The Auto-Detect feature scans NCF files in the sys:\system folder and looks for load commands for the GroupWise agents (for example, gwpoa.nlm and gwmta.nlm). Each agent load command includes the post office folder or the domain folder as the setting for the /home switch. The Auto-Detect feature also identifies startup files for the POA (post_office.poa) and the MTA (domain.mta). If your NetWare server does not have GroupWise NCF files and agent startup files in sys:\system, then the Auto-Detect feature does not find any post offices, domains, or agents.
For Windows servers, the Auto-Detect feature is not available. You must manually specify the locations of post offices, domains, and agents. Post offices and domains could be located anywhere on the Windows server. By default, the Windows agents are installed to:
c:\Program Files\Novell\GroupWise Server\Agents
By default, post offices and domains are migrated to the /var/opt/novell/groupwise/mail folder. This is the typical location for mail folders on Linux. You might prefer a shorter path name (for example, /gwsystem). Be sure to include the post office folder or domain folder in the path (for example, /gwsystem/sales).
IMPORTANT:To minimize case sensitivity issues on Linux, ensure that domain and post office folder names consist of all lowercase letters in NetWare or Windows file systems and in ConsoleOne.
The Linux POA and MTA software is always installed to subfolders of /opt/novell/groupwise/agents. On Linux, you can choose whether or not you want the agents to run as the root user, as described in the following section of the GroupWise Installation Guide for your version of GroupWise:
GroupWise 2012: Running the Linux GroupWise Agents as a Non-root User
GroupWise 8: Running the Linux GroupWise Agents As a Non-root User
Running as a non-root user is strongly preferred for security reasons.
If you are migrating a post office:
|
GROUPWISE SERVER MIGRATION WORKSHEET |
|---|
|
Under Post Office Information, specify the folder where the post office database (wphost.db) is located, the full path to the POA startup file, the full path to where you want to migrate the post office (the post office folder), and whether you want the POA to run as root. If you have more than one POA for the post office, migrate the main one first. Additional POAs must be installed and configured manually. |
To find out what changes the Server Migration Utility makes to the POA startup file when it migrates it to Linux, see the following section of the GroupWise Administration Guide for your version of GroupWise:
GroupWise 2012: GroupWise Server Migration Utility
in Security Policies
GroupWise 8: GroupWise Server Migration Utility
in Security Policies
If you are migrating a domain, you also need to consider the MTA working folder (mslocal). By default, it is located under the domain folder, but it can be placed elsewhere by using the /work switch in the MTA startup file. The Server Migration Utility can copy the mslocal folder for you if it is under the domain folder, on the same NetWare volume, or on the same Windows server as the domain folder. In all cases, it is placed under the domain folder on the Linux server.
If the mslocal folder is located on a different NetWare volume or on a different server, the Server Migration Utility cannot copy it for you. You must manually copy it to the Linux server. For instructions, see Manually Migrating the MTA Working Folder. You can do this after you have migrated the domain.
If you are migrating a domain:
|
GROUPWISE SERVER MIGRATION WORKSHEET |
|---|
|
Under Domain Information, specify the folder where the domain database (wpdomain.db) is located, the full path to the MTA startup file, the full path to where you want to migrate the domain (the domain folder), the full path to the MTA working folder, and whether you want the MTA to run as root. |
To find out what changes the Server Migration Utility makes to the POA startup file when it migrates it to Linux, see the following section of the GroupWise Administration Guide for your version of GroupWise:
GroupWise 2012: GroupWise Server Migration Utility
in Security Policies
GroupWise 8: GroupWise Server Migration Utility
in Security Policies
The Internet Agent (GWIA) and the WebAccess Agent startup files must be identified manually if you want the settings in the startup files to be migrated.
NOTE:The WebAccess Agent is not part of GroupWise 2012 or GroupWise 2014, but is part of GroupWise 8.
The GWIA startup file is gwia.cfg. The default location of the startup file varies by platform:
|
NetWare: |
sys:\system\gwia.cfg |
|
Windows: |
\domain\wpgate\gwia\gwia.cfg |
|
GROUPWISE SERVER MIGRATION WORKSHEET |
|---|
|
Under Internet Agent Information, specify the full path to the GWIA startup file and whether you want the GWIA to run as root. |
To find out what changes the Server Migration Utility makes to the POA startup file when it migrates it to Linux, see the following section of the GroupWise Administration Guide for your version of GroupWise:
GroupWise 2012: GroupWise Server Migration Utility
in Security Policies
GroupWise 8: GroupWise Server Migration Utility
in Security Policies
The WebAccess Agent startup file is webacnna.waa The default location of the startup file varies by platform:
|
NetWare: |
|
|
Windows: |
|
NOTE:The WebAccess Agent is not part of GroupWise 2012 or GroupWise 2014, but is part of GroupWise 8.
|
GROUPWISE SERVER MIGRATION WORKSHEET |
|---|
|
Under WebAccess Agent Information, specify the full path to the WebAccess Agent startup file. The WebAccess Agent must run as root. |
The Server Migration Utility migrates the WebAccess Agent but not the WebAccess Application that is installed to your web server. If you want to use a Linux web server with WebAccess, you can follow the instructions in Manually Migrating the WebAccess and WebPublisher Applications to Linux after you have migrated the WebAccess Agent.
The post office that you want to migrate might own libraries with remote document storage areas. A remote document storage area is a storage area that resides outside of the post office folder structure, rather than within it. A remote document storage area might be on the same server with the post office, or it might be on a different server. The Server Migration Utility cannot migrate remote document storage areas for you.
The utility can list all of the remote document storage areas associated with a post office and can provide their current locations. You need to decide where you want the document storage areas to reside after the post office has been migrated.
If it is necessary to keep your documents in a location other than Linux, you should create a new post office just for document storage areas and transfer your current document storage areas to that new post office. This provides a faster, more reliable way of accessing your documents through GroupWise.
|
GROUPWISE SERVER MIGRATION WORKSHEET |
|---|
|
Under Post Office Information, specify the location where you want to move each remote document storage area for libraries in the post office. |
You must move the document storage areas before the second post office data migration starts. Instructions for manually copying the document data to the planned destinations are provided at the appropriate point in the migration process. Do not move the document storage areas until you are instructed to do so.