Views:

  1. Download the MSI Installer.
    1. Log in to the WFBS-SVC console.
    2. Go to Security Agents and select the target group.
    3. Click the Add Security Agents button.
    4. Click Download Installer to download the MSI file.

      Download Installer

      Click image to enlarge.

    5. Specify if the installer is for Windows or Mac, then click Download to download the Download Utility (WFBS-SVC_Downloader.exe).

      Download Options

      Click image to enlarge.

    6. Double-click the WFBS-SVC_Downloader.exe file to start the download process. The Download Utility will download the Installation Package (WFBS-SVC_Agent_Installer.msi) to your computer.
     
    Make sure that the MSI Installer will be on a shared folder/network that can be accessed or has a read permission for "Authenticated Users" and "Domain Computers".

    installer

  2. Download and edit the deployment script.
    1. Log on to the WFBS-SVC console.
    2. Go to Administration > Tools.

      Tools
      Download tool

    3. Place the Example Deployment Script on the folder where you put the WFBS-SVC Agent installer.
    4. Extract the Example Deployment Script.
    5. Open the example script (WFBS-SVC Example Deployment Script.vbs) using a text editor such as Notepad.
    6. Modify the first line pathOfWFBSHInstaller="msiexec /qn /i WFBS-SVC_Agent_Installer.msi" to the UNC path of your environment:
      • For Non-Service Providers: pathOfWFBSHInstaller=”msiexec /i <executed MSI file> path /L*v <Log file path>”
        For example:
        pathOfWFBSHInstaller=”msiexec /i \\1.2.3.4\GPO\WFBS-SVC_Agent_Installer.msi /L*v C:\Windows\Temp\WFBS_Debug\wofie_msi.log”
      • For Service Providers: ppathOfWFBSHInstaller=”msiexec /i executed MSI file path IDENTIFIER= ABANDON=0 SILENTMODE=1 /L*v ”
        For example:
        pathOfWFBSHInstaller=”msiexec /i \\1.2.3.4\GPO\WFBS-SVC_Agent_Installer.msi IDENTIFIER=BCD6Xb2RpJ6f9oBC1BfVykbbrnl3ZtWTm4GZY5ZMKxx0cBlh5Nlj09BD8pnHv+PVOICwCYfKJ5i+p7qtdTfKMc6W/In2ZZaCWTu8FXC5l74UtwOipVG2FdVUeMfQ/2d3Q09hNhycejMMxceYKmLg0w== ABANDON=0 SILENTMODE=1 /L*v C:\Windows\Temp\WFBS_Debug\wofie_msi.log"
         

        Parameters:

        • IDENTIFIER=<Your_Identifier>
          The Identifier determines the company and group that agents report to after completing the installation. Use the Identifier to install the Agent on multiple Windows computers that are on a different group and account as the computer used to download the installer package.
        • ABANDON=0
          This means that Security Agent installation can't be cancelled by the users.
        • SILENTMODE=1
          This means that the progress of installation won't be seen by the users. The Security Agent would be installed silently with no pop-up and physical action needed.

        Check FAQ No.2 for on how to get the identifier.

        Check FAQ No.4 if you want to use batch file for GPO deployment.

         
    7. Save the file.
  3. Set the group policy.
    • Open the Group Policy Management from your AD server.
    • Select a target OU or create a new OU, then create a new GPO by clicking Create a GPO in this domain, and link it here....

      Create GPO

    • After creating a new GPO, rightclick it and then click Edit. The Group Policy Management Editor will open.
    • Go to Computer Configuration > Policies > Windows Settings > Scripts (Startup/Shutdown), and then double-click Startup to edit it.

      Startup

    • In the Startup Properties window, click Show Files. A new window will popup and the path of the VBS file will be displayed.

      Startup Properties

    • Copy the path and close the popup window.
    • In the Startup Properties window, click Add... to add the script.
    • In the Add a Script window, browse to copied path and put the batch file inside.

      Startup Path

    • Choose the batch file, and the click OK to finish the setup.

      Add Script

    • In the Group Policy Management window, select the GPO and check its “Scope” settings to make sure your target user group is in “Security Filtering”, and the “Links” contains correct OU.
    • Right-click your target OU and click Group Policy Update... to trigger the GPO deployment.
       
      If you receive an error during Update which says 'The remote procedure call was cancelled'. Please make sure that the Inbound Firewall Rules below are enabled.

      Firewall Settings

       
  4. Test the deployment.
    • On client (target) machine, open the Command Prompt.
    • Enter the command “gpupdate /force” and then reboot the machine to test the deployment.

      Policy Update

