Download Installer — Different Group and Account Installation

Use the Identifier to install the Security Agent on multiple Windows endpoints that are in a different group and account as the endpoint used to download the installer package.

This method is recommended for resellers or administrators who need to manage multiple endpoints that are in different groups or domains. Instead of downloading multiple copies of the installer, the same .msi file can be used with different Identifiers when installing on different endpoints.

Note:

The Identifier determines the company and group that Security Agents report to after completing the installation.

The example deployment script used in this task saves the latest debugging logs to help you troubleshoot any installation issues.

  • LoginScript.log: Contains the Visual Basic Script (VBScript) logs

  • MSI_Installer.log: Contains the detailed MSI installation logs

When a Local System account runs the deployment script, the logs are saved in %SystemRoot%\Temp\WFBS_Installer_Debug. In other scenarios, the logs are saved in %Temp%\WFBS_Installer_Debug.

  1. Download the Security Agent installer as described in Security Agent Installation — Download Installer.
  2. Obtain the Identifier information.
    1. On the Worry-Free Business Security Services web console, go to SECURITY AGENTS.
    2. Above the Security Agent List, click Add Security Agents.
    3. Under Download Installer, click Instructions for service providers.

      The Identifier information displays.

    4. Click Copy Identifier.

      Worry-Free Business Security Services saves a copy of the Identifier information to the clipboard.

  3. Run the following command to deploy the .msi file:
    • No Identifier:

      msiexec /i <"executed MSI file path"> SILENTMODE=1 /L*v+ <"Log file path">

    • Include Identifier:

      msiexec /i <"MSI file path"> IDENTIFIER=<"Your_Identifier"> SILENTMODE=1 /L*v+ <"Log file path">

    Deployment Method

    Example

    Batch file

    For example, WFBS-SVC_deployment.bat

    • No Identifier:

      • msiexec /i "\\ShareFolder\WFBS-SVC_Agent_Installer.msi" SILENTMODE=1 /L*v+ “C:\Windows\Temp\WFBS_Debug\wofie_msi.log”

      • msiexec /i "C:\Users\AdminiWin7x64\Desktop\WFBS-SVC_Agent_Installer.msi" SILENTMODE=1 /L*v+ "C:\Windows\Temp\WFBS_Debug\wofie_msi.log"

    • Include Identifier:

      msiexec /i "\\ShareFolder \WFBS-SVC_Agent_Installer.msi" IDENTIFIER="Identifier" SILENTMODE=1 /L*v+ "C:\Windows\Temp\WFBS_Debug\wofie_msi.log"

    • msiexec /i "C:\Users\AdminiWin7x64\Desktop\WFBS-SVC_Agent_Installer.msi" IDENTIFIER="Identifier" SILENTMODE=1 /L*v+ "C:\Windows\Temp\WFBS_Debug\wofie_msi.log"

    PowerShell

    Add a single quote (') before and after the log file path.

    msiexec /i "\\PCRDS01\PointClickTeam\WFBS-SVC_Agent_Installer.msi" SILENTMODE=1 /L*v+ '"C:\Windows\Temp\WFBS_Debug\wofie_msi.log"'

    Deployment script

    The example deployment script is available in ADMINISTRATION > Tools.

    Add a double quote (") before and after the .msi file, Identifier, and log file path.

    • pathOfWFBSHInstaller="msiexec /i ""C:\Users\AdminiWin7x64\Desktop\WFBS-SVC_Agent_Installer.msi"" IDENTIFIER=""nkpwSGYhtp7ODzK55KGCm/buomXE1nH2GhtFdaBzUuip2HUzlDJGVsUp4y4Cwbc6EQZmL8i/SJLD6dSgHmz1CrtofMXhvpPkXz2gZgpmdghM7q8bW1j1ffhFnvqzfTzJpqZaTVPrTqq1OIoIQUyXXA=="" SILENTMODE=1 /L*v+ ""C:\Windows\Temp\WFBS_Debug\wofie_msi.log"""

    • pathOfWFBSHInstaller="msiexec /i ""\\bpserver\Software_Distribution_Point\TrendMicro\WFBS-SVC_Agent_Installer.msi"" IDENTIFIER=""nkpwSGYhtp7ODzK55KGCm/buomXE1nH2GhtFdaBzUuip2HUzlDJGVsUp4y4Cwbc6EQZmL8i/SJLD6dSgHmz1CrtofMXhvpPkXz2gZgpmdghM7q8bW1j1ffhFnvqzfTzJpqZaTVPrTqq1OIoIQUyXXA=="" SILENTMODE=1 /L*v+ ""C:\Windows\Temp\WFBS_Debug\wofie_msi.log"""