Views:

Duplicate GUID commonly happens every time a non-persistent machine is restarted because as per design, endpoints will automatically re-generate agent GUID once rebooted. This issue will generate increasing number of offline security 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 you ever 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 cases when the web console has been populated already by duplicate security agent or endpoint, 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 restore previously removed Windows Security Agents after connection has been re-established.
 

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

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.