Patching Third-Party Applications - Tips & Tricks
Patching Cyberduck on Windows
Cyberduck has a version limitation on 32-bit installs. The latest 32-bit version is 7.0.2. Automox will patch to that version if a 32-bit install exists. Automox will not install newer 32-bit versions because of a vendor behavior that we cannot change or control. 64-bit versions will be updated to the latest available version of Cyberduck.
Patching File Sync Applications on Automox (Box Drive, Dropbox)
This describes the behavior when patching file sync applications, such as Dropbox and Box Drive, through Automox.
Even if a file sync app has been shutdown, it might relaunch after an update. This is a vendor behavior that we cannot control or change. If the app is open during the patch, Automox will relaunch it.
The behavior described here applies to the following file sync apps supported by Automox:
- Dropbox
- Box Drive
Oracle SE Java 8 Support Shift and How It Impacts Automox Users
Effective immediately, Automox is no longer able to support patching for Oracle SE Java 8.
Many third-party software providers have EULAs (End User License Agreements) that prevent patching solutions from directly redistributing patches or software updates. Recently, Oracle’s Java SE 8 went through the “End of Public Updates” process for legacy releases. Patches can vary by system architecture and platform, but the fundamentals remain the same.
What this means for Automox users is that Automox will no longer be able to enable third-party application patching for Oracle SE Java 8 without violating the EULA from Oracle. Customers currently reliant on Automox to help automate this process will need to adopt a new approach to patch Java 8 moving forward. This process is detailed here as well as in a community post on the Automox Alive Community.
Automox can still help to automate patching of third-party applications like Java 8 on your terms through Automox Worklets.
How to Update Oracle SE Java 8 Software
Oracle SE Java 8 requires a login to the Oracle support portal and the acceptance of the Oracle EULA. The patch is then available for download and can be uploaded to the Automox console for distribution.
The key actions for adding third-party patches into the Automox console are as follows:
Obtain the patch through manual download of the “offline” install file or through a Worklet
Review all required third-party EULA terms and conditions ensuring alignment with your company policies and legal charter. Manually download the patch or leverage Automox Worklets to automate the process altogether.
Upload the patch to the Automox console
By uploading the file to the Automox console, the patch is added to the ecosystem for your organizational use. This step ensures that devices are able to obtain the required patch from the Automox console. Make adjustments to policies (if necessary).
Make any necessary adjustments to policies in applying the patch to devices in scope. This might mean altering the installation syntax if command line parameters have changed. If no existing required software policy exists for the patch, create a new one and add the name, version, and installation script syntax.
Patching Skype on Windows and macOS
The Skype application will only be patched when it is not in use.
You might see that a patch for Skype will fail if the application is being used during the patch window for Skype. Automox will show that a patch is available pending. The patch will be updated the next time the policy runs if the application is not in use. Because updates to the Skype application require a restart, the operation can only be successful when Skype is closed and does not appear in the system tray.
Patching Skype from the Software page
To view a scheduled patch, you can go to the Software Page and search for Skype. When a version of Skype listed has a patch available, it will list a number under Impacted Devices. If you are not using the application, you can immediately patch by clicking Actions → Patch Now. Confirm your selection.
Patching Skype from the Device Details page
You can also view scheduled patches from the Software section of the Device Details page. The patch for Skype will show as Update Available. If you are not using the Skype application, from here you can decide to immediately apply the patch. From the Bulk Actions menu, select Patch. Additionally, you can navigate to the Overview Report and it will reflect the pending patch in the list of Available.
Creating a Patch Policy for Skype
You can decide to patch Skype with a separate policy that focuses on the patch schedule. Your workflow and use of Skype will determine how you schedule the update and how you notify users.
You can set up a Patch Only policy, filter for the appropriate patch, and schedule it to be applied outside of working hours. For the basics of creating a policy, see the following articles:
When you schedule this policy as desired, you can create a message to inform your users that Skype updates only occur outside of the use of the application and therefore it is possible the patch could occur upon restarting the device.
For additional help, please submit a support request through the customer portal.