New Cloud Client MSI Parameter - No CSE (Cloud Client ONLY)

What is a one sentence summary of your feature request?

New Cloud Client MSI Parameter - No CSE (Cloud Client ONLY)

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

We use multiple imaging options. During imaging, we prefer to manage, prescribe, and control as much as possible. The cloud client MSI automatically checks for, downloads, and installs or updates the CSE. This process is usually successful, but it adds a layer of network communication and an aspect of a “delayed finish” that has sometimes disrupted the imaging process. A “No CSE” MSI parameter would allow the sequential and controlled installation of the Cloud Client then the CSE.

How do you currently solve the challenges you have by not having this feature?

We add both Cloud Client and CSE installers to our installation package, and we add logic to install the CSE first if the device is imaging. The Cloud Client “No CSE” parameter would remove some complexity and margin for error. It would also provide a bonus option for easier rollbacks if ever necessary.

Before I answer, if you have a LATER or CURRENT CSE already on the box (vs. the specific group), then the Cloud Client doesnt attempt to download anything. Have you tried that yet?

Yeah, that “current or later CSE” scenario has been the experience so far. That’s essentially what we already do during image deployment workflows - install the CSE before the Cloud Client. However, in non-imaging scenarios, I still like installing the Cloud Client and letting it do the needful regarding the CSE. Also, upgrading versions via cloud works very well :slight_smile: The majority of our deployments and initial installs occurs during imaging. This request is because I like the idea of having as much of a controlled and expected workflow as possible in as much of the imaging workflow as possible.

Check to see if this magically works..

The property is SKIPCSEINSTALLATIONWHENREGISTERING

Possible values are 0 - don’t skip CSE installation when registering, 1 - skip CSE installation when registering. CSE installation is skipped during registration time., CSE is installed by PPC Client automatically withing next 4 hours.

Example:

msiexec /i “PolicyPak Cloud Client for PolicyPak Internal (Customer) x64” /quiet /l logfile.txt SKIPCSEINSTALLATIONWHENREGISTERING =1

Hey hey.. Making sure you saw my response.. Thanks !

1 Like