Exchange Server 2010 Service Pack 1 was released yesterday! Here’s a small list of what’s new:
- New Deployment Functionality
- Client Access Server Role Improvements
- Improvements in Transport Functionality
- Permissions Functionality
- Exchange Store and Mailbox Database Functionality
- Mailbox and Recipients Functionality
- High Availability and Site Resilience Functionality
- Messaging Policy and Compliance Functionality
- Unified Messaging Server Role Improvements
- Audit Logging Improvements
- Support for Coexistence with Exchange Online
- Support for Multi-Tenancy
Before installing SP1, please read the Release Notes For Exchange Server 2010 SP1 and make sure you install the necessary prerequisites.
There are also some related downloads with the RTM version of SP1:
- Exchange Server 2010 SP1 UM Language Packs [*NEW Language Packs*] – These downloads contain pre-recorded prompts, grammar files, text to speech data, Automatic Speech Recognition (ASR) files, and Voice Mail Preview capabilities for a specific language that is supported by Exchange 2010 SP1 Unified Messaging (UM). Warning: This UM language pack must only be installed as an add-in to Exchange Server 2010 SP1 Unified Messaging.
- Microsoft Exchange Server 2010 SP1 Language Pack Bundle – This download contains the most recently updated language packs for Exchange 2010. The language bundle includes all packs for all supported languages.
- Exchange Server 2010 SP1 Help – This download contains a standalone version of Microsoft Exchange Server 2010 SP1 Help.
- Exchange Management Shell Quick Reference for Exchange 2010 – This download contains a quick reference sheet that can be used to access frequently used Exchange Management Shell cmdlets and syntax in Microsoft Exchange Server 2010.
Cached Exchange Mode in a Remote Desktop Session Host environment: planning considerations is a technical whitepaper recently released by Microsoft.
Historically, Microsoft Outlook has only been supported in an RDSH environment when it is deployed in Online Mode and connected to a Microsoft Exchange Server. This is still the recommended configuration for Microsoft Outlook 2010 when it is deployed in an RDSH environment. However, customers who deploy Outlook 2010 now have the supported option of enabling Cached Exchange Mode when Outlook 2010 is installed in a Remote Desktop environment. Cached Exchange Mode might be ideal for deployments in which Outlook is connecting over a high latency connection to an Exchange server that is located remotely. For the relatively few users who access Outlook through a remote desktop, this might be the ideal configuration. However, Online Mode against the Exchange server is still the most scalable and optimized configuration for large deployments.
This white paper covers three major areas that you should consider when you deploy Outlook 2010 with Cached Exchange Mode in a Remote Desktop environment:
- Storage footprint
- Performance impact
- Networked Storage
How to accurately evaluate Outlook Cached Exchange Mode when you prepare to deploy Microsoft Office 2010 in your Remote Desktop Session Host (RDSH) environment.
This document is provided as an addendum to the document Remote Desktop Session Host Capacity Planning in Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkId=196861) and is provided so that you can accurately evaluate Outlook Cached Exchange Mode when you prepare to deploy Microsoft Office 2010 in your Remote Desktop Session Host (RDSH) environment.
The Microsoft Forefront Server Protection Script Kit is available to download.
The Forefront Protection Server Script Kit (FPSSK) is a set of interrelated Windows PowerShell scripts that you control from a single master script, the FPSSK.ps1 script file. These scripts enable you to manage the configuration of two Forefront Protection products: Forefront Protection 2010 for Microsoft Exchange Server and Forefront Protection 2010 for SharePoint.
The script kit enables you to capture the names of all computers running Forefront Protection 2010 in a an Active Directory domain, capture Forefront Protection 2010 configuration settings from specified computers, deploy those settings to specified computers, compare captured settings to those on specified running computers, and run basic computer status reports.
The Microsoft Forefront Protection Server Script Kit provides multi-server management for Forefront Protection 2010 for Exchange Server and Forefront Protection 2010 for SharePoint.
The Forefront Protection Server Script Kit provides multi-server management for Forefront Protection 2010 for Exchange Server and Forefront Protection 2010 for SharePoint. In addition to the ability to manage multiple Forefront Protection Servers from a single location, this Solution Accelerator provides easily extensible command-line scripts that help enable server discovery, configuration, deployment, and integration with existing management technologies. It also offers basic reporting capabilities to detect configuration drift and monitor server statistics.
Supported Protection Servers Forefront Protection 2010 for Exchange Server Forefront Protection 2010 for SharePoint
Configuration Management and Reporting Capture server configuration snapshots and push snapshots to any number of servers Compare configuration of any number of servers or baselines Obtain statistics from one or many servers, including information about infected files, detected malware, server health, and more See summary and/or server detail views
Ease of Use Discover Forefront Protection Servers and export information to a .CSV file Use customizable Windows PowerShell™ scripts to enhance your existing automation
To learn more about the Forefront Protection Server Script Kit, visit the TechNet Library.
Send questions or feedback directly to the security team at email@example.com.
Microsoft released recently the Beta version of the Exchange Unified Messaging Troubleshooting Tool. You can invoke the Powershell get-help for the comdlet to find detailed information about each parameter and usage examples:
Get-help Test-ExchangeUMCallFlow -detailed
The Exchange 2010 UM Troubleshooting Tool is used to diagnose configuration errors specific to call answering scenarios and to test whether voice mail is functioning correctly in Exchange 2010 SP1 Unified Messaging deployments.
The Exchange 2010 UM Troubleshooting Tool is an Exchange Management Shell cmdlet that you can use to diagnose configuration errors specific to call answering scenarios and to test whether voice mail is functioning correctly in both on-premises and cross-premises UM deployments. You can use this cmdlet in deployments with Microsoft Office Communications Server 2007 R2 or Microsoft Communications Server "14" or in UM deployments with IP gateways or IP PBXs.
This cmdlet emulates calls and runs a series of diagnostic tests that help on-premises administrators to identify misconfigurations in telephony equipment, Exchange Server 2010 SP1 Unified Messaging settings, and connectivity issues between on-premises and cross-premises deployment of Exchange 2010 SP1 Unified Messaging.
When you run the cmdlet, it states the reason and possible solutions for issues that have been detected. It also outputs general audio quality metrics for diagnosing audio quality issues related to network connectivity such as jitter and average packet loss.
- Supported Operating Systems: Windows 7; Windows Server 2008 R2; Windows Server 2008 R2 Enterprise; Windows Server 2008 R2 for Itanium-based Systems; Windows Server 2008 R2 Foundation; Windows Server 2008 R2 Standard; Windows Server 2008 Service Pack 2; Windows Vista
The components listed below must be installed on a computer running Windows 7, Windows Vista, or the 64-bit edition of Windows Server 2008 prior to installing the Test-ExchangeUMCallFlow cmdlet:
Publishing Exchange Server 2010 with Forefront Unified Access Gateway 2010 and Forefront Threat Management Gateway 2010 is a technical whitepaper recently made available by Microsoft.
This white paper provides information about publishing Microsoft Exchange Server 2010 using Forefront Unified Access Gateway 2010 and Forefront Threat Management Gateway 2010, including how to choose between them for different scenarios, and provides specific steps you can take to configure Forefront TMG and Forefront UAG to publish Exchange 2010.
Allowing access to corporate resources from any location, perhaps using devices that are not controlled by the organization, presents additional risk to the security of the data and services being accessed. Therefore it’s critical to take measures to ensure that the data is being accessed securely, which means implementing technologies such as certificates, firewalls, enforcing pre-authentication, and device or endpoint validation. This white paper provides detailed information about publishing Microsoft Exchange Server 2010 using Forefront Unified Access Gateway 2010 and Forefront Threat Management Gateway 2010, including how to choose between them for different scenarios, and provides specific steps you can take to configure Forefront TMG and Forefront UAG to publish Exchange 2010.
The document contains a neat table that summarizes the differences between publishing Exchange Server 2010 with UAG versus TMG:
This is a nice technical document that was released a couple of weeks ago: Exchange Server 2010 Design and Architecture at Microsoft, How Microsoft IT Deployed Exchange Server 2010.
With Exchange Server 2007, Microsoft IT streamlined the messaging environment through server clusters based on Windows Clustering, and a highly available, direct-attached storage technology helped ensure 99.99 percent availability. However, the costs and general limitations associated with the platforms and technologies used in the Exchange Server 2007 environment prevented Microsoft IT from efficiently meeting emerging messaging and business needs.
By replacing all servers running Exchange Server 2007 with servers running Exchange Server 2010, Microsoft IT created new opportunities to reduce costs and system complexities while increasing security and deploying new features not available in previous versions of Exchange Server.
- Increased reliability through new high-availability technologies, such as database availability groups.
- Increased mailbox sizes through Mailbox servers equipped with cost-efficient storage solutions.
- Reduced total cost of ownership (TCO) through cost-efficient storage solutions and elimination of backups.
- Increased compliance through transport rules, litigation hold, and Information Rights Management.
- Enhanced remote access and mobility options through Client Access servers.