Most of the time, when running either RSOP or GPUpdate, you are trying to track down something specific, and you probably have a pretty good idea of whether the things you are looking for reside inside User Configuration settings, or Computer Configuration settings. You will notice that when you run RSOP or GPUpdate, you generally only get one side of the story. For example, running either of these commands from a non-administrative Command Prompt that is running in the logged-on user's security context, you will only get results that are specific to that logged-on user (this was the case for both my RSOP and GPResult data in the earlier screenshots). RSOP will even give you an error message informing you that the user does not have rights to view the computer-level information. Since these regular user accounts do not have the permissions needed to query Computer-level criteria, RSOP and GPUpdate will only display the information that is relevant to the user account and User Configuration settings.

Alternatively, when you need to view information about Computer Configuration settings, a regular user account will not have permission to see this data and you would naturally launch an elevated Command Prompt from which to re run the command, right? While this will correctly display for you the RSOP and GPResult information related to the computer account and Computer Configuration settings, it is important to note that any user data displayed inside this output is now relevant for whatever administrator's credentials you used to open the elevated Command Prompt. Since the Command Prompt is no longer running in the logged-on user's context, you can't view that user's information inside the RSOP or GPResult output.

If you need to review both User Configuration and Computer Configuration settings, you will likely need to run your commands twice, once from each security context (administrator versus standard logged-on user).