<?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: BSOD due to OneAgent Installation in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110241#M7058</link>
    <description>&lt;P&gt;You are right &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 10 Dec 2018 10:52:52 GMT</pubDate>
    <dc:creator>radek_jasinski</dc:creator>
    <dc:date>2018-12-10T10:52:52Z</dc:date>
    <item>
      <title>BSOD due to OneAgent Installation</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110234#M7051</link>
      <description>&lt;P&gt;We deployed OneAgent on the Db server and it caused server reboot and BSOD . We removed the Agent and brought the server back normal . The question we got from platform is Did Dyantrace OneAgent install any driver on the server . We had this issue on 3 servers so far. Any input or solution appreciated.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Dec 2021 07:46:59 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110234#M7051</guid>
      <dc:creator>pshinde</dc:creator>
      <dc:date>2021-12-10T07:46:59Z</dc:date>
    </item>
    <item>
      <title>Re: BSOD due to OneAgent Installation</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110235#M7052</link>
      <description>&lt;P&gt;The agent doesn't install any additional drivers on the monitored component's side. &lt;/P&gt;&lt;P&gt;It seems to me that the best solution in this case will be open a support ticket.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Dec 2018 09:39:26 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110235#M7052</guid>
      <dc:creator>radek_jasinski</dc:creator>
      <dc:date>2018-12-10T09:39:26Z</dc:date>
    </item>
    <item>
      <title>Re: BSOD due to OneAgent Installation</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110236#M7053</link>
      <description>&lt;P&gt;I've encountered the same issue at one customer who has Windows servers hardened and they are running multiple host security tools. Our issue was BSOD during installation of oneagentmon driver and it was caused by McAfee SolidCore running on the host. Even the SolidCore was running in update mode (mode when changes to the system are allowed), BSOD occurred.&lt;/P&gt;&lt;P&gt;Finally, I've been able to locate the issue to memory protection mechanism in SolidCore which interfered with Oneagent installation. Our solution was to temporarily disable memory protection in SolidCore during Oneagent installation (also during upgrades). Memory protection could be turned back on after oneagentmon driver was installed.&lt;BR /&gt;&lt;BR /&gt;In your case check the logs first, probably this will be similar situation and also look for any antivirus/hardening software running on the same host.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Dec 2018 09:39:33 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110236#M7053</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2018-12-10T09:39:33Z</dc:date>
    </item>
    <item>
      <title>Re: BSOD due to OneAgent Installation</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110237#M7054</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://answers.dynatrace.com/users/4724/view.html" nodeid="4724"&gt;@Radosław J.&lt;/A&gt; On windows, Oneagent installs the oneagentmon driver which is responsible for injecting code into applications. See more &lt;A href="https://www.dynatrace.com/support/help/deploy-dynatrace/oneagent/windows/installation/permission-requirements-for-oneagent-installation-and-operation-on-windows/"&gt;here&lt;/A&gt;.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Dec 2018 09:42:23 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110237#M7054</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2018-12-10T09:42:23Z</dc:date>
    </item>
    <item>
      <title>Re: BSOD due to OneAgent Installation</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110238#M7055</link>
      <description>&lt;A rel="user" href="https://answers.dynatrace.com/users/16467/view.html" nodeid="16467"&gt;@Julius L.&lt;/A&gt;&lt;P&gt; ins't it oneagentmon device not driver? Driver is confusing name &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Dec 2018 09:51:05 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110238#M7055</guid>
      <dc:creator>skrystosik</dc:creator>
      <dc:date>2018-12-10T09:51:05Z</dc:date>
    </item>
    <item>
      <title>Re: BSOD due to OneAgent Installation</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110239#M7056</link>
      <description>&lt;P&gt;I agree with the sentence that driver is confusing name&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Dec 2018 10:45:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110239#M7056</guid>
      <dc:creator>radek_jasinski</dc:creator>
      <dc:date>2018-12-10T10:45:21Z</dc:date>
    </item>
    <item>
      <title>Re: BSOD due to OneAgent Installation</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110240#M7057</link>
      <description>&lt;P&gt;It's both &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; There is a oneagentmon device present in the system that is handled by the oneagentmon driver. At least this my understanding.&lt;/P&gt;&lt;P&gt;Dynatrace help glossary refers both device and driver:&lt;/P&gt;&lt;P&gt;https://www.dynatrace.com/support/help/get-started/reference/glossary/#o&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Dec 2018 10:48:17 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110240#M7057</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2018-12-10T10:48:17Z</dc:date>
    </item>
    <item>
      <title>Re: BSOD due to OneAgent Installation</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110241#M7058</link>
      <description>&lt;P&gt;You are right &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Dec 2018 10:52:52 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/BSOD-due-to-OneAgent-Installation/m-p/110241#M7058</guid>
      <dc:creator>radek_jasinski</dc:creator>
      <dc:date>2018-12-10T10:52:52Z</dc:date>
    </item>
  </channel>
</rss>

