| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| Hi All, After a license update, our Integrity client didn't launch automatically when we start our computer. Do you know how to launch our Integrity automatically when we reboot our computer? Thanks, eldo. |
| |||
| Which version of Integrity? If you haven't entered the correct key, this would cause a problem. In the registry check HKLM..........> Zone Labs>True Vector>fwstartup this should be set to 2. disabled is 0 |
| |||
| Hi Betski, Thank you for your reply. We haven't got this entry in the registry. Do we need to create this entry ? We run Check Point Integrity Server 6.0.659.0 and Check Point Integrity Agent version:6.0.182.000 Thanks, eldo37. Last edited by eldo37; 2007-04-25 at 08:44. |
| |||
| Hi Betski, I have a problem when I want to remove Integrity client. when I run iclient iclientSetup_IFen.exe /X /s /V" /qn INSTALLPASSWORD=<password>" message the file doesn't exist. Msiexec /X /qn <Product GUID> INSTALLPASSWORD=<password> Msiexec /X /qn <installDatabase.msi> INSTALLPASSWORD=<password> and msi files doesn't exist too. Any idea how to remove the Integrity client? thanks, eldo. |
| |||
| Sounds like your only option at this point would be to rip it out of the file system and the registry. Don't forget to backup your registry first, and I'd advise making a Windows system recovery disk(disc). |
| |||
There are a couple of other pieces of junk laying about, but that shouldn't bother you really. This goes for verion 6.5, other versions might be different. You probably want to consider upgrading to 6.5 or even 6.6. |
| |||
| We encountered the same problem. The trial version of the client ran out on two laptops. We installed the Checkpoint Licence key on both. We rebooted both and one starts up automatically the other does not. We have the FWSTARTUP set to 2 on both. Not sure why we have this problem ? We are running 6.5.063.135 Thanks Matt |
| |||
| Hi sorry to add a thread withing this thread but my issue seems to be fairly similar We are using integrity server 6.5 HFA05. and the clients are on 6.5 HFA03. We have created an enforcement rule so we can update the clients on 6.5 HFA5. But it is not working although the enforcement rule seems to work we tried to configure minimum version 6.5.063.122 in "rule condition", but when configuring to minimum 6.5.063.122, we do not get any message,so therefore no upgrade possible . Anyone got an idea ? any help is greatly appreciated |
| |||
| Based on your comment apparently the enforcement rule identifies clients that that are below build 122. I believe that HFA04 is build 135 and HFA05 is build 166. What version are you upgrading too? Also have you added the client package that you want upgraded to the server? |
![]() |
| Thread Tools | |
| Display Modes | |
| |