- Log on to the WFBS-SVC console of the new account.
-
On the Dashboard page, in the Security Agent Status widget, click Add Security Agents.
-
From the Add Security Agents to dropdown list, select which group you want to add the Security Agent to.
-
Under Select an installation method, do either of the following:
-
Click Send Installer Link to copy the download URL into your default email client, to be sent to your users. Send the Install link to users and advise them to click the Install link to migrate the Agent to the new account.
-
Click Install on this Endpoint to migrate the Agent of the endpoint where you are currently logged in to the new account. Activation will initialize. If there is no WFBS-SVC Agent detected, the URL will redirect you to Web Installation.
The "Protection activated" message appears once migration is completed.
-
- Go to Security Agents to verify that Agents have been migrated.
- Log on to the WFBS-SVC console of the new account.
-
On the Dashboard , in the Security Agent Status widget, click Add Security Agents.
-
From the Add Security Agents to dropdown list, select which group you want to add the Security Agent to.
-
Under the Download the Installer Package (Advanced) section, expand Instruction For Service Providers and click Copy Identifier.
-
For the script to execute “HostedAgentPluginTool.exe”, use the following script:
Example: @echo off Reg query HKLM\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\HostedAgent /f <companykey value> /d > nul 2>&1 If %ERRORLEVEL% EQU 1 (goto :next) else (goto :end) :next @if /i "%PROCESSOR_ARCHITECTURE%" == "x86" (@goto :x86) else (@goto :x64) :x86 cmd /min /C "set __COMPAT_LAYER=RUNASINVOKER && start /wait "" "C:\Program Files\Trend Micro\Security Agent\HostedAgent\HostedAgentPluginTool.exe"" wfbss_change_identity <identifier> :x64 cmd /min /C "set __COMPAT_LAYER=RUNASINVOKER && start /wait "" "C:\Program Files (x86)\Trend Micro\Client Server Security Agent\HostedAgent\HostedAgentPluginTool.exe"" wfbss_change_identity <identifier> :end
- The command “cmd /min /C "set __COMPAT_LAYER=RUNASINVOKER && start /wait” will be bypassing the admin privilege needed for domain users to run the script.
- The <company key value> on the first part of the script will be checking its current value. You can put the company key value of the old AC where it’s reporting to, to do its checking. If the value you put on the script is same with the value on the registry, it will perform the moving of security agent to the new console.
-
The <company key value> is located on this Registry Hive: HKLM\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\HostedAgent
- Name: CompanyKey
- Type: REG_SZ
After creating the script, put it as a Startup Script on the GPO:
-
Under Security Filtering, add the “Domain Computers” group:
-
Enforce the Group Policy