New-ItemProperty -LiteralPath 'HKLM:\SOFTWARE\Fortinet\FortiClient\Sslvpn\Tunnels\LETSCONFIGMGRVPN2' -Name 'Server' -Value 'demovpn2.someaddress. New-ItemProperty -LiteralPath 'HKLM:\SOFTWARE\Fortinet\FortiClient\Sslvpn\Tunnels\LETSCONFIGMGRVPN2' -Name 'Description' -Value 'Lets ConfigMgr VPN 2' -PropertyType String -Force -ea Silentl圜ontinue C:temp to avoid long path names and would call the win32 installer/setup from there, wait for exit and gather exit code to return the exit code to the Intune Win32 package. I would package the program files of my app into a 7zip or regular zip archive and my custom installer would then extract to e.g. If ($ENV:PROCESSOR_ARCHITEW6432 -eq "AMD64") I would install the app via a custom install wrapper script. Installation Scriptįor the sake of this demo, I am going to make up the VPN address, but this can be edited for your actual gateway address, the installation script is as follows (Save as InstallFortiClientandProfile.ps1): # Restart Process using PowerShell 64-bit We need to create the installer and Uninstaller scripts before we can wrap and upload the files to Microsoft Intune, these scripts will deploy FortiClient VPN and configure the VPN Profile. Creating the Installer \ Uninstaller Scripts
0 kommentar(er)
