Avatar of fallriverelectric
 asked on

Deleting IIS log files from Exchange 2010 server

I'm running Exchange 2010 on Windows Server 2008 R2 Standard.  My disk space is filling up, and it seems to be caused largely by IIS logs located in C:\inetpub\logs.  Is it ok to delete some of these logs?  Or are these similar to the Exchange transaction logs, which I believe should not be touched?  (Transaction logs are currently truncating and are not a problem space-wise.)  I just need to know if it will cause any problems to delete these IIS logs.  

Avatar of undefined
Last Comment

8/22/2022 - Mon

The issue is related to WSUS log files. There is also some that say some of the logs are generated by leaving the SBS console open. So... Close your SBS console (if sbs.. but in your case it is not) and apply this :

go to WSUS admin in IIS -WSUS Administration site and open Logging... Disable logging and you will be good to go.

This link has the screen shot of the setting to change:



I don't have WSUS listed in IIS.  The only site I have is default web site.

How much space is available on your server per partition? Are the transaction logs truncating after weekly/nightly backups?

How much data are these logs taking up?
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy

The transaction logs are truncating after backups and are only a few GB.  The IIS logs, however, are occupying about 62GB of my 250GB partition.

So you have a single 250 GB partition?

More importantly I would find out why you're getting so much traffic on your IIS files -- and whether or not this would be normal for your implementation.

Sometimes Exchange may create a larger amount of log files if there is a large amount of replication that's taking place.

You can delete those log files safely. If you are a bit worried then leave today's ones and delete the older ones.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question


You can delete the file safely. Simple command prompt, del c:\inetpub\log\*.log can do.

You can make batch file for that command and use this app from codeproject to make it as Windows Service, http://www.codeproject.com/KB/system/xyntservice.aspx.

BTW, my suggestion, please go and check what cause the error. Turn off the services that generate it if possible.


In looking through the logs, I see a lot of connections to our GFI MailArchiver server.  So I'm guessing journaling is what's causing most, if not all, of these logs to appear.  Is it still ok to delete these logs, since I won't be turning off the GFI services?  And is there a better way to determine if there is anything else contributing to the logs, or if it's just GFI?

Everytime a program connects to exchange through Exchange WebServices it will connect using IIS and with every connection it will log a line in the log file.
Your help has saved me hundreds of hours of internet surfing.

That's exactly what I needed.  Thank you!