Thanks for the responce! Yes, all the machines in that group have the same policy serial number (well, they are not all the same as there are sub-groups under the main one, but the dates all match up).
Here's the catch. It's a multi-GUP policy, however, only one system is assigned as a GUP. I wouldn't expect or want all machines in the group/sub-groups to have that GUP's machine in that registry key, only the machines that are on the same subnet of that GUP.
This is why I'm thinking that even though the policy is set up to be a multi-GUP policy, it's defaulting to single-GUP mode because only one machine is defined as a GUP currently.
We have other sites running multi-GUP policies that are working fine. There are a two differences however:
1. The other sites are in separate OUs in our AD structure
2. The other sites actually have multiple machines assigned as GUPs in their multi-GUP policy
Would it be worth breaking out that small remote site in AD and placing it in it's own OU? I'm thinking it wouldn't make much of a difference as there is no documentation specifically stating the environment needs to be set up that way.
Anything else I could try before contacting our Symantec Rep? Again, I appreciate the help with this!