This issue is resolved in Service Pack 2 of pcAnywhere:  https://kb.altiris.com/article.asp?article=50630&p=1the following work-arounds are available:

If you are unable to update at this time, 

1. Use Active Directory authentication rather than NT authentication. This allows for selection of groups which were queried directly from Active Directory.
   
2. Modify the Host (*.BHF) and Caller files (*.CIF) for each localized host language to include the correct Caller object.

To accomplish this second work-around, you can either install the pcAnywhere 12.5 "box" product on a localized OS, or if your Symantec Management Platform server OS language matches that of the hosts, this can be done by opening the "Symantec pcAnywhere" application from the server desktop.

Take a copy the default host and caller files from a host computer of the desired language under the <%ALLUSERSPROFILE%>\Application Data\Symantec\pcAnywhere\Hosts folder, and modify those two files to implement the work-around.

Symantec has published Knowledge Base article called "Steps by Step How To Creating a pcAnywhere Host" at http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/2009042809411860 with several screen shots, although in this case we will modify an existing host file rather than create a new one.

While editing the NT caller properties for each language, be sure to check the box for "Support global NT users and groups defined in local NT groups".  Otherwise nested users and groups will not be able to authenticate due to another known issue.

Once the localized caller file (for example the English version is named "WINNT.[Local Machine]+Administrator.cif") is created, then both this file and the corresponding *.bhf file should be copied to the <%ALLUSERSPROFILE%>\Application Data\Symantec\pcAnywhere\Hosts folder on each host computer with the same localized OS.

It is important to disable the host configuration policies in the Symantec Management Console if you implement this work-around, because any updates to the policy will overwrite the modifications described above.

Please contact Symantec Technical Support if you have any questions.