The community script Copy-ReceiveConnector has been updated. Receive Connectors that do exist on a specified target server can now be updated.
Besides the receive connector communication the assigned permissions of the source connector can be copied as well.
Are you unsure, if you should migrate to Office 365? You want to know more about security of cloud applications and services? Your Exchange Server infrastructure requires an upgrade? Contact me via email: email@example.com
A new community PowerShell script to simplify Exchange Server mailbox migrations has been published to TechNet Gallery and Github.
See script help for examples.
Check out the professional services provided by Granikos for planning and migrating your existing Exchange Server infrastructure to the cloud.
PowerShell module providing centralizied logging and other helpful functions.
$ScriptDir = Split-Path $script:MyInvocation.MyCommand.Path
$ScriptName = $MyInvocation.MyCommand.Name
# Create a new logger object, keeping the last 14 days of log files
$logger = New-Logger -ScriptRoot $ScriptDir -ScriptName $ScriptName -LogFileRetention 14
# Write a new informational message to the log file
$logger.Write('My Log Message')
# Write an error message to the log file
$logger.Write('My custom error message')
# Write a warning message to the log file
$logger.Write('My custom warning')
# Send a log file by email at the end of your script
$logger.SendLogFile('firstname.lastname@example.org', 'email@example.com', 'smtpserver.mcsmemail.de')
You can "install" a PowerShell module by copying the module to a sub folder of the same name as the module in either of the two following locations:
PS C:\> $env:PSModulePath
Create a new folder named GlobalFunctions in C:\Program Files\WindowsPowerShell\Modules
Copy the GlobalFunctions.psm1 file to C:\Program Files\WindowsPowerShell\Modules\GlobalFunctions
These steps assume that you use a dedicated PowerShell scripts folder, e.g. D:\MyScripts
Close the current PowerShell window and open a new PowerShell window. That's it.
When using PowerShell 5, you can simply use the following PowerShell command from within an administrative PowerShell window.
When a new version of the GlobalFunctions module has been released, use the following PowerShell command to update the module.
This script copies a single receive connector from a source Exchange Server to a single target Exchange server or all other Exchange servers.
The primary purposes of this script are:
Find the most recent full documentation at GitHub.
Copy Exchange 2013/2016 receive connector RC2 from server MBX01 to server MBX2
.\Copy-ReceiveConnector.ps1 -SourceServer MBX01 -ConnectorName RC2 `
-TargetServer MBX2 -DomainController MYDC1.mcsmemail.de
Copy Exchange 2013/2016 receive connector RC2 from server MBX01 to all other Exchange 2013 servers
.\Copy-ReceiveConnector.ps1 -SourceServer MBX01 -ConnectorName RC1 `
-CopyToAllOther -DomainController MYDC1.mcsmemail.de
Copy Exchange 2013/2016 receive connector relay from Exchange 2007 server MBX2007 to Exchange 2013 server MBX01 and reset network bindings
.\Copy-ReceiveConnector.ps1 -SourceServer MBX2007 -ConnectorName "relay" `
-TargetServer MBX01 -MoveToFrontend -ResetBindings `
Additional credits go to Jeffery Land, https://jefferyland.wordpress.com
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
Switch to send an Html report
Email address of report sender
Email address of report recipient
SMTP Server for email report
This post has first been posted on my legacy blog.