If you're an organization that manages computers for its users then you may have questions about how to distribute the Little Arms Launcher and Zephyr and how to manage updates to both applications.
Ultimately each organization’s situation and distribution platforms are different, but the same principle can be applied to your situation.
The key points about these applications and their interactions are as follows:
Zephyr MUST be launched through the Little Arms Launcher
The Little Arms Launcher is used to manage Zephyr updates
The Little Arms Launcher is responsible for managing login credentials and downloading required Zephyr content
We’ll use Microsoft’s Configuration Manager as our first example.
Create a content object in the Microsoft Configuration Manager
NOTE: the content object could contain the Little Arms Launcher & the Zephyr application, but we advise that they use separate content objects for each since Zephyr updates differently than the Little Arms Launcher
Once the content objects are created, you can use the Software Library in the Configuration manager to make those content objects available to the clients.
You would use the client manager to tell the clients to download the content objects if they are out of date.
Where there is an update to the Zephyr or the Little Arms Launcher applications, you can update the files in those content objects and trigger an update cycle on the clients.
That will update the sim silently to whatever they have placed in the content object.
Reference guide:https://learn.microsoft.com/en-us/mem/configmgr/core/servers/deploy/configure/deploy-and-manage-content