You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Active Directory/AD Users/Get-LockedOutLocation.ps1
+30-31Lines changed: 30 additions & 31 deletions
Original file line number
Diff line number
Diff line change
@@ -1,60 +1,59 @@
1
-
#Requires -Version2.0
2
-
FunctionGet-LockedOutLocation {
1
+
functionGet-LockedOutLocation {
3
2
<#
4
3
.SYNOPSIS
5
-
This function will locate the computer that processed a failed user logon attempt which caused the user account to become locked out.
4
+
This function will locate the computer that processed a failed user logon attempt which caused the user account to become locked out.
6
5
7
6
.DESCRIPTION
8
-
This function will locate the computer that processed a failed user logon attempt which caused the user account to become locked out.
9
-
The locked out location is found by querying the PDC Emulator for locked out events (4740).
10
-
The function will display the BadPasswordTime attribute on all of the domain controllers to add in further troubleshooting.
7
+
This function will locate the computer that processed a failed user logon attempt which caused the user account to become locked out.
8
+
The locked out location is found by querying the PDC Emulator for locked out events (4740).
9
+
The function will display the BadPasswordTime attribute on all of the domain controllers to add in further troubleshooting.
11
10
12
11
.EXAMPLE
13
-
PS C:\>Get-LockedOutLocation -Identity Joe.Davis
12
+
PS C:\>Get-LockedOutLocation -Identity Joe.Davis
14
13
15
14
16
-
This example will find the locked out location for Joe Davis.
15
+
This example will find the locked out location for Joe Davis.
17
16
.NOTE
18
-
This function is only compatible with an environment where the domain controller with the PDCe role to be running Windows Server 2008 SP2 and up.
19
-
The script is also dependent the ActiveDirectory PowerShell module, which requires the AD Web services to be running on at least one domain controller.
20
-
Author:Jason Walker
21
-
Last Modified: 3/20/2013
17
+
This function is only compatible with an environment where the domain controller with the PDCe role to be running Windows Server 2008 SP2 and up.
18
+
The script is also dependent the ActiveDirectory PowerShell module, which requires the AD Web services to be running on at least one domain controller.
0 commit comments