The PowerShell script to purge IIS and Exchange Server 2013 has been updated to support email reporting.
When executed by a scheduled task it is extremely helpful to Exchange Administrators to receive some sort of conformation of the script execution.
If using the SendMail switch, a summary report is sent as an Html email
Parameters added:
.PARAMETER SendMail Switch to send an Html report .PARAMETER MailFrom Email address of report sender .PARAMETER MailTo Email address of report recipient .PARAMETER MailServer SMTP Server for email report
This post has first been posted on my legacy blog.
This script adds a new scheduled task for an Exchange Server 2013 environment in a new task scheduler group "Exchange".
When providing a username and password the scheduled task will be configured to "Run whether user is logged on or not".
When username and password are provided the Register-ScheduledTask cmdlet verfies the logon credentials and will fails, if the credentials provided (username/password) are not valid.
Note: The cmdlet Register-ScheduledTask consumes the user password in clear text.
# EXAMPLE # Create a new scheduled task using a dedicated service account .\New-ScheduledExchangeTask.ps1 -TaskName "My Task" -ScriptName TaskScript1.ps1 -ScriptPath D:\Automation -TaskUser DOMAIN\ServiceAccount -Password P@ssw0rd # EXAMPLE # Create a simple scheduled task .\New-ScheduledExchangeTask.ps1 -TaskName "My Task" -ScriptName TaskScript1.ps1 -ScriptPath D:\Automation
This script removes/disables HealthMailboxes that show an inconsistent error when querying monitoring mailboxes using
Get-Mailbox -Monitoring
and receiving a warning like
"WARNING: The object DOMAINNAME/Microsoft Exchange System Objects/Monitoring Mailboxes/Health_Mailbox_GUID has been corrupted,
# Remove the HealthMailbox(es) having an empty database attribute .\Fix-HealthMailboxes.ps1 -Remove
When you maintain a number of servers which require to trigger the same scheduled task manually, you can simply the process by triggering the scheduled task remotely.
In this example I assume that the script is being executed on a dedicated management server (aka job server) within an Exchange Server 2013 environment. The scheduled task must exist on all servers having the same name.
Create a simple PowerShell script at a file location of your choice (i.e. D:\Scripts\Start-RemoteScheduledTasks.ps1)
$cimSession = New-CimSession -ComputerName SERVER1,SERVER2,SERVER3,SERVER4 Start-ScheduledTask TASKNAME -CimSession $cimSession Remove-CimSession $cimSession
Now create a new shortcut on your server desktop with the following configuration:
Target: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "& D:\Scripts\Start-RemoteScheduledTasks.ps1"
If required, select "Run as Adminstrator" in Shortcut -> Advanced settings.
Enjoiy.
This post has been published originally on my legacy blog SF-Tools.
This script removes the proxy address(es) for a selected protocol from mail enabled public folders.
Any proxy address with a given protocol is removed from the proxy addresses list.
The script can fix the alias of mail enabled public folders as well. The code used is based opon a blog post by Shay Levy.
# EXAMPLE 1 # Check mail enabled public folders for proxy addresses having "MS:" as a protocol type. # Do not remove and update addresses, but log found addresses to RemovedAddresses.txt .\Clean-MailEnabledPublicFolders.ps1 -ProtocolToRemove "MS:*" # EXAMPLE 2 # Check mail enabled public folders for proxy addresses having "MS:" as a protocol type. # Remove and update addresses and log found addresses to RemovedAddresses.txt .\Clean-MailEnabledPublicFolders.ps1 -ProtocolToRemove "MS:*" -UpdateAddresses
This Powershell script has been optimized using the ISESteroids™ add-on. Learn more about ISESteroids™ here.