This section describes the necessary steps to upgrade the code of the TME 10 Netfinity Server V4.0 from any prior modification level to the latest one. Only update from level 1 to 3 has been tested, and while updates from other level have not been verified, it is applicable.
You need 50MB of free space on preparation site. This includes also temporary space that can be freed after installation complete.
On preparation site the following steps have to be done:
24/02/97 16.32 23.040 NFSRSTOP.EXE 24/02/97 16.23 73.220 update.ins 18/02/97 13.38 176.902 _setup.lib 30/09/96 10.06 6.128 _SETUP.DLL 04/11/96 15.04 44.928 setup.exe 05/11/96 18.17 320.276 _INST32I.EX_ 06/02/97 18.27 30.720 SVUNINST.exe 21/02/97 11.21 27.704 POST.EX 21/02/97 11.19 27.692 PRE.EXE These file are in the UPDV403.ZIP file released with this document.
Following there are three examples, one for each profile.
GLOBAL NAME: NFS.NT.PRE.REF.4.0.3
DESCRIPTION: NetFinity Server CLient Windows NT
CHANGE FILE TYPE: GEN
COMPRESSION TYPE: LZW
POST-INSTALL: D:\tmp\pre.exe
DEFAULT TOKEN: NewDir=D:\tmp
OBJECT: SOURCE NAME: d:\tmp\pre.exe
TARGET NAME: d:\tme10\pre.exe
TYPE: FILE
ACTION: COPY
Sample profile.1
GLOBAL NAME: NFS.NT.REF.4.0.3
DESCRIPTION: NetFinity Server CLient Windows NT
POST-INSTALL: D:\tmp\setup.exe -s -fD:\tmp\update.ins -f1D:\tmp\setup.iss
DEFAULT TOKEN: NewDir=D:\tmp
OBJECT: SOURCE NAME: $(NewDir)\*.*
TARGET NAME: D:\tme10\*.*
TYPE: FILE
ACTION: COPY
Sample profile.2
GLOBAL NAME: NFS.NT.POST.REF.4.0.3
DESCRIPTION: NetFinity Server CLient Windows NT
CHANGE FILE TYPE: GEN
COMPRESSION TYPE: LZW
POST-INSTALL: D:\tmp\post.exe
DEFAULT TOKEN: NewDir=D:\temp
OBJECT: SOURCE NAME: d:\tmp\post.exe
TARGET NAME: d:\tme10\post.exe
TYPE: FILE
ACTION: COPY
Sample profile.3
To generate the response file run the command
The resulting setup.iss file can be used in a silent mode to make a clone installation on other machine. After you have prepared the profiles and the response files on the preparation site, check if the connection with the Software Distribution server is up. Run from any command prompt the command
Then build the catalogues, from the preparation site type:
nvdm bld profile.1
nvdm bld profile.2
nvdm bld profile.3
On the server check if the profiles have been catalogued
nvdm ls "global name"
Then run the installation: