Windows 11 version 25H2 introduces a new Group Policy setting, Configure maintenance windows for automatic updates, that lets you define precise time windows for downloading, installing, and restarting after updates. The policy ships with version 3.0 of the ADMX administrative templates and is currently available only in Windows 11 Insider Preview builds. It takes priority over several existing update-related policies, but the interaction rules are only partially documented.
After installing the most recent Updates on their Domain Controllers, some readers have reported in the comments that they experienced that the Local Security Authority Subsystem Service (LSASS) process on their Domain Controllers continually increases memory usage making their Domain Controllers become unresponsive and even automatically restart…
Let’s say that you have a GPO that is scoped to a specific security group. If you add a computer to this security group, you would normally need to restart in order for the computer to see that it is now a member of this group. To bypass this, you can delete the system’s Kerberos ticket and run GPUpdate. The computer will magically see its new group membership without a restart.
Source :
DeployHappiness | Quick Tip: Add Computer to Group – GPUpdate without Restart
When Active Directory replication breaks, IT is in trouble. PowerShell comes with a few cmdlets that allow you to test if Active Directory replication is working properly.
Source :
4sysops
So as many of you may know, yesterday Microsoft released a security hotfix
that changed the behavior of Group Policy. Put simply if you have a security
group filtered User Group Policy Object and you also removed the “Authenticated
Users” group from the policy it will no longer apply after you install
MS16-072.
Source :
Group Policy Central
