How to manually unlock a locked GPO or OU? (4230565)

How to manually unlock a locked GPO or OU?

How to manually unlock a GPO or OU when you receive the following error:

Quest.Avalanche.Exceptions.LockException: This object has been locked for exclusive use by another user.  Objects are usually only locked for very short periods of time, so chances are good that if the operation is retried it will succeed.  If an object continues to yield this error, please contact Quest Software Support.

1. Go to the properties of the GPO or OU within GPOADmin and make note of the GPOADmin ID on the General tab
2. Connect to the Configuration store (the steps to connect to a Configuration store in AD LDS is in the additional information below). Open ADSI Edit and navigate to the Configuration naming context. If you can see the Configuration naming context, proceed to step 3. If you cannot see the Configuration naming context  then right-click on the root ADSI Edit node and select Connect To. Make sure the checkbox “Select a well known Naming Context” is checked and select Configuration from the dropdown. Click the OK button. If using a AD LDS server then you will need to connect to the server and port number
3. Expand the Configuration container to CN=Configuration, CN=Services, CN=Quest, CN=QGPM, CN=Wentworth,CN=VCRoot. 
4. Find the GUID for the GPO or OU within the VCRoot
5. Once found go to the properties and edit the Description attribute
6. Make note or copy the GUID listed here. Remove the GUID and Click OK
7. Go back to GPOADmin and attempt to perform the action again (check in, deploy, etc). If this still does not work, the change may require replication time.

How to manually unlock a Version Controlled object in GPOAdmin

Please note that if you cannot find the ID of the GPO right under the VCRoot container, as described in Step 4, chances are it is in one of the containers down the subtree. If that's the case, look up each container's ID in GPOAdmin Console and drill down the container structure in ADSIEdit to get to the GPO in question. If this issue continues to occur, check the delegation on the target GPO to ensure the service account has proper permissions (check denys) How to connect to a local AD LDS instance using ADSIedit.msc 1. First step is to determine the LDAP port being used by the instance (this is configured during the AD LDS role installation). Open a command prompt and type 'dsdbutil'. At the dsdbutil: prompt type 'list instances'. This will display the instance name as well as the port number. 2. Open ADSIedit.msc, right click on ADSI Edit and go to "Connect to" 3. Select "Configuration" within the dropdown menu for "Select a well known Naming Context" 4. For the section "Select or type a domain or server" type in the local computer name. It will try to connect automatically using port 389. If the default port is not being used type it in, for example servername:50000. 5. Once connected, it will automatically connect to the Configuration context (for example "CN=Configuration,CN={ADLDS INSTANCE GUID}").