Sharing is caring, so we'll share our best practices and tips for using Automox. Ask your questions to make the most of your Automox experience!
- 563 Topics
- 2,001 Replies
Hi, I am trying to install automox agent automatically using Puppet. Issue is I have no way to check if agent is registered properly on automox, so every time puppet agent is starting deregistration and registration again. I tried to use agent to show me a group that node belongs, but there is no way to do it. I looked at API doc but I do not see a way to pull to which group node belongs. Is there any way to check from node itself if agent is already registered or not?
I’m not sure if this is Automox related but our company keeps having a black screen issue. It looks like the update is downloaded and the server is looking a reboot but if we don’t reboot the server I’ll will just sit on a black screen and we can’t login to it- this is causing issues because some applications won’t run. In this situation we need to use nutanix to reset the servers and it does install the updates then.Have you heard about this issue before? What is the fix for it if a policy which is supposed to reboot servers over weekend doesn’t work?
When we first implemented Automox we created the suggested “Keep browsers up-to-date” policy available on the console’s front page. I recently saw this installed KB5030216 overnight on a few VMs with the policy applied. Has anyone else seen this behavior? Is this because “Everything Microsoft Edge” is included in the policy?
I started my computer up this morning and was prompted with an Automox popup saying that my computer was going to restart in 5 min. I was not given an option to defer. Normally we give two deferal options and allow the person to defer three times max. So Im wondering is, even though my computer was turned off, Automox took the automatic deferal options and now that my computer is on, is forcing me to reboot? Hopefully that makes sense. If that is the correct, how do you handle that? We dont want people turning on their computers, and getting prompted to have to reboot 5 min into their work day. Thank you, Greg
I have several Windows servers that the Automox agent reports and issue with the Windows update server.Connectivity to Patch Source:Windows Update ServerThere is no problem with using Windows Update locally on the server. I had to resort to using it locally to patch this server. I had opened a support case on this and was told to contact Microsoft support. This response made no sense and I told the engineer that. I'm supposed to contact MS support and tell them there is an problem with Windows Update working on a server when it is working as expected.
Hi,I apologize for my oversight in posting this question in the wrong category. I am uncertain about which category is most suitable for this query and whether it should be posed in the community section.If necessary, please feel free to relocate this post to the appropriate category, as I lack the capability to change the category myself. Thank you for your assistance.Greetings, everyone. I've noticed the presence of a recently introduced policy results report within the Automox console.https://help.automox.com/hc/en-us/articles/10402651969684-Policy-Results-Report#PolicyResultsReport-PolicyResultsOverviewI am currently exploring the feasibility of extracting data from the mentioned report through an API.Upon reviewing the available documentation, it appears that the API supports data retrieval primarily for attention reports and pre-patch reports.However, I would greatly appreciate your guidance if I have overlooked any relevant information or functionalities in this regard.Thanks.
Hi,We are looking for a way for Automox to be able to apply updates when a computer is shut down, like Windows Update does.We don’t know if with powershell (through a worklet) we could “tweak” the start menu so it looks like it does with Windows, with the options to “Shut down”, “Update and shut down” and so on.So we are wondering if this is something that someone else has struggled with, or if the Automox team has assessed this possibility. It would be a really convenient feature to have, so users are less bothered by the patching process, but we understand it´s a complicated issue.Do you have any idea if this is poossible through a worklet? How would you start developing it?Thanks!
Hi, We are had a problem when during installation user closed laptop lid what put PC in suspension.As Bitlocker encryption was already suspended and keys were deleted. User blocked his laptop wrongly entering passwords. . We can’t login into laptop. We have keys but they are not correct anymore. Can we disable that action so encryption never would be disabled. Cheers Michal
I’m curious if anyone else has run into this and has a solution. The device details page remains blank on 1% of agents ~765 total workstations.Running locally: Get-WmiObject Win32_ComputerSystem shows error “get-wmiobject : Invalid class "Win32_ComputerSystem" winmgmt /verifyrepository shows WMI repository is consistent
We have been playing around with the remote control feature in Automox but have noticed some stability issues where it will disconnect the remote session once or a couple of times before the remote session is finally stable and doesn’t disconnect. We do not have any firewall configuration that would cause an issue with this and the people we have supported tend to have good connection, many of them being on prem. Has anyone else run into similar issues?
I have 4 CentOS 7 servers which are acting as app connectors for Zscaler Private Access. I wanted to install automox on them so the underlying OS can be patched along with our regular patching schedule. The installation worked fine but then the agent lost connection to the console. I am trying to reinstall the agent according to the instructions here: https://help.automox.com/hc/en-us/articles/5384334313108 I have already removed the boxes from the console but since the server isnt communicating with the console, it doesnt appear to be removing the agent. When i run the cmdsudo /opt/amagent/amagent --deregister I get the following error:/opt/amagent/amagent: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /opt/amagent/amagent) From what i can find, it seems that CentOS7 only supports GLIBC_2.17, but automox indicates that CentOS7 is a supported OS: https://help.automox.com/hc/en-us/articles/5352186282644-Supported-Operating-Systems Any help would be appreciated.
Hi, My name is Paul and we have been using Automox for over 2 years now. We patch 450+ servers (mix of virtual servers 2016/2019 OS)located in the US, once on a monthly basis. Our US patch windows commonly exceed 5 hours to finish patching all servers. We also patch about 100 servers in the Asia Pacific region, once monthly, and this patch window takes 4+ hours to complete. Wondering if this community can help in justifying if this aligns with their patch window duration. How long are your monthly patch windows taking to complete?How many servers are you patching during these windows? Do you have a mix of virtual servers 2016/2019 OS?How much bandwidth is your pipe your servers use to get out to the internet? Are you pre-staging (downloading the KB’s ahead of time) prior to the start of the actual patch window?
I know this has been a topic for some time, and currently my understanding is that Automox can generate some email alerts, but we want to have more focused alerting integrated with our ITSM system.We’re currently working on hitting the API to create tickets for things likeDetecting endpoints that have not been connected for X number of days Detecting endpoints that are unmanaged and need to be assigned a policy Detecting policies that have been out of X% compliance for Y number of days Some of this can get quite complex as we have to take the X number of days logic outside Automox and therefore have a method of tracking this. For example if a bunch of new updates are released we wouldn’t want to alert immediately on a policy being out of compliance, therefore we want to have some level of delay, while still picking up issues where remediation actions may need to be taken to bring a policy back into compliance. As a managed service provider, going through dashboard to see this isn’t an
We have 450+ servers (mix of virtual servers 2016/2019 OS)located in the US, and our patch windows have commonly exceeded 5+ hours to complete. We patch these on a monthly basis. Each month, we also have to manually patch about 30-70 servers manually by RDP. How long are your monthly patch windows taking to complete? How many servers are you patching during these windows? Do you have a mix of virtual servers 2016/2019 OS? How much bandwidth is your pipe your servers use to get out to the internet? Are you pre-staging (downloading the KB’s ahead of time) prior to the start of the actual patch window? In a previous month, we finally found out that we should ignore Beyond_Compare and KB890830 to prevent the update from delaying other items in the manifest. Still having long windows, regardless of the ignoring of certain apps/KB’s - but we need help to figure out if its in our environment (network, servers, internet, etc).
I have a couple of computers stuck in bad states on the console, one in Rebooting and another in Refreshing.I have tried uninstalling the agents, but that is not helping…. When they get readded they are right back to their bad state again. Is there anything else i can do?
Hi, We’re running into an issue when some of our clients just stop communicating with Automox. I can see that the status of the agent is loaded but it fails to start. The only solution i’ve found is to remove the agent and reinstall, not ideal. has anyone else experienced this?
Is it possible to change this UX? We are starting to roll out, and our users and reporting that this popup looks fake (like a spammy “Windows update centre” popup). Potentially if we could replace the green shield with our logo, or just remove it completely that would be better.
I’m currently testing things out on a Trial version, so it’s possible I guess that it’s causing my issue.On the Devices tab I’m check boxing a few devices, then going to Actions → Apply TagsAfter completing it I get a green box that says “1 tag is being applied to # devices. It may take a few minutes to complete.” Unfortunately it never completes the tagging though.
Hi everyone, Will there be any built-in support for dynamic group assignments coming to the product? For example, MS Azure has built-in features where depending on the OS, the device auto-populates itself in an assigned group upon discovery. We are a SMB running 90% on MAC, and our IT team is relatively small. They sometimes forget to log on the console and move a device from the default group to our custom groups which have specific patching policies applied to them. I think this is a feature that would greatly improve qualify of life. No one likes manual tasks! I think the core principle of the product is a cloud-based hands-off solution. I do read “Auto” in Automox! 🙂 Thank you!
Usage question here and potentially a feature request if it’s not available.Is there a way to filter the Software page to exclude software with an ‘Impacted’ value of zero? It would be a handy way to cut down the noise in reviewing software yet to be patched. Helps identify gaps or troublesome patching areas quickly.
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.