App Control: How To Upgrade Agents With 3rd Party Utilities (Minor Upgrades)

[#1]

Environment

• App Control Agent: All Supported Versions
• Microsoft Windows: All Supported Versions 

Objective

To perform a Minor Upgrade (when the product GUID has remained the same) of the Agent via a 3rd Party Utility, such as SCCM.

Resolution

1. Authenticate with the Agent and set the allow_upgrade flag:

   cd "C:\Program Files (x86)\Bit9\Parity Agent"
   dascli password GlobalCLIPassword
   dascli setconfigprop allow_upgrade=1
   

2. Issue the Minor Upgrade command for the Agent:

   msiexec /fvamus "https://YourServer/hostpkg/pkg.php?pkg=ParityHostAgent.msi" B9_NOCONFIG=1 /L*v "C:\Temp\AgentUpgrade.log"
   

3. Verify allow_upgrade is returned to default:

   cd "C:\Program Files (x86)\Bit9\Parity Agent"
   dascli password GlobalCLIPassword
   dascli setconfigprop allow_upgrade=0

Additional Notes

• An alternative to local authentication and setting allow_upgrade=1 would be the creation & enabling of a temporary Agent Config with the value: allow_upgrade=1
• When the App Control Server is upgraded, a new version of ParityHostAgent.msi and configlist.xml is created in the hostpkg directory.
• To control which version of the agent is pushed out, they can be manually grabbed and distributed:
  1. Login to the App Control Server
  2. In Windows Explorer, navigate to C:\Program Files (x86)\Bit9\Parity Server\hostpkg
  3. Obtain a copy of ParityHostAgent.Msi and configlist.xml
  4. Distribute ParityHostAgent.Msi and configlist.xml to a location that is accessible to the agents being upgraded.
  5. Have the third party utility run command:

     msiexec /fvamus <EnterFullPathHere>\ParityHostAgent.msi B9_CONFIG=<EnterFullPathHere>\configlist.xml /qb- /L*v+ <EnterFullPathHere>\AgentUpgrade.log

Related Content

App Control: How To Upgrade Agents With 3rd Party Utilities (Major Upgrades)