I find shell scripts to run faster and have less over head, and I know shell a lot better than I know apple script at the moment.Are you looking to uninstall MacPilot from your Mac? MacPilot is a popular utility tool for Mac that allows users to access hidden features and customize their system settings. It basically tells apple script to output a numerical result based on what it finds and then reads either 1 or 0 and then executes a command. # I used the dialog's status next just for test purposes.Įxit $ASerror # <- put whatever exit code you like instead # seems best to test for cancel click via exit code FIRST: Reply=$(2>/dev/null /usr/bin/osascript <<-AppleSkript ![]() # redirecting fd2 to dump AppleScript's error text when Cancel is clicked: # function to parse the string (1st arg is the full text, 2nd arg is the desired field): I had someone help me write this as I am not huge on apple script vocabulary at the moment.ĭeclare -x PATH=/bin:/usr/bin:/sbin:/usr/sbinĪSerror=1 # assumes worst case to err on the side of caution Nice script, I was doing the same thing but with a combo script of both shell and apple script. We see 4MB+ download speeds from Apple when updating. Once we get everyone patched and down to maybe two patches needed, we'll then cut over to using our JSS as the Apple Software Update Server. For this first round of getting everyone patched, we're having them pull down from Apple. We have smart groups in place and network segments laid out. We've done tests like this before with VPN software and have had fast results so we know we can push out something fast if need be. If a critical update comes out, we'll create a manual one off process to push out a zero day like scenario. We want to have our Macs check weekly for Apple updates and install. We're looking at getting patch compliance in place by Feb/March time frame. I like Self Service, but have no idea how to integrate into our virtual checkout system we have in place already for getting software internally. Self service is a service we already have created in house on our internal site. Usually when I encounter user computers, their uptime is more than a week, rebooting is never really on their mind. We encourage flexibility and working remotely if needed. All Macs are portables as their desktop computer. So maybe a background on our environment: I know, weird and not helpful.īut if anyone has had experience with this situation or knows more about this policy, please let me know. Oh we have had some users with machines that rebooted out of the blue, but they're not sure if they clicked the OK button or not. ![]() ![]() Does the time I specify (2 hours in this case) start when the window goes away? I guess a followup is, does the countdown timer actually begin when the user clicks ok, or when it appears? The policy setup page is a little fuzzy for me to know if this is what happens. The concern I have is that some users have reported that when a reboot is needed for one of the updates, the message I have set shows up, but when they move another window to the front, it disappears. So I've been adding 50 computers at a time to this policy, let them run it, and see what the logs say. Our network guys would notice this and question what's going on. ![]() The thing I want to avoid is having these machines all run the Apple software updates option at the same time. So we're beginning to roll out a policy that will gradually encompass all 900 Macs in our company. Just wondering if anyone else is seeing this problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |