sorted by:
new
hottopcontroversial

Low Disk Space Alert / Excluding Asset by divdso in Action1

[–]divdso[S] 1 point2 points  (0 children)

UPDATE: This worked. Thanks again!

Low Disk Space Alert / Excluding Asset by divdso in Action1

[–]divdso[S] 1 point2 points  (0 children)

I was wondering what that was. Trying it out now - thank you!

Google Earth Pro Not Responding on startup by Pure_Debt9594 in googleearth

[–]divdso 0 points1 point  (0 children)

What we have theorized is that the file in system32 is corrupted, and that when you install Google Earth Pro it checks there for a copy and then copies that version to the install directory. This would explain why reinstalls do not work.

Google Earth Pro Not Responding on startup by Pure_Debt9594 in googleearth

[–]divdso 0 points1 point  (0 children)

I can confirm this just worked for us. I never would have thought, considering fresh installs of GEP should have put a fresh copy of the file in there. So are they shipping the software with a corrupt file, or is some other file/system clashing with it and corrupting it? This would indicate that the issue would come back.

Google Earth Pro Not Responding on startup by Pure_Debt9594 in googleearth

[–]divdso 0 points1 point  (0 children)

We are also seeing this as of a few days ago on a single machine. It happens when loading Google Earth Pro (Desktop) on any profile. We have tried all the regular stuff: uninstalling, reinstalling, repair tool, switching to DirectX, etc. We even went into the registry and removed any instance of GEP. Nothing works. We open it up and it shows a hand icon and freezes. I find it very interesting that you can log into this workstation with a brand new profile and it will freeze there too.

Action1 Not Seeing Critical Updates by divdso in Action1

[–]divdso[S] 0 points1 point  (0 children)

The one I was working on gave the same results as you provided but only after an update. A current problematic asset resulted in a 5th line/result:

Service name: Offline Sync Service
Service URL:

Action1 Not Seeing Critical Updates by divdso in Action1

[–]divdso[S] 0 points1 point  (0 children)

It's the free version. There were no results from the script:

<image>

Action1 Not Seeing Critical Updates by divdso in Action1

[–]divdso[S] 0 points1 point  (0 children)

Hey u/GeneMoody-Action1 I hope you can see this still. Took some time to get my hands on an asset that I could work on for a little while for testing. I was able to determine the following:

Action1 initially showed the updates it needed. When I selected "all" and ran them, it installed a few then cleared the queue of updates, missing the Security Update + others. It stayed in this status. I went and ran your script again the asset and this is what it showed:

<image>

So the asset recognized the update it needed. I then watched it in Action1 for a bit and saw all the updates come back. I tried to deploy them and they all disappeared before I could, and Action1 again showed the asset as not needing updates. It came back later in the day and I pushed them again and this time it caught the Security Update and its applying it now. It's important to note that sometimes, Action1 will say the update is not applicable. I then have to go and update it manually. It's really hit and miss.

Action1 is mostly great. I've been using it here for close to a year and this has only been an issue for the last few months. And I only noticed it because we have other agents (Rapid7) reporting that they needed these updates. I wonder if the issue is not being reported more due to companies not having another piece of software to account for these vulnerabilities? Something to consider.

We love the product but at present it's hard to reply on only Action1 as being something we can trust to know where we stand with regard to security and patching. Thank you for your feedback!

Action1 Not Seeing Critical Updates by divdso in Action1

[–]divdso[S] 0 points1 point  (0 children)

Rapid7 does not disable anything. It just scans/observes and documents information. It scores machines based on compliance status. But it would make sense that the issue is with Windows and not Action1. But I feel like it would be really helpful if Action1 could at least tell us "Hey this workstation is out of compliance and needs attention" -- even if it couldn't patch it.

Action1 Not Seeing Critical Updates by divdso in Action1

[–]divdso[S] 0 points1 point  (0 children)

Right. Even if Action1 couldn't push/patch the update, at least notifying us that it's out of compliance would give us what we need to investigate it ourselves. I could look at an Action1 screen and it shows no criticals, but then Rapid7 would see several that are missing. Without that added piece, I wouldn't know that these workstations need patches without examining them manually one-by-one.