Better method to upgrade agents

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

Better method to upgrade agents

L3 Networker

Hi,

 

We're a new customer foreseeing the EPM agent's upgrade process will be particularly challenging. Plan to deploy & upgrade via SCCM. I would much rather do via the portal but sounds like it will be difficult with its weak timeout agent architecture and the fact it runs under the USER rather than system context. IMHO, the next time the agent sees the SAAS service, it should simply upgrade under SYSTEM context with no timeout at all. 

 

Assuming the reasoning is that should there be a major release bug or feature, a deployment won't break something. All other agents we deploy can deploy the latest to a pilot group and keep the production group N-1. Now, yes, we could achieve by having a discreet pilot SET. Two key issues I see: #1 Still the way the agents deal with issue I discussed above; #2 one would need to manage those two SETS keeping the pilot one in parity all the time with production.

 

In addition, having to download and prep a whole new pkg (key & config file too) and then having to re-pkg with SCCM also seems very challenging which would also be alleviated if the above is rectified so all upgrades can be pushed via the console (pilot group: latest & the masses: N-1).

 

Thx! 

1 accepted solution

Accepted Solutions

Thanks @Matt Jennison​ 

 

Hi @Douglas Einck​ 

We already have plans to improve the upgrade process with an option to "always upgrade" and an option to work with previous agent version, as you suggested .

 

Can you please elaborate on why the context (user or system) is matter for the upgrade?

View solution in original post

13 REPLIES 13

L7 Applicator

Hey @Douglas Einck​ 

Thanks for this feedback. We do have an Enhancement Requests section for future product requests. I would encourage you to utilize this as it's the best way to get Product Management to see the request.

 

@Uri Shoham​ , I thought you might like to also see this feedback.

 

-Matt

L3 Networker

Great, did so. thx!

Thanks @Matt Jennison​ 

 

Hi @Douglas Einck​ 

We already have plans to improve the upgrade process with an option to "always upgrade" and an option to work with previous agent version, as you suggested .

 

Can you please elaborate on why the context (user or system) is matter for the upgrade?

Hi,

Fantastic news! I'll certainly be on the lookout for it. ETA by chance?

 

I could be thinking about it all wrong, but the context matters so that the agent wouldn't be reliant upon a USER login, rather the next time the SYSTEM itself 'sees' the service, it simply upgrades itself independent of the user.

 

I also won't even see the agent 'alive' in EPM as upgraded till a user interactively logs-in. Yet another reason it's challenging to administer.

 

So, guess more than limited to just the upgrade itself, but the product's address space execution. I understand though we're talking about major architectural changes in the product. Besides, it's a kernel-mode filter driver, so why not? At the very least, trying to understand the reasoning behind.

 

As I'm not going to list specific examples of our products here, all our other agents run under SYSTEM partly for this very reason.

The EPM agent runs as SYSTEM, and it works from the moment the machine is running , regardless to logged in user

You can upgrade it even if no user is logged in.

Hmm, so why do agents show 'disconnected' in EPM and don't seem to come 'alive' till a user logs in? And why can I not check the option to 'upgrade all older' and have all, even disconnected ones upgrade reliably? I don't want timeouts. I want to force an upgrade across the board and ensure every one of them gets upgraded once they see a network connection. It seems very unreliable and not robust as-is. Screenshots attach describe a bit of what I'm talking about.

thx

Field_Content_versions_oct20__0682J00000JLOuzQAH.png 

The process you are referring to is responsible for the interaction with the user (dialogs, support etc..). That is why you see it launched upon logon.

This is NOT EPM process that runs as a system in the background and does EPM duties .

 

As for the Disconnected issue - once the machine is live, it appears as connected, regardless of user being logged in or not -

you can see screenshot from my lab -

The upper one is when the machine is running.

The lower one is when I logged in.

Field_Content_versions_oct20__0682J00000JczEaQAJ.png 

If you have a running machine that doesn't appear as Connected, pls wait a couple of min till it happens.

L3 Networker

I appreciate the reply. So, once you add the option to deploy the agent to 'auto-upgrade' as stated above, we won't have the issue to always be upgrading agents via SCCM as they will self-maintain?

 

Plan to have a test SET with the latest build and or Production SET at N-1 (major build only), then if good, get Production up to latest. In other words, I feel the experience of having to 'chase' machines via EPM's console is not good. Reporting on what builds are installed on what agents would be desured (as some may truly be offline). But to be the only way to deploy/upgrade not wanting to have to pester our SCCM admin would be greatly desired. Agree or am I still not understanding something?

 

We do not see machines show in there unless someone's logged in. For example, I have 3 or 4 VMs and VDIs that remain up and, on the network, but state disconnected until I log in to one.

 

thx

L3 Networker

Any more thoughts on this? thx

L2 Linker

 

@Uri Shoham​ you said "We already have plans to improve the upgrade process with an option to "always upgrade" and an option to work with previous agent version, as you suggested ."|

 

This is great news. Can we confirm you will support both an "N" and "N-1" and possibly and

"N-2" approach for the agent upgrade rules?

L2 Linker

And - is it planned for this year?

L5 Sessionator

Hi @Joel Harrison​ 

 

At the moment I don't have dates of delivery for both items, but next year looks more feasible than this one..

You are welcome to upvote both ERs:

https://community.cyberark.com/s/article/CyberArk-EPM-Agent-Auto-Upgrade-option-hQAI

https://community.cyberark.com/s/article/Ability-to-downgrade-agents-to-a-previous-version-via-EPM-console-oQAA

L5 Sessionator

Do you have more VM that behave as expected? and only those 3,4 don't connect when they up and running?

 

  • 1 accepted solution
  • 544 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!