Deploying Cisco Secure Connect client via SCCM

[MerkiWaters]

Hello,

I'm attempting to deploy the latest Cisco Secure Connect client to our users that work remotely.  I've created an Application in SCCM that utilizes msi files and a cmd script as the installer.  I've been successful in getting the software to install on my test machine.  However, the client does not launch automatically after the installation - the VPN connection drops (as expected) the installs take place and that's it.

I've tried creating a second Deployment Type called "Start" in the application that has the first DT as a dependency.   The "Start" DT is set to run in the user context while the Install DT runs as system.  "Start" has a cmd file that is supposed to launch csc_ui.exe once the Install DT finishes installing the msi's.  In short, this isn't working.  AppDiscovery.log shows that "Start" is determined to not yet be installed, but then it doesn't not install and there's no evidence of action or error regarding it in AppEnforce.log.

Am I approaching this correctly?  How have others here deployed the client to remote workers and have the software launch automatically and the VPN connect again?

[alemabrahao]

You can add a launch step to your original install script using ServiceUI.exe or a scheduled task, this avoids the need for a second DT and ensures the UI relaunches after install.

[MerkiWaters]

Thank you, although this is proving difficult.  In the Installation Program field, I'm specifying

powershell.exe -ExecutionPolicy Bypass -File "Install-SecureClient-PowerShell-Test.ps1"

I have the ps1 file and ServiceUI.exe as part of the content.

The ps1 file has this code:

# Quote the target application path

$serviceUIPath = Join-Path -Path $PSScriptRoot -ChildPath "ServiceUI.exe"

$targetApp = "C:\Program Files (x86)\Cisco\Cisco Secure Client\UI\csc_ui.exe"

$quotedAppPath = "`"$targetApp`""

Start-Process -FilePath $serviceUIPath -ArgumentList "/Process:explorer.exe", $quotedAppPath

I'm using Start-Transcript functionality to log all output.  The script seems to run fine but the Cisco Secure Client never launches.  I've tested this script by running locally in a powershell terminal run as System (using psexec -i -s powershell.exe)

Could you share the code you've used?