Pulse Install via Intune with config file

I’m trying to get pulse installed via Intune with a custom config file. I’ve packaged the msi, config file and bat file into a .Intunewin file. The command line I’m using is…

msiexec.exe /i “PulseSecure.x64.msi” CONFIGFILE=“cmpIntune.pulsepreconfig” /qn /norestart

This does not seem to be working correctly. Looking for some direction. Pulse gets installed, but when I open pulse after windows loads, there are no configurations applied. If I run the command from windows, it works fine and the configuration is there.

Thanks

Interesting. Did you open a ticket with Pulse about that? What client version do you distribute?

A few customers of mine distribute the client via SCCM (or something similar: I’m not very familiar with Windows world) and all works fine.

EDIT: Did you try to set full-path to the config file? Might it be that when triggering the command remotely, the working directory is different and msiexec simply can’t find the file?

Hi,

I know this is quite late, but I was having the exact same problem when attempting to automate the installation of the Pulse Client for Autopilot. Below is how I was able to resolve in the end.

  1. Create a Win32 app without the CONFIGFILE property (i.e. msiexec.exe /i “PulseSecure.x64.msi”)

  2. Create a new folder with only the pulsepreconfig file.

  3. Create a .cmd file with the below command
    ““C:\Program Files (x86)\Common Files\Pulse Secure\JamUI\jamCommand.exe” -importfile .pulsepreconfig
    echo “Pulse config imported successfully” > C:\Windows\Temp\Pulse-Config.txt”

  4. Create the Win32 app using the .cmd file.

  5. Upload to Intune and Use the detection of “C:\Windows\Temp\Pulse-Config.txt” as the detection rule.

  6. Set the Pulse Secure Client as a dependency to the config file.

Wala! All done. Took a bit of time but got there in the end.

The jamCommand.exe application comes pre-installed with the VPN client and can be used to import Pulse config files.

Are you saying to create two separate .intunewin files? One for the Pulse Secure installer, and the second for the Pulse Config?

Hi,

Thanks for this! I have a few questions:

  1. when i add the config file as an win 32 app in intune: What do i write in the install/uninstall command field?
  2. How do i add the cmd script file when its only powershell that can be added?

Thanks!

/Jonas

Yes thats correct - when you upload the config, make the pulse installer a dependency.

  1. Install: msiexec.exe /i “PulseSecure.x64.msi”
    Uninstall: MsiExec.exe /X{6D8DF24A-085C-4C75-9D40-55D26259529E}*

  2. You have to use the Intune Win32 Content Prep tool. You’ll need to look into how to use that as it’s a little out of the scope of this thread. Here’s one guide you could use.
    How to deploy Win32 Apps with Intune » Prajwal Desai

*****The GUID may change depending on the version you have installed. You can check the uninstall string of your version by navigating to the below hive in your registry:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall

Once I understood I was able to get it to work. I put the “Config” installer in the Company Portal so when it’s executed from there, it calls the app dependancy and installs that first. Works brilliantly. Thank you!!!

Thanks for the quick answer

Maybe i am missunderstanding but my question was specific on when i add the config file as a intune app and the install command for that since its not an msi.

I have created two separate intune win files: one from the msi and one from only the pulse secure konfiguration file. When i add the intune win file based on the config file i get the option to add install command and uninstall command. Also when trying to add the script to the config application i only get the option to use powershell.

If u have the time to explain i would be very grateful thx!

/Jonas

Awesome, glad it worked!

am

Ah okay - I think I understand.

So with the config - the cmd from step 3 is packaged with the config file as a Win32 app.

I’ve used both the install/uninstall commands to point to the cmd file within the intunewin file you’ve uploaded.

Config file
- Is a intunewin file that contains both the .pulseconfig & .cmd file.
- Is uploaded to intune as a Win32 app
- I’ve used the same .cmd for uninstall as for the install.
-- Even though this technically doesn’t remove the config file, it’s unimportant as
-– 1) This is a dependancy of the actual Pulse Client install package.
-– 2) Based on this assumption, the config file will uninstall as part of the client uninstallation (not confirmed but either way it’s not really a big deal).

Ok now i get it thx so much!