Using Automox

I am still very new to Powershell and using Automox with Powershell and was wondering what would be needed to create a worklet that would create a start-up item. This is for a Papercut printing client that is run from a network share. I would mean avoiding a mass manual install so would be very useful! Sorry if this is not the right place for this. Thanks!

Enhancements Added support for SLES 15. Added support for Fedora 30 and 31. Bug Fixes Fixed a bug on SLES12 where partitions were listed multiple times on the Devices page. Fixed a bug on SLES where the installed packages table contained invalid data. Fixed an issue where the 2FA image would not appear in Settings Security page. Fixed an issue where editing a policy and hitting back button in a browser redirected the user to an incorrect URL. https://support.automox.com/help/archive-release-notes-2020

Well some of us are. We’ve grown so fast that we’ve run out of space in our current offices and are opening a satellite office down the street. All of us in sales and marketing will be moving to the new office over the weekend and are busy packing up our stuff today: IMG_31654032×3024 2.98 MB

Enhancements macOS background updates are now manageable with auto patch controls disabled. Bug Fixes Fixed macOS auto patch controls for macOS 10.14 and 10.15 Fixed an issue that was showing the incorrect time in the Activity log. https://support.automox.com/help/archive-release-notes-2020 Relevant KB: https://support.automox.com/help/what-are-macos-background-updates

To make it easier to copy code from worklets into your console, I’ve added a copy to clipboard button that shows up on code blocks. If you’re not seeing it yet then do a full reload of the community page to refresh. You should now see this on all code blocks: Screen Shot 2020-01-23 at 10.20.23 AM720×276 23.7 KB

I wanted to take the pulse of the community on our email frequency. I get too many emails from Automox I get just the right amount of email from Automox I would like more frequent emails from Automox 0 voters

Bug Fixes Fixed a bug that created false alarms for Microsoft Remote Desktop Importer. Fixed an issue where Office for Mac may not show pending updates. Improved the functionality that prevents a browser’s autofill from filling out options on the Group and Policy creation pages. https://support.automox.com/help/archive-release-notes-2020

Has anyone ever used Kaseya to deploy Automox agents in bulk? How do you add the access key automatically for all servers/workstations?

…and why is it Windows ME?

Is there any sort of update on when the reboot notifications will be improved upon? The current worklet solution still only works if the user is sitting at their desk to see it. Preferably (IMHO), a notification would appear and not go away until they click ok to allow rebooting. I think this is how SCCM works. Without having something like this, it leaves much room for users not being made aware of the pending reboot. Thank you

Enhancements Updated the Dashboard’s “Up to Date” percentage calculation to have significant figures for larger organizations. Updated the counts on the Dashboard’s widgets (Manual Approval, Pending Updates, Needs Attention, and Exceptions) to not exceed the width of the widget. For organizations with counts above 1 million, we will display 999,999+. Updated the display and editing format for dates throughout the console to be YYYY-MM-DD. Add Devices modal updated to fully match the Dark Mode version of the console’s design. The Promotional Code in the Billing area will only display for new Manage subscriptions. Improved the Billing area to include more details for customers not paying with a credit card. Improved the display of the “Filter By Group” pulldown in the Edit Policy page. Improved Settings Security page to look better at smaller browser window sizes. Bug Fixes Fixed an issue in the Device Details page when sorting policies by “Next Patch Window” so that it will sort corr

With yesterday’s release we added those three titles: https://support.automox.com/help/archive-release-notes-2020 If you’re on a Patch All policy, know that now Skype, Notepad++ and RDP for Mac will now automatically be included. If you need to exclude any of those software titles for any reason, you can use a Patch All Except policy and exclude patches that way. Note: if Skype or Notepad++ are in use at the time the patch policy attempts to install a patch, it will fail and attempt again next time the policy runs. This is to avoid interruption to Skype calls, or data loss from Notepad++ which doesn’t automatically save changes on exit (although there are settings you can change to make it do so: https://stackoverflow.com/questions/24447786/notepad-doesnt-save-document-on-exit) New applicable KB articles: https://support.automox.com/help/patching-skype-on-windows-and-macos https://support.automox.com/help/patching-notepad-on-windows Updated list of all 3rd party titles: https://docs.