Logs to collect for troubleshooting:

  • ofcdebug (c:\Windows\Temp\WFBS_Debug)
  • wofie_msi (c:\Windows\Temp\WFBS_Debug)
 

When /qn is used, it will trigger RestartManager, exits original Msiexec and re-create another msiexec to install VCRT. It uses 1602 to exit the original msiexec installation flow. RestartManager will keep finishing the installation flow after VCRT msiexec installation finishes. It includes an update result. The Agent will be installed. You may detect 1st msiexec process and when you check the log, it will have this scenario.

It is suggested to use SILENTMODE=1 only in installation flow.

When using GPO or SCCM, /qn does not matter. It will always be silent when executing msiexec in service mode.

 

  1. Why are clients not getting the GPO?

    Check the Firewall and make sure that it is set correctly. You can also disable the firewall temporarily and try again.

  2. Where to get the identifier?

    1. Go to the WFBS-SVC web console > Security Agents > Manual Groups and choose the group that you want to deploy.

      Manual Groups

    2. Choose Add Security Agents..

      Add Security Agents

       

    3. Under Download Installer option, click the Instructions for service providers link.

      Instructions for service providers

    4. Copy your identifier.

      Copy identifier

  3. Why does the client console display the incorrect language?

    Answer: The Agent will always detect language and reset the client's UI language at service start up. It uses the Windows API GetUserDefaultLangID. According to MSDN, it will use the user locale and return its language.

    If you have language problems, do the following:
    1. Check if the correct language is set under the Registry Key: Software\TrendMicro\PC-cillinNTCorp\CurrentVersion\Misc.\Lang

      Language code list: (MSDN language code)
      DA-DK , DE-DE , EN-US , ES-ES , FR-FR , IT-IT , JA , NB-NO , NL-NL , PL , PT-BR , RU , SV-SE , TR , ZH-CN , ZH-TW

    2. Check the problematic computer’s user local setting. Do the following:

      1. Go to Control Panel > Clock, Language, and Region > Change date, time, or number formats.

        Region and Languages 

      2. Under the Formats tab, choose the correct language.
        Select Language 
      3. If both settings are not consistent, use CDT tool to collect information.
      4. If you directly deploy the MSI with GPO, not with a batch file, it may display an incorrect MSI language on GPO, check this KB article: Arabic language appears when deploying the Worry-Free Business Services (WFBS-SVC) MSI agent via Global Policy Management.
        We recommend users to use VBS or batch file to deploy the Agents instead of using the MSI directly, because it may result to installation failure.
  4. Prepare the batch file as following and then follow the same steps with VBS to prepare the GPO.

    File name: WFBSS_Migration.bat

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

    Example:

    	msiexec /i "\\1.2.3.4\GPO\WFBS-SVC_Agent_Installer.msi" IDENTIFIER="BCD6Xb2RpJ6f9oBC1BfVykbbrnl3ZtWTm4GZY5ZMKxx0cBlh5Nlj09BD8pnHv+PVOICwCYfKJ5i+p7qtdTfKMc6W/In2ZZaCWTu8FXC5l74UtwOipVG2FdVUeMfQ/2d3Q09hNhycejMMxceYKmLg0w==" ABANDON=0 SILENTMODE=1 /L*v "C:\Windows\Temp\WFBS_Debug\wofie_msi.log"
Keywords: install agent,installing agents,deploy agent,example deployment script,deployment script,deploy wfbs-svc,/qn,msiexec,VCRT