<?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 Reporting clients with the timestamp workaround (datetime.xml file) in place in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Reporting-clients-with-the-timestamp-workaround-datetime-xml/m-p/496378#M84673</link>
    <description>&lt;P&gt;Is there a way to check which hosts (universal forwarders or splunk enterprise) have the updated datetime.xml installed?&lt;BR /&gt;
We have several different groups that send us logs from an internal network via a heavy forwarder, so I can see their splunkd logs, but there seems to be no record of the new file.&lt;BR /&gt;
On the heavy installs, It reports properly.&lt;BR /&gt;
On the universal forwarders, I was hoping that it would fail the file validation at startup and send the log to _internal, but even though "splunk.exe validate files" shows there is a change, nothing shows up in the splunkd log or at startup.&lt;/P&gt;

&lt;P&gt;I am trying to generate a list of all hosts that do not have the file installed.&lt;/P&gt;

&lt;P&gt;I realize that this timestamp issue may not affect certain log types, but we are not in a position to pick/choose which ones will work, so our strategy will be to apply the workaround to 100% of the instances.&lt;/P&gt;</description>
    <pubDate>Tue, 03 Dec 2019 19:32:55 GMT</pubDate>
    <dc:creator>oliverj</dc:creator>
    <dc:date>2019-12-03T19:32:55Z</dc:date>
    <item>
      <title>Reporting clients with the timestamp workaround (datetime.xml file) in place</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Reporting-clients-with-the-timestamp-workaround-datetime-xml/m-p/496378#M84673</link>
      <description>&lt;P&gt;Is there a way to check which hosts (universal forwarders or splunk enterprise) have the updated datetime.xml installed?&lt;BR /&gt;
We have several different groups that send us logs from an internal network via a heavy forwarder, so I can see their splunkd logs, but there seems to be no record of the new file.&lt;BR /&gt;
On the heavy installs, It reports properly.&lt;BR /&gt;
On the universal forwarders, I was hoping that it would fail the file validation at startup and send the log to _internal, but even though "splunk.exe validate files" shows there is a change, nothing shows up in the splunkd log or at startup.&lt;/P&gt;

&lt;P&gt;I am trying to generate a list of all hosts that do not have the file installed.&lt;/P&gt;

&lt;P&gt;I realize that this timestamp issue may not affect certain log types, but we are not in a position to pick/choose which ones will work, so our strategy will be to apply the workaround to 100% of the instances.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2019 19:32:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Reporting-clients-with-the-timestamp-workaround-datetime-xml/m-p/496378#M84673</guid>
      <dc:creator>oliverj</dc:creator>
      <dc:date>2019-12-03T19:32:55Z</dc:date>
    </item>
    <item>
      <title>Re: Reporting clients with the timestamp workaround (datetime.xml file) in place</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Reporting-clients-with-the-timestamp-workaround-datetime-xml/m-p/496379#M84674</link>
      <description>&lt;P&gt;Any suggestions here?&lt;BR /&gt;
Having a hard time coming up with a verification method.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Dec 2019 14:21:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Reporting-clients-with-the-timestamp-workaround-datetime-xml/m-p/496379#M84674</guid>
      <dc:creator>oliverj</dc:creator>
      <dc:date>2019-12-05T14:21:17Z</dc:date>
    </item>
    <item>
      <title>Re: Reporting clients with the timestamp workaround (datetime.xml file) in place</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Reporting-clients-with-the-timestamp-workaround-datetime-xml/m-p/496380#M84675</link>
      <description>&lt;P&gt;Deployment server can produce a list of Splunk versions for UF/Splunk which can indicate that the endpoint being on a non patch UF. &lt;/P&gt;</description>
      <pubDate>Fri, 06 Dec 2019 20:36:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Reporting-clients-with-the-timestamp-workaround-datetime-xml/m-p/496380#M84675</guid>
      <dc:creator>ycefalas</dc:creator>
      <dc:date>2019-12-06T20:36:28Z</dc:date>
    </item>
    <item>
      <title>Re: Reporting clients with the timestamp workaround (datetime.xml file) in place</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Reporting-clients-with-the-timestamp-workaround-datetime-xml/m-p/496381#M84676</link>
      <description>&lt;P&gt;Yes, but in our case, we only updated the XML. &lt;BR /&gt;
Software updates would be better, but the release turnaround in our environment is prohibitively slow for an emergency like this.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2019 17:06:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Reporting-clients-with-the-timestamp-workaround-datetime-xml/m-p/496381#M84676</guid>
      <dc:creator>oliverj</dc:creator>
      <dc:date>2019-12-09T17:06:50Z</dc:date>
    </item>
    <item>
      <title>Re: Reporting clients with the timestamp workaround (datetime.xml file) in place</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Reporting-clients-with-the-timestamp-workaround-datetime-xml/m-p/496382#M84677</link>
      <description>&lt;P&gt;Per Splunk support, the universal forwarders do not generate a usable message in their logs, although the heavy/full versions do.&lt;BR /&gt;
It is possible to build a script that you can install as an app that will to a checksum check, but we are not in a position to install apps across devices we do not own.&lt;BR /&gt;
So, manual checks it is.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Dec 2019 14:08:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Reporting-clients-with-the-timestamp-workaround-datetime-xml/m-p/496382#M84677</guid>
      <dc:creator>oliverj</dc:creator>
      <dc:date>2019-12-11T14:08:36Z</dc:date>
    </item>
  </channel>
</rss>

