Known issues in version 24.2.0.1855

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

Known issues in version 24.2.0.1855

L1 Bithead

After a recent upgrade to 24.2.0.1855 on the CyberArk EPM agent, several instances has been reported where the Windows UAC pops up for elevation instead of the CyberArk prompt. The prompt pops up although the policy has been in place that allows the activity with elevation before.

 

In addition, several workstations are showing as disconnected on the CyberArk platform, although the user is able to 'Request Settings' from the system tray.

 

I would like to know if these are known issues and if there is a solution at this time.

13 REPLIES 13

L7 Applicator

hey @Franklyn Camejo​ 

Can you add some details here? Please include full context and question you need answered.

 

thanks,

-Matt

L1 Bithead

Thanks Matt.

After a recent upgrade to 24.2.0.1855 on the CyberArk EPM agent, several instances has been reported where the Windows UAC pops up for elevation instead of the CyberArk prompt. The prompt pops up although the policy has been in place that allows the activity with elevation before.

 

In addition, several workstations are showing as disconnected on the CyberArk platform, although the user is able to 'Request Settings' from the system tray.

 

I would like to know if these are known issues and if there is a solution at this time.

thank you for the details. I have edited your original post to reflect this.

 

-Matt

L4 Transporter

We're seeing weirdness after an upgrade to 24.4.0 and 24.4.0.1980 agents this weekend 4/21. We don't actively do much in EPM, and now folks are complaining the few policies we do use, no longer applying. They request settings, are up to date, and lower number/higher priority policies do not appear as the applied policy on the CyberArk EPM tab.

L1 Bithead

@Matt Jennison​ 

 

If what @Todd Sherwin​ is mentioning is true, this is looking critical case. I was told by support to upgrade my 10000+ assets to 24.4.0.1980 as my resolution after the disruptive experience with 24.2.0.1855.

 

What is the actual solution to these issues?

Hello @Franklyn Camejo​ 

I can bring this to the attention of our EPM team, but I do not have any additional information outside of Supports recommendations. If this is a critical issue then I would encourage you to call into the Support line for assistance.

 

-Matt

We were on 24.2.0.1855 agents for 2+ months with no issues, so interesting to hear about the bad experience you had there. The 24.4.0.1980 issue of the last few days is only annoying at this point, so I was mainly interested if there were other similar reports. It doesn't raise to Support Case levels at this point for us. Thank you.

L3 Networker

Hello @Franklyn Camejo​  and @Todd Sherwin​ 

can you please open a support case and upload the agent logs if you have not done so yet? We'll need this to check the scenario's at hand.

 

L4 Transporter

Full Disclosure, we've identified our issue. We don't use many policies, but the original filename apparently changed on the most prevalent (non-QS policy), that we do use, with a very vocal user segment, probably making the problem seem much worse than it really was. The change (of course) coincided with the upgrade, so probably jumped to a conclusion. Sorry CyberArk 🙂

L1 Bithead

@Todd Sherwin​ 

I would like to get some details on your experience to see if it helps my issue.

Is the original filename a policy you changed?

When we built the Advanced policy (all it does is explicitly elevate Taskmgr.exe), we did what we’ve seen as a best practice, and used as many of the properties from the EXE as possible (publisher, file name, original file name, etc.)

I don’t know why (I’m not a desktop guy) but I finally noticed the ‘original filename’ for all these people had changed (mine had not). The policy was exact match, so no longer actually applying to the file, even though it was to their endpoint. I was fine.

I just removed that property from the policy, and had them Request Settings. All good.

L4 Transporter

@Franklyn Camejo​ This was an Advanced Policy with an application definition for Task Manager that included multiple attributes. One of which was Original Filename. For some reason, for these users, Original Filename for 'taskmgr.exe' changed to 'taskmgr.exe mui'. I have no idea why. We are not in the desktop/app space. But mui (as you can Google) is multi-language. So we removed that piece from the policy definition, the users refreshed (Request Settings) and are good to go. I was a bit premature blaming the CyberArk upgrade (again, my apologies 🙂 ), due to the issue occurring literally simultaneously with the update. I should know better.

We have a video nugget on building and maintaining good policy definitions. It covers the concepts needed to ensure that policies are secure and do not break due to minor application changes.

  • 26 Views
  • 13 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!