To install NGM207 and thereby upgrade from v2.0b/v2.0c to v2.0d
Use this upgrade to modify an existing NetWare Global MHS installation.
Before you install this upgrade, you must have installed either NetWare Global MHS v2.0b or v2.0c.
NOTE: This patch is designed to upgrade NetWare Global MHS v2.0b or v.20c to v2.0d. If you have a version other than v2.0b or v2.0c, this upgrade will not work. To determine your current NGM version, type 'MODULES' at the server console prompt and verify that the version number for 'NGMADMIN.NLM' is v2.0b or v2.0c. If you have any other version, this patch program will NOT work.
WHICH FILES ARE UPGRADED?
-------------------
1. NGM.NLM 688333
2. NGMADMIN.NLM 373003
3. NGMAMP.NLM 197335
4. NGMDEINS.NLM 153848
5. NGMDSYNC.NLM 56071
6. NGMEXTRC.NLM 22653
7. NGMSMF.NLM 497838
8. NGMUPGDE.NLM 145256
9. BASTONGM.NLM 34794
10. NGMADMIN.HLP 197967
11. NGMBIMPT.NLM 16263
12. NGMBIND.NLM 20031
13. NGMNIMPT.NLM 20084
14. NGMTOOLS.NLM 47334
15. DIRADM.EXE 230469
16. README.20B 90174
17. README.20D 24149
18. README.40X 26318
This upgrade does not change the serial number and maximum number of licensed users for your NetWare Global MHS installation.
NOTE: If you are installing this patch over NetWare Global MHS v2.0c, the resulting 'RESULTS.TXT' file will indicate that 17 Btrieve related files do not exist in the NGM\BIN directory.
This is to be expected when upgrading from v2.0c to v2.0d.
UPGRADING YOUR SERVER
-------------------
1. Login to your NGM server as supervisor.
2. The contents of the GMHS 2.0d patch is as follows:
1. README.UPG
2. PATCH.EXE
3. PATCHNGM.BAT
4. NGM20D.RTP
3. Copy the files 'PATCH.EXE', 'PATCHNGM.BAT', and 'NGM20D.RTP' to the root NGM directory. The default NetWare Global MHS directory is
<drive:>\NGM\.
Sample: COPY PATCH.EXE <drive:>\NGM\*.*
COPY PATCHNGM.BAT <drive:>\NGM\*.*
COPY NGM20D.RTP <drive:>\NGM\*.*
If you installed NetWare Global MHS v2.0b/c in a different directory, be sure to copy the upgrade files to that directory.
For example, if NetWare Global MHS is installed in the directory
The patch program searches all subdirectories to find the appropriate files to upgrade. So, it is very important to start the upgrade procedure from the correct directory.
4. Unload NGM at the server console and make a backup copy of your
NetWare Global MHS Directory structure.
NOTE: Do not save backup files under the same directory structure
in which you installed NetWare Global MHS.
The upgrade procedure will update the first file within the
directory structure. If this first file happens to be a
backup file, then the correct system file will not be upgraded.
5. Verify that your server has at least 7 MB of free hard disk space.
This is the recommended minimum required to install this upgrade.
6. Change to the root NGM directory (where you copied the upgrade files). Verify that you do NOT have a \NGM\BACKUP directory which
contains previous NetWare Global MHS patch files. If this directory
exists prior to running the patch program, the appropriate backup
files may not be created. If this directory is not present,
enter:
PATCHNGM
The patch program upgrades all appropriate files. The patch program also retains a log of the results in a file called 'RESULTS.TXT'. To verify your upgrade installation, view the contents of 'RESULTS.TXT' after the upgrade is complete.
7. Verify your NetWare Global MHS files have been upgraded correctly by reviewing the file 'RESULTS.TXT', in the NGM directory, and by comparing the files, listed above in the section 'WHICH FILES ARE UPGRADED?', to the files in your NGM\BIN directory.
If your file sizes do not match those listed above, please
contact your Novell representative. Please be prepared to
give the exact steps you followed to perform the upgrade,
the size and date of the upgrade files, your NGM directory
structure and the contents of the 'RESULTS.TXT' file.
8. The patch process will also include the file DIRADM.EXE which resides in the MHS\EXE directory. The patch process will place this file in the NGM\DPATCH directory. For the upgrade procedure to be complete you must copy NGM\DPATCH\DIRADM.EXE to the MHS\EXE directory.
9. During the patch process a BACKUP directory is created under the directory from which you ran 'PATCHNGM'. The BACKUP directory contains all files that were changed and a file called 'UNPATCH.BAK'. If you want to undo your upgrade and return your installation to its previous state, perform the following procedure.
o To restore your system, change to the BACKUP directory,
copy 'UNPATCH.BAK' to 'UNPATCH.BAT', and type "UNPATCH".
This file will delete all new files in the appropriate
directories and replace them with the files which originally
existed.
o Verify the original files have been correctly re-installed
and delete the BACKUP directory before attempting to upgrade
the system for a second time.
1. Improvements in memory utilization
o NGMINS and NGMDEINS now initializes memory when
passing a memory block.
o NGMEXTRC no longer initializes a non existent handle.
o NGMUPGRADE no longer passes an absolute pointer to create
a screen.
o NGMADMIN now uses free() instead of FREE() when deallocating
memory.
o NGMADMIN no longer abends when deleting a gateway host.
o NGMSMF no longer abends when adding a new application.
2. Unreleased Resources
o When any module is loaded with the -s option, CreateScreen()
allocates memory . This memory was not released when
the module was unloaded. The modules DSYNC.NLM,
NGM.NLM, NGMEXTRC.NLM, NGMSMF.NLM were modified to use
DestroyScreen() to release the memory.
3. General Improvements
o CMP now verifies that update messages were originated by the
master host.
o Deleting a record now generates opcode (Delete) in an ASCII CMP message.
o Root workgroup ownership is changed to the new messaging server if that messaging server's name is the same as the root workgroup.
o Dlist can now be added on a gateway after a member unparticipates.
o Member now finishes participation and notifies Postmaster when it encounters a situation where incomplete information is received from the Hub.
o Naming or ownership conflicts no longer cause Directory Synchronization to hang.
o Personal information for users created via ASCII CMP is now propagated.
o Forced Reconciliation no longer corrupts the database.
o Errors encountered when opening a file no longer cause NGMSMF to abend.
o Unparticipation no longer results in workgroups being deleted from the server.
o The Directory Synchronization process now sends a message to the Postmaster when naming conflicts are encountered.
o Ownership of GMHS records is no longer shared between servers.
o The 'Redirect-to' parameter, in the FORWARD.SMF file, now works for a user on a passive messaging server.
o Message queue handling has been improved when errors are encountered.
o Statistics generation for Passive Servers has improved.
o The size of the Personal information field has been correctly calculated when using DIRADM.EXE.
o Incorrect time zone setting no longer generates illegal format of date header.
o Improvements in the processing of directory exchange messages from non-Global MHS participating servers.
Note: Line-folding issues with long extended addresses have not
been addressed in this release. These issues will be resolved
in a subsequent patch release.
4. Enhancements
o GMHS will log Non-Deliverable CMP messages to NGMDSYNC.LOG instead of sending them to the Postmaster if the following option is set to ON in NGM.CFG.
[NGMDSYNC]
Log-Non-Delivery-Notification=ON
o Default message fan-out directory has changed to '3 by 4'.
o Error messages generated by Directory Synchronization are improved.
o The NetWare full name is now used for the user's NGM name.
Note: New Parameter For Linking NetWare Full Name with NGM Name
By default, Global MHS uses the NetWare bindery Full name to create the user's NGM Name. This value is set in NGM.CFG.
[NGMBIMPT]
USE-NETWARE-FULL-NAME=TRUE
Novell recommends that you leave this parameter set to TRUE unless you have a specific reason for wanting the NetWare login name and NGM name to be the same. The following example shows the type of NGM name that Global MHS will create if you set this parameter to FALSE.
If the login name is JHSMITH and the fullname is JOHN HOLLISTER SMITH, Global MHS will create a NGM Name of JHSMITH.
o New NGMTOOLS "Supervisor Delete" Option
The "Supervisor Delete" option has been added to NGMTOOLS to enable
the administrator to delete records that otherwise could not be deleted.
To use this option, you must load NGMTOOLS with the following command:
NGMTOOLS -D
When you enter this command, the "Supervisor Delete" option appears as option #7 on the NGMTOOLS menu.
!!!WARNING!!!: The "Supervisor Delete" option in the NGMTOOLS utility
is very powerful. Use with extreme caution. Improper use of this option may cause irreparable damage to the Global MHS database. Never use this option to perform normal administrative duties.
EXAMPLE:
Assume that SERVER1 and SERVER2 participate in directory synchronization. If SERVER2 creates a record for the workgroup,
GROUP2.ROOT, directory synchronization will cause a record for
GROUP2.ROOT to be created on SERVER1. If SERVER2 is removed from the network before GROUP2.ROOT is deleted, the record for GROUP2.ROOT cannot be deleted because SERVER1 does not own the
workgroup. In this case, the administrator of SERVER1 could use the "Supervisor Delete" option to delete the record of that workgroup.
It is recommended that you use this option with extreme caution and ONLY when there is no other way to delete a record.
NOTE: If the "Supervisor Delete" option is used to remove a record, NO directory synchronization update message is sent to the other participating servers.
o Automatic Subscription
This feature automatically provides a contact messaging server with a subscription to any workgroups created during directory exchange with a participating non-Global MHS server. To enable this feature, you must add the following parameter to the [NGMDSYNC] section of the NGM.CFG file:
Enable-Dir-Gateway=TRUE
When set to TRUE, the contact messaging server will automatically subscribe to any workgroup created as a result of a directory exchange message from a non-Global MHS participating server. The contact server will then accept further information from the non-Global MHS participating server regarding the workgroup (including users and distribution lists in that workgroup).
By default, this parameter is set to FALSE. This means that the contact server will not accept any further information regarding the workgroup.
If the contact server's subscription to any workgroup created on a non-Global MHS participating server is deleted, the following warning message will be displayed:
!!!Caution!!!
If this server no longer subscribes to
this workgroup, directory synchronization
messages from Non-NGM servers, regarding
this workgroup will not be accepted.
<Press ESCAPE To Continue>
<Press CANCEL (F7) To Abort>
If you delete the subscription, the contact server will not accept subsequent directory-exchange messages from the non-Global MHS
participating server regarding the workgroup.
o Passive Server/Gateway configuration note.
When defining Passive Servers and/or Gateways in your system configuration, you must consider the following to ensure successful Directory Synchronization.
a. If you wish to define a workgroup on a Passive Server or a Gateway that will have the same name as that Passive Server/Gateway, you MUST first define the workgroup on the host and then when creating the Passive Server/Gateway have the Passive/Gateway subscribe to that workgroup. This will ensure that all information for these entries will be propagated to all participating servers.
EXAMPLE:
1. From the NGMAdmin Main Menu, select
'Workgroups, Users, and Dlists'.
2. Select 'Workgroups'.
3. Press <INSERT> to create the new workgroup on the host.
4. After the workgroup is created, select 'This Server' from the Main Menu.
5. Select either 'Passive Messaging Servers' or 'SMF Gateways'.
6. Press <INSERT> to add a new Passive Server or Gateway to the host.
7. Highlight the new Passive Server or Gateway and press <ENTER>.
8. Select 'Workgroups'.
9. To subscribe to the previously created workgroup, press <INSERT>, highlight the appropriate workgroup and press <ENTER>.
10. The system is now configured correctly to allow a Passive Server/Gateway and an associated workgroup to have the same name.
Novell, Inc. makes no representations or warranties with respect to this software patch, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose.
Novell's intentions for this software patch is to provide a temporary
work-around to the anomalies described in this file. Such
work-arounds are typically addressed in future releases of NetWare Global MHS.
Distribution of this patch is forbidden without the express written
consent of Novell, Inc. Novell reserves the right to discontinue distribution of this software patch.
Novell will not be responsible for any data loss that may result from
implementing this patch. Novell strongly recommends a backup be made
before any patch is applied. Technical support for this patch is provided at the discretion of Novell.
