EPM-W PMC Package Manager

It depends on the software deployment tool you are using. You can refer to KB0020776 for bulk deployment using Intune.

If you are using other deployment tools such as SCCM, PDQ or others. Provide msi installers along with command line installation switches to your deployment team.

Below is an example command line installation for BIMode deployment. Likewise you need to adjust the switches as per your requirement. 

msiexec.exe /i PrivilegeManagementForWindows_x64.msi BIMODE=1 BEYONDINSIGHTURL="https://example.com/EventService/Service.svc"

While we don't have any KBs to specifically address mass deployment strategies for Package Manager, we can grab the MSI package and necessary install strings (both available in your PM Cloud Console), and then leverage the deployment solution used in your environment (SCCM, BigFix, etc.). As @Prudhvi Keertipati noted, once you have the MSI installer package along with your install switches, you should be good to go.

Our primary documents around Package Manager installs can be found in our Admin guide here: https://www.beyondtrust.com/docs/privilege-management/console/pm-cloud/package-manager/index.htm

And our KB article here: https://beyondtrustcorp.service-now.com/csm?id=kb_article_view&sysparm_article=KB0020382

There are however some caveats to consider prior to deployment, most notably network requirements. We have this KB which outlines all of the necessary ports, IPs, and domains to be allow listed for PM Cloud: https://beyondtrustcorp.service-now.com/csm?id=kb_article_view&sysparm_article=KB0019458

For Package Manager, we use the following URLs:

• https://prdpkgsinstallercdn.azureedge.net
• https://prd2pkgsinstallercdn.azureedge.net

For net new EPM deployments, you can simply deploy Package Manager alone and it will handle the subsequent Client/Adapter installs for you. For existing EPM deployments, we'll want to make sure that your endpoints are running 23.5+ in order to be compatible with Package Manager.

Once Package Manager is installed, it will initially scan for updates within 3 minutes and then continues to scan for updates every 2 hours thereafter. Whenever an update is available for Package Manager itself, it will automatically update itself.

msiexec.exe /i PrivilegeManagementForWindows_x64.msi BIMODE=1 BEYONDINSIGHTURL="https://example.com/EventService/Service.svc"

Attempting to install package manager and we are getting error that package manager ends prematurely.  Are there logs where we can look at to see what specifically is failing? I’ve tried in both cloudPC and in on-prem windows domain joined machines. 

Additional information-  I’ve run TNC on the following just to ensure basic communication is available .. 

• https://prdpkgsinstallercdn.azureedge.net
• https://prd2pkgsinstallercdn.azureedge.net
• https://prdpmpolicyeastus.blob.core.windows.net

Hey @MichaelD, the default log location for the Package Manager install logs should be here: C:\ProgramData\Avecto\IC3 Adapter\Logs

For reviewing install failures, I typically go all the way down to the bottom of the logs to see the error code (most commonly 1603). From there, if the error was a 1603 failure, you can search UP for the first occurrence of “Return value 3”. This will show you the initial point of failure.

Maybe I'm just slow. Not sure what I did differently but this time the Package Manager installed.  I did remove a different version of .NET from the machine as I thought maybe it didn’t like the later version and really needed 4.6.2.  I'm a bit puzzled but will test on another machine