Installation and setup changedthird-party/claude-desktop/installation
Nearest release: v2.1.239, published an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+6added
Lines−6removed
From line
45
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits23to this page, all time
The whole hunk
from line 45, old and new numbered
/
from line 45
4545
4646Configuration reaches devices in one of two ways. Both typically use your MDM tooling to push a profile; the difference is what the profile contains.
4747
48| | MDM profile | Bootstrap server |
49| -------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
50| What you deploy to devices | The full configuration, exported as a `.mobileconfig` or `.reg` profile | A minimal profile containing only the bootstrap keys (`bootstrapUrl`, optionally `bootstrapOidc`) |
51| Where settings live | In the profile, identical for every device the profile targets | On an HTTPS endpoint you operate, which returns each user's configuration at sign-in |
52| Per-user values | Separate profiles per device group | The server keys its response to the signed-in user |
53| Changing settings | Export and push an updated profile | Change your server's response; devices pick it up at the next fetch, with no profile push |
48| | MDM profile | Bootstrap server |
49| -------------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
50| What you deploy to devices | The full configuration, exported as a `.mobileconfig` or `.reg` profile | A minimal profile containing only the bootstrap keys (`bootstrapUrl`, optionally `bootstrapOidc` or request headers) |
51| Where settings live | In the profile, identical for every device the profile targets | On an HTTPS endpoint you operate, which returns each user's configuration at sign-in |
52| Per-user values | Separate profiles per device group | The server keys its response to the signed-in user |
53| Changing settings | Export and push an updated profile | Change your server's response; devices pick it up at the next fetch, with no profile push |
5454
5555Choose an MDM profile when one configuration, or a few group-scoped profiles, covers your fleet. Most MDMs support role-based distribution, so per-group configuration doesn't require a bootstrap server.
5656
No line in this hunk matches that.