CheckPoint Pointsec 6.2
Hi all
This is my first post here. I was wondering if anyone has had any experience deploying CheckPoint Pointsec for PC. I have set up the shares, service account and Admin PC and now looking at deploying it to other computers. The problem I have is that the Deployment guide says to use SMS and to run a silent install. The problem is we don't have SMS here.. we use CA DSM for our software delivery.
If I try to run a command like: msiexec /i "installpath.msi" /q .... nothing happens as part of the installation requires company details and serial number. The guide also says not to edit the .msi file so I'm not sure what to do.
If anyone has any recommendations, it will be greatly appreciated.
Thank you in advance
This is my first post here. I was wondering if anyone has had any experience deploying CheckPoint Pointsec for PC. I have set up the shares, service account and Admin PC and now looking at deploying it to other computers. The problem I have is that the Deployment guide says to use SMS and to run a silent install. The problem is we don't have SMS here.. we use CA DSM for our software delivery.
If I try to run a command like: msiexec /i "installpath.msi" /q .... nothing happens as part of the installation requires company details and serial number. The guide also says not to edit the .msi file so I'm not sure what to do.
If anyone has any recommendations, it will be greatly appreciated.
Thank you in advance
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
znake
14 years ago
Hi, inside a installed pointsec computer you need to create an silent install profile..
/znake
/znake
Posted by:
anonymous_9363
14 years ago
It's never a good idea to directly edit vendor-supplied MSIs. Changes can be applied via what's called a transform file (an MST). You can create transforms with a full-blown packaging tool (realistically, there are only 2 playes: Altiris (Wise) and Accresso (InstallShield) or with a bare-bones editing tool like Orca (part of the [free] Windows Installer SDK) or InstEdit
(also free, http://www.instedit.com). I would 8strongly* advise you, as a newcomer to packaging, against trying to use the bare-bones tools: there's a steep learning curve with Windows Installer package creation.
Once you have an MST, you then specify it on the command line, along with your other switch:
BTW, I think your test failed because you need to add a qualifier with the '/q' switch: on its own, it's meaningless and will probably trigger the "help" screen. You can see I've used '/qn' which means "Quiet, with no user interface".
(also free, http://www.instedit.com). I would 8strongly* advise you, as a newcomer to packaging, against trying to use the bare-bones tools: there's a steep learning curve with Windows Installer package creation.
Once you have an MST, you then specify it on the command line, along with your other switch:
msiexec /i "installpath.msi" TRANSFORMS="[path_to_and_name_of_transform.mst]" /qn /l*v %temp%\a_log_file_name.logBTW, I think your test failed because you need to add a qualifier with the '/q' switch: on its own, it's meaningless and will probably trigger the "help" screen. You can see I've used '/qn' which means "Quiet, with no user interface".
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.