Proximity Company Roll out

[Mitchell Smith]

Hi, We have a few questions on rolling out Proximity company wide.

We have figured out how to suppress the EULA, first run wizard, and the auto start when systems are rebooted. How do we stop the application launching right after it is installed?

Are there any security implications for microphone always listening on laptop?

We read that per system install disables the auto update feature. Is that true?

[mneergaa · Accepted solution]

1. Suppressing autostart is not currently supported. I have plans for making such a feature, probably by adding the property LAUNCH_PROXIMITY. That property, when implemented, would be available on the msiexec command line and through some deployment tools. If you are using group policy to deploy, you would have to make a transform for the property.

2. The data captured from the microphone is never stored to disk or sent anywhere. Any security implications from running the Proximity app are, as far as I know, not directly related to listening to the microphone.

3. Yes, per-system installs disables auto-upgrade. This prevents a circular upgrade in a naive mass deployment (e.g. Proximity 2.0.4 is mass deployed, 2.0.5 is latest, computers keep upgrading and downgrading between the versions...)

[Ray1o]

Hi, Could you please elaborate on disabling auto update using per-system installs. We are doing a mass deployment using SCCM and our users do not have admin rights to update Proximity. We dont want them to keep receing update alerts.

Thanks,

Ray

[mneergaa · Accepted solution]

There is now an additional option for suppressing auto update. Please check the guide at https://supportforums.cisco.com/t5/mobile-applications-documents/windows-mass-deployment-guide-new-as-of-version-2-0-8/ta-p/3314009