{
	"id": "b47914f3-5cee-4d1e-8186-bc5e84bd1fe4",
	"created_at": "2026-04-06T02:11:55.656617Z",
	"updated_at": "2026-04-10T13:12:17.607742Z",
	"deleted_at": null,
	"sha1_hash": "f56b17bef39ac8a5ee5c4d3b227cc52c39b23529",
	"title": "Get-ADUser",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 107201,
	"plain_text": "Get-ADUser\r\nBy Archiveddocs\r\nArchived: 2026-04-06 01:51:38 UTC\r\nGets one or more Active Directory users.\r\nGet-ADUser -Filter \u003cstring\u003e [-ResultPageSize \u003cint\u003e] [-ResultSetSize \u003cSystem.Nullable[System.Int32]\u003e] [-SearchBa\r\nFilter\r\nResultPageSize\r\nResultSetSize\r\nSearchBase\r\nSearchScope\r\nSearchScope\r\nAuthType\r\nCredential\r\nPartition\r\nProperties\r\nServer\r\nGet-ADUser [-Identity] [-AuthType { | }] [-Credential ] [-Partition ] [-Properties \u003cstring[]\u003e] [-Server ] []\r\nIdentity\r\nAuthType\r\nCredential\r\nPartition\r\nProperties\r\nServer\r\nGet-ADUser -LDAPFilter [-ResultPageSize ] [-ResultSetSize \u003cSystem.Nullable[System.Int32]\u003e] [-\r\nSearchBase ] [-SearchScope { | | }] [-AuthType { | }] [-Credential ] [-Partition ] [-Properties \u003cstring[]\u003e] [-\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 1 of 19\n\nServer ] []\r\nLDAPFilter\r\nResultPageSize\r\nResultSetSize\r\nSearchBase\r\nSearchScope\r\nAuthType\r\nCredential\r\nPartition\r\nProperties\r\nServer\r\nThe Get-ADUser cmdlet gets a user object or performs a search to retrieve multiple user objects.\r\nThe Identity parameter specifies the Active Directory user to get. You can identify a user by its distinguished name\r\n(DN), GUID, security identifier (SID), Security Accounts Manager (SAM) account name or name. You can also\r\nset the parameter to a user object variable, such as $\u003clocalUserObject\u003e or pass a user object through the pipeline\r\nto the Identity parameter.\r\nTo search for and retrieve more than one user, use the Filter or LDAPFilter parameters. The Filter parameter uses\r\nthe PowerShell Expression Language to write query strings for Active Directory. PowerShell Expression\r\nLanguage syntax provides rich type conversion support for value types received by the Filter parameter. For more\r\ninformation about the Filter parameter syntax, see about_ActiveDirectory_Filter. If you have existing LDAP query\r\nstrings, you can use the LDAPFilter parameter.\r\nThis cmdlet retrieves a default set of user object properties. To retrieve additional properties use the Properties\r\nparameter. For more information about the how to determine the properties for user objects, see the Properties\r\nparameter description.\r\nSpecifies the authentication method to use. Possible values for this parameter include:\r\nNegotiate or 0\r\nBasic or 1\r\nThe default authentication method is Negotiate.\r\nA Secure Sockets Layer (SSL) connection is required for the Basic authentication method.\r\nThe following example shows how to set this parameter to Basic.\r\n-AuthType Basic\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 2 of 19\n\nThe following lists the acceptable values for this parameter:\r\nNegotiate**\r\nBasic**\r\nDefault Value: Microsoft.ActiveDirectory.Management.AuthType.Negotiate\r\nData Type: ADAuthType\r\nAttributes\r\nName Value PSMAML Attribute\r\nRequired? false required\r\nVariable Length? false variableLength\r\nAccept wildcard characters? false globbing\r\nAccept Pipeline Input? false pipelineInput\r\nPosition? named position\r\nValue Attributes\r\nName Value PSMAML Attribute\r\nRequired? true required\r\nVariable Length? false variableLength\r\nSpecifies the user account credentials to use to perform this task. The default credentials are the credentials of the\r\ncurrently logged on user unless the cmdlet is run from an Active Directory PowerShell provider drive. If the\r\ncmdlet is run from such a provider drive, the account associated with the drive is the default.\r\nTo specify this parameter, you can type a user name, such as \"User1\" or \"Domain01\\User01\" or you can specify a\r\nPSCredential object. If you specify a user name for this parameter, the cmdlet prompts for a password.\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 3 of 19\n\nYou can also create a PSCredential object by using a script or by using the Get-Credential cmdlet. You can then\r\nset the Credential parameter to the PSCredential object The following example shows how to create credentials.\r\n$AdminCredentials = Get-Credential \"Domain01\\User01\"\r\nThe following shows how to set the Credential parameter to these credentials.\r\n-Credential $AdminCredentials\r\nIf the acting credentials do not have directory-level permission to perform the task, Active Directory PowerShell\r\nreturns a terminating error.\r\nDefault Value: **\r\nData Type: PSCredential\r\nAttributes\r\nName Value PSMAML Attribute\r\nRequired? false required\r\nVariable Length? false variableLength\r\nAccept wildcard characters? false globbing\r\nAccept Pipeline Input? false pipelineInput\r\nPosition? named position\r\nValue Attributes\r\nName Value PSMAML Attribute\r\nRequired? true required\r\nVariable Length? false variableLength\r\nSpecifies a query string that retrieves Active Directory objects. This string uses the PowerShell Expression\r\nLanguage syntax. The PowerShell Expression Language syntax provides rich type-conversion support for value\r\ntypes received by the Filter parameter. The syntax uses an in-order representation, which means that the operator\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 4 of 19\n\nis placed between the operand and the value. For more information about the Filter parameter, see\r\nabout_ActiveDirectory_Filter.\r\nSyntax:\r\nThe following syntax uses Backus-Naur form to show how to use the PowerShell Expression Language for this\r\nparameter.\r\n\u003cfilter\u003e ::= \"{\" \u003cFilterComponentList\u003e \"}\"\r\n\u003cFilterComponentList\u003e ::= \u003cFilterComponent\u003e | \u003cFilterComponent\u003e \u003cJoinOperator\u003e \u003cFilterComponent\u003e |\r\n\u003cNotOperator\u003e \u003cFilterComponent\u003e\r\n\u003cFilterComponent\u003e ::= \u003cattr\u003e \u003cFilterOperator\u003e \u003cvalue\u003e | \"(\" \u003cFilterComponent\u003e \")\"\r\n\u003cFilterOperator\u003e ::= \"-eq\" | \"-le\" | \"-ge\" | \"-ne\" | \"-lt\" | \"-gt\"| \"-approx\" | \"-bor\" | \"-band\" | \"-recursivematch\" | \"-\r\nlike\" | \"-notlike\"\r\n\u003cJoinOperator\u003e ::= \"-and\" | \"-or\"\r\n\u003cNotOperator\u003e ::= \"-not\"\r\n\u003cattr\u003e ::= \u003cPropertyName\u003e | \u003cLDAPDisplayName of the attribute\u003e\r\n\u003cvalue\u003e::= \u003ccompare this value with an \u003cattr\u003e by using the specified \u003cFilterOperator\u003e\u003e\r\nFor a list of supported types for \u003cvalue\u003e, see about_ActiveDirectory_ObjectModel.\r\nExamples:\r\nThe following examples show how to use this syntax with Active Directory cmdlets.\r\nTo get all objects of the type specified by the cmdlet, use the asterisk wildcard:\r\nAll user objects:\r\nGet-ADUser -Filter *\r\n-or-All computer objects:\r\nGet-ADComputer -Filter *\r\nTo get all user objects that have an e-mail message attribute, use one of the following commands:\r\nGet-ADUser -Filter {EmailAddress -like \"*\"}\r\nGet-ADUser -Filter {mail -like \"*\"}\r\n-or-Get-ADObject -Filter {(mail -like \"*\") -and (ObjectClass -eq \"user\")}\r\nNote: PowerShell wildcards other than \"*\", such as \"?\" are not supported by the Filter syntax.\r\nTo get all users objects that have surname of Smith and that have an e-mail attribute, use one of the following\r\ncommands:\r\nGet-ADUser -filter {(EmailAddress -like \"*\") -and (Surname -eq \"smith\")}\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 5 of 19\n\n-or-Get-ADUser -filter {(mail -eq \"*\") -and (sn -eq \"Smith\")}\r\nTo get all user objects who have not logged on since January 1, 2007, use the following commands:\r\n$logonDate = New-Object System.DateTime(2007, 1, 1)\r\nGet-ADUser -filter { lastLogon -le $logonDate }\r\nTo get all groups that have a group category of Security and a group scope of Global, use one of the following\r\ncommands:\r\nGet-ADGroup -filter {GroupCategory -eq \"Security\" -and GroupScope -eq \"Global\"}\r\n-or-Get-ADGroup -filter {GroupType -band 0x80000000}\r\nNote: To query using LDAP query strings, use the LDAPFilter parameter.\r\nDefault Value: **\r\nData Type: string\r\nAttributes\r\nName Value PSMAML Attribute\r\nRequired? true required\r\nVariable Length? false variableLength\r\nAccept wildcard characters? false globbing\r\nAccept Pipeline Input? false pipelineInput\r\nPosition? named position\r\nValue Attributes\r\nName Value PSMAML Attribute\r\nRequired? true required\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 6 of 19\n\nName Value PSMAML Attribute\r\nVariable Length? false variableLength\r\nSpecifies an Active Directory user object by providing one of the following property values. The identifier in\r\nparentheses is the LDAP display name for the attribute.\r\nDistinguished Name\r\nExample: CN=SaraDavis,CN=Europe,CN=Users,DC=corp,DC=contoso,DC=com\r\nGUID (objectGUID)\r\nExample: 599c3d2e-f72d-4d20-8a88-030d99495f20\r\nSecurity Identifier (objectSid)\r\nExample: S-1-5-21-3165297888-301567370-576410423-1103\r\nSAM account name (sAMAccountName)\r\nExample: saradavis\r\nThe cmdlet searches the default naming context or partition to find the object. If two or more objects are found,\r\nthe cmdlet returns a non-terminating error.\r\nThis parameter can also get this object through the pipeline or you can set this parameter to an object instance.\r\nThis example shows how to set the parameter to a distinguished name.\r\n-Identity \"CN=SaraDavis,CN=Europe,CN=Users,DC=corp,DC=contoso,DC=com\"\r\nThis example shows how to set this parameter to a user object instance named \"userInstance\".\r\n-Identity $userInstance\r\nDefault Value: **\r\nData Type: ADUser\r\nAttributes\r\nName Value PSMAML Attribute\r\nRequired? true required\r\nVariable Length? false variableLength\r\nAccept wildcard characters? false globbing\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 7 of 19\n\nName Value PSMAML Attribute\r\nAccept Pipeline Input? true (ByValue) pipelineInput\r\nPosition? 1 position\r\nValue Attributes\r\nName Value PSMAML Attribute\r\nRequired? true required\r\nVariable Length? false variableLength\r\nSpecifies an LDAP query string that is used to filter Active Directory objects. You can use this parameter to run\r\nyour existing LDAP queries. The Filter parameter syntax supports the same functionality as the LDAP syntax. For\r\nmore information, see the Filter parameter description and the about_ActiveDirectory_Filter.\r\nThe following example shows how to set this parameter to search for all objects in the organizational unit\r\nspecified by the SearchBase parameter with a name beginning with \"sara\".\r\n-LDAPFilter \"(name=sara*)\" -SearchScope Subtree -SearchBase \"DC=NA,DC=fabrikam,DC=com\"\r\nDefault Value: **\r\nData Type: string\r\nAttributes\r\nName Value PSMAML Attribute\r\nRequired? true required\r\nVariable Length? false variableLength\r\nAccept wildcard characters? false globbing\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 8 of 19\n\nName Value PSMAML Attribute\r\nAccept Pipeline Input? false pipelineInput\r\nPosition? named position\r\nValue Attributes\r\nName Value PSMAML Attribute\r\nRequired? true required\r\nVariable Length? false variableLength\r\nSpecifies the distinguished name of an Active Directory partition. The distinguished name must be one of the\r\nnaming contexts on the current directory server. The cmdlet searches this partition to find the object defined by the\r\nIdentity parameter.\r\nThe following two examples show how to specify a value for this parameter.\r\n-Partition \"CN=Configuration,DC=EUROPE,DC=TEST,DC=CONTOSO,DC=COM\"\r\n-Partition \"CN=Schema,CN=Configuration,DC=EUROPE,DC=TEST,DC=CONTOSO,DC=COM\"\r\nIn many cases, a default value will be used for the Partition parameter if no value is specified. The rules for\r\ndetermining the default value are given below. Note that rules listed first are evaluated first and once a default\r\nvalue can be determined, no further rules will be evaluated.\r\nIn AD DS environments, a default value for Partition will be set in the following cases: - If the Identity parameter\r\nis set to a distinguished name, the default value of Partition is automatically generated from this distinguished\r\nname.\r\n- If running cmdlets from an Active Directory provider drive, the default value of Partition is automatically\r\ngenerated from the current path in the drive.\r\n- If none of the previous cases apply, the default value of Partition will be set to the default partition or naming\r\ncontext of the target domain.\r\nIn AD LDS environments, a default value for Partition will be set in the following cases:\r\n- If the Identity parameter is set to a distinguished name, the default value of Partition is automatically generated\r\nfrom this distinguished name.\r\n- If running cmdlets from an Active Directory provider drive, the default value of Partition is automatically\r\ngenerated from the current path in the drive.\r\n- If the target AD LDS instance has a default naming context, the default value of Partition will be set to the\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 9 of 19\n\ndefault naming context. To specify a default naming context for an AD LDS environment, set the msDS-defaultNamingContext property of the Active Directory directory service agent (DSA) object (nTDSDSA) for the\r\nAD LDS instance.\r\n- If none of the previous cases apply, the Partition parameter will not take any default value.\r\nDefault Value: **\r\nData Type: string\r\nAttributes\r\nName Value PSMAML Attribute\r\nRequired? false required\r\nVariable Length? false variableLength\r\nAccept wildcard characters? false globbing\r\nAccept Pipeline Input? false pipelineInput\r\nPosition? named position\r\nValue Attributes\r\nName Value PSMAML Attribute\r\nRequired? true required\r\nVariable Length? false variableLength\r\nSpecifies the properties of the output object to retrieve from the server. Use this parameter to retrieve properties\r\nthat are not included in the default set.\r\nSpecify properties for this parameter as a comma-separated list of names. To display all of the attributes that are\r\nset on the object, specify * (asterisk).\r\nTo specify an individual extended property, use the name of the property. For properties that are not default or\r\nextended properties, you must specify the LDAP display name of the attribute.\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 10 of 19\n\nTo retrieve properties and display them for an object, you can use the Get-* cmdlet associated with the object and\r\npass the output to the Get-Member cmdlet. The following examples show how to retrieve properties for a group\r\nwhere the Administrator's group is used as the sample group object.\r\nGet-ADGroup -Identity Administrators | Get-Member\r\nTo retrieve and display the list of all the properties for an ADGroup object, use the following command:\r\nGet-ADGroup -Identity Administrators -Properties *| Get-Member\r\nThe following examples show how to use the Properties parameter to retrieve individual properties as well as the\r\ndefault, extended or complete set of properties.\r\nTo retrieve the extended properties \"OfficePhone\" and \"Organization\" and the default properties of an ADUser\r\nobject named \"SaraDavis\", use the following command:\r\nGetADUser -Identity SaraDavis -Properties OfficePhone,Organization\r\nTo retrieve the properties with LDAP display names of \"otherTelephone\" and \"otherMobile\", in addition to the\r\ndefault properties for the same user, use the following command:\r\nGetADUser -Identity SaraDavis -Properties otherTelephone, otherMobile |Get-Member\r\nDefault Value: **\r\nData Type: string[]\r\nAttributes\r\nName Value PSMAML Attribute\r\nRequired? false required\r\nVariable Length? true variableLength\r\nAccept wildcard characters? false globbing\r\nAccept Pipeline Input? false pipelineInput\r\nPosition? named position\r\nValue Attributes\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 11 of 19\n\nName Value PSMAML Attribute\r\nRequired? true required\r\nVariable Length? true variableLength\r\nSpecifies the number of objects to include in one page for an Active Directory Domain Services query.\r\nThe default is 256 objects per page.\r\nThe following example shows how to set this parameter.\r\n-ResultPageSize 500\r\nDefault Value: 256\r\nData Type: int\r\nAttributes\r\nName Value PSMAML Attribute\r\nRequired? false required\r\nVariable Length? false variableLength\r\nAccept wildcard characters? false globbing\r\nAccept Pipeline Input? false pipelineInput\r\nPosition? named position\r\nValue Attributes\r\nName Value PSMAML Attribute\r\nRequired? true required\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 12 of 19\n\nName Value PSMAML Attribute\r\nVariable Length? false variableLength\r\nSpecifies the maximum number of objects to return for an Active Directory Domain Services query. If you want to\r\nreceive all of the objects, set this parameter to $null (null value). You can use Ctrl+c to stop the query and return\r\nof objects.\r\nThe default is $null.\r\nThe following example shows how to set this parameter so that you receive all of the returned objects.\r\n-ResultSetSize $null\r\nDefault Value: **\r\nData Type: System.Nullable[System.Int32]\r\nAttributes\r\nName Value PSMAML Attribute\r\nRequired? false required\r\nVariable Length? false variableLength\r\nAccept wildcard characters? false globbing\r\nAccept Pipeline Input? false pipelineInput\r\nPosition? named position\r\nValue Attributes\r\nName Value PSMAML Attribute\r\nRequired? true required\r\nVariable Length? false variableLength\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 13 of 19\n\nSpecifies an Active Directory path to search under.\r\nWhen you run a cmdlet from an Active Directory provider drive, the default value of this parameter is the current\r\npath of the drive.\r\nWhen you run a cmdlet outside of an Active Directory provider drive against an AD DS target, the default value of\r\nthis parameter is the default naming context of the target domain.\r\nWhen you run a cmdlet outside of an Active Directory provider drive against an AD LDS target, the default value\r\nis the default naming context of the target LDS instance if one has been specified by setting the msDS-defaultNamingContext property of the Active Directory directory service agent (DSA) object (nTDSDSA) for the\r\nAD LDS instance. If no default naming context has been specified for the target AD LDS instance, then this\r\nparameter has no default value.\r\nThe following example shows how to set this parameter to search under an OU.\r\n-SearchBase \"ou=mfg,dc=noam,dc=corp,dc=contoso,dc=com\"\r\nWhen the value of the SearchBase parameter is set to an empty string and you are connected to a GC port, all\r\npartitions will be searched. If the value of the SearchBase parameter is set to an empty string and you are not\r\nconnected to a GC port, an error will be thrown.\r\nThe following example shows how to set this parameter to an empty string. -SearchBase \"\"\r\nDefault Value: **\r\nData Type: string\r\nAttributes\r\nName Value PSMAML Attribute\r\nRequired? false required\r\nVariable Length? false variableLength\r\nAccept wildcard characters? false globbing\r\nAccept Pipeline Input? false pipelineInput\r\nPosition? named position\r\nValue Attributes\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 14 of 19\n\nName Value PSMAML Attribute\r\nRequired? true required\r\nVariable Length? false variableLength\r\nSpecifies the scope of an Active Directory search. Possible values for this parameter are:\r\nBase or 0\r\nOneLevel or 1\r\nSubtree or 2\r\nA Base query searches only the current path or object. A OneLevel query searches the immediate children of that\r\npath or object. A Subtree query searches the current path or object and all children of that path or object.\r\nThe following example shows how to set this parameter to a subtree search.\r\n-SearchScope Subtree\r\nThe following lists the acceptable values for this parameter:\r\nBase**\r\nOneLevel**\r\nSubtree**\r\nDefault Value: Subtree\r\nData Type: ADSearchScope\r\nAttributes\r\nName Value PSMAML Attribute\r\nRequired? false required\r\nVariable Length? false variableLength\r\nAccept wildcard characters? false globbing\r\nAccept Pipeline Input? false pipelineInput\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 15 of 19\n\nName Value PSMAML Attribute\r\nPosition? named position\r\nValue Attributes\r\nName Value PSMAML Attribute\r\nRequired? true required\r\nVariable Length? false variableLength\r\nSpecifies the Active Directory Domain Services instance to connect to, by providing one of the following values\r\nfor a corresponding domain name or directory server. The service may be any of the following: Active Directory\r\nLightweight Domain Services, Active Directory Domain Services or Active Directory Snapshot instance.\r\nDomain name values:\r\nFully qualified domain name\r\nExamples: corp.contoso.com\r\nNetBIOS name\r\nExample: CORP\r\nDirectory server values:\r\nFully qualified directory server name\r\nExample: corp-DC12.corp.contoso.com\r\nNetBIOS name\r\nExample: corp-DC12\r\nFully qualified directory server name and port\r\nExample: corp-DC12.corp.contoso.com:3268\r\nThe default value for the Server parameter is determined by one of the following methods in the order that they\r\nare listed:\r\n-By using Server value from objects passed through the pipeline.\r\n-By using the server information associated with the Active Directory PowerShell provider drive, when running\r\nunder that drive.\r\n-By using the domain of the computer running Powershell.\r\nThe following example shows how to specify a full qualified domain name as the parameter value.\r\n-Server \"corp.contoso.com\"\r\nDefault Value: **\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 16 of 19\n\nData Type: string\r\nAttributes\r\nName Value PSMAML Attribute\r\nRequired? false required\r\nVariable Length? false variableLength\r\nAccept wildcard characters? false globbing\r\nAccept Pipeline Input? false pipelineInput\r\nPosition? named position\r\nValue Attributes\r\nName Value PSMAML Attribute\r\nRequired? true required\r\nVariable Length? false variableLength\r\nA user object is received by the Identity parameter.\r\nReturns one or more user objects.\r\nThis cmdlet returns a default set of ADUser property values. To retrieve additional ADUser properties, use the\r\nProperties parameter.\r\nTo get a list of the default set of properties of an ADUser object, use the following command:\r\nGet-ADUser \u003cuser\u003e| Get-Member\r\nTo get a list of the most commonly used properties of an ADUser object, use the following command:\r\nGet-ADUser \u003cuser\u003e -Properties Extended | Get-Member\r\nTo get a list of all the properties of an ADUser object, use the following command:\r\nGet-ADUser \u003cuser\u003e -Properties * | Get-Member\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 17 of 19\n\nThis cmdlet does not work with an Active Directory Snapshot.\r\nCommand Prompt: C:\\PS\u003e\r\nGet-ADUser -Filter * -SearchBase \"OU=Finance,OU=UserAccounts,DC=FABRIKAM,DC=COM\"\r\n \r\nGet all users under the container 'OU=Finance,OU=UserAccounts,DC=FABRIKAM,DC=COM'.\r\nCommand Prompt: C:\\PS\u003e\r\nGet-ADUser -Filter 'Name -like \"*SvcAccount\"' | FT Name,SamAccountName -A\r\n \r\nName SamAccountName\r\n---- --------------\r\nSQL01 SvcAccount SQL01\r\nSQL02 SvcAccount SQL02\r\nIIS01 SvcAccount IIS01\r\nDescription\r\n-----------\r\nGet all users that have a name that ends with 'SvcAccount'.\r\nCommand Prompt: C:\\PS\u003e\r\nGet-ADUser GlenJohn -Properties *\r\n \r\nSurname : John\r\nName : Glen John\r\nUserPrincipalName :\r\nGivenName : Glen\r\nEnabled : False\r\nSamAccountName : GlenJohn\r\nObjectClass : user\r\nSID : S-1-5-21-2889043008-4136710315-2444824263-3544\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 18 of 19\n\nObjectGUID : e1418d64-096c-4cb0-b903-ebb66562d99d\r\nDistinguishedName : CN=Glen\r\nJohn,OU=NorthAmerica,OU=Sales,OU=UserAccounts,DC=FABRIKAM,DC=COM\r\nDescription\r\n-----------\r\nGet all properties of the user with samAccountName 'GlenJohn'.\r\nCommand Prompt: C:\\PS\u003e\r\nGet-ADUser -Filter {Name -eq \"GlenJohn\"} -SearchBase \"DC=AppNC\" -Properties mail -Server lds.Fabrikam.com:50000\r\nGet the user with name 'GlenJohn' on the AD LDS instance.\r\nNew-ADUser\r\nSet-ADUser\r\nRemove-ADUser\r\nOnline version:\r\nSource: https://technet.microsoft.com/library/ee617241.aspx\r\nhttps://technet.microsoft.com/library/ee617241.aspx\r\nPage 19 of 19",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"origins": [
		"web"
	],
	"references": [
		"https://technet.microsoft.com/library/ee617241.aspx"
	],
	"report_names": [
		"ee617241.aspx"
	],
	"threat_actors": [
		{
			"id": "2864e40a-f233-4618-ac61-b03760a41cbb",
			"created_at": "2023-12-01T02:02:34.272108Z",
			"updated_at": "2026-04-10T02:00:04.97558Z",
			"deleted_at": null,
			"main_name": "WildCard",
			"aliases": [],
			"source_name": "ETDA:WildCard",
			"tools": [
				"RustDown",
				"SysJoker"
			],
			"source_id": "ETDA",
			"reports": null
		},
		{
			"id": "256a6a2d-e8a2-4497-b399-628a7fad4b3e",
			"created_at": "2023-11-30T02:00:07.299845Z",
			"updated_at": "2026-04-10T02:00:03.484788Z",
			"deleted_at": null,
			"main_name": "WildCard",
			"aliases": [],
			"source_name": "MISPGALAXY:WildCard",
			"tools": [],
			"source_id": "MISPGALAXY",
			"reports": null
		}
	],
	"ts_created_at": 1775441515,
	"ts_updated_at": 1775826737,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/f56b17bef39ac8a5ee5c4d3b227cc52c39b23529.pdf",
		"text": "https://archive.orkl.eu/f56b17bef39ac8a5ee5c4d3b227cc52c39b23529.txt",
		"img": "https://archive.orkl.eu/f56b17bef39ac8a5ee5c4d3b227cc52c39b23529.jpg"
	}
}