<?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: Deploying across multiple OS in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Deploying-across-multiple-OS/m-p/37973#M8587</link>
    <description>&lt;P&gt;Sure, have a look at &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Definedeploymentclasses"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Definedeploymentclasses&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;In particular you want to look at machineTypes, here you can define the machine type. To find your machine type have a look at this from the &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.2/Admin/Serverclassconf"&gt;serverclass.conf&lt;/A&gt; documentation;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;# client machineTypes can also be used to match clients.
# This setting lets you use the hardware type of the deployment client as a filter. 
# This filter will be used only if a client could not be matched using the whitelist/blacklist filter.
# The value for machineTypes is a specific string that is designated by the hardware platform itself. 
# The method for finding this string on the client itself will vary by platform, but if the deployment client 
# is already connected to the deployment server, you can determine what this string is by using this
# Splunk CLI command on the deployment server:
# &amp;lt;code&amp;gt;./splunk list deploy-clients&amp;lt;/code&amp;gt;
# This will return a value for &amp;lt;code&amp;gt;utsname&amp;lt;/code&amp;gt; that you can use to
# specify &amp;lt;code&amp;gt;machineTypes&amp;lt;/code&amp;gt;.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Fri, 27 Apr 2012 08:15:02 GMT</pubDate>
    <dc:creator>Drainy</dc:creator>
    <dc:date>2012-04-27T08:15:02Z</dc:date>
    <item>
      <title>Deploying across multiple OS</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Deploying-across-multiple-OS/m-p/37972#M8586</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;

&lt;P&gt;I have a network with Windows and Linux Systems mixed. &lt;BR /&gt;
It is not possible to seperate them or create IP ranges.&lt;/P&gt;

&lt;P&gt;Now for me it is important to know if a app deployed for Windows causing problems on a Linux machine? And if a Windows Systems get a app deployed for Linux?&lt;BR /&gt;
The App for Windows Systems is collecting PerfMon data and the App for Linux is monitoring directories.&lt;/P&gt;

&lt;P&gt;Is there a way to check the operating system before roll out the app? I want to avoid that Windows systems get the apps for the Linux Systems and the same for Linux.&lt;/P&gt;

&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Fri, 27 Apr 2012 08:07:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Deploying-across-multiple-OS/m-p/37972#M8586</guid>
      <dc:creator>nebel</dc:creator>
      <dc:date>2012-04-27T08:07:56Z</dc:date>
    </item>
    <item>
      <title>Re: Deploying across multiple OS</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Deploying-across-multiple-OS/m-p/37973#M8587</link>
      <description>&lt;P&gt;Sure, have a look at &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Definedeploymentclasses"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Definedeploymentclasses&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;In particular you want to look at machineTypes, here you can define the machine type. To find your machine type have a look at this from the &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.2/Admin/Serverclassconf"&gt;serverclass.conf&lt;/A&gt; documentation;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;# client machineTypes can also be used to match clients.
# This setting lets you use the hardware type of the deployment client as a filter. 
# This filter will be used only if a client could not be matched using the whitelist/blacklist filter.
# The value for machineTypes is a specific string that is designated by the hardware platform itself. 
# The method for finding this string on the client itself will vary by platform, but if the deployment client 
# is already connected to the deployment server, you can determine what this string is by using this
# Splunk CLI command on the deployment server:
# &amp;lt;code&amp;gt;./splunk list deploy-clients&amp;lt;/code&amp;gt;
# This will return a value for &amp;lt;code&amp;gt;utsname&amp;lt;/code&amp;gt; that you can use to
# specify &amp;lt;code&amp;gt;machineTypes&amp;lt;/code&amp;gt;.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 27 Apr 2012 08:15:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Deploying-across-multiple-OS/m-p/37973#M8587</guid>
      <dc:creator>Drainy</dc:creator>
      <dc:date>2012-04-27T08:15:02Z</dc:date>
    </item>
    <item>
      <title>Re: Deploying across multiple OS</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Deploying-across-multiple-OS/m-p/37974#M8588</link>
      <description>&lt;P&gt;thanks for that! Splunk rocks &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Apr 2012 08:17:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Deploying-across-multiple-OS/m-p/37974#M8588</guid>
      <dc:creator>nebel</dc:creator>
      <dc:date>2012-04-27T08:17:45Z</dc:date>
    </item>
  </channel>
</rss>

