-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MDM workflow not working for me #21
Comments
Robert, It's not accurate to only look for "COMPLETE" as there are many instances of that during an update where it's not fully complete. For example, check out this update.log. There are roughly 10 instances of "COMPLETE", but they clearly do not indicate the process is done. Only when the log generates a "COMPLETED" are we for sure at the end of the process. To that end, perhaps I can choose something more clear for the download stage like "(end): phase:PREPARED stalled:NO" and for the install phase like "(end): phase:PREPARED_COMMITTING_STASH stalled:NO" Kevin |
Hi Kevin. I checked everything again. There is a state COMPLETED now in my logs. Earlier whenever I tried to run super local or deployed via Jamf there was never a state like that. I will check it again. So changes are not necessary at the moment. My bad. Kind regards, Robert |
This should be resolved with |
Hello,
I'm Robert.
First: The script is amazing. Thanks you very much for that.
Second: I tried it out with MDM workflow. Unfortunately it did not work for me. That's why I read through the whole script and I think I found a small mistake. In line 2517 the script checks the update.log for phase "COMPLETED" but in the log there is phase "COMPLETED". But there is a phase "COMPLETE". I think this is the reason why the script is not working for me.
I changed it in the script and now it works. Can you please update it?
Thanks in advance.
Kind regards,
Robert
The text was updated successfully, but these errors were encountered: