Why Do Computer Objects Require Purging for Group Membership Updates?

I'm dealing with a puzzling issue after our company moved all facility objects to a different top-level Organizational Unit (OU) while migrating to a new division. Initially, everything worked fine, but now I'm facing a strange problem with network group memberships. Before the migration, security groups would automatically assign to computer objects, allowing access to the domain's Wi-Fi.

Since I don't have much insight into the higher-level processes, I suggested to my team that we manually assign these security groups to the computers until I could automate the process. However, despite imaging the computers with Autopilot and seeing the groups in the object's settings, running 'gpresult /r /SCOPE COMPUTER' shows that the groups aren't actually applied unless I use a command to clear the cache.

To get these groups to take effect, I have to:
1. Remote into the computer and check the group assignments with 'gpresult /r /SCOPE COMPUTER'.
2. Execute 'klist -li 0x3e7 purge'.
3. Run 'gpresult /r /SCOPE COMPUTER' again to find the groups now assigned.

I'm puzzled why these groups only apply after I do the purge. Before the migration, this was seamless. We've tried leaving the computers on, preventing sleep, and even stopping the network card from turning off to save power, but nothing has helped. Has anyone else encountered something like this?