Unsolved

1232

August 20th, 2021 14:00

Thin Client Not Applying GP Computer Configuration

Hello, this may be a mix of Thin Clients combined with Active Directory/Group Policy, thanks in advance for the help! Short summary is that the Computer Configuration portion of my group policies won't apply to my Windows 10 5070 thin clients, but the User Configuration policies apply with no issues. Anyone else run into this?

More details, sorry if there are too many but just trying to give a full picture:
I've added my 5070 Thin Clients (Windows 10 IoT Embedded) to my domain and Windows Server 2012 Active Directory, and have the thin clients in their own organizational unit (Thin Client OU). This OU also contains a nested OU (Console OU) with the console user account that we'll default to.

Thin Client OU is linked to the Thin Client GP group policy that contains all of our Computer Configuration settings like interactive logon warning banner.
Console OU is linked to the Console GP group policy with the user-specific settings like a certain desktop background and disabling the Control Panel.

When I log into the thin clients as Console, rsop.msc shows me that the User Configuration settings have been applied exactly as they should be from the correct Console GP policy, but all of the Computer Configuration settings say "Not Defined" and no logon banner shows up.

gpresult /r lists the Thin Client GP under the computer's applied group policy objects, but none of its settings come through. Been troubleshooting this for ages and can't seem to make any progress, thanks for the help!

August 23rd, 2021 05:00

Oh, and some additional info, I tried moving the thin clients to another OU that I know is applying GP Computer Configs correctly and it still didn't work, only User Config changes came through, all Computer Config settings were Not Defined.

18 Posts

September 3rd, 2021 03:00

Turn off the write filter and update the policy Gpupdate /sync & reboot

Turn ON the writer filter and check. 

No Events found!

Top