How to use AD Schema snap-in to manage an AD LDS Schema

You will need to be logged in as an administrator (or elevate your privilege level) to complete this task.
First you need to register your Schema snap in before we can use it.

Click Start. Type cmd and press Enter.

Type regsvr32 schmmgmt.dll and press Enter.

Click OK when prompted.

Type Exit and press Enter.

Click Start, type MMC and press Enter.

Click File and then click Add\Remove Snap-ins

Click Active Directory Schema and then click Add

Click OK

Right click Active Directory Schema and then click Change Active Directory Domain Controller…

Click Type a Directory Server name[:port]here;

Type the DNS name, NetBIOS name, or IP address of the server hosting the AD LDS instance. In this example, the server name is MCT-1.

Now click on the enter you just made in the Change Directory Server window and then click OK.

You can now view the classes and attributes of your AD LDS instance.

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog