Disable updates (macOS) just gonna leave this here...
Moderator: Project members
- donmontalvo
- 504 Command not implemented
- Posts: 10
- Joined: 2010-02-15 17:35
- First name: Don
- Last name: Montalvo
Disable updates (macOS) just gonna leave this here...
https://www.jamf.com/jamf-nation/discussions/28929/suppressing-filezilla-3-35-1
Re: Disable updates (macOS) just gonna leave this here...
This is dangerous advise.
Updates are a good thing, do not disable them.
Updates are a good thing, do not disable them.
- donmontalvo
- 504 Command not implemented
- Posts: 10
- Joined: 2010-02-15 17:35
- First name: Don
- Last name: Montalvo
Re: Disable updates (macOS) just gonna leave this here...
(removing, please see my next post)
Last edited by donmontalvo on 2018-08-05 16:41, edited 1 time in total.
Re: Disable updates (macOS) just gonna leave this here...
Updates aren't forced. Maybe they should though, users of outdated versions waste my time.
That said, the proper way to preconfigure the client is through fzdefaults.xml, never touch the user's configuration.
Last but not least, editing XML with regular expressions? I'm sure Perl has proper XML modules.
That said, the proper way to preconfigure the client is through fzdefaults.xml, never touch the user's configuration.
Last but not least, editing XML with regular expressions? I'm sure Perl has proper XML modules.
- donmontalvo
- 504 Command not implemented
- Posts: 10
- Joined: 2010-02-15 17:35
- First name: Don
- Last name: Montalvo
Re: Disable updates (macOS) just gonna leave this here...
Agreed 100%. In enterprise we disable updates only so updates can be vetted and deployed.
If an enterprise user opens a ticket about an issue, after initial troubleshooting the ticket is routed to us and we vet/deploy the latest update.
Other times we get a ticket from security with a CVS, and a deadline to get the latest version deployed.
Enterprise users shouldn't ever contact the developer, but we can't force them to not use existing forums.
Thanks for the https://wiki.filezilla-project.org/Fzdefaults.xml link.That said, the proper way to preconfigure the client is through fzdefaults.xml, never touch the user's configuration.
I updated the Jamf Nation post to show enterprise admins can put this code in "/Applications/FileZilla.app/Contents/SharedSupport/fzdefaults.xml".
Code: Select all
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<FileZilla3>
<Settings>
<Setting name="Disable update check">1</Setting>
</Settings>
</FileZilla3>
Yeap, I opened a ticket with Apple Enterprise Support to get their recommendation on a good XML command line tool, since it's slim pickings on the macOS side.Last but not least, editing XML with regular expressions? I'm sure Perl has proper XML modules.
Thanks,
Don
- donmontalvo
- 504 Command not implemented
- Posts: 10
- Joined: 2010-02-15 17:35
- First name: Don
- Last name: Montalvo
Re: Disable updates (macOS) just gonna leave this here...
Lazy Sunday...this might help folks tasked with deploying to macOS users in enterprise environments...HTH:
Code: Select all
#!/bin/sh
#
# Run this script with using sudo. 20180805 DM
sourceFile="FileZilla_latest_macosx-x86.app.tar.bz2"
downloadUrl="https://download.filezilla-project.org/client/${sourceFile}"
appPath="/Applications/FileZilla.app"
# Set pwd
currentDir=$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )
cd ${currentDir}
# Download source archive
curl --location --remote-name ${downloadUrl}
# Decompress source archive
tar xvjf ${sourceFile}
# Disable updates
cat <<'EOF' > FileZilla.app/Contents/SharedSupport/fzdefaults.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<FileZilla3>
<Settings>
<Setting name="Disable update check">1</Setting>
</Settings>
</FileZilla3>
EOF
# Set ownership and permissions
chown -R root:admin FileZilla.app
chmod 644 FileZilla.app/Contents/SharedSupport/fzdefaults.xml
# Replace old app with new app
if [[ -e ${appPath} ]]; then
rm -Rf ${appPath}
fi
ditto FileZilla.app ${appPath}
# Create deployable flat package
versionString=$( defaults read "${appPath}"/Contents/Info CFBundleShortVersionString )
pkgbuild --install-location /Applications --component "${appPath}" FileZilla3_"${versionString}".pkg
exit 0
Last edited by donmontalvo on 2018-08-06 03:51, edited 4 times in total.
Re: Disable updates (macOS) just gonna leave this here...
Looking good, other than the hard-coding of a specific mirror that may or may not exist in the future.
Please use download.filezilla-project.org as hostname.
Please use download.filezilla-project.org as hostname.
Re: Disable updates (macOS) just gonna leave this here...
Oh, and make sure curl follows redirects with -L
- donmontalvo
- 504 Command not implemented
- Posts: 10
- Joined: 2010-02-15 17:35
- First name: Don
- Last name: Montalvo
Re: Disable updates (macOS) just gonna leave this here...
Done! Updated the script comments too.
- donmontalvo
- 504 Command not implemented
- Posts: 10
- Joined: 2010-02-15 17:35
- First name: Don
- Last name: Montalvo
Re: Disable updates (macOS) just gonna leave this here...
Curious, would you have a URL that points to the latest version, so the script can run without first having to set $sourceArchive when a new version is released?
UPDATE: Answered my own question: https://download.filezilla-project.org/ ... pp.tar.bz2
UPDATE: Answered my own question: https://download.filezilla-project.org/ ... pp.tar.bz2
- donmontalvo
- 504 Command not implemented
- Posts: 10
- Joined: 2010-02-15 17:35
- First name: Don
- Last name: Montalvo
Re: Disable updates (macOS) just gonna leave this here...
OK, so the "Updates" menu is disabled, but users are getting prompted...so our Help Desk is getting calls...how do we totally disable updates checking?
- Attachments
-
- 2018-09-20 at 08.41.07.jpg (75.55 KiB) Viewed 1893 times
- donmontalvo
- 504 Command not implemented
- Posts: 10
- Joined: 2010-02-15 17:35
- First name: Don
- Last name: Montalvo