Closed yl10401ee closed 1 year ago
Hello, try to firstly update to the latest Monterey release (12.6.3) and then to the latest public build of Ventura (13.2.1). It should not be necessary to provide the script the macOS full installer (at least for the first step). The script should fully manage the download and installation procedure.
Regards
Also check the API URL you are providing in the variables section. It should have nothing after .com, here is an example of what it should look like:
Hello, I just wanted to acknowledge that after updating to 12.6.3 I was able to pull the download with the script. However still getting the same response when initiating the install. I then changed the API URL as you mentioned above with nothing after .com, but this stopped the script from working entirely. Just to note: my apiURL had https://*****.awmdm.com/api as the rest api listed in my settings. Not sure what I could try next, but thank you for responding.
Yes make sure the URL does not have the '/api' in it as that will lead to the 404 errors you were receiving. Are you on MacAdmins slack?
No I'm currently not in MacAdmins slack. Looks like I'll have to get an invitation to it.
Feel free to DM me on there or send me an email at mzaske@vmware.com and I can try to help troubleshoot.
@yl10401ee Sign up here for the MacAdmins Slack
Describe the bug
Hello, I'm having some trouble getting the MUU script working. Some context: followed every step in applying this script in Workspace One. Everything works fine up until an install has been triggered for an update and the API response is something I don't understand. See below the macOSupdater.log
Any help would be much appreciated!
Reproduction steps
1.Ensured correct steps in applying ClientID, ClientSec, Rest API URL and Token URL 2.Installer in correct path: /Applications/Install macOS Ventura.app 3. ...
Expected behavior
End user able to see the prompt to defer update or to being. After deferring twice, chose to begin the upgrade. Was expecting the install to happen immediately and follow with a reboot but nothing happened.
Additional context
The installer is downloaded via workspace one internal application, because when the script tried to download the installer (after checking that it didn't exist) I came up with the same error as detailed in the image attached. So once I pushed out the download for the installer, the script recognized the download. My only problem is when the upgrade gets triggered to begin, nothing happens.