This is the earliest customers have been able to deploy BlackBerry smartphones with a new Exchange release.
In order to enable full support, the following updates must be installed:
Please see the Exchange Team post and the following RIM website on Exchange 2010 for more info.
~Christian
You can download the update here and read more information in the KB article
~Christian
This poster provides a visual reference for understanding key technologies in Windows Server 2008 R2. It focuses on Active Directory Domain Services, Hyper-V, Internet Information Services, Remote Desktop Services (including Virtual Desktop Infrastructure (VDI)), BranchCache, and DirectAccess technologies. In addition, updates to core file services and server management are illustrated. You can use this poster in conjunction with the previously published Windows Server 2008 Component Posters.
Grab it here
With Exchange 2007 RTM and SP1, the Self-Signed Certificates was valid for 1 year. This has been changed to 5 years in Exchange 2007 SP2 and Exchange 2010.
Exchange 2007 SP2:
Exchange 2010:
Please note that the Self-Signed certificate validity period does not change when upgrading existing Exchange 2007 RTM or Exchange 2007 SP1 to Exchange 2007 SP2. The 5 year period is only applied when installing Exchange 2007 SP2 from scratch, or when renewing the Certificate.
It is very simple to renew the certificate to achieve the 5 year validity period, just follow these steps.
Get the list of Exchange Certificates and note the ThumbPrint of the certificate.
Get-ExchangeCertificate | fl ThumbPrint, IsSelfSigned, NotBefore, NotAfter, Services
Replace the existing certificate with a new one
Get-ExchangeCertificate “ThumbPrintOfOldCertificate” | New-ExchangeCertificate
When you create new certificate it is enabled for POP, IMAP and SMTP services, but if the old certificate was also enabled for IIS services, then you need to enable IIS service for new certificate manually
Enable-ExchangeCertificate -ThumbPrint “ThumbPrintOfNewCertificate” -Services IIS
You can now remove the old certificate since it is no longer used
Remove-ExchangeCertificate –ThumbPrint “ThumbPrintOfOldCertificate”
Posted by admin on December 1, 2009 – 09:50
With the release of Exchange 2007 SP2 we provided a Supportability Matrix which outlined the supported configurations for Exchange 2000 SP3, Exchange 2003 SP2, and Exchange 2007 (RTM, SP1, and SP2). But as many are aware, with the release of Windows Server 2008 R2 there have been a variety of questions raised about our support policies and a multitude of feedback. Two pieces of feedback occurred numerous times - the need to support Exchange 2007 on Windows Server 2008 R2 and the need to support Exchange 2003 against Windows Server 2008 R2 Active Directory servers.
In response to this feedback we will be making several updates to the supportability matrix.
- As I recently blogged about, we will be adding support for Exchange 2007 on the Windows Server 2008 R2 platform. While we had hoped to add this application/operating system combination quickly, unfortunately adding this support requires code changes to setup in Exchange 2007. Therefore, our vehicle for adding this support will be via a third Service Pack for Exchange 2007 in the second half of calendar year 2010.
- Exchange 2003 SP2 will now be supported against writeable Windows Server 2008 R2 Active Directory Servers. Additionally, with the General Availability of Exchange Server 2010, and those looking to standardize on Windows Server 2008 R2 we have enhanced the supportability of forest and domain functional levels up to Windows Server 2008 R2. This change is effective immediately on Exchange 2003 SP2.
- Exchange 2007 is now supported on servers running .NET Framework 3.5 SP1 provided that the .NET platform was upgraded from .NET Framework 2.0. This change is also effective immediately on Exchange 2007 SP2.
Each of these changes are being made to provide the flexibility you requested – to change your operating system architecture without changing your messaging architecture. In addition to the existing combinations, we will be adding supportability guidance for Exchange 2010 to the matrix. Note that all of these changes may not immediately appear on the supportability matrix, but be assured that any documentation update lag will not affect your supportability with Microsoft Support.
Finally I do want to update all on one other piece of feedback we have received – allowing the in place upgrade of the operating system under Exchange. Technically the work required to provide this capability is consistent with the work we would need to do to support an in-place upgrade of Exchange itself. As such the amount of work needed is outside the scope and complexity of what we can do in a post release product update. Still we do understand the demand and desire and it is something we will continue to look at for future versions of the product.
While we hope these changes are welcome news and address questions you may have had, we also understand we have areas to improve in. Our desire is to simplify and improve the support experience with Exchange. If you have more feedback, please continue to provide it.
Source: MSExchangeTeam