About ibrahim_pulseadmin

ibrahim_pulseadmin · ‎09-24-2019

As per the documentation available in Pulse Secure Admin Guide below; https://docs.pulsesecure.net/WebHelp/PDC/9.0R1/Content/PDC_AdminGuide_9.0R1/Using_jamCommand_to_Import.htm # Using jamCommand to Import Pulse Secure Connections To install Pulse connections using jamCommand: Create a . pulsepreconfig file on the Pulse server. In the Pulse server admin console, click Users > Pulse Secure > Components . Select the component sets you want, and then click Download Installer Configuration . Distribute the . pulsepreconfig file to the Pulse endpoints. Run jamCommand with the . pulsepreconfig file as an option. For example: On Windows: \Program Files\Common Files\Pulse Secure\JamUI\jamCommand -importfile myfile. pulsepreconfig For Windows machines, create a new GPO at Windows Login and push this changes via Script/Batch File. //Ibrahim

ibrahim_pulseadmin · ‎07-16-2019

In the config file (access.ini) the folder location # C:\Program Files (x86)\Common Files\Pulse Secure\JUNS\access.ini there is section for CAV as shown below. We need to change Start Type from ‘Auto’ to ‘Manual’, the cav.exe won’t be started by Pulse service. [CloudAppVisibilityService] StartType=Auto You can include this file modification request during the time of creating a new application package request with the packaging/deployment team. If the PCD client has been pushed to all the machine base, then check the feasibility on your side to push/deploy this file using SCCM or any similar tools, followed by ‘Pulse Secure Service’ service restart(or machine restart), the CAV won’t start i.e. functionality will be disabled. Hope this helps. //Ibrahim

Re: Auto publish New connection

Re: Remove Cloud App Visibility agent (cav.exe)