Showing results for 
Search instead for 
Did you mean: 

Packaging Pulse Client

Regular Contributor

Packaging Pulse Client

We will shortly be moving from Network Connect to Pulse and are working with our SCCM packaging team to create a package to deploy the Pulse client with the configuration pointing to our boxes. Everything works until Pulse starts at the end of the install at which point we get an "Interactive Services Detection" message from Windows saying a program is trying to display a message. The project is Pulse and it seems to be the Splash screen it's trying to show.


Running the package manually from a command line works without any problem so we suspect it is an issue the user package runs as. Anyone know how to get round this or a parameter in the installer to stop Pulse running immediately after the install?


Pulse Version:

Command using to install:

msiexec.exe /i JunosPulse.x86.msi CONFIGFILE=%CD%\Pulse.jnprpreconfig ADDLOCAL=PulseNC,NCTNCClientPlugin /l*v "%windir%\Logs\JunosPulse_Install.log" /qn



Respected Contributor

Re: Packaging Pulse Client

i'm not sure; what are you seeing in the log file?

can your sccm team suppress messages to work around this?

does this happen with newer versions of Pulse (3.0, 3.1, or 4.0)?

Frequent Contributor

Re: Packaging Pulse Client

Have you tried to disable the Splash Screen in the connection set?