<?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 VDI dynamic VMs and Splunk forwarders in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/VDI-dynamic-VMs-and-Splunk-forwarders/m-p/410406#M24744</link>
    <description>&lt;P&gt;How do you go about ensuring splunk forwarders forward all data from a gold image created VM that then gets blown away when a user logs off?  How are people managing VM creation/destruction and in relation to the monitoring console "missing forwarder" report growing as VMs come and then go?&lt;/P&gt;</description>
    <pubDate>Tue, 26 Jun 2018 18:53:46 GMT</pubDate>
    <dc:creator>ShaunBaker</dc:creator>
    <dc:date>2018-06-26T18:53:46Z</dc:date>
    <item>
      <title>VDI dynamic VMs and Splunk forwarders</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/VDI-dynamic-VMs-and-Splunk-forwarders/m-p/410406#M24744</link>
      <description>&lt;P&gt;How do you go about ensuring splunk forwarders forward all data from a gold image created VM that then gets blown away when a user logs off?  How are people managing VM creation/destruction and in relation to the monitoring console "missing forwarder" report growing as VMs come and then go?&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jun 2018 18:53:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/VDI-dynamic-VMs-and-Splunk-forwarders/m-p/410406#M24744</guid>
      <dc:creator>ShaunBaker</dc:creator>
      <dc:date>2018-06-26T18:53:46Z</dc:date>
    </item>
  </channel>
</rss>

