VMware Horizon Community
ppoirier85
Contributor
Contributor

Machine Targeted Group Policies not consistently loading in Horizon View Environment

I've seen a couple posts on this but I haven't seen an answer that seems to fit my issue. We have had random issues in the past with Group Policies not running on login but it seems like recently we have been getting a lot more reports of it (It is still inconsistent though) and it appears to specifically be our Machine-Targeted policies that are failing to load. In the last 2 months we have upgraded our View environment from 7.4 to 7.10 and also turned on Cloud Pod architecture. Here is the basic info on our environment:

Cloud Pod:

  • 2 Sites with 1 Pod in each Site
  • 6 Production Global Entitlements
  • 4 Entitlements using Home Sites (2 in the remote site and 2 in the main site)

System Layout:

  • 2 Data Centers (each are a separate Site in Cloud Pod)
  • 4 UAGs (2 in each DC) for external connections
  • 4 Connection Servers (2 in each DC)
  • 2 Composer Servers (1 in each DC)
  • SQL Availability Group (2 members)

Agent VMs

  • Windows 7
  • Profile Management: Liquidware Labs Profile Unity

I tried adding the GpNetworkStartTimeoutPolicyValue reg entry (with a 45 second value) as Microsoft recommended and also enabled the "Always wait for the network at startup and logon" local group policy (both in a test pool) but I am still getting inconsistent GP loads. Any suggestions would be appreciated.

Thanks!

Tags (2)
3 Replies
Shreyskar
VMware Employee
VMware Employee

Hi ppoirier85

Notedown the timestamp when GPO fails and once you are logged in to machine, launch event viewer as local admin and check the GPO events under Applications and Services Logs/Microsoft/Windows/GroupPolicy. Once you start tracking each event since the time you started logon, you will definitely find something there to troubleshoot further.

Other than that you can also enable GPO logging on the machine (http://woshub.com/gpo-logging-using-gpsvc-log-in-windows-7/ ) and review that.

ppoirier85
Contributor
Contributor

Thanks Shreyskar. I have enabled GPO logging in a test pool and working on recreating the issue so I can check out the logs.

Mach6
Contributor
Contributor

We've had a similar issue where Machine GPOs were not loading, and this was due to the Daylight-saving-Times. Some machines did not have enough time to synchronize the time with the domain when booting up, which in return makes Machine group policies unable to load.

After every DST change, we have to open our master templates to synchronize the time, close the templates, take a new snapshot and recompose our pools.

Reply
0 Kudos