Enhancements If a device is disconnected in the Edit Group page, the tooltip will now show the disconnect date and time. Added the ability to provide updates for Microsoft Remote Desktop Client in MacOS (MacOS Only). Added the ability to provide updates for Skype on MacOS and Windows. An Application Restart is required for the patch to take effect. Added the ability to provide updates for Notepad++ in Windows (Windows Only). An Application Restart is required for the patch to take effect. Updated the Software page to display an OS Version column that will include the OS and OS Version of the shown package. Bug Fixes Fixed an issue for Windows 10 devices that could prevent forced reboots from executing after a feature update. Fixed an issue in the Patches Applied - History section of the Overview report that was not displaying accurate counts for patches identified as critical and none. https://support.automox.com/help/archive-release-notes-2020

We have separate groups and policies for each of our main linux distributions. The policies are a manual approval policy so we can strictly control and report on what servers are patched with what and when new servers are brought on, we can force a patch down and know it will be at the same level as the others. That being said, is there an easy way to approve all patches in a manual policy? I looked in the API and I am not seeing a way to easily do this and there isn’t a way to do it in the portal either. Basically our end goal is to control patching so all are on the same versions for specific groups.

Hi all, following the recent announcement regarding CVE-2020-0601, one of our clients has requested a report on all our systems identifying which devices are vulnerable. Is it possible to generate such a report from Automox yet? That would be awesome!

Windows 7 is going end of life on Jan 14, 2020, so you’ve got a little over a month to upgrade those last few machines in your company. Automox will continue to patch your Windows 7 third party software and support the agent on Windows 7, but Microsoft will only release Windows 7 OS & security patches for those of you who purchase very expensive extended support. Here’s their FAQ on the subject: https://support.microsoft.com/en-us/help/4057281/windows-7-support-will-end-on-january-14-2020 If you need help finding those last few Windows 7 boxes, you can use Automox to help track them down by sorting by OS Version on the Devices page. Note that with the 11/27/19 release, we now sort the entire data set and not page by page, which makes this process easier. How many of you still have machines left to upgrade, and if so, how many? image1079×748 131 KB

Bug Fixes Fixed a bug that improves the performance of Policy queries at scale. Fixed a bug that when using characters in a group name, the name is now displayed correctly in the Device Details page. Fixed a bug where the console would incorrectly show that the customer’s trial has expired when it actually had not. https://support.automox.com/help/archive-release-notes-2020

What are your favorite books, website and tutorials for learning how to write scripts? I’m always a big fan of the O’Reilly books: O’Reilly Online Learning Windows PowerShell Pocket Reference, 2nd Edition This portable reference to Windows PowerShell 3.0 summarizes the command shell and scripting language, and provides a concise reference to the many tasks that make PowerShell so useful. If you’re … - Selection from Windows PowerShell Pocket... Post links to your favorites!

TechCrunch Insight Partners acquires data management company Veeam for $5B – TechCrunch Last year Insight Partners invested $500 million in cloud data management company Veeam. It apparently liked the company so much that today it announced it has acquired the Swiss startup for $5 billion. Veeam helps customers with cloud data backup... Who here uses them for backup?

Bug Fixes Fixed a bug where the NonCompliance and Patch Reports were not loading for some customers. https://support.automox.com/help/archive-release-notes-2020

This User Guide walks you through the different ways you can slice and dice the data: https://docs.automox.com/home/devices/searching-sorting-and-filtering-device-information The full list of statuses that you can put in are: Device Status: Compliant Device Status: Up-To-Date Device Status: Non-Compliant Device Status: Pending Device Status: Connected Device Status: Disconnected Device Status: Needs Attention Device Status: Exception Patch Status: Missing Package Status: Installed Package Status: Not Installed Recently Added Windows Linux Mac In addition you can filter by any group or policy that you’ve created. Combine multiple factors to narrow down your search to exactly the device or devices you’re looking for.

Zoom client updates require the application to restart. Using a separate patch policy will eliminate inconvenient restarts.https://support.automox.com/help/third-party-software-patching-zoom-on-windows

If you go to the Software page in the console, and click on any of the severity links, it will show you the CVE(s) relevant to that particular patch. Clicking on the CVE links will take you to the Mitre page: Screen Shot 2020-01-09 at 10.10.50 AM757×461 26.9 KB

Enhancements Support ‘Safe Patching’ in Zoom. Patches will be skipped if a meeting is in progress. Does not support Zoom on MacOS before 4.4.2. Improved the Activity Log design including localizing the event time for users, show/hide ability for long event details, and specifying the Event Type (error/activity). Bug Fixes On the Devices page, increased size of the the Assign to Group modal’s group pulldown to improve usage. Fixed a bug causing unexpected behavior in Remediate Now policy execution on the System Management page. Fixed a bug causing some users to experience prompts for 2FA codes even though 2FA was not configured. https://support.automox.com/help/archive-release-notes-2020