If you have got a Windows Web Server, it is possible that IIS is enabled to generate the IIS Log files and over the years this could cause some disk space problems.
In order to clear up the disk space; one good option is cleaning up the old IIS log files automatically by using a Windows Scheduler Task and a Powershell script.
For this solution; all credit goes to Bob McCoy, this has helped me and my Client, hope it will help you, too.
Step 1: Copy/Create Script
Copy the following script to a place where your privileged user can get to it. Since it's going to be run by the task scheduler, you don't want it somewhere where users can modify it to accomplish their nefarious purposes.
# Script to be run weekly by task scheduler to cleanup IIS log files
# greater than 30 days old.
$start = (get-date).AddDays(-30)
cd c:\inetpub\logs\logfiles\w3svc1
Get-ChildItem | where {$PSItem.LastWriteTime -lt $start} | Remove-Item
If you are running PowerShell v2, replace $PSItem with $_.
Step 2: Schedule the Cleanup
Assumptions for this step:
1) You named the script Remove-OldIisLog.ps1.
2) You placed it in a folder called C:\scripts.
Actions:
1) As an administrative user, open the Task Scheduler MMC snap-in (taskschd.msc).
2) Click Action | Create Task.
3) On the General tab give it a name (something like IIS Logfile Cleanup). Give it a descriptin if you like. And select the user the task will run under. This script will run well under SYSTEM if you don't want to select a user account.
4) Under the Triggers tab select New to create a new "On a schedule" trigger. I run it weekly at 6:00 am on Mondays. Choose what fits for you.
5) Under the Actions tab select New to create a new "Start a program" action.
Program/script: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Add arguments (optional): -ExecutionPolicy Bypass C:\Scripts\Remove-OldIisLog.ps1
6) The Conditions, Settings, and History tabs can remain at their default values, or modify to suit your environment.
Step 3: Test the Cleanup
From within the task scheduler, you should be able to run the task to test it. Right click on the entry and click run. For the test run you may want to modify the above script for some other number of days further out than your default. That way you can see the effect of specific dates. Be sure to reset the number of days for your production run.
In order to clear up the disk space; one good option is cleaning up the old IIS log files automatically by using a Windows Scheduler Task and a Powershell script.
For this solution; all credit goes to Bob McCoy, this has helped me and my Client, hope it will help you, too.
Step 1: Copy/Create Script
Copy the following script to a place where your privileged user can get to it. Since it's going to be run by the task scheduler, you don't want it somewhere where users can modify it to accomplish their nefarious purposes.
# Script to be run weekly by task scheduler to cleanup IIS log files
# greater than 30 days old.
$start = (get-date).AddDays(-30)
cd c:\inetpub\logs\logfiles\w3svc1
Get-ChildItem | where {$PSItem.LastWriteTime -lt $start} | Remove-Item
If you are running PowerShell v2, replace $PSItem with $_.
Step 2: Schedule the Cleanup
Assumptions for this step:
1) You named the script Remove-OldIisLog.ps1.
2) You placed it in a folder called C:\scripts.
Actions:
1) As an administrative user, open the Task Scheduler MMC snap-in (taskschd.msc).
2) Click Action | Create Task.
3) On the General tab give it a name (something like IIS Logfile Cleanup). Give it a descriptin if you like. And select the user the task will run under. This script will run well under SYSTEM if you don't want to select a user account.
4) Under the Triggers tab select New to create a new "On a schedule" trigger. I run it weekly at 6:00 am on Mondays. Choose what fits for you.
5) Under the Actions tab select New to create a new "Start a program" action.
Program/script: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Add arguments (optional): -ExecutionPolicy Bypass C:\Scripts\Remove-OldIisLog.ps1
6) The Conditions, Settings, and History tabs can remain at their default values, or modify to suit your environment.
Step 3: Test the Cleanup
From within the task scheduler, you should be able to run the task to test it. Right click on the entry and click run. For the test run you may want to modify the above script for some other number of days further out than your default. That way you can see the effect of specific dates. Be sure to reset the number of days for your production run.
Comments
Post a Comment