Exchange 2016 delete IIS log files

[webbobfc]

I think I know the answer to my own question but just looking for re-assurance. Our onsite exchange 2016 server has been getting low on disk space and upon further investigation I have we have found loads of log files in c:\inetpub\logs\logfiles and then in 3 folders W3SVC1, 2 and 3. From what I have read they are just used for troubleshooting and diagnostics. Is it safe to just go in and delete all these and is there any specific way of doing it, stopping services etc. We have never had any need for the log files in the past but could save the last few weeks etc, they are going back years. I see you can stop the logs files from been created in IIS.

 

Thanks

Webbobfc

[3s-gtech]

There are various hacks for Exchange logs, and I've been through them all as I set ours up with a too small C: partition! Be cautious about disabling any of the logs or IIS features - I once used these to restore OWA after Office Web Apps broke the bindings. Do you have another VHDX/partition you can move logs to (and changing the logging process to use that new location)? Also consider compressing some of them - where these aren't in use, you can save a massive amount of space while not having to delete or move anything.

[Roberto]

I think I know the answer to my own question but just looking for re-assurance. Our onsite exchange 2016 server has been getting low on disk space and upon further investigation I have we have found loads of log files in c:\inetpub\logs\logfiles and then in 3 folders W3SVC1, 2 and 3. From what I have read they are just used for troubleshooting and diagnostics. Is it safe to just go in and delete all these and is there any specific way of doing it, stopping services etc. We have never had any need for the log files in the past but could save the last few weeks etc, they are going back years. I see you can stop the logs files from been created in IIS.

 

Thanks

Webbobfc

 

If you are talking about just IIS logs in the locations specified then you can delete these without any worries. I would suggest that you should leave the current logs available unless you need to troubleshoot but you can dispose of IIS application logs if you want. I wouldn't recommend preventing the creation of logs either, again they can be invaluable for troubleshooting.

 

I also find that applying NTFS compression to that folder will greatly reduce the space it needs but do this after you remove old logs. You don't need to stop IIS to remove old logs.