Windows 10: How to apply GPO to specific server in SERVERS OU?

Servers OU - contains all servers, including server1. Main OU for applying GPOs on servers. So, shifting server1 to another OU isn't an option for me. Users OU - Contains all users. I want to apply a GPO to server1, that will run a logon script when users log in to it. Others servers should not be affected.How to do it?What I have done. - Created GPO, set user Logon script, enabled loopback policy with the merge option in Computer Configuration.- Applied the GPO to Servers OU.- Set the security filtering, and added server1, given permissions are Read, Apply GPO.- Removed Authenticated users.W

:)

 

GPOs linked to user OUs not appearing in Results Wizard

Hello, I'm noticing an issue in my domain where GPOs linked to user OUs are not being applied and not even appearing in the Group Policy Results Wizard report (neither under Applied GPO's nor Denied GPO's, like they don't exist at all).

A few clues:

• I did recently release June Windows updates including MS16-072. However, I was aware of the security processing change and all the related GPO's already had "Authenticated Users" with Read and Apply permission. I added "Domain Computers" to one GPO as a
  test but no luck.
• So far, issue is appearing on Windows 10 computers only. Computers are correctly processing GPO's linked to the computer's OU/hierarchy. A GPO containing loopback-processed user settings does appear under the user settings in the Results wizard, but that
  GPO is linked to a "computers" OU.
• If I link a "user" GPO to a "computers" OU, it appears in the Results Wizard under user settings. However, this is a drastic change in behavior and will interfere with desired outcomes such as a user having drives mapped to their department's files regardless
  of which computer they use.

Please advise, do I need to adjust some setting in Windows 10 to restore processing of GPO's linked to user OU's?

Thanks in advance for any assistance.

 

GPO for Automatic Updates doesn't seem to be applying


Howdy,

I'm trying to create a GPO to point our Windows 10 machines to our WSUS server and then use Automatic Download and Install during a maintenance schedule.

• I've gone under Automatic Maintenance Activation Boundary and set that to 13:00 (1PM) for testing.
• I've gone under Maintenance Random Delay and set that to 1 hour

• I've gone under Config Automatic Updates and set it to 4 (download and install). I also set day to Saturday and time to 13:00 (1PM) but I don't know how this affects the Maintenance Boundary up above...
• I've gone under Specify Intranet Site and put in our WSUS server.

Anyway, I then ran a GPUpdate on my laptop which worked and gpresult says it applied the setting. However, when I go under All Settings | Update & security and then click Advance Options, it still shows "Never check for updates" which is what our normal GPO for everyone else uses. I put my machine in a sub-OU and assigned the test GPO to that sub folder. The main WSUS GPO is not Enforced and the test GPO is Enforced.

Should that dropdown change to reflect the current settings? Is there some other way to tell if the settings are applied correctly? I don't want to click "Check for Updates" because that usually checks and installs which is NOT what I want to do. I want to test the automatic install portion but can't tell if the right settings are in place or not.

I hope that all makes sense. Let me know if I can provide any other information.

Thanks!

 

Windows server 2012R2 GPO failed to apply on windows 10 creators update clients

I have a PDC windows server 2012R2 and BDC 2012R2, GPO is configured in BDC.

I have the below GPO's configured.

->By default, my company intranet page is the default page in internet explorer.

->Lock screen

These are not getting applied on the windows 10 clients where as the remaining clients like windows 7, windows 8.1 are able get these GPO settings.

GPResult command shows that the settings are applied but actually they are not.

Please suggest.

Thanks in advance

***Post moved by the moderator to the appropriate forum category.***