<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Log-Files on Anything About IT</title><link>https://www.verboon.info/tags/log-files/</link><description>Recent content in Log-Files on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 13 Oct 2013 14:35:41 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/log-files/index.xml" rel="self" type="application/rss+xml"/><item><title>ConfigMgr - PowerShell Script to collect remote log files</title><link>https://www.verboon.info/2013/10/configmgr-powershell-script-to-collect-remote-log-files/</link><pubDate>Sun, 13 Oct 2013 14:35:41 +0000</pubDate><guid>https://www.verboon.info/2013/10/configmgr-powershell-script-to-collect-remote-log-files/</guid><description>&lt;p&gt;Looking at a client’s ConfigMgr Agent log files is inevitable when managing a Configuration Manager infrastructure. If you are working within a local area network only, then you will most likely just connect to the remote systems configuration manager log folder and drag and drop the appropriate log files into CMTrace.exe. But if your clients are distributed across a WAN network with slow network links opening the log file from a remote location is probably not the most efficient way for analyzing the log files content. And because troubleshooting typically requires looking at multiple log files you finally end up copying multiple log files or just the whole log folder to your client to open them locally.&lt;/p&gt;</description></item></channel></rss>