How to resolve Group Policy error codes 8007071a and 800706ba

Case



You are running "Group Policy Update" on an OU inside the Group Policy Management Console in Active Directory but you are receiving RPC errors from your servers or domain-joined workstations, as shown in the example below.





After a Group Policy Update, you come across Group Policy error codes 8007071a and 800706ba.





This means that the local Windows Firewall is not configured properly to allow Group Policy (GPO) traffic. GPO traffic an be either remote GPO update or remote GP Resultant Set of Policy (RSOP) operations.



Solution



Option 1

Run gpedit.msc and create a new local group policy object which implements the following policies under Local Computer Policy --> Computer Configuration --> Windows Settings --> Security Settings --> Windows Defender Firewall --> Inbound Rules :





The full configuration is shown below.





After the above local group policies are configured on each domain server and workstation, you can start applying group policy objects to the domain targets. To ensure that group policy update is working without issues, run a "Group Policy Update" force operation from within the gpmc.msc console by right clicking on the desired OU which contains AD computer objects to be tested.



Option 2

Utilize the two starter GPOs available out of the box in all modern versions of Windows, as shown below.





Windows Server Group Policy offers new Starter GPOs called Group Policy Remote Update Firewall Ports and Group Policy Reporting Firewall Ports. These Starter GPO include policy settings to configure the firewall rules required for GPO operations. This enables inbound network traffic on the ports, which is necessary to allow the remote Group Policy refresh and RSOP to run. It is a best practice to create new GPOs from this Starter GPO, and then link the new GPOs to your domain with a higher precedence than the Default Domain GPO, so that you can configure all computers in the domain to enable a remote Group Policy refresh.



Group Policy Remote Update Firewall Ports Starter GPO





Group Policy Reporting Firewall Ports Starter GPO




https://stefanos.cloud/kb/how-to-resolve-group-policy-error-codes-8007071a-and-800706ba/

Comments

Post a Comment

Popular posts from this blog

How to perform hardware health checks in Windows

Image
Case You need to perform an overall hardware health check in a Windows machine, running either a Windows client or a Windows Server operating system. This article provides guidance on the steps to carry out to perform hardware health checks in Windows. Solution Carry out the steps below. - Thoroughly check all Windows event logs (Application, System, Security) for any warnings or errors which may be related to issues you are experiencing with your Windows machine. - Check the device management mmc console by running devmgmt.msc. Ensure that you choose to show all hidden devices from the View menu. If you notice any exclamation marks next to any device, you will need to re-install its driver from the respective manufacturer to ensure that there afterwards no warnings in the device management console. - Check the health of all your disks , either HDD or SSD. Follow instructions in the following KB article for steps to follow to check your disk health: https://stefanos.cloud/kb/how-to-ch
Read more

FsLogix 2201 Public Preview release

Image
The FsLogix 2201 Public Preview release is now available for download from Microsoft. The change log is as follows: - Fixed issue where the FSLogix Profile Service would crash if it was unable to communicate with the FSLogix Cloud Cache Service. - The OfficeFileCache folder located at %LOCALAPPDATA%MicrosoftOffice16.0OfficeFileCache is now machine specific and encrypted so we now exclude it from FSLogix containers. Office files located outside this folder are not impacted by this update. - Windows Server 2019 version 1809, and newer versions of Windows Server, natively support per-user search indexes and we recommend you leverage that native search index capability. FSLogix Search Indexing is no longer available on those versions of Windows Server. - Windows 10 Enterprise Multi-session and Windows 11 Enterprise Multi-session natively support per-user search indexes and FSLogix Search Indexing is no longer available on those operating systems. - FSLogix now correctly handles cases where
Read more