Microsoft released the newest version of the Exchange 2010 language pack that resolves three key issues some customers have experienced. The Exchange 2010 Service Pack 2 included the full language pack, and if you are not experiencing the problems or have not installed any language packs post SP2 you do not need to apply this language pack.
- Events being logged in the application log for any user not using en-us as their chosen language after installing SP2 RU1.
- A wording error in the German version of OWA
- A wording error in the Dutch version of OWA
You can download the newest version of the Exchange 2010 language pack here.
Also, the Exchange Server Deployment Assistant (ExDeploy) now includes full checklist support for configuring hybrid deployments for Exchange 2010 SP2 organizations interested in maintaining some users on-premises and some users hosted in the cloud by Microsoft Office 365 for enterprises.
"Like the Exchange 2003 scenario released in March and the Exchange 2007 scenario released in April, this Exchange 2010 scenario also uses the Hybrid Configuration wizards to streamline deployment," Microsoft said.
Important information to know about this new Exchange 2010 scenario:
- Information is only available in English at this time.
- You'll not need to add any additional Exchange 2010 servers to your current Exchange organization. Your existing on-premises Exchange 2010 servers will be configured to support the hybrid deployment.
- If you have previously configured a hybrid deployment using ExDeploy and Exchange 2010 SP1 and still need guidance; don't worry, we haven't forgotten about you! For your convenience, checklists for configuring hybrid deployments with Exchange 2010 SP1 are here.
You can find Exchange Server Deployment Assistant (ExDeploy) here.
Finally, Microsoft Security Development Lifecycle Process Guidance - version 5.2 (SDL 5.2) is now available for download (.docx format) as well as updated online in the MSDN library.
"The changes in SDL 5.2 demonstrate how the Microsoft SDL evolves internally to address new attack vectors, provides guidance that leads to implementation of new protections, and improves the security of Microsoft products throughout our software development lifecycle," Microsoft said.
This public update of Microsoft's SDL Process Guidance documentation is intended to provide transparency into how we implement the SDL at Microsoft.