EPM Agent Issues Recap

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

EPM Agent Issues Recap

L4 Transporter

Recapping this (partially for my benefit).

 

I think we all understand the issue with the Microsoft KB and the need to get to the 1196 or (ideally) the 1198 agents.

We are currently pushing to 1198 from the EPM console with decent success, while we hold off the patching (another team) as long as we can.

 

Even without the KB issue though, we (and apparently others) have been experiencing agent disconnects for the last month now. The workstations are alive, but no matter the effort, the EPM agent does not come back without a manual uninstall (using the MSI GUID) and reinstall. This is clearly not sustainable.

 

So this leaves us with disconnected agents of varying versions, with more likely coming due to the KB

I've seen suggestions about turning off self-protection (temporarily). I'm having a hard time understanding how that will help us with agents that were already broken, prior to turning it off. How would they even know? And for the ones that weren't yet broken and would recognize S-P is off because they can connect to the console, what does that do. It feels like a consistent way of mass uninstalling would be more efficient (vs some with the Token, and some without).

 

Since we're talking thousands of agents, and we don't manage the desktops, I'm ultimately looking for some guidance what we can ask be done. I'm not able to confidently tell the SCCM team to do XYZ. I've got to believe others are in the same situation.

 

Perhaps it's over-simplifying (and likely not even possible), but is this an SCCM check of the EPM service, if it's not running check the registry for the EPM version and GUID, if it's less than 1198 uninstall whatever it is, then install 1198 as is normally done on new builds?

 

Thanks for listening.

Thank you.

 

 

4 REPLIES 4

L4 Transporter

Like I said, working it out in my head. Hopefully this helps others ......

(sorry, I've got nothing available to me to try any of these things out myself)

 

From the training docs, it shows an upgrade can be completed as follows:

msiexec.exe /i AgentMSIFile.msi SECURETOKEN=ABCDEFG INSTALLATIONKEY=123456789 CONFIGURATION=CONFIGFILE.INI /qn

 

  1. Is this correct? Is this truly an in-place upgrade? I'm hoping the SCCM folks can look for the 23.3.0.1198 GUID in the registry and if present, NOT do anything. Maybe we need to additionally check for the DisplayName of CyberArk Endpoint Privilege Manager Agent (to confirm it's not a fresh install) but this way we don't have to figure out the existing version and GUID, to do a version-targeted uninstall.
  2. The bigger question. My apologies as I've asked this several times, but not very well. Will disconnected agents recognize a Secure Token (generated for all computers) that was generated AFTER they were already disconnected? And I just don't mean can the Agent use it if it is disconnected, but how would it ever know what the token is in the first place?

 

Thank you

 

 

L4 Transporter

I've since been able to confirm the following:

 

A Secure Token generated for All Computers and/or a specific endpoint, IS recognized by that endpoint, even if the agent was disconnected from the console at the time the token was generated, and continues to not have connectivity. So if you have agents that were already disconnected prior to the KB issue (or other reasons- we've had non recoverable disconnects since mid-March) a newly generated Secure Token can be used to remediate them.

 

The EPM agent upgrade CAN be upgraded in place. This is more of a benefit that you may realize. Typically an uninstall requires knowing the GUID. Then you still have to reinstall a fresh copy. Since we have multiple versions of Agents that are dead, uninstalling programmatically (since we don't own SCCM) would have been challenging. A command line agent upgrade can be performed (remember: they are disconnected so we don't have the Console in these cases) from any version to 23.3.0.1198 using a Secure Token generated for all computers, then the other typical command line format, in a single command (below). Adding the secure token command is what makes it an upgrade, vs a fresh install.

 

I think the token information may be new to folks (this is first I've actually sort of worked that out).

The upgrade option is perhaps less of a revelation, but I've seen conflicting documentation that made me question if it really was a thing.

 

 

 

Field_Content_versions_oct20__0682J00000PaPapQAF.png 

 

@Todd Sherwin​ Thanks for this write-up. However, have you been able to confirm that you can "upgrade in place" a disconnected agent that is already version 1198? Meaning, run the single command you included above to install 1198 on a machine that already has 1198 but won't connect, so a re-install of the same version is necessary?

I have only upgraded a disconnected agent version prior to 1198, to 1198. I’ve not tried to upgrade 1198 to itself to resolve a disconnect issue, though we haven’t had any 1198 disconnects, for any reason.
  • 18 Views
  • 4 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!