This article will allow administrators to install the Security Agent using a Deployment Script. This is a more efficient option when installing a large number of Agents.
- Download the MSI Installer.
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".
- Download and edit the deployment script.
- Log on to the WFBS-SVC console.
- Go to Administration > Tools.
- Place the Example Deployment Script on the folder where you put the WFBS-SVC Agent installer.
- Extract the Example Deployment Script.
- Open the example script (WFBS-SVC Example Deployment Script.vbs) using a text editor such as Notepad.
- Modify the first line pathOfWFBSHInstaller="msiexec /qn /i WFBS-SVC_Agent_Installer.msi" to the UNC path of your environment:
"pathOfWFBSHInstaller="msiexec /qn /i \\\WFBS-SVC_Agent_Installer.msi"
Example: "pathOfWFBSHInstaller="msiexec /qn /i \\DESKTOP-F8ON0RE\Users\Test\Downloads\WFBS-SVC_Agent_Installer.msi"
- Save the file.
- Set the group policy.
- Click Start > Runand type "mmc" on the Open field to open the Group Policy Management console.
- Click File > Add/Remove Snap-in.
- Search for Group Policy Object Editor under Available snap-ins section, and then click Add.
- Click Ok.
- Click Finish.
- On the left panel, go to Computer Configuration > Windows Setting > Scripts(Startup/Shutdown) > Startup.
- Copy the script to the default location. This will ensure that the scripts have proper privilege.
For example: \\MYFILESERVER\share\WFBS-SVC Example Deployment Script.vbs.
- Use the Group Policy Update Utility to reapply all policy settings.
- Open a command prompt window, and then press 'Enter'.
- Run the following command:
The user logon script is not used because the user may not have the necessary permission to install software.
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.