@BigMacAdmin commented on GitHub:
Because Installomator passes all arguments through eval , any argument that contains whitespace needs to be both quoted and escaped.
As you confirmed on…
@asri-tm commented on GitHub:
i am able to install just fine with 10.6beta, would be helpful with some logs to pinpoint what has failed
@asri-tm commented on GitHub:
Apologies, I should've lead with that. Upon further troubleshooting, I realized the download was being blocked by Zscaler which of course should be fixed from my…
@Artos254 commented on GitHub:
Apologies, I should've lead with that. Upon further troubleshooting, I realized the download was being blocked by Zscaler which of course should be fixed from my…
@Artos254 commented on GitHub:
I was using the wrong script... /facepalm. I'll just see myself out.
@AymenAbb commented on GitHub:
There's 2 ways of doing that, best way imo you replace the problematic code which is in googlechromepkg.sh. The other is going with custom parameters but that's a…
@acodega commented on GitHub:
Believe this is fixed in Installomator 10.6
@karsondude97 commented on GitHub:
jamfconnect) name="Jamf Connect" type="pkgInDmg" packageID="com.jamf.connect" appNewVersion=$(getJSONValue "$(curl -s "https://learn-be.jamf.…
@tbcahill commented on GitHub:
Thanks for confirming, would you have any guidance for how to tell installomator to use Google API instead of Omaha proxy, do I need to to create my own version of…
@acodega commented on GitHub:
Believe fixed in Installomator 10.6
@alexandernezis commented on GitHub:
You can reference the changes here that will help: https://github.com/Installomator/Installomator/pull/1366
Omaha proxy is dead, so switching to Google API…