group policy objects
3 TopicsDomain user can not change password for AD by him self
Hello, I have a domain controller with windows server 2019 and also i joined many users to this DC and everything is ok expect that domain user cannot change his password by his self through his PC and when he tried to do this this message show to him "Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain." I did everything right from group policy , i opened group policy then right click on default domain policy and then clicked edit , then i clicked on this path : Computer Configuration>Policies>Windows Settings>Security Settings>Account policies>Password policy. and made changes about password policy and i saw that user`s PC had applied the policy but nothing change and also use could not change password, is this bug or what? Please help me to solve this problem ASAP. Sorry for little English Thanks.Solved97KViews0likes4CommentsFSR to DFRS migration sort of broke the GPOs
So, I'm not a guru here, more of a tinkerer. I'm learning on a home lab which has a Win2k12r2 and a Win2k16 server. I ran through the process of transitioning from FSR to DFSR using the "Quick" option outlined here: https://techcommunity.microsoft.com/t5/storage-at-microsoft/streamlined-migration-of-frs-to-dfsr-sysvol/ba-p/425405 I was able to complete every step successfully. I thought everything worked just fine. Unfortunately, it did not. While the Sysvol share is visible under SYSVOL_DFSR, it's not populated with anything. Furthermore, there is no NETLOGON directory. I see my GPOs under the GPM console, but when I go to edit them, I get an error that says "Failed to open the Group Policy Object. You might not have the appropriate rights." The error then says the following under the details "The system cannot find the path specified." I am however, able to create a new policy. Does someone mind helping me our here? I don't know if the DFSR removes the need for a NETLOGON, which is why that folder doesn't exist. I also don't know why nothing seems to have been copied over from SYSVOL to SYSVOL_DFSR. Since the procedure deleted the SYSVOL folder, I can't check to compare the permissions, but from what I can tell, the permissions on SYSVOL_DFSR are there, so I'm going to assume that they're the right permissions?1.2KViews1like0CommentsCreating Computer Registry in Group policy
Hi to all, In the Group policy I created a OU with the name Azure for this I create a group policy in registry to block the new folder creation HKEY_CLASSES_ROOT\Directory\Background\Shellex\ContextMenuHandlers\New\Default I removed the D to block the user to create new folder in the computers. Now the issue was :-- The remain OU computer and users are getting the Policy.(all user are not able to create a new folder in the computer) In the Gpresult it was not showing. Any idea ????780Views0likes0Comments