Hi,
Anytips for the 10.13.4 installer / combo installer .pkg 's through Self Service?
Jamf's position (at least when we open tickets about Combo Updates not getting past auth restart) has been to push the Full Installer.
It works.
@donmontalvo So you download the full 10.13.x installer from the App Store and push that instead of an update? That would at least lower the number of packages I would need.
Proxy?
https://support.apple.com/en-us/HT207567
This documentation highlights a few hostnames that need to be whitelisted through corporate proxies although in my testing there also some additional hostnames that also need to be added.
I ended up here because I'm trying to troubleshoot an issue installing High Sierra Security Update 2019-001 on some T2-equipped MacBook Pros which shipped with High Sierra and cannot migrate yet to Mojave... "packagewithpath returned nil" appears to be the start of my troubles but they continue with the likes of:
SoftwareUpdate: request for status for unknown product _ManualUpdate
bridgeOS prepare summary... "An error occurred during preflight."... NSUnderlyingError=0x7fe757ca0e10 {Error Domain=BridgeOSSoftwareUpdateError Code=19 "MSU - 2 (Failed to personalize with options.);MSU - 2 (Could not personalize boot/firmware bundle.);AMAI - 3099
SUBridgeOSUpdateManager repeats that...
SoftwareUpdate: Error preparing bridgeOS update for manual product at /var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate/localhost/AdoptedManual/SecUpd2019-001HighSierra.pkg
softwareupdated[#]: Manual product is nil, therefore an error occured, stashing token will NOT be created...
installer[#]: ManualAdoption: Error adopting /Library/Application Support/JAMF/Waiting Room/SecUpd2019-001HighSierra.pkg: Error Domain=SUErrorDomain Code=602 "An error occurred installing the update."
I'm reading far too many similar threads from far too many users having similar sounding issues without clear resolution.
While I understand Apple's made a determination to expect full connectivity to and every device downloading updates from their 17.0.0.0/8 network, it's discouraging that they don't recognize the reality of restrictions (bandwidth and networks) where this isn't possible and updates need to be reliably deployable in multiple ways with well documented solutions and troubleshooting.
In the meanwhile perhaps the comment about finding and disabling all proxying will help someone else:
https://discussions.apple.com/thread/8477051?page=2
