@scriptingosx commented on GitHub:
Additional it would be great if it will check if an application is already installed and skip them.
Installomator and Jamf App Installers already do this.…
@ooftee commented on GitHub:
+1 on the Sucessfull/Failed check at the end and a possibility to start over. We have users in asia with not so reliable home internet and a retry would be much…
@scriptingosx commented on GitHub:
related Network outage handling: #15
@ooftee commented on GitHub:
Most of our fails are due to network, so this is how we check for network connectivity right now, it would be nice to have something similar built in:
#!/bin/bash…
@scriptingosx commented on GitHub:
implemented in 1.3, you will have to hold the option key when clicking "About this Mac" to see the MDM server. You should also see it in the Network info panel…
@scriptingosx commented on GitHub:
could you specify "various settings are configured"? what kind of "various settings" are you specifically interested in?
@scriptingosx commented on GitHub:
note that you can currently achieve this with custom policy/script that works on the finishedTrigger or finishedScript but I understand the request for…
@master-vodawagner commented on GitHub:
Yes those things should be continually checked in MDM, it’s still useful IMO to show those items are configured and/or enabled for the user.
FV2 could…
@phillscholl commented on GitHub:
I would love this too:
It would be great if it will deliver an Overview of all Steps (Sucessfull/Failed) at the end and a possibility to start over. Additional…
@fraserhess commented on GitHub:
12458 bytes seems to be the important limit.
Testing results: 1.3 beta with 1.3 configuration (finalAction: none; finishedTrigger): log truncated at 12458…