The KB is http://support.microsoft.com/?kbid=982639 

Download from here http://www.microsoft.com/downloads/details.aspx?FamilyID=09b4973e-3a80-4fb9-9f60-5c6e2b7a2727&displaylang=en

By the way Exchange 2007 SP2 is at Update Rollup 4 : http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b8f7f872-16d5-49d6-9867-adc01351c06f 

The Exchange Server 2007 SP3 bits are available online in 11 languages and on two platforms (32/64bit). The accompanying documentation includes: Release Notes and What's New in Exchange Server 2007 SP3.

My fav is this :)

Exchange 2007 SP3 introduces password reset functionality for Internet Information Services (IIS) 7. For more information, see How to Enable the Exchange 2007 SP3 Password Reset Tool.

Problem:

When planning to deploy Exchange 2010 RTM Schema in an Exchange 2007 environment that is running SP3, you will encounter the following error:

“Setup encountered a problem while validating the state of Active Directory. The Active Directory schema version (14625) is higher than the Setup’s version (14622). Therefore, PrepareSchema can’t be executed.”

This is becasue the schema version of Exchange 2007 SP3 is higher than the one from the Exchange 2010 RTM setup.

Solution:

Exchange 2007 SP3 already has the schema changes required by Exchange 2010, so you don’t need to perform E2010 prepareschema again. Please remember, that you still need to run setup.com /PrepareAD from Exchange 2010 setup.

Head over to the Download Center to download the Exchange Server 2010 Architecture Poster (PDF).

I was thinking to write a blog post around schema version till I found this great post:

http://www.bhargavs.com/index.php/2009/11/20/verify-exchange-server-schema-version/

Download: http://www.microsoft.com/download/en/details.aspx?id=28751

For a list of changes that are included in this update rollup, see KB2608656.

The Calendar Checking Tool for Outlook is a command-line program that checks Outlook Calendars for problems. To use this tool, the Outlook calendar must reside on a Microsoft Exchange Server. The tool does not work with IMAP, with POP3, or with other non-Exchange mail servers. The tool opens an Outlook profile, opens the Outlook Calendar, and then checks several things such as permissions, free/busy publishing, and auto booking. Then, the tool checks each item in the calendar folder for problems that can cause items to seem to be missing or that might otherwise cause problems in the Calendar.

http://www.microsoft.com/download/en/details.aspx?id=28786

Very happy to hear that...dont miss it :)

http://blogs.technet.com/b/exchange/archive/2012/03/06/mec-is-back.aspx

Creates an HTML Report showing Distribution and Dynamic Distribution Group Summary and Members

http://www.get-mailbox.org/downloads/32

Generate Mailbox Permission Report using Powershell (who has access to where )

http://www.get-mailbox.org/exchange-2010/generate-mailbox-permission-report-using-powershell/

.

On 16^th April 2012  the Exchange CXP (Customer Experience) team released Update Rollup 2 for Exchange Server 2010 SP2 and Update Rollup 7 for Exchange Server 2007 SP3  to the Download Center

 Update Rollup 2 for Exchange Server 2010 SP2 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.

 One of the key issues addressed by this rollup is that it fixes the issue in KB2696913 : You cannot log on to Outlook Web App when a proxy is set up in an Exchange Server 2010 environment.

 Update Rollup 7 for Exchange Server 2007 SP3 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.

 For Exchange Server and Update Rollups Builds Numbers kindly visit  http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollups-builds-numbers.aspx 

This Script  can be used to find Exchange 2007 and Exchange 2010 build numbers in your environment.

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 running fscutility /enable.

Exchange team blog post: http://blogs.technet.com/b/exchange/archive/2012/05/29/released-update-rollup-3-for-exchange-2010-service-pack-2.aspx

download from here: http://www.microsoft.com/en-us/download/details.aspx?id=29899

I have started seeing this issue recently while doing my usual customer visits , kindly check the workaround for the time being

http://blogs.technet.com/b/exchange/archive/2012/06/28/mailboxes-on-a-database-are-quarantined-in-an-environment-with-system-center-operations-manager.aspx

documentation

http://technet.microsoft.com/en-us/library/bb124558(EXCHG.150).aspx

You can download the rollup from here http://www.microsoft.com/download/en/details.aspx?id=27849

Post rollup,  the binary build number should be 14.1.355.02.

For Turkish customers, the "Retention policies are applied to Contact items unexpectedly in an Exchange Server 2010 environment" issue is resolved in this rollup http://support.microsoft.com/kb/2571791

Mailbox cleanup could not completely remove the mailbox for user XXXXXXX following mailbox removal. Encountered error 0xfffffae8. Should this message continue to persist for the same mailbox, it may be indicative of a problem that requires
further investigation.

to solve this problem dismoun/mount the current databse (if previous databse still exist dismount/mount this database also )

http://www.microsoft.com/download/en/details.aspx?id=26554

http://www.microsoft.com/download/en/details.aspx?id=1573

$user = Get-Credential

$session = New-PSSession -Configurationname Microsoft.Exchange –ConnectionUri http://servername/powershell -Credential $user

Import-PSSession $session

Version: 6553.0002
Date Released:11/4/2013
Notable Changes:
 

• Fix to handle Read-Only Domain Controllers in Password Sync.
• DirSync can be installed on a Domain Controller (Development purposes).  Documentation on how to deploy can be found here
      

You can check your DirSync version by running the following PowerShell command: 

(GP 'hklm:SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Online Directory Sync').DisplayVersion

The latest version can be downloaded here: Windows Azure Active Directory Sync tool – 64 bit

Nice tool, adding it to the blog , so we never forget about it

