Enabling Netskope before login
Good afternoon all,
So I've made some great progress on getting netskope to run so I can access all my network resources etc when it's up and running. However I've run into an issue when it comes to doing a remote Hybrid AD join.
The application is packaged up and working
I can access my domain controllers when not on a VPN through netskope private access.
What I can't do at the moment is domain join machines remotely, is there a way that I can for want of a better word, bodge the install or configure it in such a way so I can open network access and then authenticate against my on-prem domain controllers? I read somewhere that you can use NSBranding.JSON or something to enable the configuration but I can't find any official documentation.
Good morning RGE_Master,
Currently, Private Access only runs in as the logged in user and there is currently no way with the current product to have a tunnel come up prior to login. Do you have a local admin account provisioned on these devices? If so, my suggestion is to log in for the first time with the local admin account, which will allow the NPA tunnel to connect, then do a domain join. Do not reboot, but instead after joining the domain, switch user to a domain user which will then cache the credentials of the now logged in domain user.
I would also suggest reaching out to your SE so they can line up a call with the product manager so you can hear of our plans to better address this use case in the coming months.
We are actively developing capability in NPA, to allow Windows PCs to connect to Domain Controllers, w/o requiring the user to authenticate into the Netskope Client. This would be similar to the Pre-login capability that exists in traditional VPN solutions. Is this something you are interested in learning more about? If so, please DM me or have your account team ping me.
Netskope Private Access
Hi, @chrisisinclair. Welcome to the community! I'm on the community team (not an SME). Let me know if you need any help with the community. Just @mention @JulieB and I can help you to find the right staff to answer your questions. Also, feel free to send me any community feedback through a DM. Thanks again for joining us!
The call was very informative! However, we've chose to wait for GA since I recall we discovered we were facing an issue in the Netskope client that would be fixed in next release.
We have recently moved the entire organization to NPA so Pre-login will be an exciting next step.
@AidanH NPA Prelogon is GA starting with Netskope Client 97.1 release.. Documentation is available here - https://docs.netskope.com/en/netskope-client-configuration.html#UUID-1e7e72e4-74ef-f041-8dec-ee64a30...
PreLogin itself has been working well for us but unfortunately since it is not compatible with MultiUserMode (the "puruser" install flag) we will unfortunately have to wait until it is to deploy out to our fleet
We deploy all Netskope clients in multi user mode (the default is single user). This ensures that the client updates policies and logs traffic under the current logged in user instead of locking a particular machine to the very first user who logs in.
Currently PreLogin does not work with multi user mode (according to their support) so while the IT staff we have that tested Pre Login and found it to work well (we confirmed windows laptops even authenticate against AD with the right settings!) we are not going to enable it until they get it working with multi user.
@KunalShah Is the multi user mode truly not supported? We also use mode=peruserconfig in our deployments. Although our devices are usually 'owned' by one primary user the reality is any other user may login to a device. This is especially true for our "loaner' laptops and test PCs we have deployed in our office locations around the world.
We were looking forward to GA in July
That is exactly our use case as well - and in addition usually one of our helpdesk staff will logon to the laptop right after being imaged to finish up a few quick tasks before it is deployed to the user - if single user mode is enabled then the laptop unfortunately gets locked to the helpdesk user account. Of course this is no good as whatever user policies are supposed to apply to the end user will not apply (it will apply the users assigned to the helpdesk user)
Great 97.1 supports Prelogon on perusermode,
Couple of questions @KunalShah
- Do we need to specify prelogonuser= argument during msi install with 97.1x?
- Since Client Configs does not allow the use of same prelogin account in different Configs , what is expected behavior when different users associated to different client configs login to the perusermode configured machine? Would the prelogon account change to the one defined in client config pulled down by last logged in user?