Fix Group Policy error 1058

Greetings again,
Sorry for not being here for a long period of time. Recently I faced a strange issue which made me to pen down an article about it. So I will share this experience in case you may encounter it in near future.
While updating group policy clients my client was receiving an error indicating that the group policy folder in SYSVOL is not accessible. At first I thought that it might be related to some problems in DFS share and NETLOGON but it seemed everything was working perfectly because there was no error in DFS event log of the domain controllers.

Create Shadow Groups (Dynamic Groups) in Active Directory

Recently I faced a request from a client wanting a Dynamic Security Group in Active Directory which automatically update its members.. However we do have the concept of dynamic objects in Active Directory (I promise to speak on that on another article), but this one was completely different. The client wanted to have a security group which automatically removes the disabled users from it. So I started a lovely conversation with my lovely friend PowerShell.

Am I locked out? Where? How?

Account lockout feature is one of the powerful methods in order to prevent password related attacks. Using this method victim user account will be locked out after a number of failed attempts in a specific period of time. This feature has found its way to a lot of other technologies these days. My cellphone will be locked out after three wrong passwords and will not be able to work for about 2 minutes.
Although this policy can help you to prevent attackers from guessing user’s password, it is important to consider the risk provided by this solution in your environment because authorized users can lock themselves by mistyping their passwords when they do not remember the password. This problem can be quite costly for your organization, because locked out accounts will be unable to logon unless their accounts unlocks automatically after specific period of time or get unlocked by an administrator

Manipulate delegation wizard in Active Directory

Ever wanted to add your custom attribute to Delegation Wizard feature of Active Directory? Then you came to the right place. Sometime it can happen that default attributes of ‘Delegation Wizard’ are not just enough for you and you would like to add more options to it. In order to do that, you have to edit delegwiz.inf file which you can simply find it on a Domain Controller.

What is Secure Channel in Active Directory?

The word channel is easy to explain. Channel is a way of communicating with people or getting something done. Considering that communication can be a public process, a question will pop up that how can I secure my communication? That’s where the word secure comes into play. A combination of these two words will result in a concept which is absolutely crucial in Active Directory environment and that’s Secure Channel. The term “Secure Channel” can be defined as a way which authenticates the requestor and also provide confidentiality and integrity of data sent across the way.


Manipulating Active Directory search and add custom attribute

Delegation Wizard is one of the great features in delegating permissions to a group or user in order to delegate the responsibility and administering of objects in Active Directory. This wizard is maintained using delegwiz.inf file in each domain controller. In this tutorial we will cover how to manipulate this wizard and add our custom tasks into the default tasks of Delegation Wizard.

Manipulating the delegation wizard is not a difficult process. Firstly you have to navigate to %systemroot% and copy the delegwiz.inf file to your desktop. We have to do this because the file is protected and you are not allowed to overwrite the file. Once you copied the file you open it using notepad and edit using the following way.

Lingering Objects in Active Directory and How To's?

There are some specific concepts in active directory which may put your environment in trouble if you do not attend to fix them as soon as you notice. One of them is lingering objects. Defining the meaning of Lingering Objects (LO) is not difficult. Basically, if an object in your active directory partitions exist in one or more domain controllers and not exist in the rest of the domain controllers in the same partition. So you may ask yourself how that is possible to have an object in a DC and not having the same object in another DC? So what is the responsibility of replication? Wasn’t it designed in order to have a synchronized AD database in your environment? We are going to cover your questions as well.