<?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: Force Re-Enumeration of all AD objects with ADmon? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32141#M5689</link>
    <description>&lt;P&gt;Should it not be "inputs.conf" instead of "admon.conf"?&lt;/P&gt;</description>
    <pubDate>Wed, 05 Mar 2014 14:15:43 GMT</pubDate>
    <dc:creator>helge</dc:creator>
    <dc:date>2014-03-05T14:15:43Z</dc:date>
    <item>
      <title>Force Re-Enumeration of all AD objects with ADmon?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32136#M5684</link>
      <description>&lt;P&gt;From my understanding, ADmon will pull down all objects in AD on first run, then only report changes from then on. However, the original baseline data will get lost when it ages out of an index.&lt;/P&gt;

&lt;P&gt;Is there a way to force ADmon to re-enumerate all AD objects to get a proper baseline, occasionally?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jan 2011 03:16:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32136#M5684</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2011-01-26T03:16:57Z</dc:date>
    </item>
    <item>
      <title>Re: Force Re-Enumeration of all AD objects with ADmon?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32137#M5685</link>
      <description>&lt;P&gt;(Without completely clearing fishbucket.)&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jan 2011 04:21:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32137#M5685</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2011-01-28T04:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: Force Re-Enumeration of all AD objects with ADmon?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32138#M5686</link>
      <description>&lt;P&gt;You could do one of the following to re-sync the events from the server.&lt;/P&gt;

&lt;P&gt;i) Manually add another stanza in &lt;CODE&gt;etc\...\local\admon.conf&lt;/CODE&gt; like so:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[newCollection]
targetDc = "your Server here"
startingNode = 
monitorSubtree = 1
disabled = 0
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;ii) Use Splunkweb to add the new collection with the same settings as the old one.&lt;/P&gt;

&lt;P&gt;iii) In the splunk directory, under &lt;CODE&gt;var\lib\splunk\persistentstorage\ADMon&lt;/CODE&gt;
there is a file called "your collection name here.ini".
Deleting this file before restarting splunk-admon.exe will resync the data from the server. If there are multiple such files, pick the file pertaining to the collection you want to reenumerate.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jan 2011 05:30:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32138#M5686</guid>
      <dc:creator>rgopalan</dc:creator>
      <dc:date>2011-01-28T05:30:49Z</dc:date>
    </item>
    <item>
      <title>Re: Force Re-Enumeration of all AD objects with ADmon?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32139#M5687</link>
      <description>&lt;P&gt;I have not been able to test this, but am going to mark this as accepted. If anyone is able to test this, please comment!&lt;/P&gt;</description>
      <pubDate>Tue, 01 Feb 2011 23:25:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32139#M5687</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2011-02-01T23:25:14Z</dc:date>
    </item>
    <item>
      <title>Re: Force Re-Enumeration of all AD objects with ADmon?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32140#M5688</link>
      <description>&lt;P&gt;Deleting the INI files is the way to go!&lt;/P&gt;</description>
      <pubDate>Wed, 05 Mar 2014 14:14:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32140#M5688</guid>
      <dc:creator>helge</dc:creator>
      <dc:date>2014-03-05T14:14:54Z</dc:date>
    </item>
    <item>
      <title>Re: Force Re-Enumeration of all AD objects with ADmon?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32141#M5689</link>
      <description>&lt;P&gt;Should it not be "inputs.conf" instead of "admon.conf"?&lt;/P&gt;</description>
      <pubDate>Wed, 05 Mar 2014 14:15:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32141#M5689</guid>
      <dc:creator>helge</dc:creator>
      <dc:date>2014-03-05T14:15:43Z</dc:date>
    </item>
    <item>
      <title>Re: Force Re-Enumeration of all AD objects with ADmon?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32142#M5690</link>
      <description>&lt;P&gt;Yes &lt;/P&gt;

&lt;P&gt;method 1 worked for me : &lt;BR /&gt;
modify input app deployed on UF locally on AD : &lt;BR /&gt;
in inputs.conf&lt;BR /&gt;
change the admon collection name [admon:collection2]&lt;BR /&gt;
used baseline=1&lt;BR /&gt;
disabled=0&lt;BR /&gt;
targetDC = "myAD"&lt;BR /&gt;
index=myindex&lt;BR /&gt;
monitorSubtree=1&lt;/P&gt;

&lt;P&gt;push to uf&lt;BR /&gt;
then wait for baseline to complete &lt;BR /&gt;
then change baseline to 0 and repush to uf&lt;/P&gt;

&lt;P&gt;This way is easier when you don't have local access on the AD to clean up files&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2017 09:06:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Force-Re-Enumeration-of-all-AD-objects-with-ADmon/m-p/32142#M5690</guid>
      <dc:creator>maraman_splunk</dc:creator>
      <dc:date>2017-01-27T09:06:42Z</dc:date>
    </item>
  </channel>
</rss>

