Logo - tutorial.programming4.us
Windows XP
Windows Vista
Windows 7
Windows Azure
Windows Server
Windows Phone
 
 
Windows Server

Windows Server 2008 Server Core : Managing System Users - Obtaining Group Policy Results with the GPResult Command

3/25/2011 2:20:05 PM
Use this command to obtain the Resultant Set of Policy (RSoP) for a particular user on a system. This command considers all of the security settings for both the computer and the user and creates a resultant policy—the policy that actually affects the user's security setup on the system. Microsoft provides a wealth of articles on RSoP. For example, you can see how RSoP affects Internet Protocol Security (IPSec) assignments at http://technet2.microsoft.com/windowsserver/en/library/35675107-c728-47cd-8ad9-bfd2d5e7fe0a1033.mspx. You'll also find an excellent article on planning and logging RSoP at http://www.windowsnetworking.com/articles_tutorials/Resultant-Set-Policy-Planning-Logging.html. This command uses the following syntax:
GPRESULT [/S system [/U [domain\]user [/P [password]]]]
[/SCOPE {USER | COMPUTER}] [/USER [domain\]targetuser] [/V | /Z]

The following list describes each of the command line arguments.


/S
system

Specifies the remote system that you want to check. In most cases, you'll also need to supply the /U and the /P command line switches when using this switch.


/U
[domain\]user

Specifies the username on the remote system. This name may not match the username on the local system. You'll need to supply a domain name when working with a domain controller.


/P
[password]

Specifies the password for the given user. You can provide the command line switch without specifying the password on the command line in cleartext. The system prompts you for the password. Using this feature can help you maintain the security of passwords used on your system.


/USER
[domain\]targetuser

Displays RSoP data for the specified user. You can check the information of users in other domains by including the user domain.


/SCOPE {USER | COMPUTER}

Specifies the scope of the output. You can display the user or computer information separately. The utility displays both user and computer information when you omit this command line switch.


/V

Displays verbose information about the user or computer. The amount of additional information you receive varies by system. The utility displays detail-specific settings that have a precedence of 1.


/Z

Displays superverbose information about the user or computer. The amount of additional information you receive varies by system. The utility displays detail-specific settings that have a precedence of 1 or higher. Using this command line switch lets you see whether a setting is set in multiple places.

Much of the Microsoft documentation leads you to believe that this utility is useless without having Active Directory installed. However, even without Active Directory, you can discover security information about a user with this utility. For example, you can verify that the system views the workstation as stand-alone, check the user's group participation, and verify local policies for the user.

 
Other -----------------
- Windows Server 2008 Server Core : Managing System Users - Configuring Profiles with the CMStP Utility
- Windows Server 2008 Server Core : Auditing User Access with the AuditPol Utility
- BizTalk Server 2010 : Configuring Core Server Settings
- BizTalk Server 2010 : Indicating Matches in Maps
- SharePoint 2010 : Publishing to Excel Services (part 2) - Allowing Parameter Input in Excel Web Access
- SharePoint 2010 : Publishing to Excel Services (part 1)
- Securing an Exchange Server 2010 Environment : Securing Outlook Web App
- Securing an Exchange Server 2010 Environment : Protecting Against Spam
- Securing an Exchange Server 2010 Environment : Securing Outlook 2007
- Securing an Exchange Server 2010 Environment : Securing Your Windows Environment
 
 
Top 10
- Microsoft SQL Server 2012 : Knowing Tempdb - Troubleshooting Common Issues (part 3) - Troubleshooting Space Issues
- Microsoft SQL Server 2012 : Knowing Tempdb - Troubleshooting Common Issues (part 2) - Latch Contention - ikelihood of it happening. Multiple Tempdb Data Files
- Microsoft SQL Server 2012 : Knowing Tempdb - Troubleshooting Common Issues (part 1) - Latch Contention - Allocation Page Contention
- Microsoft SQL Server 2012 : Knowing Tempdb - Overview and Usage (part 2) - The Version Store
- Microsoft SQL Server 2012 : Knowing Tempdb - Overview and Usage (part 1) - User Temporary Objects
- Microsoft Lync Server 2013 : Windows Client - Navigating in the Client - Useful Lync Client Shortcuts
- Microsoft Lync Server 2013 : Windows Client - Navigating in the Client - Managing Contacts, Managing Groups, Status View
- Microsoft Lync Server 2013 : Windows Client - Navigating in the Client - Configuring Basic Options
- Microsoft Lync Server 2013 : Windows Client - Installing the Client
- Microsoft Exchange Server 2013: Configuring mailbox delivery restrictions, permissions, and storage limits (part 4) - Setting storage restrictions on mailbox and archives
 
Windows XP
Windows Vista
Windows 7
Windows Azure
Windows Server
Windows Phone