<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Splunk Support for Active Directory: After running an ldapsearch, why does accountExpires or Enabled properties not populating data? in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Support-for-Active-Directory-After-running-an-ldapsearch/m-p/260337#M30003</link>
    <description>&lt;P&gt;I was able to resolve this issue and since no one posted an answer I'll write what I found. &lt;/P&gt;

&lt;P&gt;It turns out that accountExpires and Enabled and not true LDAP attributes, but part of the Win32_UserAccount class.  It can be accessed via WMI and Powershell commands easily, but since they are not true LDAP attributes ldapsearch won't bring in those objects.   This information can be obtained through the Splunk TA for Windows infrastructure or imported via csv file produced from a PowerShell output.  &lt;/P&gt;</description>
    <pubDate>Fri, 07 Apr 2017 14:30:17 GMT</pubDate>
    <dc:creator>sfefcu</dc:creator>
    <dc:date>2017-04-07T14:30:17Z</dc:date>
    <item>
      <title>Splunk Support for Active Directory: After running an ldapsearch, why does accountExpires or Enabled properties not populating data?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Support-for-Active-Directory-After-running-an-ldapsearch/m-p/260336#M30002</link>
      <description>&lt;P&gt;Using Splunk Support for Active Directory 2.1.3. &lt;/P&gt;

&lt;P&gt;When we run an ldapsearch to get accountExpires or Enabled properties, no data comes back.  When we run a similar search using PowerShell on Active Directory, a value such as "9223372036854775807" for accountExpires and (True or False) for Enabled is returned.  My search is below:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| ldapsearch search="(&amp;amp;(objectClass=user)(!(objectClass=computer)))" attrs="sAMAccountName,accountExpires,Enabled"
| table sAMAccountName,accountExpires,Enabled
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any help would be appreciated.   &lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 19 Oct 2016 19:54:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Support-for-Active-Directory-After-running-an-ldapsearch/m-p/260336#M30002</guid>
      <dc:creator>sfefcu</dc:creator>
      <dc:date>2016-10-19T19:54:33Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Support for Active Directory: After running an ldapsearch, why does accountExpires or Enabled properties not populating data?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Support-for-Active-Directory-After-running-an-ldapsearch/m-p/260337#M30003</link>
      <description>&lt;P&gt;I was able to resolve this issue and since no one posted an answer I'll write what I found. &lt;/P&gt;

&lt;P&gt;It turns out that accountExpires and Enabled and not true LDAP attributes, but part of the Win32_UserAccount class.  It can be accessed via WMI and Powershell commands easily, but since they are not true LDAP attributes ldapsearch won't bring in those objects.   This information can be obtained through the Splunk TA for Windows infrastructure or imported via csv file produced from a PowerShell output.  &lt;/P&gt;</description>
      <pubDate>Fri, 07 Apr 2017 14:30:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Support-for-Active-Directory-After-running-an-ldapsearch/m-p/260337#M30003</guid>
      <dc:creator>sfefcu</dc:creator>
      <dc:date>2017-04-07T14:30:17Z</dc:date>
    </item>
  </channel>
</rss>

