<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Eventlog on Anything About IT</title><link>https://www.verboon.info/tags/eventlog/</link><description>Recent content in Eventlog on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 10 Dec 2019 22:10:23 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/eventlog/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Defender Advanced Threat Protection – Respond Actions Events</title><link>https://www.verboon.info/2019/12/microsoft-defender-advanced-threat-protection-respond-actions-events/</link><pubDate>Tue, 10 Dec 2019 22:10:23 +0000</pubDate><guid>https://www.verboon.info/2019/12/microsoft-defender-advanced-threat-protection-respond-actions-events/</guid><description>&lt;p&gt;Hey there, to be honest I had some difficulties to find the right title for todays blog post, so if you are still wondering here&amp;rsquo;s what this is all about. I had a customer asking me &amp;ldquo;&lt;em&gt;how can we see what MDATP Respond actions were taken on a particular machine both from a Console and client perspective?&lt;/em&gt;&amp;rdquo;. At the time of writing this blog post we have the following machine response actions that trigger a remote action available for MDATP managed devices.&lt;/p&gt;</description></item><item><title>Enabling PowerShell logging for PowerShell Core 6 (Workaround)</title><link>https://www.verboon.info/2018/01/enabling-powershell-logging-for-powershell-core-6-workaround/</link><pubDate>Sat, 13 Jan 2018 02:02:41 +0000</pubDate><guid>https://www.verboon.info/2018/01/enabling-powershell-logging-for-powershell-core-6-workaround/</guid><description>&lt;p&gt;By default, PowerShell Core does not log events to the Windows Event logs. From a security perspective this isn’t ideal, but that’s something I’ll take a closer look at later. To enable PowerShell logging you have to run &lt;code&gt;RegisterManifest.ps1 which is located in the &amp;quot;C:\Program Files\PowerShell\6.0.0&amp;quot; folder. But unfortunately running that command would not work for me. Now this is the beauty of PowerShell being open sourced, the code as well as the comments from developers is publicly available. So after a short search within the GitHub repo of PowerShell Core I found references about the issue. &lt;/code&gt;&lt;/p&gt;</description></item><item><title>How to automate the creation of Windows Eventlog Custom Views</title><link>https://www.verboon.info/2011/12/how-to-automate-the-creation-of-windows-eventlog-custom-views-2/</link><pubDate>Sat, 17 Dec 2011 16:32:31 +0000</pubDate><guid>https://www.verboon.info/2011/12/how-to-automate-the-creation-of-windows-eventlog-custom-views-2/</guid><description>&lt;p&gt;In the past couple of days I have been working on measuring system boot performance and you are probably going to see some posts from me on that subject soon. Today I want to share with you how you can automate the creation of a Windows Eventlog custom view.  &lt;/p&gt;
&lt;p&gt;While running these boot performance tests I reinstalled Windows several times on different systems and each time I wanted to collect the boot performance data from these clients I had to create a custom view within the Windows Event log to filter out the boot events. Well after doing that a few times manually I thought I would be better of to get that thing automated.&lt;/p&gt;</description></item></channel></rss>