Group Policy troubleshooting Overview 2

Next, we will introduce the Group Policy troubleshooting knowledgeGroup PolicyTroubleshooting knowledge. The specific content is as follows.

Step 2: Check the infrastructure to troubleshoot problems in the core execution phase

Next, let's talk about the failure of the core execution phase indicated by the Group Policy result wizard, that is, the status of the Group Policy infrastructure component is displayed as Failed ). Such failures usually indicate problems in the infrastructure, which are related to the client or domain controller DC of the Management Group policy information. Note that the client can be either a server or a workstation. Some technologies can cause core execution problems. We can follow the steps below to check:

Does the TCP/IPNetBIOSHelper service run on a client? To successfully execute the Group Policy, this service is required. To check the service, run the netstart command at the command line prompt to obtain the list of currently running services. You can also access the management tool group in the Start Menu, then select the Microsoft Management Console MMC) Service Management Unit to verify that the service has been started.

Is the DNS on the client correctly configured to ensure that the system can correctly parse the DC Name?

Does the network enable the ICMP protocol? Before the Group Policy is executed, the client and DC must be able to perform low-speed connection detection through ICMP. If the ICMP protocol is not enabled, all group policies fail to be executed.

Can a client communicate with a DC? Can I access the copy of Group Policy objects stored in Sysvol of DC? If not, the Group Policy fails to be executed. You can use gpotool.exe tool in the Microsoft Windows2000 resource package to retrieve all the DC in the domain and determine whether Sysvol replication related to group policy storage is synchronized. Sysvol replication that is not synchronized usually indicates that the system has the issue of FR replication.

If you want to know how to solve the WordPress issue on WindowsServer2003, refer to Microsoft's technical document "HOWTO: solving the file replication service problem in WindowsServer2003" at "http://support.microsoft.com/kb/327341/zh-cn.pdf ". Another WordPress monitoring and troubleshooting tool named Ultrasound can help you identify and correct WordPress replication problems, and you can download this tool from the address below: "http://www.microsoft.com/downloads/details.aspx? FamilyID = 61acb9b9-c354-4f98-a823-24cc0da73b50 & DisplayLang = en ".

You can also view the application event logs on the client to find the Event Logs whose event source is Userenv. You can get clues about core execution issues from these logs. These events are usually related to core executions and sometimes contain information about some errors that occur during execution. In this case, you 'd better use the gpolog. adm template to enable detailed application event logs.

Step 3: Solve the client expansion problem through Application Event Logs

If the Group Policy result Wizard shows that the problem is related to a specific client extension, you should focus on the cause of the extension failure. Start by viewing the related errors in the application event log. For specific client expansion problems, you usually see the following content:

FolderRedirection is used for Folder Redirection policies)

Userinit is used for script Policy)

Scecli is used to set security policies)

ApplicationManagement is used for software installation policies)

Userenv is used to manage template policies and core processes)

Application Event Logs alone are not enough. You may need to explore more deeply to find out specific client expansion problems.

Step 4: Enable logs for core or client Extension Execution

If the information in the Application Event Log is not detailed enough, you may need to study the problems in the core execution or client expansion phase in more depth. The gpolog. adm template I mentioned earlier can open various logs. It is recommended that the Userenv log be written to % windir % \ debug \ usermode) for analysis. This log can capture detailed information about each step in the core and client Extension Execution phase, it also includes user configuration file activities. This file will be updated during the execution cycle of each group policy. Through this file, you can traverse the execution actions of each client extension. You can see whether a client extension is successfully executed. If not, you can also see the reason. For example, the log file may show that the client extension is not running because the Group Policy object it processes has not changed since the previous cycle.

Finally, you can enable detailed logs to help you eliminate errors in specific client extensions. For example, you can enable detailed logs of software installation extensions to determine why an installation package cannot be correctly installed, whether it is a client extension or a package issue. If the problem is related to the package, you can start the detailed Windows Installation Log in the management template policy Computer Configuration \ management template \ Windows component \ Windows installation service \ log) to further track the problem.

Methods

Group Policy troubleshooting must adopt a systematic and gradual approach. First, narrow down the scope of the problem and then seek a solution. I believe that the tools and suggestions I mentioned earlier can help you shorten troubleshooting time and easily find a solution.

The key to troubleshooting the Group Policy is to know where to find the problem. I hope this article will be helpful to readers by introducing the Group Policy troubleshooting knowledge. More knowledge about group policies remains to be explored and learned by readers.