I will show you today how to manage, backup and restore you sender safe list on Exchange 2007 and 2010 using exchange management shell cmdlets.
To add a entry
$SafeSenders = (Get-ContentFilterConfig).bypassedSenders $SafeSenders.Add("firstname.lastname@example.org") Set-ContentFilterConfig -BypassedSenders $SafeSenders
To remove an entry
We are all faced, from time to time, with the need to change the IP address of our Microsoft Exchange server.
There is no hard relation between the operation of your Exchange server and its IP address thus changing the latter will not break your system.
In short this operation can be considered as safe however it requires a certain level of planning and considerations. I will try to cover in this article the various things you should think about before and after actually changing the IP of your server.
If you are familiar with Microsoft Exchange 2007 you already know about the AddReplicaToPFRecursive.ps1 script that can be found in the "X:\Program Files\Microsoft\Exchange Server\Scripts", however this script has a bug it doesn't look to support public folders which names contains spaces.
It is quite common to enclose parameters that contains spaces with "quotations" but that doesn't work here.
If you simply try to use the following it will fail.
AddReplicatoPFRecursive.ps1 -TopPublicFolder “\PublicFolder with space” -ServerToAdd “servername”
The solution turned out to be to use single quotes inside the double quotes so it should be something like
AddReplicatoPFRecursive.ps1 -TopPublicFolder “'\PublicFolder with space'” -ServerToAdd “servername”
That's really weird and not standard but it works !
Disclaimer: Guys if you happen to be suffering from "Event ID: 494" syndrom on your Microsoft Exchange Server do not attempt anything before reading this article, I might save you a lot of time.
It is always frustrating to me to receive a calls from customers telling me that their exchange database is refusing to mount and that they have tried everything, even restored from their last backup but nothing seems to work! Oh if only they'd call earlier
Symptoms: Typically a storage group will fail to mount and an error will be logged in the Application Log with an event id of 494. The error is the following