Hi Mark,

I looked at the deployment videos and are you sure you want to set the script to After?  I would think that the .plist file would need to be on the Macbook prior to the software installing.  Also there is nothing in the videos stating how to setup the system extension for Big Sur and Catalina.  you state how to do a KEXT but that is not enough for the two newest macOS's.

Hey all!!  Just wanted to hop in here and update everyone on a few things that have happened.  First, I'll state: I'M A NETSKOPE EMPLOYEE  🙂  Now that that's out of the way, we've been GA for Big Sur for some time now.  Obviously, this posting I'm responding to is a bit old; the client version is showing 80.x, and we're now on 88.x, so that speaks to the changes/progress version wise.  From a JAMF/Big Sur perspective, hop on over to our support portal and check out these articles:

https://docs.netskope.com/en/deploy-netskope-client-with-jamf.html

https://support.netskope.com/hc/en-us/articles/4402657721111-Netskope-Client-on-macOS-11-Big-Sur

The first is specifically to JAMF deployment, per the name.  The second is more around the client operation itself.  It's no secret: the new architecture of system/network profiles vs kexts has presented some challenges for ALL VENDORS as we adopt to the new way/permissions required to operate successfully, and we've put a lot of time into researching/building/troubleshooting/etc.  Most times when issues occur, it's not just one component...it's when two components are both using the network profiles to spin up tunnels (Anyconnect AND Netskope, for instance)...and most of that has been addressed as well.  Be sure to follow best practices with VPN clients and interop with Netskope, which can be found on the support portal as well...just query your VPN client, and I can almost guarantee you'll find a config doc for it!

Lastly, please do join the Netskope Community: https://community.netskope.com/

The more members we have, the more that's shared and the stronger/better we all get together!!!

Cheers!

I've been working on deployment of the Netskope Client to macOS 11+ (Big Sur, Monterey, etc) recently.  

We're installing v96.0.0.1009 currently, and using a combined Config Profile containing both Approved Kernel Extensions and System Extensions (to cover macOS 10.15+).  We use a Smart Computer Group to identify those Macs where the config profile has been installed for scoping the client install Policy (which runs at Recurring Check-in, Once per computer).  The install takes place in the background while no user is logged in.

So far this process is working OK for macOS 10.15 Catalina clients, with no prompts to the user at login.  On macOS 11+ clients the user is prompted to allow "proxy configurations".  This prompt is incessant and will continue to appear until Allow is clicked (no matter how many times you click 'Don't Allow').  Anybody else seeing this?  Is there some way to avoid this by deploying the proxy configuration with the config profile?  Below is what we see in Sys Prefs, and it is a VPN configuration (but referred to as 'proxy configuration' by the Netskope Client installer).

Hi @janthenat 
I have the same question as you. Did you find the solution to this?

Unfortunately, no... but that's because probably because I have not spent any time on it since that last post.  I was really hoping someone else would solve it for me ;^)

Haha our job makes us become too lazy :P

@leobrt @janthenat Do you have a VPN payload in your Netskope Configuration Profile? If not see the "Approve VPN Popup for App Proxy" section in this guide: https://docs.netskope.com/en/netskope-help/traffic-steering/netskope-client/netskope-client-deployment-options/jamf/