<div>
Add this to your &nbsp;.Bat file.<br />
Adjust sourcedir and yourcommand as needed.<br />
It's in debug mode for visual confirmation. To run it for real, remove the ECHO prefix when satisfied.<br />
<br />

<pre><code class="code-1 nolinks" id="code-20-42415584-1"><span>set sourcedir=c:\dirname</span>
<span></span>
<span>for %%a in ('dir /bs &quot;%sourcedir%\*.log&quot;) do (</span>
<span>  ECHO yourcommand &quot;%%a&quot;</span>
<span>  pause</span>
<span>)</span>
</code></pre>
</div>


<div>
NVIT script has a few bugs:<br />
<br />
set sourcedir=c:\dirname<br />
<br />

<pre><code class="code-1 nolinks" id="code-20-42415635-1"><span>for %%a in ('dir /b /s &quot;%sourcedir%\*.log&quot;') do (</span>
<span>  ECHO yourcommand &quot;%%a&quot;</span>
<span>  pause</span>
<span>)</span>
</code></pre>
</div>


<div>
Thank you for the script and thank you for the correction. I appreciate it.<br />
<br />
The original script I was running is a FORFILES command, in order to convert *.log files to *.csv files. <br />
<br />
Would either of you have a better suggestion than the following for the conversion script?<br />
<br />

<pre><code class="code-1 nolinks" id="code-20-42415852-1"></code></pre>
forfiles /s /C &quot;cmd /c echo @date, @time, @s-ip, @cs-method, @cs-uri-stem, @cs-uri-query, @s-port, @cs-username, @c-ip, @cs(User-Agent), @cs(Referer),@sc-status, @sc-substatus, @sc-win32-status, @time-taken&quot; &gt;&nbsp;%Timestamp%_Log.csv &quot;%%a&quot;<br />
<br />
It generates a file, but unlike running just the raw FORFILES command, there is no data in the file.<br />
<br />
Thank you again for your attention. I greatly appreciate it.
</div>


<div>
Currently, your forfiles line echos echos the @date, @time, @s-ip, @cs-method, @cs-uri-stem, @cs-uri-query, @s-port, @cs-username, @c-ip, @cs(User-Agent), @cs(Referer),@sc-status, @sc-substatus, @sc-win32-status, @time-taken&quot; <br />
output to a CSV file.<br />
<br />
The &quot;%%a&quot; seems incorrectly placed after the output redirection.<br />
<br />
Is there another line to run the conversion?<br />
Is there more code to show?
</div>


<div>
No more code to show, NVIT. <br />
<br />
I removed the &quot;%%a&quot; and it did generate a file, but the file was only filled with the headers (e.g. @date, @time, etc).<br />
<br />
I paired down what needs to be converted (what I believe to be essential) and I'm getting no real data to speak of:<br />
<br />
&nbsp;<a href="https://filedb.experts-exchange.com/incoming/2017/12_w52/1216642/log-file-results.png" target="_blank" title="log-file-results.png (253 KB)"><img alt="log-file-results.png" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2017/12_w52/800_1216642/log-file-results.png" /></a><br />
Looks like I'm going to go back to the drawing board. Any suggestions of ways to convert .Log files to .CSV files for Windows?<br />
<br />
Thanks again.
</div>


log-file-results.png

<div>
Is the log file a text file? &nbsp; If so, just rename it to a csv file.<br />
<br />
What generates the log file?
</div>


<div>
The log file is a text file, but doesn't have commas in it. I'm seeking to do this with IIS Log Files.<br />
<br />
Thanks
</div>


<div>
This is close to something that I will write for Production. Thank you.
</div>


<div>
<div class="content wysiwyg-content">
I am writing a cmd file that converts *.log files to *.csv on a Windows Server 2016 machine.<br />
<br />
How do I have the script traverse the folder structure and find just the files of &quot;*.log&quot; type and then run the conversion process from *.log five to *.csv?<br />
<br />
Thanks for your help
</div>
</div>


I am writing a cmd file that converts *.log files to *.csv on a Windows Server 2016 machine.

How do I have the script traverse the folder structure and find just the files of "*.log" type and then run the conversion process from *.log five to *.csv?

Thanks for your help

CMD Script Traversal and Find Files of Certain Type

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Microsoft Azure is a cloud computing platform and infrastructure for building, deploying and managing applications and services through datacenters. It provides both platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems. Cloud Services is a PaaS environment and can be used to create scalable applications and services; there are specific software development kits (SDKs) provided by Microsoft for Python, Java, Node.js and .NET. Azure also has file and storage services, data management, analytics and DNS services.

Azure

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.