Checkpoint SecureClient NGX R60
want to be able to distribute my pre-configured client package of Check Point VPN-1 SecuRemote/SecureClient NGX R60, using the MSI distribution through Microsoft SMS 2003.
The question is, how do I customize it? I've tried the R61 client packager; it provides the option to save the output file in MSI format. However, if I provide a source path with the unpacked R60 installation files it creates an executable file with the MSI-extension. If I provide a source path with the original MSI package and a userc.c file, it outputs a "real" MSI-file which is installable, but customizations does not get included and the client is not working.
I've also tried to create a transform in Wise Package studio on the original MSI, were I've tried to replace the original product.ini with an altered one with the settings I want. (I want to enable SDL in the customized package). However, the original MSI-distribution of SecureClient NGX R60 does not seem to be a standard MSI package, as I cannot replace or update any of the files in the package.
The question is, how do I customize it? I've tried the R61 client packager; it provides the option to save the output file in MSI format. However, if I provide a source path with the unpacked R60 installation files it creates an executable file with the MSI-extension. If I provide a source path with the original MSI package and a userc.c file, it outputs a "real" MSI-file which is installable, but customizations does not get included and the client is not working.
I've also tried to create a transform in Wise Package studio on the original MSI, were I've tried to replace the original product.ini with an altered one with the settings I want. (I want to enable SDL in the customized package). However, the original MSI-distribution of SecureClient NGX R60 does not seem to be a standard MSI package, as I cannot replace or update any of the files in the package.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
beekey
17 years ago
I found the solution in the CheckPoint_R62_VPN_Guide myself.
The cpmsi_tool lets you update files in the MSI-package.
The cpmsi_tool lets you update files in the MSI-package.
Posted by:
NZmsi
16 years ago
I also tried to update a file (userc.c) in the Checkpoint SecureClient install using a transform. Looking at the resulting log the file installed OK, but then a custom action in the Vendor MSI overwrote it.
As noted by beekey Checkpoint provides a tool called cpmsi_tool.exe that lets you extract and/or update certain files in the vendor MSI (obviously you should make a backup before you begin)
SC/SR configurable files list:
------------------------------
product.ini
product.ini.simp
userc.c
userc.set
reg.ini
SecuRemoteAuthenticate.wav
SecuRemoteConnected.wav
SecuRemoteDisconnected.wav
SecuRemoteFailed.wav
logo.bmp
logging.bat
install_boot_policy.bat
collect.bat
scvins.bat
scvuins.bat
msfw.bat
harden.bat
1031.mst
1033.mst
1034.mst
1036.mst
1040.mst
The tool is installed as an option within SmartConsole from the CheckPoint NGX CD.
I used the tool from the R65 CD although the client package was R60 HFA2.
Couldn't find a download source, had to locate a CD...
As noted by beekey Checkpoint provides a tool called cpmsi_tool.exe that lets you extract and/or update certain files in the vendor MSI (obviously you should make a backup before you begin)
SC/SR configurable files list:
------------------------------
product.ini
product.ini.simp
userc.c
userc.set
reg.ini
SecuRemoteAuthenticate.wav
SecuRemoteConnected.wav
SecuRemoteDisconnected.wav
SecuRemoteFailed.wav
logo.bmp
logging.bat
install_boot_policy.bat
collect.bat
scvins.bat
scvuins.bat
msfw.bat
harden.bat
1031.mst
1033.mst
1034.mst
1036.mst
1040.mst
The tool is installed as an option within SmartConsole from the CheckPoint NGX CD.
I used the tool from the R65 CD although the client package was R60 HFA2.
Couldn't find a download source, had to locate a CD...
Posted by:
anonymous_9363
16 years ago
ORIGINAL: NZmsiMoving the CA in the transform to a position after the InstallFiles action (or after the vendor's CA which copied the file in question) would overcome that.
I also tried to update a file (userc.c) in the Checkpoint SecureClient install using a transform. Looking at the resulting log the file installed OK, but then a custom action in the Vendor MSI overwrote it.
I would *NEVER* update a vendor's MSI, even using their own tool. Use a transform.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.