Use this method to install the Security Agent on multiple Windows
endpoints that are in the same group and account as the endpoint used to download
the installer package.
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
.Procedure
- Download the Security Agent installer as described in Security Agent Installation — Download Installer.
- Place the Security Agent installer
(
WFBS-SVC_Agent_Installer.msi
) into a folder (for example,D:\share
) on one of your servers (for example,MYFILESERVER
). - Share the folder (
D:\share
) using permissions so that everyone can access this folder and the Security Agent installer. - Download the example deployment script from .
- Open the example script (
WFBS-SVC Example Deployment Script.vbs
) with an editor. - Modify the first line from
pathOfWFBSHInstaller="msiexec /qn /i ""WFBS-SVC_Agent_Installer.msi"""
to the path of your environment, for examplepathOfWFBSHInstaller="msiexec /qn /i ""\\MYFILESERVER\share\WFBS-SVC_Agent_Installer.msi"""
. - Set the Windows startup script to the path where you put the script, for
example
\\MYFILESERVER\share\WFBS-SVC Example Deployment Script.vbs
(The user logon script is not used because the user may not have the necessary permission to install software).
What to do next
For more information on how to set up a Windows startup script in
Windows domain controller, see the following: