![]() ![]() My organization is currently about to update Forcepoint from version 12 to the latest version. This ensures the crowdstrike is installed first no matter what. Then when it's renamed correctly the rest comes down including Forcepoint. I had to damn well create a process where we name machines as "Spare" when imaging so that fall outside the relevant collection for all machines and don't install any software other than crowdstrike. ![]() Who has the time to be fiddling around remediating loads of issues on client machines.ĭoes your security team have a contender in mind? Oh yes, I'd also forgotten the original issue, even with the previous client □ basically we use crowdstrike as well, however on newly imaged machines, if forcepoint is installed with the task sequence, it blocks crowdstrike from installing. There seems to be no rhyme or reason to it. This will also be my recommendation, this has been super disruptive and it's inexplicable how it can install for one, with a single reboot, and the next machine takes 30 mins worth of manual intervention to finally get it working. I'd love to know others'experiences with this nightmare solution, in particular the latest version and if you got it pushed out without any issues, how on earth did you do it? Never in my life have I had so much grief from a single solution, the last forcepoint update went like a dream with not even a single reboot. The only way to remediate the issue when it gets to this position is to use the Microsoft install/uninstall tool to forcibly remove Forcepoint and install it again exactly the same way it was initially installed. I've manufactured the package about a million different ways and even at best a reboot is needed, in many cases even when installed successfully the damn thing just refuses to work properly, displaying the proxy authentication box. I cannot understand how this absolute bastard of a solution can be successfully deployed reliably. We have about 1k endpoints and I can honestly say this forcepoint update is the biggest nightmare I've ever come across. ![]() Has anyone had the misfortune to deal with pushing the latest forcepoint out, possibly replacing the old version or a new install on new machines? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |