fleetdm / fleet

Open-source platform for IT, security, and infrastructure teams. (Linux, macOS, Chrome, Windows, cloud, data center)
https://fleetdm.com
Other
3.03k stars 419 forks source link

Support additional keys for software update DDM #20501

Closed spokanemac closed 2 months ago

spokanemac commented 3 months ago

UPDATE: Closed because it's duplicate of the following issue:

(noahtalerman)


Problem

As a Mac Admin, I would like to take advantage of the additional keys in the softwareupdate.enforcement DDM configuration including setting the time of day for TargetLocalDateTime, adding a DetailsURL, and support for TargetBuildVersion to allow testing this feature with beta updates on macOS, iOS, and iPadOS.

What have you tried?

This DDM JSON is obfuscated behind UI or GitOps configurations.

Potential solutions

Support all keys in the UI and GitOps declaration or provide a method to maintain my own JSON configuration for this declaration.

https://github.com/apple/device-management/blob/release/declarative/declarations/configurations/softwareupdate.enforcement.specific.yaml

What is the expected workflow as a result of your proposal?

As a Mac Admin, I can target a specific build to install by a specific date and time while providing a company-specific URL explaining the upcoming action on the user's device.
nonpunctual commented 3 months ago

https://github.com/fleetdm/fleet/issues/20500 this ticket is a duplicate of 20501. Please pull in all info from both into a single ticket if one is closed as a duplicate. Thanks.

Also, related: https://github.com/fleetdm/fleet/issues/10826

noahtalerman commented 2 months ago

Thanks for tracking this @spokanemac!

I would like to take advantage of the additional keys in the softwareupdate.enforcement DDM configuration including setting the time of day for TargetLocalDateTime, adding a DetailsURL, and support for TargetBuildVersion

As an IT admin at Fleet, what would you set these values to?

nonpunctual commented 2 months ago

@noahtalerman @spokanemac I think the TargetLocalDateTime is the most useful. If you had a culture of doing updates "at the end of the day" or "at the beginning of the day" this setting lets you broadly account for that. TargetBuildVersion is also useful. Yes, you want everyone "up-to-date" but there may be some time period you are on version X.1 & assessing X.2, so X.2 is not released until assessment is complete. Same kind of thing customers do with Fleet releases.

spokanemac commented 2 months ago

@noahtalerman

Here's how the DetailsURL appears in the OS: 20240718_092302_psumac2024-Delving-the-Depths-of-DDM pdf

spokanemac commented 2 months ago

I'll also add that there is a potential to want to set these on a per-host basis (Maintenance windows) vs. Team-wide.

According to . DDM software updates are the preferred method for >= macOS14.4. For maintenance windows, I would like to set the date and time of a macOS software update using DDM. I have been informed that this can be changed reliably up to an hour before. (If the update was set for 9 a.m. on Tuesday, you could change this anytime before 8 a.m. on Tuesday; otherwise, the ship will have already left the port, so to speak.)

noahtalerman commented 2 months ago

Hey @spokanemac, @zayhanlon, and @nonpunctual this looks like a duplicate of the following issue:

Closing this one and moving over customer/prospect labels. Please feel free to re-open if that's not the case.

fleet-release commented 2 months ago

In the cloud city, Keys unlock updates' flow, Guiding Macs on time.