This may be a question for Sonicwall (not Intune Reddit) but here we go anyway. I’ve pushed a Sonicwall VPN client successfully via Intune/EM to our client systems. The VPN client obviously requires a hostname/domain to connect, so I created a batch file that adds in the hostnames to our VPN servers, which I’ve tested by running locally on my system without issues:
@ECHO OFF
SET MPPATH=“C:\Program Files (x86)\SonicWall\SSL-VPN\NetExtender”
CD %MPPATH%
NECLI.exe addprofile -s (our vpn hostname) -d (ourdomain)
I packaged the batch using IntuneWinApp - then built a new Win32 app in Intune. I deployed it to a test PC and even though Intune says it ran successfully on the target system, it did NOT add in the server hostnames. I am scratching my head, any advice?
Install and open ORCA from microsoft. (need sdk pack)
Open the MSI and navigate to the PROPERTY section on the left.
Change SERVER, DOMAIN to your desired values. Also, change ALLUSERS to value of 2. Change EDITABLE to TRUE
Right click and add a new row in the properties called NETLOGON with a value of true
Save .
Deploy the new MSI with intune and it will install to all users on the machine, have editable fields for the domain and server, but be prepopulated with your specified server and domain values if set. Silent install reference for other deployments
I have this working… I added my required IP and domain by modifying the registry settings. I have it pushed out via Powershell script from Intune right now, but it does say that it “fails”, however, the registry changes are made and the connection information is visible in NE. I added a profile on a test machine, then copied the registry keys from there. Below are the registry keys I add to each new machine. (XXXX would be your info).
Ah, wonderful, thank you. I actually did end up getting it working, with one caveat. I converted the script to Powershell, then deployed via intune and set it to run in the USER profile (not system profile). It works, but may be problematic when we deploy to users that do not have admin rights (the vast majority of users). I’ll try this if it doesn’t work out. Thank you!
I will try to test later, but I believe a second profile is just a dropdown in the UI for the Server box, so just adding 2 entries on the field may work. Not sure the separator that should be used, but it only takes a few mins to edit the msi and install/uninstall
Update: setting the script to run in the user profile WORKS even when deploying to user’s that don’t have admin rights (99% of them). It seems admin rights are not necessary to run the NECLI command line profile add rules. So we are all set!