When you deploy a preconfiguration file along with client, the user sees those connections when app is launched. ![]() With preconfiguration file you can define settings such URI, server ID, GUID etc. However in this post I will cover the deployment of pulse secure client along with preconfiguration file. Most of all Pulse Secure Desktop client is available for download as 32-bit and 64-bit installers. Probably you can get the latest installer and still the same deployment steps should work.ĭownload Pulse Secure Desktop Client 9.1Rx. So I thought of posting a deployment guide of pulse secure desktop client using SCCM.Īt the time of writing this post, the latest version of pulse secure desktop client is 5.3 R6. I have seen some large enterprises using pulse secure desktop clients. There is something called Pulse Connect Secure, which is a mobile VPN to enable secure access from any device to enterprise apps and services in the data center or cloud. ![]() The pulse secure gateway could be either Pulse Connect Secure or Pulse Policy Secure. The endpoint device could be a Windows 10 client or mac computer. The Pulse Secure desktop client provides a secure and authenticated connection from an endpoint device to a Pulse Secure gateway. First of all let me provide some details about pulse secure desktop client. ![]() This post covers the steps to deploy Pulse Secure desktop client using SCCM.
0 Comments
Leave a Reply. |