How to determine which ports your AD LDS instance is listening on.

On occasion, you may have misplaced your documentation on which ports AD LDS is listening on. We have all “misplaced” our documentation before.

Open a command prompt with administrative privileges on the server hosting the AD LDS instance.

Type dsdbutil “li I” q and press Enter

In the above image, you can see both the LDAP port and the secure LDAP port being used by the AD LDS instance.

Comments

Anonymous said…

Excellent, Thank you!

December 4, 2012 at 7:56 AM

Unknown said…

Hello Sir,

When I want to synchronize the AD in windows storage Server 2012 it is asking me LDAP port for the Main Domain Controller .

Can you help me ..

Thanks
Syed Asrar

May 20, 2013 at 4:09 AM

Jason Yoder, MCT said…

Syed,

The normal port for LDAP is 389. Give that one a try. If this does not work, send me more of a detailed description of what you are attempting to do and I will see if I can help.

Jason

May 20, 2013 at 6:23 AM

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

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