Numbers below are for the "Mobile" install mode.Īlso keep in mind that Mobile & Securemote installs are NOT affected by the issue in sk171213 (that wasn't crystal clear in the initial wording of the kb). My guess is that the build number is different, depending whether you install the client in "Checkpoint Mobile" mode, or in "Endpoint Security" mode, for instance. Here's a table that I made, correlating the "E8x.xx" version number with the build number reported by inventory tools.
If there's a good way to determine the Windows/MacOS version that will be unsupported, please share. There was older post I came across which had a similar concern. Unsure what CP employee/dept needs to see this ( but if CheckPoint could update sk102150 with the Windows/MacOS version numbers in another column I think that would solve some of the confusion. It would be very helpful for those of us with asset tracking systems such as SCCM/PDQ/Etc to find unsupported client versions listed in sk171213. I don't have a Mac to test with, so I can't confirm how it looks from the OS X point of view.
From within Windows 10 Programs and Features, it lists E84.20 as version. This SK is a great resource, but the one critical thing it doesn't list is Windows/MacOS version numbers alongside of the CP Client Version/Build Numbers.Įxample: CP Client version E84.20 has a Client build number of. In regards to the recent VPN Clients failing to work after (sk171213), I did some digging to find the VPN Build Numbers article (sk102150).
0 kommentar(er)
