Reset Search
 

 

Article

KB28093 - Pulse Connections are not listed in the active connection list of Pulse GUI when deployed through preconfiguration file.

« Go Back

Information

 
Last Modified Date8/1/2015 10:24 PM
Synopsis
When Pulse Secure Desktop Client is deployed using a preconfiguration file on machines running Windows, no active connections are listed even though connection profiles are listed in the preconfiguration file.

This KB provides one possible reason as to why the connection profiles are not getting listed in the Pulse GUI.
Problem or Goal
The Pulse Secure Desktop Client preconfigured installer program with msiexec (the command line for launching .msi programs on Windows platforms) is used when Pulse Secure Desktop Client is deployed using a preconfiguration file on Windows machines.  When the program is run, the Pulse client is installed however no active connections are listed even though connection profiles are configured as part of generating the preconfiguration file.

The Pulse Secure Desktop Client logs display messages similar to the following: 

=================================================================================================================
00136,09 2013/08/26 12:16:20.811 3 user jamcommand.exe jamCommand p0448 t7D8 jamCommand.cpp:639 - 'jamCommand' Import data to connection store.
00149,09 2013/08/26 12:16:20.811 1 user jamcommand.exe jamCommand p0448 t7D8 jamCommand.cpp:211 - 'jamCommand' unable to open script file test.jnprpreconfig
00134,09 2013/08/26 12:16:20.811 1 user jamcommand.exe jamCommand p0448 t7D8 jamCommand.cpp:655 - 'jamCommand' ImportFromFile failed. Code -1

00229,09 2013/08/30 12:16:49.281 3 SYSTEM dsAccessService.exe ConnectionStore p2756 t264 ConnectionStoreDocSet.cpp:528 - 'ConnectionStoreService' SaveDocument: C:\Program Files\Common Files\Juniper Networks\ConnectionStore\connstore.dat
00232,09 2013/08/30 12:16:49.281 3 SYSTEM dsAccessService.exe ConnectionStore p2756 t264 ConnectionStoreDocSet.cpp:591 - 'ConnectionStoreService' SaveUserDocument: C:\Program Files\Common Files\Juniper Networks\ConnectionStore\S-1-5-18.dat
00274,09 2013/08/30 12:16:49.421 1 SYSTEM dsAccessService.exe ConnectionStore p2756 t264 ConnectionStoreDocSet.cpp:67 - 'ConnectionStoreService' Invalid/missing config file: C:\Program Files\Common Files\Juniper Networks\ConnectionStore\S-1-5-21-57989841-1844237615-1417001333-1003
==================================================================================================================


What do the errors mean and why are no active connections displayed?
Cause
The following command line for the CONFIGFILE property was defined wrong.  The Pulse Secure Desktop Client installation is incomplete, hence there are no active connections listed in Pulse UI.

msiexec -i PulseSecure.x86.msi CONFIGFILE=dot1x.jnprpreconfig /qb
Solution
To use the CONFIGFILE property on the msiexec command line, you must specify the full path to the preconfiguration file. The MSI calls jamCommand (which is located in the Program Files\Common Files\Juniper Networks\JamUI directory), if no path to the configuration file is given, jamCommand will look in its own directory instead of the actual location.

Incorrect Syntax which is causing the issue:

msiexec -i PulseSecure.x86.msi CONFIGFILE=dot1x.jnprpreconfig /qb

Correct Syntax with no issue:

msiexec -i PulseSecure.x86.msi CONFIGFILE=<full path to file>\dot1x.jnprpreconfig /qb
 

Once you execute the correct syntax, Pulse Secure will install completely with the preconfigutaion profile configured.  After a successful installation, the configured connections will be listed under the Pulse Secure GUI.
Related Links
Attachment 1 
Created ByData Deployment

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255