In developing a custom PowerShell script which leveraged ADSI, I noticed that the script wasn\u2019t working properly.<\/p>\n
Here\u2019s a sample block of the script which uses ADSI to get changes made to ExtensionAttribute11 as part of an Active Directory Convergence test script:<\/p>\n
| \n 1 \n2 \n3 \n4<\/div>\n<\/td>\n \n | $ADSITarget = [ADSI]”LDAP:\/\/$DC” \n$Searcher = New-Object DirectoryServices.DirectorySearcher($ADSITarget,”(sAMAccountName=$ConvergenceObject)”) \n$ConvergenceObjectData = ($Searcher.FindOne()).properties \n$ConvergenceObjectDataValue = (($Searcher.FindOne()).properties).ExtensionAttribute11<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n I usually use Title Case when typing attributes and the script block above was not populating the variable \u201c$ConvergenceObjectDataValue\u201d with any data even though the attribute had data. I realized after enumerating the variable $ConvergenceObjectData that the attribute name was displayed as extensionattribute11 <\/strong>not E<\/strong>xtensionA<\/strong>ttribute11.\u00a0 After changing line #1 to line #2, it worked:<\/p>\n Line #1: Line #2: So, be careful when using ADSI (or any other API) since it may be case sensitive.<\/p>\n","protected":false},"excerpt":{"rendered":" In developing a custom PowerShell script which leveraged ADSI, I noticed that the script wasn\u2019t working properly. Here\u2019s a sample block of the script which uses ADSI to get changes made to ExtensionAttribute11 as part of an Active Directory Convergence test script: 1 2 3 4 $ADSITarget = [ADSI]”LDAP:\/\/$DC” $Searcher = New-Object DirectoryServices.DirectorySearcher($ADSITarget,”(sAMAccountName=$ConvergenceObject)”) $ConvergenceObjectData = … <\/p>\n |