Category filter
Configuration profile to automatically install web apps for macOS users
Admins can remotely install web applications on users’ macOS devices. To install web apps for the Chrome browser, the Chrome browser on users’ devices must be managed by the organization.
To enroll cloud-managed Chrome browsers, sign up for Chrome Browser Cloud Management (CBCM), generate an enrollment token, and add devices to the console. Once the Chrome browser is managed, admins can deploy a configuration profile using the Deploy Custom Configuration feature to remotely install the desired web apps on Macs.
The sample configuration profiles provided below are created using various profile creator applications.
Install web applications
You can automatically install web apps on devices without any user interaction. To set up automatic installation, add the URLs of the desired web apps as the value for the WebAppInstallForceList key. Once installed, users will not be able to remove or disable these apps.
Below is a sample configuration profile to install the Google Docs web application on the user’s device.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 |
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>PayloadContent</key> <array> <dict> <key>PayloadContent</key> <dict> <key>com.google.Chrome</key> <dict> <key>Forced</key> <array> <dict> <key>mcx_preference_settings</key> <dict> <key>WebAppInstallForceList</key> <array> <dict> <key>url</key> <string>https://www.docs.google.com</string> </dict> </array> </dict> </dict> </array> </dict> </dict> <key>PayloadDisplayName</key> <string>Google Chrome Web Apps</string> <key>PayloadEnabled</key> <true/> <key>PayloadIdentifier</key> <string>com.Chrome.319C8431-3922-48B1-AA46-74D91F945074</string> <key>PayloadType</key> <string>com.apple.ManagedClient.preferences</string> <key>PayloadUUID</key> <string>319C8431-3922-48B1-AA46-74D91F945074</string> <key>PayloadVersion</key> <integer>1</integer> </dict> </array> <key>PayloadDescription</key> <string>Chrome web apps policy</string> <key>PayloadDisplayName</key> <string>Chrome Web Apps</string> <key>PayloadIdentifier</key> <string>macOS.0B44A8EE-0CF7-4335-8D92-54C6C1FA52BE</string> <key>PayloadOrganization</key> <string>CompanyName Inc.</string> <key>PayloadRemovalDisallowed</key> <false/> <key>PayloadScope</key> <string>System</string> <key>PayloadType</key> <string>Configuration</string> <key>PayloadUUID</key> <string>1ADCFBB4-BF11-4273-AC4C-F8FE2EFA528D</string> <key>PayloadVersion</key> <integer>1</integer> </dict> </plist> |
Users need to restart the Chrome browser for the configuration profile to take effect. Once you successfully associate the configuration profile, you will find the web app installed on the device. The web app will be accessible from the device’s Launchpad, and it can be differentiated by its distinct icon and name. Generally, the name of the web app displayed on the Launchpad corresponds to the website or service it represents.
- To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager or manually create them using text editors.
- Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across devices.
- Ensure that you do not associate conflicting configurations with the devices.
- It is recommended to manually validate the configuration profile on a system before executing it in bulk.
- Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.
