Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Duplicate GUID when deploying Worry-Free Business Security (WFBS) agents on a non-persistent Citrix Environment

    • Updated:
    • 7 Apr 2021
    • Product/Version:
    • Worry-Free Business Security Advanced 10.0
    • Worry-Free Business Security Standard 10.0
    • Platform:

This article will guide you on how to prepare the golden image before deploying the WFBS agent on a non-persistent Citrix Environment, and how to prevent duplicate agents from consuming your license seats.

A non-persistent Citrix environment is a type of VDI on which all the changes on the machine are lost when the machine restarts, while a persistent Citrix environment retains changes or personalizations even when the machine restarts.

Duplicate GUID commonly happens every time a non-persistent machine is restarted because as per design, WFBS Services will automatically re-generate agent GUID once rebooted. This issue will generate increasing number of offline agents on the web console which eventually consume the license seat count. To prevent the issue, it is recommended to use our GUID regeneration tool before deploying.

When cloning the golden image, make sure it CANNOT communicate with the WFBS server. Kindly ensure to turn off the image before provisioning it to a new machine. This is to avoid the agent to have duplicate GUID being generated once it connects to the WFBS server.

If ever that you receive an error when running the KeyCleanup.bat of WFBS-SVC, you may need to turned-off the agent self-protection feature before running the tool. To disable it, refer to Enabling/disabling self-protection on WFBS Services.
In case that the web console has been populated already by duplicate agents (GUID), you may refer to the following articles below to address the issue:
If an online agent was inactive for a certain number of time you have configured, the server will automatically restores previously removed Windows Security Agents after connection has been reestablished.

Issue: Agent is reporting back to the default Server/Desktop group when the machine reboot

Solution: By default, new agents will report on the its default group. You can add a startup script that will change the Domain and Domain ID (Device Group regkey) of the agent, so they will report back to the Citrix group every reboot. Do the following:

  1. Go to an agent reporting to the Citrix Group.
  2. Open Registry Editor.
    Always back up the whole registry before making any modifications. Incorrect changes to the registry can cause serious system problems.
  3. Go to the following registry hive:
    • 32 bit: HKLM\Software\TrendMicro\PC-cillinNTCorp\CurrentVersion
    • 64 bit: HKLM\Software\Wow6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion
  4. Look for Domain and Domain ID.
  5. Create a startup script that will update the domain group of the agent.
Solution Id:
Did this article help you?

Thank you for your feedback!

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.