mirror of
https://github.com/jamf/Setup-Manager.git
synced 2026-02-03 14:13:24 +00:00
Jamf Setup Manager Suggestions #51
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @K10DK on GitHub.
Hi there,
Following on from JNL 2025, I have a few suggestions I'd like to share regarding Jamf Setup Manager:
Suggestion 1: Just after the welcome screen for Jamf Setup Manager is displayed, a network check is carried out to confirm if the Mac that is being enrolled into any Jamf Pro instance is connected to a restricted network (trains, hotels, airports, public spaces) in order to stop failed enrolments in occurring?
Suggestion 2: The option to have concurrent downloads take place based on application priority, for example:
Microsoft Word, Excel and Powerpoint having a priority of 9 whilst Audacity and / or TextMate having a priority of 5?
Suggestion 3: The ability for Jamf Setup Manager to utilise Caching Server to reduce the overall network utilisation and enrolment process - I realise this suggestion "takes two to tango" therefore a suggestion to Apple via feedback has now been submitted.
@scriptingosx commented on GitHub:
👋I appreciate your comments (and our discussion at JNL). I enjoyed your enthusiasm.
A few comments:
I don't believe this is technically possible. Even if we could identify a network with a capture portal over another one, not all problematic networks have a capture portal, and I know of several organizations that intentionally tell users to enroll on their org's guest wifi (which often has a capture portal) to avoid network restrictions
We (the team working on Setup Manager) cannot change how Jamf policies or Jamf App Installers work. Please take this feedback to the main Jamf feedback your Sales Rep, SE or Customer Success Manager
Setup Manager does not download and install directly. It tells Installomator to run (which downloads directly from the vendor/developer server), a policy to run (which downloads from the distribution point, which could have a local mirror). Alternatively it can wait for Mac App Store/VPP apps (Apple's Servers, will use a Apple caching server if present) or Jamf App Installer apps (Jamf CDN)
If you mostly rely on Mac App Store/VPP apps a caching server will be respected. If you mostly rely on policies for installations, a local distribution point can be configured.
Installomator is not designed with local caching in mind and never will be. You could override the
downloadURLto a local server, but that takes a lot of preparation.If you want a caching server for Jamf App Installers, please provide feedback.
@K10DK commented on GitHub:
Hi there,
Sorry for the late response.
No problem at all, I'll reach out to our Jamf rep and feedback feedback number 2, with regards to feedback 3, I've already sent feedback to Apple on the whim that they may able to assist in future revisions, one can only hope!
Thank you for your time and patience here and at JNL, it was great speaking to you.
Kind regards,
K10DK