Every time I request a permission change the IT group at my company instructs me to wait 20 minutes and reboot the computer. I cannot believe that in this day and age you still need to reboot the computer to clear whatever cache stores the permissions locally. It feels like something out of the NT 4 days.
It depends on what the "permission change" is. If they are adding you to a group, you will need to log off/on to effect the change. If they are adding your account, or a group you are already in, to a resource, you wouldn't need to to log off/on.
FYI: If the change is to a machine policy (which can be indirectly via loopback processing), you will need to reboot.
klist tgt. NB: I've not tested this myself; just going off the info in the article.
Commented
Jul 5, 2018 at 9:07
Running gpupdate /force then logging out then in should be fine.
Normally a logout/login should be sufficient.
gpupdate - as mentioned in another answer - will not be enough.
Most likely your IT department manages permissions with group memberships. And those are only updated on logon.
The 20 minutes are due to the default replication frequency of 15 minutes. This could be improved by enabling change notifications.
http://msdn.microsoft.com/en-us/library/how-global-catalog-servers-work(v=ws.10).aspx Cache Refresh and the Availability of Group Changes
