When in a bind and needing to troubleshoot something inside Group Policy, there are numerous commands and tools at our disposal. Group Policy is an interaction between multiple systems. As such, you will almost never be troubleshooting from a single place. If attempting to diagnose the addition or disappearance of settings on a client workstation, you will likely be touching that local machine to see what's going on. Once you have a handle on what is or is not happening with the client, chances are that you will discover that some kind of change must have been made within the server infrastructure, which caused the symptoms you are now experiencing on that client machine. So you will probably find yourself logging in to a Domain Controller, or at least launching GPMC from your management workstation, to check out that side of things.

And don't forget about the network in between. All of the Group Policy magic happens successfully because the underlying network is transporting all of the data and packets back and forth between those servers and client computers. Sometimes this network is the super-stable LAN, and sometimes it is weaker, slower remote connections, such as MPLS circuits or VPN links. There are a number of things that could go wrong between client and server. Here are some of the most common general things to look for when troubleshooting a Group Policy interaction.