I've come to find that our SandBlast Browser Extension causing IE to freeze for users. This specific issue started at the attempt to deploy users to Endpoint client version e80.88.
Typically, after start-up, (as we have our users restart their machines each evening before they leave), the issue will occur after they open IE for the first time. From my understanding, once they've force closed the program using Task Manager, the issue goes away until they come in the next morning.
This has caused me to stall my upgrades.
I have a ticket open with Check Point already, but kind of have run into a dead end. Most of what I've figured out is from me bumbling around on a computer toggling various configurations.
The conclusion that I've come to is-
- This, obviously, does not happen when SandBlast is disabled.
- This does not happen with environments outside of our domain.
- This does not happen when our start-up scripts are disabled.
- This does not happen when Silverlight is disabled.
- It *does* happen regardless of whether or not compatibility mode is toggled.
- It does not happen in Firefox or Chrome. (But we *need* IE for certain web applications.)
So, the common denominators, outside of SandBlast itself, seem to be our start-up scripts and Silverlight. These items are controlled by GPO. With that in mind, would implementing SandBlast in IE serve as a fix. AND, if so, *where* exactly would I need to make the modifications?
I've read sk108695 and it has more detail in regards to how to manage Firefox and Chrome. (Example: What registry path is needed, etc.)
I'm not a GPO admin, but I would likely have to tell our admins how to deploy this properly.