McAfee support confirmed this to be a compatibility issue for which they currently don’t have a solution. To be continued …

Symptom: Even when not-read message are disabled in Outlook, users automatically send “Your email was deleted without being read” to the sender. The messages are related to mails which are 120 days old.

Cause: In my case the user moves all his unread mails from his Inbox to different mapped PST files with Client side rules. The resulting not-read message is known bug in Exchange 2010 SP1 RU3. An interim update is available on demand (KB2471964), though we decided not to install it as according to Microsoft the issue shall be solved in RU4. Release of RU4, quoting a Microsoft employee, will be somewhere mid July 2011 (no promises).

Imagine you have all your servers somewhere listed in a SQL database (home-made, our in a 3th party application), you could use them to fill the Receive Connector on a schedule. You will have to add the task on every server which needs the receive connector.

To run the script, a scheduled task can be created on a server which needs the receive connector:

Program/Script: C:\exchangeScripts\serverdb_receiveconnector.ps1
Start In: C:\Program Files\Microsoft\Exchange Server\V14\Bin

The following 2 scripts should be made available on the system:

C:\serverdb_receiveconnector.bat:

Powershell.exe -PSConsoleFile “C:\Program Files\Microsoft\Exchange Server\V14\Bin\exshell.psc1″ -command “C:\serverdb_receiveconnector.ps1″

Now the actual script called “serverdb_receiveconnector.ps1″. Replace the $query parameter with the query which applies to your database, use the correct server/database/user/password to access the database.

#Receive Connector
$rc=”Test Receive Connector”
$query=”SELECT server_name FROM Servers”
$connstring=”server=FQDNSQLServer;database=DatabaseName;trusted_connection=false;UID=UserToAccessDB;PWD=PlainTextPasswordHere”
$Connection = New-Object System.Data.SQLClient.SQLConnection
$Connection.ConnectionString = $ConnString
$Connection.Open()
$Command = New-Object System.Data.SQLClient.SQLCommand
$Command.Connection = $Connection
$Command.CommandText = $Query
$Reader = $Command.ExecuteReader()
$Counter = $Reader.FieldCount

$conn = Get-ReceiveConnector $rc
Set-ReceiveConnector $rc -RemoteIPRanges “255.255.255.255″
while ($Reader.Read()) {
for ($i = 0; $i -lt $Counter; $i++) {
$ipadd=$Reader.GetValue($i)

Try{
$ipaddtranslated=[System.Net.Dns]::GetHostAddresses($ipadd)
}Catch{
write-host “DNS lookup failed for ” + $ipadd
}

Try{
$conn.RemoteIPRanges += “” + $ipaddtranslated
}Catch{
write-host “Add failed for ” + $ipadd
}

}
}
Set-ReceiveConnector $rc -RemoteIPRanges $Conn.RemoteIPRanges
$Connection.Close()

Replace the “ThisIstheOUToWhichYouWantToLimitTheDeletions” with the short OU name (no ldap path needed), so e.g. “Financial Department”

$AllUsers = get-mailbox * -ResultSize Unlimited -OrganizationalUnit “ThisIstheOUToWhichYouWantToLimitTheDeletions”
ForEach ($User in $AllUsers) {
$user.displayname | out-file C:\Mailboxpermissions.txt -append
get-mailboxfolderpermission $user | Select User, FolderName, AccessRight | out-file C:\Mailboxpermissions.txt -append
$userperm=get-mailboxfolderpermission $user | Select User

ForEach($perm in $userperm) {
if($perm -match “S-1-5-21″){
$sid=$perm.user
Remove-MailboxFolderPermission -identity $user -user $sid -Confirm:$false
}
}
}

Stream to Me: download here
Serve To Me: download here

After noticing this in EWS we had 3 cases were users forwarded messages to home PCs (Outlook 2010) from Office workstations (Outlook 2003,2007) and saw exactly the same issue, no EWS involved. The issue is still pending investigation …

When you send a mail with an inline attachment, the attachment is not visible by the receiving party which uses an Exchange 2007/2010 Exchange environment. The client can be outlook 2003/2007/2010. An inline attachment is an attachment created by e.g. dragging a file in the mail while creating it to add the attachment. This can be easily fixed by using the following configuration adjustment:

Exchange Server 2010:

• Stop the Exchange Transport service.
• Locate the EdgeTransport.exe.config file. This file is located in the following path:
• C:\Program Files\Microsoft\Exchange Server\Bin\
• In the EdgeTransport.exe.config file, add the following entry between the <appSettings> element and the </appSettings> element:

  <add key=”TreatInlineDispositionAsAttachment” value=”true” />

• Restart the Transport service.

If the TreatInlineDispositionAsAttachment option does not exist or if the option is set to “false,” the behavior is the same as the behavior that is mentioned in the “Symptoms” section.

If the TreatInlineDispositionAsAttachment option is set to “true,” the inline attachment that is not referenced is available for download.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;954684

http://support.microsoft.com/kb/958662

When you have the folling symptoms with outlook 2007 you can use the following workarround when using an Exchange 2010 environment:

Symptoms:

The following workarround can be used:

MS: : http://support.microsoft.com/kb/958934/en-us

Using regedit, navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

And on the key, make a new DWORD value, name it DisableTaskOffload. Set its value to 1.