Released: Update Rollup 7 for Exchange 2007 Service Pack 3

Earlier today the Exchange CXP team released Update Rollup 7 for Exchange Server 2007 SP3 to the Download Center.

This update contains a number of customer-reported and internally found issues since the release of SP3 RU6. See KB2655203: Description of Update Rollup 7 for Exchange Server 2007 Service Pack 3 for more details.

Note: Some of the following KB articles may not be available at the time of publishing this post.

We would like to specifically call out the following fixes which are included in this release:

• KB2617514 Include updated version of Portuguese-Brazil speller.
• KB2696649 Exchange 2007sp3/2010 OWA CSRF via Cookie Tossing.
• KB2696628  Read Receipt is still duplicated when connecting IMAP.

Note that this fix will resolve the CAS to CAS OWA proxying incompatibility with Exchange 2010 SP2 RU1 as discussed here.

General Notes:

For DST Changes: http://www.microsoft.com/time.

Support lifecycle statement: This is the final release under standard support for Exchange 2007, as the Exchange 2007 Mainstream Support has now ended. Extended Support for Exchange 2007 SP3 will end on 4/11/2017. Please see the Microsoft Support Lifecycle page for more information about Microsoft Support Lifecycle for Exchange 2007. Got questions about Microsoft Support Lifecycle Policy? Head over toMicrosoft Support Lifecycle Policy FAQ.

Note for Forefront Protection for Exchange users  For those of you running Forefront Protection for Exchange, be sure you perform these important steps from the command line in the Forefront directory before and after this rollup’s installation process. Without these steps, Exchange services for Information Store and Transport will not start after you apply this update. Before installing the update, disable ForeFront by using this command: fscutility /disable. After installing the update, re-enable ForeFront by runningfscutility /enable.

(source : http://blogs.technet.com/b/exchange/archive/2012/04/16/released-update-rollup-7-for-exchange-2007-service-pack-3.aspx)

Released: Update Rollup 2 for Exchange 2010 Service Pack 2

Earlier today the Exchange CXP team released Update Rollup 2 for Exchange Server 2010 SP2 to the Download Center.

This update contains a number of customer-reported and internally found issues since the release of SP2 RU1. See KB2661854: Description of Update Rollup 2 for Exchange Server 2010 Service Pack 2 for more details.

Note: Some of the following KB articles may not be available at the time of publishing this post.

We would like to specifically call out the following fixes which are included in this release:

• KB2696913 You cannot log on to Outlook Web App when a proxy is set up in an Exchange Server 2010 environment
• KB2688667 High CPU in W3WP when processing recurrence items who fall on DST cutover
• KB2592398 PR_INTERNET_MESSAGE_ID is the same on messages resent by Outlook
• KB2630808 EwsAllowMacOutlook Setting Not Honored
• KB2661277 Android/Iphones stuck with 451 during Cross forest proxy in datacenter
• KB2678414  Contact name doesn’t display company if name fields are left blank

Note that this fix will not cause the CAS to CAS OWA proxying incompatibility with Exchange 2007 as discussedhere. No additional updates are required on Exchange 2007 for proxying to work once Exchange 2010 SP2 RU2 is installed.

General Notes:

For DST Changes: http://www.microsoft.com/time.

Note for Forefront Protection for Exchange users  For those of you running Forefront Protection for Exchange, be sure you perform these important steps from the command line in the Forefront directory before and after this rollup’s installation process. Without these steps, Exchange services for Information Store and Transport will not start after you apply this update. Before installing the update, disable ForeFront by using this command: fscutility /disable. After installing the update, re-enable ForeFront by runningfscutility /enable.

SQL Requests & Powershell

It could be really hard to find something interesting on the web when we encountered a trouble in Powershell.

After a long search, I found it ! So, let’s share..

A request in SQL using powershell can be send using .Net Frameword.

You should have in mind that SQL request through powershell are exactly the same like standard SQL requests !

Here is an example with a simple Select :

$conec = “server=;database=;Integrated Security=sspi”
$cmd = “SELECT FROM WHERE ”
$da = new-object System.Data.SqlClient.SqlDataAdapter ($cmd, $conec)
$dt = new-object System.Data.DataTable
$da.fill($dt)

The “Integrated Security” allow to use Windows Authentication, so the account used to launch the powershell script should have rights on the Database !

The SQL request’s results are contained into the “$dt” variable.

So… Let’s “play” now !