Win2003 Group Policy Troubleshooting Six Tips

The power of Group Policy is well known, but it is also well known that when its results are often not what you expect. Group Policy is very important for system administrators, but it is also a headache for system administrators when Group Policy is in trouble. The following is a detailed introduction to Group Policy troubleshooting methods. 1. Unexpected results when applying policies to specific users and computers

Suppose you have created a new Set Group Policy object. However, the settings have not yet been applied to the target object. Group policy issues like this are harder to capture. However, Microsoft has adopted a new Group Policy Management Console, which you can download for free. The tool includes a wizard that allows you to quickly view the same policy-related Resultant Set of Policy (RSoP) information. Figure A shows the RsoP information for a specific user on a particular computer
Figure A: The administrator RSoP on a server named RAS

As you can see, the default domain policy is managed by the Windows management architecture ( WMI, Windows Management Instrumentation) The filter was rejected because of a WMI error. This gives an important first step in determining where the group strategy problem lies. In this case, the policy is not applied because the WMI filter believes that the policy will only be applied to the user when they log in to Windows XP Professional. This particular user is now logged into a Windows Server 2003 computer, causing filtering to fail. Figure B shows the failure of the GPO application caused by the WMI filter on Windows Server 2003.
Figure B: WMI filter indicates windows xp Pro

As an option, you can use the gpresult.exe Windows Server 2003 Resource Kit command line tool to view the details of RsoP operations. Because GPMC is so powerful and easy to use, I won't discuss gpresult.exe in this article. Previous1234Next page Total 4 pages