Capture Client Installation via Command Line Interface or PowerShell

10/16/2021 11 People found this article helpful 187,289 Views

Download

Print

Share

• LinkedIn
• Twitter
• Facebook
• Email
• Copy URL The link has been copied to clipboard

Description

Mass deployment can be done in multiple ways. The following options are recommended depending on the
complexity of the network and available tools:

• Using a third party software deployment tool like an RMM.
  If using a software management tool like Microsoft SCCM, the client can be downloaded and packaged
  with specific command-line parameters for silent installation on the clients.
  
  
• Using Microsoft Global Policy Objects (GPO) or Scripts
  With the help of Microsoft GPO or with custom PowerShell or bash scripts, the client can also be pushed.
  
  
  

Resolution

For command line installation run CMD or PowerShell as administrator. Download the MSI file. The Tenant ID is passed through the TOKENID parameter required for installation. You can find the Tenant ID in the Capture Client Console. Finally, a location of the installation log is entered last. Logs can be used for debugging failed installations.

1. The MSI download happens from the Dashboard. The file will have the Tenant ID appended by default, you can rename the file and remove the Tenant ID to make it a neutral MSI you can reuse for different tenants.
   
   
   
   
   
   
   
2. The Tenant ID is found under Management |Tenant Settings.
   
   
   
   
   
3. Run the command line installation parameters in CMD or PowerShell.

• CMD format and example:
  msiexec /i “<location of msi on filesystem or URL>” /qn /promptrestart TOKENID=<Tenant ID> /L*V “<log file location>"
  
  msiexec /i "C:\Users\test\Downloads\Capture Client.msi" /qn /promptrestart TOKENID=64539818-5169-4516-97db-2922c991234 /L*V “C:\Users\test\Downloads\CCInstall.log”
  
  
  
  
  
• PowerShell format and example:
  Start-Process -FilePath "$env:systemroot\system32\msiexec.exe" -ArgumentList '/i "<location of msi on filesystem or URL>" /qn /promptrestart TOKENID=<Tenant ID> /l*v <log file location>’
  
  Start-Process -FilePath "$env:systemroot\system32\msiexec.exe" -ArgumentList '/i "C:\Users\test\Downloads\Capture Client.msi" /qn /promptrestart TOKENID=64539818-5169-4516-97db-2922c991234 /l*v 'C:\Users\test\Downloads\CCInstall.log'
  
  
  
  
  
  
  

Related Articles

• Capture Client - system requirements
• SentinelOne agent version availability with SonicWall Capture Client
• New Features, Enhancements and Resolved Issues in SentinelOne Agents

Categories

• Endpoint Security > Capture Client > Activity