Update Rollup 6 Causing Some Access Denied Issues - IgnoreTokenCheck Ramifications?

I have been seeing an uptick of complaints in the forums regarding Update Rollup 6 causing "Access Denied" issues.

Example with workaround: http://social.microsoft.com/Forums/en/crmdevelopment/thread/57032ef6-c690-4ab2-a7e1-21f1081e5350?prof=required

It seems you can add a IgnoreTokenCheck registry to fix the issue as a workaround.

HKLM>Software>Microsoft>MSCRM>IgnoreTokenCheck (Dword)=1

I am wondering what the risks and ramifications might be of this operation and maybe the community at large could help out by discussing them at this linked forum if they know anything.

http://social.microsoft.com/Forums/en-US/crm/thread/4b30b899-fbdb-4c9e-807e-f442858412b2

 - Thanks!