The Exchange ActiveSync Admin (EASAdmin) tool enables administrators to manage the process of remotely erasing lost, stolen, or otherwise compromised mobile devices. The EASAdmin Tool is designed for use with Exchange Server 2010, Exchange 2013, Office 365 (Wave14 and 15).

Download and further details @ http://gallery.technet.microsoft.com/Tool-to-manage-Exchange-8a458b2a

The big news is here :)

Exchange Server 2013 Service Pack 1 Coming in Early 2014

Few notable improvements are:

• Windows Server 2012 R2 Support
• S/MIME support for OWA Support for S/MIME
• Edge Transport Server Role

For further details , check the Exchange team blog @ http://blogs.technet.com/b/exchange/archive/2013/11/20/exchange-server-2013-service-pack-1-coming-in-early-2014.aspx

Exchange 2013 CU3

The Exchange team is announcing today the availability of our most recent quarterly servicing update to Exchange Server 2013. Cumulative Update 3 for Exchange Server 2013 and updated UM Language Packs are now available on the Microsoft Download Center. Cumulative Update 3 includes fixes for customer reported issues, minor product enhancements and previously released security bulletins. A complete list of customer reported issues resolved in Exchange Server 2013 Cumulative Update 3 can be found in Knowledge Base Article KB 2892464.

Our next update for Exchange 2013, Cumulative Update 4, will be released as Exchange 2013 Service Pack 1. Customers who are accustomed to deploying Cumulative Updates should consider Exchange 2013 SP1 to be equivalent to CU4 and deploy as normal.

Exchange 2010 SP3 Rollup 3

The Exchange team is announcing today the availability of Update Rollup 3 for Exchange Server 2010 Service Pack 3. Update Rollup 3 is the latest rollup of customer fixes available for Exchange Server 2010. The release contains fixes for customer reported issues and previously released security bulletins. Update Rollup 3 is not considered a security release as it contains no new previously unreleased security bulletins. A complete list of issues resolved in Exchange Server 2010 Service Pack 3 Update Rollup 3 may be found in KB2891587.

I have written before about the case of a missing shortcut for Exchange PowerShell here http://blogs.technet.com/b/nawar/archive/2010/09/03/exchange-management-shell-ems-missing-after-applying-exchange-2010-sp1.aspx

Today while working onsite with a customer trying to executing some Exchange PowerShell commands , we started getting the following

“'Microsoft.Exchange.Management.PowerShell.E2010' is not installed on this machine.”

The first thing we did was to verify that the ConnectFunctions.ps1 , RemoteExchange.ps1 and CommonConnectFunctions.ps1 files are present in the %ExchangeInstallPath%\bin directory.

NOTE : If these files are missing, you can copy the files from the Exchange Server 2010 Service Pack  installation media (depending on the service pack you are using) to the %ExchangeInstallPath%\bin directory.
These files are present in the \setup\serverroles\common folder.

Since those files existed on the server that we were having the problem with , we proceeded to check the Exchange registered snap-ins with the following command from the Exchange PowerShell:

Get-PSSnapin –Registered

For Exchange 2010 this should return

Name        : Microsoft.Exchange.Management.PowerShell.E2010

PSVersion   : 1.0

Description : Admin Tasks for the Exchange Server

Name        : Microsoft.Exchange.Management.PowerShell.Setup

PSVersion   : 1.0

Description : Setup Tasks for the Exchange Server

Name        : Microsoft.Exchange.Management.Powershell.Support

PSVersion   : 1.0

Description : Support Tasks for the Exchange Server

In our case it only returned

Name        : Microsoft.Exchange.Management.PowerShell.Setup

PSVersion   : 1.0

Description : Setup Tasks for the Exchange Server

Looking at the following registry key on the server (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\) showed only the registry key related to setup, which means we need to manually create the other two registry keys to solve the broken Exchange PowerShell problem.

The easiest way to do this is by exporting two missing resitry key from a healthy server , but you need to make sure that the install path is exactly the same and servers are running the same version, if the installation path is not the same you can change to match the path on your broken server after exporting the key .

The actual keys are below , but as I mentioned before make sure that the installation path of exchange from server you export from matches the exchange installation path of the server you are importing to

Admin

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.PowerShell.E2010]

"CustomPSSnapInType"="Microsoft.Exchange.Management.PowerShell.AdminPSSnapIn"

"ApplicationBase"="C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin"

"AssemblyName"="Microsoft.Exchange.PowerShell.Configuration, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"

"Description"="Admin Tasks for the Exchange Server"

"ModuleName"="C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin\\Microsoft.Exchange.PowerShell.Configuration.dll"

"PowerShellVersion"="1.0"

"Vendor"="Microsoft Corporation"

"Version"="14.0.0.0"

Support

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.Powershell.Support]

"CustomPSSnapInType"="Microsoft.Exchange.Management.Powershell.Support.SupportPSSnapIn"

"ApplicationBase"="C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin"

"AssemblyName"="Microsoft.Exchange.Management.Powershell.Support, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"

"Description"="Support Tasks for the Exchange Server"

"ModuleName"="C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin\\Microsoft.Exchange.Management.Powershell.Support.dll"

"PowerShellVersion"="1.0"

"Vendor"="Microsoft Corporation"

"Version"="14.0.0.0"

Exchange 2013 SP1 is expected to have a new protocol implementation called MapiHttp. To help you understand this better at this stage, Joe Warren, Principal Software Developer, delivered a presentation covering the Exchange 2013 MAPIHttp protocol implementation and answered some questions.

You can view and download the presentation from here.

And, we will continue with our on-premises releases of both SharePoint Server and Exchange Server on our traditional 2-3 year release cadence.  We’ll also continue supporting hybrid deployments spanning both cloud and on prem technologies.

http://blogs.office.com/2014/02/17/transforming-work-transforming-office/