Upgrade package manager

Hey, you can do it through the console for both the agent and adaptors. Admin Guide content here: https://www.beyondtrust.com/docs/privilege-management/console/pm-cloud/package-manager/set-group-updates.htm

Let us know if you have any questions.

Thank you for your response, James. My concern is that we previously installed the adaptors and the agent manually on the user endpoints. Can we now upgrade the agent version on these user endpoints using the package manager, even though the initial installation was done manually? Is it possible to perform the upgrade through the package manager?

Hi ​@Manasvi ,

I’ve tested Package Manager installation in various formats for my organization and I can tell you even if you manually install or deploy from a software management system like JAMF or Microsoft Configuration Manager, that once Package Manager is installed you have complete control over the version of the Client and Adapter via the Computer Group like James linked above.  There is a certain delay in the check-in process that Package Manager performs though.  

Things I’ve personally tested as a consumer:

• Client installed then Installation of Package Manager
• Adapter installed then Installation of Package Manager
• Client and Adapter installed then Installation of Package Manager
• Installation of only Package Manager

In all of these tests Package manager took over the Installation/Update process for both Client and Adapter.

Thank You for the response.

By default, how much time does it take to automatically upgrade the client and adapter version if we enable the package manager in the computer group?

I’ve seen it be anywhere from 15 minutes to a few hours, it truly depends on the configuration of your tenant and frequencies of the machine check-in, as well as how large your environment is. Default Throttle is 1,000 machines a hour. If you have 2,000 machines in your environment, then they should be around every 2hours to check in. However, in my own testing, I’ve noticed the machines will check in multiple times in that hour, so you may see a range of machine 200-1,000 updating. And as you have more machines in the environment, they you will see some take longer than others. I currently only have about 85 of my 5,000 machines in a package manager update enabled computer group. If some error out and retry that chews up another attempt in the 1,000 throttles. 

Of course, you can easily increase the throttle in the configuration's settings.