Disabling Secure Client on Boot

[BarryStiefel]

Disabling Secure Client on Boot



On Windows NT/2000/XP, disable the Check Point SecuRemote Service and the Check Point SecuRemote Watchdog services. You will need to manually start one of these services, which you can do from services or with the command: net start sr_service (Note these are with the NG version of SecuRemote, the service names may vary in earlier versions)

On Windows 9x, you can remove HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Run\fwenc.exe from the registry and reboot. You can also disable this by using the "msconfig" program present in Windows 98 or Win98SE. You can then use the link installed in the start menu to run SecuRemote when you need to.

Note that if you are using Secure Client with a Desktop Security Policy, even if you stop the service it does not disable policy downloaded from your policy server. The only way to disable this is to uncheck the Check Point items in your network or dialup adapters.

-- PhoneBoy - 10 Apr 2004

FAQForm FAQs.Class: SecureClientFAQs FAQs.OS: FAQs.Version:

[Tapper]

Looks like this message is about a year old. Has there been any changes in disabling Secure Client on boot or at least disabling the security policy on boot. We have just recently started using Secure Client in my company and having the policy always on is making my job difficult. Any advice would be helpful.

[Sergej]

There was some earlier discussions. Here is informative one Permanently disabling the policy in SecureClient

[RayPesek]

What issues are you seeing that cannot be resolved by the default policy?

We've got 300+ people on it and do not allow anyone to disable the policy and it works fine internally or externally.

Ray

[giulitn]

Hi all,
How do you use SR on the internal LAN?
Even if we disconnect the SR or we stop the services it doesn't permit to connect ot the internal ALN.
I've change the right parameters into the userc file but the only way is to disable security policy locally on the client.
Any help would be appreciated; whit Secure Client installed I can connect from anywhere but not from my internal LAN!!!!!
Thanks,
Bye

[mikem]

I do not use the all users group in my policy. I have identified a specific user group in my desktop policy. When the machine is not connected to the vpn the policy is not used so they can communicate freely when they are connected to the internal network.

Not sure if this helps but I did lock myself out a few times a couple of years ago.

Mie