<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>System-Center on Janik von Rotz</title>
    <link>https://janikvonrotz.ch/tags/system-center/</link>
    <description>Recent content in System-Center on Janik von Rotz</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 26 Oct 2017 07:15:24 +0000</lastBuildDate>
    <atom:link href="https://janikvonrotz.ch/tags/system-center/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PowerShell - Logging in CMTrace format</title>
      <link>https://janikvonrotz.ch/2017/10/26/powershell-logging-in-cmtrace-format/</link>
      <pubDate>Thu, 26 Oct 2017 07:15:24 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2017/10/26/powershell-logging-in-cmtrace-format/</guid>
      <description>&lt;p&gt;CMTrace is probably the first choice for a log viewer in a Microsoft environment. When working with System Center Configuration Manager there aren&amp;rsquo;t any alternatives available. In a recent scenario I had to write log files in the CMtrace format. There are already many cmdlets available to do so, however, most of them did not work well or were overengineered. There I&amp;rsquo;ve taken a look at the CMTrace format specs and wrote a PowerShell function to create compatible log files.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
