If I look at the instructions for configuring prelogon, then this seems to require a reinstall of the client with the correct “prelogonuser=<user>@prelogon.netskope.com” command line parameter.
The “nsdiag” command does have a few extra things up its sleave, including update of the secure enrollment tokens.
Is there a (hidden) option to also allow adding a prelogon user to an already installed client?
--Erik
Best answer by sshiflett
@elawaetz,
A reinstall is not required for prelogon. You can enable prelogon for already provisioned and enrolled devices by updating the respective client configurations with prelogon settings. Once you’ve done this, the clients will begin enrolling with these settings as they check in.
The instructions to enable via the command line installer are for cases where a user hasn’t enrolled and you want to provide machine level connectivity such as first time log ons, joining a remote machine to the domain and Intune Autopilot.
A reinstall is not required for prelogon. You can enable prelogon for already provisioned and enrolled devices by updating the respective client configurations with prelogon settings. Once you’ve done this, the clients will begin enrolling with these settings as they check in.
The instructions to enable via the command line installer are for cases where a user hasn’t enrolled and you want to provide machine level connectivity such as first time log ons, joining a remote machine to the domain and Intune Autopilot.