Windows couldn t connect to the group policy

#Windows couldn t connect to the group policy windows

If itвЂ™s not a port defined in the application segment, then it would get dropped at the ZAPP client. This could be caused by one of more of the following:

This could be caused by one of more of the following:ДЄ) Name Resolution failure on the current domain controller.Д«) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).

#Windows couldn t connect to the group policy windows

Windows could not resolve the computer name.

my domain is already set in the DNS search domain list. To diagnose the failure, review the event log or run GPRESULT /H GPReport.html from the command line to access information about Group Policy results. User Policy could not be updated successfully. If you do not see a success message for several hours, then contact your administrator. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. The processing of Group Policy failed because of lack of network connectivity to a domain controller. I canвЂ™t figure out why this is failing.Д¬omputer policy could not be updated successfully. IвЂ™m not seeing any blocked traffic to my domain controllers. I believe I have the app segment and policy configured correctly. I get the below when I try to perform a вЂњgpupdate /forceвЂќ on my computer when connected to ZPA.