Our server is in domain X. In the beacon we specify an AD import from domain Y with a username and password from domain Y. However, the AD import brings in users, computers, and group members from domain X only. Inspecting the .actdir file confirms that even though the file is named for domain Y, its contents are domain X.

Therefore, we setup a Beacon in domain Y and the .actdir file is generated correctly, however, we still do not see the correct results in ActiveDirectoryMember_MT in the FNMS compliance DB. This is throwing our XenApp numbers way off. Looking for hints or pointers on where to investigate.