You could do this in different ways with powershell. But the whole idea is to keep it simple
$CURRENTDATE=GET-DATE -Format "MM/dd/yyyy" $FIRSTDAYOFMONTH=GET-DATE $CURRENTDATE -Day 1 $LASTDAYOFMONTH=GET-DATE $FIRSTDAYOFMONTH.AddMonths(1).AddSeconds(-1) $FIRSTDAYOFMONTH $LASTDAYOFMONTH
Pass each attachment location to a variable and add this to the Attachments parameter separated by comma
Example
$Att1="c:\test1.csv" $Att2="c:\test1.csv" Send-MailMessage -To abc@tkr.com - From xyz@tkr.com -Subject "Attachments" -Attachments $Att1,$Att2
Are your Local Drives of your IIS Server running out of space? Have you checked the size of your IIS Logs?
If your IIS was setup by a professional; you would not have to go through this issue. The log files would have been managed appropriately
Ideally I do not see a purpose to keep IIS Log files beyond a period of 1 month. Those older than one month should ideally be removed to prevent disk space issues
I found below posts which will assist you. Before you use the below scripts; please identify the location of your log files
Using Powershell
http://www.codeproject.com/Articles/663000/Simple-Powershell-script-to-clean-up-IIS-log-files
Using VBScript
http://www.iis.net/learn/manage/provisioning-and-managing-iis/managing-iis-log-file-storage#02
By default; you would find them on C:\inetpub\logs\LogFiles\
To verify the location; open IIS and select the Default Website and click Logging
Take note of the path mentioned in the directory field
Error: The file *.ps1 is not digitally signed. The script will not execute on the system
+FullyQualifiedErrorID: UnauthorizedAccess
To resolve above error; set the execution policy to unrestricted
Set-ExecutionPolicy -ExecutionPolicy Bypass
If you have overcome a situation where-in; while exporting results using Export-CSV; multi-valued columns return just the property System.String[]; I have just the right solution for you
If the multi-valued column name is recipients; use the column as below
@{Name=’recipients’;Expression={[string]::join(“;”, ($_.recipients))}}
Please note that the below command applies for use in the Windows Powershell Console and not in the Windows Powershell ISE
Use the More function to achieve the page wise output
Get-Service -ComputerName computername | more
Are you using the System.Net.Mail to send File Attachments? Is the file attachment above 3MB?
If yes; you have just found out the reason for the error. The System.Net.Mail Class throws an exception if a file attachment is over 3MB
Microsoft has a patch available which solves this issue
https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=30226
If you have any issues downloading the file; you may post your comment on this post.
Once the patch is applied; you should now be able to send large attachments using your Powershell Send-MailMessage cmdlet.
Please ensure that you use the -UseSSL in your cmdlet. If you leave out -UseSSL; you are most likely to encounter the below error
Send-MailMessage : The operation has timed out.
Get-WmiObject : The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) At line:1 char:1 + Get-WmiObject win32_bios -ComputerName remotecomputername|Select PSComputerName,Manufact ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [Get-WmiObject], COMException + FullyQualifiedErrorId : GetWMICOMException,Microsoft.PowerShell.Commands.GetWmiObjectCommand
u
Well, all you need to verify is the current version of your .NET Framework. To verify the current version; proceed to the registry
HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP
The branch is most likely only upto V3 or V3.5
Download and Install .NET Framework 4 and your system will be ready to Install the Windows Management Framework 3
You may also find below post useful
http://www.happysysadm.com/2012/06/upgrading-to-powershell-30-on-windows.html
If you have received this error using Powershell when trying to Write to the Event Log; it’s because you have not registered the source yet
Use the New-EventLog cmdlet to register the source prior to writing to the event log
New-EventLog -LogName Application -Source <Sourcename>
