With this script, you will be able to monitor the user object status in the Active Directory. The script performs these steps
- set the domain controller list : one dc per domain you want to retrieve the informations
- create an array that contains the disabled user objects
- create an array that contains the user objects with the parameter “Password never expires” enabled
- create an array that contains the inactive user objects (inactive for more than 100 days)
- create an array that contains the locked out user objects
- for each domain controller, create an array that contains all user objects
The final result output is an array with 5 columns : the first column contains the object distinguished names and the others contain the status ($true or $false) for each category (disabled, password never expires, inactive and locked out). This array is also exported as a csv file.
import-module activedirectory # setup vars $array = @() # set the domain controller list : one dc per domain you want to retrieve the informations $dc_array = "dc01.domain1.local" , "dc01.domain2.local" , "dc01.domain3.local" # create an array that contains the disabled user objects $disable_account_list = Get-ADObject -LDAPFilter "(&(objectCategory=person)(objectClass=user)(userAccountControl:1.2.840.113556.1.4.803:=2))" # create an array that contains the user objects with the parameter "Password never expire" enabled $password_never_expire = Get-ADObject -LDAPFilter "(&(objectCategory=person)(objectClass=user)(userAccountControl:1.2.840.113556.1.4.803:=65536))" # create an array that contains the inactive user objects (inactive for more than 100 days) $inactive_user_account = search-adaccount -accountinactive -usersonly -timespan "100" # create an array that contains the locked out user objects $lockedout_user_account = $dc_array | % { search-adaccount -lockedout -server $_ } # for each domain controller, create an array that contains all user objects $all = $dc_array | % {Get-ADObject -LDAPFilter "(&(objectCategory=person)(objectClass=user))" -ResultSetSize $null -Properties WhenCreated,DistinguishedName,name,samaccountname -Server $_} $all | % { $loop_entry = $_ $loop_entry_dn = $loop_entry.DistinguishedName $loop_entry_san = $loop_entry.samaccountname $is_disabled = $false $is_never_exp = $false $is_inactive = $false $is_lockedout = $false $orig_lock = "Not Available" switch ($loop_entry_dn){ {$disable_account_list -match $loop_entry_dn}{ $is_disabled = $true } {$password_never_expire -match $loop_entry_dn}{ $is_never_exp = $true } {$inactive_user_account -match $loop_entry_dn}{ $is_inactive = $true } {$lockedout_user_account -match $loop_entry_dn}{ $is_lockedout = $true } default { continue } } $Properties = @{ObjectDN=$loop_entry_dn;isDisabled=$is_disabled;PasswordNeverExpires=$is_never_exp;isInactive=$is_inactive;isLockedOut=$is_lockedout;origLock=$orig_lock} $Newobject = New-Object PSObject -Property $Properties $array +=$newobject } $array | ConvertTo-Csv -NoTypeInformation -Delimiter ";" | Foreach-Object {$_ -replace '"', ''} | Out-File c:\temp\ad_users.tmp -Encoding ASCII Move-Item -Path c:\temp\ad_users.tmp -Destination c:\temp\ad_users.csv -Force
Reference
Syntax
Get-ADObject -Filter[-ResultPageSize ] [-ResultSetSize ] [-SearchBase ] [-SearchScope { | | }] [-AuthType { | }] [-Credential ] [-IncludeDeletedObjects ] [-Partition ] [-Properties ] [-Server ] [ ]
- Filter
- ResultPageSize
- ResultSetSize
- SearchBase
- SearchScope
- AuthType
- Credential
- IncludeDeletedObjects
- Partition
- Properties
- Server
Get-ADObject [-Identity][-AuthType { | }] [-Credential ] [-IncludeDeletedObjects ] [-Partition ] [-Properties ] [-Server ] [ ]
- Identity
- AuthType
- Credential
- IncludeDeletedObjects
- Partition
- Properties
- Server
Get-ADObject -LDAPFilter[-ResultPageSize ] [-ResultSetSize ] [-SearchBase ] [-SearchScope { | | }] [-AuthType { | }] [-Credential ] [-IncludeDeletedObjects ] [-Partition ] [-Properties ] [-Server ] [ ]
- LDAPFilter
- ResultPageSize
- ResultSetSize
- SearchBase
- SearchScope
- AuthType
- Credential
- IncludeDeletedObjects
- Partition
- Properties
- Server
Detailed Description
The Get-ADObject cmdlet gets an Active Directory object or performs a search to retrieve multiple objects.
The Identity parameter specifies the Active Directory object to get. You can identify the object to get by its distinguished name (DN) or GUID. You can also set the parameter to an Active Directory object variable, such as $<localADObject> or pass an object through the pipeline to the Identity parameter.
To search for and retrieve more than one object, use the Filter or LDAPFilter parameters. The Filter parameter uses the PowerShell Expression Language to write query strings for Active Directory. PowerShell Expression Language syntax provides rich type conversion support for value types received by the Filter parameter. For more information about the Filter parameter syntax, see about_ActiveDirectory_Filter. If you have existing LDAP query strings, you can use the LDAPFilter parameter.
This cmdlet gets a default set of Active Directory object properties. To get additional properties use the Properties parameter. For more information about the how to determine the properties for computer objects, see the Properties parameter description.
Parameters
AuthType
Specifies the authentication method to use. Possible values for this parameter include:
Negotiate or 0
Basic or 1
The default authentication method is Negotiate.
A Secure Sockets Layer (SSL) connection is required for the Basic authentication method.
The following example shows how to set this parameter to Basic.
-AuthType Basic
The following lists the acceptable values for this parameter:
- Negotiate
- Basic
Default Value: Microsoft.ActiveDirectory.Management.AuthType.Negotiate
Data Type: ADAuthType
Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | false | required |
Variable Length? | false | variableLength |
Accept wildcard characters? | false | globbing |
Accept Pipeline Input? | false | pipelineInput |
Position? | named | position |
Value Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
Credential
Specifies the user account credentials to use to perform this task. The default credentials are the credentials of the currently logged on user unless the cmdlet is run from an Active Directory PowerShell provider drive. If the cmdlet is run from such a provider drive, the account associated with the drive is the default.
To specify this parameter, you can type a user name, such as “User1” or “Domain01\User01” or you can specify a PSCredential object. If you specify a user name for this parameter, the cmdlet prompts for a password.
You can also create a PSCredential object by using a script or by using the Get-Credential cmdlet. You can then set the Credential parameter to the PSCredential object The following example shows how to create credentials.
$AdminCredentials = Get-Credential “Domain01\User01”
The following shows how to set the Credential parameter to these credentials.
-Credential $AdminCredentials
If the acting credentials do not have directory-level permission to perform the task, Active Directory PowerShell returns a terminating error.
Default Value:
Data Type: PSCredential
Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | false | required |
Variable Length? | false | variableLength |
Accept wildcard characters? | false | globbing |
Accept Pipeline Input? | false | pipelineInput |
Position? | named | position |
Value Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
Filter
Specifies a query string that retrieves Active Directory objects. This string uses the PowerShell Expression Language syntax. The PowerShell Expression Language syntax provides rich type-conversion support for value types received by the Filter parameter. The syntax uses an in-order representation, which means that the operator is placed between the operand and the value. For more information about the Filter parameter, see about_ActiveDirectory_Filter.
Syntax:
The following syntax uses Backus-Naur form to show how to use the PowerShell Expression Language for this parameter.
<filter> ::= “{” <FilterComponentList> “}”
<FilterComponentList> ::= <FilterComponent> | <FilterComponent> <JoinOperator> <FilterComponent> | <NotOperator> <FilterComponent>
<FilterComponent> ::= <attr> <FilterOperator> <value> | “(” <FilterComponent> “)”
<FilterOperator> ::= “-eq” | “-le” | “-ge” | “-ne” | “-lt” | “-gt”| “-approx” | “-bor” | “-band” | “-recursivematch” | “-like” | “-notlike”
<JoinOperator> ::= “-and” | “-or”
<NotOperator> ::= “-not”
<attr> ::= <PropertyName> | <LDAPDisplayName of the attribute>
<value>::= <compare this value with an <attr> by using the specified <FilterOperator>>
For a list of supported types for <value>, see about_ActiveDirectory_ObjectModel.
Examples:
The following examples show how to use this syntax with Active Directory cmdlets.
To get all objects of the type specified by the cmdlet, use the asterisk wildcard:
All user objects:
Get-ADUser -Filter *
-or-
All computer objects:
Get-ADComputer -Filter *
To get all user objects that have an e-mail message attribute, use one of the following commands:
Get-ADUser -Filter {EmailAddress -like “*”}
Get-ADUser -Filter {mail -like “*”}
-or-
Get-ADObject -Filter {(mail -like “*”) -and (ObjectClass -eq “user”)}
Note: PowerShell wildcards other than “*”, such as “?” are not supported by the Filter syntax.
To get all users objects that have surname of Smith and that have an e-mail attribute, use one of the following commands:
Get-ADUser -filter {(EmailAddress -like “*”) -and (Surname -eq “smith”)}
-or-
Get-ADUser -filter {(mail -eq “*”) -and (sn -eq “Smith”)}
To get all user objects who have not logged on since January 1, 2007, use the following commands:
$logonDate = New-Object System.DateTime(2007, 1, 1)
Get-ADUser -filter { lastLogon -le $logonDate }
To get all groups that have a group category of Security and a group scope of Global, use one of the following commands:
Get-ADGroup -filter {GroupCategory -eq “Security” -and GroupScope -eq “Global”}
-or-
Get-ADGroup -filter {GroupType -band 0x80000000}
Note: To query using LDAP query strings, use the LDAPFilter parameter.
Default Value:
Data Type: string
Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
Accept wildcard characters? | false | globbing |
Accept Pipeline Input? | false | pipelineInput |
Position? | named | position |
Value Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
Identity
Specifies an Active Directory object by providing one of the following property values. The identifier in parentheses is the LDAP display name for the attribute.
Distinguished Name
Example: CN=saradavis,OU=users,OU=asia,DC=corp,DC=contoso,DC=com
GUID (objectGUID)
Example: 599c3d2e-f72d-4d20-8a88-030d99495f20
The cmdlet searches the default naming context or partition to find the object. If two or more objects are found, the cmdlet returns a non-terminating error.
This parameter can also get this object through the pipeline or you can set this parameter to an object instance.
Derived types, such as the following are also accepted:
Microsoft.ActiveDirectory.Management.ADGroup
Microsoft.ActiveDirectory.Management.ADUser
Microsoft.ActiveDirectory.Management.ADComputer
Microsoft.ActiveDirectory.Management.ADServiceAccount
Microsoft.ActiveDirectory.Management.ADFineGrainedPasswordPolicy
Microsoft.ActiveDirectory.Management.ADDomain
This example shows how to set this parameter to an ADObject object instance named “ADObjectInstance”.
-Identity $ADObjectInstance
Default Value:
Data Type: ADObject
Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
Accept wildcard characters? | false | globbing |
Accept Pipeline Input? | true (ByValue) | pipelineInput |
Position? | 1 | position |
Value Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
IncludeDeletedObjects
Specifies to retrieve deleted objects and the deactivated forward and backward links. When this parameter is specified, the cmdlet uses the following LDAP controls:
Show Deleted Objects (1.2.840.113556.1.4.417)
Show Deactivated Links (1.2.840.113556.1.4.2065)
Note: If this parameter is not specified, the cmdlet will not return or operate on deleted objects.
Default Value:
Data Type: switch
Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | false | required |
Variable Length? | false | variableLength |
Accept wildcard characters? | false | globbing |
Accept Pipeline Input? | false | pipelineInput |
Position? | named | position |
Value Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
LDAPFilter
Specifies an LDAP query string that is used to filter Active Directory objects. You can use this parameter to run your existing LDAP queries. The Filter parameter syntax supports the same functionality as the LDAP syntax. For more information, see the Filter parameter description and the about_ActiveDirectory_Filter.
The following example shows how to set this parameter to search for all objects in the organizational unit specified by the SearchBase parameter with a name beginning with “sara”.
-LDAPFilter “(name=sara*)” -SearchScope Subtree -SearchBase “DC=NA,DC=fabrikam,DC=com”
Default Value:
Data Type: string
Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
Accept wildcard characters? | false | globbing |
Accept Pipeline Input? | false | pipelineInput |
Position? | named | position |
Value Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
Partition
Specifies the distinguished name of an Active Directory partition. The distinguished name must be one of the naming contexts on the current directory server. The cmdlet searches this partition to find the object defined by the Identity parameter.
The following two examples show how to specify a value for this parameter.
-Partition “CN=Configuration,DC=EUROPE,DC=TEST,DC=CONTOSO,DC=COM”
-Partition “CN=Schema,CN=Configuration,DC=EUROPE,DC=TEST,DC=CONTOSO,DC=COM”
In many cases, a default value will be used for the Partition parameter if no value is specified. The rules for determining the default value are given below. Note that rules listed first are evaluated first and once a default value can be determined, no further rules will be evaluated.
In AD DS environments, a default value for Partition will be set in the following cases: – If the Identity parameter is set to a distinguished name, the default value of Partition is automatically generated from this distinguished name.
– If running cmdlets from an Active Directory provider drive, the default value of Partition is automatically generated from the current path in the drive.
– If none of the previous cases apply, the default value of Partition will be set to the default partition or naming context of the target domain.
In AD LDS environments, a default value for Partition will be set in the following cases:
– If the Identity parameter is set to a distinguished name, the default value of Partition is automatically generated from this distinguished name.
– If running cmdlets from an Active Directory provider drive, the default value of Partition is automatically generated from the current path in the drive.
– If the target AD LDS instance has a default naming context, the default value of Partition will be set to the default 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 AD LDS instance.
– If none of the previous cases apply, the Partition parameter will not take any default value.
Default Value:
Data Type: string
Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | false | required |
Variable Length? | false | variableLength |
Accept wildcard characters? | false | globbing |
Accept Pipeline Input? | false | pipelineInput |
Position? | named | position |
Value Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
Properties
Specifies the properties of the output object to retrieve from the server. Use this parameter to retrieve properties that are not included in the default set.
Specify properties for this parameter as a comma-separated list of names. To display all of the attributes that are set on the object, specify * (asterisk).
To specify an individual extended property, use the name of the property. For properties that are not default or extended properties, you must specify the LDAP display name of the attribute.
To retrieve properties and display them for an object, you can use the Get-* cmdlet associated with the object and pass the output to the Get-Member cmdlet. The following examples show how to retrieve properties for a group where the Administrator’s group is used as the sample group object.
Get-ADGroup -Identity Administrators | Get-Member
To retrieve and display the list of all the properties for an ADGroup object, use the following command:
Get-ADGroup -Identity Administrators -Properties *| Get-Member
The following examples show how to use the Properties parameter to retrieve individual properties as well as the default, extended or complete set of properties.
To retrieve the extended properties “OfficePhone” and “Organization” and the default properties of an ADUser object named “SaraDavis”, use the following command:
GetADUser -Identity SaraDavis -Properties OfficePhone,Organization
To retrieve the properties with LDAP display names of “otherTelephone” and “otherMobile”, in addition to the default properties for the same user, use the following command:
GetADUser -Identity SaraDavis -Properties otherTelephone, otherMobile |Get-Member
Default Value:
Data Type: string[]
Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | false | required |
Variable Length? | true | variableLength |
Accept wildcard characters? | false | globbing |
Accept Pipeline Input? | false | pipelineInput |
Position? | named | position |
Value Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | true | variableLength |
ResultPageSize
Specifies the number of objects to include in one page for an Active Directory Domain Services query.
The default is 256 objects per page.
The following example shows how to set this parameter.
-ResultPageSize 500
Default Value: 256
Data Type: int
Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | false | required |
Variable Length? | false | variableLength |
Accept wildcard characters? | false | globbing |
Accept Pipeline Input? | false | pipelineInput |
Position? | named | position |
Value Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
ResultSetSize
Specifies the maximum number of objects to return for an Active Directory Domain Services query. If you want to receive all of the objects, set this parameter to $null (null value). You can use Ctrl+c to stop the query and return of objects.
The default is $null.
The following example shows how to set this parameter so that you receive all of the returned objects.
-ResultSetSize $null
Default Value:
Data Type: System.Nullable[System.Int32]
Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | false | required |
Variable Length? | false | variableLength |
Accept wildcard characters? | false | globbing |
Accept Pipeline Input? | false | pipelineInput |
Position? | named | position |
Value Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
SearchBase
Specifies an Active Directory path to search under.
When you run a cmdlet from an Active Directory provider drive, the default value of this parameter is the current path of the drive.
When you run a cmdlet outside of an Active Directory provider drive against an AD DS target, the default value of this parameter is the default naming context of the target domain.
When you run a cmdlet outside of an Active Directory provider drive against an AD LDS target, the default value is 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 AD LDS instance. If no default naming context has been specified for the target AD LDS instance, then this parameter has no default value.
The following example shows how to set this parameter to search under an OU.
-SearchBase “ou=mfg,dc=noam,dc=corp,dc=contoso,dc=com”
When the value of the SearchBase parameter is set to an empty string and you are connected to a GC port, all partitions will be searched. If the value of the SearchBase parameter is set to an empty string and you are not connected to a GC port, an error will be thrown.
The following example shows how to set this parameter to an empty string. -SearchBase “”
Default Value:
Data Type: string
Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | false | required |
Variable Length? | false | variableLength |
Accept wildcard characters? | false | globbing |
Accept Pipeline Input? | false | pipelineInput |
Position? | named | position |
Value Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
SearchScope
Specifies the scope of an Active Directory search. Possible values for this parameter are:
Base or 0
OneLevel or 1
Subtree or 2
A Base query searches only the current path or object. A OneLevel query searches the immediate children of that path or object. A Subtree query searches the current path or object and all children of that path or object.
The following example shows how to set this parameter to a subtree search.
-SearchScope Subtree
The following lists the acceptable values for this parameter:
- Base
- OneLevel
- Subtree
Default Value: Subtree
Data Type: ADSearchScope
Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | false | required |
Variable Length? | false | variableLength |
Accept wildcard characters? | false | globbing |
Accept Pipeline Input? | false | pipelineInput |
Position? | named | position |
Value Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
Server
Specifies the Active Directory Domain Services instance to connect to, by providing one of the following values for a corresponding domain name or directory server. The service may be any of the following: Active Directory Lightweight Domain Services, Active Directory Domain Services or Active Directory Snapshot instance.
Domain name values:
Fully qualified domain name
Examples: corp.contoso.com
NetBIOS name
Example: CORP
Directory server values:
Fully qualified directory server name
Example: corp-DC12.corp.contoso.com
NetBIOS name
Example: corp-DC12
Fully qualified directory server name and port
Example: corp-DC12.corp.contoso.com:3268
The default value for the Server parameter is determined by one of the following methods in the order that they are listed:
-By using Server value from objects passed through the pipeline.
-By using the server information associated with the Active Directory PowerShell provider drive, when running under that drive.
-By using the domain of the computer running Powershell.
The following example shows how to specify a full qualified domain name as the parameter value.
-Server “corp.contoso.com”
Default Value:
Data Type: string
Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | false | required |
Variable Length? | false | variableLength |
Accept wildcard characters? | false | globbing |
Accept Pipeline Input? | false | pipelineInput |
Position? | named | position |
Value Attributes
Name | Value | PSMAML Attribute |
---|---|---|
Required? | true | required |
Variable Length? | false | variableLength |
Examples
————————– EXAMPLE 1 ————————–
Get-ADObject -LDAPFilter "(objectClass=site)" -SearchBase 'CN=Configuration,DC=Fabrikam,DC=Com' -Properties CanonicalName | FT Name,CanonicalName -A
Name CanonicalName
—- ————-
HQ FABRIKAM.COM/Configuration/Sites/HQ
BO1 FABRIKAM.COM/Configuration/Sites/BO1
BO2 FABRIKAM.COM/Configuration/Sites/BO2
BO3 FABRIKAM.COM/Configuration/Sites/BO3
Description
———–
Displays a list of sites for Fabrikam using the LDAP filter syntax.
————————– EXAMPLE 2 ————————–
Get-ADObject -Filter 'ObjectClass -eq "site"' -SearchBase 'CN=Configuration,DC=Fabrikam,DC=Com' -Properties siteObjectBL | foreach {$_.siteObjectBL}
CN=192.167.1.0/26,CN=Subnets,CN=Sites,CN=Configuration,DC=FABRIKAM,DC=COM
CN=192.166.1.0/26,CN=Subnets,CN=Sites,CN=Configuration,DC=FABRIKAM,DC=COM
CN=192.168.1.0/26,CN=Subnets,CN=Sites,CN=Configuration,DC=FABRIKAM,DC=COM
CN=192.165.1.0/26,CN=Subnets,CN=Sites,CN=Configuration,DC=FABRIKAM,DC=COM
CN=192.164.1.0/26,CN=Subnets,CN=Sites,CN=Configuration,DC=FABRIKAM,DC=COM
CN=192.163.1.0/26,CN=Subnets,CN=Sites,CN=Configuration,DC=FABRIKAM,DC=COM
CN=192.162.1.0/26,CN=Subnets,CN=Sites,CN=Configuration,DC=FABRIKAM,DC=COM
CN=192.161.1.0/26,CN=Subnets,CN=Sites,CN=Configuration,DC=FABRIKAM,DC=COM
CN=192.160.1.0/26,CN=Subnets,CN=Sites,CN=Configuration,DC=FABRIKAM,DC=COM
CN=192.159.1.0/26,CN=Subnets,CN=Sites,CN=Configuration,DC=FABRIKAM,DC=COM
CN=192.158.1.0/26,CN=Subnets,CN=Sites,CN=Configuration,DC=FABRIKAM,DC=COM
CN=192.157.1.0/26,CN=Subnets,CN=Sites,CN=Configuration,DC=FABRIKAM,DC=COM
Description
———–
Gets the Site objects from the Configuration Naming Context and then enumerates through the list outputting ‘siteObjectBL’.
————————– EXAMPLE 3 ————————–
$changeDate = New-Object DateTime(2008, 11, 18, 1, 40, 02); Get-ADObject -Filter 'whenChanged -gt $changeDate' -IncludeDeletedObjects
Gets all the objects, including the deleted ones, whose ‘whenChanged’ attribute is greater than the specified date. Note that both deleted and non-deleted (and non-recycled) objects matching the filter will be returned.
————————– EXAMPLE 4 ————————–
$changeDate = New-Object DateTime(2008, 11, 18, 1, 40, 02) Get-ADObject –Filter 'whenChanged -gt $changeDate -and isDeleted -eq $true -and -not (isRecycled -eq $true) -and name -ne "Deleted Objects"' –IncludeDeletedObjects
ObjectGUID : 98118958-91c7-437d-8ada-ba0b66db823b
Deleted : True
DistinguishedName : CN=Andrew Ma\0ADEL:98118958-91c7-437d-8ada-ba0b66db823b,CN=Deleted Objects,DC=FABRIKAM,DC=COM
Name : Andrew Ma
DEL:98118958-91c7-437d-8ada-ba0b66db823b
ObjectClass : user
Description
———–
Gets all the deleted objects, whose ‘whenChanged’ attribute is greater than the specified date. The clause ‘name -ne “Deleted Objects”‘ makes sure that the Deleted Objects Container is not returned. This will only return objects which can be restored
————————– EXAMPLE 5 ————————–
$changeDate = New-Object DateTime(2008, 11, 18, 1, 40, 02) Get-ADObject –Filter 'whenChanged -gt $changeDate -and isDeleted -eq $true -and -not (isRecycled -eq $true) -and lastKnownParent -eq "OU=Accounting,DC=Fabrikam,DC=com"' –IncludeDeletedObjects
ObjectGUID : 12d53e7f-aaf7-4790-b41a-da19044504db
Deleted : True
DistinguishedName : CN=Craig Dewar\0ADEL:12d53e7f-aaf7-4790-b41a-da19044504db,CN=Deleted Objects,DC=Fabrikam,DC=com
Name : Craig Dewar
DEL:12d53e7f-aaf7-4790-b41a-da19044504db
ObjectClass : user
Description
———–
Gets all the deleted objects whose ‘whenChanged’ attribute is greater then the specified date AND at the time of deletion were the children of the specified Organizational Unit.
————————– EXAMPLE 6 ————————–
Get-ADObject -Identity "DC=AppNC" -server "FABRIKAM-SRV1:60000"
ObjectGUID DistinguishedName Name ObjectClass
———- —————– —- ———–
62b2e185-9322-4980-9c93-cf… DC=AppNC AppNC domainDNS
Description
———–
Gets the information of the domainDNS object of an LDS instance